Jason Halogen

17 minutes ago, scook said:

This is not a big deal, however; the devs monitor the current feedback thread closely.

Posting issues with the current release in the feedback thread may get a faster reply and a fix, if it truly is a current release issue.

This one, of course, is not unique to 2021.12.

Totally get it - like I said, long-time user, seldom poster. I actually worked there in another life. BTW, Chris B. says hi.

2 minutes ago, scook said:

An easy fix. Glad it worked for you.

This is not new. The problem started in 2013 with the release of SONAR X3.

At that time, the default for "Enable MIDI Output" changed. Any synth capable of sending MIDI data has "Enable MIDI Output" turned on.

This along with "Always Echo Current MIDI Track" defaulting to enabled caught many users. This setting changes track inputs to Omni if they were set to None. 

Starting with CbB 2021.01, if a project contains any plug-in with "Enable MIDI Output" turned on, instead of switch None to Omni, the DAW switched to All External Inputs Omni. a new input option. This way the user has to actively select an input capable of picking MIDI from plug-ins.

 

 

 

Yeah, I skipped X3, I think. I'm actually surprised I never ran into this before! Anyway, thanks so much. And I'll try to post something in the right place next time I have an issue.

8 hours ago, scook said:

Often the result of the record enabled track input set to "All Inputs - MIDI Omni" and a synth plug-in with "Enable MIDI Output" turned on. Change the input and/or check the VST2/3 drop down in the standard header above the plug-in UI 

This was exactly it, thank you! In almost two decades of using Cakewalk DAWs I'd literally never come across this problem before, or even had a compelling reason to pull down that menu. Thanks again.

4 hours ago, bdickens said:

What "attitude?" 

Nobody else seems to have this problem.

Nothing in your OP indicates you have any experience whatsoever with DAWs at all, let alone Cakewalk. Your whole post screams newbie and your issue is the exact sort of thing that happens to people who don't bother to RTFM, start stumbling around blindly and then don't get the results they expect.

Here's one of many songs I've produced, in Cakewalk. I've recorded dozens of records for my own projects and others, in Cakewalk, not that it matters... In my experience, people come to help forums because they've got an issue that they think might be easily fixed by interacting with other people, which is what I did, and in my case it was a simple part of the program I'd never had to deal with before, and someone quickly and easily pointed it out. *shrug*

Fun side note: You were wrong, it was a setting in the synths that I'd never dealt with before. But still, I appreciate your suggestion.

Not sure where the attitude comes from, but it's on an awful lot of your replies in these threads, and it's a shame that it's manifesting in a help forum. Hope you like the tune.

https://youtu.be/e7kfr_LWvtc
 

1 minute ago, scook said:

I doubt it is related to 2021.12 but there is an easy way to test. Roll back to the previous release and see if the problem still exists. For some time now, a rollback installer link is in every release announcement.

When encountering issues known to be related to the current release, the best approach is posting the problem in the feedback thread for the release. Here is the feedback thread for 2021.12.

 

appreciated, and sorry if I'm posting in the wrong area. Long time user, seldom-if-ever poster.

7 hours ago, IgoRr said:

@Jason Halogen

This has never happened to me and never happens, although my keyboard is different. But I'm pretty sure your problem is that you've set the wrong MIDI input parameters on the tracks. You need to select for ALL tracks "Oxygen 88 Omni", almost completely sure that your problem will be solved. In addition, you should definitely arrange the outputs in all MIDI channels on each track by ascending numbers, because of this, confusion can also occur.

thank you, that's how the inputs are set - outputs are simply routed to the corresponding synth. I'll look into this as well.

2 hours ago, scook said:

Often the result of the record enabled track input set to "All Inputs - MIDI Omni" and a synth plug-in with "Enable MIDI Output" turned on. Change the input and/or check the VST2/3 drop down in the standard header above the plug-in UI 

Thank you, I'll check this out! It's a new issue, and I've been using Cakewalk products for about 19 years.

7 hours ago, IgoRr said:

@Jason Halogen

This has never happened to me and never happens, although my keyboard is different. But I'm pretty sure your problem is that you've set the wrong MIDI input parameters on the tracks. You need to select for ALL tracks "Oxygen 88 Omni", almost completely sure that your problem will be solved. In addition, you should definitely arrange the outputs in all MIDI channels on each track by ascending numbers, because of this, confusion can also occur.

thanks, I'll look into this - never happened before Dec '21!

3 hours ago, bdickens said:

Not to be an *****, but the solution is to utilize the doccumentation, maybe watch a tutorial or two and learn how to do things before just winging it and getting frustrated....

This is happening because you don't have your MIDI channels set up correctly.

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Dialogs2.058.html

 

I've been recording and releasing music made with Cakewalk products since 2003, so while I appreciate the advice, the attitude really isn't necessary.

This is a huge problem, hopefully someone has figured out the solution. 

I'm setting my MIDI input on new tracks to just the controller (Oxygen 88, in my case) and when I start to record a new synth performance, MIDI data from *other MIDI tracks on other instruments* is being automatically printed into the new MIDI track. Obviously this is a terminal issue. I can't be laying down a drum pattern and have the nice atmospheric synths triggering different drums on playback unless I go in and meticulously erase every note that was somehow imported from the other tracks.

Anyone else having this issue?

On 4/7/2019 at 10:42 PM, James Argo said:

Num 0 switches CbB into Keyboard Navigation mode, it somehow disables default key binding for nudge & clip splitting.

DEAR GOD thank you.

Thinking about it as I typed it I don't think it'll be an issue, because all I'm really doing is changing the signal flow... but still. Advice or experience welcome.

Heeeeeyyy, I have a question for y'all.

Thinking of picking up a small MIDI keyboard to bring to work (I'm blessed with downtime and privacy). My satellite setup is a nice laptop and a Focusrite Saffire 2i4.

My concern with getting a directly connected USB keyboard is that the additional processing required to take in the MIDI data will mess with the Saffire, since it's already got its own MIDI inputs. I could have this backwards, the USB3 connection might actually provide faster response time than the old school Saffire, but wanted to throw it out there and see what people think.

Thanks!

I forgot to post any type of update! So... after I plugged in the external (Scarlett 2i4, my "little" converter), it worked fine. But strangely, when I tried to run CbB again without the Scarlett, it STILL worked fine. 

It almost seems like the presence of the Scarlett made the internal soundcard feel like such a punk that it went back to school.

Well in that case, I'm proud to contribute. :)

Folks, I appreciate your attempts to help me navigate what turned out to be a total brainfart.

Get this.

After nearly 2 decades working in DAW environments, I forgot to plug in an external sound card of some kind. Plugged in my Focusrite and the problem is 100% solved.

Is there any way to delete a post out of embarrassment?

Hello. 15 year Cakewalk user, mostly happy with CbB. I just picked up a new laptop, Dell G5 series, 6 cores at 2.6 Ghz, 16 MB RAM, dedicated graphics card, SSD, etc. 9th Gen Intel i7 processor.

In CbB and ONLY in CbB, any mouse movement tracks fine on the screen but a mouse click has a solid 3 seconds delay before response... for example, if I click on the timeline it'll take 3 seconds for that click to register and move the cursor. It's a brand new install.

I'm having a hard time believing it's the machine. Any ideas?