Jean Corivo

I upgraded my computer from Windows 10 to Windows 11. Generally speaking, the switchover went smoothly, but there seems to be a problem with the UWP MIDI mode on Cakewalk.

Some MIDI messages are no longer getting through, including "Machine Control" messages. I'm using the VS-700C: I receive all status messages on the VS-700C, but I can't send any to Cakewalk, i.e. one-way communication. However, the control surface is well configured. I can only use MME mode.

With Windows 10 I didn't have this problem.

Perhaps it's Microsoft's rapid abandonment of UWP mode towards "Project Reunion" that's the cause, but obviously for many users it seems that using MIDI UWP mode is problematic.

Hi @Noel Borthwick

I installed Cakewalk 2021.09 Update 1 and I'm having the same stuttering problems as with Cakewalk 2021.09 when I use the oversampling feature

In fact, the problem seemed to have disappeared with Cakewalk 2021.09 Update 1 Early Access, but with the latest update I'm getting the same stutter problem...

I have tried several synthesizer plugins from different companies and even Cakewalk's own such as Rapture Pro and the problem is recurring. The only way around it is to install Cakewalk 2021.06 (build 58) or Cakewalk 2021.09 Update 1 Early Access...

21 hours ago, Noel Borthwick said:

We're pleased to announce Early Access for Update 1 of 2021.09! This release includes a small handful of user reported stability issues.

If you have encountered any of these issues, please check out this release and and confirm that your issue is resolved before we release the official public version. 

Please note that Early Access installers are update installers, which only update from a specific version. To install the 2021.09 Update 1 Early Access build, you must be on the latest public release of 2021.09. 

Download Cakewalk 2021.09 Update 1 EA installer

If you haven't already done so, please read about the Early Access Program before participating.
Please keep responses specific to problems or comments on this release. Unrelated bugs or feature requests should be posted in other threads or the feature request channel.

Thanks again for your participation!
The Bakers

Issues Resolved in Build 143:

• Bounce to track dialog forces render sample rate to 44100 always
• Export audio dialog uses default project sample rate instead of actual project sample rate
• Bounce to Tracks should always use project sample rate to prevent unnecessary sample rate conversion
• Large bounce buffer sizes cause flatline audio when exporting or bouncing clips with 96K or higher sample rates
• Bounce to clips unexpectedly uses bounce buffer size from export audio dialog
• Exporting audio with plugins on a surround bus can hang the export while flushing plugin buffers
• In rare cases certain plugins could hang export while flushing plugin buffers
• Export task fails with no meaningful message if drive or path is invalid
• Export as MIDI File should not show audio track warning message
• Warn if duplicate filenames in export task queue
• Changes to Notes tab are not reflected in the ID3 MP3 Options dialog until CbB restart.
• MP3 Options dialog should default to 256 kbps
• Export with External encoder was not functional
• Expand width of file overwrite prompt when exporting multiple files and make the list scrollable

 

Hi Noel,

This update seems to solve the stutter problem, when oversampling is activated on the synthesizers

2 hours ago, Noel Borthwick said:

@Jean Corivo Have you tried rolling  back to the prior release to verify that this is actually specific to 09?
Upsample on render depends on whether the plugin supports it. Not all synths support it properly. Also by any chance are you setting the render buffer size to a higher value?

 

@Noel Borthwick 

Hi Noel,

I did the test of reinstalling Cakewalk 2021.06 Update 3 (build 27.06.0.058) without changing any asio parameter of the apollo UAD card. The render (freeze track) works fine with oversampling on

I then reinstalled version 2021.09, I open the same project and try to render on the same track and I only hear stutter. It gives the impression that the synthesizers are no longer synchronized on the wordclock reference of the project.

I did the test with a new project, same result.

All the tests were done with a sampling rate of 48khz 

With version 2021.09 the upsample function (render & playback) seems to have a bug.
When I do a render (freeze track) of a synthesizer on which I have set the upsample function, the result is an audio file with a stutter effect.

If I open an existing project, on which the upsample function (2X) is on and whose synthesizer tracks have not been frozen, it is absolutely necessary to set the upsample function to off and then to on, otherwise the sound is completely distorted. 

