Hi, I'm new on the list, and working with PD from a couple of years...
I'm on linux, Ubuntu Studio 9.10 and Fedora 10 / planet CCRMA
I have some troubles on latest vanilla version in repos (0.41):
All the midi-out objects do the same: no problem to set midi channel and CC or Note number, but for each value change, I get in jack: ALSA: connection graph change and the buttons in alsa-midi tab flash shortly... but 128 time if I push up a CC fader for example!
Some precisions: -no problem with midi-in objects -happens in my two systems (US and CCRMA) (don't know in earlier version, maybe I didn't noticed) -other alsa clients doesn't make any problem -happens when PD is connected or not in alsa-midi -but only when pd dsp is on -same with alsa audio drivers or FFADO (firewire) -other person seems to have the same problem:
http://puredata.hurleur.com/sujet-3479-midi-note-leads-connection-graph-chan...
Something else: PD seems to eat a lot of CPU when connected with jack/FFADO (~25%), and very few with jack/alsa, even with DSP off!?!
-I noticed some bugs (or will be enhancement?): when closing a patch (ctrl+w or mouse), dialog opens behind others (top of PD main)... When 10 (sub)patches are opened it's something boring... -when PD opens, it connects everything in jack, not just I/O, same in midi-connections... Maybe it's too much?
Thank's for your help cheers r
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Raphael Raccuia wrote:
Hi, I'm new on the list, and working with PD from a couple of years...
I'm on linux, Ubuntu Studio 9.10 and Fedora 10 / planet CCRMA
I have some troubles on latest vanilla version in repos (0.41):
All the midi-out objects do the same: no problem to set midi channel and CC or Note number, but for each value change, I get in jack: ALSA: connection graph change and the buttons in alsa-midi tab flash shortly... but 128 time if I push up a CC fader for example!
i noticed something like that very recently as well. i had no time to investigate what is going on here, but i seem to remember that i was able to make it without connection-graph-changes as well (read below)
Something else: PD seems to eat a lot of CPU when connected with
"something else" is bad for replying. better to send an email for each unrelated question you have...
-I noticed some bugs (or will be enhancement?): when closing a patch (ctrl+w or mouse), dialog opens behind others (top of PD main)... When 10 (sub)patches are opened it's something boring...
well known "feature" of Pd; should go away with the gui-rewrite currently undertaken.
-when PD opens, it connects everything in jack, not just I/O, same in midi-connections... Maybe it's too much?
that was definitely meant as a feature. since i noticed pretty soon that it can be avoiding as well (esp. when autoconnecting to the MIDI-thru), there is also a workaround: if you tell Pd to create to alsaseq ports (even if you only use one of them), it will not try to autoconnect.
this might also have been the "solution" to the connection-graph-change problem.
mfgasdr IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Raphael Raccuia wrote:
Hi, I'm new on the list, and working with PD from a couple of years...
I'm on linux, Ubuntu Studio 9.10 and Fedora 10 / planet CCRMA
I have some troubles on latest vanilla version in repos (0.41):
All the midi-out objects do the same: no problem to set midi channel and CC or Note number, but for each value change, I get in jack: ALSA: connection graph change and the buttons in alsa-midi tab flash shortly... but 128 time if I push up a CC fader for example!
rectification: problem occurs also when DSP is off...
i noticed something like that very recently as well. i had no time to investigate what is going on here, but i seem to remember that i was able to make it without connection-graph-changes as well (read below)
Something else: PD seems to eat a lot of CPU when connected with
"something else" is bad for replying. better to send an email for each unrelated question you have...
actually it's maybe related, but I forgot a part: with FFADO, I noticed a big MIDI latency (2-3 seconds. Sound tested with jdelay: without PD: ~10ms. 5ms more @ 96000/3 =15ms, seems pretty good). No problem with alsa!?! I thought maybe has to do with CPU usage...
-I noticed some bugs (or will be enhancement?): when closing a patch (ctrl+w or mouse), dialog opens behind others (top of PD main)... When 10 (sub)patches are opened it's something boring...
well known "feature" of Pd; should go away with the gui-rewrite currently undertaken.
good
-when PD opens, it connects everything in jack, not just I/O, same in midi-connections... Maybe it's too much?
that was definitely meant as a feature. since i noticed pretty soon that it can be avoiding as well (esp. when autoconnecting to the MIDI-thru)
yes, especially midi-thru. I've just read the thread about autoconnect...
, there is also a workaround: if you tell Pd to create to alsaseq ports (even if you only use one of them), it will not try to autoconnect.
How can I do that? searched on the web, but nothing...
this might also have been the "solution" to the connection-graph-change problem.
hope so thank's for your help r
mfgasdr IOhannes
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAksDr+8ACgkQkX2Xpv6ydvRwegCg2vkm/XnUW76i4SbWmmrUPXui vRkAoOMxIzztBIUSczYo0sJlNgmXtJYz =lJcZ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Raphael Raccuia wrote:
rectification: problem occurs also when DSP is off...
i noticed something like that very recently as well.
[ot] you have a weird mailer; indentation of quotes seems to be totally broken.
that was definitely meant as a feature. since i noticed pretty soon that it can be avoiding as well (esp. when autoconnecting to the MIDI-thru)
yes, especially midi-thru. I've just read the thread about autoconnect...
the problem is simple: the default for dummy users should make all their midi gear appear on [midiin] and friends. so we want some way of autoconnection. when doing autoconnection we have zero possibilities to find out which device is useful and which is not; MIDI-thru makes most problems and you cannot reliably detect it (the name is arbitrary; the port is arbitrary as well); i have no idea why MIDI-thru is still so omnipreset: with alsa-seq you don't need it at all.
, there is also a workaround: if you tell Pd to create to alsaseq ports (even if you only use one of them), it will not try to autoconnect.
How can I do that? searched on the web, but nothing...
try this:
$ pd -help 2>&1 | grep -i midi
and _later_ this: $ pd -alsamidi -mididev 1,1
fgsadr IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Raphael Raccuia wrote:
rectification: problem occurs also when DSP is off...
i noticed something like that very recently as well.
[ot] you have a weird mailer; indentation of quotes seems to be totally broken.
[ot] ??? it's thunderbird and seems to work fine
that was definitely meant as a feature. since i noticed pretty soon that it can be avoiding as well (esp. when autoconnecting to the MIDI-thru)
yes, especially midi-thru. I've just read the thread about autoconnect...
the problem is simple: the default for dummy users should make all their midi gear appear on [midiin] and friends. so we want some way of autoconnection. when doing autoconnection we have zero possibilities to find out which device is useful and which is not; MIDI-thru makes most problems and you cannot reliably detect it (the name is arbitrary; the port is arbitrary as well); i have no idea why MIDI-thru is still so omnipreset: with alsa-seq you don't need it at all.
ok
, there is also a workaround: if you tell Pd to create to alsaseq ports (even if you only use one of them), it will not try to autoconnect.
How can I do that? searched on the web, but nothing...
try this:
$ pd -help 2>&1 | grep -i midi
and _later_ this: $ pd -alsamidi -mididev 1,1
-alsamidi was already in my pd launcher, so I added -mididev 1,1 (and then in .pdsettings): works great, I have now two midi clients in alsa-tab (ch 1-16 & 17-32) and no graph connection change I still don't understand what 1,1 means. Thank's for your help! cheers r
fgsadr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAksFDYMACgkQkX2Xpv6ydvQP1wCfbIE9L6XKRCxgwsnH2QUCPR5O QkgAn1fa7b8y8wSJDl7kRLDnzgtdATjC =bL8c -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Raphael Raccuia wrote:
IOhannes m zmölnig a écrit : Raphael Raccuia wrote:
rectification: problem occurs also when DSP is off...
i noticed something like that very recently as well.
[ot] you have a weird mailer; indentation of quotes seems to be totally broken.
[ot] ??? it's thunderbird and seems to work fine
weird. then it's probably my mailer (thunderbird as well). quotes are displayed fine as long a i view your mail, but when i reply all the ">" levels are wrong. nevermind.
and _later_ this: $ pd -alsamidi -mididev 1,1
-alsamidi was already in my pd launcher, so I added -mididev 1,1 (and then in .pdsettings): works great, I have now two midi clients in alsa-tab (ch 1-16 & 17-32) and no graph connection change I still don't understand what 1,1 means.
$ pd -help 2>&1 | grep midi
- -midiindev ... -- midi in device list; e.g., "1,3" for first and third
- -midioutdev ... -- midi out device list, same format
- -mididev ... -- specify -midioutdev and -midiindev together
the commat notationn is Pd's way to handle multiple devices. "-mididev 2" means (on OSS) that you want to open midi-device #2 (/dev/midi1) "-mididev 1,3" means (on OSS) that you want to open 2 midi-devices (aka ports; so you have channels 1-32), the 1st one being /dev/midi0, the 2nd one /dev/midi2. on alsaseq there is no concept of a fixed midi-device like on OSS. therefore "-mididev 1" just means open one midi-port (channels 1-16). "-mididev 2" means literally the same (like in OSS you are asking for a single port; unlike in OSS you are not attaching Pd to an existing _other_ device, but rather are offering ports; in this context the value of the argument does not have much meaning) "-mididev 1,2" means that you want to open 2 ports; again the actual values "1" and "2" don't matter.
i hope this helps.
fgamsdr IOhannes
Thank's for your help! cheers r
fgsadr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
IOhannes m zmölnig -
Raphael Raccuia