Forum Replies Created
-
Posts
-
I’ve not played with this at all, but, if you have two virtual cables defined and set one up as the input to BAE and the other as the output, you might then be able to configure Audials to “listen” to VAC2.
The other possibility is that you are using “KS” (Kernel Streaming) as the input and output. This is a very low level layer in the audio processing, and Audials may not listen at that level. Try changing the output of BAE to “WAV” or even “DS”. Audials may “see” the output at this higher layer.
It’s available directly from their website. https://www.claessonedwards.com/download/
I’ve been running 22H2 since 28th September and have not had a problem with BAE. It seems to be driver related, with some PCs failing and others sailing on unimpeded.
I’ve raised it with Leif. He may get back to me and ask you to provide more information on your particular environment.
Mark, I have been thinking about this issue. BA1 has no input option for either RDS or MPX. They are both generated internally (within the program, using shared code), so there is no way that they can “drift”.
I’m not sure how you are measuring, or even if the measurements can be verified, but I suspect that it may either be a matter of interpretation of the test data presented, or the testing method is flawed.
My role is to try to resolve problems presented here on the forum, so that the subject matter can be shared and viewed by others who may have the same or similar issues. It is also to try and protect Leif from direct contact as much as possible, so that he can get on with his development work.
You are very lucky to have received direct communication from Leif, so there is really not much more that I can add, as he is far more experienced than I am.
Perhaps, after you have resolved the issue, you can share with us all, so that someone else may resolve a similar problem.
Sorry to hear of your woes. Similar to another post in this forum, I get very suspicious when something which has been working flawlessly suddenly behaves badly with a change of hardware or OS.
Is the new hardware on the same OS level as the old? Windows 10 or 11? How similar is the configuration – Motherboard, sound card, RAM?
When you say that the old machine “blew up”, are any of the components salvageable? Could you swap the old hard drive/configuration back in? Is the sound card serviceable?
I’d like to see some settings images and oscilloscope patterns.
@lumper5x. If this really is a problem on the “latest and greatest” version, it may take some time to track down. It may be a driver specific to your particular environment, or it may be widespread.
Either way, the short time solution would be to roll back the latest and greatest to a stable platform, and wait until we can re-produce the error, and then work on a fix.
The AAC Plus zip file (link available elsewhere on the forum) contains three files – enc_aacplus.dll, enc_aacplus.dll and nscrt.dll and these should all be copied to the BA1 installation folder (typically “C:\Program Files\BreakawayOne”). You should then close and re-open BA1 for the list to update. If you are running BA1 as a service, you will need to shut that down and re-start it for the list to update.
Sadly, Keith passed some time ago, but his son, John is taking care of business. The correct email address should be support@claessonedwards.com. I raised this matter with John privately and he tells me that the new codes have been passed to you now.
Glad you got things going again, although a very drastic method which shouldn’t have been necessary.
You only use the pipeline as an intermediate step if your playout software normally goes directly to a sound device. BAE needs to be “sandwiched” between the player and the output device so that the presets and tweaking can be applied to the audio before it is passed to the output device. So the process becomes Playout SW > Pipeline > BAE > Sound device.
If your software allows it’s output to be seen as an input device to BAE, then you don’t need the pipeline.
I have exactly the same setup as you on my home system, except I use the “internal” stream option instead of Icecast. I can have the HD core playinf straight out of my home system, but, down in my workshop half a kilometre away, I can listen to the stream over my network.
You can only select different presets in the HD core > Audio Processing section, but the preset you select should automatically be heard in the stream (slightly delayed due to buffering). I say this without actually being able to try the Icecast option, but I am certain it would behave exactly the same way.
I also find lots of screen prints are useful. Open your core, common, audio, preset, Stream etc pages and press Ctrl + PrtSc and then save the images in a document, and then back up that document with your configuration file.
Are you using the Breakaway pipeline at all? If so, do you have the latest version for Windows 11 which is 4.31. The fact that you are getting this message “Error opening Breakaway Pipeline for test tone output!”, suggests to me that there is a mis-match.
The other possibility, seing as it has suddenly started after many years, is that a recent W11 update has clobbered something. Usually uninstalling and reinstalling BAE gets around this problem, but it might be something new that you have stumbled across. Check your Windows Update History to see if there is something that was installed at the same time as the fault developed.
