On Tue, 21 Oct 2014 19:52:21 +0200 Ralf Mardorf <ralf.mardorf(a)rocketmail.com> wrote: You're both quite right, but I was trying to keep the survey as simple as possible but covering most options. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

On Wed, 2014-10-22 at 17:43 +0100, Will J Godfrey wrote: That's the surprise for me, I expected around 90%. That isn't a big surprise, just a little surprise, e.g. Qtractor only provides ALSA MIDI, so bridging is common, there are several reasons to use either. There are a a few reasons to just use Jack or ALSA, when people simply use just some Linux MIDI software and not much Linux MIDI software. A little bit surprising is that there are more Jack, than ALSA MIDI users, perhaps MIDI bridging is the way most of us go, for what reason ever. I e.g. often use Jack 2's alsarawmidi to decrease MIDI jitter when using external MIDI devices, so I tend to bridge.

On Wed, 22 Oct 2014 19:19:38 +0200 Ralf Mardorf <ralf.mardorf(a)rocketmail.com> wrote: No, 16% either, 7 % alsa -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

Great Will, I'm sure this information is valuable in many ways, at least to take the pulse of the situation nowadays. 2014-10-25 17:55 GMT+02:00 Will Godfrey <willgodfrey(a)musically.me.uk>uk>: -- C. sanchiavedraZ: * NEW / NUEVO: www.sanchiavedraZ.com * Musix GNU+Linux: www.musix.es

On Sat, 25 Oct 2014 18:26:10 +0200 Robin Gareus <robin(a)gareus.org> wrote: I actually wanted to let it run for *much* longer, but survey monkey only registers the first 100 responses. After that you have to pay 15uk pence per response, and I've a suspicion that they mean per question too, so that makes 30uk pence. I'm not a skinflint, but I don't think this kind of simple assessment warrants the expense. -- It wasn't me! (Well actually, it probably was) ... the hard part is not dodging what life throws at you, but trying to catch the good bits.

On Sat, 2014-10-25 at 11:44 -0700, Len Ovens wrote: It would be nice to get a more representative poll. I guess we are a few more than just 100 people and some perhaps less often retrieve mails, so the poll should continue for longer than a month.

On Sat, 25 Oct 2014, Will Godfrey wrote: I wonder how many choices are based on the SW in use rather than choice of audio driver. Some one using an application like audacity with a broken jack implementation or one of the midi apps that only does ALSA midi, have less choices. Someone developing embedded HW has to develop ALSA drivers first then get jack to work on that platform as well. There are lots of jack client walk throughs, but no guide at all on writing jack backends that might allow such people to go direct to jack. The info is probably right in front of my face but not in a way I see it... In any case I think any backend is either jack1 or jack2. a2jmidi (at least with jack2) does not clearly make the HW midi ports look like they belong in jack midi, giving the user the idea that alsa midi makes more sense. While it is true that HW midi ports are becoming rare, USB midi still shows up like hw ports. Anything using long sysex midi uses alsa midi. SO this choice is made by jack itself. (I know work is being done to allow jack to do non-rt midi transfers, but it will take some time for developers to make use of it) The midi jack/alsa thing is getting more complex with applications choosing one or the other and forcing the user to use both. a2jmidi is really a way of using both, but allowing the connections to be made in one place. These are meant to observations, I am personally glad to have all these things working as well as they do now. But it is obvious that people's choices of audio/midi backends is based on more than dis/likes. That would be interesting. -- Len Ovens www.ovenwerks.net