CTRL + Click randomly does not function correctly, though usually no problem. What gives?

[Benjamin McMullan]

So, the search function returned such generic results I decided to simply ask outright.  I apologize if this has been covered before, but I've looked and not found.

Apparently the oh-so-useful "CTRL + click" mechanism to adjust parameters of multiple selected tracks at once sometimes decides to stop working.  I have not yet been able to figure out the culprit.

In some projects it is just fine and functions as expected.  However, in other projects (and/or seemingly projects in which it had previously worked), it will only change the last track touched, despite multiple tracks being selected and CTRL being depressed while mouse is clicked.  I have noticed that one seems to have to perform this operation rather slowly for it to catch.  The problem is that sometimes, for whatever reason, it simply is not possible.

Has anyone else experienced this and/or is there a real fix?

Thank you all!

[OutrageProductions]

There are TWO CTRL keys on most keyboards. Have you completely eliminated the possibility that it may be a sticky/intermittent/failing CTRL key by using the other one in a consistent manner?

Edited January 28 by OutrageProductions

[Byron Dickens]

This isn't a Cakewalk problem, it's a your keyboard problem.

[OutrageProductions]

8 minutes ago, Benjamin McMullan said:

It is a bug, as verified.  Thankfully the solution is simply to go REALLY slow with certain parameter changes among so many tracks, simultaneously.
Ever hit the save button while playing 64 tracks with numerous plugins?

It's not a bug. It is within the specified timeslices that the clock rate of your CPU & I/O chipset allows.
Even a Cray-3 Vector is not completely instantaneous. Can't break the laws of physics, unfortunately.

Edited January 28 by OutrageProductions

[Byron Dickens]

My apologies as well.

I tend to be very blunt and direct and that doesn't serve me well when I jump the gun instead of finding out more information first.

We have had so many people come by here and blame the software when they're trying to do things like run it on a dinosaur machine that is already breathing it's dying breaths or using multiple instances of ozone and things like that. I made an unwarranted assumption and forgot how to spell assume.

[OutrageProductions]

I used to provide NI input as an adjunct marketing advisor several years ago, and saw the direction that they were headed in terms of design and implementation. I was not impressed, so decided to stop upgrading after Komplete CE V13 & Kontakt 6. If you spend any time on the NI forum, you will soon see that the recent evolutions in both HW & SW have turned out to be an absolute turd farm. It is a well known issue now that Kontakt 7/KK3.x/Mk3 are extremely slow, even after all sources have been scanned into the DBF. Some "in the know" believe that it is due to the recent implementation of the resizable vector graphics. I'm really glad that I saw that coming and haven't upgraded anything in over a year. I've started to add instruments from any other source because of that.

