Milky

In my experience, there can be a delay of up to an hour between nags, so, if the update wasn't that long, you might get lucky. Even if you do get the nag, it is not that bad. It extols the virtues of Breakaway, but sounds a bit like a radio commercial. Most people wouldn't notice to be honest.

If you had both your playout PCs going to a mixer, it would be a simple matter to cross fade between the two so that the backup PC was playing whilst you update Win10. Once it comes back online, you can cross fade back the other way, or wait until the end of a track and start the upgraded PC.

The config files can be backed up (there is an option within BA1) and moved to the other PC as a complete folder. It is also possible to include the config address in the command line (ini_folder=c:/blah) so you can have it stored almost anywhere that is accessible to the PC.

I run BA1 on Win 10 with no stability problems, but I DO have the Management package, and therefore run BA1 as a service. I'm not sure that running as a service is the entire answer, but it certainly works for me. I have, on occasions, run Breakaway directly (not as a service), but only for relatively short periods. I never had a crash, but the running times were not very significant.

Do you run the TX version as a service?

Having said all of that, I would look at possible driver or code bloat as the culprit. Look at all unnecessary programs and processes and shut them down permanently. Also check for scheduled tasks. A lot of updates are now set up as a scheduled task and, if you delete them, they magically come back. This includes things like Adobe updates. I run a very "skinny" version of Win 10 (64 bit) and it seems very stable.

ASIO4all is a software ASIO simulator. It is NOT a genuine ASIO driver.

[quote author=beej6 link=topic=5612.msg19805#msg19805 date=1550969640]
Audio Processor > Final > Final Clip Drive. This amateur's advice is to write down the default setting for whichever preset you are modifying; as you might expect, each preset is set at a particular Clip Drive level.
[/quote]

Have you noticed that the text changes colour if you move any settings from the default? Certainly write down any settings yoyu are experimenting with, but, if you are not sure where you started, move the slider and you will see the text will go back to white when it hits the original setting.

The .amx files can be imported/exported to/from BA1 using the built in option, but I suspect that there is an add-in program which lets the various parameters be tweaked and that is only in the possession of people like Leif, Jesse G etc. We mere mortals don't get to play in that sand pit.

Sure, you can edit the file in notepad, and tweak some of the settings, but to add or subtract a whole lot of band settings would not be for the faint hearted.

I don't use BAE, but its "big brother", Breakaway One. However, the principal is the same. Both use Automatic Gain Control (AGC) to pull up the quieter levels to a pre-set point. It follows that the AGC can work in reverse – pushing DOWN the levels where they exceed the pre-set point. In BA1, you can tweak the head room upwards or downwards so that the AGC will not clamp until later. I assume that you can do the same in BAE.

Alternatively, switch to a preset which is more tolerant of the higher dynamics.

Without getting too technical (because I don't have the terminology), it is all about the "frame rate" or the number of complete frames that fit into the allocated area. Obviously, the larger the buffer, the more frames can fit, so the jitter percentage drops. However, it takes longer to refresh the buffer, so the latency rises. So it's a compromise between low jitter and low latency.

Bottom line – if you can't hear artefacts of any sort, a higher jitter rate is not a bad thing unless you are playing music videos where the lip synch will drift from the audio. If you are synching with video, you should aim for the lowest jitter rate, or adjust the video delay (if an option) so the audio and video are synchronised.