Descargar Autotune Para Windows 7 32 Bits
Rocki Stenger
Well, there you answer your own question to why you cant for the life of it workout why your sample rate of your interface in windows need to be the same as your asio sample rate within CbB to run Autotune live for recording without any issues.
When you set your device as the default audio card in windows - windows automatically reverts its drivers to use with your interface. Within windows i only get 44k at 24bit and 48k at 24bit with my 2i2. So that tells me that windows uses my interface as the primary audio card by converting its drivers to be used with the device. Once this is not match I get dropout during recording with Autotune enabled.
This is not the case, I have been working with Cakewalk for many years without any problem, but I wanted to find out to what extent a voice could be recorded with Autotune in real time as rappers do and I had never tried this thoroughly.
Cakewalk will force the interface to conform to its preferred settings in Preferences, independently to Windows. If you're recording live audio within Cakewalk, why does it even matter that system audio - which ISN'T ASIO - is set to something else? Unless you're actively switching to something else while you're recording, which is generally a bad idea anyway, how is it even coming into play?
So I see in this thread. But it's actually not the case, unless you're trying to use some other software that plays audio at the same time as you're using Cakewalk, which I assume you're not. If you're recording vocals, why would you be?
As I said in my first post in the thread, so long as you have your interface's ASIO drivers installed properly, selected in Cakewalk in Preferences, and you've set your latency as low as it'll allow you to go and you've disabled any direct monitoring in your interface's control panel, then all you need to do is click the Input Echo on the track you're recording on to hear the autotune effect. That's it.
If you want to record the track with the effect on it, you do need to route it to an Aux track or something like that and record that Aux track, because you can't record live effects to a track directly, but you can still apply those effects after the recording is done.
If you're also using your main audio interface as your Windows audio device, although it doesn't matter what bit depth Windows has your interface set to, most interfaces don't support different sample rates between Windows and ASIO. So it is important to make sure the Windows sample rate is set to your Cakewalk project sample rate.
Also, although Cakewalk will attempt to set the sample rate of the interface to match your project, not all interfaces support this and will require opening the ASIO panel to change the settings.
Of course all of this can be avoided by using your on-board sound device for Windows audio, and your audio interface exclusively in Cakewalk.
My point I was making though was this kind of went off on some tangent somewhere that wasn't really related to recording a live effect inside Cakewalk, rather than making sure the drivers were correctly installed and input monitoring was set up. It's like not being able to start your car and rather than asking if someone has the key in the ignition, it turns into a discussion about different fuel types - which can be very important - but is really muddying the waters with getting the task done.
It didn't really change, someone commented that the windows audio settings should match Cakewalk's even though they are different drivers, so that there are no latencies, that is: Sample rate and Bits depth, when I try to put the windows audio settings in 24 bits using my Motu Ultralite Mk3 Hybrid, to coincide with my projects in cakewalk, it only gave me the possibility to put 16 bits, this generated more conversations between users to find out why I couldn't.
I was going to say that this is getting off the topic of the OP, but really it is still relevant, because unless you understand & have full control over how your DAW sounds are routed through your interface, getting live input monitoring to work the way you want can be difficult. -Generally speaking, the more i/o options your interface can provide, the more you need to discover how it works and how to route the options. -If you only have a 2-channel interface, it can be simple, but add separate headphone and/or line outs, etc., and your routing paths can get hard to understand, unless you spend some time learning your specific interface mixing options.
@JohnnyV -On my particular current interface, for instance, I chose to route the WASAPI feed from Windows outputs to a mix that always appears in my headphones, via a driver setting and an interface mixer routing. And for me, it causes no obvious problems with Cakewalk so far as I can tell, to run both driver paths simultaneously, but that varies from interface to interface, so it is not a general answer for everyone. The same goes for how I route my interface options when using live input monitoring, versus the interface direct monitoring, for instance. As I always seem to say - it's all about the routing, - understanding, often testing that, is key for many things beyond simple recording & playback.
That was Will. I'm not sure why he tossed that at you even though I agree it's a very good idea as far as Sample rates go. I recommend people keep everything at 48. There's also a minor improvement in latency with 48.
You are trying to sort out why your bit depth is only 16 so windows setting are outside of where you need to look to fix this. If your interface was 10 years old, then ya, it might be 16 bit, but it's not ( or is it?)
Yeah, the big problem with this thread is there's 2 entirely different conversations going on that are being conflated, making each one of the solutions seem like they're mixed in together somehow. There's been some very informative and great suggestions in the thread but if taken out of context, those solutions are just making things more confusing.
Cakewalk is using an ASIO driver to get the sound into it. It's separate to Windows audio (Windows doesn't use ASIO), but as was mentioned, it's generally a good idea to have the sample rate the same for both the ASIO driver and Windows audio if you're using the same device for both things.
Like was mentioned in the thread and in my post, your need to have your interface installed correctly first, with the correct manufacturer's supplied drivers, and you do your initial settings inside your audio interface's control panel. If you haven't got your MOTU's control panel software installed, do that first, and look for the setting in there.
This should change over any Windows settings automatically, but as was suggested, it's a good idea to have your Windows audio match your MOTU's settings just to be extra safe, to avoid any possible mismatches. What you're seeing in that Windows speaker properties stuff really has no bearing on what's coming into Cakewalk at all, it's an ENTIRELY different driver and different audio path, but in the weird case that some other application is using your audio device, having them match can stop some issues. Unlikely if you're just recording a vocal track with nothing else playing, however, but it's still generally a good idea.
The key takeaway here is that your MUST have your proper MOTU drivers and control panel software that you downloaded from the MOTU site installed first. It's always a good idea to check back to see if there's any updates to the software too, so you have the latest drivers, control panel and firmware installed. If you're unable to switch out of 16 bits, this is a good place to start looking to fix it.
d3342ee215