I have scoring templates with 120+ tracks each with individual articulations instituted, then archived until needed using KK as a wrapper (for the NKS VSTi's) and VSL & EW & Spitfire as well. This template loads in about 50 seconds, but I know better than to hit any other key until the cursor stops spinning. And yet, I will occasionally work faster than the machine & slaves can respond, and inadvertently crash the application, tho that is only about once a month. I'm on this thing as a full time gig and have just gotten used to the pitfalls.

Edited January 28 by OutrageProductions

[Benjamin McMullan]

Thank you for your feedback, but I am not a dolt who assumes he knows about my keyboard, Lord Byron.

It is a bug, as verified.  Thankfully the solution is simply to go REALLY slow with certain parameter changes among so many tracks, simultaneously.

Ever hit the save button while playing 64 tracks with numerous plugins?

Yeah, even computers need time to swallow their pride.

Thanks again you guys.

First reply was helpful.  Second is drivel from a condescending vulture perch.  Nothing personal; I have been a troll for waaaay too long myself.  Old habits Die Hard, and sometimes require one to traverse broken glass with bare feet

Peace

[Benjamin McMullan]

To clarify, the issue is not my keyboard.  It is possible that it is my tuned mouse, but only presents as problematic in specific situations with so many tracks and upon adjusting certain parameters.  It COULD be a processor/memory constraint, though my diagnostics and system specs indicate that is not the case.  Perhaps it has something to do with maneuvering too quickly after a project load– before the "somewhat" slow CW has completed scanning all my VST's.  Or maybe, it occurs when a certain pro-channel emulator is changed simultaneously along too many tracks at once for it to digest.

At any rate, as a programmer and blah blah blah credentials blah n qualifications blah blah...

I have better things to do than get down and jiggy with it here

Thank you both, sincerely, for your contributions.  I apologize for letting my mouth run.  I know at least one of you can sympathize with me on this

[Benjamin McMullan]

5 minutes ago, OutrageProductions said:

It's not a bug. It is within the specified timeslices that the clock rate of your CPU allows.
Even a Cray-3 Vector is not completely instantaneous. Can't break the laws of physics, unfortunately.

Sounds important, though I am not sure how relevant.

After further troubleshooting experiments, it seems CW is simply choking on too much too soon after launch.  This is likely because I have it scan for VST's every time.  I guess I could turn that off if I am not actively procuring more at the moment.

To be more precise, the main interface that gives me gruff is the Pro-Channel controls, and specifically the console emulator functions.  Most simple tasks run without issue upon CTRL + click.  The Pro-Channel on/off switches for Tube control, console type, and component tolerance are the exact parameters which work A-OK in most projects, but for whatever reason, will not respond to multi-select and CTRL + click within some projects.   IDK

Again, my apologies for whipping out the real D*CK which I have zero problem becoming whenever shallowly challenged.  I truly understand where we all come from, for better and worse.  I forgive all "slights" and hope the same for all others.

Thanks again~

[Benjamin McMullan]

I think it is important to note that I only seem to have these issues when using Native Instruments plugins within Cakewalk.  Similarly, certain NI plugins cause CW to completely crash and close upon my closing the NI VST window before minimizing it.  IDK for sure, but this seems to be related somehow.  Specifically, Kontakt 7 has been troublesome in this way.

[Benjamin McMullan]

8 minutes ago, Byron Dickens said:

My apologies as well.

I tend to be very blunt and direct and that doesn't serve me well when I jump the gun instead of finding out more information first.

We have had so many people come by here and blame the software when they're trying to do things like run it on a dinosaur machine that is already breathing it's dying breaths or using multiple instances of ozone and things like that. I made an unwarranted assumption and forgot how to spell assume.

No problemo!  I tend to do the same, and have witnessed exactly what you describe.  I do my due diligence before daring to declare that I may be lost, which is why I can be sensitive to being treated like another average bear, so to speak.

It does seem to be an issue with timing/CPU/memory, but not necessarily due to my machine's specs.  This issue usually does not present itself and therefore is not a regular concern.  When it does interfere, though, it can be super frustrating.  The feel of this issue reminds me of having a slower bandwidth connection and trying to click links which delay, then the screen shifts, and before you realize it you're lag-hoppin' toward some strange Singapore website and– ya know... LOL

I appreciate your honesty and hope you trust mine.  Peace, Brother!

[Benjamin McMullan]

12 minutes ago, OutrageProductions said:

I used to provide NI input as an adjunct marketing advisor several years ago, and saw the direction that they were headed in terms of design and implementation. I was not impressed, so decided to stop upgrading after Komplete CE V13 & Kontakt 6. If you spend any time on the NI forum, you will soon see that the recent evolutions in both HW & SW have turned out to be absolute turds farms. It is a well known issue now that Kontakt 7/KK3.x/Mk3 are extremely slow, even after all sources have been scanned into the DBF. I'm really glad that I saw that coming and haven't upgraded anything in over a year. I've started to add instruments from any other source because of that.

I have scoring templates with 120+ tracks each with individual articulations instituted, then archived until needed using KK as a wrapper (for the NKS VSTi's) and VSL & EW & Spitfire as well. This template loads in about 50 seconds, but I know better than to hit any other key until the cursor stops spinning. And yet, I will occasionally work faster than the machine & slaves can respond, and inadvertently crash the application, tho that is only about once a month. I'm on this thing as a full time gig and have just gotten used to the pitfalls.

AHA!

Thank you for your insightful input.  NI (specifically Kontakt 7) is what seems to be the bugaboo in this case.  I have had no other problems integrating my wealth of NI stuff into Cakewalk.  However, Kontakt 7 has caused some real headaches lately.

Thank you both for your thoughtful replies and unique perspectives.  You have each been very helpful.