Forum Replies Created
-
Posts
-
I am unsure of the definitive answer to this without setting up some scenarios and viewing the results on an oscilloscope. However, I always align windows, Pipeline and BAE settings to the same value. I have heard some systems where music recorded at 48k played slower when down-converted to 44.1k
Having said that, I believe that the Windows settings are ignored if you select “KS”, because that is a lower level layer than the Windows options.
There is a neutral preset in ‘Reference Settings’. It just provides a constant output level, with very little colouration of the source material.
When using your USB device, you probably need to change the input of BAE to pipeline 1,and the output as the USB device.
Good research!
When you say that it uses twice the CPU and RAM, what does that take it to? My experience is that CPU and RAM usage that is around 50% and occasionally transients to 75% still leaves enough headroom provided that the PC is adequately cooled.As you probably know, the whole point of the LL path was intended for radio presenters to be able to hear their own foldback, without there being a delay. It is very confusing if you are hearing your voice 1 second delayed because of processing delays.
I think that you just have to let your ears decide if it works for you or not. Obviously, it won’t work with all types of music, but may bring out some percussion characteristics in some genres.
These are probably questions best aske of John Edwards
I assume you know that the streaming option shares the same preset as the core it is attached to? For instance, if you have an HD core and you run Plutonium preset, then the stream from that core will be Plutonium.
I have found this information in the soon-to-be-released operating manual. I hope this helps explain the various options.
https://ceaforum.net/wp-content/uploads/2023/03/Breakaway-Documentation.pdf
I am seeking the definitive answer, and will get back to you. They are not things that I personally use.
If any other members has some knowledge of these effects, please contribute.
Yes, Breakaway Audio Enhancer is compatible with Windows 11 and the new release dramatically improves the screen readability with hi-res screens. If you need the Breakaway Pipeline program as a bridge between your playout software and BAE, make sure that you download that also from the same link below.
It IS, however, still a 32 bit application, having been developed originally back in the day of Windows XP. It will run perfectly, even on a 64 bit device, but is slated for a significant re-write, where it will be 32/64 bit capable.
You can download and purchase from https://www.claessonedwards.com/download/
@KIX
If it wasn’t in the release notes, it didn’t happen. However, as I said to timmywa, the requests were all passed on and will be considered for subsequent versions.@timmywa
EVERY request that was raised here was passed on and collated into a spreadsheet. Then the gurus went through and filtered/prioritised them all, so they may appear in a subsequent update if they made the cut. Priorities were set based on “urgency”, but also on the complexity of coding to achieve them.This release was from a backlog of earlier requests, but also included some recent requests because they were easy to incorporate along the same development path.
There is an article at this link which discusses BAE setup https://ceaforum.net/?topic=fine-tuning-breakaway-audio-enhancer-all-about-interfaces-buffers-and-rates
Basically, you need to aim for the smallest buffers, so providing for anything larger than a multiple of the sample rate would be useless.
Jitter is only an issue if it produces audible artefacts. If you can’t hear it, it isn’t a problem.
@Mwyann
Sadly, the news isn’t good. Leif has confirmed that the latest development tools and other libraries used to develop the BA1 3.30.93 version increasingly depend on operating system functions that didn’t exist 21 years ago.Your only options are to upgrade your OS, or stay on the version of Breakaway One that you are on. Reference to XP compatibility will be removed from the Website.
The settings in the pipeline only restrict/allow the minimum/maximum range that it will allow through to the input of BAE.
Typically, it should be set to 44100 – 48000 because the BAE config program only allows for those two frequencies in the “Rate” drop-down box.Not sure if this will work the way you want it to. The point was that, originally, the pipeline was part of the installer, but, as many people downloaded and installed later versions of the Virtual Audio Cables program than that which was bundled with BAE, complications arose.
Now, VAC is not automatically installed, but a link is provided pointing to the latest version available from the Breakaway website. You can optionally use the one already on your system, or you can remove that and update to the latest, separate from the BAE install.
Therefore, theoretically, you could use a different device. Provided that BAE sees it as an input/output device, you could use it.
Ah, sorry, your reference to BAE 1.40+ threw me.
I wasn’t even aware that Breakaway One would run on a 32 bit device as I thought that it was developed exclusively for a 64 bit environment. Certainly, since I have been using it, I have always installed on 64 bit machines.
I’ve referred it on to see if it can be downward compatible. It might just be a compiler switch which Leif needs to use when he does a new build.
