posted 06 April 2011 19:09            

I have been thinking... *insert collective groan here*

I know this topic has been well debated but I have a question/perhaps feature request.

So... at the moment I create a marvellous synth engine, I mould the structure and sculpt the VCS until everything is intuitive and sensible. One might then populate the VCS pre-set list with some good starting points etc. At this point I might be invested some hours on not only the presets but the VCS layout etc.

Then we enter the composition stage. I like to make use of the Timeline synced to logic. I place sound on the timeline and negotiate and channel and voice issues!!

As you start sequencing and manipulating events and controls on the timeline you remove the parameters one by one from the VCS as you commit the movement to timeline.

It is this process that creates me a little issue. I know the VCS is a realtime reflection of the variables active at that moment, yet I get quite attached to my layouts, but its seems silly to make them nice and colour-coded when they get removed from the layout upon use, it also changes the order of the faders/pots/buttons as they are committed.

I would like a mode where the items stayed put on the VCS once they are automated, either greyed out and inactive or reflect the movement and status of the item, perhaps allowing for a 'overdub/performance' quick grab once the parameter was automated.

Maybe there is a way I have overlooked.

I was thinking of creating a wish on the twiki, but I thought I should canvas some opinion first...

Does that make any sense at all?

Hehe Rotten eggs in this direction thx.

Charlie

posted 22 May 2011 11:29            

Also "grouping" widgets in a VCS layout, which then would stay together in the timelines VCS, would be great and make things much easier!

I also thought about how nice it would be to have discrete VCS for each track of the timeline and then switch between tracks on my motormix!
:-)

posted 24 May 2011 16:28            

As it stands live automation can only be recorded from an external controller as this doesn't have to fight it's way through the host computer. Also you may notice that when you grab a control on the VCS it temporarily stops the rest of the VCS from updating. It's like non duplex coms and more like a switched single direction communication.

The problem is we users do like to have virtually limitless numbers of controls and it will require a lot of processing by the host PC/MAC. As it stands the host PC can be any old thing as the paca/capy is doing nearly all the work. If this area was re written I suspect that there would have to be a restriction on what PC/MAC and operating system you could use with Kyma.

I would love to have these features but it's a biggy and if the SSC guys did do it they would have to be showered with undying gratitude.

posted 27 May 2011 02:32            

However, in my opinion, the main killers with the timeline + VCS are:

- Copying a sound to the timeline changes the arrangement of the sounds VCS.
- All the sounds VCS controls get copied on to the top level timeline VCS.

With the second one I would love some option to turn toggle all VCS controls from a certain track on or off in the global VCS. Personally I usually just use the timeline tracks volume, rotation etc on the top level VCS.

From memory, there's also a frustrating issue with VCS controls added to sounds once they have been put in the timeline. I think I always ended up with those controls only visible on the top layer of the timeline VCS, not at the sound level.

I must admit that due to these shortcomings in the timeline I usually do sequenced work with sounds and MIDI Voices, and CAG's mixer. Which is a shame because the program change jumps in the timeline were really useful....