Il 19/05/2015 20:09, Will Godfrey ha scritto: > On Tue, 19 May 2015 18:08:47 +0200 > Kristian Amlie <[email protected]> wrote: > >> On 19. mai 2015 16:10, Nicola Pandini wrote: >>> Hi, >>> this is my first post on this list: Yoshimi is an important tool for my >>> live setup. I play drums, and I use Yoshimi to create melodic lines on >>> the fly. (if you are interested, here is a small demo of my live set: >>> https://youtu.be/u8AQezPfPGU ) >>> >>> I have a little problem using Yoshimi: after Yoshimi starts, the first >>> note I send to Yoshimi produces lots of xruns for a couple of seconds. >>> After that, Yoshimi is playable without xruns for hours. >> Yes, I have noticed this too. First thing to check: Are you running the >> jack server with mlocking ("No memory lock" should be off in QJackCtl)? Hi Kristian, the jack server has "no memory lock" = off. The only checkbox set to on is "real time".
> > Hmmm, never had anything like this myself so let's see if we can narrow it > down. I would like to be able to duplicate it if I can. > > What latency are you working at? Hi Will, I'm working at 5.8ms of latency. My jackd settings are: /usr/bin/jackd -P70 -dalsa -dhw:3 -r44100 -p128 -n2 > Does the 'Messages' window in qjackctl say the xrun is coming from Yoshimi? > This is not conclusive, as jack tends to kick whatever app is last in the > chain. You can get even more confused if you start things up in a different > order as it's, first-up = first served. You can only have a *bit* of > confidence > if it's the same app that always seems to cause the problem regardless of the > installation order. When the xruns occurs, the logs are: JackEngine::XRun: client = Qtractor was not run: state = 1 JackAudioDriver::ProcessGraphAsyncMaster: Process error 18:37:00.424 XRUN callback (1). ... ... JackEngine::XRun: client = Qtractor was not run: state = 1 JackEngine::XRun: client = yoshimi was not run: state = 1 JackAudioDriver::ProcessGraphAsyncMaster: Process error Yoshimi is the last app that I start, I'll try to start it before Qtractor. > In 'Settings' what is OscilSize? Does it make a difference if you change it? > > Do you get the same problem if Yoshimi audio - jack are only connected to the > sound card? i.e. no other audio processing loading jack. > > Does it only happen with certain instrument patches? > If so are they mostly add, sub or pad engines? > > If you are running Wheezy I guess you must be compiling it yourself. Have you > seen the same problem with earlier versions? > > Are you running 32bit or 64? I believe core2 comes in both flavours. > If 64 bit, have you set the optimisations in ccmake . ? > > Would you like to try the current snapshot in the 'Code' tab of our > sourceforge page? It should be completely stable. > Today I haven't had much time to test other configurations, partially because the xruns happens only one time in a session: To reproduce it I need to reboot the OS, it doesn't happen if I only close and open Yoshimi and others software. So it takes more time to test it. I'm only sure that it doesn't depends on the instruments, so I'll try the current snapshot, changing the scenario as you suggest. I'll also test a scenario using the internal soundcard. Thanks for the advices! :-) p.s. I use a 32bit distro without optimizations in ccmake, where can I find documentation on how to optimize it? -- Nicola ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ yoshimi-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yoshimi-user
