From: Patrick S. <be...@la...> - 2004-07-28 16:17:55
|
Intel system with fedora core 2 and updated kernel rpm 2.6.7 however no realtime-lsm module. sblive and midisport 2x2 usb I have been seeing some error messages from jack after doing the midi import and trying to play the midi file. So the odd behavior I have been reporting with muse and midi import may be from not having all the system requirements. That being said I have the latest source from sourceforge installed now and the rpm from ccrma has been removed After importing the lilypond midi file, I have to have do two things move the end marker and adjust the value in the len box which is defaulting to a value of 1. After I save the med file, I can play the file. I will be configuring another system with the realtime-lsm but not right away. |
From: John C. <j4s...@bi...> - 2004-07-28 20:00:36
|
On Wednesday 28 July 2004 12:17 pm, Patrick Stanistreet wrote: > Intel system with fedora core 2 and updated kernel rpm 2.6.7 > however no realtime-lsm module. sblive and midisport 2x2 usb > > I have been seeing some error messages from jack after doing > the midi import and trying to play the midi file. > So the odd behavior I have been reporting with muse and midi > import may be from not having all the system requirements. > I don't think that's likely, but it's possible. The import/export is all MusE. If it was something else, there would a likelihood of it affecting another midi playback app. > That being said I have the latest source from sourceforge > installed now and the rpm from ccrma has been removed > > After importing the lilypond midi file, I have to have do two > things move the end marker and adjust the value in the len box > which is defaulting to a value of 1. After I save the med file, > I can play the file. > > I will be configuring another system with the realtime-lsm > but not right away. I have my system configured thusly. Get me a copy of the MIDI file from lilypond and I'll see if it makes a difference here. You probably should bypass the list, or post it to the net and send a link, unless it's real small. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: Russell H. <han...@st...> - 2004-07-29 07:04:48
|
On Wed, 2004-07-28 at 13:08, John Check wrote: > On Wednesday 28 July 2004 12:17 pm, Patrick Stanistreet wrote: > > Intel system with fedora core 2 and updated kernel rpm 2.6.7 > > however no realtime-lsm module. sblive and midisport 2x2 usb > > > > I have been seeing some error messages from jack after doing > > the midi import and trying to play the midi file. > > So the odd behavior I have been reporting with muse and midi > > import may be from not having all the system requirements. Similar problems on MDK 10.0 w/ 2.6.7 w/lsm. Importing regular midi file seems to piss jack off. Along with loading sound fonts in Fluidsynth. Might be another 2.6.* issue? The "realtime priority" argument has me curious for Muse? What is it's purpose or more over, why is there a choice. Most linux DAW apps are either RT or not right? > > > > I don't think that's likely, but it's possible. The import/export is all MusE. > If it was something else, there would a likelihood of it affecting > another midi playback app. > > > That being said I have the latest source from sourceforge > > installed now and the rpm from ccrma has been removed > > > > After importing the lilypond midi file, I have to have do two > > things move the end marker and adjust the value in the len box > > which is defaulting to a value of 1. After I save the med file, > > I can play the file. > > > > I will be configuring another system with the realtime-lsm > > but not right away. > > I have my system configured thusly. Get me a copy of the MIDI > file from lilypond and I'll see if it makes a difference here. > You probably should bypass the list, or post it to the net and send a link, > unless it's real small. > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by BEA Weblogic Workshop > > FREE Java Enterprise J2EE developer tools! > > Get your free copy of BEA WebLogic Workshop 8.1 today. > > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > > _______________________________________________ > > Lmuse-user mailing list > > Lmu...@li... > > https://lists.sourceforge.net/lists/listinfo/lmuse-user > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: Robert J. <rj...@sp...> - 2004-07-29 07:36:35
|
> > > > > > I have been seeing some error messages from jack after doing > > > the midi import and trying to play the midi file. > > > So the odd behavior I have been reporting with muse and midi > > > import may be from not having all the system requirements. > > Similar problems on MDK 10.0 w/ 2.6.7 w/lsm. Importing regular midi file > seems to piss jack off. Along with loading sound fonts in Fluidsynth. > Might be another 2.6.* issue? The "realtime priority" argument has me > curious for Muse? What is it's purpose or more over, why is there a > choice. Most linux DAW apps are either RT or not right? It's not a choice of using RT or not, even in RT there are different levels. You are selecting the RT-thread priority. Set it to max and your machine is more likely to lock up 8-). Normally you should never change this. /Robert -- http://spamatica.se/music/ |