Re: [PD] max midi in devices

[Miller Puckette]

What OS are you on?  (I just found out there are problems finding MIDI
devices by name in linux, FWIW)

thanks
Miller

On Fri, Aug 22, 2014 at 11:21:19PM -0300, Alexandre Torres Porres wrote:
> hey, works, thought I had tried it exactly like this too, but maybe not.
> Now, I couldn't do it by calling the devices by name, how should I do it?
> 
> Cool, now I'm running 5 inputs, but the midiin dialog only shows the first
> 4 devices. Is there a way to make it show more than that?
> 
> What is the maximum number of inputs now? I assume there is a limit.
> 
> I also always wondered how the devices are numbered in a sequence - I
>  mean, why they are listed in the order they show up. Is there a way to
> control the order? Same doubt applies to audio soundcard input.
> 
> This might be useful because MIDI channel number depend on this order,
> right?
> 
> thanks
> 
> 
> 2014-08-22 21:26 GMT-03:00 Miller Puckette :
> 
> > The startup flags should just be "-midiindev 1,2,3,4,5" (without the "pd").
> >
> > cheers
> > M
> >
> > On Fri, Aug 22, 2014 at 08:23:23PM -0300, Alexandre Torres Porres wrote:
> > > "just do for midi input:
> > > pd -midiindev 1,2,3,4,5"
> > >
> > > doesn't seem to work, is this exactly what I need to insert in the
> > startup
> > > flags?
> > >
> > > cheers
> > >
> > >
> > > 2014-08-22 15:44 GMT-03:00 Nicolas Montgermont <
> > nicolas_montgerm...@yahoo.fr
> > > >:
> > >
> > > >  just do for midi input:
> > > > pd -midiindev 1,2,3,4,5
> > > > n
> > > >
> > > > Le 22/08/2014 19:41, Alexandre Torres Porres a écrit :
> > > >
> > > > hmm, I'm curious about that nicolas - one way or another I think it'd
> > be
> > > > good to epxand this limit by default, I don't see what would be the
> > problem
> > > > for that, right?
> > > >
> > > >  don't know any midi merger software, any recommendations?
> > > >
> > > >  cheers
> > > >
> > > >
> > > > 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont <
> > > > nicolas_montgerm...@yahoo.fr>:
> > > >
> > > >> IIRC you can have more than 4 devices if you ask for them in command
> > line.
> > > >> It's just the graphical interface that is limited to 4
> > > >> n
> > > >>
> > > >>
> > > >> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> > > >> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
> > > >> por...@gmail.com> wrote:
> > > >> >> Hi, can we only have 4 multiple midi inputs in od?
> > > >> >>
> > > >> >> what is the workaround?
> > > >> >>
> > > >> > A midi merger (either hard or software)
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >>  http://www.nimon.org
> > > >>
> > > >>
> > > >> ___
> > > >> Pd-list@lists.iem.at mailing list
> > > >> UNSUBSCRIBE and account-management ->
> > > >> http://lists.puredata.info/listinfo/pd-list
> > > >>
> > > >
> > > >
> > > > -- http://www.nimon.org
> > > >
> > > >
> >
> > > ___
> > > Pd-list@lists.iem.at mailing list
> > > UNSUBSCRIBE and account-management ->
> > http://lists.puredata.info/listinfo/pd-list
> >
> >

> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Alexandre Torres Porres]

hey, works, thought I had tried it exactly like this too, but maybe not.
Now, I couldn't do it by calling the devices by name, how should I do it?

Cool, now I'm running 5 inputs, but the midiin dialog only shows the first
4 devices. Is there a way to make it show more than that?

What is the maximum number of inputs now? I assume there is a limit.

I also always wondered how the devices are numbered in a sequence - I
 mean, why they are listed in the order they show up. Is there a way to
control the order? Same doubt applies to audio soundcard input.

This might be useful because MIDI channel number depend on this order,
right?

thanks


2014-08-22 21:26 GMT-03:00 Miller Puckette :

