Hello Dan, Robert, lists. If I may offer my perspective:
Please remember, midi automation using the mixer (touch, write etc)
On May 29, 2009 06:47:18 pm Robert Jonsson wrote:
> Hi Tim,
> Seems there are some issues with automation in the latest and greatest.
> Both for audio and midi.
> For midi, please see my response to Dan's question on the user list.
never worked yet (that's why I didn't make the buttons red).
I have not had time to fix it. I am planning to activate it, but not for
Instead, midi automation is accomplished with controller graphs in the
midi/drum editor windows. Muse will of course also accept recorded midi
controller events, and they should show up in the controller graphs.
Or you can always use the event list editor.
Other than that, the midi automation system SHOULD be fully workable !
Remember that Muse instruments play a big role here - use them to make
various midi controllers show up in the graph's list of controllers.
You've got the basics: Add audio automation events by 'touching' the control
at various time positions, or by right-clicking the control and selecting
There should be NO issues with storing and loading what you have touched -
"what you touched is what you get".
Remember that muse will interpolate (smooth out) between touched points.
The 'write' automation mode is more complicated. It is usually used when
the transport is running so muse will record your control motions.
In lieu of an audio automation HOWTO, I direct you to this:
See the section titled:
In particular the paragraph titled:
"What's the bare minimum I need to know to start using automation?"
I modelled my changes on that paragraph, with these differences:
Touch mode can be used when when stopped so that a single value
can be stored. Write mode can be used when stopped so that a
'first value' can be queued for when you roll the transport and then
move the given control. It will not store until you move the control
Of course, muse has no 'auto latch' mode.
Jack does that sometimes. Sometimes Jack will kick us out,
> Oh, that's right there's a third issue I found. If I use the slider menu to
> go to the "next event" and the next event is long way away (or possibly
> just the last event) it happens often that muse is kicked by jack (atleast
> when jack has small buffers). Is the search for the automation point
> somehow performed in the audio thread?
and if we allow Muse to restart Jack, no problem - it restarts.
But other times Jack keeps on kicking us out again and again
until Muse can't restart the audio any more.
I urge you to try again, restart Jack if you have to.
Eventually you should arrive at a stable setup.
I tried tonight and you are right: When it's bad, it is bad -
kicking us out a lot. But then I tried again, with the same file,
and it was stable.
In general, manual motion of the cursor will tend to cause it more.
Also, if the 'Song type' is other than 'NO', then seeking the
cursor to the beginning of the song causes an intense
process of controller initialization, which can sometimes kill Jack.
Hold on - There is a certain 'type' of Jack 'crackling' which is a classic
> I'm having some issues with crackling also but I'm blaming my hardware for
> that. I've had these problems on and off for a long time and finally
> ordered some new hardware (upgrade time anyway) to try to eliminate it.
symptom which affects many apps including Muse. It's NOT the hardware !
Unless your hardware is really crappy, or you are pushing the buffer
size too small, or you don't have Jack 'really' running in realtime,
then it just might be the same problem that I'm thinking of:
*** If you hear crackling, try Muse's 'restart audio', but note that
it actually never gets rid of the crackling by itself - do this too:
Keep hitting 'Save' until the crackling suddenly stops.
*** I highly recommend this ***
Muse's 'Save' is an operation which is intense, and often actually
CAUSES the crackling to suddenly happen (or Jack to quit).
But repeated 'Save's can often also suddenly STOP the crackling !
I have found that 'Restart audio' NEVER STOPS the crackling,
just 'kicks it' into another 'phase', so that 'Save' has a better chance
of stopping it.
Trust me on this !
Jack shutdown and static noise often appear together.
Well that's all I can stay awake to write for now..
COMMENTS ENCOURAGED !
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
Lmuse-developer mailing list