Noel Borthwick

1 hour ago, Tez said:

It was temporary, I'll try and recreate it and check if it's consistently behaving as previously described. How do you want it sent?

You can upload it to a file share and PM it to me and Jon

1 hour ago, GreenLight said:

It did happen with no sustain pedal in use when I played synth parts with Diva as well.

I will continue producing and report back, while also keeping in mind what you wrote above. Thanks!

@GreenLight are you only getting stuck notes with notes played from the keyboard or is it also playback of notes from the track that are sticking.
Is it simple track and keyboard controller playback or are you also using generative effects/synths etc.
Are you sure that this is specific to the 09 release? i.e. if you roll back do you still see this?

14 hours ago, GreenLight said:

>The MIDI All Notes Off message is no longer sent to VST plugins on transport stop. Since Cakewalk manages all MIDI note on's explicitly, >sending note off messages for just those notes, the All Notes Off message is no longer required.

I updated to 2021.09 yesterday, and first of all - thanks for the bugfixes! ?

After the update, in just a few hours I've been getting more hanging notes than usual with several of my VSTi:s... it feels like it ought to be directly related to the removed MIDI All Notes Off message?

An idea – if permitted in this thread – would be to make an option under Preferences / Project / MIDI / like "Send MIDI All Notes Off message on transport stop". So that it could be user-enabled in circumstances that require it?

EDIT: Even sustain pedal messages seem to be hanging... (Happened once so far.) Am I the only one experiencing this?

Which VSTs?

Look at this video around 6:15. Read about audio snap.

Yes mine has a vesa mount like other monitors.

12 hours ago, Will. said:

Now the question is: and I'm sorry if this is in the posted in wrong topic - isn't there a way for track 1 to mute behind the scenes and only let the armed track be heard to give the user the actual picture of what is being projected to him through these inputs? 

No because as far as routing goes an input on a track from a patch point behaves the same as a hardware input. Arming a track shouldn’t impact what you hear from other tracks. If you are feeding one tracks input from other tracks you will need to manually solo to hear just that track.

6 hours ago, Tez said:

Bounce to track bug:

I setup a test project (44.1-16 WASAPI Exclusive) with 2 identical length stereo audio tracks taken from a similar projects rendered audio files, ergo the audio files are 32 bit. The sends of both audio tracks were set to the same aux track which had a couple FX plugs, and the aux track's send was to a hardware out.

All tracks were selected for the range of the audio files. On executing a bounce to tracks for source category tracks the following occurred:

1. Selecting just the aux track not in real-time with the buffer set to "playback" the rendered track was all silence.

2. Selecting just the aux track  in real-time  rendered the track normally.

3. If the track was rendered as per 1. and the immediately followed by a second bounce as per 1. the track  rendered normally.

This is odd behavior,  it feels like some kind of a timing issue, but wadda I know ?

Will investigate thanks.

Yes

On 10/17/2022 at 5:09 AM, István Máté said:

Yes. In my use case, I create MIDI multitracks for live use, main (Master) mix is for myself during creation, but each track is sent to a dedicated hardware output (Dante Virtual Soundcard) via Send. I usually send stereo channels, only the Metronome aux (stereo channel) and the Bass (stereo channel) is sent mono to a hardware out L and R. In this version both the Metronome and Bass were present in the hardware out's L and R, while in previous versions I had the Metronome in L and Bass in R. Did notice, that changing the Metronome aux to mono did solve the issue for the metronome, I presume, that changing the Bass channel to mono would have solved it for Bass too, but I did not test it, I rolled back.

I presume, that this is not intended, sends to a mono hardware out (more specifically, to only one channel of a stereo hardware out) from a stereo channel should not creep into the hardware out's other channel.

@István Máté this is fixed in the early access release we just posted above

@Kvancho there is a build with a fix for this issue.

We just release an early access build that we plan to release on Monday. It has a few fixes to reported problems. Please check it out.

This is unlikely to be related to your project file. Meters going into the red are a sign of the plugins generating garbage floating point data or denormals. Most likely caused by bugs or corrupt data in the plugins themselves. Some plugins also intermittently misbehave when the double precision engine is enabled or with Plugin load balancing active so you can experiment with disabling those options.
If the issue persists contact the respective plugin vendor to troubleshoot further since its not a host problem.

Its, not clear what you were trying to do in the video.  It seems you were confused by the default audio and midi track that are pre created in a new project.
The dialog for insert synth is the advanced dialog that happens when you insert a synth manually from the browser.

There is an easier way to insert an instrument track. Click the big + button at the top of the tracks view. In the instrument tab pick the instrument you want and click Create. Thats it - the synth routing is all set up for you and you can immediately play the synth.

I have the Keystep32 running here and there are no issues with MIDI from the keyboard.
Make sure you have their latest MIDI drivers installed from the MIDI Control center. 

Have you tried record enabling a MIDI track and testing recording from the controller?
BandLab support won't necessarily be able to assist you with configuring third party hardware controllers.

@Mage_et_lent Cakewalk no longer actively supports Windows 7. If you continue to use it, it's up to you to ensure your Windows 7 has the latest fixes from Microsoft. As things are bound to break.