> The startup flags should just be "-midiindev 1,2,3,4,5" (without the "pd").
>
> cheers
> M
>
> On Fri, Aug 22, 2014 at 08:23:23PM -0300, Alexandre Torres Porres wrote:
> > "just do for midi input:
> > pd -midiindev 1,2,3,4,5"
> >
> > doesn't seem to work, is this exactly what I need to insert in the
> startup
> > flags?
> >
> > cheers
> >
> >
> > 2014-08-22 15:44 GMT-03:00 Nicolas Montgermont <
> nicolas_montgerm...@yahoo.fr
> > >:
> >
> > >  just do for midi input:
> > > pd -midiindev 1,2,3,4,5
> > > n
> > >
> > > Le 22/08/2014 19:41, Alexandre Torres Porres a écrit :
> > >
> > > hmm, I'm curious about that nicolas - one way or another I think it'd
> be
> > > good to epxand this limit by default, I don't see what would be the
> problem
> > > for that, right?
> > >
> > >  don't know any midi merger software, any recommendations?
> > >
> > >  cheers
> > >
> > >
> > > 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont <
> > > nicolas_montgerm...@yahoo.fr>:
> > >
> > >> IIRC you can have more than 4 devices if you ask for them in command
> line.
> > >> It's just the graphical interface that is limited to 4
> > >> n
> > >>
> > >>
> > >> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> > >> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
> > >> por...@gmail.com> wrote:
> > >> >> Hi, can we only have 4 multiple midi inputs in od?
> > >> >>
> > >> >> what is the workaround?
> > >> >>
> > >> > A midi merger (either hard or software)
> > >> >
> > >> >
> > >> >
> > >>
> > >> --
> > >>  http://www.nimon.org
> > >>
> > >>
> > >> ___
> > >> Pd-list@lists.iem.at mailing list
> > >> UNSUBSCRIBE and account-management ->
> > >> http://lists.puredata.info/listinfo/pd-list
> > >>
> > >
> > >
> > > -- http://www.nimon.org
> > >
> > >
>
> > ___
> > Pd-list@lists.iem.at mailing list
> > UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Miller Puckette]

The startup flags should just be "-midiindev 1,2,3,4,5" (without the "pd").

cheers
M

On Fri, Aug 22, 2014 at 08:23:23PM -0300, Alexandre Torres Porres wrote:
> "just do for midi input:
> pd -midiindev 1,2,3,4,5"
> 
> doesn't seem to work, is this exactly what I need to insert in the startup
> flags?
> 
> cheers
> 
> 
> 2014-08-22 15:44 GMT-03:00 Nicolas Montgermont  >:
> 
> >  just do for midi input:
> > pd -midiindev 1,2,3,4,5
> > n
> >
> > Le 22/08/2014 19:41, Alexandre Torres Porres a écrit :
> >
> > hmm, I'm curious about that nicolas - one way or another I think it'd be
> > good to epxand this limit by default, I don't see what would be the problem
> > for that, right?
> >
> >  don't know any midi merger software, any recommendations?
> >
> >  cheers
> >
> >
> > 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont <
> > nicolas_montgerm...@yahoo.fr>:
> >
> >> IIRC you can have more than 4 devices if you ask for them in command line.
> >> It's just the graphical interface that is limited to 4
> >> n
> >>
> >>
> >> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> >> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
> >> por...@gmail.com> wrote:
> >> >> Hi, can we only have 4 multiple midi inputs in od?
> >> >>
> >> >> what is the workaround?
> >> >>
> >> > A midi merger (either hard or software)
> >> >
> >> >
> >> >
> >>
> >> --
> >>  http://www.nimon.org
> >>
> >>
> >> ___
> >> Pd-list@lists.iem.at mailing list
> >> UNSUBSCRIBE and account-management ->
> >> http://lists.puredata.info/listinfo/pd-list
> >>
> >
> >
> > -- http://www.nimon.org
> >
> >

> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Alexandre Torres Porres]

"just do for midi input:
pd -midiindev 1,2,3,4,5"

doesn't seem to work, is this exactly what I need to insert in the startup
flags?

cheers


2014-08-22 15:44 GMT-03:00 Nicolas Montgermont :

