Promidi

2 hours ago, User 905133 said:

Would you be kind enough to post the link to the specific post where this is stated?  Thanks. 

I was wondering the same thing as well.....

This does look like a permissions issue.

What happens if move the “Sound Canvas VA.DLL” file in a new folder outside of the c:\program files folder (Preferable on a separate drive.)

Add this new folder to your VST scan folders and rescan.

You might have to uninstall and reinstall Sound Canvas VA, but perform a custom install and specify this new folder for the DLL location.

I have run the trial of Sound Canvas VA in CbB without any issues.

Personally, I have all my VST2 DLL files in a separate folder on a separate drive. 

For my workflow, definitely Sonar.

On the Track View Menu, select “Options” > “Select Events with Sections”

3 hours ago, jkoseattle said:

Ah, is that what you meant? I was unable to translate "check the setting on that low limit pot" to "turn that little dial on the side", lol

But was that the solution?

This is one reason I still use CAL scripts and Studioware panels.  For things like this.

Pitch bend range is a setting defined in the synth itself.

If you are using a GM/GS/XG compatible synth, then inserting an RPN 0 > 1536 in your MIDI track will set the given track’s bend range to 1 octave.  This also works in TTS-1 (if you still have it).

2 hours ago, jad said:

I used to have it in an old version and I liked the way it sounds. Hoping I can recreate it or something? Thanks!

Here you go.

Drum_Destroyer.ini

Use the VST2 version, use Program change MIDI Event.

Personally I would just skip the fluffing around and just get a new pedal.... 

6 minutes ago, sjoens said:

Not sure but it sounds like I got 2 different answers??

MIDI does not store offsets of any kind. 

However, when Cakewalk exports or saves a MIDI files from a project that contains time offsets (from articulations or track time offset parameters), the actual positions of the MIDI events themselves in the MIDI file will be changed to reflect those offsets.

When I saved the project as a MIDI, the temporal placement of the MIDI events themselves were changed - that is, the offsets were baked into the actual MIDI events in the file.

I actually tested this before answering your question.  I added an articulation map that produces an offset to some MIDI events.  I reloaded the resultant MIDI file into Sonar.  The MIDI events themselves were offset.

On 3/21/2024 at 10:57 AM, sjoens said:

Does this translate to exported MID files that can be played with another sound source or does it remain exclusive to the Cakewalk project?

Yes. All articulations that are present translate to exported and saved MID files (That includes time offsets).

27 minutes ago, jkoseattle said:

Thanks for the advice. I installed ShowMIDI as instructed, and it worked great right away. What I learned is that the expression pedal does generate CC11 through the it's entire range of motion, but the range of messages only go from 83 to 127. So pressing the pedal from bottom to top will generate messages starting at 83 and going up to 127. This agrees with what Cakewalk is recording. The pedal itself is sending messages through its whole range, so it doesn't appear to be a physical issue, just that it won't send anything below 83. 

So now what?

Which range of values is ShowMIDI standalone displaying.   83 to 127, or 0 to 127?

29 minutes ago, Eric Parsons said:

I'm not familiar with converting a midi file.  Is this easy to do?

Very.

I used GNMIDI to convert these groove files.

However, if you don't have GNMIDI,  Cakewalk can do it. 

Simply open these groove files in Cakewalk (open, not import). 

Delete the surplus tracks (1 to 9), so that the MIDI Events are on MIDI track 1. 

Change the MIDI channel of the MIDI track if necessary.

Then Save as MIDI type 1.

See:

http://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x18A8C

I actually prefer the way Cakewalk handles Type 0 MIDI files.  Maybe a setting in the TTSEQ.INI file to do what you are asking.

FWIW, maybe put in a feature request, you can do so here:

https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/

Note: Even though CbB is no being developed and no new features are being added, the Bakers might still look in here for candidates to add to the new Sonar.

Until then, simply convert to type 1.

No

It's because of the way Cakewalk imports (or opens) type 0 MIDI files (which these groove MIDI file are).

The MIDI events in Type 0 MIDI files are all one track.  When Cakewalk imports type 0 MIDI files, any MIDI Events that are set to different MIDI channels, get split to their respective MIDI tracks. 

The MIDI events in these MIDI grooves are all on MIDI channel 10.  Because of this, Cakewalk create a MIDI track 10 to correspond to the MIDI events in these grooves.   It has to create MIDI tracks 1 to 9 to fill the gap.  Numerically and ordinally, you cannot start at the 10th track.

The reason for MIDI channel 10 for these grooves is because back in the day of Roland GM/GS (and Yamaha XG) , MIDI channel 10 was usually reserved for the percussion track.

I converted these to type 1 MIDI files which, when opened in Cakewalk, created a single track and then set that track’s MIDI channel to 10.   No other MIDI tracks were created.

7 hours ago, Jaga said:

Have the same issue. Haven't found a solution yet.

Create an account here: (If you have not done so already)

https://www.bandlab.com/sign-up

Then use the Cakewalk Product Center to install.
 

Note: Bandlab Assistant is no longer used to install Cakewalk by Bandlab.

4 minutes ago, Noel Borthwick said:

We’re looking into other package options. Anything like that involves back end, and has a lot of other moving parts which is why there is a delay in information being made available.

I am very confident that this is a case of “All good things come to those who wait”....

I have no doubt that this whole thing has many moving parts....  there is also change management to consider...

24 minutes ago, Alan Bachman said:

I do not mind the subscription or plan idea at all.

I would rather have a perpetual licence - a similar way that Sonar Platinum was offered (before the lifetime licence was offered). 

Making 12 consecutive monthly, or one annual payment, gives you a version that keeps working.

If any updates are released while you have an active membership, you have access to those updates.

If, after the 12 consecutive monthly, or the one annual payment, you decide to stop renewing your membership, then you keep the version you had when you stopped renewing.

What I definitely would not like is for the only way to keep using Sonar is via membership.  I think that would annoy a lot of users.

Can any of the Cakewalk devs tell me if Cakewalk by Bandlab reads the registry entry “UseGraphicsHWAccel” under the key “HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Sonar” if upon start up?

My instinct is telling me to set this to 1.  However, I am not sure if actually reads this key upon start up, or if this key and value is a carry over from older version of Cakewalk.  

When it comes to CbB, 29.9.0.98 = 2402.98.  It’s just a different numbering system.

For those who use OBS Studio to do screen recordings of their Cakewalk session (or just PC screen), OBS Studio has been updated to 30.1.0.  (Click on “Windows” to download)

https://obsproject.com/ (Click on “Windows” to download the installer)

On a side note, if you wish to record using ASIO mode from inside OBS Studio, you an use this ASIO plugin to do so.

obs-asio v3.2.0

https://github.com/Andersama/obs-asio/releases/ (Scroll down to “Assets” and click on “obs-asio-3.2.0-windows-x64-Installer.exe” to download the installer)