NealClark

I do understand that. However Dimension Pro is a Cakewalk product so they should be fully aware of what the plugin is doing. It's all a tad confusing as I said, it was working, but now on the latest CbB release it's a bit like I feel I am taking a chance inserting certain plugins. Crashes aren't consistent with any particular scenario other than the one I mentioned in my original post. As a further test I have tried the plugins in an alternate DAW on the same PC and they do not crash.

A Cakewalk project will hold a reference to the exact location of the video file. For Example "C:\my videos\video1.mov" if that file is not in the exact same location it will obviously fail to locate it. It will still however show the file name of where it "thought" the file was from when the project was last saved.

You are getting confused by trying to "Save" your project as an MP3. This is not the method. You should go to File > Export Audio where you will be presented with the option to save in various formats, including mp3. Then as scook described you will see the bitrate options etc and be able to select the 320kbps you require.

Thanks for the reply. I have opened a case with Cakewalk support. After examining the dmp file they tell me that the issue when using BBC SO Discovery is caused by the plugin and I should therefore contact Spitfire regarding this. I then realised I also had the issues with Dimension Pro that I explained in my original post. I have again supplied the Dmp file to support and am yet to hear back from them Seems slightly confusing to me that the answer from Cakewalk is that it is a plugin issue. I could understand that if it was just one plugin, but it's not it's several of them. My system is based around an i7 CPU, 16GB RAM, GTX-1060 6GB GPU, SSD Drives. I have a brand new Focusrite Saffire 18i8. I am running Windows 10 Version 2004 all fully patched and up to the latest release as are all the drivers. Using 24bit / 48Khz. Buffer size = 256, ASIO. I am an experienced Cakewalk user. From version 8, 8.5, X1, X2, X3 and SPlat. I wasn't having the issue I described with Dim Pro until recently. The BBC SO was only a recent addition to the system so I don't have any history with that. Dim Pro however has always worked just fine for me, for years and years, so it's odd to suddenly start getting errors with it. It's also not a consistent error. Adding it into an existing project as a new instrument track may or may not cause the error, it's very random in its behaviour. By doing exactly as I described in my original post it happens 100% of the time, the same with the BBC SO VST3. It's odd to say the least and getting in the way of me getting on with some video scoring projects I am working on. Incidentally I tried it on my old Windows 7, on the same PC, where I also have a SONAR X3e Producer x64 installed. Everything seems to be working fine. I aslo have CbB on that install, and I know CbB isn't supported on Win 7 any more, but it exhibits the same crashes as the Windows 10 install. So it would seem that it is not directly OS related. Hopefully I can find a solution or work around soon. I appreciate your help. Thanks,

Just a couple of questions to try and understand the issue. When you say, some tracks wont export at all, do you mean that they export as silent tracks or don't actually create the expected file. When exporting tracks do you have them all selected ? CTRL-A to select everything ?

I have been experiencing quite a number of crashes when inserting Instrument tracks. A quick example is I open Cakewalk, from the start screen I create a new empty project, add an instrument track, in this case Dimension Pro (x64), with my Cakewalk by Roland A-500 Pro as the midi input, then select the first instrument in the guitars section, as soon as start to play I get the first few notes and then it crashes with this error message. This has happened with a number of plugins now. BBC SO Discovery VST3, Kontakt and Dim Pro are just a few that I have had this issue with. It's only recently that I have experienced this so I am wondering if it part of the latest release that has caused the problem. I have also get the exact same error within Sonar Platinum which was working fine with these instruments until recently. If anyone has any ideas I would appreciate any feedback.

I use a Behringer X-Touch as my control surface and have it set to Mackie Control, this works perfectly, and not as you have Mackie Control XT. There are also option within the X32 itself to set the control protocol that will be used. Details of how to change these can be found on page 55 of the user manual. Hope that helps.

There is information on using Bandlab and Cakewalk here:- https://help.cakewalk.com/hc/en-us/articles/360022218453-Integration-between-BandLab-and-Cakewalk- As far as I know there are no dedicated Bandlab forums.

