Go to your master Bus and see what it's output is set for. If you do have an interface then you need to install the drivers and make sure it is working by checking windows audio settings. If not then do as Scook says and use WASAPI and make sure to click APPLY
Lots of old guys here, including me.
In Track View, click the control outlined in red to bring up any busses already available.
If there are no busses, right-click in the empty bus pane and Insert 1 or more. Double-click the name of the bus and name it whatever you want, like Master or Guitars, etc.
All busses should have their outputs set to the Master, and the Master's output should be set to the sound card's or audio interface's output.
It might all be no good anyway. I tried uninstalling and reinstalling because I know sometimes there can be a glitch that gets sorted doing that, but tried 4 times now and it gets to downloading 5/5 ---- then nothing! Nothing downloaded or installed, no error message, nothing.
If it still doesn't install this time, or I have the same sound problem I think I might just give up and try Waveform or something, but I really would like Cakewalk as it seems to be about the best and most comprehensive of the free programes.
Most of the tutorials all assume you will have an audio interface because that is best practices. Trying to get on board audio working smoothly is a bit more work because Cakewalk and most DAW's are designed to work with ASIO driver support. Audio interfaces start at only $50. Recording equipment used to cost $$$$ $50 and a free DAW is pretty cheap.
Did I waist my time making the tutorial? I made it just for you. And you need a master bus,99% of users do it that way. Yes you can go directly to your sound card but there are good reasons to use the master bus. One is once you have a dozen tracks playing you will have no idea of how loud the combined tracks have become. The video I made you covers all this. There are plenty of good tutorial videos. Just google your question and include Cakewalk in that.
I'd tend to spend the time dropping in your own manually inserted markers rather than letting Audiosnap try and detect things. It's more work in the beginning, but you'll get much better results in the end.
I personally wouldn't use the slice/crossfade method on this, I'd be inclined to use stretching instead, just so you're not getting odd artefacts as notes loop over each other. That can work for drums but for guitar it can be really iffy on the sustain of notes.
But this all said, quantizing is great and will get you over the line, but there's a magic in someone just nailing their part. It's those little human variations that add so much excitement and thickness to a part that makes it something special. I'd definitely recommend doing a bunch of takes and editing together the best parts rather than quantizing once you're up to the ability to do that. The part will really come to life!
If that's it, the root cause could be that there is some inherent latency in the playback of whatever you are playing against in the project, be that a metronome or a prearranged accompaniment. Usually, a recording is aligned (after the fact) when played against a project with latency, but sometimes things can go wrong with that.
Dont forget about the pre-count in to get you into the groove before the actual recording starts. And practice. some day very soon, you will be surprised when your music starts exactly with the beat, and the metronome just disappears into your music.
You'll want to be aware of the stretching algorithms using AudioSnap. The Elastique algorithms will give you the best bang for your buck for online rendering (what you hear during real time playback). You can set the defaults for this in the Preferences or change per clip via the AudioSnap Palette or Clip Properties.
I've gotten great results with stretching for most things, and like Jon said, choosing the right algorithm is super important, and so is bouncing down the audio when the stretching is done, so you're not using the less CPU costly online algorithms that have less quality than the bounced offline ones.
I've found that slicing and crossfading on guitars does all kinds of weird stuff to note decays. If you're most of the way through a sustained note and you crossfade at the wrong point, not only is the level going to be an issue but the whole timbre of the note can change dramatically over a couple of milliseconds. It can sound super stuttery.
If the timing is so bad that it's hard lining up a start time of a phrase, you're going to run into huge issues trying to fade between stuff that's so far off the beat, IMO. Stretching, while it'll never be as good as actually playing the part, will mitigate that to a point, especially with the right algorithm.
I have been working on a project for a game I'm creating and all has been going smoothly for the most part. However, recently I got an error message related to drivers (I don't remember what it said exactly and it only came up once) and after clicking past it my project no longer plays.
Oddly enough though, I am able to export the midi and audio from the project in question to a new project and everything plays just fine. Old projects playback perfectly with the same driver settings as well. Every project I have played as expected except for this one.
As I was able to export the midi and audio I can gain back a small amount of progress but as that doesn't transfer over my plugin settings, FX stacks, or my automation, I'm losing lots of time and the arrangements of everything that was exported out is pretty wonky as well.
The driver thing sounds weird but let's pass over that for a bit.
What happens if you open the project in Safe Mode by holding down SHIFT when you open the project, and saying NO to loading each plugin? Does it play with the plugins not loaded? It's possible something has gotten into a bad state that's blocking the audio engine from playing somehow.
It's sometimes useful saving a safety copy of the project before you do any of this work, so if you're doing a process of elimination, you could delete all of your busses and save as a new project and see if it plays, or delete half of the tracks and see what it does - if it plays then you know the problem is in the second half of your project, so you can further refine by deleting half of those tracks and seeing if it works, and continue on until you find the culprit.
One thing you might be able to do is to save everything in the project as a Track Template, then starting up a new project and importing that template, and then copying in the source project's audio and MIDI files. If this is effects related, this will probably fail on the new project though, but it's worth a shot just in case the tangle is somewhere in the project topology rather than in an effect state.
I'm not sure what the root cause of this is. Perhaps my switching back and forth between my speaker and headphone outputs is not playing nicely with my selected driver? But either way, I'm glad to have at least gained back the lost project. Again, I very much appreciate both of your responses. I've spent most of the day dreading having to try and recreate this project so I'm very happy that is no longer necessary.
What I think has happened with the driver is something else has tried to take exclusive control of it and it's shut Cakewalk out. What kind of audio interface and driver model (ASIO, WASAPI, etc.) are you using?
Just FYI, you are not going to lose the project data in a situation like this. If you are concerned about a project potentially becoming corrupted, you can still save it with a new name to keep them both (keep the original, and save with a new name after a glitch).
The Edit->Preferences->Audio->Playback and Recording is good to visit any time you are changing the hardware you are working with. This forces the application to look for what you are trying to use and will let you know if it is available or not. The ASIO mode will only allow one device to be active at a time, so if you disconnect that, Cakewalk has nothing to talk to until you shift modes/select another available device.
I'm having trouble getting Cakewalk to output audio to my computer's 3.5mm jack. My goal is to mimic what I was able to do with GarageBand on OSX; connect my guitar through a USB interface, play with GarageBand's amp emulator, listen through my 3.5mm headphones directly from the computer.
I am able to hear output audio from the Scarlett Solo 6.5mm jack, but for convenience it would be nice to use my computer audio. I'm just learning and trying to get the most simple practice setup I can on Windows.
You can try changing the driver mode to WASAPI shared or WDM. The internal sound chip should be one of the devices available and these driver modes allow multiple different devices, however; there are performance trade-offs using these modes instead of the ASIO driver designed for the interface.
This is a common issue with people who have just purchased an Audio Interface and have not yet purchased proper studio monitors. You have to use the outputs on the back of the interface and they only have consumer computer speakers.
Byron, nobody's going to disagree with you about the superiority of Focusrite over RealTek. However, the OP explicitly said he wants a simplified setup for practicing. Not recording, not mixing or mastering. For that, the built-in interface should do just fine. I do the same thing when I go on holiday and only want to be burdened by my laptop and nothing else.
7fc3f7cf58