gmp

Here's the bun, let me know how it does https://onedrive.live.com/?id=C256E2DAE26B22A5!105&cid=C256E2DAE26B22A5

Here's the bun, let me know how it does https://onedrive.live.com/?id=C256E2DAE26B22A5!105&cid=C256E2DAE26B22A5

Nothing unusual, no delay active, but 1 is on Aux send 3 lot's of plugins on blank tracks, almost none turned on, - I'll see if I can send you a bun later tonight

The Aux Track which shows up in the Track Pane (not Bus pane) has the output going to one of my sound card outs, not back to the bus pane master bus. Go ahead and try again, if you get no dropout at 4:07 with the input echo off, then maybe it's fixed and I simply need to delete it in my template and create a new one. Thanks for your help with testing

Thank you Chuck E Baby for the link below to the similar problem involving Aux Tracks. This enabled me to fix my dropout problem

Thank you Chuck E Baby for the link below to the similar problem involving Aux Tracks. This enabled me to fix my dropout problem

In my previous post was was incorrect - the problem was not solved and cropped up again. I finally did fix it and it has to do with having an Aux Track input echo turned off. If it's "on" there is no dropout Here's my new post explaining this and warning others that may have this problem.

I've had a few posts trying to solve some dropout problems I've had for about a year. It turns out it's caused by turning the Input Echo on an Aux Track off. On my template I have an Aux Track and the input echo button is on. But I also use input echo to trigger 2 tracks at the same time - a piano and a bass. That's also set to "on" in my template. At times I want to turn the input echo off, especially i I cloned those tracks and have several now "on". So I always use the global icon in the Control Bar to turn off all input echo buttons, unfortunately it also turns off the input echo button on the Aux Track. Here how you create an Aux Track: right click bus in bus pane - Insert send - choose new Aux Track Now look in the track pane and you see a new track named - Aux 1. This is the track that the Input Echo must be set to "on" otherwise there will be a recording dropout at 2:08 or 4:17 This has also fixed a long standing problem I've had with when I leave CbB and then come back about 5 min later I see a dropout message at the lower bottom right. Last night I tested it with a stopwatch and the dropout comes right at 4:17 every time, if the Input Echo button is off. If it's on, I never get that dropout. So this has solved 2 long standing mysteries for me. The bottom line is Aux Tracks are great, as long as you understand this strange little quirk. This happens regardless of whether you're actually using the Aux Track in your project. If it's there in the Track Pane then it can cause this problem.

Try this recipe Here how you create an Aux Track: right click bus in bus pane - Insert send - choose new Aux Track Now look in the track pane and you see a new track named - Aux 1. This is the track that the Input Echo must be set to "on" otherwise there will be a recording dropout at 2:08 or 4:17 Let me know if this gets a dropout This has also fixed a long standing problem I've had with when I leave CbB and then come back about 5 min later I see a dropout message at the lower bottom right. Last night I tested it with a stopwatch and the dropout comes right at 4:17 every time, if the Input Echo button is off. If it's on, I never get that dropout. So this has solved 2 long standing mysteries for me

I've also had the 2:08 dropouts and solved it, by archiving some tracks that were using an Aux Track. I'm also the one that was having the strange dropouts at 4:17. I could be recording an audio track or even recording a midi track and get the dropout. Thank you Chuck E Baby for the link to the similar problem involving Aux Tracks. It turns out that also fixed my problem. I just turned on the input monitor button on my Aux Track and the 4:17 dropouts are gone. So both of my problems with dropouts at 2:08 and 4:17 were related to the Aux Track input monitor. Strange mystery appears to be solved

Thanks Bob for sharing your experiences. Some of us may find ourselves in similar situations, so it's always good to hear. I hope the new motherboard transition is smooth. I read that an M.2 HD can connect with SATA but it doesn't have the speed increase, it's just like an SSD HD as far as speed. But yet in your disaster situation maybe it would have given you some peace of mind to connect it to your old computer just to know it hadn't lost data.

Did the lightening strike take out any HD's? I backup my 3 computers to a USB HD every night and I also run Backblaze online backup in case a real disaster happened like all HD's got fried or the house burns down or anything unforeseen. Hopefully I'll never have to use Backblaze, but it's there. Thanks for all the info and especially alerting me of the M.2 HD - I must say I'm amazed at how much faster it is than my fast 2 SSD HD's I use for boot and samples. My computer is 4 years old. Can I get that kind of performance with my computer if I have a PCIe slot? I think I do

I have a desktop computer and see no reference to Wi-Fi in device manager unless it's hidden. Thanks for the info

I did uncheck "power option on all USB hubs, but thanks for adding to the list

Thanks for the printer experience you had. My Canon MX920 is connected by USB to my DAW, but it first auto installed itself using Wi-Fi. I later tried to uninstall it and do the install on my DAW. I'm not sure either which way is best for the install, maybe no difference. I do have an external powered USB hub for things like printers and dongles

