Tenfoot

Ah! There it is indeed. Thanks again Azslow.

Hey Bass Guitar. Thanks for the input. As Azslow mentioned, VB matrix is a far cry from the software you are comparing it to. Utilising it I am able to route any audio on my system (DAW's, DaVinci Resolve, standalone processors and instruments, etc) directly through the monitor bus of Reaper and send it to any of the 4 pairs of Monitors plus a sub and mono Avantone or 4 headphone mixes in my studio, as well as toggle VST room analysis software inserts independently for each of those sends and switch between crossover points for the sub channel should I wish to use in combination with any of my Monitors. By also utilising Bome Midi Translator, I am able to do this by pushing the button of my choice on a Stream Deck, irrespective of the software I am using. I use this system 8 hours every day, and up until now it has performed flawlessly in every DAW except Sonar. Now, thanks to Azlows help, it is working flawlessly there too. I am pretty sure I have the right hardware:)

Hey azslow. Inspired by your success I have dug a little deeper. My studio is on its own local offline network, and I only go online to update when necessary. I was an update behind on Sonar, and the latest release has indeed solved the issue! Whatever it was has been addressed by Cakewalk. I should have checked that first, but as I mentioned I don't use Cakewalk that often and had given up hope. Thanks so much for testing Coconut for me. You are a legend! Kindest regards, Bruce.

Hey Azslow3. Thanks for the detailed response! I have used Sonar for a very long time and am also very familiar with how VB Audio Matrix works. I do use the Coconut variety, as it seems does everyone in the other thread reporting issues, including a Cakewalk staff member who concluded that using a driver other than ASIO was the solution, so Coconut may be the problem. Since you had gone to so much trouble to respond and I know you have a lot of experience and knowledge with windows audio, I did return to my studio to give your suggestions a try. Here is what happened: 1. VB Audio Matrix is set up with my RME Fireface as clock master, and all virtual devices set to slave to it with the same sample rate. This is how I have always run it. 2. Sonar was set up and running with Audio Matrix with its driver mode set to shared WASAPI utilising one of VB matrix VAIO devices without any issues. 3. All other audio software was set up and able to run using VB Matrix virtual ASIO devices. 4. With only Sonar and VB Audio Matrix running, I set a new virtual ASIO device active in DB Audio Matrix. I then went to Sonars settings, and changed the driver mode from WASAPI to ASIO. As soon as I did this, Sonar began to scan the available devices and immediately crashed. Once this happens, Sonar can't be re-opened. It gets as far as the splash screen then closes. This is the behaviour I described in my first post that you mentioned you didn't understand my statement. I have been down the uninstall/re-install/delete AUD.ini path many times trouble shooting this issue. Again tonight, only uninstalling VB Audio Matrix allowed Sonar to open again, upon which it defaulted to the RME ASIO drivers. If I don't change the driver mode in Sonar to something other than ASIO before reinstalling VB Audio Matrix, Sonar will again not get past the splash screen after. I use Macrium Reflect to restore my system to a optimal condition so do not mind experimenting. I think I have tried most everything!It seems the issue lies between VB Audio Matrix Coconut and Sonar. I have reproduced this issue on 2 other computers as well, all running Windows 11. Sonar is no longer my main DAW, and I only have to use it on the rare occasion that a client has started a project and I need to port that project to Reaper, Studio One or Cubase, so I can get by with WASAPI drivers. It would be nice to have ASIO back though:) You mentioned that you can't expect low latency with DB Matrix. On the contrary, I run my whole studio through DB Matrix with a safe general setting of 128smp with zero issues outside of Cakewalk. It seems the problem lies somewhere between Sonar and VB Coconut. It is surprising, as I have found both to be very stable otherwise. Thanks again for chiming in! Kind regards, Bruce.

I thought I would start a new thread for this as the old one is marked as solved, and it really isn't. This is a continuing issue with Sonar. As described in the older thread it crashes upon attempted opening once any ASIO device is selected in VB audio matrix as Sonars device. The only way to restore functionality is to uninstall VB matrix. Simply deleting aud.ini does not work. Using wasapi shared in Sonar and VB matrix works fine. Strange and disappointing, as I also use Reaper, Cubase and Studio One, all of which work perfectly well with VB matrix ASIO virtual devices. If anyone has found a solution I would love to hear:)

This is a continuing issue with Sonar. As described above it crashes upon attempted opening once any ASIO device is selected in VB audio matrix as Sonars device. The only way to restore functionality is to uninstall VB matrix. Simply deleting aud.ini does not work. Using wasapi shared in Sonar and VB matrix works fine. Strange and disappointing, as I also use Reaper, Cubase and Studio One, all of which work perfectly well with VB matrix ASIO virtual devices.

A bit of a trip down memory lane with some of these posts! I used Cakewalk products from the 12 tone days, only jumping ship with the demise of Sonar Mk1 at the hands of Gibson. Great to see that Noel is still at the helm! It will certainly be interesting to see where cakewalk goes now. Whilst I am old school and no fan of subscription models like Adobe, Sonars previous model (with the possible exception of the 11th hour lifetime subscription :) was very fair. You really subscribed to the updates, not the program. All the best to the Cakewalk team and now apparently immense user base for the future. Sonar rides again!

Hey Harddrive. I used Cakewalk for live performance with DMXIS for many years. The best way to use DMXIS is as a standalone application running alongside Cakewalk rather than as a vst insert, and then trigger your scene changes via midi notes from Cakewalk using virtual software midi cable such as loopbe (which is free for a single 'cable' version). That way DMXIS only needs to load once, and all of your scenes stay in ram rather than having to load with every song. It also solves the problem of blackouts between songs should it arise. The programming process is the same. Just store your scenes. The only difference is how they are triggered. It is rock solid. With regards to your other issues, I had a similar problem with songs showing as 'dirty' with the asterix appearing upon loading into a setlist. It turned out to be a particular plugin causing it. Regardless, I believe there is an option in Cakewalk now to tell it to ignore any 'changes' if the song is loaded via a playlist. This should solve your problem. Your audio outputs are indeed stored with your Cakewalk song when it is saved as a .cwp. They should be correct as long as your hardware does not change. Unfortunately some drivers/interfaces will show up as different outputs when an external interface is unplugged and then reconnected. Have you tried ASIO drivers with your setup to see if they are more consistent? Another thing you can do is to save all of your songs with the outputs assigned and your interface connected, then backup your configuration files. That way if you have any issues in the future you can quickly restore them. The files are AUD.ini, ctlrsurface.dat, INSTRMAP.INI, Master.ins and TTSEQ.INI. Not all of these apply to your audio i/o, but they are small files and backing up all of them saves your entire daw configuration. Last time I used Cakewalk (win 10) they were located at C:\Users\"user name"\Appdata\Roaming\Cakewalk\(your version). Hopefully they still are

Great news mate! Well done:)

