John Vere

This looks like that USB driver limit of 10 issue. Watch this video to resolve issue.

So Ok. You fired up Cakewalk without first watching tutorials or reading the documentation and it doesn’t work like YOU think it should work. Every DAW is about the same as far as learning curve goes. Cakewalk is a top quality DAW used buy many of us for a long , long time. We used to gladly pay the $500 for it only a few years ago. Don’t let the price tag fool you. You are more than welcome to go pay $500 for Pro Tools the so called industry standard and report back to us about how easy it was to use ? Go to the tutorials sub forum and start watching and feel free to ask more questions if something isn’t working properly for you.

Well the best method would be to figure out how many Milliseconds the new audio is late, or sometimes early, To do this set the time line on milliseconds. In my first screen shot which is demonstrating Midi latency, you can see the frozen audio track is about 400 ms late of the Midi note but below that is the Loopback using ASIO mode and that track is right on to the Audio loopback. So then you enter 400 ms in the adjustment box under sync and cashing( I think it's a negative number so might have to try both - and +. and then re do the loopback test to see if it is now close enough. A little bit is not noticeable but 400 ms is a lot. Once this set you should be good to go and not have to think about it. This shows testing my Tascam interface. Not all modes are supported by some drivers.

Glad to hear it’s all going well. If you’re curious about how well your system is syncing you can try a loop back test Its tricky with a mike because there’s not direct audio route. Take a Midi drum track and freeze the instrument to create an audio track. You want a nice obvious transient spike Now create a new audio track and set the mike as input and set in record standby DONOT turn on input echo or you will get feedback place the mike 6” from the speaker and play the drum track testing the level Now record a measure Place the now time right on the original transient and zoom way in and take note of where the newly recorded tracks transient is . For my tests I used a buffer setting of 256. A lower setting will give you better results but my system can’t handle lower settings on a day to day basis. Every system will be different. The tests always came out with ASIO being right on but all other drivers were late by various degrees with MME being the worst and WASAPI exclusive the closest but still off by 1/32 So if you can work at lower buffer settings the amount of off set might not even be noticed. And you can adjust for this in the sync and cashing options

I’d be also interested as I have a Korg 05R/w and if I use it as a hardware device that Mode thing always needs to be changed and sometimes I forget what mode I was using when calling up projects from 10 years ago.

So therefore you will have sync issues. WASAPI mode is just fine for those who only use loops and Midi but any one who needs to add vocals or live instruments needs an ASIO audio interface or they are hooped

This is probably just a sample rate conflict. If your Windows default is 44.1 and you open Cakewalk and load a 48hz project you will hear the pop. This is why I recommend you pick a sample rate and make sure all your settings are the same. 1-Audio Set up

CTRL drag. 11-Audio Tracks

Be warned, overdubbing audio using generic audio drivers will result in a timing offset of up to 1/16 note. USB mikes are gereally for Podcasting and not recomended for serious audio production where timing and sync is critical. 1-Audio Set up 106-Why ASIO is important

To delete the data in PVR, To select all zoom out until you see the whole song. you can also delete it in the events list but that's slower. https://www.veed.io/view/6dccb5ac-2150-4ce4-9509-d18077e09ddb

Ya. In my video on Shopping for an interface I thought I’d covered just about every possible feature but that’s one I missed because I’ve never heard of it before. But I do recommend the on/ off switch. Anyhow at this point re reading the thread my conclusion is. This interface is probably as good as any in its price range. With that comes higher RTL (round trip latency.) My guess is in the 20 ms range at a safe buffer of 256ms. RTL does not matter if you use direct monitoring. It only is noticeable when you turn on Input Echo on an audio track while recording. Solution is Turn off input echo and use direct monitoring. In the OP there’s also a mention of Midi latency which is common if your latency gets increased by using certain effects. Solution bypass the effects while recording. If your interested in a little educational material on these topics here are some of my videos that explain clearly how to set up and record both audio an midi.

As I said 10 ways to do anything in Cakewalk. My routine is select all CTRL A. Go to “tracks” menu and selected tracks output and choose the Master buss

You are obviously using a old version of Cakewalk. The new dialogue is much easier to use.

If you just delete the lane the data is still there you need to delete the data.

Huge difference. But it’s sort of you want that for your OS drive and your data drive too if that’s where you put your projects. Nothing terribly wrong with using old school drives for storage if they are at least 7200 RPM. But SSD drives are dirt cheap so for an upgrade to your machine you can’t loose. If you do buy a new computer down the road you can swap them over. And yes you need at least 12 GB of RAM these days.

Midi is data so if you’re keyboard is successfully entering data to cakewalk then the only difference would be the data is incorrect and that can possibly be a channel or the range of the notes. Are you using Omni?

Actually now I see this switch is unique because it has the mono option a handy dandy idea. Still a Blend controller that you can select any amount of either input or playback works best. I find the switch system found on many interfaces a comprising feature. You then have to turn down your master buss if the playback is louder than your input. This switch is the same but adding the mono option at least is a nice option that I’ve never run across before.

Ya I didn’t elaborate because I figured everyone involved in this thread understands this stuff pretty clearly. I have never had to adjust my Hardware outputs and for me they are always hidden. Actually if you load a basic template and default workspace I think even the master buss is always hidden. There’s been plenty of newbies asking where to find it. I was wondering why the default in export is always the Hardware and not the Master but I guess as said people might not use busses. In my case it’s not an issue as I analyze my master buss and always analyze the exported file as well. There never a difference. But if people don’t understand how signal flow works and they are not even aware they have a master those exports might be wrong. Example the habit of always muting your master buss to make sure everything is routed there. Then the scenario where someone forgets to assign their tracks correctly and some tracks are going directly to the Hardware outputs. Those are now totally bypassing any limiters on the master buss Guess why I know this ?

That wasn't my point. The experiment was to see what actually would happen if you did turn these down. I don't think many people would ever touch them as they are mostly hidden from view. But the OP was about signal flow and I was just confirming, to myself, that these are definatly the last step in the signal flow before audio is exported, not the Master bus.

This got my curiosity about something when you mentioned about people getting different results on export. Personaly since Sonar 8.5 all my exports have always been perfect renditions of what's happening in Cakewalk. I'm always mistified by posts about this topic. There's actually one right now here. But the question popped into my mind was how we are told your audio interface has zero to do with export becuase it's all internal. But what about those Hardware faders? SO I just tried an experiment where I turned them down to -15 db and exported using the default I've always used which is "entire mix". The resulting file you see I dropped into You lean to analyze and sure enough the export is -15db. So the Hardware faders do matter for export.

Your screen shot doesn't show the midi channel, bank and patch dialogue boxes. It's either off screen or your workspace has disabled that view. Set the Track Control Manager to ALL to see those dialogue boxes. It's found at the top of the track header and it will either show Workspace or Custom. I have a bunch or tutorials involving Midi and using VST's as well as harware set up.

Please start a new thread for your topic. It's a big waste of our time because people open this thread and read it not always seeing the date.

This is a very advanced complex operation and this video is the best one I found that explains the process clearly.

M Audio M Track Duo- $ 140 Can. ( I was wrong about the $70, that was on E Bay ) So it's around the same price as a Focusrite Solo, Presonus Audiobox 96 or a Tascam 2x2 all which are excellent interfaces. M Audio has been around a long time I have a Fast Track Pro sitting on the self. The drivers are outdated like your Tascam. Looking in the specs -This is not clear if it has Direct monitoring or not. • USB/Direct Mono/Direct Stereo switch for monitoring mic, line or instrument inputs in stereo or mono Can you hear your DAW playback and the Mike input in the headphones without turning on Input echo? The switch looks like it's either your input in mono or stereo or the USB but not both? That's very odd. I didn't think anybody made an interface these days without direct monitoring. FYI- Direct Monitoring = hearing the direct signal from your input mixed with the DAW playback. This results in Zero latency. This means you can record latency free at any buffer setting. But higher buffers equal more Round trip latency and you will not be able to use Input echo. Noises in recordings can be caused by DPC interupting your audio streaming, run this tool to check- https://www.resplendence.com/latencymon They can also be caused by dropouts because you're using too low a buffer setting. Also if you have effects in the project that are CPU intensive. I always by pass effects while recording by using the global bypass button.

It might be fine, and I could be wrong but it's an old saying- You get what you pay for. The Behringer UMC 22 comes to mind as well. Both are sort of Mac oriented companies so the devices work great on a Mac but Windows and Cakewalk tend to be more picky about drivers. Have you done all the proper ASIO driver set up including what you might want to set in Windows. Make sure there's no other drivers like Asio4all and Real tech etc. The Tascam driver will not interfere but make sure the M audio driver is showing in all the boxes in your audio preferences settings and especially the sync and cashing timing box. Make sure to use this driver https://m-audio.com/support/drivers