From: Robert J. <rj...@sp...> - 2006-03-14 20:02:09
|
On Tuesday 14 March 2006 19.32, Hiram Abiff wrote: > Quoting Robert Jonsson <rj...@sp...>: > > Hi, > > > > Sorry for the delay, been away working. > > No prob. I've been working to, I know the feeling. > > > Wierd indeed! Hmm. If you start MusE in a terminal what does it say about > > timers? > > It used to complain that it couldn't find /dev/rtc so I recompiled my > kernel a few days ago to include support for the real-time-clock. > I always start it from a terminal window, here's the output I get now: > > no locale <muse_en_US>/</usr/local/share/muse/locale> > Trying RTC timer... > got timer = 12 > QObject::connect: No such signal PartCanvas::horizontalScroll(int) > QObject::connect: (sender name: 'unnamed') > QObject::connect: (receiver name: 'unnamed') > Arranger::configChanged - no bitmap! > Arranger::configChanged - no bitmap! Interesting, I don't get them with current REL07-cvs, possibly I did a fix I can't recall ;-P > > Despite these error messages (QObject and Arranger - GUI related?) I can > use muse's GUI and toolbars and everything normally. I don't know > what they reffer to. The missing locale doesn't seem to be affecting > muse's operation, either. The locale is no problem at all since then MusE falls back on the default language (which mostly is english ;). The other errors hopefully do not have any drawbacks either. > > > If there is a message about using AlsaTimer with 250hz it means that your > > system has a non-working rtc (or possibly not the right permissions) and > > the new alsatimer setting of 250 instead of 1000. > > A timer at only 250 hz might be low enough to account for the lack of > > accuracy, but still the tempo should be in the same ballpark. > > I remember setting the "timer frequency" to 1000Hz in kernel config > cause the info for this option stated that it was the recommended > choice for > desktop systems. > > > Is it in the transport panel that you set the tempo? > > Nope. I tried setting it from there but no matter to which value > I set it to the song is played at tempo 120. Hmm, the transport really should change the tempo when you edit it. If you change it in the master-track-list is the tempo in the transport updated? (If you start MusE with -M you should be able to observe the output of midi-data changing tempo) > When I set the DR-880 to use > MIDI mode for syncing it's Tempo display is showing 120 and cannot > be changed with the tempo button on the drum machine. Which is > normal, I guess since it is expecting to receive MIDI Tempo > messages from a MIDI Master device. Sounds right > I suspect that when I don't > use the transport panel to set the tempo, Muse takes the tempo > value from the DR-880, although it is the Master. While MusE is the master it should ignore whatever setting the DR-880 has. > > That is why I set up the initital tempo in the mastertrack, at which > point the DR-880 updates it's Tempo display to the value I set > in Muse's mastertrack. And then it starts switching values like I > described earlier. Ok. Unfortunately my synth does not display the received tempo.. > > > Are you using Jack or running MusE standalone? > > I am using jack and qjackctl to connect the DR-880, om, swami, specimen > (which I can't get to receive MIDI messages from Muse for some reason - I'm > still trying to set it up) > and a USB MIDI controller for playing all these. Ok. Nothing strange with that setup. > > >> I saw that Muse has a bunch of nifty MIDI options, like > >> MIDI Input Filter and MIDI Input Transform which I would like to dig > >> into and use. > > > > I don't use them myself, especially the transform I think is quite > > bugridden. > > drat. :) Indeed :-/ Regards, Robert > > > Quite understood, will need to think about this some more... > > > > Regards, > > Robert > > Well, thanx for all the help you provided so far and the time you > spent. I really appreciate this. > > Hiram. -- http://spamatica.se/musicsite/ |