Hey @Ron Harrell . When you select Lyrics view as Chuck described above, it will by default open in the multidock. Be aware that lyric view is track selection dependent. You need to make sure you have the track selected that contains the notes that will trigger the lyrics as the song plays - a single midi note for each word. Heres the process I use: 1. Write your song lyrics in a text file 2. Create an empty midi track. This will be used to trigger your lyrics. It does not matter what instrument it is assigned to (if any) as it will be muted. It does not matter what notes you play. Just the timing is used to scroll through the lyrics. 3. Record enable the track and start recording, and as the song plays, play a midi note for each word (exactly as they are written in your text file). Once done, this track can be muted. 4. With the midi track you just recorded selected, choose Views> Lyric View. A window filled with dashes (one for each note you played) will appear in the multi dock. Drag its tab out of the multidock so that the window is free floating. 5. Select all of the lyrics in your text document and copy them (Ctl>C) 6. Now select all of the dashes in your lyric view window and paste the lyrics in (Ctl>V). The dashes will be replaced with your lyrics. 7. Play back the song back and make sure that the highlighted lyrics are in time with your backing. You can now set the font and resize the window to suit your screen layout. You can have a larger font and smaller window, as the lyrics will be highlighted and scroll with the song on playback. I generally like to have 4 lines visible the full width of the screen, but this is entirely up to you. Arrange all of the project windows as you would like them to appear upon opening. MAKE SURE THAT YOUR LYRIC TRACK IS SELECTED. Lock the current screenset, then save the song. Hope that helps:)

