Menu
▾
▴
lmuse-developer
|
From: nilitonilito n. <nil...@ho...> - 2006-12-04 22:30:26
Attachments:
midiintest.tar.gz
|
Hi Werner, I join with this email a very simple project that generate the bug on my computer. Simply a midi input connected to deicsonze. Could you try it and tell me if everything is normal on your computer? I noticed something interesting and weird... My kernel is not patched to be real-time and my machine is not very fast (XP2200). When I start jack with the maximum latency (approx 330ms) MusE skips very few midi events. When I start jack with the minimum latency (approx 5ms) MusE skips almost all events. I can see that MidiInPort::eventReceived(snd_seq_event_t* ev) receives well all events by using the option -i when I start muse. So the problem is inside muse but I don't know where. Further more, this does not happen when I use some other jack softsynth, this is also why I believe it is a bug of muse. I think the reason why such a bug didn't show up on your machine is because it is more powerfull and the kernel is patched for real time (can you confirm me that?). Just to be sure, I tryied from the last clean svn check out but the bug is still here. Maybe you can succeed to reproduce this bug by starting jack with a very very low latency...? If you have any idea or suggestion, even roughly, I am most interested. Regards, Nil >From: Werner Schweer <ws...@se...> >To: lmu...@li... >CC: nilitonilito nilitonilito <nil...@ho...> >Subject: Re: [Lmuse-developer] Midi message disorder >Date: Mon, 4 Dec 2006 21:50:36 +0100 > >Hi Nil, > >i cannot reproduce the bug you see. For me its all working fine. >I have an external keyboard connected to midi in and playing directly to >a soft synth, recording to a midi track and playback of a midi track >all work here. >Maybe you should start MusE with -o option to see what events are >actually send to the synth. I had some problems with midi routing. Funny >things happen if there is more than one route from input to track or >Midi Out /SoftSynth. >You should check the *.med file to make sure the routes are right. > >Regards, >Werner > >On Monday 04 December 2006 18:55, nilitonilito nilitonilito wrote: > > Hi all, > > > > I am impatient to play with the new version of MusE 1.0. The first bug >that > > hampers me is that the midi messages (when too frequent?) arrive in my > > softsynth in disorder, resulting in missing notes or never cutting off > > others. I really wish to have this bug fixed but I don't know where to > > start. > > > > Werner or others, do you know what is driving this bug, do you have sone > > ideas about the files involed in this bug that I have to look into >first? > > > > I noticed that this bug occurs when the midi events come from a midi >input > > or a miditrack going to an internal softsynth (MESS or DSSI equally). >When > > the midi are going out of MusE by midi output the bug seems to be less > > frequent but still here (or I was just more lucky those times). > > > > Thanks for your help, > > Nil > > > > _________________________________________________________________ > > Découvrez Live.com : le nouveau moteur de recherche par Messenger! > > http://www.windowslive.fr/livecom/ > > > > > > >------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share >your > > opinions on IT & business topics through brief surveys - and earn cash > > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Lmuse-developer mailing list > > Lmu...@li... > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys - and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Lmuse-developer mailing list >Lmu...@li... >https://lists.sourceforge.net/lists/listinfo/lmuse-developer _________________________________________________________________ Les révélations de la starac 6 commentées par Jérémy! http://starac2006.spaces.live.com/ |
|
From: Werner S. <ws...@se...> - 2006-12-04 23:00:13
|
Hello Nil, your testproject works fine on my system. I tried with 2.9ms and 186ms latency. No missing or hanging notes. Only when using sustain i got some weird effects (arbitrary notes stopped, voice overflow?). My machine is a dual athlon running at 2 GHz. The kernel version is 2.6.18-rt7 (realtime patched).=20 Of course MusE should work on a slow machine and should not drop any midi events. Only some JACK xruns are expected if the load is too high. Tomorrow i will try it on a different system (laptop). Werner On Monday 04 December 2006 23:30, nilitonilito nilitonilito wrote: > Hi Werner, >=20 > I join with this email a very simple project that generate the bug on my= =20 > computer. Simply a midi input connected to deicsonze. Could you try it an= d=20 > tell me if everything is normal on your computer? >=20 > I noticed something interesting and weird... > My kernel is not patched to be real-time and my machine is not very fast= =20 > (XP2200). When I start jack with the maximum latency (approx 330ms) MusE= =20 > skips very few midi events. When I start jack with the minimum latency=20 > (approx 5ms) MusE skips almost all events. >=20 > I can see that MidiInPort::eventReceived(snd_seq_event_t* ev) receives we= ll=20 > all events by using the option -i when I start muse. So the problem is=20 > inside muse but I don't know where. Further more, this does not happen wh= en=20 > I use some other jack softsynth, this is also why I believe it is a bug o= f=20 > muse. I think the reason why such a bug didn't show up on your machine is= =20 > because it is more powerfull and the kernel is patched for real time (can= =20 > you confirm me that?). >=20 > Just to be sure, I tryied from the last clean svn check out but the bug i= s=20 > still here. >=20 > Maybe you can succeed to reproduce this bug by starting jack with a very= =20 > very low latency...? >=20 > If you have any idea or suggestion, even roughly, I am most interested. >=20 > Regards, > Nil >=20 > >From: Werner Schweer <ws...@se...> > >To: lmu...@li... > >CC: nilitonilito nilitonilito <nil...@ho...> > >Subject: Re: [Lmuse-developer] Midi message disorder > >Date: Mon, 4 Dec 2006 21:50:36 +0100 > > > >Hi Nil, > > > >i cannot reproduce the bug you see. For me its all working fine. > >I have an external keyboard connected to midi in and playing directly to > >a soft synth, recording to a midi track and playback of a midi track > >all work here. > >Maybe you should start MusE with -o option to see what events are > >actually send to the synth. I had some problems with midi routing. Funny > >things happen if there is more than one route from input to track or > >Midi Out /SoftSynth. > >You should check the *.med file to make sure the routes are right. > > > >Regards, > >Werner > > > >On Monday 04 December 2006 18:55, nilitonilito nilitonilito wrote: > > > Hi all, > > > > > > I am impatient to play with the new version of MusE 1.0. The first bu= g=20 > >that > > > hampers me is that the midi messages (when too frequent?) arrive in my > > > softsynth in disorder, resulting in missing notes or never cutting off > > > others. I really wish to have this bug fixed but I don't know where to > > > start. > > > > > > Werner or others, do you know what is driving this bug, do you have s= one > > > ideas about the files involed in this bug that I have to look into=20 > >first? > > > > > > I noticed that this bug occurs when the midi events come from a midi= =20 > >input > > > or a miditrack going to an internal softsynth (MESS or DSSI equally).= =20 > >When > > > the midi are going out of MusE by midi output the bug seems to be less > > > frequent but still here (or I was just more lucky those times). > > > > > > Thanks for your help, > > > Nil > > > > > > _________________________________________________________________ > > > D=E9couvrez Live.com : le nouveau moteur de recherche par Messenger! > > > http://www.windowslive.fr/livecom/ > > > > > > > > >=20 > >------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to sha= re=20 > >your > > > opinions on IT & business topics through brief surveys - and earn cash > > >=20 > >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > > > _______________________________________________ > > > Lmuse-developer mailing list > > > Lmu...@li... > > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > > > > > >------------------------------------------------------------------------- > >Take Surveys. Earn Cash. Influence the Future of IT > >Join SourceForge.net's Techsay panel and you'll get the chance to share= =20 > >your > >opinions on IT & business topics through brief surveys - and earn cash > >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > >_______________________________________________ > >Lmuse-developer mailing list > >Lmu...@li... > >https://lists.sourceforge.net/lists/listinfo/lmuse-developer >=20 > _________________________________________________________________ > Les r=E9v=E9lations de la starac 6 comment=E9es par J=E9r=E9my!=20 > http://starac2006.spaces.live.com/ >=20 |
|
From: nilitonilito n. <nil...@ho...> - 2006-12-04 23:29:58
|
>your testproject works fine on my system. I tried with 2.9ms and 186ms >latency. No missing or hanging notes. Only when using sustain i got some >weird effects (arbitrary notes stopped, voice overflow?). Oh, interesting that you mension that, certainly a bug of deicsonze that I have to fix. >My machine is a dual athlon running at 2 GHz. The kernel version is >2.6.18-rt7 (realtime patched). >Of course MusE should work on a slow machine and should not drop any midi >events. Only some JACK xruns are expected if the load is too high. I am reading the code of midiinport.cpp and others and I start wondering if this bug isn't related to the new midi implementation of jack, since (as I understood...) getEvents is called by jack... >Tomorrow i will try it on a different system (laptop). good idea. Nil > >Werner > >On Monday 04 December 2006 23:30, nilitonilito nilitonilito wrote: > > Hi Werner, > > > > I join with this email a very simple project that generate the bug on my > > computer. Simply a midi input connected to deicsonze. Could you try it >and > > tell me if everything is normal on your computer? > > > > I noticed something interesting and weird... > > My kernel is not patched to be real-time and my machine is not very fast > > (XP2200). When I start jack with the maximum latency (approx 330ms) MusE > > skips very few midi events. When I start jack with the minimum latency > > (approx 5ms) MusE skips almost all events. > > > > I can see that MidiInPort::eventReceived(snd_seq_event_t* ev) receives >well > > all events by using the option -i when I start muse. So the problem is > > inside muse but I don't know where. Further more, this does not happen >when > > I use some other jack softsynth, this is also why I believe it is a bug >of > > muse. I think the reason why such a bug didn't show up on your machine >is > > because it is more powerfull and the kernel is patched for real time >(can > > you confirm me that?). > > > > Just to be sure, I tryied from the last clean svn check out but the bug >is > > still here. > > > > Maybe you can succeed to reproduce this bug by starting jack with a very > > very low latency...? > > > > If you have any idea or suggestion, even roughly, I am most interested. > > > > Regards, > > Nil > > > > >From: Werner Schweer <ws...@se...> > > >To: lmu...@li... > > >CC: nilitonilito nilitonilito <nil...@ho...> > > >Subject: Re: [Lmuse-developer] Midi message disorder > > >Date: Mon, 4 Dec 2006 21:50:36 +0100 > > > > > >Hi Nil, > > > > > >i cannot reproduce the bug you see. For me its all working fine. > > >I have an external keyboard connected to midi in and playing directly >to > > >a soft synth, recording to a midi track and playback of a midi track > > >all work here. > > >Maybe you should start MusE with -o option to see what events are > > >actually send to the synth. I had some problems with midi routing. >Funny > > >things happen if there is more than one route from input to track or > > >Midi Out /SoftSynth. > > >You should check the *.med file to make sure the routes are right. > > > > > >Regards, > > >Werner > > > > > >On Monday 04 December 2006 18:55, nilitonilito nilitonilito wrote: > > > > Hi all, > > > > > > > > I am impatient to play with the new version of MusE 1.0. The first >bug > > >that > > > > hampers me is that the midi messages (when too frequent?) arrive in >my > > > > softsynth in disorder, resulting in missing notes or never cutting >off > > > > others. I really wish to have this bug fixed but I don't know where >to > > > > start. > > > > > > > > Werner or others, do you know what is driving this bug, do you have >sone > > > > ideas about the files involed in this bug that I have to look into > > >first? > > > > > > > > I noticed that this bug occurs when the midi events come from a midi > > >input > > > > or a miditrack going to an internal softsynth (MESS or DSSI >equally). > > >When > > > > the midi are going out of MusE by midi output the bug seems to be >less > > > > frequent but still here (or I was just more lucky those times). > > > > > > > > Thanks for your help, > > > > Nil > > > > > > > > _________________________________________________________________ > > > > Découvrez Live.com : le nouveau moteur de recherche par Messenger! > > > > http://www.windowslive.fr/livecom/ > > > > > > > > > > > > > > > >------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net's Techsay panel and you'll get the chance to >share > > >your > > > > opinions on IT & business topics through brief surveys - and earn >cash > > > > > > > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > _______________________________________________ > > > > Lmuse-developer mailing list > > > > Lmu...@li... > > > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > > > > > > > > > > >------------------------------------------------------------------------- > > >Take Surveys. Earn Cash. Influence the Future of IT > > >Join SourceForge.net's Techsay panel and you'll get the chance to share > > >your > > >opinions on IT & business topics through brief surveys - and earn cash > > > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > >_______________________________________________ > > >Lmuse-developer mailing list > > >Lmu...@li... > > >https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > _________________________________________________________________ > > Les révélations de la starac 6 commentées par Jérémy! > > http://starac2006.spaces.live.com/ > > > _________________________________________________________________ Live.com: Le nouveau moteur de recherche par Messenger! http://www.windowslive.fr/livecom/ |
|
From: Robert J. <rj...@sp...> - 2006-12-04 23:39:02
|
Hi guys, Just some additional input, I tried the test program on my machine. Amd dua= l=20 core with unpatched SMP kernel. =46irst I was running jack with 128 frames and no realtime, behaviour was r= eally=20 bad, lots of clicks and stuck notes. The clicks are to be expected though. Tried with 256 frames and -R, now it mostly works, but it's no problem to g= et=20 stuck notes. Do note that my keyboard produces aftertouch so there are lots of midi=20 messages flying around. A question about the new midi input meter. For me it only lights the first= =20 light (1), is that the right behaviour? Regards, Robert On Tuesday 05 December 2006 00:29, nilitonilito nilitonilito wrote: > >your testproject works fine on my system. I tried with 2.9ms and 186ms > >latency. No missing or hanging notes. Only when using sustain i got some > >weird effects (arbitrary notes stopped, voice overflow?). > > Oh, interesting that you mension that, certainly a bug of deicsonze that I > have to fix. > > >My machine is a dual athlon running at 2 GHz. The kernel version is > >2.6.18-rt7 (realtime patched). > >Of course MusE should work on a slow machine and should not drop any midi > >events. Only some JACK xruns are expected if the load is too high. > > I am reading the code of midiinport.cpp and others and I start wondering = if > this bug isn't related to the new midi implementation of jack, since (as I > understood...) getEvents is called by jack... > > >Tomorrow i will try it on a different system (laptop). > > good idea. > > Nil > > >Werner > > > >On Monday 04 December 2006 23:30, nilitonilito nilitonilito wrote: > > > Hi Werner, > > > > > > I join with this email a very simple project that generate the bug on > > > my computer. Simply a midi input connected to deicsonze. Could you try > > > it > > > >and > > > > > tell me if everything is normal on your computer? > > > > > > I noticed something interesting and weird... > > > My kernel is not patched to be real-time and my machine is not very > > > fast (XP2200). When I start jack with the maximum latency (approx > > > 330ms) MusE skips very few midi events. When I start jack with the > > > minimum latency (approx 5ms) MusE skips almost all events. > > > > > > I can see that MidiInPort::eventReceived(snd_seq_event_t* ev) receives > > > >well > > > > > all events by using the option -i when I start muse. So the problem is > > > inside muse but I don't know where. Further more, this does not happen > > > >when > > > > > I use some other jack softsynth, this is also why I believe it is a b= ug > > > >of > > > > > muse. I think the reason why such a bug didn't show up on your machine > > > >is > > > > > because it is more powerfull and the kernel is patched for real time > > > >(can > > > > > you confirm me that?). > > > > > > Just to be sure, I tryied from the last clean svn check out but the b= ug > > > >is > > > > > still here. > > > > > > Maybe you can succeed to reproduce this bug by starting jack with a > > > very very low latency...? > > > > > > If you have any idea or suggestion, even roughly, I am most intereste= d. > > > > > > Regards, > > > Nil > > > > > > >From: Werner Schweer <ws...@se...> > > > >To: lmu...@li... > > > >CC: nilitonilito nilitonilito <nil...@ho...> > > > >Subject: Re: [Lmuse-developer] Midi message disorder > > > >Date: Mon, 4 Dec 2006 21:50:36 +0100 > > > > > > > >Hi Nil, > > > > > > > >i cannot reproduce the bug you see. For me its all working fine. > > > >I have an external keyboard connected to midi in and playing directly > > > >to > > > > > >a soft synth, recording to a midi track and playback of a midi track > > > >all work here. > > > >Maybe you should start MusE with -o option to see what events are > > > >actually send to the synth. I had some problems with midi routing. > > > >Funny > > > > > >things happen if there is more than one route from input to track or > > > >Midi Out /SoftSynth. > > > >You should check the *.med file to make sure the routes are right. > > > > > > > >Regards, > > > >Werner > > > > > > > >On Monday 04 December 2006 18:55, nilitonilito nilitonilito wrote: > > > > > Hi all, > > > > > > > > > > I am impatient to play with the new version of MusE 1.0. The first > > > >bug > > > > > >that > > > > > > > > > hampers me is that the midi messages (when too frequent?) arrive = in > > > >my > > > > > > > softsynth in disorder, resulting in missing notes or never cutting > > > >off > > > > > > > others. I really wish to have this bug fixed but I don't know whe= re > > > >to > > > > > > > start. > > > > > > > > > > Werner or others, do you know what is driving this bug, do you ha= ve > > > >sone > > > > > > > ideas about the files involed in this bug that I have to look into > > > > > > > >first? > > > > > > > > > I noticed that this bug occurs when the midi events come from a > > > > > midi > > > > > > > >input > > > > > > > > > or a miditrack going to an internal softsynth (MESS or DSSI > > > >equally). > > > > > >When > > > > > > > > > the midi are going out of MusE by midi output the bug seems to be > > > >less > > > > > > > frequent but still here (or I was just more lucky those times). > > > > > > > > > > Thanks for your help, > > > > > Nil > > > > > > > > > > _________________________________________________________________ > > > > > D=E9couvrez Live.com : le nouveau moteur de recherche par Messeng= er! > > > > > http://www.windowslive.fr/livecom/ > > > > > >----------------------------------------------------------------------= =2D- > > >- > > > > > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > >share > > > > > >your > > > > > > > > > opinions on IT & business topics through brief surveys - and earn > > > >cash > > > > >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDE > > >V > > > > > > > > _______________________________________________ > > > > > Lmuse-developer mailing list > > > > > Lmu...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > > >----------------------------------------------------------------------= =2D- > > >- > > > > > > >Take Surveys. Earn Cash. Influence the Future of IT > > > >Join SourceForge.net's Techsay panel and you'll get the chance to > > > > share your > > > >opinions on IT & business topics through brief surveys - and earn ca= sh > > > > > >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDE > > >V > > > > > > >_______________________________________________ > > > >Lmuse-developer mailing list > > > >Lmu...@li... > > > >https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > > > _________________________________________________________________ > > > Les r=E9v=E9lations de la starac 6 comment=E9es par J=E9r=E9my! > > > http://starac2006.spaces.live.com/ > > _________________________________________________________________ > Live.com: Le nouveau moteur de recherche par Messenger! > http://www.windowslive.fr/livecom/ > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys - and earn ca= sh > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer =2D-=20 http://spamatica.se/musicsite/ |
|
From: nilitonilito n. <nil...@ho...> - 2006-12-05 00:23:32
|
Hi Robert, >Hi guys, > >Just some additional input, I tried the test program on my machine. Amd >dual >core with unpatched SMP kernel. > >First I was running jack with 128 frames and no realtime, behaviour was >really >bad, lots of clicks and stuck notes. The clicks are to be expected though. >Tried with 256 frames and -R, now it mostly works, but it's no problem to >get >stuck notes. Good point...I tried with -R and it is almost perfect, only very few skipped events. Also, my assumption that the error could come from jack is not right because I could check that getEvents is always properly called. Still trying to find out... Nil >Do note that my keyboard produces aftertouch so there are lots of midi >messages flying around. > >A question about the new midi input meter. For me it only lights the first >light (1), is that the right behaviour? > >Regards, >Robert > >On Tuesday 05 December 2006 00:29, nilitonilito nilitonilito wrote: > > >your testproject works fine on my system. I tried with 2.9ms and 186ms > > >latency. No missing or hanging notes. Only when using sustain i got >some > > >weird effects (arbitrary notes stopped, voice overflow?). > > > > Oh, interesting that you mension that, certainly a bug of deicsonze that >I > > have to fix. > > > > >My machine is a dual athlon running at 2 GHz. The kernel version is > > >2.6.18-rt7 (realtime patched). > > >Of course MusE should work on a slow machine and should not drop any >midi > > >events. Only some JACK xruns are expected if the load is too high. > > > > I am reading the code of midiinport.cpp and others and I start wondering >if > > this bug isn't related to the new midi implementation of jack, since (as >I > > understood...) getEvents is called by jack... > > > > >Tomorrow i will try it on a different system (laptop). > > > > good idea. > > > > Nil > > > > >Werner > > > > > >On Monday 04 December 2006 23:30, nilitonilito nilitonilito wrote: > > > > Hi Werner, > > > > > > > > I join with this email a very simple project that generate the bug >on > > > > my computer. Simply a midi input connected to deicsonze. Could you >try > > > > it > > > > > >and > > > > > > > tell me if everything is normal on your computer? > > > > > > > > I noticed something interesting and weird... > > > > My kernel is not patched to be real-time and my machine is not very > > > > fast (XP2200). When I start jack with the maximum latency (approx > > > > 330ms) MusE skips very few midi events. When I start jack with the > > > > minimum latency (approx 5ms) MusE skips almost all events. > > > > > > > > I can see that MidiInPort::eventReceived(snd_seq_event_t* ev) >receives > > > > > >well > > > > > > > all events by using the option -i when I start muse. So the problem >is > > > > inside muse but I don't know where. Further more, this does not >happen > > > > > >when > > > > > > > I use some other jack softsynth, this is also why I believe it is a >bug > > > > > >of > > > > > > > muse. I think the reason why such a bug didn't show up on your >machine > > > > > >is > > > > > > > because it is more powerfull and the kernel is patched for real time > > > > > >(can > > > > > > > you confirm me that?). > > > > > > > > Just to be sure, I tryied from the last clean svn check out but the >bug > > > > > >is > > > > > > > still here. > > > > > > > > Maybe you can succeed to reproduce this bug by starting jack with a > > > > very very low latency...? > > > > > > > > If you have any idea or suggestion, even roughly, I am most >interested. > > > > > > > > Regards, > > > > Nil > > > > > > > > >From: Werner Schweer <ws...@se...> > > > > >To: lmu...@li... > > > > >CC: nilitonilito nilitonilito <nil...@ho...> > > > > >Subject: Re: [Lmuse-developer] Midi message disorder > > > > >Date: Mon, 4 Dec 2006 21:50:36 +0100 > > > > > > > > > >Hi Nil, > > > > > > > > > >i cannot reproduce the bug you see. For me its all working fine. > > > > >I have an external keyboard connected to midi in and playing >directly > > > > > >to > > > > > > > >a soft synth, recording to a midi track and playback of a midi >track > > > > >all work here. > > > > >Maybe you should start MusE with -o option to see what events are > > > > >actually send to the synth. I had some problems with midi routing. > > > > > >Funny > > > > > > > >things happen if there is more than one route from input to track >or > > > > >Midi Out /SoftSynth. > > > > >You should check the *.med file to make sure the routes are right. > > > > > > > > > >Regards, > > > > >Werner > > > > > > > > > >On Monday 04 December 2006 18:55, nilitonilito nilitonilito wrote: > > > > > > Hi all, > > > > > > > > > > > > I am impatient to play with the new version of MusE 1.0. The >first > > > > > >bug > > > > > > > >that > > > > > > > > > > > hampers me is that the midi messages (when too frequent?) arrive >in > > > > > >my > > > > > > > > > softsynth in disorder, resulting in missing notes or never >cutting > > > > > >off > > > > > > > > > others. I really wish to have this bug fixed but I don't know >where > > > > > >to > > > > > > > > > start. > > > > > > > > > > > > Werner or others, do you know what is driving this bug, do you >have > > > > > >sone > > > > > > > > > ideas about the files involed in this bug that I have to look >into > > > > > > > > > >first? > > > > > > > > > > > I noticed that this bug occurs when the midi events come from a > > > > > > midi > > > > > > > > > >input > > > > > > > > > > > or a miditrack going to an internal softsynth (MESS or DSSI > > > > > >equally). > > > > > > > >When > > > > > > > > > > > the midi are going out of MusE by midi output the bug seems to >be > > > > > >less > > > > > > > > > frequent but still here (or I was just more lucky those times). > > > > > > > > > > > > Thanks for your help, > > > > > > Nil > > > > > > > > > > > > >_________________________________________________________________ > > > > > > Découvrez Live.com : le nouveau moteur de recherche par >Messenger! > > > > > > http://www.windowslive.fr/livecom/ > > > > > > > > >------------------------------------------------------------------------ > > > >- > > > > > > > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > > > Join SourceForge.net's Techsay panel and you'll get the chance >to > > > > > >share > > > > > > > >your > > > > > > > > > > > opinions on IT & business topics through brief surveys - and >earn > > > > > >cash > > > > > > > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > > > >V > > > > > > > > > > _______________________________________________ > > > > > > Lmuse-developer mailing list > > > > > > Lmu...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > > > > > >------------------------------------------------------------------------ > > > >- > > > > > > > > >Take Surveys. Earn Cash. Influence the Future of IT > > > > >Join SourceForge.net's Techsay panel and you'll get the chance to > > > > > share your > > > > >opinions on IT & business topics through brief surveys - and earn >cash > > > > > > > > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > > > >V > > > > > > > > >_______________________________________________ > > > > >Lmuse-developer mailing list > > > > >Lmu...@li... > > > > >https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > > > > > _________________________________________________________________ > > > > Les révélations de la starac 6 commentées par Jérémy! > > > > http://starac2006.spaces.live.com/ > > > > _________________________________________________________________ > > Live.com: Le nouveau moteur de recherche par Messenger! > > http://www.windowslive.fr/livecom/ > > > > > > >------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys - and earn >cash > > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Lmuse-developer mailing list > > Lmu...@li... > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > >-- >http://spamatica.se/musicsite/ > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys - and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Lmuse-developer mailing list >Lmu...@li... >https://lists.sourceforge.net/lists/listinfo/lmuse-developer _________________________________________________________________ Ten : profite de ton Messenger en illimité sur ton mobile ! http://mobile.live.fr/messenger/ten/ |
|
From: Werner S. <ws...@se...> - 2006-12-05 12:54:12
|
On Tuesday 05 December 2006 01:23, nilitonilito nilitonilito wrote: > Hi Robert, > > >Hi guys, > > > >Just some additional input, I tried the test program on my machine. Amd > >dual > >core with unpatched SMP kernel. > > > >First I was running jack with 128 frames and no realtime, behaviour was > >really > >bad, lots of clicks and stuck notes. The clicks are to be expected though. > >Tried with 256 frames and -R, now it mostly works, but it's no problem to > >get > >stuck notes. > > Good point...I tried with -R and it is almost perfect, only very few skipped > events. the bug is hidden by RT. Switching to non-RT i get the same problems with missing midi events. I found the bug and a fix is already in svn but needs more testing. Werner |
|
From: nilitonilito n. <nil...@ho...> - 2006-12-05 15:40:25
|
>the bug is hidden by RT. Switching to non-RT i get the same problems with >missing >midi events. >I found the bug and a fix is already in svn but needs more testing. That's great! Can't wait testing it and looking at the fix. Nil > >Werner _________________________________________________________________ Live.com: le nouveau moteur de recherche par Messenger! http://www.windowslive.fr/livecom/ |
|
From: nilitonilito n. <nil...@ho...> - 2006-12-08 15:49:29
|
Hi Werner, I noticed that there is a muse.pro in the root of the project. I first thought it was for designer but I cannot open it. Is there some IDE that can open it and use it (and by the way, what tools are you using for developing MusE? I once tried some IDEs but I didn't like the editors so I am still developing with the old emacs). Or maybe this muse.pro is for CMake? Regards Nil _________________________________________________________________ Live.com: le nouveau moteur de recherche par Messenger! http://www.windowslive.fr/livecom/ |
|
From: Werner S. <ws...@se...> - 2006-12-08 17:11:50
|
On Friday 08 December 2006 16:49, nilitonilito nilitonilito wrote: > Hi Werner, > > I noticed that there is a muse.pro in the root of the project. I first > thought it was for designer but I cannot open it. Is there some IDE that can > open it and use it (and by the way, what tools are you using for developing > MusE? I once tried some IDEs but I didn't like the editors so I am still > developing with the old emacs). > > Or maybe this muse.pro is for CMake? > its a qt project file normally used for qmake. Its actually used for the qt lupdate and lrelease utilities to produce the translation files. The procedure is described in doc/README.translate. Werner |
|
From: Werner S. <ws...@se...> - 2006-12-05 08:41:32
|
On Tuesday 05 December 2006 00:39, Robert Jonsson wrote: > Hi guys, > > Just some additional input, I tried the test program on my machine. Amd dual > core with unpatched SMP kernel. > > First I was running jack with 128 frames and no realtime, behaviour was really > bad, lots of clicks and stuck notes. The clicks are to be expected though. > Tried with 256 frames and -R, now it mostly works, but it's no problem to get > stuck notes. > Do note that my keyboard produces aftertouch so there are lots of midi > messages flying around. > > A question about the new midi input meter. For me it only lights the first > light (1), is that the right behaviour? every light is associated with a midi channel. There is no "meter" anymore but some kind of activity light which means that your keyboard is sending events at midi channel 1. Werner |
|
From: <rj...@sp...> - 2006-12-05 10:23:02
|
Werner Schweer skrev: > On Tuesday 05 December 2006 00:39, Robert Jonsson wrote: > >> A question about the new midi input meter. For me it only lights the first >> light (1), is that the right behaviour? >> > > every light is associated with a midi channel. There is no "meter" anymore but > some kind of activity light which means that your keyboard is > sending events at midi channel 1. > Aha, I was so obsessed with it being a meter, great solution! /Robert > Werner > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
Thanks for helping keep SourceForge clean.
X