Jump to content

Xoo

Members
  • Posts

    5,321
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Xoo

  1. Blue Oyster Cult - Lips In The Hills
  2. Dave Brock and the Agents of Chaos - Heads
  3. Dave Dee, Dozy, Beaky, Mick and Tich
  4. Someone had to... Bing Crosby - White Christmas
  5. Nik Kershaw - I Won't Let The Sun Go Down On Me
  6. Sounds like you have Ripple Edit accidentally enabled.
  7. Never seen that with any version of a Cakewalk DAW.
  8. #2 is standard Windows behaviour (try moving a bunch of files in Explorer for instance) so is probably hard to change and also probably not something that *should* be changed as it's then non-standard behaviour.
  9. You don't - you route Windows Audio to loopback to Sonar input to Sonar output to hardware. Windows audio doesn't come into effect after the first step. If you do want to do this, I'd look at a lightweight VST host like Blue Cat Patchwork. Or I'd just load the audio into a dummy project in Sonar and listen to it there. It seems like a lot of effort if you need to run Sonar/Patchwork alongside media player (assuming you can't find a media player that hosts VSTs, and I'm sure one exists).
  10. Maybe some ideas here: https://gearspace.com/board/music-computers/1261800-audio-players-can-run-vst.html
  11. 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!
×
×
  • Create New...