On September 19, 2012 10:17:53 AM Robert Jonsson wrote: 2012/9/19 Robert Jonsson <[email protected]>
2012/9/19 Tim E. Real <[email protected]> On September 19, 2012 12:55:26 AM Tim E. Real wrote: > Ya know, there *is* another old timer which MusE supports: > Ye olde RTC Clock. > > When you start MusE (possibly with debug messages), do you > see any messages about the RTC clock? Permission denied? > > I haven't gotten the RTC clock to work for a long time but I think > Robert wrote some info about poking the /proc tree to make it work. > Try the README. > Rats! > First of all there's outdated info in the README. > > Where it says: > > - make sure MusE can set the rtc clock: > echo 8192 > /proc/sys/dev/rtc/max-user-freq > inspect with: > cat /proc/sys/dev/rtc/max-user-freq > > That should read /sys/class/rtc/rtc0/max_user_freq. > At least here on *buntu. > > Can someone change it if I don't get to it? > > > > I'll give it a shot tonight if time permits... Thing is I had done improved > instructions for this on the webpage but it seems it got lost with the > unfortunate rollback of the server. I forgot to put it in the README, in > which case all would have been well. > > > Ah, I had rewritten it already! > http://muse-sequencer.org/index.php/Faq#Proper_timing_source > It could use another overhaul though, I'll put it in the README too. > > Regards, > Robert > Darn. I tried all the instructions including sudo echo 2048 > /proc/sys/dev/hpet/max-user-freq which is also present here. No luck. Permission denied even as root. I think something has grabbed the RTC and won't give it up. I tired killing PA but no luck. BTW Jack isn't even running. --- Also, Robert: On the page linked above there's a section: "Wave - output ports are still visible in qjackctl although deleted in MusE This is because of the undo function which just hides the track from the arranger. This could not have been done differently because then you would lose all your routings if you use "undo" from within MusE." Not true! I can tell you with *absolute* certainty that should not happen. If it does, it's a bug. Deleting an Audio Output or Input track should disconnect it from Jack. Similarly deleting the connection in QJackCtl should work too. And Redo-ing should automatically reconnect. However I do recall, I wrote once that with Jack1 there seemed to be some funny business under certain conditions with QJackCtl still showing connections, or 'phantom' connections which just won't go away, or connections which refuse to appear but I'm not sure if it was upon deleting tracks, and possibly only Jack Midi connections. Thought it was non-MusE bug. I think it may be in the ChangeLog... Will check. I can't recall Jack2 ever doing this and I think my comments refer to that. Tim. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
