To Jo: Editing Controller Data

[Supersonic1]

I don't want to sound critical here, but I wonder if you have any plans to give indicators as to the levels/positions when drawing in controller data under the piano roll.

It would be great if it was a point to point system, where you can create as many or as few points as you like to define the changes over time and that you get at least a temporary view of what level you have drawn the point to e.g. 0db for level or a value of between 0-127 for pan and other controllers.

At the moment it seems that you can only guess what level your at. Also, if there was a clearly visible point created then you could go back and edit it from exactly the right place. The way it is now, it seems too easy to end up with lots of spikes rather than smooth changes when you try to go back and edit.

Also, could there be automation of at least volume (maybe pan as well), integrated in audio tracks in the main screen. At present, as DaveL60 pointed out to me, you can automate these by creating a new sequence track, choosing the mixer strip you want to control, switching into the piano roll editor, choosing gain from the parameters list and drawing in your desired changes in the controller editor. However, you can't see the audio track you want to control when your in the piano roll and you have to keep toggling back and forth.

Maybe these are things on the to-do list already.

[muzycian]

Yes, i want to give every part the possibility to include any automation data, right in the composer

But maybe i shouldn't say this, as you will now start to ask: when? which version?

And i can't give an eta on that yet.

The works on the house are still busy (sorry), they are progressing though. Hope to move my main computer mid december. That will increase my work efficiency anyway.

And besides that, i'm currently focussing on the new Part Property Panel and the new Rack system (evolved mixerstrip system).

So integrated part automation is on the whishlist, but not yet in the R&D pipeline.

[pljones]

Okay, I had some thoughts on this, too...

Sequence parts can contain MIDI CC data which can be routed to a VST as MIDI input, yes? And a sequence part can also contain VST controller data, that isn't MIDI events - is that right? VST controller data having a wider range than MIDI CC (0-127)?

Why have two kinds of Part? Why not just the one? It's all a stream of events... Any part could have sequence (MIDI or VST control) or audio data. That way, all that automation people want to view alongside their audio tracks would just be there... Of course, you'd want to be able to edit automation down to sample-accurate timing, then...

Yuk. Okay - I don't like that at all. In fact, I'd rather see everything separated out - but allow multiple Parts to be viewed/edited in parallel. So you could have a MIDI part (Notes, CCs etc, but strictly MIDI that would export "as is"), a VST control part (maybe allow this exported as some approximation?) and and Audio part all visible and synchronised (vertically).