Jimbob Blues

18 hours ago, reza sadeghi said:

Guys,

Is there a workaround for installing VS-700r on Mac OS 13 (Ventura)? 

If I can't find a solution I will sell the whole set.

This post will walk you through getting the drivers to work with Windows 10 http://forum.cakewalk.com/How-to-use-V700-win-8-driver-in-win-10-also-applies-to-some-other-Roland-drivers-m3206046.aspx

It does work but to be honest, its buggy. I've had CbB shutdown unexpectedly while working on projects, it's not Cakewalks fault it's the fact that Windows is using older drivers to run the VS-700. So you can try it but don't expect it to be perfect.

*** I just noticed that you're working on a Mac, sorry

"I am a bit tired of these circular 'debates"

"stressing over things out of our control is truly a waste"

Couldn't agree more

"Can someone define 'Soon' in musical terms?"

No

We're not going down this road again, are we? Please don't.

This horse just will not die, will it?

So with the new version will I have to pay for it? How much will it cost? How do I activate the older versions? Will it still work in Windows 10?  Will I have to buy a new computer? What kind of computer should I buy? Why haven't I ever found any bugs?

On 6/10/2023 at 2:52 PM, Lord Tim said:

See, this is my reasoning for a lot of the complaints too. REAPER is a great example for me - it's a fantastic DAW but man, do I ever plod in it because it just doesn't agree with me at all as far as workflow goes. I do marginally better in Studio One, but I keep returning to Cakewalk because I'm super fast in it and nothing (for me at least) gets between my brain and recording the idea (questionable talent notwithstanding 😒).

There's definitely areas where CbB can be improved, of course, and I have a few thoughts about that also, but it really seemed like there was suddenly a bunch of people who have been biting their tongue about them because of the free thing, and now it's a problem.  Are those things more than preferences? What am I missing?  That's the question!

Thanks Mark, funny how you can look at something almost everyday and not notice the little things.

I noticed the other day that if a plugin is in an fx chain module the ACT button is missing when the plugin is open, if a plugin is in the fx rack the ACT button is visible. Has it always been this way and I just never noticed or has something gone goofy with my template?

I've had it working for a few months. I had some plugin issues at first but not related to the VS-700.

I upgraded to Windows 11 yesterday (with much hesitation) and discovered a few things. The first was the VS-700 will work infact the drivers loaded much faster than they did in Windows 10.  Here's the but, several projects that I tried to open cause CBB to close and even trying to open the same projects in Sonar Platinum have the same effect. I haven't had much time to dig into it but will do so this evening and hopefully I can find a resolution. I am very happy that the VS-700 works but it's has a few quirks also in that when opening CBB it says there are no audio sources but on the project I can open it works perfectly. The frustrations of using Windows, I think a Linux version of CBB would solve a lot of problems : ).

I love mine. I turned off automatic updates for Windows because every once in a while the updates would give me grief but it's a great console. If it had more pro-channel control that would be great but I still love it. 

Some opinions may vary, some assembly required, batteries not included.

5 hours ago, Moving Air Productions said:

I'm not a programmer and fully admit I have no idea what would be involved with this process, but I was wondering if Cakewalk by Bandlab has ever considered upgrading the plugins that used to come with Cakewalk (like the Tube Leveler, Boost11, Percussion Strip, Vocal Strip, etc.) to VST3? I think some tweaks to these and getting them up to today's standards would be an excellent addition to the modern Cakewalk.

Thoughts?

I agree, I use a few VST2 plugins that I would like to see "upgraded". I too am not a programmer and have no idea how difficult it would be to accomplish but it would be nice.

And of course that worked because it makes perfect sense. Thanks.

I have a guitar track with a send to a bus and in the bus I have several effects. If I mute the track I can still hear the bus with the effects when I play the project. It's kind of annoying, is there a work around for this? 

4 hours ago, Max Arwood said:

