John Vere

So in WDM mode things are worse. The Motu just does not like anything other than ASIO and WASAPI shared. Look at the gibberish I get in WDM mode..

The test was a total failure. I could select both interfaces in preferences under WASAPI exclusive. I could also select either interface in the 2 tracks I set up but when you hit record it tells you the old pop up that the device in use does not support the currant driver mode. So testing individually it turns out the Motu does not support WASAPI exclusive. The Focusrite works fine under WASAPI exclusive. So once again every manufacture has a little bit different coding in its driver.

This was good information , something I actually know about but always forget. Syncing is important and this is why I use ASIO so that it is correct. Dang audio is complicated! Anyways I guess it's back to a 4x4 interface and possibly a little mixer to do duty as the second volume control. I guess I got away with 2 interfaces for live recording because live recordings have a ton of latency anyway due to leakage. One could do a latency test easily buy splitting a signal to both interfaces and comparing the 2 tracks. I might just do that! I wonder if Cakewalk would always use the interface that is at the top of the device list for the clock?

Ya agreed, The SPDIF is for my Yamaha 01v digital mixer and it is just to big to keep set up, even though it blows the Mix 8 out of the water with options, the mix 8 is super small. I will someday build a under the desk slide out tray for the Yamaha. But the other issue it has is then I'm stuck with 44.1.

I'm glad you brought this topic up because I had never done this and tried WASAPI Exclusive. I always use ASIO and just turn off the interface I'm not using. I have to keep my Scarlett alive as it has SPDIF and the Motu doesn't. Funny how WASAPI mode is calling the digital ins and outs analogue. But this gives me 8 analogue inputs if I need them without dusting off the Tascam. There are lots of small mixer around I used to have a little Yamaha too. I have the Mix 8 for the studio and then a Mackie Pro effects 4 that I used for my solo gigs. For it's size the Mix 8 does a lot. Especially useful is the Tape input which you can send to your headphones or to the Main outputs or both. If I want to do a loopback test all I need to do is push the Mains button if I have the mixer running back to inputs 3/4. I have used it in many configurations. I have a Lexicon MX 200 hooked up and when I was tracking clients I would use it to give them a different cue mix than I was hearing. As I said my Scarlett could do all that but was always confusing because of software.

Out of curiosity I hooked up my Scarlett. You can see by the screen shots that in ASIO mode it took over from my Motu which I believe is Cakewalk's system of using Alphabetical order for in/out defaults. Example " digital SPDIF" often takes over as the master bus output. But as you see in both ASIO and WASAPI Shared I can only use one or the other interface. But in WASAPI Exclusive I can easily use both.

I have nothing against it if your using W7, and 4 years ago I was using it on a W7 laptop exclusively and it was fine. But WASAPI is integrated into windows and has made asio4all obsolete. We did some testing and WASAPI exclusive got better RTL on loopback tests than asio4all. Asio4all performance is just like WDM mode and WASAPI is more up to date with W10 inclusion. Both would require loopback testing and timing offset adjustments to work perfectly. If your not overdubbing it won't matter. I guess the only case where something like asio4all might work better is when an audio interface doesn't support WASAPI, like my 14 year old Tascam. Asio4all at least would show all the ins and outs.

Sounds good. I never think to look for used gear. But interfaces become outdated so fast therefore I like to keep mine no older than 5 years. My Tascam us1641 is 14 years old and still has drivers that work. But last update was 2014 so that is going to die someday. I have always bought interfaces with 4 outputs because of my set up where I use a small mixer for headphones. The small mixer ( Mackie mix 8 @ $ 80) can also be run to a second pair of speakers and therefore has that volume control your looking for. So that's another option. Right now that's patched to a sub woofer I rarely use. But one thing for sure I agree that the reason I have that small mixer is due to wanting those physical controls handy. My Scarlett 6i6 has a software mixer and it's a royal pane to use. A lot of interfaces cheap out and don't have controls on the front panel. I avoid those. Give me lots of knobs I can see. I think the ultimate answer for your question is as Noel said and it really depends on the manufacture and the ASIO driver. I know I've read a few times of people using 2 Roland interfaces together. But getting back to using what you have, I still would avoid asio4all if you can as you really don't need to stack that on top of the already available WASAPI. We did some test a year ago and WASAPI is a very good alternative driver and you need not contaminate your audio system to use it. I used to record our band and I would use WDM mode as WASAPI wasn't really there yet, I used my Tascam us1641 and a Yamaha mixer that had 2x2 USB. Worked great gave me 16 analog inputs and midi...Used this set up for a long time without a hitch. I would easily switch back to ASIO for overdubbing etc. I often switched between WASAPI shared and ASIO when I was making tutorials but then discovered my Motu M4 has a loopback so I can use other apps with Cakewalk running now. So I think your easiest rout might be the 2 interfaces you have in WASAPI mode.

