hi all
first post here.
just downloaded pure data last night.
great stuff 
so far i haven't been able to find an answer to whether or not sysex data can be generated and output via midi.
any insight would be really appreciated.
best
jeff
-
Sysex
-
its working here gnu/linux with jack alsamidi.
[midiin] [midiout]
comma separated integer messages.
eg [240, 34, 26, 43, 253, 247(
on windows youll get messages the some midiobjects are not working.
But do your own testing some seems to work anyway. -
ah yeah thanks, i did manage to get it working too.
-
which version do you guys use where [midiout] does work?
i'm on 0.40.3-extended and no output
-
On winxp midi seems difficult under 0.40.3 extended. Yesterday i've downloaded 0.41.4 extended RC3 and midi works a charm now, so maybe you could try that as well.
|] [] |.| ][|-| -- http://soundcloud.com/domxh
-
Thanks domien! I have actually grabbed 0.42-5 and [midiout] seems to work now... well something is still wrong with my sysex, but there is output indeed
)) -
Just to put it out there. I got it to work on PD Extended 0.41.4 on OS X with a microKorg. The trick is to use sysex for input and midout for output, ignore the second inlet, and make sure to use a 1ms delay between bytes (messages) when writing out.
-
thank you! i've been trying for AGES to get Pd to communicate via sysex with my korg microkontrol and didn't realise sysexin / midiout would work.
One problem I encountered, however, was that not every piece of software and hardware recognises the decimal-formatted sysex output from Pd. Midi Monitor recognises it, for example, but Sysex Librarian doesn't, and neither does my microKontrol.
As a workaround, I'm routing the sysex output from Pd into a Max patch which contains a midiin object connected directly to a midiout: although the sysex data isn't being changed in any way, when it's sent out by Max it's recognised by all my software and hardware (including the microkontrol). It's a bit of a hack, but is relatively straightforward and means that i now have full in/out sysex functionality from Pd.
-
Getting the sysexin to work was quite easy, the hard part was writing the data out. At first it just wouldn't work at all, but once I added a 1ms delay between every byte sent to midout it worked.
-
Saturno:
Can you send an example?
It will be very helpful for me.
Thanks in advance.
-
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.
-
-
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.
-
-
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 unknowndoes someone knows what is going wrong?
thanks in advance,
