From: Levi D. B. <ld...@pu...> - 2004-10-08 04:09:41
|
Im using muse version 0.7.0. The controllers in the pianoroll are greyed out and uneditable for anything other than velocity. Why is this? How can I edit other controllers? Thanks. -- Levi D. Burton http://www.puresimplicity.net/~ldb/ |
From: Werner S. <ws...@se...> - 2004-10-08 08:07:59
|
On Friday 08 October 2004 04:12, Levi D. Burton wrote: > Im using muse version 0.7.0. > > The controllers in the pianoroll are greyed out and uneditable for anything > other than velocity. Why is this? How can I edit other controllers? > > Thanks. a gray area means that the controller value is undefined. New controller events are created with the pencil tool and pressing shift + left mouse button. Without shift you can only edit already _existing_ controller events. /werner |
From: <in...@ne...> - 2004-10-12 16:37:54
|
Hi, jack sync with ardour works well but there is an offset. MusE is lagging. If you record a fluidsynth into ardour you should start recording before the note comes, ifnot you will lost some data. It seems that MusE have problems with boundaries. When i set a loop in MusE, a Cymbal hit is played albeit not being part of the loop (but just after). Cheers, Linium |
From: Werner S. <ws...@se...> - 2004-10-12 20:17:28
|
On Wednesday 13 October 2004 16:35, in...@ne... wrote: > Hi, > > jack sync with ardour works well but there is an offset. MusE is lagging. > If you record a fluidsynth into ardour you should start recording before > the note comes, ifnot you will lost some data. It seems that MusE have > problems with boundaries. When i set a loop in MusE, a Cymbal hit is played > albeit not being part of the loop (but just after). > > Cheers, > > Linium MusE 0.7 depends for all transport functions on JACK transport. That means a loop can only end on a segment (JACK buffer) boundary i.e. the loop is too long in most cases. To get at least a constant loop len (which is important if you edit a drum pattern) MusE moves the loop start (which can be at arbitrary positions). For every loop play the start and end of the loop may vary a little bit. Of course small buffer sizes (= low latency) help a lot and make this effect nearly unnoticable. But if you have some events near loop start/end you can get some erratic behaviour. All this is of course only a workaround and a special "loop interface" for jack is already announced on the JACK mailing list. I hope this will allow a sample accurate looping implementation. /werner |