I was just thinking, currently Pd can get a list of the active MIDI devices, on Windows and Mac OS X at least. Would there be any problem if Pd just automatically added those and enabled them if there weren't any preferences saved?
So if someone has setup their MIDI devices, then they would not be touched. But if the MIDI device setup was just device, it would just add the MIDI devices found by sys_get_midi_devs() in sequential order.
.hc
Programs should be written for people to read, and only incidentally for machines to execute.
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
by enumeration? if you don't use a fixed setup all the time, the enumeration on windows changes quite randomly.. i had problems before when windows changed the order of my internal soundcard and my motu and Pd tried to start the internal card with asio, which it doesn't support, which caused pd to crash at startup..
as for your idea to automatically open a midi devices, guess it can be useful for people who have only one device, but as son as you connect an external midi device, most of the time you have also an internal midi playback on the soundcard and you don't know which one is first in windows' enumeration..
all the best,
Kristof
info@kristoflauwers.domainepublic.net
http://soundcloud.com/kristof-lauwers http://kristoflauwers.domainepublic.net ____________________________________
At 04:03 2012-03-23, Hans-Christoph Steiner wrote:
I was just thinking, currently Pd can get a list of the active MIDI devices, on Windows and Mac OS X at least. Would there be any problem if Pd just automatically added those and enabled them if there weren't any preferences saved?
So if someone has setup their MIDI devices, then they would not be touched. But if the MIDI device setup was just device, it would just add the MIDI devices found by sys_get_midi_devs() in sequential order.
.hc
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
The MIDI Settings Dialog needs a big overhaul, that's for sure. I'm happy to help anyone if they take that on. Saving by device names is a great idea, for example. I'll keep that in mind with the coding I'm going to do, and if its obvious, I'll add it.
This automatic stuff won't replace complex setups, it'll just make simple setups really easy and leave the prefs stuff alone for complex setups. I just want to make sure I'm not going to make things hardware for the non-simple setups.
.hc
On Mar 23, 2012, at 9:29 AM, kristof lauwers wrote:
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
in the midi settings dialog (on windows), you can only select two midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
would it be possible to save the setup by device names rather than by enumeration? if you don't use a fixed setup all the time, the enumeration on windows changes quite randomly.. i had problems before when windows changed the order of my internal soundcard and my motu and Pd tried to start the internal card with asio, which it doesn't support, which caused pd to crash at startup..
as for your idea to automatically open a midi devices, guess it can be useful for people who have only one device, but as son as you connect an external midi device, most of the time you have also an internal midi playback on the soundcard and you don't know which one is first in windows' enumeration..
all the best,
Kristof
info@kristoflauwers.domainepublic.net
http://soundcloud.com/kristof-lauwers http://kristoflauwers.domainepublic.net ____________________________________
At 04:03 2012-03-23, Hans-Christoph Steiner wrote:
I was just thinking, currently Pd can get a list of the active MIDI devices, on Windows and Mac OS X at least. Would there be any problem if Pd just automatically added those and enabled them if there weren't any preferences saved?
So if someone has setup their MIDI devices, then they would not be touched. But if the MIDI device setup was just device, it would just add the MIDI devices found by sys_get_midi_devs() in sequential order.
.hc
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
The arc of history bends towards justice. - Dr. Martin Luther King, Jr.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-23 14:29, kristof lauwers wrote:
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
- in the midi settings dialog (on windows), you can only select two
midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
why 4? (and not, say, 37?)
as for your idea to automatically open a midi devices, guess it can be useful for people who have only one device, but as son as you connect an external midi device, most of the time you have also an internal midi playback on the soundcard and you don't know which one is first in windows' enumeration..
i'm also rather sceptical about auto-connection, esp. when based on numerical IDs. e.g. i don't see a big advantage to autoconnect to a MIDI-thru device, that will loopback all the data i just sent.
fgmasr IOhannes
At 08:45 2012-03-26, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-23 14:29, kristof lauwers wrote:
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
- in the midi settings dialog (on windows), you can only select two
midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
why 4? (and not, say, 37?)
well, 4 is as much as i need. ;) unlimited would be ideal of course..
greetings,
kristof
info@kristoflauwers.domainepublic.net
http://soundcloud.com/kristof-lauwers http://kristoflauwers.domainepublic.net ____________________________________
On Mar 26, 2012, at 2:45 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-23 14:29, kristof lauwers wrote:
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
- in the midi settings dialog (on windows), you can only select two
midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
why 4? (and not, say, 37?)
as for your idea to automatically open a midi devices, guess it can be useful for people who have only one device, but as son as you connect an external midi device, most of the time you have also an internal midi playback on the soundcard and you don't know which one is first in windows' enumeration..
i'm also rather sceptical about auto-connection, esp. when based on numerical IDs. e.g. i don't see a big advantage to autoconnect to a MIDI-thru device, that will loopback all the data i just sent.
I think that having something setup by default is more helpful than nothing, as long as it doesn't cause problems. Then for people who want to have it setup differently, they can do what they've always done.
.hc
"[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-26 16:09, Hans-Christoph Steiner wrote:
i'm also rather sceptical about auto-connection, esp. when based on numerical IDs. e.g. i don't see a big advantage to autoconnect to a MIDI-thru device, that will loopback all the data i just sent.
I think that having something setup by default is more helpful than nothing, as long as it doesn't cause problems. Then for people who want to have it setup differently, they can do what they've always done.
sure. only...i was referring to real problems in existing autoconnectors.
fgmasdr IOhannes
On 2012-03-26 10:09, Hans-Christoph Steiner wrote:
On Mar 26, 2012, at 2:45 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-23 14:29, kristof lauwers wrote:
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
- in the midi settings dialog (on windows), you can only select two
midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
why 4? (and not, say, 37?)
as for your idea to automatically open a midi devices, guess it can be useful for people who have only one device, but as son as you connect an external midi device, most of the time you have also an internal midi playback on the soundcard and you don't know which one is first in windows' enumeration..
i'm also rather sceptical about auto-connection, esp. when based on numerical IDs. e.g. i don't see a big advantage to autoconnect to a MIDI-thru device, that will loopback all the data i just sent.
I think that having something setup by default is more helpful than nothing, as long as it doesn't cause problems. Then for people who want to have it setup differently, they can do what they've always done.
What if I'm also using jack's patchbay to set up a default connection? Is it possible to have Pd set up a default connection only if no connection already exists?
Martin
On Mar 26, 2012, at 11:02 AM, Martin Peach wrote:
On 2012-03-26 10:09, Hans-Christoph Steiner wrote:
On Mar 26, 2012, at 2:45 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-23 14:29, kristof lauwers wrote:
Hi,
If you are going to make changes to the midi device setup, i have two other suggestions:
- in the midi settings dialog (on windows), you can only select two
midi output devices. the only way i found to use more then 2 devices is by adding them manually in the registry. it would be nice if you could add at least 4 devices from the dialog..
why 4? (and not, say, 37?)
as for your idea to automatically open a midi devices, guess it can be useful for people who have only one device, but as son as you connect an external midi device, most of the time you have also an internal midi playback on the soundcard and you don't know which one is first in windows' enumeration..
i'm also rather sceptical about auto-connection, esp. when based on numerical IDs. e.g. i don't see a big advantage to autoconnect to a MIDI-thru device, that will loopback all the data i just sent.
I think that having something setup by default is more helpful than nothing, as long as it doesn't cause problems. Then for people who want to have it setup differently, they can do what they've always done.
What if I'm also using jack's patchbay to set up a default connection? Is it possible to have Pd set up a default connection only if no connection already exists?
The logic I'm thinking is pretty straightforward: if there are no MIDI settings in the preferences, then automatically assign the ones it finds. The one thing this would prevent is having the user have MIDI on but force no assigned devices. That seems like a worthwhile trade-off for having newbies be able to use MIDI without doing anything but send MIDI data to a MIDI object.
.hc
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." --Bjarne Stroustrup (creator of C++)