Notifications
Clear all
Topic starter
I have a serious problem with the Cubase application and modx8
First the problem: I open Cubase 10.5 or 11, when I select the Yamaha Steinberg Usb Asio driver, the message appears "The device could not be opened"
-I cannot connect my modx8 to cubase 10.5 anymore, and also in the past I was allowed to connect to the driver.
-When I try to change the driver in cubase "Studio setup-->select driver-->Yahama Steinberg usb Asio driver---->the message appears "Device could not be opened"
-When I go in Windows 10 to Start--->Yamaha Steinberg Usb driver folder--->control panel--->Modx device doesn't show, gray in the selection zone.
-When I open Device manager in win 10 I don't have Modx under Sound, Game and Video Controllers
What I tried to fix the problem is:
-I downloaded the new software for modx8 from Yahama.com and I have: MODX Connect V1.1.1 for Windows,Yamaha Steinberg USB Driver V2.0.4 for Windows 10 (64-bit),MODX OS Updater V2.51 but the problem consists
-I contacted Yahama Studios Technical support in Germany, he described the problem as to many drivers in the Driver32 folder. On the phone he instructed me to open Regeditor in Win, to the WindowsNT folder-->the driver32 folder-->he said the max drivers in this folder could not exceed 10 or windows would not recognise the Yahama Steinberg Usb Asio driver--> I had over 25 drivers??--->I made a back up of the reg file, because he instructed me to delete every driver on the list and reboot and then reinstall the Steinberg usb asio driver again---> I did everything but this does not solve the problem
-I tried to let windows 10 look for new hardware---->windows doesn't find the modx
-I double checked the Usb cable, I can see it works because in the Utility section on the modx8 my connection switches on as soon as I connect to Usb to my computer
What can I do to solve the problem??
Posted : 25/01/2021 10:36 pm
Probably nothing wrong with your MODX, probably nothing wrong with Cubase. The problem is clearly a Windows issue.
I hesitate to do any ‘adjustments’ to your Windows Registry via a forum like this — You are best served by either phone support or direct support from someone who can help you overcome your computer issues.
After you see the message that the Driver cannot be loaded, you can stop, right there. Doing anything else just adds to your frustration.
It’s like the car has no engine, the fact that one of the tires is low on air, or the lock on the trunk is broken is of no concern, the car isn’t going anywhere until you get that Driver opened. Worry about the tire and trunk later.
Reading your post, first thing I would suggest is to make sure you are connected DIRECTLY to the computer. That means NO HUB.
You don’t mention whether you are or are not using one; and I’ve seen customers do everything (including reinstalling Windows, unnecessarily) — all they needed to do was remove the HUB (they didn’t think it important to mention that they were using one... Don’t.
Continue getting help locally. Problem with the computer are best handled via phone support or direct support.
Let us know if you get the Driver recognized. Good news the driver is installed, as you can see the Driver’s Control Panel.
Posted : 26/01/2021 7:38 am
Calling support (for Windows or the Computer Brand) will lead to the inevitable joy of them saying "Contact the Driver Manufacturer.... not our problem"
Posted : 26/01/2021 12:24 pm
Calling support (for Windows or the Computer Brand) will lead to the inevitable joy of them saying "Contact the Driver Manufacturer.... not our problem"
I think the original poster was in contact with the right people. But thanks for the encouraging words.
Posted : 26/01/2021 1:40 pm
This registry key?
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionDrivers32
Because I have 20 entries there and everything is working.
I just do not think this business about more than 10 is true if the above is the registry key you're referring to.
I think your support team is mixing up things here. There was an API limit of 10 MIDI ports. This is not related to how many drivers you have installed in driver32. Newer APIs have a much higher limitation - still no relationship to the amount of entries in the "Drivers32" registry folder referenced above.
This limitation is primarily a problem with older MIDI software. Software that uses newer calls - as Cubase 10 or 11 should most certainly use - would not have this kind of limitation.
That said - your MIDI drivers that are connected to USB devices have a way of littering your system with zombie entries. If you plug in your instrument to different ports - then a new instance of the driver will be "installed". The Yamaha Steinberg USB Driver used by MODX and Montage will present issues with WebMIDI when there are these zombies out there. It's best to clean house every so often.
Cleaning house can be done by uninstalling the Yamaha Steinberg USB Driver, then rebooting without the driver installed, then installing fresh. This will clean up all of the old entries.
If you haven't done this already - I would do this before mucking around with the registry. If you think Cubase is fouling up the works - just wait until you tangle up your OS with bad edits and try to undo those. Best of luck if that's the plan. Backing up keys is OK - but some doors are one-way if the system "reacts" to registry keys being set a certain way. The best way to back up your system is to ghost your drive bit-by-bit. Shy of that - creating a restore point may be OK. I wouldn't "trust" this and would still suggest "ghosting" your drive (as in Norton Utilities Ghost - but there are others out there and I'm not sure if Norton is the leader in this anymore). Doing this would allow for you to do anything you want and restore back.
Posted : 26/01/2021 9:37 pm
