John Vere

It doesn't have ASIO drivers, it's basically 1/2 step up from using On board audio. and I've mentioned this in at least 3 other threads. The above mentioned M track solo apparently does not have an ASIO driver either so another pointless purchase. Looking on Sweetwater It seems the ASIO drivers will start with models at around $100. The Focusrite Solo and the Tascam 1x2HR would be my first choices knowing the quality of those products and drivers. They are on sale right now. Can you not return the useless interface in exchange? we are talking about $20-$40 difference to get you running smoothly, you've been bashing your head against the wall for a long time now.

It’s always a plug in . There’s been no change to export for a long while. Even the warning tells me it was probably a plug in. Did it generate a crash dump. Send it to Cakewalk.

Which just reminds me they better get that update out there pretty soon or a million people will get the above message for the first time in a long while.

It’s a typical widow action screen where you either execute an action or close it. Just about the most common feature in most software. It’s identical to the little window that will pop up when you try and close any program with out saving. Some have a box that says “ don’t show me this again “. Or like in this case you can disable it forever in preferences. But the thing is they all open automatically for a reason that is et in the software to trigger it and requires action on your part to close it

Thanks, forgot about that annoying feature I disabled it long ago.

No. Read my reply in your other thread. I find if you open a project and close it with out saving it might not show on the start screen list. But you say you were working on it. A confusing thing you said was during scanning and loading? That doesn’t happen until you choose a project. Otherwise You open Cakewalk and the start screen will appear unless you disable it I don’t think Cakewalk scans anything other than phone home to check for updates during loading and there’s no visible signs of that.

Absolutely. When I was testing stuff I’d often have 10 in a bin. Beyond that is sort of unreasonable. I think there’s a limit due to the console view but in track view the track can basically fill the horizontal height of your screen

Workspaces don’t set or save ins and outs. Those are per project settings. Workspaces are global to all projects and if set to none can be totally ignored. They are used to save you screen layout including what features are showing their widgets like the control bar stuff. I only have 2. One for using one monitor and one for using two. But you can get fancy and have saved layouts for anything possible. The dumb thing is instead of none or advanced they set the default to Basic which sucks because it hides a lot of features. Back to the OP midi inputs will reset if any changes are made to which devices are connected. I make sure to always have devices connected before starting.

I made some screenshots of how I make a backing track from a song that has vocals and guitar. You see the routing. The vocals had an effects send so the effects bus need to be mutes as well. This is what my export dialog looks like.

A screenshot of the export dialogue would tell us more. I’m not even sure what the one above includes. It seems only part of your console view. You obviously are not understanding your signal path to the master bus. Another possibility is a hidden track.

I think you covered it well. I actually have very, very rarely automated an effect. Reverb it is taught should be a global effect shared by the mix. This puts your song in a space, like a room or a concert hall. They say using a different reverb on multiple tracks creates a muddy mix. It’s sort of like having each musician in a different location. So I always use a reverb bus and use the send from the tracks I need in that space. But as said above there’s no right or wrong and I often will use a touch of built in reverb if a VST has it like True Pianos and Addictive Drums. Chorus if often included in a VST interface and if it isn’t I have a few options from my freebie collection that go in the effect rack. Pan? That’s built in to the channel strip.

There’s many free meters available which you can add to the effects bin. The Cakewalk meter is strictly peak just like all mixing consoles have. Span has RMS and LUFS as example.

Exactly but sometimes you come up with adding a new track or like in this case are still editing midi. I always bypass all effects before proceeding. Most effects are more or less harmless but especially mastering effects and well known CPU hogs live Waves and Isotope will cause lagging.

The audio interface has nothing to do with this behaviour. It’s is always plug in delay. Easy to test and easy to resolve. Have you not tried it yet?