>  just do for midi input:
> pd -midiindev 1,2,3,4,5
> n
>
> Le 22/08/2014 19:41, Alexandre Torres Porres a écrit :
>
> hmm, I'm curious about that nicolas - one way or another I think it'd be
> good to epxand this limit by default, I don't see what would be the problem
> for that, right?
>
>  don't know any midi merger software, any recommendations?
>
>  cheers
>
>
> 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont <
> nicolas_montgerm...@yahoo.fr>:
>
>> IIRC you can have more than 4 devices if you ask for them in command line.
>> It's just the graphical interface that is limited to 4
>> n
>>
>>
>> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
>> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
>> por...@gmail.com> wrote:
>> >> Hi, can we only have 4 multiple midi inputs in od?
>> >>
>> >> what is the workaround?
>> >>
>> > A midi merger (either hard or software)
>> >
>> >
>> >
>>
>> --
>>  http://www.nimon.org
>>
>>
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> http://lists.puredata.info/listinfo/pd-list
>>
>
>
> -- http://www.nimon.org
>
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] [PD-announce] pd 0.46-0test1 released

[Chris McCormick]

Hi Miller,

On 22/08/14 23:08, Miller Puckette wrote:
> I think I'd want to disambiguate everything in one mechanism - perhaps
> interspersing the message itself with the information (putting the 
> count in ahead of the address, and also putting symbols 'f', 'i', 's' and
> 'b' in front of the items).  But I'm thinking it's wisest to wait and see
> what people need in real usage - if, indeed, anyone ever wants such
> disambiguation at all.

Gotcha, and anyway it strikes me that the user can still get the number
of address components already by counting the slash characters in the
input, which is a trivial subpatch/abstraction.

Cheers,

Chris.

-- 
http://mccormick.cx/

___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] [PD-announce] pd 0.46-0test1 released

[Miller Puckette]

I think I'd want to disambiguate everything in one mechanism - perhaps
interspersing the message itself with the information (putting the 
count in ahead of the address, and also putting symbols 'f', 'i', 's' and
'b' in front of the items).  But I'm thinking it's wisest to wait and see
what people need in real usage - if, indeed, anyone ever wants such
disambiguation at all.

cheers
M

On Fri, Aug 22, 2014 at 06:14:02PM +0200, Chris McCormick wrote:
> Hi Miller,
> 
> Very cool, thanks for getting OSC objects into native Pd!
> 
> On 21/08/14 17:22, Miller Puckette wrote:
> > Correct.  The bet I'm making is that nobody who's receiving OSC messages
> > would have any doubt which is it.  YOu have to know what messages the source
> > is sending you and what to do with them anyway.
> >
> > OTOH, if it does turn out that there's any real situation when such 
> > disamiguation is needed (for instance, storing OSC streams for later 
> > sequencing?) the objects could easily be altered to put in symbolic markers
> > to separate everything - this would be in the form of a creation flag to
> > make it an option.  But I think for 99% of the use cases this would just be 
> > a huge extra pain.
> 
> I have attached a patch to oscparse giving it an extra outlet telling
> the user how many of the atoms belong to the address component. Let me
> know what you think or if I should take a different tack.
> 
> I feel like there are definitely going to be use-cases we can't think of
> requiring this information for the user (as well of the one you have
> already thought of).
> 
> Another good flag for the future might be one that leaves the address
> component the way it looks when it comes in so that people don't have to
> set up multiple routes if they are just listening for a single thing or
> two, what do you think?
> 
> Cheers,
> 
> Chris.
> 
> -- 
> http://mccormick.cx/

