Variorum

That stability may be why the API isn't public. If you get a bunch of knuckleheads (ahem 🙄) writing faulty PC plugins, then Cakewalk starts locking up/crashing and the users complain about the lack of stability and blame it on the fact that free software is buggy and Brand X DAW is so much better...

They'd probably want to implement a QC procedure on any plugins and that takes time and costs $$$

Still be nice to have it available, though... all of my code is perfect and never crashes 😎

I think the API for the Pro Channel interface is proprietary... if it's been published, I haven't seen it. I'd guess that companies like Boz and Softube requested the docs or had a partnership of sorts to develop their plug-ins.

But if it were to become available... 😁

Just as an aside, in this video, the guy is testing Behringer's ASIO Driver for the Zenyx family devices (available here) with the UMC22. Apparently the ASIO driver works with the UMC22 even down to a pretty respectable latency. Might be worth a try if you want to keep the UMC22 as a backup interface.

Here's an updated version of CSMultiCompander called... CSMultiCompanderV2!
The same functionality is available, but it uses a Spline Curve instead of the sliders... should be more intuitive.
It's a different component than the original version, so any previous presets you've saved won't apply to this one.

It's also effectively a replacement for CSResponseCurve since it contains the same functionality (better, actually... fixed some minor issues)
When it's in Velocity adjustment mode, hitting keys on your Midi device will display an indicator of the velocity in the window (just for @ZincT 😁)

Get it here.

2 minutes ago, Max Arwood said:

Thanks for the articulation editor.

NP... It could do a lot more with a little work, but I really have no idea what would be useful.  🤷‍♂️

I whipped up a little Articulation Map Editor that should solve your Transpose problem 🙂

It's a hidden page (not available from the main page) because I'm lazy.

Get it here.

Excerpt from website...
The only functionality included in this version is Transposing Note events. This covers Articulation Maps that control key-switches.

Select the Articulation Map you want to modify in the Articulation Maps panel. All Groups contained in the map will be displayed in the Groups panel. Click to select one or more Groups to modify. You can use standard Windows controls (i.e. Hold Ctrl to select/deselect multiple items and hold Shift to select a range).

Set the amount to transpose each note/key using the numeric control on the right. The range is +/-48, which is 4 octaves up or down.

Click modify to start the process. The first time an Articulation Map is modified, the program will save a copy with the added extension “.orig” in the same folder, just in case. A message box will pop up to confirm the operation.

If the selected transposition causes any note range to go out of bounds ( less than ‘0’ or more than ‘127’), the program will notify you of the specific articulations that would fail and abort the entire modification operation without changing the file. If this occurs, you may need to modify the articulations individually in Cakewalk.

On 12/19/2021 at 9:18 PM, Max Arwood said:

Very nice. I’ll check it out. I know it will be good!!

Only good for a specific need, but nice to add to your collection 🙂

13 hours ago, ZincT said:

One suggestion/improvement is that you could show a vertical line on the graph representing the velocity of the last key pressed (like Arturia Piano Velocity Curve) so it is easy to see where a key press appears on the response curve.

Wellllll... That would be a good idea, but this plugin only affects CC's, not velocity 😜

I'll probably make a revised version of MultiCompander that uses my new spline control. I'll make sure it shows pressed keys when modifying velocity... 'cause Arturia does it! Not to mention theirs looks prettier than mine.

Hey @gmp,

I made a dedicated response curve MidiFX that might suit your needs a bit better. Check out the post here.

Here's a specialized plugin for adjusting the response curve of a keyboard control (ie. Volume, Modulation, etc,) called CSResponseCurve
Of course, you can  use it for any CC, I just made it to address a specific issue raised by @gmp to balance volume response between an external keyboard/TG and a VST.

Download it here as usual.

Hope it works!

21 minutes ago, gmp said:

I installed it and l added the DLL and it works very good in real time with the volume pedal.  All the changes you're working on sound very good and useful. Thanks for all your help

No problem. I'll try to finish up the final version soon...

11 hours ago, User 905133 said:

Will the algorithm (log v. linear) be switchable? Are you moving in the direction of selectable curves?

Probably not switchable in this plugin... a log response will just be a little more "natural". I may split this plugin out to a dedicated Response Curve MidiFX that will use a simple spline curve or a linear line.
Any plugins after that will likely be VST-Midi plugins... unless Steinberg completely cripples it in the future 😬

I made a couple modifications to MidiCompander to get rid of the glitch and display a more meaningful graph when it's set to anything other than Velocity.
I'm working on changing the algorithm to be logarithmic rather than linear for CC's, but if you want to try out this interim version you can download it here. You'll probably get the "This type of file may damage your computer, blah blah blah" warning because you're downloading a DLL directly. You can ignore it...
If you just copy it over your existing CSMultiCompander.dll file it will work... you won't have to uninstall, re-register, etc.
It would be best to do this when Cakewalk isn't running

