Jump to content

Recommended Posts

Posted (edited)

@Noel Borthwick Thanks for your reply.

Yes, Cakewalk reported the crash of VST plugin, as you assumed (see my screenshot).

As I already mentioned, previous versions of Cakewalk (including the latest preview) did't reported this, started right with this new update.
I didn't observe any misbehavior of these plugins within previous Cakewalk versions, but as you stated, it doesn't mean that there were no issues.

I also don't observe any problem with these plugins in other hosts / daws, so maybe specific combination of these u-he fx vst3s and Cakewalk? Maybe something specific about how DAW feeds state data to plugin during it's initialization?

Anyway, I'm also attaching the minidump file, unfortunatelly, I'm unable to analyze it by myself. :)
I'll also send it to u-he with specific info on DAW (Cakewalk version), so they can analyze this scenarios.

From my point of view, it looks like there is some issue with plugin instance state "deserialization" during plugin initialization phase?
I also tried this:

- Uninstalled VST3 version of Presswerk from my PC (actually moved .vst3 files out of the vst3 folder).
- Loaded Cakewalk project containing this plugin into DAW (project did load successfully, with plugin instances placeholders).
- I saved FX chain state to fxc file (also attached - FX1.zip), assuming it will save also the plugins state.
- Re-installed VST3 files of presswerk while Cakewalk still running, rescanned VSTs, checked Presswek (VST3) is present and enabled).
- Loaded FXC file back into bus - it also caused crash of Presswerk VST3 plugin, caught by Cakewalk.

Question: Is there anyhow possible for me to restore plugin instance state stored within existing cakewalk project, so I can set parameters of the VST2 instance of this plugin with exactly same values? Unfortunatelly I didn't same the plugin state as standalone preset and I want to try restore Presswerk and Satin settings using VST2 instances. :(

Thank you, Noel, and wish you all the best.

Cakewalk_Presswerk_Crash.png

2021-02-25_05012021_191305.dmp.zip FX1.zip

Edited by Štefan Gorej
Typos
  • Thanks 1

Share this post


Link to post
Share on other sites

@Štefan Gorej I’m curious if you insert this plugin in a new project, change its settings, save as a new project and open it does it also crash?
You can’t restore VST3 plugin state into a VST2 plugin unless the plugin supports it.
Waves support going from VST2 to VST3 but most other vendors do not.

I looked at your dump file. Its definitely a crash solely in the plugin caused by it accessing a null location. So the stricter error handling is doing its job in pointing this out and stopping execution. While bugs like this may have sometimes gone undetected in the past in some cases they could corrupt the memory state leading to all kinds of instability in the app. So its critical that issues like this are fixed in the plugins to avoid destabilizing the entire project.

According to the dump I don't see Cakewalk loading the project in the stack so perhaps the crash occurred after the project loaded. Was it still loading the project when it crashed? Sometimes its hard to see from the dump since the data doesn't always accurately report the rest of the state.

---
Unhandled exception at 0x00007FFC38DF5D64 (Presswerk(x64).vst3) in 2021-02-25_05012021_191305.dmp: 0xC0000005: Access violation reading location 0x0000000000000000.

Presswerk_x64_+3d5d64
00007ffc`38df5d64 8b11            mov     edx,dword ptr [rcx]

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffc38df5d64 (Presswerk_x64_+0x00000000003d5d64)
   ExceptionCode: c0000005 (Access violation)
Attempt to read from address 0000000000000000

DEFAULT_BUCKET_ID:  NULL_POINTER_READ

PROCESS_NAME:  Cakewalk.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FOLLOWUP_IP: 
Presswerk_x64_+3d5d64
00007ffc`38df5d64 8b11            mov     edx,dword ptr [rcx]
 

 

Share this post


Link to post
Share on other sites

As I mentioned in the other topic, this is a bug for me when comparing with Sonar Platinum. And when you open the Bus Pane and lift it to the top, when you collect it by the button, that separation disappears on Cakewalk.

Sonar PlatinumSonar.PNG.618f5926d6080ea438cd47bbf02d7e97.PNG

Cakewalk By Bandlab Cakewalk.PNG.fb7af7967fda964d7e46e04d49747a87.PNG

  • Thanks 1

Share this post


Link to post
Share on other sites