> From 4bdcdea33c079f8b9ad5f15f4c665493c18f4b22 Mon Sep 17 00:00:00 2001
> From: Chris McCormick 
> Date: Fri, 22 Aug 2014 17:49:24 +0200
> Subject: [PATCH] Added outlet to oscparse to indicate how many of the symbols
>  belong to the address component of the incoming message.
> 
> ---
>  doc/5.reference/oscparse-help.pd |   32 +---
>  src/x_misc.c |   11 ---
>  2 files changed, 25 insertions(+), 18 deletions(-)
> 
> diff --git a/doc/5.reference/oscparse-help.pd 
> b/doc/5.reference/oscparse-help.pd
> index 42a4d3d..8b96aea 100644
> --- a/doc/5.reference/oscparse-help.pd
> +++ b/doc/5.reference/oscparse-help.pd
> @@ -1,10 +1,10 @@
> -#N canvas 5 71 705 636 12;
> +#N canvas 4 66 705 636 12;
>  #X obj 170 492 oscparse;
>  #X text 51 579 see also:;
>  #X obj 139 579 oscformat;
>  #X obj 223 579 netreceive;
>  #X text 434 582 updated for Pd version 0.46;
> -#X obj 170 515 print parse-output;
> +#X obj 170 539 print parse-output;
>  #X obj 313 579 list;
>  #X obj 418 437 netreceive -u -b;
>  #X msg 418 382 listen 5000;
> @@ -20,25 +20,27 @@
>  #X text 415 358 packets from network;
>  #X text 520 382 slisten on port 5000;
>  #X text 557 437 UDP packets \, binary output, f 13;
> -#X text 45 41 oscparse take incoming lists of numbers \, interpreting
> -them as the bytes in an OSC message. The output is a list containing
> -\, first \, the symbols making up the address of the OSC packet \,
> -and following that \, numbers and symbols as present in the OSC message.
> -OSC messages may contain 'float' \, 'int' \, 'string' \, or 'blob'
> -elements. Blobs are arrays of bytes (numbers between 0 and 255) and
> -are copied to the output preceded by the blob's byte count.;
>  #X text 80 11 oscparse - parse Open Sound Control (OSC) packets into
>  Pd messages, f 67;
> -#X text 44 187 OSC is a complicated networking protocol (FUDI \, as
> +#X obj 223 515 print address-count;
> +#X text 44 207 OSC is a complicated networking protocol (FUDI \, as
>  used in netsend/netreceive is simpler and better but less widely used).
>  oscparse and oscformat make no attempt to deal with timetags or aggregates
>  of packets \, nor with streaming OSC. Also \, no attempt is made here
> -to clearly distinguish between the OSC address (symbols) and the following
> -data \, nor between blobs and lists of numbers - it is assumed that
> -you know what types the message should contain. You can alternatively
> -use the OSC objects from mrpeach which have more features than these.
> -;
> +to between blobs and lists of numbers - it is assumed that you know
> +what types the message should contain. You can alternatively use the
> +OSC objects from mrpeach which have more features than these.;
> +#X text 45 41 oscparse take incoming lists of numbers \, interpreting
> +them as the bytes in an OSC message. The left outlet yeilds a list
> +containing \, first \, the symbols making up the address of the OSC
> +packet \, and following that \, numbers and symbols as present in the
> +OSC message. The right outlet yeilds the number of elements comprising

Re: [PD] max midi in devices

[Miller Puckette]

Or, as of 0.46, you can specify them by name (in case the numbers switch
around):

pd -midiaddindev device-name-1 -midiaddindev device-name-2 [...]

You can get the device names by looking at the MID dialog, or by starting

pd -listdev

Theoretically, you can add all the -midiaddindev (etc) garbage to Pd's
command line in the "startup" dialog -- I haven't tried that myself.

cheers
Miller

On Fri, Aug 22, 2014 at 08:44:34PM +0200, Nicolas Montgermont wrote:
> just do for midi input:
> pd -midiindev 1,2,3,4,5
> n
> 
> Le 22/08/2014 19:41, Alexandre Torres Porres a écrit :
> > hmm, I'm curious about that nicolas - one way or another I think it'd
> > be good to epxand this limit by default, I don't see what would be the
> > problem for that, right?
> >
> > don't know any midi merger software, any recommendations?
> >
> > cheers
> >
> >
> > 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont
> > mailto:nicolas_montgerm...@yahoo.fr>>:
> >
> > IIRC you can have more than 4 devices if you ask for them in
> > command line.
> > It's just the graphical interface that is limited to 4
> > n
> >
> >
> > Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> > > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres
> > mailto:por...@gmail.com>> wrote:
> > >> Hi, can we only have 4 multiple midi inputs in od?
> > >>
> > >> what is the workaround?
> > >>
> > > A midi merger (either hard or software)
> > >
> > >
> > >
> >
> > --
> > http://www.nimon.org
> >
> >
> > ___
> > Pd-list@lists.iem.at  mailing list
> > UNSUBSCRIBE and account-management ->
> > http://lists.puredata.info/listinfo/pd-list
> >
> >
> 
> -- 
> http://www.nimon.org
> 

> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

[PD] phase mod x freq mod equivalence

[Alexandre Torres Porres]

Hello, do any of you know how to convert a FM index to a phase mod
equivalent considering they both have the same carrier and modulator
frequency? Is it even possible?

thanks
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Nicolas Montgermont]

just do for midi input:
pd -midiindev 1,2,3,4,5
n