I can not believe how well my system is running with EA2! Noel did some magic programming on this version.  I have not run without glitched and crashes since I upgraded to windows 10.  I was also having an issue with Lexicon PCM reverbs,  All that is gone now.  All the rough playback - smooth now.  I will have to say that these projects were loaded! Ball park of 55+ tracks with 64 plugins on the busses , 100 on tracks -all active and another 45 frozen VSTs.  5 soft synths -  B4 II, CFX Grand, Superior 3, Kontakt 5 and Omnishpere (Some frozen)  Unbelievable!

Noel - I don't know how you sorted through all that code so fast and fixed all this - GREAT JOB!!

Many Thanks To a Great Team!!!!!

Max Arwood

Agreed Max! I don't use midi very often and was having latency issues a few months ago, tried it this afternoon and worked like a champ! These guys are awesome!

21 minutes ago, User 905133 said:

You have the Basic workspace; change that. See the image here--no screensets in the Basic Workspace.

 

Fixed. Thank you, it's the simple things we overlook.

10 minutes ago, User 905133 said:

The issues I described have not gone away; they are reasonably consistent; I am trying narrowing it down. At least with the projects I am using on my PC, they might be related to the drawing of VSTs, possibly specific VSTs or specific VSTs from specific manufacturers.  Or, it could be related to some changes I did to my PC: (1) removing virtual desktops and/or (2) under privacy settings denying permissions for apps, such as camera, mic, location, etc.

I rarely use screensets and have the ability to explore work arounds. I was curious when I saw the screenset issue post and found I also had it under the newest Early Access Release.  I am used to other issues with Cakewalk that go unresolved, so it is not a major issue for me. The nature of bugs can be elusive--sometimes they show up, sometimes they don't.

I have no doubt that 99% of users might not have a specific problem.  

As for me, I will roll back to the last working non-early release and re-test the files I have been testing the screenset issue. If I don't have these issues, I will put a post-it note on my monitor not to accept any newer versions. 

If I find a work around, I might share that.  So far, for me the FX VST Control Bar lock up I have been experiencing this morning can be resolved my minimizing the plug-in and then docking it in the Multidock. Unfortunately, that locks the FX VST into a cutoff mode.  There are several work arounds for that--such as deleting the plug-in and inserting it again.

If I can create a new project with a non-third-party paid plug-in that distributes the issues, I will share it.

To be clear, as I originally stated (i.e., the reference to Project A and Project B), I have also been able to open some projects and not have the screenset issues.  On my PC, it only seems to occur with some projects. I am now officially bored with trying to isolate the problem.  😉 

Apologies to those who have no issues with screensets.

I opened four older projects and the screenset module is not there (see pic).

I ran the rollback - module not there. I uninstalled and re-installed CbC - module not there. I still have Sonar Producer so I ran it and the module is there (see Pic).

Not sure whats happening?

6 minutes ago, User 905133 said:

Preliminary observations: This is odd. I was on EA1, verified my current project [A] had screensets, rolled back to the previous version, updated to EA2, loaded the same project [A] and found the screensets module did not seem to work at all.

I loaded another project and found screensets were there.

Then I switched to the first project [A] and the screensets from the second project persisted, but I was able to switch them and get the screensets from the first project [A].

It does not seem to be a user workspace issue because my workspaces is set to "None."  This is odd.

I will try several more times.

UPDATE 1: I reopened project A. Hovering over buttons in the screenset module shows names for screensets, but the buttons do nothing.  I will test for the effect of a custom theme as the possible cause.

 

 

  

I didn't try opening an older project. On my most recent project the module did not exist. I will try to open an older project tomorrow. Thanks for your response.

Hopefully it's just me but the Screen Sets are missing. I did run the Rollback and then installed the newest version, maybe I need to do it again? I do love that Screen Set option.

On 12/11/2019 at 8:31 AM, siordanescu said:

 

Noel, the version ... 63 is not installed , over the one I have ... 54. I did an update through the band lab assistant and it tells me that the update is only installed over the version ... 54. But I have the version ... 54! I checked!

Did this get sorted out? I have the same issue.

My hats off to everyone at CbB for all the great work you've been doing! It's so awesome that your focus is fixing bugs, Cakewalk is truly becoming a fantastic DAW and I'm exited for it's future! Great job!!