I'm at work, once home I'll send it.

Thank you very much Saturno.

Are you working on PC, Mac or Linux?
What version of PD do you use?

Thanks again.

Latest version of PD-Extended on Os X
Windows does not have the sysexin object.

I have not tested it in Linux.

@saturno said:

I'm at work, once home I'll send it.

Nice, cheers.

Maybe you can help me with this issue:

I'm going to use Sysexin in order to retrieve sysex messages from ProTools. For example the track name in order to pass it to my own midi controller in PureData.

What do you think is the best way to do it?
What do you think is the best way to convert the sysex message to "text"?

Your suggestions will be welcome. Thanks in advance.

Here it is.

Open up microKorg/program-help

http://www.pdpatchrepo.info/hurleur/microKorg.zip

I can't open the zip folder. Error message.

Just downloaded it and opened it in a different computer just fine.

You are right Saturno, sorry.

Do you have any ideas about my questions in previous post?

Thanks a lot!

Having never used ProTools I'm not sure.

One think I found was that I had to use the micro korg with it's midi clock turned off or else sysexin would constantly churn out values.

As far as interpreting the sysex messages I also have no idea. I didn't have to for my patch, just save and load.

Hi,

im having some problems with audio in Pd. Im running extended 0.42.5 in Linux and midi is not working. The midi out test in the "midi and audio test" does not make any sound. This errors ocurrs in the inicialization:

audio I/O error history:
seconds ago error type
2.90 A/D/A sync
2.90 A/D/A sync
2.96 A/D/A sync
2.96 A/D/A sync
2.96 A/D/A sync
2.96 A/D/A sync
2.96 DAC blocked
2.96 A/D/A sync
2.96 unknown
2.96 unknown

does someone knows what is going wrong?

thanks in advance,

Conclusion, it's very easy to emit sysex from pure data:

Send a list into the left inlet of a midiout,
starting with 240 and ending with 247,
with the values you want in between, in decimal.