Le 22/08/2014 19:41, Alexandre Torres Porres a écrit :
> hmm, I'm curious about that nicolas - one way or another I think it'd
> be good to epxand this limit by default, I don't see what would be the
> problem for that, right?
>
> don't know any midi merger software, any recommendations?
>
> cheers
>
>
> 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont
> mailto:nicolas_montgerm...@yahoo.fr>>:
>
> IIRC you can have more than 4 devices if you ask for them in
> command line.
> It's just the graphical interface that is limited to 4
> n
>
>
> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres
> mailto:por...@gmail.com>> wrote:
> >> Hi, can we only have 4 multiple midi inputs in od?
> >>
> >> what is the workaround?
> >>
> > A midi merger (either hard or software)
> >
> >
> >
>
> --
> http://www.nimon.org
>
>
> ___
> Pd-list@lists.iem.at  mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>

-- 
http://www.nimon.org

___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Brian Fay]

I've also been wondering what the flags to control the number of MIDI
devices are. I'm using ALSA MIDI and I often have 3 MIDI devices connected,
but at least in pd-l2ork the default is 2 devices and I'm not sure how to
change it.


On Fri, Aug 22, 2014 at 1:42 PM, Alexandre Torres Porres 
wrote:

> moreover, aren't there any flags to call for multiple input/output devices
> automatically? I'm being able to call only one
>
> cheers
>
>
> 2014-08-22 14:41 GMT-03:00 Alexandre Torres Porres :
>
> hmm, I'm curious about that nicolas - one way or another I think it'd be
>> good to epxand this limit by default, I don't see what would be the problem
>> for that, right?
>>
>> don't know any midi merger software, any recommendations?
>>
>> cheers
>>
>>
>> 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont <
>> nicolas_montgerm...@yahoo.fr>:
>>
>> IIRC you can have more than 4 devices if you ask for them in command line.
>>> It's just the graphical interface that is limited to 4
>>> n
>>>
>>>
>>> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
>>> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
>>> por...@gmail.com> wrote:
>>> >> Hi, can we only have 4 multiple midi inputs in od?
>>> >>
>>> >> what is the workaround?
>>> >>
>>> > A midi merger (either hard or software)
>>> >
>>> >
>>> >
>>>
>>> --
>>> http://www.nimon.org
>>>
>>>
>>> ___
>>> Pd-list@lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>>> http://lists.puredata.info/listinfo/pd-list
>>>
>>
>>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Alexandre Torres Porres]

hmm, I'm curious about that nicolas - one way or another I think it'd be
good to epxand this limit by default, I don't see what would be the problem
for that, right?

don't know any midi merger software, any recommendations?

cheers


2014-08-22 13:09 GMT-03:00 Nicolas Montgermont :

> IIRC you can have more than 4 devices if you ask for them in command line.
> It's just the graphical interface that is limited to 4
> n
>
>
> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
> por...@gmail.com> wrote:
> >> Hi, can we only have 4 multiple midi inputs in od?
> >>
> >> what is the workaround?
> >>
> > A midi merger (either hard or software)
> >
> >
> >
>
> --
> http://www.nimon.org
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[Alexandre Torres Porres]

moreover, aren't there any flags to call for multiple input/output devices
automatically? I'm being able to call only one

cheers


2014-08-22 14:41 GMT-03:00 Alexandre Torres Porres :

> hmm, I'm curious about that nicolas - one way or another I think it'd be
> good to epxand this limit by default, I don't see what would be the problem
> for that, right?
>
> don't know any midi merger software, any recommendations?
>
> cheers
>
>
> 2014-08-22 13:09 GMT-03:00 Nicolas Montgermont <
> nicolas_montgerm...@yahoo.fr>:
>
> IIRC you can have more than 4 devices if you ask for them in command line.
>> It's just the graphical interface that is limited to 4
>> n
>>
>>
>> Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
>> > On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres <
>> por...@gmail.com> wrote:
>> >> Hi, can we only have 4 multiple midi inputs in od?
>> >>
>> >> what is the workaround?
>> >>
>> > A midi merger (either hard or software)
>> >
>> >
>> >
>>
>> --
>> http://www.nimon.org
>>
>>
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> http://lists.puredata.info/listinfo/pd-list
>>
>
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

[PD] [PD-announce] PdWeekend III Sep 19-21 (Fri-Sun) in San Diego and Los Angeles

[Joe Deken]

 ** PdWeekend III ** with Miller Puckette & Friends
Sep 19-21, 2014

  Friday/Saturday: San Diego California @ UCSD
  Sunday:  Culver City CA   @ CrashSpace LA


