Jump to content

Recommended Posts

Just to follow up, my issue with Win 10 20H1 has been resolved.

I went back to Microsoft yesterday (7/16/21) and there was a new update to Win 10 with the word "critical" in it's name. (2021-07 KB5004237) I let the computer do its thing and it took about 20 minutes to install and reboot. I should have tested the DAW at that time to verify that the bug was fixed, but when I opened Cakewalk I saw Cbl had issued the new update (2021.6 Build 053) MSMCLEOD mentioned, and I installed that version right away. Everything works.

There's something MSMCLEOD mentioned about One Drive. I deliberately avoided activating One Drive on my DAW, and so my updates may have been uncoordinated when I was caught in the initial 20H1 Win 10 update just a day earlier. (I also noticed that in June, the previous update was labeled 20H2, which if memory servers, verifies that update versions and builds do not necessarily adhere to numerical order. 

Regardless, if you pay attention to the Win 10 update versions, 20H1 now seems to be cooperating with Cakewalk just fine, or vice versa.  

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites
7 hours ago, Milton Sica said:

Thank you very much.

Naming the recording and midi device ports works perfectly as they show correctly in the input box.

The problem even occurs with instrument inputs, as, according to Noel, the space for placing information.

In the previous version it appears in input 1+2, 3+4......

In the current version, even though the input is directed to stereo (1+2, 3+4,......) the information does not appear. This confuses.

I suggested putting a message with the total input indication when the mouse is over the input box.

The tooltip already shows the channel numbers.

image.png

  • Like 1

Share this post


Link to post
Share on other sites
7 hours ago, Noel Borthwick said:

@Hillmy upload the file to any file sharing service like google drive, onedrive or dropbox and send the link

OK. Uploading now and will PM you the link when it's done.

  • Thanks 1

Share this post


Link to post
Share on other sites
Posted (edited)

Oh boy.. Too many improvements and changes all at once, me thinks 🤯

I am now experiencing unexpected routing issues with 2021,06 build 053 ever since trying out the new "import" "export" integration with Bandlab Mix Editor. 

I have to manually re-enter serial numbers to reregister  SONAR ProChannel FX modules that I had purchased years ago.

Some 3rd party plugins from both Waves and iZotope  suddenly lose right side of channel start popping & clicking thru the left and locks up the DAW in playback. The only way to stop it is by "Ending Task" with Task Manager to close Cakewalk.

And the only way to stop it from happening again it to delete the 3rd party plugins and resign them in Cakewalk by Bandlab which requires re-adjusting and re-tweeking.

Or my favorite & simplest back up solution is.

Simply open the project in my trusty old SONAR Platinum and have a much better day.

And with all the new improvements and changes currently added to the new Bandlab v10 I'm scratching my head trying to learn HOW TO USE BANDLAB ALL OVER AGAIN! 😆

But I did figure out on important thing. DO NOT EXPORT TRACKS from CbB into Bandlab Mix Editor if you use multi output synth instruments. ONLY export "grouped" BUSS or "Stem" mixes.

For instance, I can have 3 to 8 tracks running in CbB for 1 guitar part by using the Nashville technique for double tracking as well adding AUX. tracks for parallel processing and group them all into 1 buss. Muted tracks get exported as well. I can easily have a 50 to 100 CbB track project for a 4 to 5 piece band sound.

Bandlab's Mix Editor doesn't have a Buss section so it can't tell the difference between CbB Channels & Busses so it imports EVERYTHING and that not only DOUBLES the OUTPUT to Bandlab's to the total sum of buss-less output the meter glows a solid bar of RED. And it adds up to so many tracks in Mix Editor nothing else can be added. 

I typically use an Alesis Sample Pad Pro as a handy table top MIDI  controller to record/sequence using Addictive Drums which outputs to 12 audio tracks in Cakewalk's "mixer" which I route to a stereo drums "buss". And that alone shows up in Bandlab's Mixer Editor "13 tracks".

And even though about 20+ tracks uploaded to Bandlab in my test project,  to the best of my knowledge Bandlab restricts the number of tracks for a 'collaboration' project to 16.

 

Edited by Steev

Share this post


Link to post
Share on other sites

2106.053 - i had to do a "repair" on my Waves install as they were showing up in the VST scan lists, but not in the Browser. and the VST3 substitute was hiding non-related VST2 plugins. prior to the repair, i re-installed the redistributables from Waves, then uninstalled CbB and reinstalled 053. still no joy. only running the "repair" (in Waves Central -> Settings) did the trick. now everything is running again.

so @Noel Borthwick there is definitely something going on in build 053 that was not going on in 050.

Share this post


Link to post
Share on other sites
2 hours ago, Glenn Stanton said:

2106.053 - i had to do a "repair" on my Waves install as they were showing up in the VST scan lists, but not in the Browser. and the VST3 substitute was hiding non-related VST2 plugins. prior to the repair, i re-installed the redistributables from Waves, then uninstalled CbB and reinstalled 053. still no joy. only running the "repair" (in Waves Central -> Settings) did the trick. now everything is running again.

