User 905133

I never looked at the patch list from the console before, and I haven't used patch lists much in recent years, but I took a look using TTS-1 and between the bottom of column one and the top of column two, I am missing one preset. Nothing missing from the bottom of column to to the top of column three. This was just a quick test, my windows display setting is at 100%, and the console patch list goes from the top of my screen to the bottom. Not sure if its off my screen, though. BUT WAIT!!! I just slid CbB to my second monitor which is smaller and has a different resolution size so things look bigger on that monitor. Column 1 goes to 36, column 2 starts at 54. Column 2 goes to 91, column 3 starts at 108. I don't have time (nor am I awake enough) to problem-solve this, but I hope something here helps. At least you know its not just you. UPDATE: I lied. I thought of a quick test. On Mon 2, I changed the display resolution to the recommended size (which makes it too tiny for my old fart eyes), but column 1 is now None --> 52, column 2 is now 54 --> 107, and column 3 is now 109 --> 127. UPDATE 2: Another quick test; changed display resolution to 800 x 600. Everything is too big and distorted, and not much fits on the screen, but BINGO!!!! The console patch list is as follows: Column 1: None --> 28; Column 2: 54 -> 83; Column 3: 108-> 127.

From page 1: In case someone who has a licensed copy of z3ta+ 1.5 (the version that has a dll to use it as an FX processor) is trying to get it to work, there is a discussion of this several pages back along with links to some useful SOS articles.

Are you grabbing the tracks in the right spot and are you watching carefully for the cursor changes? It can be a little tricky at times.

There are also other programs that use the spp file name extension. The above discussions are not about about those. Most of the references I found relate to images, for exampe:

@tulamide I totally get that you want to be a fierce advocate for the CLAP format. I think you made your point very clear: You feel very strongly that the Cakewalk developers should add support for CLAP.

I don't need the older SONAR products, but I keep some of them around, sometimes to check how features worked (to compare with CbB), sometimes to find older projects, etc. Anyone who didn't pay for them and never had them doesn't need them to use CbB. If someone has projects that were made using an older version of SONAR that they paid for, they should be able to open the older projects and use them in CbB, but if it were me, I'd make a copy of the older project file to open in CbB and then resave it to preserve the original just in case there is an issue. Did you pay for older versions of SONAR that included older plug-ins and can't get the older projects to work in CbB? If that's what you are trying to get at, you should start a new thread to ask for help. Are you asking if other people who paid for older versions of SONAR need for those older versions to be available for free?

I wrote this up yesterday but didn't post it. However, in addition to non sequiturs (in the guise of logic) you also seem prone to misinterpretation: I can't speak for anyone else, but my first reply was not made out of "fear of another plugin format." Neither is this reply. I just re-read the other posts and I don't read such fear into any of them. That being said, I do have a strong distaste for people who use emotionally charged language and spurious reasoning to try to rile up others for the purpose of making cases for their own personal preferences. You have done that (1) with your non-sequitur and (2) by attributing responses to fear. In my opinion, it is OK to have personal preferences (such as choosing to use or to not use CLAP or even to express hope that the developers will consider supporting CLAP in the future if they haven't done so already), to express that those are personal preferences, and even to inform others of reasons for making a personal choice. I also think its OK for people to state why they find no personal need for something you want and even to suggest other options. Because Cakewalk is free and because you personally want to use CLAP, you seem to believe the Cakewalk team should immediately drop everything to implement support for CLAP. That is what you are really saying. To advance that position, you use a non-sequitur and claim people who responded to you are afraid of the existence of CLAP as a plug-in format. Here, you seem to be using the veneer of logical argumentation. However, you are the one who is afraid that you might not get what you want. By overlaying fear on the people who replied to you, you actually risk alienating people who might otherwise be open to using CLAP plug-ins in the future. Again, I don't see any replies that state or imply that people don't want variety. I can understand that you and others want the CLAP format to succeed. However, I think your approach as an advocate for CLAP is inappropriate and runs the risk of backfiring. Years ago, I was looking forward to a day when there would be a better alternative to Virtual Steinberg Technology (yes, I know the S is supposed to be for Studio). However, it seems that fans of the CLAP format have been going out of their way to be aggressively obnoxious. I cannot imagine the Cakewalk team not being aware of the format, and I trust that if they feel it is in the interest of their users and can easily be successfully implemented within Cakewalk in some way, they will.