Hey @noynekker. Where did you read those release notes? The changelog on Celemony's website is actually for version 4.2, which did include fixes for both Cakewalk and Studio one. I just want to check it is worthwhile before messing with Melodyne:)

If you want to run Cakewalk with stability on a Mac your only real option is Windows OS via Bootcamp.

I believe the latest update is to ensure compatability with the latest Mac OS. Probably not hugely interesting to most Cakewalk users:)

Kids who aren't pushed yet want to do well, understand scienctific concensus, care about the planet and aren't afraid to speak up. Sounds like you and your wife could teach many others a lesson or two Ed. Awesome job:)

It certainly does @Noel Borthwick. It could be my imagination, but projects seem to be loading much faster too rendering the pre-load unnecessary. The end result is that there is no glitching and zero waiting between songs. Projects with 40+ audio tracks, fx and midi control data are loading in 1 to 2 seconds! The first project in any list loads a little slower, but that has always been the case and is obviously not an issue. The discard changes works perfectly too. The playlist is back in action my friend! Drum replacer is also working like a charm. Thanks Noel - awesome job!

Drum replacer fixed AND improvents to the play list! Sensational work @Noel Borthwick

I had problems with drum replacer yesterday too. It's transient detection would only work sporadically, and when it did moving around the project would cause any tracks utilising drum replacer to play out of time. Its a hot mess:)

Addressed this in your other thread Ron. Works on my win 10 system with CbB. Hope it helps.

It is possible to create a lense to override window placement. It works most of the time:) I have found the above method to be the only one that works perfectly every time.

If the Lyric View is docked in the multidock, simply right click on the 'Lyrics' tab in the multidock and choose 'undock'. You can then drag the lyric window to wherever you wish to place it. It will always be the top window. Check that you have no active lenses (Top right of main screen>Lenses>None). Also check that the screenset you are using is not locked (Views>Screensets>Lock/unlock current screenset). Now save the project. From then on, whenever you open that project, the lyric view will be the top window located where you placed it prior to saving. If the window placement is correct and you wish to make it permanent, simply lock the screenset (Views>Screensets>Lock/unlock current screenset) then resave the project. That way, even if you change the window layout whilst editing, the lyric view will always be restored to its rightful place on re-opening the project. (NB. The only window that can block the floating lyric view window is the Playlist window, so if using that feature make sure when organising your project windows that you leave space wherever you choose to locate your playlist)

If I'm not mistaken we have discussed this before and been waiting a while for this one @craigr68 Feels like Christmas:)

I was just editing my post to include the pause as well as the wait for keystroke as you posted! Take a look. I think it would work exactly as we both need:)

The suggestion I made would mean that the project would be loading in the delay/wait for keypress craigr68, but Noel's suggestion would solve our problem too. The Ioading syntax would work the same as it does now, but not wait for the keypress/end of delay to commence loading the upcoming project, so it would be loading in the pause as you suggest. As the playlist completed project A, it would close that project and immediately load project C, THEN wait for the keypress/end of pause to start playback of project B. If this were the case and nothing else changed, at worst we would need to load a dummy project at the start of the playlist to avoid a single instance of song loading whilst playback was taking place detween project A and B, though hopefully this would be addressed too.

The "family PC" could indeed introduce a level of chaos I had not considered Kev:)

Give it a try though greenlight. This issue does not occur with every audio interface. There is zero load time in it's absence as the next project loads whilst the current one is playing.