- This topic has 12 replies, 7 voices, and was last updated 8 years ago by
.
-
Posts
-
As you already know (at time of writing) Breakaway Broadcaster doesn't play well with Windows 8 or 8.1. I found this out the hard way, I needed to upgrade for other broadcast tools but at the time there was no information posted saying it did not work (now there is information saying "it doesn't work"). I couldn't afford to time to downgrade to windows 7 so I stuck with it as best I could.
The problem you will find is that BB will work initially with Windows 8, but over time BB develops a serious case of over flows and under flows (as seen in the Breakaway pipeline control panel). When this happens BB tries to catch up the audio, never makes it and the audio stream goes turns to crap and sounds like garbage. You can avoid this sort of this by restarting BB daily, but the problem can occur in 10 mins, 10 days or 30, there is real no time frame to when the audio would suddenly turn to crap. Generally I found it crapping out when there was CPU load on the server by other applications and background processes.
The problem seemed to the audio routing and the Breakaway pipeline control panel. I knew the Breakaway "pipeline technology" is actually an OEMed or license (to redistribute) of Virtual Audio Cable or something along those lines (you can read the copyright info in the app). So to get the same functionality I was about to drop BB altogether and go with Stereo tool but I still need the audio routing of BB so I purchased a new version of Virtual Audio Cable for $25. After install I noticed there are many new features in VAC over the Breakaway pipeline system, it also handles threading automatically, which seemed to be the problem (at least in my eyes). So since BB hasn't been updated in years and years and the fact I didn't want to invest $400 in Stereo Tool I though it best to give VAC a go and replace the audio routing of BB with VAC.
Bam! No more Oflows or Uflows and everything working perfectly for the last 2-3 weeks running windows 8.1.
So for an investment of $25.00 you can get it running.
Question for the engineers of BB, is there anyway to uninstall just the pipeline part of BB as it seems to be the issue.
Thank you for the reply, just out of interest do you think you might be able to make a minor update with a new version of VAC so that it might handle windows 8 better? It seems this is the problem exclusively, sometimes I get some under or over runs but VAC corrects itself within 2-3 ticks.
No buy direct from the author, latest version works very well with no buffer over or under runs:
Silver,
I tried to test the latest version of VAC, 4.13, I think. I found the jitter measurements shown in the test within Breakaway were MUCH higher than with the included Pipeline version. I had to bump the buffer size and numbers way up (highest) to get it around 10%. While, with the built-in, I was at 882 x 4 and had 0% jitter. I wonder what your buffer settings in Breakaway were to find good jitter measurements.
Run all your cables at 44.1 or 44.8 just make sure your source is always playing at the same rate.
For config:
Interface is DS, don't run KS! KS seems unstable on W8.1 for me.
Audio reality priority: off
Buffersize: Large
Optimize CPU usageWhat other settings you after?
I have the same problems with BAE, I tried to install Virtual Audio Cable and use it with BAE but it doesn't appear in the inputs on either Wave or DS. Anyone knows how I can use it instead of Breakaway Pipeline on BAE?
[quote author=lorin2015 link=topic=3844.msg18486#msg18486 date=1440445517]
I have the same problems with BAE, I tried to install Virtual Audio Cable and use it with BAE but it doesn't appear in the inputs on either Wave or DS. Anyone knows how I can use it instead of Breakaway Pipeline on BAE?
[/quote]You can't. BAE is hard coded to only work with Pipeline.
Well…..It finally happened……BBE and the pipeline had a major meltdown…….keep getting error messages about a "debugger" that needs to be removed from memory, and I gave up….no matter what I did, nothing works……W7 has its share of glitches, but this just busted my chops…….I've had it with this crap….any alternatives?
If you are running AVG anti-virus and Breakaway you may be able to fix the Debugger problem by having AVG exclude the folders containing Breakaway products. Open AVG then Options-Advanced Settings-Exceptions-Add exception-Folder-Browse to folder containing Breakaway-select folder then select the appropriate folder(s) to see if that fixes the problem. I restarted after doing this just as a preventative measure but I'm not sure that is necessary. I also pointed AVG to the installation files hoping that they will address the issue someday.
- The forum ‘Breakaway Professional Products – [discontinued]’ is closed to new topics and replies.