I've had an issue with the new Tempo Track. I've loaded an existing project, and it has overwritten my existing tempo data. In many cases, the overwritten version is an accurate simplification of the old data (for example, if the old data was a lot of tempo changes that amounted to a straight-line transition from one tempo to a new tempo, the new data takes the first tempo and creates a single linear transition to the new tempo). However, in some cases, the overwritten tempos are completely inaccurate. As far as I can tell, this is happening when I'd previously drawn in manual tempo changes - these have been removed and replaced with "fast" or "slow" curves, which don't match the original data. In some cases, these curves are now running until the following tempo change, which is completely inaccurate. Is this a known issue, and if so, is there a timeframe for resolution? I suspect I'm going to have to roll back to the previous version to complete the project I'm working on (and thank goodness I have a recent backup of the file!). I love the idea of the new Tempo Track - just want to be certain that the implementation isn't going to overwrite my handcrafted data before I try updating again...

Share this post


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

I've had an issue with the new Tempo Track. I've loaded an existing project, and it has overwritten my existing tempo data. In many cases, the overwritten version is an accurate simplification of the old data (for example, if the old data was a lot of tempo changes that amounted to a straight-line transition from one tempo to a new tempo, the new data takes the first tempo and creates a single linear transition to the new tempo). However, in some cases, the overwritten tempos are completely inaccurate. As far as I can tell, this is happening when I'd previously drawn in manual tempo changes - these have been removed and replaced with "fast" or "slow" curves, which don't match the original data. In some cases, these curves are now running until the following tempo change, which is completely inaccurate. Is this a known issue, and if so, is there a timeframe for resolution? I suspect I'm going to have to roll back to the previous version to complete the project I'm working on (and thank goodness I have a recent backup of the file!). I love the idea of the new Tempo Track - just want to be certain that the implementation isn't going to overwrite my handcrafted data before I try updating again...

I've just seen a post in a different thread that fixes this issue.

"If you set the following within Preferences->File->Initialization File:

TempoImportErrorThreshold=0

... the tempo will be imported exactly as it was in the old project and won't try to fit an envelope shape to the map."

 

Might be worth flagging this more prominently - currently, the new update "breaks" existing projects with non-trivial tempo data unless this flag is set. Might even be worth setting the flag as a default?

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites
3 hours ago, Herbert Zio said:

As I mentioned in the other topic, this is a bug for me when comparing with Sonar Platinum. And when you open the Bus Pane and lift it to the top, when you collect it by the button, that separation disappears on Cakewalk.

Sonar PlatinumSonar.PNG.618f5926d6080ea438cd47bbf02d7e97.PNG

Cakewalk By Bandlab Cakewalk.PNG.fb7af7967fda964d7e46e04d49747a87.PNG

That's a Bug FIX for me

  • Like 1
  • Haha 1

Share this post


Link to post
Share on other sites

@Herbert Zio, huh, you're right. If you pull the Bus Pane separator all the way up so that it fills the space (hiding the Track Pane) and then press the Show/Hide Bus Pane button, the separator line is not re-drawn.

The reason I called it a bug fix is because I don't recall the separator line being shown at all in earlier versions of SONAR/Cakewalk.

Thanks for taking the time to prepare the visual.

Share this post


Link to post
Share on other sites
1 hour ago, Herbert Zio said:

Is this a bug fix? 🤔

You see the gray line at the bottom just below where the speaker icon is? That may be the separation between the bus pane and the track pane. See if you can raise it up to expose your master out. 

Share this post


Link to post
Share on other sites
Posted (edited)

See my thread here We have a timing issue 2021.04 is dropping clips late when recording.

@Noel Borthwick Both my machines were (now are) on 2021.01 Build 98, and working properly.
I have not done a "Loop Back" test as yet, but I will and report back if I have any more issues.

"The Law of Unintended Consequences"
I see below you mentioned no changes were made to "Recording" in the .04 release, but evidently the above quoted "Law" has reached out and bite you in the proverbial; well you know what I mean.
I always blame Rockus n Rollus (The Gods of Rock Music) when things like this happen...

tom

Edited by DeeringAmps
added content
  • Thanks 1

Share this post


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

It was only done this week so it's after the EA.

I run at 2K (1440p) at 100% scaling and didn't notice a difference until I changed the scale to 150%. Since it's new we didn't enable this by default so any feedback is useful.

@Noel Borthwick,

Pros: The text is definitely crisper

Con 1: The text is rendered smaller than when the config setting is 0. It maybe just goes under the threshold of comfort, for me personally. At my normal scaling of 125% I find I prefer to turn off this feature.

Con 2: There is some kerning issues with bold text. Probably nothing you have control over, font scaling is tricky. See below, specifically "gr" "it", "at" etc.

 

