From: Brian K. <bak...@gm...> - 2010-06-07 01:29:13
|
On Mon, Jun 7, 2010 at 12:50 PM, cal <ca...@gr...> wrote: > On 07/06/10 10:39, Brian King wrote: > >> >> [ ... ] >> >> Of course when testing an app such as this I don't burden the system >> with unnecessary load so I run yoshimi as only app connected to jack. >> >> I definitely feels like a problem shared with rosegarden and the >> like....i used to have problems with guitarix but the dev's there are on >> to it.....not saying your not :-) >> > > If I knew what to go after, I would. Since I'm not seeing same the > behaviour > you are, it's kinda hard for me to "fix" it. For this kind of problem, I'm > totally dependent on feedback from those suffering the problem for me to > have > any chance of improving things. > > Are there any log files or app dumps that I could collect to help you out with what is happening when yoshimi disconnects or is disconnected from jack? > >> i wonder what's the story around why so many jack apps use alsa midi >> instead of jack midi and what bugs are lurking in that midi seq interface? >> > > There's still quite a lot of apps that just don't have jack midi > implemented. > I don't believe that's because of any issues with jack midi, more likely > just > the inherent inertia - myapp's alsa midi interface works fine, why should I > go > to the trouble of jack midi? > > No chance of an alsa midi interface with yoshimi to test if that works better here? -- ------------------------------------------------------------------------------------------- Brian King bak...@gm... Happily using Linux, Drinking fine beer, Listening to great NZ music...Kiwi 102.2FM/95BFM and heaps of other great music on http://www.jamendo.com. Helensville, New Zealand. ------------------------------------------------------------------------------------------- |