so @Noel Borthwick there is definitely something going on in build 053 that was not going on in 050.

I don't think this would be anything related to 053. Why do you think these issues are related?
The symptoms look like a microsoft redistributables issue rather than an app issue. Nothing in the plugin handling of relevance has changed that would affect Waves in any way.

Share this post


Link to post
Share on other sites
On 7/15/2021 at 8:41 PM, Sam Stalos said:

2.  If you save an open .cwp file in Cakewalk , that file name will not appear as an option the next time you boot Cakewalk. That is, the file name will not appear in the Recent Projects menu of the Start Screen.

 

 

 

^^^Seeing this here, too.  I am able to use the Open menu to open the project but it's not in the quick start list.

Share this post


Link to post
Share on other sites

i would have thought so, but the 053 build installed updated redistributables (as far as i can tell) whereas 050 didn't have this issue. no worries though the Waves repair after installing 053 took care of it. 

Share this post


Link to post
Share on other sites

 

I had recently installed CbB 2106.053 on my skinny 'lil HP Folio 9470m Intel i5 gen 3 with only bare minimum 4 gigs of RAM laptop (crash test dummy) computer running an up to date Windows 10 Pro using Windows WDDM drivers with no 3rd party VST plugins and using only a wireless mouse as an add on controller I'm having no issues other then not knowing how to get or where the license key to the included copy of Melodyne is(?) That's not a big deal though, I was just curious what the limitations free version of Melodyne 5 can do. I already have Melodyne 5 Editor version on my workstation, and that costs as much as SONAR Platinum did I know the good peeps at Celemony aren't giving THAT away.🤪

 Anyway, CbB is very snappy with low enough latency to work with and performing much better and a lot more powerful then I would have ever thought it would on a quad core CPU without ASIO drivers👍 Using CbB's new import feature I was able to select and download a 9 track Bandlab project over my Netgear Nighthawk 5G WiFi network and was ready to mix in about 5 minutes. OK Nighthawk routers are FAST, but that the only high performance device we're talking about here. The poor old HP laptop doesn't even have an SSD installed, and CbB's performance really surprised me MUCH better & smoother then Presonus Studio ONE ever did👎🏻

But on my "Big Boy" AMD 8 core workstation with super low Focusrite ASIO latency with all the bells & whistles, as in the one where I actually WORK on serious music and video projects with DEADLINES and all,  it seems to be getting very unstable ever since trying out the new CbB and Bandlab integration features.🤔 And as much fun as I have on Bandlab, Bandlab doesn't pay very well, not that I'm complaining. I'm more like eternally grateful for not only keeping my favorite DAW alive, but CbB & Bandlab are SHOCKINGLY the closest thing we can get to a Pro Tools & AVID Cloud Storage account, and believe me, that is about 180° out of phase from being FREE as you can get.  And I'm not just comparing Cakewalk performance to the VERY expensive native Pro Tools 12 on a Mac ( I have both & CbB beats that to death), I'm comparing CbB's performance to BONE CHRUSHING expensive Pro Tools "HD" with about roughly 10x the cost of software & Apple hardware of a compatible Windows system!

And still, have issues just like we are having at present with CbB/Bandlab integration rear their ugly heads.

But I'm not jumping ship on either, and if I can convey the problems by explaining what I can see might be symptoms I'm having with CbB and it helps the that staff and CbB hopefully figure out nail the current problems, good, if not, well then have a good laugh, at least I tried. ☮

Bandlab is also scanning & recognizing MIDI controller devices on my computer that I use all the time to change patching and routing as part of my routine workflow that have lots to do with CbB and very little to do with Bandlab. And that's pretty scary because it automatic and there is no way to stop it from happening and turn it OFF or configure it to only recognize MIDI controllers useful to Bandlab.

I can't help to wonder if Bandlab is sending MIDI messages to try to communicate with 2 potentially dangerous MIDI controllers all at once to Cakewalk and a multi-channel audio interface when it will only receive audio signals from the 1st 2 channels and can't sync to the Focusrite to test and adjust for recording latency like it does with standard native Windows drivers.

My Behringer X-Touch is configured for Mackie MCU protocol as is configured to full control over audio tracks in Cakewalk and only the transport control section has limited but improper function in Mix Editor which doesn't seem support MCU, nor GM (general MIDI) at least not obviously.

 My Novation Impulse 61 is mapped to Cakewalk thru straight MIDI or Automap to control all MIDI channels, synths, and plugins along side of my X-Touch, and can be manually mapped to to control Bandlab's volume and pan controls and play Bandlab's MIDI instruments which works kinda well even though Mix Editor can't sync or adjust for recording latency due to the Focusrite's super low latency measures around 20-25 ms round trip from Bandlab instruments with low off peak local internet traffic.

Simply by opening Bandlab Mix Editor with CbB running, Mix Editor disconnects & zeros out and resets the X-Touch DAW controller and SEEMINLY tries to connect to it, but the X-Touch is set up to only respond to MCU protocol messages and ignores everything else.

