Hello,
I have been tinkering around preferences(View->Options), so it has been strange for me to see "Dedicated Audio Outputs" (In Plugins tab and Instrument Section, screenshot below)
Because it will cause problems while exporting MIDI to Audio file Explained here
So i don't think of any use with it(in turn it's causing confusion especially among new users like me and also irritation among advanced users because of problem with MIDI to audio export if it's enabled accidentally)
Although not enabled by default(But there will always be a tinkerer inside humans to mess up with....)
What will be ur explaination about it rncbc..???
two beers cheers ;)
Attachment | Size |
---|---|
screen-1.png | 44.32 KB |
re. Use of Dedicated Audio Outputs
lets start by telling you that qtractor is an hybrid, regarding the modular vs. monlyth debate.
a. it plays the good guy/gal role on the modular scene; that's where those dedicated thingies comes around;
b. it looks and feels like a monolyth though, but isn't (it is NOT) at all, at least in its totalitarian sense. scnr.
since the JACK advent, the so called modular model has been a vision in the linux-audio world... to make up a long story short, the holy graal quest ever since then was about having a standard session management protocol and specification, as one consistent glue for all disparate modules that were popping and booming around (read alsa, jack clients and applications);
there was LADCCA in the beginning, then nèe LASH; but adoption never fly above the drawing desk; then LADISH, with many detractors and the same amount of adopters, nevertheless, however it was tied to some specific or esotheric infrastructure (eg. jackdbus, etc.) which wasn't there available in all cases; now, over the last couple of years, NSM has been an advocated, meself included, solution for this whole modular conundrum, if one may say such a thing....
meanwhile, during all that time that spanned across the whole last decade, by people and no doubt by alien(ated) capitalistic demand, plugins were all the rage: linux native VST come first then later the incredible complication of LV2 GUI plugins that joined and added to the monolythical model--yes, plugins, beside its deceiving name and the eye candy attractive galore, are The cornerstone of the great monolythical concept, started by steinberg (as in VST): one application (the DAW-application, eg. Cubase) is the center and to rule it all; once you make the coice of your DAW-application, you're doomed and locked-in--some might say that, the DAW(as an application program) is the new OS. whatever.
i just don't buy this world view. sorry.
however, i've been seen (a lot more than i ever wished) to condescend about the so called plugin craze, so sorry for that. mea culpa. at best, no worry, no hurry, chicken curry ;)
hyu.
cheers
So what will be ur comment
So what will be ur comment about non-timeline, non-mixer, non-sequencer(NSM is already commented)..if someone(me in this case) asked u about them...??
cheers(hats off for ur newly invented english, had to search google for meaning of the words u used......ha hah hhh)... ;)
re. So what will be ur comment
So what will be ur comment about non-timeline, non-mixer, non-sequencer
all the non-stuff, like NSM, follows the modular approach in the most pure and straight fashion--no comments about that:)
byee
Add new comment