Additional details available/updated continually: http://newblankets.org

-
  Highlights
-

Miller Puckette -- *PdWeekend( Convener & M.C.

Katja Vetter
-- 2014 New Blankets *Artist in Transit* (Rotterdam)

Confirmed Participants (08/22/2014)
--
Joe Deken(San Diego, CA)
Colten Jackson   (Urbana, IL)
Theron Trowbridge(Los Angeles, CA)
Gi Vania (Carbondale, IL)
Sofy Yuditskaya  (New York, New York)
Tom Zicarelli(Maine woods, USA)
Chris Meng   (San Diego, CA)


   (Additional participants pending and invited. All welcome with RSVP
until space(s) are filled.)

Format: A. Roundtable presentations/discussions with "Miller & Friends"
 B. Demonstrations of participants' current
projects-in-progress
 C. Tutorial and hands-on sessions for experimental Pd work D.
Video/network international roundtable Saturday
(tentative)

-
--*-- --**-- --**-- --**-- --**-- --**-- --**--

We thank Chris McCormick, Jaime Oliver & Sofy Yuditskaya for
contributions toward travel and hospitality during these meetings
and in support of the New Blankets A-I-T follow-up events, in New
York City and Carbondale IL.

--*-- --**-- --**-- --**-- --**-- --**-- --**--







___
Pd-announce mailing list
pd-annou...@lists.iem.at
http://lists.puredata.info/listinfo/pd-announce
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] Ensuring the order of inlets/outlets in a subpatch

[Jaime E Oliver]

They are sorted based on location. My advice would be to pack all the arguments 
into a single message and then unpack them in the sub patch whenever possible.

best,

J


On Aug 22, 2014, at 12:36 PM, Bektur  wrote:

>> the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
>> the best practive is to allign inle (outlet) from left to right.
> 
> Thanks!
> 
> I’m a bit confused here though, does the order in which I created 
> inlets/outlets matter? Or are they sorted only by left/right location within 
> the subpatch?
> 
> Best regards,
> Bektur
> 
> On Aug 22, 2014, at 10:31 PM, Cyrille Henry  wrote:
> 
>> 
>> 
>> Le 22/08/2014 18:08, Bektur a écrit :
>>> Hello,
>>> 
>>> I have a question about inlet/outlet order. Let’s say I have a subpatch 
>>> which accepts and outputs 3 signal inlets/outlets:
>>> 
>>> in1~   in2~   in3~
>>>  \ |   /
>>> [   pd subpatch   ]
>>>  / |   \
>>> out1~  out2~  out~3
>>> 
>>> 
>>> How do I know which inlet within the subpatch would work with in1~, in2~ 
>>> and so on? What would be the best practice to ensure correct inlet/outlet 
>>> order?
>> the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
>> the best practive is to allign inle (outlet) from left to right.
>> 
>> cheers
>> c
>> 
>>> 
>>> Best regards,
>>> Bektur
>>> ___
>>> Pd-list@lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management -> 
>>> http://lists.puredata.info/listinfo/pd-list
>>> 
> 
> 
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] Ensuring the order of inlets/outlets in a subpatch

[Cyrille Henry]

Le 22/08/2014 18:36, Bektur a écrit :



the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
the best practive is to allign inle (outlet) from left to right.


Thanks!

I’m a bit confused here though, does the order in which I created 
inlets/outlets matter?

no.

Or are they sorted only by left/right location within the subpatch?
they are sort only by location

to experiment this : create a patch with a subpatch, connect subpatch inlet, 
and change geographical position of the inlet object.
you'll see connection in the main patch to change side...

cheers
c



Best regards,
Bektur

On Aug 22, 2014, at 10:31 PM, Cyrille Henry  wrote:




Le 22/08/2014 18:08, Bektur a écrit :

Hello,

I have a question about inlet/outlet order. Let’s say I have a subpatch which 
accepts and outputs 3 signal inlets/outlets:

in1~   in2~   in3~
   \ |   /
[   pd subpatch   ]
   / |   \
out1~  out2~  out~3


How do I know which inlet within the subpatch would work with in1~, in2~ and so 
on? What would be the best practice to ensure correct inlet/outlet order?

the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
the best practive is to allign inle (outlet) from left to right.

cheers
c



Best regards,
Bektur
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list






