What I want. What I really, really want

[Bunnyboy]

Hi folks,

The FR threads are stuffed to the gills, so rather than add to them, I thought that I would highlight the ones that I most desire (these are all in there)

- Per clip VST/i assigning
- Using the QWERTY keyboard as an input source
- Triggering marker sections by Midi/QWERTY
- Midi/QWERTY automatable bypass button on each plugin!

What do you all think

[jens]

Hi folks,

The FR threads are stuffed to the gills, so rather than add to them, I thought that I would highlight the ones that I most desire (these are all in there)

- Per clip VST/i assigning

Yes!!!

Jorgen has already planned it and also even per clip automation.

- Using the QWERTY keyboard as an input source

I couldn't care less

- Triggering marker sections by Midi/QWERTY

Yes!

- Midi/QWERTY automatable bypass button on each plugin!

might be great for live-usage

What do you all think

Better don't ask

[elfan]

- Per clip VST/i assigning

Oh, yeah !

- Using the QWERTY keyboard as an input source

I would really like that in the sequencer/midi parts, at least. A more general approach could be to add a component that listens for keyboard input and sends midi to whatever component/plugin you connect it to (whenever the function is activated... I believe Jorgen suggested that this function should be enabled when caps lock is enabled). One of my top 5 .

//Tomas

[scuzzphut]

seamless export/reimport of audio to an external editor.

a playlist for the marker tracks.

that would do me

I like your ideas about qwerty triggering
I don't really see the big deal with per-clip vsti?

anyone care to convert me ?

[plastique]

- Midi/QWERTY automatable bypass button on each plugin!

i'd like to see this one implemented (cc automation would be good enough already).
mainly because you can then set an insert to a track and then can say while looking at the timeline "from here i like it to take effect until here" .

[jens]

I don't really see the big deal with per-clip vsti?

anyone care to convert me ?

(he wrote per clip vst/i )

o.k. - will do:

disclaimer: This is an extreme and unrealistic example.

Let's say you only got five drumloops.
Each drum-loop has it's own track.
Now you cut each drumloop into 16 slices so you've got 80 objects - Each object is exactly 1/16 long.

Now you want each object to contain five diffrent vst-fx so that's 400 fx all in all - with Cubase

it would be 80 vsti on each track - impossible.
With Tracktion it's only 5*5=25 fx being calculated
at the same time and you don't need any automation at all for it.

'Why should someone do such a weird thing?' you might
ask now, but that would miss the point.

With Tracktion you start to arrange and mix (and perhaps even compose)object orientated which means you don't think about tracks but instead about moments. E.g.: 'the background vox could nead for that single word here some mixture of distortion
delay and filtering' - suddenly you start to have
ideas which you wouldn't get with a track-orientated
sequencer because it would either be too complicated or impossible. (I wouldn't start automating three fx for the effect of a single word- maybe it's another three with another word) - I'm not doing experimental stuff but pop-orientated songs and I think it's
incredibly useful!

http://www.kvr-vst.com/forum/viewtopic. ... torder=asc

[tjvigil66]

- Using the QWERTY keyboard as an input source

http://www.kvr-vst.com/get/258.html

[ModuLR]

what I really want...


an icon for the .exe so I don't have to keep looking at that standard app icon in the taskbar...

[Caleb]

o.k. - will do:

disclaimer: This is an extreme and unrealistic example.

Let's say you only got five drumloops.
Each drum-loop has it's own track.
Now you cut each drumloop into 16 slices so you've got 80 objects - Each object is exactly 1/16 long.

Now you want each object to contain five diffrent vst-fx so that's 400 fx all in all - with Cubase

it would be 80 vsti on each track - impossible.
With Tracktion it's only 5*5=25 fx being calculated
at the same time and you don't need any automation at all for it.

'Why should someone do such a weird thing?' you might
ask now, but that would miss the point.

With Tracktion you start to arrange and mix (and perhaps even compose)object orientated which means you don't think about tracks but instead about moments. E.g.: 'the background vox could nead for that single word here some mixture of distortion
delay and filtering' - suddenly you start to have
ideas which you wouldn't get with a track-orientated
sequencer because it would either be too complicated or impossible. (I wouldn't start automating three fx for the effect of a single word- maybe it's another three with another word) - I'm not doing experimental stuff but pop-orientated songs and I think it's
incredibly useful!

Although I had trouble following that example I most surely appreciate what you're getting at here.

Of course why allocate per clip - when you can allocate per event. (More for VSTi though). Muzys had that option and you could assign a player via the event list editor. This would mean that if you have a drum part for example and you decided you didn't want to use the same instrument for each part (kick, snare for example) you could change channel and even player information for those without having to separate over several tracks. I think it's probably more power than eXT needs though to be quite honest.

But the vst(fx in particular) allocation per midi clip would be a really good idea I reckon.

Caleb

[glurgle]

I'm not positive, but I thought tracktion behaved more like cubase does in that example... if you have a clip sliced in half, placing an fx on both slices requires 2 instances of said fx.

I think once we can drag tracks and clips to easily rearrange and copy, per clip VST(i) won't be as big a benefit to me. adding a new track and dragging it to a folder (or adding it directly to the folder...), then ctrl+dragging a sliced out word seems like the best solution to me. Yes it will be a minimum of 3 clicks to set it up, but it will be a lot more flexible/reusable than per clip effects and vsti's.

now, per clip MFX or midi-only VSTis on the other hand....

[Bunnyboy]

Hellos

I thought that would stick my oar in again

@ModuLR: there are some cool icons kicking around at XT-HQ and Multree has some superb ones as well.

@piranha XT: Thats what I use at the moment as a Midi FX in the seq or as the first VSTi in the chain.
However, it is a pain having to assign keys in Trollo and then in EXT as Midi notes.
It would be easier to have QWERTY and Midi seperate, then Ableton-style live performance methods can be created.

@plastique: One of the reasons for having it. Per-clip VSTs would do the same trick as well (I think.../hope...).
But - BUT!! - bypass buttons would be ace for live perfomances. You could add distortion to a section of a track, or create a big wall of sound that builds up by adding FX at stages.

And, gurge, yeah - MFX needs to happen!! I wanna play with all these cool toys