CMC-TP not recognized, only sends midi note info

Hello All,

My CMC-TP is not recognized as a remote controller in Cubase 6.5. My PC is running MAC Snow Leopard.
The TP’s light is on.
When I touch a button on the TP, it sends MIDI note information.
It shows in MIDI / Midi Port Setup as " Steinberg CMC-TP port 1", both under In and Out.
However, under Remote Devices there’s only Quick Controls but no TP visible.

How can I let it be recognized as a Transport Controller in stead of a (multi key) mini keyboard?

Thanks on beforehand!

Have you installed the driver included in the Tools for CMC software? If not, you can find the link in the post at the top of this subforum.

Thanks for your reply.
I installed all software from:
It installs the driver because I can see and open the Yamaha USB driver. It is seen as a midi input and midi output device.
In Cubase it does not come up as a remote controller.
I am the main user and have Administrator rights. Should be OK.

That’s odd…

Driver seems properly installed indeed, if you can see it as a midi device within Cubase.

If you press the + symbol in the Device setup screen, do you see the CMC devices listed in there? If not, then it seems as if the CMC extension installation somehow failed.

You could try re-installing the CMC software (and just to be sure, also everything included in it), that might trigger something it somehow failed to do the first time. Good luck!

All is removed according the uninstall procedure in the manual. After that re-installed it en it’s the same.
Can somebody from Steinberg help me please?

Which Cubase? Any CMC won’t work on Cubase pre ver 5.5

It’s Cubase 6.5 Full version (latest edition). But that was already mentioned in the first message.
Platform is a Mac Snow Leopard 32 bits 10.6.8. PC is an Intel Core i7-2600K with 16 GB memory and Sound Processing is done by a Focusrite 24 PRO DSP, also taking care of MIDI IN/OUT.