___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] Ensuring the order of inlets/outlets in a subpatch

[Bektur]

> the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
> the best practive is to allign inle (outlet) from left to right.

Thanks!

I’m a bit confused here though, does the order in which I created 
inlets/outlets matter? Or are they sorted only by left/right location within 
the subpatch?

Best regards,
Bektur

On Aug 22, 2014, at 10:31 PM, Cyrille Henry  wrote:

> 
> 
> Le 22/08/2014 18:08, Bektur a écrit :
>> Hello,
>> 
>> I have a question about inlet/outlet order. Let’s say I have a subpatch 
>> which accepts and outputs 3 signal inlets/outlets:
>> 
>> in1~   in2~   in3~
>>   \ |   /
>> [   pd subpatch   ]
>>   / |   \
>> out1~  out2~  out~3
>> 
>> 
>> How do I know which inlet within the subpatch would work with in1~, in2~ and 
>> so on? What would be the best practice to ensure correct inlet/outlet order?
> the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
> the best practive is to allign inle (outlet) from left to right.
> 
> cheers
> c
> 
>> 
>> Best regards,
>> Bektur
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> 
>> http://lists.puredata.info/listinfo/pd-list
>> 


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] Ensuring the order of inlets/outlets in a subpatch

[Cyrille Henry]

Le 22/08/2014 18:08, Bektur a écrit :

Hello,

I have a question about inlet/outlet order. Let’s say I have a subpatch which 
accepts and outputs 3 signal inlets/outlets:

in1~   in2~   in3~
   \ |   /
[   pd subpatch   ]
   / |   \
out1~  out2~  out~3


How do I know which inlet within the subpatch would work with in1~, in2~ and so 
on? What would be the best practice to ensure correct inlet/outlet order?

the leftmost inlet (outlet) is the 1, the right is 3, and the middle is 2.
the best practive is to allign inle (outlet) from left to right.

cheers
c



Best regards,
Bektur
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

[PD] Ensuring the order of inlets/outlets in a subpatch

[Bektur]

Hello,

I have a question about inlet/outlet order. Let’s say I have a subpatch which 
accepts and outputs 3 signal inlets/outlets:

in1~   in2~   in3~
  \ |   /
[   pd subpatch   ]
  / |   \
out1~  out2~  out~3


How do I know which inlet within the subpatch would work with in1~, in2~ and so 
on? What would be the best practice to ensure correct inlet/outlet order?

Best regards,
Bektur
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] [PD-announce] pd 0.46-0test1 released

[Chris McCormick]

Hi Miller,

Very cool, thanks for getting OSC objects into native Pd!

On 21/08/14 17:22, Miller Puckette wrote:
> Correct.  The bet I'm making is that nobody who's receiving OSC messages
> would have any doubt which is it.  YOu have to know what messages the source
> is sending you and what to do with them anyway.
>
> OTOH, if it does turn out that there's any real situation when such 
> disamiguation is needed (for instance, storing OSC streams for later 
> sequencing?) the objects could easily be altered to put in symbolic markers
> to separate everything - this would be in the form of a creation flag to
> make it an option.  But I think for 99% of the use cases this would just be 
> a huge extra pain.

I have attached a patch to oscparse giving it an extra outlet telling
the user how many of the atoms belong to the address component. Let me
know what you think or if I should take a different tack.

I feel like there are definitely going to be use-cases we can't think of
requiring this information for the user (as well of the one you have
already thought of).

Another good flag for the future might be one that leaves the address
component the way it looks when it comes in so that people don't have to
set up multiple routes if they are just listening for a single thing or
two, what do you think?

Cheers,

Chris.

-- 
http://mccormick.cx/
>From 4bdcdea33c079f8b9ad5f15f4c665493c18f4b22 Mon Sep 17 00:00:00 2001
From: Chris McCormick 
Date: Fri, 22 Aug 2014 17:49:24 +0200
Subject: [PATCH] Added outlet to oscparse to indicate how many of the symbols
 belong to the address component of the incoming message.

---
 doc/5.reference/oscparse-help.pd |   32 +---
 src/x_misc.c |   11 ---
 2 files changed, 25 insertions(+), 18 deletions(-)

