From: Robert J. <rob...@da...> - 2004-03-08 21:09:25
|
Oh! The manual! :) > > Mixer automation records manual controller changes during _playback_. > Currently there are the following automation modes implemented, > which are selectable for every mixer strip: > > - automation off: > - automation read: > controller gui elements will be updated while playback; > no recording takes place; > You cannot change manually any slider, it will be > changed back immediately. Actually, you can, but it doesn't work ;)... > > - automation write: > manual controller changes are recorded. This "erases" all > previous recorded controller events > > - automation touch: > recording of controller events starts with pressing a > slider or knob. Recording stops if you release the slider. Ah, okay. Have to test later :) ----- Here are a few other bughunting exhibits, big and small, I got a little more time myself now so I might even try to look into some of these myself... time will tell... ----- - Sometimes when I start muse and press play or rec for the first time muse aborts instantly with: tickValues(0x331e303a) not found(1) Aborted If I then start muse again, then it works. Probably something to do with transport...(thanks Mathias for figuring it out), possibly jack has a differing idea of what state transport is actually _in_. Does muse send transport-stop when it starts, possibly it should? - After adding and removing some tracks the mixer got very big at one time, apparently it got confused and still displayed the old tracks, and duplicates other parts. - [del] adds output tracks....that was unexpected :-D - New trackInfo channelstrips are not as wide as the midi trackinfo.... when clicking through tracks this sometimes gets abit distracting. - Made a stereo track, though the waveform view in the arranger was for a mono. - Bounce to disk didn't work, a noise plugin got added but no audiotracks (and probably not midi-softsynths either, think I tried that earlier) where audible. But it was fast :) - Whenever a .MusE file is found upon startup, the meters on the mixer get all wierd. They turn _all_ red instead of having different colors for different volumes, and they don't update at all. - Metronome doesn't work very well... it was not audible during recording until after a few bars. No precount occured either. A few other trials didn't get any meteronome at all during recording... (maybe it would have kicked in later) - I've created several testsongs over the last few days that after restarting of muse can no longer be loaded, the gui freezes before the arranger is visible. If I have realtime enabled in jack they freeze the entire computer for a while (gladly some watchdog catches it and terminates muse) after this jack must be restarted, it's no longer contactable. If I start jack without realtime then muse displays in it's entirety, but I can't move the Locator, nor can I play the song. Jack-transport and, possibly, automation in muse are the things that trigger this. I tried creating a new song, importing a wav file and adding automation directly, but unfortunately I failed, it seems automation isn't working always, or I'm not understanding it, probably both :) - The little indicator on each midi-track that displays if there is midi activity seem to be gone. I think it was a good tool for identifying midi-problems (for some reason I always have problems with midi, both soft and hard), I kind of miss it. All for now, Robert |