May this problem have anything to do with a possibly incompatible chipset on my Gigabyte GA-Z68XP-UD4 (rev. 1.3) motherboard? It’s equipped with 2 x Etron EJ168 chips.(
They are not on the list of tested USB HUB’s:

This is a screenshot of the problem:


Sounds like a similar problem I had on my iMac. I had to go into OS X’s Audio MIDI Setup and delete an old instance of a CMC-FD before a new one would work (there were too many). It may have nothing to do with your situation, but it couldn’t hurt to see what devices are listed in there. If there’s more than one TP listed, your current instance won’t work.

My other thought is that running a Hackintosh is likely courting trouble. Who knows what weird interactions are occurring at the hardware level between OS X and your motherboard …

Best of luck,


Hai Sector,

Thanks. Done all of that: delete it from AMS, deinstall, reinstall but it keeps coming back as a Midi keyboard rather than a remote controller.
Suspect the USB controller but can’t change anything there.
Hope the guys of Steinberg can give me something to force it to act as it should.



I connected a CMC-QC, together with the CMC-TP. I hoped this one was detected correctly but …

Dear Steinberg and forum readers, what is wrong here and what should I do to let Cubase use them correctly?


JamesTNL is right.
Could you please answer the question? If you press on the + Symbol in the upper left corner of the device setup, do you see the CMC devices listed in the drop down list?


Dear Jan Hendrik,
First of all, apologies to James for not replying all your questions! I had already checked this because if they show up there, I could have simply added them.

If I press the + sigh in Device Setup, this is what I see:

If this helps you with your analysis: the QC-editor does react to changes of the controls i.e. turning it “up” increases the lights in the QC-editor and vice versa (if the editor is changed, the lights change). So there is some communication between the software and one of the two devices.

Any other ideas?

Best regards,

Although the problem is not solved yet, I can add a little more information to it:

  1. As my PC has two “OS-faces”, support from Steinberg is withdrawn. Something to consider if you intend to do a project like this and use Cubase. No support by Steinberg!
  2. MAC OS: Both controllers (TP and QC) work correctly as soon as Halion Sonic 4.x is started in stand-alone mode.
  3. Win 7 64bits: Both controllers work in Cubase 6.5.1 on Windows 7 64b. As mentioned somewhere on this forum, I notice spikes on the midi-out graph on the transport bar every half second. Also, not mentioned before, Cubase takes about 27 seconds to close down after Quit (no song loaded). Without the CMC’s attached it’s 3 seconds to fully Quit. This might be a driver issue in Windows but as far as I know, I’m up-to-date on these.
    In any case, the CMC hardware works. (Both are on firmware 1.1).

I’m bothered by the fact that on MAC OS both CMC-controllers work in Halion Sonic stand-alone mode but not in Cubase. Is there some kind of initiation file in which they could be added manually?
Does anyone owning a MAC and CMC-TP or CMC-QC have this (or these) file(s) available as an example?
Does anyone have a hint on where to look?


You are working with a Hackintosh which we do not support. The issue “Cubase takes about 27 seconds to close down after Quit” is not a common issue. In general when you quit Cubase drivers are signed off and then Cubase closes.

For Windows I would advise you to go through the Optimizing Windows for DAW article.

  1. Please examine your system and make sure that all device drivers of the system are up to date. This involves the drivers of the audio hardware as well as the chipset drivers and the display card drivers. Also Windows XP/Vista/7 should be up to date (Service Packs and updates/hot fixes). You should avoid using dedicated mouse and keyboard drivers, instead use the drivers provided by Windows!

  2. Systems with shared memory display setups are not advisable. They often can be found on mobile systems (laptops).

  3. In the Control Panel -> System -> Advanced system settings -> Performance Settings, you can find the option “Adjust for best performance”. This option should be checked.

  4. Audio interface related settings:
    Onboard sound cards: If your mainboards provides an onboard sound card it should be configured to be the standard playback device in the Windows Sound and Audio Settings. Thus, the Windows system sound will be played back by the onboard device without affecting the audio signal of your audio interface or soundcard. However, if playback issues occur it can also be advisable to deactivate the onboard device in the BIOS of your system. Onboard soundcards cannot be recommended for the usage with our products since they do not allow working with low latencies due to missing ASIO drivers. Furthermore, some onboard sound chips are equipped with substandard AD/DA converters and only offer low signal quality (high noise level, non-linear frequency response, bad electrostatic shield).
    Latency/Buffer Setting: If you experience audio drop-outs or crackles take a look at the “ASIO” part of the VST Performance Window (Devices menu). It indicates how much resources are left to calculate the audio data and forward it to the audio driver in time. If the latency is very low (which is corresponding to a very small buffer size) time might be too short for proper signal processing. Depending on the system, the audio interface and the running project, it might make sense to increase the latency/buffer setting. Please refer to the manual of the corresponding audio interface for details. Updating the audio driver might also improve the overall system performance and allow using latencies which weren’t usable before. Generally, internal audio cards using the PCI or PCIe bus are able to provide lower latencies than external USB or Firewire based audio interfaces.

  5. Any energy saving option should be deactivated or set to “none”. The system should be configured for continued operations. If this is not done, hard disks will throttle in speed or toggle off after a while and some processors will down clock and slow down. Because of this, our products could stop functioning correctly. For current Cubase and Nuendo releases, please see #10 which covers this part.

  6. Programs that are running in background can cause issues while working with our products or even already during installation. These programs are mostly configured to automatically start when Windows boots up, e.g. virus scanners, security software, firewalls, printer and media software. It is advisable to deactivate these programs and slim out your auto start. You can mostly configure this through the settings of the program itself or you must manually deactivate them through typing “msconfig” (without the “”) via Start -> Run. A freeware tool that could help you organizing your autostart would be the CCleaner which offers the settings in Tools -> Startup

  7. Disable Hyper-Threading if your CPU supports it (e.g. Intel i7). Further information on how to disable it can be found in the mainboard or computer documentation.

  8. Disable advanced power-saving and dynamic performance options for your CPU. This usually needs to be done in the BIOS of your computer and includes Enhanced Intel SpeedStep (EIST), AMD Cool ‘n’ Quiet, Intel Turbo Boost, and AMD Turbo CORE.

  9. Disable C-States in the BIOS, if your computer’s BIOS gives you this option. C-States allow your CPU to sleep when idle, which may interfere with real-time applications such as audio. This option is often called “Disable CPU Idle State for Power Saving” in the BIOS.

  10. “Disable CPU Energy Saving”. In Cubase 5.5 and Nuendo 5 (or later) you can find this option in the main menu under Devices -> Device Setup… -> VST Audio System. This option is disabled by default. By enabling it, the currently active power scheme settings of Windows will be duplicated, settings which are relevant to improve the system performance will be modified in this copied power scheme and will be used as long as the application is running. Quitting the application reverts back to the last used power scheme in Windows.

  11. Using the DPC latency checker: This free tool of the company Thesycon analyses your DAW and checks for issues that interrupt audio streaming. Please refer to the manufacturer’s website for further information on how to use it.

  12. Processor scheduling (Windows XP only): It might make sense to set the processor scheduling to “Background services”:

Go to Windows Start menu, select “Control Panels”
Start “System”
Select the tab “Advanced”
Click on “Settings” in the section “Performance”
In the window “Performance Options” select the tab “Advanced”
There you find the “Processor scheduling” options, set it to “Background services”


Dear Jan Hendrik,

Thanks for your suggestions for improvements on the Windows install. This might come in handy in a later stage. I have spent many hours of installing multiple VST’s in the MAC setup so I will stick to that. Everything else works.

The “spiking” of midi-sgnals can also easily be resolved by the way:

Simply turn off the midi output towards the CMC, although it’s status might not be updated anymore by track automation. Probably there is some loopback process going on.

Do you not agree that it’s strange that the controllers are immediately and correctly recognised in other software by Steinberg? HALion versions in stand-alone mode DO operate with the CMC’s on MAC and the CMC’s do not work within Cubase. With all due respect but in my honest opinion this must have something to do with:

  • some setting in Cubase, preventing correct installation
  • some file that is not saved while installed (I am Admin)
  • some interpretation error of midi signals
  • or maybe an installed VSTi in Cubase
    and rather nothing with the fact that it’s a MAC OS on an Intel processorbased PC. I think blaming the setup is a little too easy an escape.

Yesterday I have installed a small program called MiDi Monitor by Snoize to test midi data being transferred from the CMC’s. This all looks OK.

Is there a kind of pre-made config file that can be be imported as a Generic Remote that has all CMC-parameters available?

Best regards,

The “spiking” of midi-sgnals" 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.

I’m sorry but we do not test Hackintoshs and cannot make any statments about possible problems with them in conjunction with our Hard- and Software.


Dear Jan Hendrik,

First of all, thanks for all your answers, also in direct mail! I do appreciate that and wanted to thank you and Luis for efforts sofar.
I will also respect Steinberg’s policy of not supporting the Hackintosh. Please know I am available to do some testing on my own if you could give me some specifications (config files, possible importfile etc.).

As far as the spiking is concerned, I really can’t see the advantage for the user of this “feature”. I experience it as nervous signalling that only makes me wonder if there is a faulty component. Maybe Steinberg could add a selectorbox in the next softwarerelease with which one can select this feature if it is wanted. Turning all midi signalling off is not what I want, I want to see if midi-signal comes in on the transportbar to check the equipment if I hear no sound while playing.

Thanks again, still appreciate your products!

i have exacly the same problem!
did you solved it?

any ideas how to solve it?

No, the problem is not yet solved.
Would you mind to see if we possibly have installed the same software or hardware to check if we have things in common in hardware or software?