Hi everyone,
I’ve been using the Yamaha CC1 for a while and I’d like to share some suggestions that could significantly improve the user experience.
I don’t know if these points have already been discussed, but I think they are important enough to highlight.
1. Power Requirements Are Too Sensitive and Not Clearly Documented
The CC1 shows a “Low Power” warning with most modern USB chargers and USB‑A ports.
It only works reliably when:
-
connected to a dedicated USB‑C port on the computer
-
or powered by a non‑PD, non‑QC, fixed 5V supply (5V 2A or 5V 3A)
Most USB‑C chargers today are PD by default, and the CC1 does not negotiate PD profiles, so they don’t deliver stable 5V.
Suggestion:
Provide clearer documentation about power requirements and explicitly recommend a fixed‑voltage 5V supply.
2. The CC1 Software Must Stay Running at All Times
The CC1 requires its companion software to be manually launched at startup and kept running in the background.
If the software is closed, the controller loses functionality.
Suggestion:
Allow the CC1 to operate in a “standalone” mode for basic functions, or integrate the driver more deeply so the software doesn’t need to stay open.
3. USB‑A Ports Severely Limit Current
When connected via USB‑A → USB‑C, the CC1 often receives too little current because many USB‑A ports limit power unless a device negotiates charging profiles.
The CC1 does not negotiate anything, so the port never unlocks full current.
Suggestion:
Improve compatibility with USB‑A ports or provide clearer guidance on which ports are suitable.
4. Quick Controls Integration Needs Improvement
At the moment, Quick Controls behave inconsistently:
-
QC parameters do not always follow the selected track
-
automation works only for the main track volume, not for insert parameters
-
QC mappings are not always updated correctly
-
plugin parameters mapped to QC often fail to write automation
Suggestion:
Improve Quick Controls handling so that insert parameters and plugin parameters can be automated reliably from the CC1.
5. Provide an Official MIDI Remote Mapping for Cubase
Cubase has a powerful MIDI Remote system, but the CC1 does not include an official mapping.
Users must create their own, and the behavior is inconsistent.
Suggestion:
Provide an official MIDI Remote script for Cubase, with:
-
predefined pages
-
plugin parameter mapping
-
Quick Controls integration
-
transport and navigation presets
-
consistent behavior across sessions
This would dramatically improve the experience and reduce setup time.
6. General Quality‑of‑Life Improvements
A few additional ideas:
-
Allow custom mapping templates
-
Provide a “safe mode” for power‑sensitive USB setups
-
Improve feedback when the device is underpowered
-
Add an option to auto‑launch the CC1 software with Cubase
Conclusion
The CC1 is a great concept and has a lot of potential, but improvements in power handling, USB compatibility, Quick Controls integration and official Cubase mapping would make a huge difference.
I hope these suggestions are useful to the team and to other users.