- This topic has 7 replies, 4 voices, and was last updated 2 years, 3 months ago by
.
-
Posts
-
I have been using BAE in the last 6 years and it is an awesome piece of software. However, I recently run into problems.
I am currently on Windows 11 (most up to date), with BAE 1.42, everything has been fine until yesterday, BAE just suddenly doesn’t produce any sound. I re-run the simple 3 step wizard, but can’t get passed step 2 as I get “Error opening Breakaway Pipeline for test tone output!” (buffer size doesn’t matter), and I make sure to choose the correct Realtek Digital Output in step 1.
After messing in expert mode with Input as Breakaway Pipeline 1 (KS interface) and Output as my Realtek Digital Output Audio, Testing via test mode also produce “Unable to open ‘Breakaway Pipeline 1’ for input at 480000 hz, 2 channels, 16 bits. Device does not support requested format, or sound device is busy”. I try to change the format in Realtek Digital Output, but it doesn’t matter, same error. Closing and restart BAE gives the same error.
Nothing is wrong with Realtek Digital Output, as I get the sound from it just fine. Device Manager doesn’t return any error with BAE installed.
I have reinstalled BAE multiple times, reinstalled Realtek driver, tried 1.41 version. Nothing works so far. How can I resolve this issue as I can’t use the software anymore?
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.
Thank you for the reply,
By default, I have never had Breakaway Pipeline installed separately (do I need it at all?). Anyway, I took time and re-installed a fresh copy of Windows 11, made sure it was up to date, and then re-installed BAE. It is working again, but such a hassle since uninstalling and reinstalling BAE didn’t solve the issue. It could be that the Windows 11 updates corrupted something.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 had the same problem with Windows 10 yesterday when I opened BAE (configured to not autostart). After an update 2 days ago (computer off for a week or so) BAE was a non-starter. Had to uninstall. Also uninstalled my audio card driver (shotgun technique maybe to aggressive to figure out the real cause). Here the dangerous part and I’ll get yelled at… Used CCleaner (older style interface “virus free” version 6.00.9727) to clean the registry after uninstall and reboot (to unload any BAE/Audio card drivers). Been doing this for years and can’t say I’ve ever had CCleaner break anything that was installed properly. Actually never remember anything being broken by CCleaner (yet). CCleaner removed pointers to things not installed (could see audio related stuff being cleaned up) and then after a second reboot I reinstalled audio driver and (after required install reboot) made sure the audio card was working correctly and installed BAE v1.42.00. All’s back to functionality. Here’s what I see though when I check the version of the Pipeline.
Driver Provider: Eugene Muzychenko
Driver Date: 9/13/2020
Driver Version: 4.64.0.11318I did not notice if the driver was uninstalled upon the uninstall of the broken BAE so I was wondering if somehow there was a background update to the Pipeline since it’s not version 4.31 as Milky stated above.
OMG… Another note: ASIO4ALL seemed to get messed up also so maybe there was a root change in the audio structure for Windows. I have another machine that I’m blocking Windows update so I’ll possibly get another chance to check this out.
[code]Driver Provider: Eugene Muzychenko
Driver Date: 9/13/2020
Driver Version: 4.64.0.11318I did not notice if the driver was uninstalled upon the uninstall of the broken BAE so I was wondering if somehow there was a background update to the Pipeline since it’s not version 4.31 as Milky stated above.[/code]
If I recall correctly, there was a windows 10 update a couple of years ago that broke Ray’s Virtual Audio Cable, on which BreakawayPipeline is based. The Pipeline version included in 1.42 is the updated version (which I believe is 4.64 of VAC). I think since they’re not technically the same product, Pipeline and VAC will be using different version numbers, but I don’t know.
All I know is I currently use BA1 with the official VAC and haven’t had this issue yet. I’ll play around with BAE and see if I can’t replicate this issue.
- You must be logged in to reply to this topic.