If I unfreeze a track that was playing correctly from an existing project and then freeze it again, I end up with stutter

I also sometimes get a message that the sampling rate of the synthesizer is not correctly set at the time of rendering...

Test made with the synthesizers of the Komplete Ultimate 13 suite and the Synthogy pianos

x299 9980XE Skylake X 18-Core 64g ram Apollo thunderbolt audio card

5 hours ago, Thiago D said:

I'm also having this issue, expect it's bandlab itself that's not letting not login/redirecting me to the same site

I have the same problem with my Bandlab account. Whether it is with the app or via the web

On 4/23/2020 at 2:34 PM, Vernon Barnes said:

There is a thread in the deals forum

Basically since the most recent Softube update prochannel modules are not functioning correctly and attempting to open a project with them in will cause Cakewalk to crash to the desktop.

I reported this to Softube who say in their initial response.

 

 

I have now contacted Cakewalk support with a crash dump in case they can help.

For the time being I would recommend against updating Softube products if yo use them in the Pro Channel. Also I would tend to use the VST versions in the FX bin until some clarification or solution is found.

Do Softube support Cakewalk by Bandlab particularly with regard to Prochannel? Their list mentions Sonar but scook says the problem also occurs in Platinum. It maybe the particular service person at Softube was unaware of the link between Sonar and Cakewalk?

 

 

 

Here is the message I sent to David Gustafsson from Softube...

After several hours of investigations on the compatibility of the latest versions of softube plugins in ProChannel mode in Cakewalk here are my conclusions:
Version 2.4.96 is totally incompatible with the ProChannel version of Cakewalk, i.e. the 64-bit versions of Active Equalizer, FET Compressor, Focusing Equalizer, Passive Equalizer, TSAR-1R Reverb. In addition, all projects that were created with earlier versions of Softube (which worked relatively well) can no longer be opened. They literally crash the system and we are forced to reboot the computer, regardless of the sound card used (Apollo UAD, Focusrite Clarett, Tascam, Roland V-Studio 700).
I already noticed that since versions 2.3.xx occasional instabilities appeared. But since version 2.4.xx and subsequent versions, the problems have worsened, becoming completely inoperative with version 2.4.96.
It is mandatory to use the plugins in standard vst mode (vst2 or vst3) to be able to use them. This in itself is not a problem for projects that have used the standard versions of the plugins, but highly catastrophic when trying to open projects in which the plugins have been used in ProChannel mode.
I wondered how the Saturation Knob plugin (64-bit) in ProChannel mode, which is in the standard Cakewalk installation, didn't crash the system, even though I'm installing the Softube plugin series from version 2.4.96, of which Saturation Knob is a part.
Cakewalk installs in a particular folder all the plugins that will be recognized in ProChannel mode whose path is the following one: C:\Program Files\Cakewalk\Shared Utilities\Internal. All the ProChannel plugins installed in this folder and recognized by Cakewalk will bypass the more recent versions installed elsewhere, such as in the Vstplugins folder. for example. To my knowledge, I have never seen any Softube plugins other than Saturation Knob installed in this folder. All other plugins made by Softube, are installed in the standard Vstplugins folders, even for the ProChannel versions of Active Equalizer, FET Compressor, Focusing Equalizer, Passive Equalizer, TSAR-1R Reverb.
The current version used by Cakewalk of Saturation Knob (64 bits) is 2.2.84. It bypasses the ProChannel version of the plugin, but if I use the standard vst version, I end up with version 2.4.96.

Workaround:
The only way I found to retrieve my projects with Softube ProChannel plugins was to unzip an old 64-bit version of the Softube installer (2.2.79) I found on my server to extract the faulty plugins and copy them to the C:\Program Files\Cakewalk\Shared Utilities\Internal folder. 

I do not touch in any way the normal installation of Softube plugins which can be found in the following folder C:\Program Files\Cakewalk\Vstplugins\Softube.

Now everything works perfectly, I have access to the saved settings and presets. Moreover, I found a stability with Cakewalk (Bandlab) that I hadn't known for a long time. 
On the picture below I inserted 6 various plugins on 64 tracks without any kind of problem

 