I could, but that still wouldnt solve the issue with being able to run the existing 64 Bit plugins. I was hoping that someone would be able to say "ah, yes, Cakewalk updated BitBridge on such and such a date, the older version worked fine." What I might do is Install a fresh version of X3e onto a Laptop and compare the versions of the BitBridge.exe and BitBridge.dll files and see if anything has changed. That might at least point me to a possible solution. It could be that MS have also changed something in their C++ libraries that is causing the issue. It's an annoying place to be though. Best of luck getting your old projects migrated. It sure is a lot of work to redo everything with new plugins. I guess like me you have spent a huge amount of time already on the older projects and to have to go over them again is quite a task. Thanks for your input.

I did mention the issues. "terrible audio breakup, crackling and stuttering" when using the 32 bit plugins. I don't have a 32 bit install of X3 on there, only a 64 bit. The only 32 bit install I have is X1. As I mentioned the issue with using a 32 bit version of the software is that other 64 bit plugins that were also used in the projects wont be available. I guess using the hybrid combination of 32 bit and 64 bit plugins wasn't the best idea, but it was what was available at the time. One reason for migrating the projects over is to take some of these projects and migrate them to 64 bit CbB on Windows 10 where I have a load of new VST's and Guitar Amp modelling that I would like to try with the projects. There are many things done with the older 32 bit plugins that would take an horrendous amount of work to reproduce in the migrated files. One thing I have noticed that is if I freeze the tracks that contain the 32 bit plugins they render in place and play, using those 32 bit plugin effects, without any issues. It's only when I preview them in "real-time" that I have the issues. To eliminate any possibility that it is latency related I have adjusted the number of samples up and down on my ASIO audio device (Focusrite Saffire 18i8) but this made no difference at all. After many hours of investigation am pretty much convinced that it is BitBridge related in some way. As I said before all of these plugins worked perfectly in Sonar X3e 64 bit at one point.

I am experiencing some issues that appear to be Bitbridge related that I wondered if anyone can offer advice on. The situation and brief history are as follows:- I have a PC setup that has the ability, via two boot drives, that allows me to boot into either Windows 7 x64 or Windows 10. On the Windows 7 install I have all my original Sonar installs, from version 8 through to X3e Producer. In this Windows 7 system I have a huge number of "projects" that have been lingering around for many years and over time I have been migrating them where possible over to the Windows 10 install and it's associated X3e, SPlat and CbB installs. However I have a number of projects where I have used 32 bit plugins that I am now having issues with. The majority of these projects were last edited in Sonar X3e Producer where those 32 bit plugins worked just fine and I can't ever remember experiencing any issues using them. So as part of the plan to migrate these projects over to Windows 10 I installed CbB onto this Windows 7 install. This was prior to the release where it was stated that CbB was no longer supported on Windows 7. Now when I try to run any of the projects that use the 32bit plugins and BitBridge within Sonar X3 I get terrible audio breakup, crackling and stuttering. The version of BitBridge that is installed has a date on it of 2015 which would be after the release of my installed X3e Producer. So my main question is "were there previous version of BitBridge prior to that date that differed in any way?". Obviously whatever I had prior to the CbB install worked just fine. I am kind of stuck being able to do some final edits on these projects. My whole back catalogue of music written over many years are contained within these projects. I don't really want to be purchasing newer versions of these older plugins in order to be 64 bit compatible. Also many of them are no longer available but were pretty much cutting edge at the time. I have found a work around for some things in that I have both a 32 and 64 bit install of Sonar X1. If I open the projects in there I can obviously use all of these plugins without issue, as BitBridge isn't required, but I then have the problem that any 64 bit plugins and VST's don't work or show up. Any help with suggestions would be appreciated. If it's worth me going back to a previously installed version of BItBridge, that's if there was such a thing, and it is any different and also where that version would be contained in the original install files. I know that there is always the option to install JBridge but I have read many differing reports about the relative success of using that. So am not really keen to spend any further monies to get around a problem that at one point didn't exist in my X3 Install. Look forward to reading and suggestions all you Sonar / Cakewalk gurus may have. Cheers Neal.