But CbB, Novation Impulse 61 MIDI keyboard controller, and AUTOMAP software doesn't ignore MIDI messages & AUTOMAP try's to communicate & configure with everything MIDI and plugins listed in Windows x32 and x64 "Program Files" including Windows and Edge browser plugins, and probably any plugin that Bandlab GUI includes or uses, if any, and that's why I never select the it's MIDI port to use it until MIDI 2.0 devices are further developed & stable. But Mix Editor sees it and sees PropellerHead, Reason 11 Studio's new "Rack Extension" now runs as a VST 3 plugin in Cakewalk as a host & might try, and possibly AUTOMAP routing and patching Cakewalk's mixer thru Reason's SSL 4000 console mixer, and loop BACK AGAIN? 🤬💥

And the fact that Mix Editor recognizes & lists Novation's powerful & intelligent MIDI port "Automap" as a simple "Microsoft" device is not only troubling, it's kind of nerve wracking when it comes to thinking about tight integration between a DAW installed on my computer and a cloud based DAW on Bandlab's website at the same time I'm developing unusual patching config changes that I didn't make with CbB.

This is a screen shot of what Bandlab Mix Editor scans and opens for every time I open it. Only the "Impulse" which is a straight in USB MIDI port is useful. If I could shut the rest down I WOULD and maybe I wouldn't have any more routing problems in CbB?

 I donno. But I do know that I never had routing problems until I tried the new CbB Import/Export feature. Which is nice and very cool and all, but not for me.

204217120_BandlabreconizesMANYthings2021-07-18_11-39-37.thumb.jpg.910b234bdda04859ad056b8442cb0e91.jpg

Share this post


Link to post
Share on other sites
Posted (edited)

Don't know if this has been reported or not...

When using Process > Slide neither Arranger nor Track Automation is slid.

In 27.06.0.053 open project, hit Ctrl_A to select all tracks open Process / Slide...
 

2116804196_CW27_06.0.053Slideissues-before.thumb.jpg.0f2080ef3f92111477a530ee872860e2.jpg

428289382_CW27_06.0.053Slideissues-after.thumb.jpg.049265a1c399b3fab2b8da6506c18ed2.jpg

Edited by TheSteven
  • Confused 1

Share this post


Link to post
Share on other sites

Note on the above post - the automation tracks are modifying plugin parameters of FX in the track view FX  bin such as iZotope.

Share this post


Link to post
Share on other sites
On 7/17/2021 at 3:41 PM, Hillmy said:

OK. Uploading now and will PM you the link when it's done.

@Hillmy
Thanks for the dump file - I investigated it. It happens because the plugin doesn't complete its processing while you are changing presets and because cakewalk waits for it to finish processing it hangs. Its actually faulty multithreading on the plugin's part.

However the actual hang happens due to some thread safety changes we made for 06. I am fortunately able to work around the problem and have implemented a fix.
You should be able to prevent the issue for now by changing presets only when the engine is off.  (turn off the engine button on the transport when not playing) 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Rebooted tried Process / Slide again with only Cakewalk stuff ie. a MIDI track and & Audio track.

892093081_CW27_06.0.053Slideissues.thumb.jpg.99053dcef9b2073540b9f64b336d63ef.jpg
only automation track that slides in this example is the one directly linked to audio clip - Volume.

Project (unslide) is attached.

27.06.0.053 Process - Slide.cwb

Share this post


Link to post
Share on other sites
3 hours ago, Noel Borthwick said:

@Hillmy
Thanks for the dump file - I investigated it. It happens because the plugin doesn't complete its processing while you are changing presets and because cakewalk waits for it to finish processing it hangs. Its actually faulty multithreading on the plugin's part.

However the actual hang happens due to some thread safety changes we made for 06. I am fortunately able to work around the problem and have implemented a fix.
You should be able to prevent the issue for now by changing presets only when the engine is off.  (turn off the engine button on the transport when not playing) 

Awesome! Thanks for investigating and for the workaround. No hang or crash happens if I turn the audio engine off before changing presets. That's something I never thought of! :D

Looking forward to the fix. :)

Share this post


Link to post
Share on other sites
Posted (edited)

Cakewalk is having problem reading VST2 32bit plugins. It causes pops and clicks in all them.

At first I thought it was a  Bitbridge and Jbridge issue. Installed those - same problem. 

Are we fading those out? 

Edited by Will_Kaydo

Share this post


Link to post
Share on other sites

Loading VSTs is acting strange. It takes a while now after the latest update.  The spinning wheel icon now comes up on the screen and it acts like Cake is looking for the plugin!! It does load but nowhere near as quickly. Is anyone else having this behavior?

Share this post


Link to post
Share on other sites
17 minutes ago, Will_Kaydo said:

Cakewalk is having problem reading VST2 plugins. It causes pops and clicks in all them.

At first I thought it was a  Bitbridge and Jbridge issue. Installed those - same problem. 

Are we fading those out? 

32 bit ones you mean?  Synths or effects or both?  I can check a handful later but I've not seen (heard!) anything obvious.

Share this post


Link to post
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...