But Paul, you know that I'm the only user that matters. 😉
Your argument to have the bus as a default is very much from the, "my son is the only kid in the marching band in-step!" playbook...
Name me a single application that pre-loads actual content into a new, default document (not loading a template, but a NEW document) that requires a dialog box visit if you want to open a file over it? You can't do that!
Additionally, WHO SAYS that using a bus is a desired default routing method? I can name you a dozen perfectly great workflows, and ALL of them are "good" and "correct". And 11 of these workflows do not use a default bus. Especially routed to outputs 1-2. I would imagine that your VE Pro customers already use a professional host such as Cubase or Protools or Logic and we are all smart enough to make a channel and assign an output.
ESPECIALLY NOW since you've done a superb job updating the VE Pro and VI Pro documentation. It's quite comprehensive now, and there is little justification to pre-load content of any kind. The user will RTFM and instantly know to add whatever their needs require. You have made a killer product with lots of flexibility and more than one way to get there.
IMAGINE if you pre-loaded a preset or matrix or patch into a VI - you would never do that! Please, take this all the way and remove all default content. It really doesn't belong.
FINALLY -- since many users will ultimately make their own default viframes and metaframes anyway, make it easy for us to load our saved default files without the extra step EVERY time.
Thanks for listening.
VE Pro Users, please CLICK HERE for a SURVEY !!!!