I'm doing everything suggested so far, but I'm wondering about the Wi-Fi. I have an AT&T U-Verse modem for my internet. It also works as a router giving internet and a wired network connection between 3 computers, including my DAW. I don't think Wi-Fi is setup on my DAW, because under Networking and Sharing Center. and Change adapter setting - I see an Ethernet connection and not a Wi-Fi. I know my U-Verse modem has Wi-Fi because clients with a laptop can connect to the internet using my password. And when I first got one of my Canon printers, I was surprised that it seemed to install itself on my DAW using it's wireless connection. So is it possible I do have Wi-Fi enabled on my DAW? If so I'd like to disable it

The optimization lists I have are pretty old. Does anyone have a fairly current list?

Today it happened with the transport stopped. It doesn't always happen that way, but always messes up when the transport is moving.

Marker bug in 2019.07 I use F11 to add a marker. When the transport is stopped it works fine to add a marker and to name it. If the transport is playing back or recording and I add a marker, I then right click the marker to bring up the window and name the marker and hit OK. The marker window pops up again (this is the bug). It shouldn't pop up again. I hit OK a 2nd time and the window goes away. Has this bug been reported?

It turns out that Windows Update changed some of my settings that I had setup when I first installed WIN 10 in March of 2016. I found that Windows Search and Win Update were enabled, plus a few other services that I had disabled. Once I disabled those it may be that fixed the problem. I tried your suggestion of 750 for Midi Prepare Buffers and got no dropouts, then went back to my default of 250 and that worked too. Still I'm leaving it at 750 since you said that works better with MOTU midi. After I tested midi 2x and also audio recording 2x with no dropouts, then I went back to a problem song and found it still dropped out at 4:17 recording midi or audio. So today I created a new song and copied all the tracks from the bad song into the new song and I have no dropouts for midi or audio. So for some reason that song turned into a corrupt file, best I can tell. I still have this strange audio dropout message appear after I've left the computer inactive for a few minutes or hours. So it appears that this strange 4:17 dropout mystery is finally fixed - I hope. I'll post again if it crops up again. But I do have a question. Back when I did my WIN 10 optimize in 2016 I did this tweak: Device Manager open the Disk Drives menu. 2. For all of your hard drives, right click on the drive name and select Properties 3. Go to the Policies tab and check the boxes to Enable write caching and Turn off Windows write-cache buffer flushing Again Windows Update changed this setting. "Turn off Windows write-cache buffer flushing" was unchecked for all internal HD's, I rechecked it I also found that Sound Exclusive Mode was also changed from disabled to enabled. This is in Control Panel/Sounds under properties for sound cards. I went ahead and disabled it for my on board Realtec sound card, but left it enabled for MOTU audio What do you suggest for these settings? Or does it matter?

Thanks Jim, I'll try this. Mine was set to 500, so I just raised it to 750. I'll test this tomorrow

Thanks I watched the video and made sure all my settings were the same. They were already set that way - but thanks for the very clear clarification of this issue

I assume you talking about this Device manager/usb/Power management - uncheck box - allow computer to turn off this device to save power All the boxes are unchecked for USB Hubs. Is that what you're asking? thanks for your input

Lots of good suggestions and ideas to explore - so thanks everyone. I did some more testing and checked my notes some more and it turns out that I do get a dropout at 4:17 whenever I record a midi track, but not always on an audio track. I do have a few songs that do consistently get an audio dropout at 4:17 and this does happen every time. If it were 1 song I'd attribute it to a corrupt CWP file, but it has happened too many times on different songs over many months, maybe a year. I record quite a lot, but I don't have that many songs that are longer than 4:17, so this doesn't come up that often. My MOTU audio card has Midi also, so I'll try some tests with using a different midi interface and not use the MOTU midi. I also found somethings in the event viewer that has me wondering. Around the time and date I had a midi dropout, Under event viewer/windows logs/ System I found this Background Intelligent Transfer Service The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Next time I have a midi dropout, if this same thing comes up I'll disable it and see if that helps. I need to run Latency monitor to see what that gets, in the past it was fine. I have my computer tuned for real time audio, yet sometimes Windows updates change those settings, so I looked that up and found many settings were enabled, so I disabled them again. If anyone has a more updated list of real time audio settings, it would be worth comparing to my old lists. I've disabled USB sleep settings I've noticed before getting a dropout later than 4:17 only to find out that I punched in and the midi track was 4:17 in length and then it stopped. I also went back to a problem song for audio dropouts and started the recording at 14 sec and it did dropout at 4:33 after going 4:17, so it's not an end of the song issue. I am using 2019.07 with the same results. I"m wondering if I should do a clean install of CbB. I've been using Cakewalk since the DOS days and this computer for 4 years. Upgraded from WIN 8.1 to WIN 10. I think this dropout problem is related to another problem. If I leave the computer for a few minutes or hours, when I come back I always see the audio dropout message at the lower right, even though there was no activity since I was gone. I have to click the top bar of CbB to bring the focus back to it. And sometimes when I'm playing the midi piano, the piano stops responding and I have to hit the spacebar 2x to get the focus back on the piano, then it plays again. Something is clearly happening with dropouts for no apparent reason, like the usual reasons of many tracks, FX, etc

Every single time I record either midi or audio, I get a dropout that stops the transport and displays the audio dropout message at 4:17. ? For this to happen I have to record from 0 sec to 4:17 without stopping. This happens on every song, even ones with nothing else recorded. . Has anyone had this sort of predictable dropout happen?