Jump to content

Recommended Posts

2 hours ago, gmp said:

 the only way I can view Pro Channel now is by undocking the Inspector. 

It seems part of the problem is not enough space at the top of the Inspector Show/Hide Arranger Inspector, etc
 

Check your theme. Are you using a custom theme? Does this happen when using Mercury or Tungsten, the default themes?

Share this post


Link to post
Share on other sites
53 minutes ago, Colin Nicholls said:

Check your theme. Are you using a custom theme? Does this happen when using Mercury or Tungsten, the default themes?

When testing make sure CbB session starts up loading Mercury or Tungsten.

If the custom theme is loaded first, swapping to Mercury or Tungsten will still have image size problems. 

After changing from a custom theme to Mercury or Tungsten shut down and restart CbB.

Share this post


Link to post
Share on other sites

use the default themes - there are several themes that worked correctly up to build 175 and need some tweaking (flat white, minimalistic orange etc) but the default mercury works correctly in 175. i had problems with all themes in build 141 and then 155 - but the "EnablePluginMenuFix=1"  in the cakewalk.ini addressed that issue with the spacing on the inspector. so that may help until the theme you're using is updated

Share this post


Link to post
Share on other sites

Cakewalk is now crashing on me whenever I insert a MIDI track and try to trigger a synth with it, and whenever I attempt to bounce a to a track.  in short, the program is basically unusable.  

 

I have yet to expernience a Cakewalk update without experiencing very serious problems afterward.  It's enough to make me try another DAW.

 

 

  • Sad 1

Share this post


Link to post
Share on other sites
Posted (edited)

I can no longer trigger any synth via MIDI input.  The input and output settings are appropriate; MIDI metter is triggering with notes, so MIDI is being received, but the synth does not show any response, and the app will hang if I try to bounce.  

I have reversed the update to the Jan,. 29 version; same issue.  Re-installed the May 17 version; same result.

Tried loading the project ion Sonar X3; the application hung.

TH=his is a lot more than a minor inconvenience.  This is core functionality.

Edited by Richard Hunter
fuller explanation

Share this post


Link to post
Share on other sites

I changed to the Mercury theme, closed and reopened CbB and it worked. I then tried the cakewalk.ini entry EnablePluginMenuFix=1  I entered it correctly, then changed to my custom GP Logic 21 theme, closed and reopened CbB and still have the seam problem. I double checked the Preferences and they're done right. At least I have a workaround of undocking the Inspector.

IS this something that will be fixed in a new version of CbB, or do I need to edit my theme and fix it? It's been right at 4 years since I messed with Themes. When I installed 2021.04 it said my Theme needed to be updated. I did that and it now has worked fine, but now I have this problem. If I need to update my Theme, any guidance would be appreciated.

Any more suggestions?

Share this post


Link to post
Share on other sites

The images in the user theme must be modified to their new size.

This may be done by using the images from Tungsten, any user theme that has already been updated or removing the images allowing the theme to use the Mercury images.

Maybe this post may make more sense now

It did not seem to be very well received when originally posted.

Share this post


Link to post
Share on other sites
47 minutes ago, scook said:

The images in the user theme must be modified to their new size.

This may be done by using the images from Tungsten, any user theme that has already been updated or removing the images allowing the theme to use the Mercury images.

Maybe this post may make more sense now

It did not seem to be very well received when originally posted.

Yes that was my post and what you said worked fine, so my theme is updated and has a new date on it. CbB stopped saying I had an outdated theme. So shouldn't it work with the Pro Channel Inspector?

Share this post


Link to post
Share on other sites

If images identified in the post I linked were modified the theme should work.

There was no indication in the thread what was done other than opening and resaving the theme. This does nothing to correct image sizes.

New images must be added to the theme. the current images must be resized with an image editor or the images removed so that the theme uses the Mercury images.

 

  • Thanks 1

Share this post


Link to post
Share on other sites

I opened my custom theme in Cakewalk Theme editor, the new Theme editor, that I installed from Bandlab Assistant when I made that other post. I saw Inspector in the folders on the left and selected it and saw the Arranger tab and Tempo tab icons that look exactly like the ones I see in the Inspector using 2021.04. So I would think because of this that my Theme is updated otherwise those new tabs wouldn't be there. 

So what am I supposed to change as far as images, there appear to be hundreds of them? Has there been a system outlined to explain to users like me how to do this? If not maybe they need to update the Theme Editor again so it takes care of these things

Share this post


Link to post
Share on other sites
9 minutes ago, gmp said:

So what am I supposed to change as far as images, there appear to be hundreds of them? Has there been a system outlined to explain to users like me how to do this? If not maybe they need to update the Theme Editor again so it takes care of these things

(1) When you say a custom theme, do you mean that you created it? Did someone create it for you?

