From: Werner S. <ws...@se...> - 2004-03-08 22:12:20
|
On Monday 08 March 2004 21:57, Robert Jonsson wrote: > Oh! The manual! :) manual writin is evil! It instantly shows all the open ends, missing code, misfeatures, design flaws etc. > > > 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? it was commented out for some testing and is now active again. > > - 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. funny effect; hopefully now fixed in cvs more fixes coming soon... /Werner |