M Audio Project Mix Driver
Xena Donovan
So, I recently installed the latest Cakewalk update (I believe it's version 2019.07, I'm not 100% sure on the name, though. 25.07.0.79, maybe). After this update, every time I attempt to open Cakewalk, I receive the message "There are no audio devices for the current driver model on your system. Please go to Edit Preferences Audio Playback and Recording and choose a different driver model." Then afterwards, I press "Okay," Cakewalk opens, and I can open a project, where I receive the message "The following tracks and buses are currently assigned to a silent hardware output. The items listed below will by silent in your project until their outputs are reassigned to an appropriate hardware output." Below it, it says simply "Master." Then none of my projects will play back- I can press play, but it is completely silent. I also am unable to record- I can press arm for record, but then the record button does nothing.
Here is a setup guide that may help with interface and driver mode setting. Use "SONAR Platinum" as the product. If the guide recommends MME and the PC is running Win10, try the WASAPI driver mode settings.
Do you have Sonarworks Reference installed? They just sent out an update that talks about an error like this. Might be related. I don't use Systemwide so I never saw this but perhaps it's the source of your problem?
I had the exact same message just today. The problem was caused by a power blink. All I did to fix it was unplug my interface from the computer and plug it back in. After that I opened cakewalk up and a window popped up that said a new device (focusright scarlett 18i20) was recognized, do you want cakewalk to add it? Just hit yes. This added my interface to the list of outputs I was able to choose from. This can be caused by other things than just a power blink. Its basically cakewalk not recognizing all available outputs.
I got this message yesterday on my DAW. The last time I used CbB I was using a Boss SY-1000 as an interface. When I opened CbB yesterday the SY-1000 was powered off and a MOTU M4 was powered on. When I opened preferences the M4 was there, but as expected nothing was checked. Checking the appropriate boxes everything was fine. Seems like it could be a case of switching devices as well - I use both the SY-1000 and M4 in ASIO mode.
The first thing to do is open preferences and see if the Tascam US appears in the audio devices. If so that's not the problem. Then make sure that audio tracks are routed to a bus. Then check that buses are routed to master and that the master is routed to the Tascam.
I just want to stick my hand up here and say something encouraging...
Six months ago, I was where you are now. I was new to DAWs and nothing - nothing - would work like it was supposed to. Every single step was painful. Every solution I tried seemed to balls up two other things it had taken me a week to get right. It was very, very frustrating and discouraging.
It's hard, and I still don't understand why it has to be. No, I do. It was a combination of lack of knowledge and understandable impatience. But it passes.
And here's the good news. You're in the right place. I spent a small fortune on a Cubase licence, and could not get my head around it. Looking for help, I went to various Cubase forums, and I didn't feel at all supported or understood. I felt stupid, is what I felt.
I switched to Cakewalk because I discovered the brilliant videos of Creative Sauce, and they made sense to me. Having made that switch, I joined up here - and I was not made to feel stupid, even when my questions and struggles were quite....well...basic.
So, this is a little aside to express my own gratitude for this forum, and to assure you that what you're going through is not that unusual, and that everyone here understands that.
...okay, that's the end of the sloppy bit. I shall go back to being my usual acerbic and unpleasant self.
When I did this, the system said that demarking this option will make to change the frequence of the project and asked me if I wanted to re-adjust it automatically (I remember something like 40.000Hz to 48.000) Ignorant of me I clicked OK.
IF you have the option to use a specialized ASIO driver, dowmnload it. I use an RME interface which comes with its own mixer (like some other manufacterers as well, of course), where you can quickly change pitch in the driver itself easily; this is great if you for example play with virtual amps and want to quickly want to match another concert pitch than 440 Hz, without having to retune your guitar.
I copied the vm3011 folder: firmware-nordic-thingy53/drivers/vm3011 at main edgeimpulse/firmware-nordic-thingy53 GitHub from their repository into my own project under a /drivers folder at the root of my application.
My questions are as follows:
1) Why would my project, which targets that thingy53_nrf5340_cpuapp_ns board target pull in some kconfig resources for the x_nucleo_53l0a1 shield? This reference to the shield is causing a dependency loop error listed above. How would I debug why this shield file gets pulled in?
2) Is there a good example for adding an out of tree driver to a basic project? My understanding is that I need to provide the driver files which Edge Impulse as already written, then add a devicetree overlay file that adds the vm3011 to system and it should just work correct?
2) When I remove the line `select SENSOR` from the vm3011 driver config the dependency loop goes away. I tried tracing the files that SENSOR includes or selects but was not able to find a link back to the nucleo board.
I used Tamas's implementation as basis audio playback in my NRF52840 SoC based project and it works like a charm. Simple flexiblel and lightweight. This saved me a lot of time. I used a PAM3804 audio amplifier for prototyping and attenuated the noise using a 22uF cap in parallel with the PWM output pin and GND. This is ok for a 4 Ohm speaker.
NOTE! Powering the PAM8304 with a separate power source is recommended to prevent power surges on the usb port.
As far as I've seen there is a Linux driver out there for the TAS2563, but when checking the sources I could not find anything about PDM. As we need to connect two PDM microphones to the TAS2563 I would like to know if there exists a driver supporting PDM too.
The project uses one TAS2563 and the use of the TAS2563 will be like an intercom (playback and recording at the same time) for a parking system with one speaker and two PDM microphones.The idea for using two microphones is either to have a better quality or to implement beamforming at a later time to compensate ambient noise a bit.
normally, tx path is 4-slot, 16-bit, samplerate is same as the rx path's. the signal in tx path is slot 0 is pdm-left mic data, slot 1 is pdm-right mic, slot 2 is echo reference data (about -6db less than rx data ). ,
I recently purchased my first DIY speaker kit (Scanspeak ReDiscovery from Madisound) and I was wondering how I'm meant to determine the polarity of the drivers as there don't appear to be any marks. The tweeters do have one of their terminals painted white but the woofers don't appear to have any markings. The drivers are:
The woofer is an easy one. Connect a 1.5 volt dry cell battery across the speaker terminals. Don't leave it on for long (just a second or so). If the cone moves forward from the rest position with the +ve terminal of the battery applied to one terminal of the speaker and the -ve terminal on the battery connected to the other speaker terminal, then the the terminal connected to the +ve of the battery is the +ve terminal of the speaker. See the attached pic.
Grab a torch and look again - often they have a marking that isn't very clear, usually there is a red marking for +. Do you have the bits to do measurements? If so, the tell tale sign is an obvious dip at the crossover point. Apparently the battery test actually does work on tweeters too, but I wouldn't try it.
G'day Josh, take a look at your driver in this pic here. The LHS terminal looking at the pic is the positive terminal and they've marked it with a big red dot. Did you buy the kit complete or just the drivers?
I purchased the complete kit, I thought this was the safest way to go for a first project. I'm building it in a 22l sealed cabinet and supplementing the low end with a rythmik ds1501 (I hope to add a second one later in the year)
StereoNET (Australia) is part of an international network of publications owned wholly by Sound Media Group (Australia). Our publication is supported by its audience. By clicking links on our site, we may earn affiliate commission, but our editorial remains entirely independent and unbiased.
When running loading large cubase 12 projects the software tells me that it cannot load the audio driver. This can be built-in internal audio driver in my mac, or one of two other audio drivers (focusrite-USB or allen and heath-Firewire).
When this happens I am unable to a) use cubase b) play any other sound on my mac (e.g., youtube gives audio render error, apple music just makes no sound, VLC the same, soundcloud just won't load the page, the spotify app says it's unable to play).
I've been in contact with cubase now and after trying a number of things they told me to contact the audio device hardware manufacturers. They also told me that there is an issue with the audio driver in the Ventura OS.
93ddb68554