diff --git a/doc/5.reference/oscparse-help.pd b/doc/5.reference/oscparse-help.pd
index 42a4d3d..8b96aea 100644
--- a/doc/5.reference/oscparse-help.pd
+++ b/doc/5.reference/oscparse-help.pd
@@ -1,10 +1,10 @@
-#N canvas 5 71 705 636 12;
+#N canvas 4 66 705 636 12;
 #X obj 170 492 oscparse;
 #X text 51 579 see also:;
 #X obj 139 579 oscformat;
 #X obj 223 579 netreceive;
 #X text 434 582 updated for Pd version 0.46;
-#X obj 170 515 print parse-output;
+#X obj 170 539 print parse-output;
 #X obj 313 579 list;
 #X obj 418 437 netreceive -u -b;
 #X msg 418 382 listen 5000;
@@ -20,25 +20,27 @@
 #X text 415 358 packets from network;
 #X text 520 382 slisten on port 5000;
 #X text 557 437 UDP packets \, binary output, f 13;
-#X text 45 41 oscparse take incoming lists of numbers \, interpreting
-them as the bytes in an OSC message. The output is a list containing
-\, first \, the symbols making up the address of the OSC packet \,
-and following that \, numbers and symbols as present in the OSC message.
-OSC messages may contain 'float' \, 'int' \, 'string' \, or 'blob'
-elements. Blobs are arrays of bytes (numbers between 0 and 255) and
-are copied to the output preceded by the blob's byte count.;
 #X text 80 11 oscparse - parse Open Sound Control (OSC) packets into
 Pd messages, f 67;
-#X text 44 187 OSC is a complicated networking protocol (FUDI \, as
+#X obj 223 515 print address-count;
+#X text 44 207 OSC is a complicated networking protocol (FUDI \, as
 used in netsend/netreceive is simpler and better but less widely used).
 oscparse and oscformat make no attempt to deal with timetags or aggregates
 of packets \, nor with streaming OSC. Also \, no attempt is made here
-to clearly distinguish between the OSC address (symbols) and the following
-data \, nor between blobs and lists of numbers - it is assumed that
-you know what types the message should contain. You can alternatively
-use the OSC objects from mrpeach which have more features than these.
-;
+to between blobs and lists of numbers - it is assumed that you know
+what types the message should contain. You can alternatively use the
+OSC objects from mrpeach which have more features than these.;
+#X text 45 41 oscparse take incoming lists of numbers \, interpreting
+them as the bytes in an OSC message. The left outlet yeilds a list
+containing \, first \, the symbols making up the address of the OSC
+packet \, and following that \, numbers and symbols as present in the
+OSC message. The right outlet yeilds the number of elements comprising
+the address portion of the incoming message. OSC messages may contain
+'float' \, 'int' \, 'string' \, or 'blob' elements. Blobs are arrays
+of bytes (numbers between 0 and 255) and are copied to the output preceded
+by the blob's byte count.;
 #X connect 0 0 5 0;
+#X connect 0 1 22 0;
 #X connect 7 0 0 0;
 #X connect 8 0 7 0;
 #X connect 9 0 7 0;
diff --git a/src/x_misc.c b/src/x_misc.c
index 6fb48aa..ba805cc 100644
--- a/src/x_misc.c
+++ b/src/x_misc.c
@@ -328,6 +328,8 @@ static t_class *oscparse_class;
 typedef struct _oscparse
 {
 t_object x_obj;
+t_outlet *x_out1;
+t_outlet *x_out2;
 } t_oscparse;
 
 #define ROUNDUPTO4(x)

Re: [PD] max midi in devices

[Nicolas Montgermont]

IIRC you can have more than 4 devices if you ask for them in command line.
It's just the graphical interface that is limited to 4
n


Le 22/08/2014 17:41, IOhannes m zmölnig a écrit :
> On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres  
> wrote:
>> Hi, can we only have 4 multiple midi inputs in od?
>>
>> what is the workaround?
>>
> A midi merger (either hard or software)
>
>
>

-- 
http://www.nimon.org


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] max midi in devices

[IOhannes m zmölnig]

On 22. August 2014 09:37:54 MESZ, Alexandre Torres Porres  
wrote:
>Hi, can we only have 4 multiple midi inputs in od?
>
>what is the workaround?
>

A midi merger (either hard or software)



-- 
mfh.ifs.dhr
IOhannes

sent from my pdp-12

___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

[PD] max midi in devices

[Alexandre Torres Porres]

Hi, can we only have 4 multiple midi inputs in od?

what is the workaround?

thanks
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list