From: Philippe M. <phi...@gm...> - 2010-05-15 10:53:55
|
Hi, I'm new to MusE, which I discovered only recently. I've been using Cubase on my old Atari for almost twenty years, but it's now time to move on (and replace my Atari which decided to retire), and it seems that MusE is what comes closest to Cubase in terms of workflow. I came across a weird behavior while playing around with looping, and before trying to look into it (I'm a former C++ programmer) I wanted to check on the list if this is may be known problem or if there is something I'm doing wrong. Create a new song, place the locators at 5 and 6 respectively, create a new Drum track, create a new Part (1 bar long), edit the part to add a snare on each beat. Close the edit window, check there is some drum instrument that can play the midi notes (I'm using QSynth), click on the loop button and press play... What I hear is something strange: the single repeating drum, and every 4 beats (when the position returns back to the left locator) the timing is slightly shorter between the drum hits, just as if there was some time skipped... It's a bit awkward to explain, but it takes hardly a minute to try. It's so "basic" I somewhat hope I've got something wrong, but I can't figure out what. Not a real showstopper actually, simply annoying. Any ideas on this? Thank you, and keep up the good work with what appears so far as a very good program. Best regards, Philippe |
From: Robert J. <spa...@gm...> - 2010-05-16 22:13:04
|
Hi Philippe, 2010/5/15 Philippe Macaire <phi...@gm...>: > Hi, I'm new to MusE, which I discovered only recently. I've been using > Cubase on my old Atari for almost twenty years, but it's now time to move on > (and replace my Atari which decided to retire), and it seems that MusE is > what comes closest to Cubase in terms of workflow. Yes quite a lot of inspiration comes from cubase, but we improved it ;-P > I came across a weird behavior while playing around with looping, and before > trying to look into it (I'm a former C++ programmer) I wanted to check on > the list if this is may be known problem or if there is something I'm doing > wrong. > > Create a new song, place the locators at 5 and 6 respectively, create a new > Drum track, create a new Part (1 bar long), edit the part to add a snare on > each beat. Close the edit window, check there is some drum instrument that > can play the midi notes (I'm using QSynth), click on the loop button and > press play... > > What I hear is something strange: the single repeating drum, and every 4 > beats (when the position returns back to the left locator) the timing is > slightly shorter between the drum hits, just as if there was some time > skipped... It's a bit awkward to explain, but it takes hardly a minute to > try. My laptop seems borked so I can't test at the moment. Not sure what can be the problem. I use this procedure all the time so it should work just fine. Unless it is very subtle to the point that I would not hear... Here's an example of the same type of usage from a tutorial video I made: http://www.youtube.com/watch?v=GOGKuyvwDfM > > It's so "basic" I somewhat hope I've got something wrong, but I can't figure > out what. Not a real showstopper actually, simply annoying. Not sure what to do for fault analysis... Are there any errors when muse starts? Could you record it and stick the recording somewhere so we could listen to it? > > Any ideas on this? > > Thank you, and keep up the good work with what appears so far as a very good > program. Thanks :) Regards, Robert |
From: Philippe M. <phi...@gm...> - 2010-05-18 07:03:34
|
Hi Robert, thanks for your reply. On Mon, May 17, 2010 at 12:12 AM, Robert Jonsson <spa...@gm...>wrote: > My laptop seems borked so I can't test at the moment. Not sure what > can be the problem. I use this procedure all the time so it should > work just fine. > Unless it is very subtle to the point that I would not hear... > > Here's an example of the same type of usage from a tutorial video I made: > http://www.youtube.com/watch?v=GOGKuyvwDfM > > Yeah, on this tutorial the loop works just fine... > Not sure what to do for fault analysis... > Are there any errors when muse starts? > Sorry, I forgot to check... it's on my linux box at home. Now I've just checked on a Virtual Machine at work (not the best to play with audio...), but I could not reproduce the problem, and looping sounds fine. I'm getting to think that there is a specific issue on my box... Not Muse's fault at least. I'll check tonight if I can and will get back to the list. Thanks for your feedback. Philippe |
From: Philippe M. <phi...@gm...> - 2010-05-20 08:45:50
|
Hi Robert, On Tue, May 18, 2010 at 9:03 AM, Philippe Macaire < phi...@gm...> wrote: > On Mon, May 17, 2010 at 12:12 AM, Robert Jonsson <spa...@gm...>wrote: > > Are there any errors when muse starts? >> > > Sorry, I forgot to check... it's on my linux box at home. > > Now I've just checked on a Virtual Machine at work (not the best to play > with audio...), but I could not reproduce the problem, and looping sounds > fine. I'm getting to think that there is a specific issue on my box... Not > Muse's fault at least. I'll check tonight if I can and will get back to the > list. > > Here are the results of my check. I figured out that my Launcher had the -a option (MIDI-only mode) passed as argument. This is the resulting log: fatal error: open /dev/rtc failed: Permission denied hint: check if 'rtc' kernel module is loaded, or used by something else AlsaTimer::initTimer(): best available ALSA timer: system timer Finding best alsa timer for dummy driver: AlsaTimer::initTimer(): best available ALSA timer: system timer AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer (max is 1000) freq stays at 1000 Hz Denormal protection enabled. Muse: __i386__ or __x86_64__ defined. Using optimized float buffer copying (asm movsl). Muse: using unoptimized non-SSE dsp routines no locale <muse_en_US.UTF-8>/</usr/local/share/muse/locale> Trying RTC timer... Trying ALSA timer... got timer = 48 starting with selected song (null) Setting project path to /home/phil/Desktop audio dummy thread _NOT_ running SCHED_FIFO looping waiting for sequencer thread to start midiSeq started, is it running? 1 Muse:checkAudioDevice: no audioDevice I then tried to remove the -a option, and things started to work out as expected. Here's the log: Denormal protection enabled. Muse: __i386__ or __x86_64__ defined. Using optimized float buffer copying (asm movsl). Muse: using unoptimized non-SSE dsp routines SSE2 detected fatal error: open /dev/rtc failed: Permission denied hint: check if 'rtc' kernel module is loaded, or used by something else AlsaTimer::initTimer(): best available ALSA timer: system timer AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer (max is 1000) freq stays at 1000 Hz no locale <muse_en_US.UTF-8>/</usr/local/share/muse/locale> Trying RTC timer... Trying ALSA timer... got timer = 50 starting with selected song (null) Setting project path to /home/phil/Desktop JackAudioDevice::setMaster cannot set master because useJackTransport is false JackAudioDevice::setMaster cannot set master because useJackTransport is false JackAudioDevice::dummySync Sync timeout - audio not ready! looping waiting for sequencer thread to start midiSeq started, is it running? 1 Muse:checkAudioDevice: no audioDevice In both cases I can see some errors, but I don't know if they are significant. My guess is that I now should do without with the -a option definitely... Does it makes sense? I'm using only external softsynths (QSynth) on UbuntuStudio 9.10. Thanks for the time, Philippe |
From: Robert J. <spa...@gm...> - 2010-05-20 10:15:04
|
Hi Philippe, 2010/5/20 Philippe Macaire <phi...@gm...>: > Hi Robert, > >> > Here are the results of my check. I figured out that my Launcher had the -a > option (MIDI-only mode) passed as argument. This is the resulting log: > <...> > audio dummy thread _NOT_ running SCHED_FIFO > looping waiting for sequencer thread to start > midiSeq started, is it running? 1 > Muse:checkAudioDevice: no audioDevice > > I then tried to remove the -a option, and things started to work out as > expected. Here's the log: > > Denormal protection enabled. > Muse: __i386__ or __x86_64__ defined. Using optimized float buffer copying > (asm movsl). > Muse: using unoptimized non-SSE dsp routines > SSE2 detected > fatal error: open /dev/rtc failed: Permission denied > hint: check if 'rtc' kernel module is loaded, or used by something else > AlsaTimer::initTimer(): best available ALSA timer: system timer > AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer (max > is 1000) > freq stays at 1000 Hz > no locale <muse_en_US.UTF-8>/</usr/local/share/muse/locale> > Trying RTC timer... > Trying ALSA timer... > got timer = 50 > starting with selected song (null) > Setting project path to /home/phil/Desktop > JackAudioDevice::setMaster cannot set master because useJackTransport is > false > JackAudioDevice::setMaster cannot set master because useJackTransport is > false > JackAudioDevice::dummySync Sync timeout - audio not ready! > looping waiting for sequencer thread to start > midiSeq started, is it running? 1 > Muse:checkAudioDevice: no audioDevice > > > In both cases I can see some errors, but I don't know if they are > significant. There are some mysterious errors in the last, no audioDevice? dunno why. Though since you only use midi it should be fine. QSynth is a fluidsynth frontend, MusE has a fluidsynth plugin internally also with the same name. I think QSynth implements more features but generally the internal one may be easier to use (configuration would be stored together with the song) > My guess is that I now should do without with the -a option definitely... > Does it makes sense? I'm using only external softsynths (QSynth) on Running in sequencer only mode doesn't really improve it's sequencing abilities so you will be fine in standard mode. Especially if you already use Jack for other things. Regards, Robert > UbuntuStudio 9.10. > > Thanks for the time, > Philippe > |
From: Robert J. <spa...@gm...> - 2010-05-20 10:17:08
|
Hello again, >> audio dummy thread _NOT_ running SCHED_FIFO >> looping waiting for sequencer thread to start Forgot to comment. This may be the reason the timing was off. the audio thread should have gotten realtime (SCHED_FIFO) capabilities. Not sure but I think Tim did some improvements to -a mode in svn. Regards, Robert |
From: Tim E. R. <ter...@ro...> - 2010-05-20 21:23:35
|
On May 20, 2010 06:14:56 am Robert Jonsson wrote: > Hi Philippe, > > 2010/5/20 Philippe Macaire <phi...@gm...>: > > Hi Robert, > > > > > > Here are the results of my check. I figured out that my Launcher had the > > -a option (MIDI-only mode) passed as argument. This is the resulting log: > > <...> > > > audio dummy thread _NOT_ running SCHED_FIFO > > looping waiting for sequencer thread to start > > midiSeq started, is it running? 1 > > Muse:checkAudioDevice: no audioDevice > > > > I then tried to remove the -a option, and things started to work out as > > expected. Here's the log: > > > > Denormal protection enabled. > > Muse: __i386__ or __x86_64__ defined. Using optimized float buffer > > copying (asm movsl). > > Muse: using unoptimized non-SSE dsp routines > > SSE2 detected > > fatal error: open /dev/rtc failed: Permission denied > > hint: check if 'rtc' kernel module is loaded, or used by something else > > AlsaTimer::initTimer(): best available ALSA timer: system timer > > AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer > > (max is 1000) > > freq stays at 1000 Hz > > no locale <muse_en_US.UTF-8>/</usr/local/share/muse/locale> > > Trying RTC timer... > > Trying ALSA timer... > > got timer = 50 > > starting with selected song (null) > > Setting project path to /home/phil/Desktop > > JackAudioDevice::setMaster cannot set master because useJackTransport is > > false > > JackAudioDevice::setMaster cannot set master because useJackTransport is > > false > > JackAudioDevice::dummySync Sync timeout - audio not ready! > > looping waiting for sequencer thread to start > > midiSeq started, is it running? 1 > > Muse:checkAudioDevice: no audioDevice > > > > > > In both cases I can see some errors, but I don't know if they are > > significant. > > There are some mysterious errors in the last, no audioDevice? dunno why. Don't worry unless you see many of those and it causes MusE to fail. The message pops up sometimes while a thread is waiting etc. Usually a fraction of a second later it goes away. It's just a benign message in those cases, more like just a debug message letting us know that the caller is dutifully waiting for the audio to come online. Tim. > Though since you only use midi it should be fine. > > QSynth is a fluidsynth frontend, MusE has a fluidsynth plugin > internally also with the same name. I think QSynth implements more > features but generally the internal one may be easier to use > (configuration would be stored together with the song) > > > My guess is that I now should do without with the -a option definitely... > > Does it makes sense? I'm using only external softsynths (QSynth) on > > Running in sequencer only mode doesn't really improve it's sequencing > abilities so you will be fine in standard mode. > Especially if you already use Jack for other things. > > Regards, > Robert > > > UbuntuStudio 9.10. > > > > Thanks for the time, > > Philippe > > --------------------------------------------------------------------------- >--- > > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |