that the GUI continued to work responsively. by the time 3.1 debuts, ardour will use a configurable number of processors for DSP.
interesting. thanks for the info.
most workstations cannot import projects via OMF/AAF in a useful way. you cannot share automation data, and in a number of cases, you cannot share plugins. protools AAF files are not even in compliance with the AAF standard, so you can run into subtle breakage there. the de-facto standard for inter-workstation migration is to export each track as a stem BWF and import the result. it is true that ardour doesn't do a good enough job of making this a trivial operation.
most of the people i know work with omfs still. i suppose, to some extent, this has to do with your workflow, whether you’re doing music or film. i do post for film/video. in this context, things like the plugins and automation are less important than track structure and region positioning. i just need to get the structure transferred properly, which omf seems to do well. i get omf’s from avid or final cut, run them through proconvert (now from solid state logic) and get an edl my workstation can open. i’ve been looking into the bwf thing but it’s extremely limited in that your regions cannot be edited as they come in without handles.
the region-specific plugin thing seems to come from samplitude originally, and is not present in protools, which is still the dominant DAW within the industry. given that a ton of highly skilled audio engineers get along without it, it doesn't seem like a deeply compelling feature. its not hard to imagine a variant of region bounce that would do this in a static way. you could also start (or find an existing) sponsored feature request for this, and maybe someone will implement it.
from a post production useage point of view, the region level plugin thing is an extreme gain in efficiency. it’s far less cumbersome and, potentially saves a great many tracks. my standard template is for 96 stereo tracks. it would grow much larger if i had to move regions to specific tracks for the effects i wanted. seablade has offered a workaround involving automation of plugins but this, again, is more cumbersome than being able to manipulate the plugin discretely from within the region. it’s true that most people get by without this, but, it’s also true that it’s a far more efficient way to work.
this all reminds me a little of the vhs/betamax phenomenon of the past, yeah, one is better, but the other took over. nobody had a car at one time either. users repeatedly suffer under this pattern. think ms windows. if protools is the model, i’d think it would be better to look to what protools will be, rather than what it is. it took them forever to be able to work with stereo files. using a standardization logic, ardour should be a windows app. protools is an industrial standard, and industry is always slow and conservative with regard to innovation. does that description seem appropriate in an oss environment? we waited something like thirty years to get airbags in our cars in the us. there’s always a tension between standardization and innovation. when you’re writing your own ticket, as you are with ardour, do you aspire to be better or to the mediocrity of standardization, a pretty fluid notion in the computing world. obviously, there are arguments for both, time and funding, undoubtedly, being high on the list.
i’ve been watching ardour for a long time and this is the closest i’ve ever been to thinking i could really use it for my production. among the things i have to weigh, now, is its current functionality (how close is it to allowing me to make a clean switchover from my current work environment), how i deal with unanticipated issues (can i get my work out of ardour and into my old system if i find there are problems ardour can’t deal with yet), as well as the cost. while i would very much like to contribute now, i have to consider a looming upgrade of my current software. in that context, i look at the potential for ardour’s addressing of my issues. at the moment, it sounds like my $600 would buy me into an new environment of diminished efficiency with little interest in increasing that efficiency. unfortunately, this puts me in the position of thinking i should just keep watching and stick with my current system. this is frustrating as the main thrust of my current system’s development is into technologies i simply don’t use so my upgrade money goes to buy additional functionality for other users but none for me. still weighing this but, that’s how it looks from here.
if this sounds harsh, it’s not intended to be. ardour looks amazing, the more so given its oss status. i’ll look into region bounce as an option.