Not sure if this is related or not but the latest update has code signed dll's using SHA256. Windows 7 did not have SHA256 support by default so if you don't have a fully patched version you may have incompatibilities. This article has some further info.
https://support.microsoft.com/en-us/topic/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus-64d1c82d-31ee-c273-3930-69a4cde8e64f

Again I'm not sure if your issue is related or not. We're not seeing any problems in our Windows 7 test. Without seeing your project file there is nothing we can do further.

14 hours ago, noynekker said:

@Noel Borthwick . . . Hi Noel, thanks for the tweak . . . I'll surely give that a try, and report back here.

Here's a WeTransfer Link with a few recent dumps if you want to have a look:

https://we.tl/t-AqW3hX3CIR

Nothing in the dump file other than the line that says its heap corruption. I would try disabling the flush tails setting.

Unhandled exception at 0x00007FFB7662F6A9 (ntdll.dll) in Cakewalk.exe.2592.dmp: 0xC0000374: A heap has been corrupted (parameters: 0x00007FFB766997F0).
 

Not quite as crazy as Lord Tim's deep but I have a 35"curved screen LG that I use. The curve is subtle so it doesn't bother me. 

I wouldn't have been able to fit that on my desk if it wasn't curved.

6 minutes ago, Scott Wheeler said:

We do, but the symbols file for the VST managed to not get checked into our repo for build artefacts (just the standalone symbols got checked in, which isn't useful here), so don't have function names.  We sent the user a debug build from the same tag, but didn't hear back.

Ah yes without symbols you can't find much. Hopefully he replies. Let me know what operation caused the crash in case you find out.

It has nothing to do with cakewalk not being able to process large projects tracks. 24 tracks in itself, is tiny. People are running literally projects containing 500 tracks.
Even on a powerful machine if you put a single plugin that is expensive on a track, it can block processing for longer than the allotted time and lead to late buffers.
This is because a buffer will be delayed even if a single tracks processing is late. Raise your buffer size and it will reduce or eliminate late buffers. Plugin load balancing can also help.

Like others said if removing a particular track or tracks stops the late buffers, then something in that track is taking longer to process than the buffer quantum. If it takes longer than the time allotted playback will continue but you might hear clicks from your sound device because it is being starved.
The late buffers is just a metric to help users diagnose why glitches occur.

Try deleting the plugins in the tracks to diagnose. 

16 hours ago, XBaker said:

When I choose Insert Instrument, the default Instrument is TTS-1. Is it possible to make a different instrument the Default? I searched the Help, this forum, and poked around Manage Plugin Layouts, but no joy.

Thanks for any help!

@XBaker Hello Tom ?

No, today the "default" instrument is hardwired to TTS-1 and its primarily there provide a default routing when opening MIDI files.
However, the add track dialog remembers the last used instrument for the duration of the app session, so if you pick a different instrument, it will remember it. It just won't be listed under the default category.

For what it's worth, try turning off this setting by setting its value to 0.
Some plugins don't behave well when we try and flush them prior to doing a bounce. 
Also please attach the dump so I can have a look at the stack.

On 9/26/2022 at 4:50 PM, GCizza said:

Many thanks. I've sent the developer the dump file. 

Good. Hopefully the developer knows how to debug using dump files. It's always surprising to me but many plugin developers don't even know how.

Edit: I see that @Scott Wheeler is the developer ?
Scott if you need any information from our end or find that it's an issue related to Cakewalk don't hesitate to contact me.

Unlikely since that seemed to be the only issue in that project. Once I skipped that missing wave file name the rest of the project opened without errors.
If it were disk corruption or badly saved, then there would be far more errors. In any case the fix I made will allow such projects to load properly. Of course, any clip with the missing data will be orphaned.

On 10/11/2022 at 4:40 PM, sjoens said:

Thanks Noel, I did a few days ago and fixing the Runtimes was one of their options.

@sjoens Sorry for the late reply. I looked at the dump files and both crashes are in your soundblaster driver!
Cakewalk isn't even doing anything at the time of the crash. This is purely in the driver.
I suggest uninstalling their driver or troubleshooting what causes it to crash with the vendor. This is not related to the latest update.

Unhandled exception at 0x000000006A800598 (CtHdAs64.dll) in Cakewalk.exe.21944 - Copy.dmp: 0xC0000005: Access violation reading location 0x0000000000000008.

If you google CtHdAs64.dll you will see that it is from Creative Labs. This is the data on the file that caused the crash. 
CtHdAs64.dll    *C:\Windows\System32\CtHdAs64.dll    6.00.100.2059    3/1/2016 4:34 AM    
 

@IRAKLI KVANCHIANI

The reason it crashes is that somehow your project was saved with the catalog of referenced wave files incomplete. One of the referenced files was saved without its filename. As a result, the code wasn't expecting that and crashed. This is literally the very first time I've ever encountered this problem, so it's not impossible that something corrupted the project file somehow.

However, I was able to handle this condition gracefully in the code and your projects load fine now. We'll release an update with a defensive fix for this since we take data loss seriously.
fixed files.zip
Here is a zip with the fixed project files. Do you have any idea what you may have done that led to the files being saved incorrectly?