(2) The theme incompatibility message has a link to the most recent image changes (and the ones before that and . . . ).  If you didn't click on that link you should.  If not, you can find the link in the Cakewalk Update Available thread (or whatever its called.  If you custom theme has never been updated over the past year or two, I suppose it is possible that hundreds of image MIGHT need to be changed.

(3) As I recently learned, its the same Theme Editor that has been used previously for CbB.  As I understand it, just the resources used by the editor change changed.

(4)  Depending on how customized your theme is and when it was last updated (to take into account the changes listed in the link I mentioned), it could be a very easy fix or it could require redoing just the last set of elements that were changed.

I am just a user here, so if I am wrong, I hope some of the experts will clarify what I might have misstated.

Share this post


Link to post
Share on other sites

It's someone else's theme it may have been originally called logical.sth   My alterations of it are named "Logic GP 21". I edited the theme 21 times and saved each version.  It was the theme closest to what I wanted and then I tweaked it the rest of the way and have been using it since April 2017

For a while me and many of the forum members were really into Theme editing when it first came out. Most of us got what we wanted and just moved on

 I've been using it since April 2017 with no changes until I installed the new Theme Editor and loaded my custom Theme in that and then saved it. That fixed it good enough to stop the error message of Theme incompatibility..

 I hope Cakewalk can come up with a solution that's understandable and not huge painstaking process.

  • Meh 1

Share this post


Link to post
Share on other sites

Sends inserts in console view do not pan any more, nor do they “Follow Track Pan” when POST is enabled.  
 

I noticed a couple of weeks ago that something was starting to sound off in my mixes as they sounded washed out and cloudy.  I put it off on thinking I was just exhausted or perhaps I made an accidental change with my effects but, after taking time to finely comb through settings, I discovered the issue with the panning of sends.

I solo’d the stereo vocal track, put the reverb insert send on PRE then turned the track fader down to hear only the vocals reverb.  I always do this to find the sweet spots for group vocals panning the reverb L or R, but this is no longer possible as I can not only hear it, but I see it on the meters staying pegged to the center.  
 

I don’t know if it’s a bug or maybe I have a few gremlins wrecking my computer.   If no one can recreate the problem, I will try to do the thing with the motion graphic image thing…u know the thing!

Share this post


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

Sends inserts in console view do not pan any more, nor do they “Follow Track Pan” when POST is enabled.  
 

I noticed a couple of weeks ago that something was starting to sound off in my mixes as they sounded washed out and cloudy.  I put it off on thinking I was just exhausted or perhaps I made an accidental change with my effects but, after taking time to finely comb through settings, I discovered the issue with the panning of sends.

I solo’d the stereo vocal track, put the reverb insert send on PRE then turned the track fader down to hear only the vocals reverb.  I always do this to find the sweet spots for group vocals panning the reverb L or R, but this is no longer possible as I can not only hear it, but I see it on the meters staying pegged to the center.  
 

I don’t know if it’s a bug or maybe I have a few gremlins wrecking my computer.   If no one can recreate the problem, I will try to do the thing with the motion graphic image thing…u know the thing!

Still works here in 2021.04.175

Try a reinstall.

Share this post


Link to post
Share on other sites
On 5/22/2021 at 10:06 AM, scook said:

Not my experience at all. I have applied every update since CbB was released, some several times using the rollback installers.

Not once has it been necessary to perform a clean install or reconfigure CbB.

Also, I do not run CbB as administrator, never have.

 

That's been my experience ever since I've first installed CW - 2019.07, I believe.

I don't have to run CW as administrator, but I had to run VSTScan as administrator, from its folder, because it doesn't start in CW.

Share this post


Link to post
Share on other sites
8 minutes ago, Olaf said:

I had to run VSTScan as administrator, from its folder, because it doesn't start in CW.

This is a problem.

Vstscan.exe is not designed to run from the command line.

It should always be run from preferences.

Share this post


Link to post
Share on other sites

And if you run vstscan as adminiatrator, and CbB as a different user, you may not see the VSTs you expect in CbB (depends on if you're elevating or using another account which has admin privileges).

Share this post


Link to post
Share on other sites
Posted (edited)

Using Arranger View to move sections around deletes the first tempo node in the tempo view

Dy9N25a.gif

 

 

 

Edited by Matthew Carr

Share this post


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

Still works here in 2021.04.175

Try a reinstall.

@Will_Kaydo My issue seems to be related to working with older archived projects created in Sonar 7.02.  I am working on an anniversary rerelease and pulled up project bundles that were created back in 2009 so I am curious if this might be affected by the pan law bug?  

In a new project within the latest CW release, the panning of sends work so my only conclusion thus far has everything to do with these older project file sessions.

Share this post


Link to post
Share on other sites
Posted (edited)
39 minutes ago, Clovis Ramsay said:

I am curious if this might be affected by the pan law bug?  
 

This could possible. Have you tried changing the settings under preferences to the backward setting of Sonar 8.5 where panning was applied on clips instead of the console? 

Edited by Will_Kaydo

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