I actually agree with what @bdickens is advising. For the price of another "wrong" interface you could purchase a 4x4 interface like the Scarlett 4i4 or the Motu M4. Those are both solid reliable interfaces that have 4 outputs and not expensive. I see another Presonus iTwo would be $230 ( can) and the Motu and Scarlett are only about $75 more. If you need 4 outputs you should purchase the proper device. Simple logic and good advice. ASIO4all is bad advice. It is not ASIO, it is WDM mode in a wrapper. So your actually worse off than WASAPI which has much better performance.

In my Download folder is a sub folder Called Cakewalk. Inside that folder will be all the versions I downloaded seems starting in March with what might be an early access version. I never created this folder. The Cakewalk download must have. Does anybody else have this sub folder? There were also 2 versions ( 147 and 155) that were not in this folder. Any way if you open your download folder and go to views and select "details" you will see the dates. I'm using Chrome. I can easily roll back to a prior version using any of these installers ( I suppose ) Myself I would never update software while I have a work in progress open. I would at least close the project first.

A few things come to mind. 1-Open the synth rack from the view menu and make sure there isn’t 2 versions running. 2- insert a new version and copy the midi data to the new track. The original might have just wandered off which sucks but you just never know with computers

The update notice is always on first opening Cakewalk. I almost always do it right away as it takes only a few minutes at most. Next time I’ll see what happens if I don’t close Cakewalk. But an IT friend of mine said even though things have gotten better he still is in that old habit of closing all apps before installing any software. And always run as administrator just in case Old habits die slowly.

Actually this is the problem. The first time I did the in app update it did not close Cakewalk and got all screwed up. I learned my lesson and now I make sure to close Cakewalk before I run the install program. This is not abnormal at all most software works this way.

50! That’s pretty young for this forum

I totally agree that it is not user friendly at all. Been like that since the Assistant was introduced

Ok then you should delete everything in your download folder before you update and it will be the only file

Atari and DrT KCS. I-made 100’s if not 1,000’s of midi files on that system right up until 2004 when my monitor died. I was forced to switch to PC. Cakewalk became my DAW. When people say Cakewalk is old school I will assume they are of the new camp of wannabe music creators that want the computer to think for them. Oh my gosh I actually have to think

Install the one with the current date

It is best practices that you close any software before you update. So wait until it says it’s ready, close Cakewalk go to the download folder and then run the installer

I think the other important tool missing is a proper lyric track. It would be nice to have it tied to the arranger track somehow as a second lane at the top.

I have always had the start screen shut off as well. I use the File menu out of habit. If I click Open it takes me to my Data drive where I have different folders. One of them is a Template folder but the templates are all actually CWP files. I was only using the Start screen in my Tutorials as that's easy for beginners to figure out. But for me none of those Magic words work either. All I get is the screenshot.

Downloaded midi files should always be OPENED not imported. If you have no midi outputs selected in preferences then the TTS-1 will automatically load and play the file. To change patches you need to use the dialog in the track inspector. Those will override the changes made in the TTS-1 GUI interface. If you want to use the GUI then set bank and patch to "none" If you want to replace the TTS-1 sounds with better instruments like the SI drums and bass then insert those and set the appropriate track output to that synth. Or drag the midi data to the Instrument track.

I think generally temp files are safe to delete, and ya, for sure the Melodyne stuff too. Possibly to be sure copy those folders to an external or back up drive just in case. But my guess is they won't be missed.

Yes what I want is a midi track per output. If you need more midi tracks to share an output they are easy to add. The way I've been doing it is to not use the split track option. I used to be a big believer in using the split track method for midi. I only now use that for instruments that have only 1 output and where I need more than 1 part in it's own track. Piano as example, left and right hand parts. I have converted to using Simple instrument tracks and really gotten to like it better. If you say, use AD drums as example, I'm not going to need 2 snare tracks and 2 kick drum tracks so the Simple instrument track set up is perfect. I get one track per output and I can even delete unwanted tracks. It's less confusing to have the midi data right there next to the audio track. So this bug would never happen in my workflow. That's why I was confused abut the OP.

Sorry Will, I was only going by your screen shot in the OP where you do not show selecting split tracks. You only show Instrument track per output. So I tried it and you are correct . What it seems to do is insert 1 midi track and then the an instrument track per output plus selected number of synths. If you change instruments it automatically selects how many outputs are available. If I select SI drums I get 1, Power drums 16, Addictive drums 9 and TTS-1 you get 4. For AD it opened 9 instances of the GUI. Each with 9 audio tracks and 1 midi track or 10 tracks per instance then x 9 = 90 tracks For the TTS_1 it opened 4 GUI, with each having 4 audio and 1 midi track =5 tracks x 4 = 20 . So there is some logic behind it, but it is backwards. It should be creating 4 midi tracks and 1 instrument track. And not multiplying that as well. The thread would have been shorter if your second screen shot marked WRONG was correct. It only took me a few minutes to find the issue once I knew what you were trying to say. This problem is using the split instrument track option not the instrument per output.