Good news about the IK Product Manager Crash: I just got the exact same pair of error messages above. Background: I finally got an external 2TB SSD and was running the IK Product Manager to download all the IK sound files to my trusty 6TB HDD. It has plenty of room still. My plan was to install the sounds to the new SSD and backup the downloaded zip files to DVD RAM disk. Even the largest IK zip file is less than the DVD-RAM size. I have been keeping track of the zip files and already noticed a handful of files didn't get downloaded (i.e,, there were consecutive gaps in the part numbers--even though the time for each actual download was consistent). I call this good news because to me independent confirmation of an issue is good. Please note: I am just reporting this in case anyone finds the additional confirmation useful. I will most likely go back to downloading all the sound files part-by-part. In my experience, that method of downloading and then installing the sound content is more reliable. Since it is a relatively new version of the IK Product Manager (from a few months ago), I thought I'd give it a try. I suppose its possible that for some reason the Product Manager didn't download all the parts and when it went to install the files, the error was triggered because the file wasn't on my PC. I have never coded anything in javascript, so this is just a wild guess. It could be any of a number of other things, too. I looked up "javascript error uncaught exception ebadf bad file descriptor, read" and while there are some discussions of this issue, it's all Geek to me. 😜 PS: Forgot to mention something: FWIW, the IK Product Manager also says, "Install failed" for "ST4_MAX_Sound_Library_Update_1_5.zip."

Sorry. While it might be nice for you and other fans of CLAP to have, your assertion (Cakewalk by Bandlab should implement support for CLAP because CLAP is a free plugin format and Bandlab doesn't charge money for people to use Cakewalk) is a non sequitur.

"GPTChat, Please recode all my DX, VST and VST3 music plug-ins as CLAP plug-ins."

Weird. I tried to create an account and the site said my name was taken. So I tried a different name and the website said my alternate name was already taken and my e-mail was already used. They sent a confirmation link to my e-mail using the second user name (which it said was already taken). So I confirmed it. At one point I was told my password was invalid, but then I found I was logged in. I used the basic SOS website to sign up from cclarry's edited post.

Scroll up a few messages for the latest info. Wait a sec. Let me get you a link. See the first line in this post and also this post.

@Blogospherianman This is a long shot, but if you have MIDI Driver Mode set to MME, without a project loaded, switch to UWP mode. Yesterday I had the same issue (Stop/Pause didn't turn off sustained notes). This morning I tried a number of things with the test project I created yesterday and with the MIDI Driver Mode set to UWP, the sustain notes did indeed stop. ADDENDUM: I just switched between MME and UWP a few times and on my PC the result was consistent with the soft synths I tried.

Suggestion to Cakewalk Problem-Solvers: Before jumping in to help, see this thread: Why? Because:

Oooops. My bad. I forget that there are Mac users here. I haven't used Macs since the Macintosh and the early Performa series. AU is a blind spot for me--my eyes see it but it doesn't make it past that point. Thanks for re-minding me.

I'd agree with this, and based on my very brief test drive a couple of days ago, once I set up the options that I wanted, it was super easy. To me the flexibility of the new version outweighs the additional learning curve. If I recall correctly, the current version of the tempo track (1) has more features and (2) is more like the tempo track than when the new version was introduced.

It looks good from the description / features, but the only plug-in format supported is CLAP. Thanks for sharing. I'd be more interested in the PD if it were iPD. Maybe that will be implemented in future versions.

Did you try Alt + T?

EPIC Synth Solo fore sure!!!! The Alto Sax Solo ain't too shabby, either and the Q/A C/R duet drum interactions are just plain fun. Thanks for posting!! I hadn't seen this specific performance before.

Did you try turning on grid lines and switching the cursor tool to draw (the pencil/pen aka the "Freehand Tool")? BTW, there is an option to use whole numbers when we right-click on Tempo Track. http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Tempo.07.html This is also in CbB's built-in Help. I used "Draw Tempo" for the keyword and then I selected "Using the Tempo Track." PS: Thanks for asking about this. I don't use the Tempo Track much, so this helps me, too.

We can access and insert the images others post. We can even resize them and place them where we want as I have done here: I can also delete them from my post by editing. From what I can see we are only changing the images we have "borrowed." It doesn't look like we are changing the original images, just the characteristics of the copies we have linked. Not 100% sure what is going on. I have done this with my own images, by using a previously posted attachment as a link to the stored original. <<< Copy of image I posted in 2019 reduced.

That does not look like a din-to-usb midi interface cable. It looks like a connector/adapter designed for products from a specific manufacturer for their products only. https://www.sweetwater.com/store/detail/KMICab--keith-mcmillen-instruments-usb-midi-to-5-pin-din-midi-out-adapter-cable

Based on your reply, I have concluded that you never purchased the older products and therefore don't have any proof that you paid for them. I have purchased Cakewalk/SONAR products since Cakewalk for MS-DOS. Many other users like me have the older vst plug-ins because we paid for them. In my opinion, Bandlab has been very nice to those of us for paid hundreds of dollars (or more) over the years by configuring Cakewalk by Bandlab to use the older plug-ins. While you might feel that they should also provide the older plug-ins for free ("not for a fee") for new Cakewalk by Bandlab users, that would be a very generous move for Bandlab presuming they have the legal rights to make those available. Just so you know, several long-time users who have paid for the older plug-ins have requested they be updated. Many long-time users might even be willing to pay for updated versions. If Bandlab chooses to do this, I hope those of us who already paid for the the older version, will get a large discount. Personally, I don't think it would be a shame if those of you who paid nothing for the older plug-ins had to pay a higher price for updated versions. In case its not clear, many of us can use them. If you paid for them but cannot access them because you can't access your account, try contacting support. Maybe they can help.