Yes there are many of us old farts still here much to the annoyance of the younger folks. To bad the guy who made the video wasn't actually a long time Cakewalk user. It would have be much better. He really didn't dig that deep. There's more missing that shown but I actually pulled a few things from it I was unaware of, like the short bit about the Apple version. Now I know why I remember trying out Cakewalk in the late 80's. In my town we were all Atari users because the only computer store ( K& B Computers) sold them as well as they had a Roland dealership. There was this group of 5 of us who all used Atari's for live performance. One of us was Jeff Koftinoff http://www.jdkoftinoff.com/main/Information/About_Jeff_Koftinoff/ He learned how to program and that was his life's work. I on his web site he has removed all the links to his software. He later worked Roland in the MT 32 days. The software used to be available free on Tim's Atari midi world and I see that web site is now gone too. I'm going to have to learn how to use the Wayback machine. But anyhow, the software was called the Pro Midi Player ( I found a link https://exxosforum.co.uk/atari/mirror/tamw/promid.htm ) and it was brilliant. You could drag and drop midi 0 sequence files to create set lists, it displayed Lyrics as TXT file if the names matched, remember 8 digit names= LTMYFIRE ( name that song and win a prize) And at my request he made use of the joystick port and we invented a foot controller with 5 buttons. Start, Stop. Up, down and of course PANIC. We all used Dr T KCS ( Keyboard Controlled Sequencer) and then learned how to hack/Copy software floppy's so we would share programs we chipped in on. Yep, that stuff was expensive in those days. All of this showed up free on Tims Atari world so no regrets about being a pioneer software pirate. That's where the video triggered a vague memory of trying Cakewalk on an Atari. We had an Apple emulator and I remember having possibly used the first releases of both Cubase and Cakewalk. I could never figure out why I might have tried Cakewalk because I never bought a PC computer until 2003 so that would explain it, it was the Apple version. When K&B computers closed down in 1992 I took over the Atari and Roland dealerships. Cactus Music had it's perks in that during that decade I got my gear at cost. I still have a lot of it! Later on in the 90's The Roland sales Rep gave me a Copy of Cakewalk Guitar Studio. I didn't have a PC to run it on but I kept it and that's about when I joined the old forum in 2004. I still hate PC's.....

There will always be system latency. A/D converter, Audio Buffer and so on. With a real good ASIO audio interface you can use a lower buffer setting that can help but sometimes low buffers can cause audio glitches if your computer is not up to the task. So best way to record digital drums is to send Cakewalks output to an Aux input of the drum module plug your headphones in there as well and play along with that to record the midi track.That way there will be no latency heard. There’s also the option of connecting the audio output of the drums to your interface if you have one and use direct monitoring. Trying to use VST drums when recording will most always result in hearing a echo which is annoying. Under optimized conditions you can make the echo shorter but it will always be there. So as said above turn off input echo for the midi track so the VST is not playing live.

If you are still editing then bypassing the effects will be the solution to a lagging playback. Use the toggle in the control bar.

That is an ASIO device you will get way better performance using ASIO. I don’t think that has anything to do with editing performance. That’s usually more to do with DPC latency. Run this test https://www.resplendence.com/latencymon

Your missing the point. You can choose entire mix but if only a few tracks are selected and some are not that is the mix. So the old school method was select none. But as I pointed out you can do exactly that inside the export dialogue now. I've never had an issue once I learned how it all works. It wasn't that hard really. And you can make up your own pre sets or even create tasks so there's no guesswork involved. Only thing I keep an eye on is the Range.

This is not correct. ASIO drivers will automatically change to the sample rate used by the application in focus. This is why you might hear a loud pop when switching between sample rates if you go from Cakewalk at 44.1 to watch a You Tube which is 48. That's why I advise people use 48 for Cakewalk. It's better quality and there's no reason anyone would use 44.1 in these days. Why? You can change the sample rate of a Cakewalk project at any time. If it is all Midi then you simply open the audio interface panel and change the sample rate. You'll here a little pop and the new sample rate will show in the transport module. If there is any Audio you cannot change the sample rate. You first have to export all the audio as stems at the new sample rate, delete all the audio from the project , now change the sample rate and then drag the exported audio back to the empty tracks they came from. The bit rate is automatically set by the interfaces driver @ 24 bit for most. But Cakewalk can contain all bit rates in a project. An besides the OP seems to have solve the issue.

I guess I should have paid closer attention! It's a family habit of saying things backwards. Now I'm trying to record the narration and I keep saying PVR. I just re typed the document and I'm going to say "Piano Roll" for short. It might stem from me being a long time Railroader. I worked for the CPR, Our town has Historical locations for the Kettle Valley Railroad = KVR. So PVR just sounds better. It is the largest railway network in the world apparently.

I realized while making a new tutorial for the Piano Roll view that I for some weird reason have always called it the PVR? Nobody has ever corrected me. I then did a little searching and I see lots of posts where other long time users also call it the PVR. Is there a historical reason because it seems this would be incorrect?

I hope you didn't miss interpret that part of the video as instructing you to remove ALL ASIO drivers where it's intent was to remove ASIO4 all or any unwanted ASIO drivers. It was not to remove the Focusrite driver.

What a lot of people don't realize is there is a hidden options view in the What to export dialogue to the right that allows you to select the tracks from within the export dialogue. Once again Cakewalk likes to hide important things in an attempt to keep things looking simple? How many people every read the documentation or would notice a little tiny blue arrow? I have not bothered to use select all or select none for a long time with 100's of exports without issue. The new export features cover this. In my screen shot only the Guitar track 6 would be exported. Simple. The Range selection is not about what tracks are included, it is to select the range. Entire mix will export from 1.01 to the determined end of song or track which as we all know might be way to long. You use Time Selection to top and tail the export.

Sorry my comment was about all I could think of when I read about the OP’s track count. Just goes to show you no two people will have the same workflow and as long as they have the time and patience for their method that is all that matters. My clients never had the budget to waist time in the studio practicing parts. My studio hand out to prep them said “ Do not book studio time until you are absolutely sure you parts are as good as you can possibly perform them” I had learned earlier on that somehow people were showing up totally unprepared so it was painful and they were often chased away to go and work it out at home. This in the end worked out and parts were often put down in one take. So a lot of my workflow remains unchanged since those 8 track days. Im a huge fan of deleting any parts I feel we’re not up to snuff. I only use overwrite mode as example. I just start with one track and keep redoing it until I feel that was my best performance. Then I record a couple more that I might copy paste from if there’s something better. But on topic. First I don’t think there is a copy to location box but there is bounce to tracks that might somehow be used. I think if I was faced with 50 takes I would first group the tracks together and use colours. Then I’d start deleting.