Jump to content

Improved collaboration/migration capability


Xoo

Recommended Posts

I regularly move between using my MOTU under ASIO and internal (HDMI) using WASAPI Shared, and re-saving files messes up input and output mappings (the HDMI has no input, so any track input setting is set to None on opening a project in WASAPI mode and saved as None too).  In addition, if people move between desktop and laptop, say, when travelling, or share projects with others who (very likely) have different I/O settings, the current situation leads to confusion and likely incorrect routing.

I would suggest some changes to how Sonar handles saving and restoring I/O settings in a project file to support these use case: rather than just storing what appears to be in index into the input or output list when a track or bus is pointed at a physical input or output, an index into <Driver Mode, Device> needs to be used and stored - and not lost when Driver Mode or Device are changed - so that project movement across hardware changes is as seamless as possible.

Or other suggestions anyone might have!

  • Great Idea 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...