Zoom Audio Driver Windows 10
Вячеслав Бахтыгозин
This audio driver is located within the macOS SDK. If you pull down the latest Zoom SDK you can navigate to the driver in this directory: zoom-sdk-macos-5.5.12511.0420/Universal-Intel+M1/Plugins/ZoomAudioDevice.driver (unfortunately, since the code is only available as a download from the marketplace I can no longer point you to a direct reference via github).
Note:
ZoomAudioDevice.driver is used to sharing computer audio. ZoomAudioDevice.kext is unused now, we only use ZoomAudioDevice.driver.
Usage:
Copy this to yourAPPName/Contents/Plugins folder path.
We will also work to ensure that something like this is not released without documentation in the future. There are some internal process changes being made that should be pretty effective at mitigating against these types of changes going undetected.
I would say that the best way of verifying that this has been done properly is by testing out the ability to share computer audio within a meeting. If there are any issues with that feature, then we can look into this further.
Thank you so much for your help! I have been stuck for weeks trying to
figure this out, as almost everybody uses Mac. I have used a PC for over 30
years and do not want to switch to Mac at this point. - learning Cubase is
hard enough!
You change it to the Generic Low Latency driver, or you can install FlexASIO and change it to that. After the Zoom session is over, you change it back to whatever you have right now - I do not know what you have right now. Make a note of what you have now before you change it.
Out of curosity, how can you do this? I have an RME interface as well (HDSPe AIO PCIe card) and was not aware of this functionality. I always have to change the driver myself to get Windows Audio to capture it.
What Focusrite model do you have exactly?
If you have a vacant pair of inputs and outputs on your device you can create a physical loopback by connecting output 3/4 into input 3/4 for example. Then adjust the gain and levels via Focusrite Control (use a test generator and aim for the same level at the inputs).
On your output channel in Cubase you configure a Send that is set to output 3/4. All the other audio on your computer is set to a different output obviously (including Cubase main output, you can just set them all to output 1/2). This way you can select input 3/4 in Zoom and the others will only hear the audio from Cubase. Additionally you may want to use the same Send method on your microphone channel in Cubase so they can hear you talk.
Hi I am having the same issue, I have a Roland Studio Capture and Cubase 11 and Wavelab Elements 10, all were working great. I upgraded to Wavelab Elements 11 and it installed a generic low latency driver. That now messed up Cubase and no matter what I do to reinstall either of them, or the Roland driver, it keeps only showing a generic low latency driver in the studio setup, also showing all the missing ports. Windows tells me the Roland driver is working fine and up to date. I tried going back to Wavelab Elements 10 but it no luck. Can anybody help?
I have corrected the problem with the audio interface driver. I had uninstalled wavelab elements 11 then reinstalled it and selected to uninstall the generic low latency driver in the installation. That solved it, now Cubase 11 Pro now sees the correct Roland driver in the audio setup and no more missing ports. It seems like Wavelab was messing up the driver registry in windows 10 when it installed.
It is unbelievable why this 2021 program cannot correctly connect to the system audio activated in general settings of a Mac or PC as any other even free Audio program can do. Opening a simple file provided officially with Cubase 11 can ruin your day. You get a lot of useless messages on unmapped ports which cannot be edited or delete as they do not show in Studio.
I opened one of the producer templates provided by Cubase to check it out and it seems to creates two S/PDIF ports for which I do not have any device connected. Impossible to get rid of these each time I open Cubase now you get the unmapped message and worse no more sound and impossible to set the interface back to build-in or my Clarett interface. It simply stays on unconnected. In the Studio Audio connections you see the build-in audio but if you try to connect it simply will not accept it.
For new files I have managed to reactivate build-in but my Focusrite Clarett interface which was working perfectly with both Cubase and Logic yesterday is not showing up and I do not get the message at start up which was mentioned higher up in this thread if I want to connect to a certain device if there are more than one, if you could somehow force this message to appear and work each time you start Cubase that would already be a nice workaround.
The terrible thing is threads with the same issues have been posted since years and it is not solved. The offers to come over from Logic are great but if each time I change configuration I loose half a day to get sound to work It is not very attractive.
A related issue try going mobile and use a headphone directly connected to your Mac or PC. 1 in 3 I have to switch back to Logic as there is no way to get sound before I arrive from my three hour train ride. Connecting my nice Sony Bluetooth headphone which works perfectly with all but Cubase and Dorico, I already gave up (yes I know about latency) as that is a real uphill battle.
Thank you for the fast response. I have just reinstalled Cubase using the download assistent. So all back to default now and older files also see and connect to build in again. I have now saved the basic build-in connection as preset under audio connections. So if the issue arises again I might be able to quickly load the preset. Also the message pops up again when I open Cubase and the Clarett is connected. I also saved that preset.
To avoid the issues with the default headphone sampling rate being different from the default build-in you can change it on a Mac in the Audio Midi Setup app. Simply set it to 48 kHz and you can plug in and pull out the headphones without issues.
Indeed therefore I have the workaround each time trying to set the headphones to 48 kHz. It is still not working perfectly I can switch but sometimes the 44 kHz is back and project and output device do not match.
You also have to be very careful when to save files i.e. with which sample rate active. I recorded guitar and voice for the first time using the Cubase template Distortion Guitar + Vocal. At that time my Focusrite interface was providing the in and output. I have to check what the sample rate was for the recording. All worked well but after an audio editing session with head phones, I have probably saved the file with 44 kHz. So if I open it now I have to use 44 kHz and not 48 kHz as well to avoid the half semitone effect (you can hear it well when you know the voice timbre)
I was having the same problem. I perchance found the solution. In windows, if you go via the start button to the programs, under Steinberg there is drop down for ASIO low latency driver. If you click it it opens up an option that allows you to click the Spider driver. And it works well thereafter. Bit silly way to do it. but there it is. It happens every time the driver changes or you download something. Cheers!
I have connected the R8 to the pc to record guitar directly to Cakewalk. I have the R8 side sorted, with an input signal, after following the instructions in the R8 manual. I have installed the latest R8 driver. The R8 is recognised in the Cakewalk preferences, in all instances except for the Audio Playback and Recording Driver Mode, and under the MIDI options for Controller/Surface, where there is nothing listed.
I have tried the Asio and Wasapi Shared options so far. I had ASIO4ALL installed, but when I selected ASIO option CW popped up a window stating that this driver is not compatible. I read elsewhere that the ASIO4ALL 'wrapper' can 'hijack' other ASIO drivers (I'm not 100% sure what this alludes to). So, I uninstalled ASIO4ALL and rebooted. Now in the Audio Playback and Recording Driver Mode, when I select ASIO I do not see an error window. I assume then that now the R8 driver is recognised and accepted.
I also discovered that Windows was automatically replacing the native Zoom R8 drivers with Microsoft generic audio drivers, but was able to fix this issue by unhiding the list of (what Windows considers) non-compatible devices during the manual driver installation process, and select the Zoom R8 device.
If I set Playback and Recording to WASAPI Shared I can see the Zoom R8 in all the places it seems it should be when this setting is set to ASIO in your video. Set to WASAPI Shared I get playback sound, but no audio input from the guitar or built-in mics from the Zoom R8 is registering in CW.
Last year when I used the Zoom R8 as an interface to record in this manner I didn't have to keep entering into the Windows settings and changing them every time I wanted to use the R8, and when I had finished using it, to turn on my monitor speakers. Is there no other way than having to enter the Sound Settings in Windows and having to change them every time I want to record?
UPDATE: The firmware needs updating. Currently I have the previous version. The R8 doesn't detect the firmware file on the SD card though. I've followed the instructions correctly 3 times. I'll have to get in touch with Zoom about this.
If you would rather be making music that fighting a loosing battle with badly written drivers then do your self a big favor and buy a proper audio interface like a Focusrite.
Maybe your Zoom R8 driver is different than other Zooms drivers from the past, that would be great.
However my MRS-8, which precedes the R8, does not communicate with the computer like the R8 does. My MRS-8 also does not attempt to be everything to everyone like the R8. The R8 can be used as a digital recorder, audio interface or surface controller.
d3342ee215