You are here

auto connect of dedicated outputs

Hey Rui!
When I create dedicated output for a plugin, on project load they automatically connect to output. I see no way to alter that behaviour. Am I missing smth or is there really nothing one can do in this case?

Forums: 
rncbc's picture

i'm afraid that is so true: dedicated audio output ports (eg. audio metronome, audio file player or MIDI instrument plugins) do connect automatically to the first available physical outputs (ie. soundcard speakers) when a session starts or gets loaded.

guess that a request for new global user option or preference is between the lines? :)

cheers

Not necessarily a global user option. Could be per dedicated output option. But I think it is necessary.

But tell me, is there any necessity in auto connecting it to output? Why would people typically use a dedicated output in your understanding? Maybe allow them to connect manually and Qtractor project will remember?

rncbc's picture

well, me likes having something that just makes noise ootb... :P

guess what? there's something coming out of the oven this very moment and... voilá: qtractor 0.5.0.55 (svn trunk) has all those user preferences set in place re. audio outputs auto-connection options. :) check that out from View/Options.../Audio, Playback, Metronome, and .../Plugins/Instruments.

also, an extra bonus has been hidden there for your pleasure: whenever you change the auto-connect option of an audio master bus it gets remembered thereafter :)

that's all to say that, from now on, you are free to turn off all those auto-connection mayhem you dislike so much. woohoo!

cheers

Haha!
Thanks, Rui, will check this out soon!

Hi Rui,

can we soon use loop recording or we most wait longer for this option,

i mean loop recording on one clip,

thanks and regard

rncbc's picture

yes, loop recording is the next hot topic in the TODO list.

the way i see it is about fold/unfolding any recording taken under a looping-cycle into takes.

in essence, takes are nothing else than sub-clips of the recorded file which is then folded into one or more overlapping takes.

when a recorded file is in its folded state, one has to select which take shall prevail on playback, over all the others which are to be hidden/muted over the same time range (ie. original loop range).

the current way of record-on-looping results in what i call the unfolded version of the recorded file.

alas, this is all still theory and what i'm missing most is some good UI idea for this take selection ;)

would you elaborate on what you're actually expecting with loop recording in qtractor? that might help in shortening the wait ;)

cheers

loop recording:

it most be possible to record for example:

first loop cycle record :
some notes

and loop recording continues while you still hear the first recorded notes, then you play some notes on the next cycles and the notes will be recorded to the same clip as the first recorded notes.

this most be also possible on piano roll view:

first you record some notes in loop and when you record notes on next cycles you most see the notes that are recorded.

thanks

rncbc's picture

it turns out what you're asking is not quite loop-recording as i know it but the possibility to overdub looping or not.

those are two distinct concepts. in my pov.

in qtractor parlance, overdubbing is actually accomplished by recording new clips on top of other existing ones, while on the same track.

you cannot record a signal (audio) nor new events (midi) into an already existing clip. sorry. instead, you can overlap and merge those clips (clip merger is optional).

recording midi events directly into an existing midi clip, while in the piano-roll (aka. midi clip editor) has been tried here before but unfortunately it's still failing to get a minimal satisfactory implementation. mainly because it's a pita. to get that undo/redo-able with all the confidence and reliability it deserves. still, i'll retry and get it through again, one of these days. no promises, though ;)

cheers

Add new comment