Jump to content

Chris Boshuizen

  • Content Count

  • Joined

  • Last visited

Community Reputation

12 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Noel Borthwick, any updates? I'm about to head off to a songwriting camp and won't have access to my studio for a few days.
  2. I forgot to list the plugins. For Drive, the non-native plugins are: Izotope Neutron. Image Line Delay TAL Reverb II Soundtoys FilterFreak1, Sie-Q Nicky Romero Kickstart Sleepy-Time DSP Lisp (Desser) For Voyager: Neutron
  3. Awesome, I'll be at Namm with GHS Strings, looking forward to saying hi again Noel. I have two for you, both released 2019: Voyager at the Heliopause Ambient instrumental, with lyrics in morse code. Here's a music video with 3D animation I did - all of which are scientifically accurate recreations of Voyager's journey through the solar system. Drive Synth heavy dance track with vocals.
  4. I have a brand new Presonus studio 68c. I often use the FL Asio driver that ships with FL studio because it allows driver sharing. Potentially a smoking gun... I'll double check with the Presonus driver. I used to have a Mackie Onyx Blackjack, and it behaved the same, as does the Reatek soundcard in my laptop. But, I suspect again, possibly when using the FL driver. I haven't used ASIO4ALL in a while, as it offered no advantages over the OEM driver or FL Asio.
  5. Yeah, from my experiment it seems that the melodyne timing offset moves far from the actual clip until you hit stop and start again.
  6. Here's an example. As you can see in the vid, every time I click on the timeline the melodyne playback point gets pushed to the left. https://photos.app.goo.gl/G6EhXjTiFpGgTyWa9 I'd say this is a pretty major bug - it renders the app nearly unusable when editing or comping.
  7. For several years Sonar and Cakewalk emit an intermittent squeal when starting playback instead of playing audio. It sounds like it is just playing a microscopic loop of the audio at a high frequency. It's not completely predictable, but sometimes it seems to do it 1/3 times. I recorded a video of it here: https://photos.app.goo.gl/qtoezBihAzGYwHkP7 Sorry for the aggressive space bar slapping.
  8. Correct! So the takes end up looking like this: Take 8 ========================== Take 7 ========================== Take 5 ========================== Take 9 === Take 4 ================ Take 3 ===== Take 6 =============== Take 2 ========================== Take 1 ========================== This is a specific feature that was added and announced in one of the Sonar monthly releases 2 or so years ago. This causes me a lot of problems, becausen my mind, Take 9 is an improved version of Take 8, so it should logically sit nearby. Sometimes, in big projects, I can't even find the newest take! Comping can become a real nightmare. I would really prefer them to look like this, like it used to: Take 9 === Take 8 ========================== Take 7 ========================== Take 6 ================ Take 5 ========================== Take 4 ================= Take 3 ===== Take 2 =========================== Take 1 ========================= Thanks for reading!
  9. Thanks, what a wonderful update! This is already making my life easier! Can we add an option to disable lane-reusing on recording? For large numbers of takes this feature makes keeping track the good ones very hard because they are all disjointed and out of order.
  10. I have noticed that if I jump around the song during playback, Melodyne region effects start playing from random locations, dropping completely out of sync (dozens of bars off) with the rest of the project. This happens with clicking in the timeline, jumping to markers, or pretty much any other method of scrubbing. This has been an issue for as long as I can remember - back several versions of Sonar through the current Cakewalk build. Next time it happens I'll record a video and upload it here.
  • Create New...