image.png.006d00fdcb8ed946f6a81e9a9b49f94b.png

Share this post


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

See my thread here We have a timing issue 2021.04 is dropping clips late when recording.

 

tom

@DeeringAmps We'll investigate this. There were no changes made to recording this release. Which version were you running before you updated? Have you tried rolling back to verify if this is a new issue?

Share this post


Link to post
Share on other sites
3 hours ago, Colin Nicholls said:

@Noel Borthwick,

Pros: The text is definitely crisper

Con 1: The text is rendered smaller than when the config setting is 0. It maybe just goes under the threshold of comfort, for me personally. At my normal scaling of 125% I find I prefer to turn off this feature.

Con 2: There is some kerning issues with bold text. Probably nothing you have control over, font scaling is tricky. See below, specifically "gr" "it", "at" etc.

 

image.png.006d00fdcb8ed946f6a81e9a9b49f94b.png

Thanks, we have no control over this - its all handled by Windows.

Share this post


Link to post
Share on other sites
Posted (edited)

@Noel Borthwick, the dump file, that I sent in my previous post, was from my "experiment" with .FXC chain loading to already opened Cakewalk project.
I'm sending the dump that came from crash during Cakewalk project load. Exact steps were as follows:

1. I created a new, completely empty project, added one bus track
2. Added an instance of Presswerk VST3 to FX slot of this bus, switched the FX chain and the plugin itself
3. Opened the plugin window to ensure that it's successfully loaded and initialized
4. Saved the project as a new .CWP
5. Exited Cakewalk and started it again
6. Loaded .CWP project saved in step 4

=> Crash on Presswek VST3, dump file from this cras is attached.

So, as I experimented, plugin crashes in this two scenarios:

a) When loading .CWP project that already contains Presswerk or Satin VST3
b) When loading FX Chain that contains Presswerk or Satin VST3 into already opened Cakewalk project

I also tried following scenario:

1. Created empty .CWP project
2. Added Presswerk VST3 plugin instance
3. Loaded existing preset into it using CAKEWALK PRESET functionality (.vstpreset file)

This scenario was successfull, without crash, all parameters values from VST preset loaded successfully into existing plugin.

See my attachments.

Hope this may help to better understand my specific problem.

Thank you,
Stefan

_05022021_093720.zipPresswerk.vstpresetPresswerk.thumb.png.7f8e9f3c9b0f8b09a84545b9daf7f776.png

EDIT: Btw. How to roll back to previous Cakewalk build to be able to load my projects and manually note Presswerk and Satin values to be able to manualy set them the same way in VST2 plugin instances (until solved in software)?

_05022021_093720.zip

Edited by Štefan Gorej
Added question

Share this post


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

Thanks, we have no control over this - its all handled by Windows.

This seems to be a font that is a combination of bitmap (smaller sizes) and vector (larger sizes) - I believe it's the plain old MS Sans Serif. Changing the font on those labels would probably solve that.

While I'm here - kudos on the new look of the envelopes, I was just thinking a couple of days ago "I wonder if Cakewalk finally got rid of this outdated 3D look for nodes" :) Maybe this will convince me to upgrade (still on 2019.09 here...)

Share this post


Link to post
Share on other sites
Posted (edited)
On 4/30/2021 at 5:04 PM, Herbert Zio said:

Is there a way to change the background color of the bus pane . . . through the theme editor

@Herbert Zio  Would something like this or this be helpful? 

PS: This question is not really 2021.04 Feedback. If there is additional discussion, I'd suggest using a different thread maybe under Q & A or the UI Themes Sub Forum?

Clarification of my intent: Anything I have to say WRT colorization and the theme editor is not specific to 2021.04; therefore, I do not plan to address the question with additional posts in the current thread. Sorry for the misunderstanding.

Edited by User 905133
to clarify the intent of my response

Share this post


Link to post
Share on other sites
2 hours ago, User 905133 said:

@Herbert Zio  Algo como isso seria útil? 

PS: Esta questão não é realmente um Feedback 2021.04. Se houver discussão adicional, sugiro usar um tópico diferente, talvez em  P&R ou no Sub-fórum de temas de interface do usuário .

 

For me, it's feedback about 2021.04. After all, the Tempo Inpector function corresponds to 2021.04, and the background color of Tempo Inspector does not correspond to the rest of the DAW and is not harmonious.

It is better to fix the problem before the official release, than to accumulate unresolved bugs like the other colors I mentioned, whether from the bus pane or from others inspectors or browser.

  • Like 1

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...