[LAU] [ANN] Qtractor 0.5.1 - The Bravo Yankee return!

[Hartmut Noack]

Am 05.10.2011 18:40, schrieb Rui Nuno Capela:
> On 10/05/2011 11:36 AM, Renato wrote:
>> On Wed, 05 Oct 2011 09:09:43 +0100
>> Rui Nuno Capela<rncbc at rncbc.org> wrote:
>>
>>> Qtractor 0.5.1 (bravo yankee) is out!
>>
>> what exactly do these two mean?
>>
>>> * Linked (aka. ref-counted) audio/MIDI clips (NEW)
>
> previously on qtractor, each clip had a complete independent data object
> (buffer) from each other. now the clip data buffer is shared for all
> clips in a track that refer to the same filename, offset and length.
>
> for audio clips this can be a huge resource optimization. for midi clips
> it also means that editing or changing events on one of the "linked"
> clips will also affect all the others that refer to the same midi
> sequence (ie. same midi file, channel, offset and length, of course).
>
> in practice, it means that all copy&paste-repeated clips will refer to
> very same internal data buffer/sequence. you change one, you'll change
> all. got that?

Nice nice and useful too but then again.... what if I copy/paste a 
drum-clip and want to add a crash-hit to it whithout having that crash 
on every clip the copy has derived from? Is there some option such as 
"right-klick/make new individual clip from copy"?

>
>
>>> * MIDI-fx plugin support (NEW)
>
> midi-fx plugins are that special kind that takes midi processing
> exclusively. they take midi input, eventually transform it and throw the
> result as midi output for consumption by the next plugin in chain, which
> might be another midi-fx or ultimately a midi-instrument one (often a
> synth plugin). there's no audio signal involved. only midi going in,
> thru and out. eg. pizmidi plugin collection (vst). cf. audio-fx plugins,
> where audio is the only processing subject (eg. ladspa)
>
>
>> can't wait to play with the new toys!
>>
>> and happy birthday of course,

++

:-)

>
> thanks