It would be imperative for Softube to work on this or give indications about known bugs with the ProChannel versions of their plugins...
 

1 hour ago, Noel Borthwick said:

So by extension if someone decided to arbitrarily name .wav file .wave we should support it right and it's a "bug"that we don't? 😕

Well verify if this is indeed coming from established Mac apps

I see your point. It seems that on Mac, we're more likely to want to reinvent the wheel... 🙂

Here is a screenshot when saving a midi file with Cubase 10 on OSX. By default the .midi extension is selected.
 

2 hours ago, Noel Borthwick said:

Where are you getting .midi files from? the standard extension is .mid not .midi. And CbB sees .mid files fine in the file open dialog if you pick "files of type MIDI"

When I receive midi files from Cubase or Nuendo on OSX, the extension is .midi.
As far as I know, the same is true for files from Logic Pro.

On 5/21/2020 at 12:46 AM, Noel Borthwick said:

Quicktime video definitely works in Cakewalk using the Media Foundation engine in Windows 10. See image where I am running a QT video in the latest release.
Keep in mind that the MOV extension is just a container for a video format so just looking at the file extension doesn't mean anything.

If stock Windows can play the video then Cakewalk, should be able to load it since we rely on Media Foundation for all our video support. For it to be compatible with Windows the video must be encoded in a compatible format such as MPEG4 or you must have the appropriate codec installed. Generally a thumb rule is if the Windows video player can play it then it should be ok to import.

Actually, the Quicktime .mov works well with the "Media Foundation"  video engine.
However, changing the starting point is impossible and the entry points and operate in an approximate manner.
You have to fall back on the old video engine, much less powerful, but which allows a better handling of .avi files. (mjpeg, DV and a series of old, mostly obsolete codecs)
The only way to get around the problem is to use an application like VidPlayMTC or a second computer and do the synchronization by midi timecode. However this slows down the production process, especially when you need to synchronize sound elements at specific sync points. An integration of a better video player would be highly appreciated.
However, Cakewalk is a fantastic creative tool and the multiple updates show that it is powered by a dynamic and energetic team. ! 

A complete overhaul of the video player : 

• Better file support for both import and export files
• Possibility to change the starting point, entry point, exit point, 
• Better use of the graphic card (GPU)

Currently, the video player hasn't evolved for almost 10 years... it's completely outdated...

The use of Cakewalk in post-production, film music, tv ad, multimedia, video game's post-pro, etc.,  becomes totally tedious. 😕

9 hours ago, Jean Corivo said:

When there are 10 tracks or more with ProChannel plugins visible in the console, it makes Cakewalk totally freeze.
When I use the Cakewalk, Softube, Overloud, Boz Digital Labs plugins in ProChannel version, I must use a maximum of 8 ProChannel console tracks visible at the same time to avoid crashing my Cakewalk session.
 

After several hours of investigation, it seems that Softube's plugins in ProChannel mode of the ''Mix Bundle'' series are causing the problem. Saturation Knob as well as all other ProChannel plugins made by other software companies such as Overloud, Boz Digital Labs, do not cause any problem, even if they are used on multiple tracks and are visible on the ProChannel Strip in the console view.

Are these the latest Softube plugin updates?
I wrote a message to Softube

When there are 10 tracks or more with ProChannel plugins visible in the console, it makes Cakewalk totally freeze.
When I use the Cakewalk, Softube, Overloud, Boz Digital Labs plugins in ProChannel version, I must use a maximum of 8 ProChannel console tracks visible at the same time to avoid crashing my Cakewalk session.

Operating System
    Windows 10 Professionnel 64-bit
CPU
    Intel Core i9 7980XE @ 3.00GHz 
    Skylake-X 14nm Technology
RAM
    64,0 Go 
Motherboard
    ASUSTeK COMPUTER INC. WS X299 SAGE (LGA 2066 R4) 
Graphics
    BenQ GW2765 (2560x1440@59Hz)
    BenQ GW2765 (2560x1440@59Hz)
    4095MB NVIDIA Quadro RTX 4000 (NVIDIA) 