Select the Ctrl Chng button and type 7 into the box below it to modify Volume.
Move the High, Low, and Offset sliders and the graph will show you how the Volume will be modified.
You can stomp your volume pedal while playing your keyboard to test your adjustments in real-time.

I'll update the plugin on the main site when I've finished the log modifications.

The MIDI buffer delay only applies when you're playing back an existing (recorded) track. Real-time input (if you're playing your keyboard) is passed to the VST (or passed back out) instantly.
MidiCompander can be used to balance the response curves to multiple instruments, but it can have an annoying "jump" at the bottom or top of the range. I'll see if I can smooth that out.

Guess that explains this 👀

Might want to look at Godfazer. It'll do phase sequencing plus a whole lot more. It's $75 regular price (still cheaper than most stomp boxes), but you might catch a BF deal in the next few weeks.

Hey @Michael Bauer,

Sorry to go off on a tangent, but it looks like there are M-Audio drivers (Windows 10/64-bit) for your Uno 1 x 1... It should be usable, in case you ever need it.

https://m-audio.com/support/download/drivers/midisport-windows-driver-v6.1.3

I think you're looking for Ticks per Quarter-Note in Preferences...

I wanna be this guy when I grow up...

Yeah, this DNS change wouldn't affect the Cakewalk application authentication. I'd guess Cakewalk contacts a bandlab.com address for that and update info. It would only affect the cakewalk.com addresses (like this forum).

I did panic a bit when it looked like the cakewalk.com address was no longer valid (Eeek!)

It does look like there was an update today, though...

Maybe it was just my machine 🙄

It looks like cakewalk.com renewed or made some other DNS change today. The IP address changed from 201.(something) to 13.92.139.214 and made my Chrome very unhappy. I kept getting redirected to one of those generic search pages 😝

Clearing the local Chrome DNS cache didn't fix it; I had to clear the Windows cache (ipconfig /flushdns). 

Strangely, Firefox didn't have any issues!?!?

Just posting in case anyone else has the same problem... of course, they won't be able to get here to read to solution 🤪

Hmmm... It should be there. The only other possibility might be C:\ProgramData\Cakewalk\Cakewalk Core, but I'm pretty sure it won't be in there.

Just in case you tried searching for the file... I've noticed that using search (in File Explorer) will not find any files in sub-folders if you start the search from the C:\Users\ folder. It won't find the file unless you search from at least the C:\Users\<USER NAME>\AppData\ folder.

The file has to exist somewhere because Cakewalk stores important info about your MIDI ports in it. 

If you can't see the C:\Users\<USER NAME>\AppData\ folder, make sure you have "Hide protected operating system files" unchecked in File Explorer's Folder and Search Options.

Well, this used to be the way to tell Cakewalk to automatically turn off Local Control... not sure if it's still used.

1. In the directory where SONAR is installed, double-click on the TTSseq.ini file to open it. (In the Cakewalk Core directory).
2. In the [Options] section, add the line:     SendLocalOff=1
3. Save the file and close it.
4. When you launch SONAR, it automatically sends a Local Off message to your keyboard.

If you don't have an Options section with the line SendLocalOff=1  in your TTSseq.ini file, you could try adding it, then change the line to SendLocalOff=0

That should disable it (maybe?) 

Make a backup copy of your TTSseq.ini file before changing it... in case I'm giving you garbage advice 🤪

*** UPDATE ***

My keyboard doesn't respond to Local On/Off messages, but I tested the above option with LoopMIDI and MIDI-OX  and it does indeed work.

If SendLocalOff is not in the TTSseq.ini file at all or is present and is set to 1, Cakewalk sends the LocalOff message to each midi device. If SendLocalOff=0 is present in the [Options] section, Cakewalk does not send the LocalOff message.

BTW - The TTSseq.ini file is probably in C:\Users\<USER NAME>\AppData\Roaming\Cakewalk\Cakewalk Core

2 hours ago, PcMacsterRace said:

I have no idea what a "middle velocity section track" is. However, I did find out it's only an issue when I'm playing notes on my Midi controller. For some reason, it works perfectly during playback

Yeah... this is because there's some weirdness in the way Cakewalk processes notes when they're input from the keyboard as opposed to when they're played back from the track. When a note comes in from the keyboard, it's represented as raw (actual) Midi data in the MFX. While there are discrete Note On and Note Off events defined in the Midi standard, most Midi keyboards use a Note On event with a velocity of zero to turn the note off.  That's why the Velocity MFX leaves the note playing when it's played from the keyboard... it passes the note when the velocity is above the level you've set but it filters out the release of the note (same note where velocity=0), so the note stays on.

Notes coming from the track (during playback) are represented by a more complex structure defined by Cakewalk that always has discrete Note On/Note Off elements, so the MFX works correctly by filtering the Note On by velocity level and always passing the (discrete) Note Off event..

It would be pretty easy to write an MFX that filtered notes by velocity range for both keyboard and track input, but you'd still need a separate track for each instrument.