cmc qc midi activity spiking

and still no answer form steinberg , o well it’s their lose

Hi,

We are currently investigating this issue.
I just want to briefly explain this functionality that apparently some of you find disturbing:

This feature is similar to the MIDI spec “ACTIVE SENSE” with some extensions. It’s a functionality that enables the CMCs to detect a sudden interruption of data communication and as a result (for example) turns off all lights. This helps users to recognize that their CMC is no longer controlling Cubase when the connection has for what reasons ever been interrupted.
From the software side Cubase provides visual feedback that the connection to the CMC is constantly OK. This is what the MIDI meter is showing all the time.

It’s a functionality which has been around for nearly 25 years and that we find is a necessity.
But of course we fully understand that some of you might find the constant blinking of the MIDI meter in Cubase somehow irritating.
We are aware of this topic and we will take a deeper look into that behaviour since there are several other topics related to this that we need to take under consideration as well.

Regarding sysex dumping there shouldn’t be a problem with CMC and Cubase. The visual feedback implies that there are other MIDI data that might affect the sysex data recording if the routings are not set appropriately.

I hope I could give you some more insight and we will keep you up to date.

Cheers,

Thanks for taking it in consideration Stefan :slight_smile:

Thanks Stefan. Yes I know what Active Sense is and what it does. I simply would like to disable the display of it at will. I’d suggest a checkbox in:

Devices → Device Setup → Remote Devices → Steinberg CMC-??

A lot of space is available at the right side of “Enable Auto Select” for an additional “Enable in MIDI Activity Meter”, or whatever you would like to name it (enabled by default).

Many thanks for listening.

Paolo

Well the problem is cubase, and the solution is fairly simple. Have a prefernce settings where the user
can select what should counts as a activity. A matrix per midi port and message type. A other solution is to this in the device-setup-> midi port. And please add add a state for the port (call it system or something) that makes the port hidden. Not like the idiotic function “visable” that disable binding to controllers.

Stefan, thank you for your work to resolve this annoying issue. Wish all the best for you to find a solution.

http://www.steinberg.net/en/newsandevents/news/newsdetail/archive/2012/03/21/article/cmc-update-announced-1905.html

Thanks for the forthcoming update, but: will this midi activity spiking issue be addressed with the update?

Paolo

and fine mode locking! I could plug them back in with on/off control, no endless MIDI activity and the ability to lock fine control. Especially on the QC.

Same old irritating behavior on this issue after installing CMC 1.1.0 :imp: . I’d be very happy to know why addressing this wasn’t possible. Thanks.

Paolo

Just taking a few guesses here:

So they’re not going to remove it.

The change would have to be made on the Cubase side of things (to add an option to not display output of certain types of MIDI data). But then you couldn’t rely on the MIDI output indicator to be reliable (as it’s not reporting all MIDI data output).
The option would have to be don’t report certain data being sent to a certain port.
But it’s still something in Cubase, not the CMCs or the CMC extension.

A lot of Midi instruments continuously send MIDI active sensing (certainly, almost all my instruments do: I can see that through my amt8 MIDI interface leds). Cubase MIDI input indicator never shows that, and I certainly have never ever had any problem with that… Why that should be different with CMCs?

well this is getting annoying as i like the cmc series and am thinking of buying some more BUT the bloody midi indicator still needs to be sorted how many months later ?

So they missed a chance here.

I know that my beloved old Kawai K4 - I use that nowadays only as a keyboard, but no more producing sounds -
emits all the time MIDI active sensing - that drove me crazy, when I wrote my own MIDI processing software
but I never saw that in Cubase - since Cubase 1.0 on my ATARI ST.

Why is it so difficult to put a filter into the driver?

whole lotta bump

I have also requested this “feature” to be selectable:

This problem only occurs in my Win7 64 setup, not on MAC. But on MAC the devices aren’t even recognised, which is a completely different matter :unamused:

well it looks like we are not going to get an answer on this ,mind you it loks like steinberg have abandoned the forum just like they have abandoned certain hardware :unamused: :unamused:

Unfortunately, we got an answer (a disappointing one though):

The “spiking” of midi-signals" is not a problem but a feature by design. You should not turn off the CMC’s midi output. You can however hiode the MIDI activity meter in the transportbar.

It seems they are not even considering our request: please Steinberg, don’t remove the “feature by design” if you like it, just make its display switchable (on/off) for us who find it extremely irritating!!! Please!!!

As we are “only” at release 1.1 yet, I will wait for a possible next software or firmware release.
If by then these problems are not yet solved, the bidding can begin! Two CMC’s will become for sale after that!
I have gone used to using my keyboard for the functions the TP has to offer and as far as the QC is concerned … never had the pleasure to experience what aspects of living with Cubase they make easier.
Sorry but I’m not a Guinea Pig.

It’s been a long time since I bump and rolled

Yes, stop the CC121 midi activity thumping.

It’s ridiculous AND redundant since the blue “Cubase Ready” light on the console tells you if communication is active.