Storage
    14904GB Intel Raid 0 Volume (RAID )
    14904GB Intel Raid 0 Volume (RAID )
    1863GB Samsung SSD 970 EVO Plus 2TB
Optical Drives
    ASUS SDRW-08U9M-U USB Device
Audio
    Cakewalk VS-700 System or UAD Apollo

All grouped commands or functions with the CTRL + [command] key, no longer work.

Release: 2020.01 (Build 28)

Montreal, Canada

11 hours ago, Noel Borthwick said:

Hi @Rogério Dec this would be a limitation of the Microsoft Media foundation video framework that we use so it could be tricky to address from our side. We haven't looked at video in a long time but we'll schedule some time to investigate again in the future. Thanks for your understanding. The root issue is that MP4 compressed requires prior keyframes to be decoded before the video engine can start streaming. In general most compressed formats including MP3 work that way and are not designed for editing. Some video apps decode to an intermediate format for this reason.

This is very good news Noel, to know that you are going to focus on developing better handling, video files on Cakewalk.
This is probably the only aspect of the software that is lagging behind the competition, so that Cakewalk can be used in all stages of Post-Production.

I love this software. I use it in conjunction with the VS-700 control surface every day professionally on TV ads, short film or album production. Unfortunately on feature films, because of the shortcomings we know, I have to fall back on ProTools which offers a greater possibility of handling video files. It's a shame, because in every other aspect of the production, Cakewalk offers a greater versatility of implementation tools, for a professional sound result.

Noel, thanks again for the highly professional involvement you put into the development of Cakewalk.
We feel supported.

1 hour ago, MusicMan11712 (aka Dr. Steve) said:

Maybe the good folks at BandLab can add an option so you can open *.midi files and I can open *.smf files...

It's the request, nothing complicated to set up... 😉

23 minutes ago, MusicMan11712 (aka Dr. Steve) said:

Interesting: The standard *.mid file I renamed as *.midi (not OSX midi file) seems to open (1) by clicking on the file directly and (2) by reopening it from the start page (recently opened files), but not (3) by dragging it to the Cakewalk desktop or (4) by searching using the All Cakewalk File Browser.

Because I changed the association, Windows knows to open it with Cakewalk, but as you pointed out other ways of opening files don't presently work.

I just tested this with an old *.smf file -- the default extension for an old midi program. It opens using methods (1) and (2) but not (3) and (4).

Note sure it helps, but I figured as long as I explored this (and seem to have replicated your issue), I thought I'd share it.

Steve

 

 

The problem is CbB does not recognize the .midi extension. There may be workaround, but it is better to have this feature directly implemented in CbB. On the other hand the  .midi extension is generated when we export midi files with Cubase, Nuendo as well as other software running on Mac (OSX)

I have been working with UAD products for several years.

They integrate perfectly with CbB....

Currently one of my systems has UAD DSP cards as well as UAD AD / DA converters via Thunderbolt 3.

Everything works flawlessly..

On 8/3/2019 at 11:25 AM, HIBI said:

You might want to change/add File associations on Windows.

I know how to change file associations. 😉 This is not the problem... 
This is to open a file inside the Cakewalk app. CbB does not recognize this extension, and it doesn't appear in the files that Cakewalk recognizes..
I know we can open it from the file manager, but to speed up the process, it would be better if we could open it inside the CbB program

Something simple ...

Add the .midi extension to those recognized by Cakewalk when you try to open a midi file. These files come from the OSX platform. These are simple midi files but because of the extension are not visible when we try to open them through the Cakewalk application. You have to change the extension from .midi to .mid  so that it can be read by CbB..

Composing movie music, there are often tempo changes in the same sequence.
When I work with a small orchestra, I use a click track sent to the headphones of each musicians, which can do the trick.

But recording an orchestra of 20 or 30 musicians or more, it becomes important to be directed by a conductor. The use of visual cues becomes imperative to properly direct the ensemble when there are tempo changes. This would be an addition that would allow using CbB in movie music sessions.

In the same vein, it would really solve the problem of offset, inset and startpoint videos when we work in the Microsoft Media Foundation mode.

I leave here examples to better understand the process.