Man for the amount of time you took on this driver, there sure isn’t much here.
I don’t see it, but is there a shift lock for fine mode now?
Silly MIDI spam still going strong.
Without those two things, I’m not hooking them back up.
And it’s more stuff…
-
Channel selection doesn’t work either from the FD’s… works fine on the CH and the QC… Shift-switch would also make channelselection from touching the strip easier without messing around with the actual setting and having to use a two-touch operation all the time. Smooth fader operation though and that’s really really sweet, but i sure would like to shift-switch a lot of functions for smoother operation those moments when your’e at the end of a projekt and don’t want to mess upp any settings accidentally.
-
Why isn’t the Fadermovement calibrated to -0 db for the Controlroom fader while using the AI knob? it’s either somewhat below 0 or somewhat over… i’d like to be able to calibrate this.
-
Jogging doesn’t fall on even quantize settings and it isn’t possible to jog to a certain position without having to use the BAR buttons in conjunction
4.CMC-FD Faders JUMP regardless of setting it to “touch” or any other setting… ( Ramp or Relative didn’t work before either so that’s out of the equation.)
5.Loading a VSTi in the rack selects the corresponding MIDI-track but the “Instrument-button” doesn’t light up as it did before… one has to step to an adjacent track by the “Track-button” and then back again to make it light up
If you start with the control room fader at 0, then the AI knob will return it to 0.
It’s based on the fader start position.
Sorry to say but it doesn’t… its -0.03 or +0.12
Ah… I see what you mean now.
My original tests were moving the fader (using the AI knob) just a little bit from 0.
If I turn it all the way down, it won’t go back to 0 when I turn it back up.
It’ll either be -0.03 or +0.12
Glad we’re on the same course then 
Hello Lundin and Shinta215
Do you guys have something else that you would like to add to the list before I pass this to Yamaha Japan?
Also could you please elaborate a little bit more on point 1, what do you mean by “Channel selection doesn´t work”?
How many FD do you have connected?
I have only tested it with one, so and on the mixer it it just works as expected.
Thank you again for your feedback.
Cheers,
GN
@Guillermo yeah the cmc-AI knob does not work as advertised with third party Vst3 plugins like waves and fabfilter!!!
According to steinberg this is not their problem, but as it doesn’t work with arguably the biggest plugin company in Waves, and steinberg says it works with all vst3 plugins and doesnt then it is their problem and its a fail for me just sitting their not even looking pretty.
Graham
Hello Guillermo.
By Channelselection i mean the “arrowed” channelselection buttons in the lower left corner of each FD. i have 4 FD’s and i believe this worked before the update.
i disconnected each of my total of 8 units while updating to the new firmware. Each and every CMC updated OK.
Hello Lundin,
I have tested it with 4 FD and the channel select buttons are working properly, I have only tested it on Windows 7 32 bits, are you on 64 bits?
Thank you,
GN
Hello.
Yes, my DAW is 64-bit only together with all plug-ins i use…
Windows 7 Ultimate 64-Bit that is
The channel buttons on the FD are meant to work differently from the channel selection buttons on the CH and QC.
The CH and QC’s buttons change the selected channel in the project window.
The FD’s buttons shift the channel bank forward and back by one channel in the mixer (as it says in the documentation).
The channel bank is independent from the selected channel.
It doesn’t do jack here… i’ve re-installed the drivers and software twice, i’ve also unplugged every CMC prior to updating the second time to see wether it has some connection, but still the channelselector doesn’t work, the bank-selector doesn’t work either now?, the activate VSTi button still doesn’t work, My AI knob still doesn’t work properly. On turning the knob counter clockwise the lowest value is - 108,6 turning the knob beyond this and back again the lowest value is -90 and then it’s impossible to set it to exactly zero db. either - 0,03 or +0.12.
Under Device → Device Setup Are all the FD devices listed? What are the midi in/midi out designations? Do they all appear to be assigned to a unique midi in/out device?
Also, there is a free utility called USBDeview which enumerates and details all USB devices. Try running it and posting the results where ‘Driver Description’ = ‘Yamaha USB MIDI Driver (WDM)’. Please include the ‘Driver Version’ and check to see whether there are any duplicate entries and/or duplicates with conflicting versions.
Thanks
Casey
Hi cpechet, i really appreciate you trying to help out.
I tried the USBDeview and i cannot tell if there is conflicting USB ports and the program doesn’t seem to say either.
the driver for all WDM units is 3.1.2.0… something i noticed though is that Cubase has found 3 CMC-QC ( i have only 1) and when i deactivate 2 of them Cubase won’t argue so something is definitely not right here. I’m going to try to use a cleansweeper program to get rid of the driver residue and see what’s happening.
EDIT:
So i found out that the QC’s is for unsing with midi and the extra QC’s is nothing to worry about… But
Cleaned the “driver-residue” and re-installed the drivers and shouted out loud when all things started to work??..well… for a second that is, until i noticed i installed the old driver and software… so cleaning the system once more and installing the new drivers DOING EXACTLY AS THE MANUAL SAYS unpluggin every USB unit i have: All CMC’s, the USB HUB, NI Maschine, Novation ReMOTE Zero and a VIrus TI) starting up only 1 CMC-unit at a time, waiting a few seconds before starting another… and were greeted by this marvellous non-working software… channelselection on the FD’s= NOPE ( consecutive stepping, yes i know ) VST-button that light’s up on opening a VST for the first time= NOPE, still have to step to another channel and back again to make it light up to be able to control the GUI of the VSTi, Control-room volume at exactly zero= NOPE, still -0.03 or + 0.12
Wow, i’m really impressed.
Hi cpechet, i really appreciate you trying to help out.
I tried the USBDeview and i cannot tell if there is conflicting USB ports and the program doesn’t seem to say either.
the driver for all WDM units is 3.1.2.0… something i noticed though is that Cubase has found 3 CMC-QC ( i have only 1) and when i deactivate 2 of them Cubase won’t argue so something is definitely not right here. I’m going to try to use a cleansweeper program to get rid of the driver residue and see what’s happening.
EDIT:
So i found out that the QC’s is for using with midi and the extra QC’s showing up is nothing to worry about… But
Cleaned the “driver-residue” and re-installed the drivers and shouted out loud when all things started to work??..well… for a second that is, until i noticed i installed the old driver and software… so cleaning the system once more and installing the new drivers DOING EXACTLY AS THE MANUAL SAYS unpluggin every USB unit i have: All CMC’s, the USB HUB, NI Maschine, Novation ReMOTE Zero and a VIrus TI) starting up only 1 CMC-unit at a time, waiting a few seconds before starting another… and were greeted by this marvellous non-working software… channelselection on the FD’s= NOPE ( consecutive stepping, yes i know ) VST-button that light’s up on opening a VST for the first time= NOPE, still have to step to another channel and back again to make it light up to be able to control the GUI of the VSTi, Control-room volume at exactly zero= NOPE, still -0.03 or + 0.12
Wow, i’m really…
Sorry this is not working out for you… Tremendously frustrating…
Can you post USBDeview’s:
- USB Version
- Driver Version
- Instance ID
- Driver Filename
- Power (I know this seems weird, just want to make sure the devices are all getting 500 mA)
Thanks
Casey
Hello Casey.
I will try to upload some more info to you but i’m beginning to see more and more reasons to throw this garbage toystuff out of the window… it get’s more and more useless as there is new stuff that’s uncovered that’s not working properly… either there is a large batch that’s faulty or… read below
Some news about my CMC-AI:
I got down to the retailstore here in Sweden two weeks ago and told them about my issue with the strange working AI knob and that it doesn’t resolve to exactly zero when turning the knob from +/- odb down to infinity, turning an extra turn (past infinity) and then back to zero again. (that it’s either -0.03 or +0.12 ) i also made a screencapture video showing in realtime what’s happening and it were sent to either Steinberg or some representative. a week later they told me Steinberg couldn’t reproduce the problem so they ordered a completely new unit for me as replacement.
Today i got down to the store and brought my unit to try it with their computers (MAC Pro ) and also unpacked the new unit, updated the H/W with 1.10 together with the new drivers, hooked my old unit up and the AI didn’t work as expected… we then hooked up the new unit, and like magic - same problem with the new unit: IT DOESN’T RESOLVE TO ZERO EITHER!!! and jogging is still a joke,erratic as hell
Wow…
Hello Lundin,
Just to resume all your posts.
You are complaining about the fact that when you use the AI knob to move the fader (or to Jog) If you start in 0.00 db and you rotate the knob one step left it will go to -0.16. But if you are in 0.00 and you turn the knob one step right it will go to 0.31 Instead of 0.16. It is not equidistant.
Am I right, Is that what you want?
P.S. I received the video today from our sales rep.
Cheers,
GN