Forum Replies Created
-
Posts
-
Hi Milky,
I’ve successfully installed Breakaway Pipeline 4.64 on both my Win10 64 bits and 32 bits machines, and it works just fine. Of course BAE 1.42 wouldn’t install with the newer version of Breakaway Pipeline installed (although it complains about an “older version” installed, which is wrong ;)), so I had to manually overwrite the files over, and after doing so, BAE 1.42 works fine with BP 4.64. So the BAE installer still needs to be updated too of course.
And thanks to Leif for this update too!
You can still buy a license right now, and it’ll work with the 2018 version, which is fine (you still get what you’re paying for). You can even try the software fully before buying. But I see that this update mess (no new official version for 3 years, and more recent versions available on dark sites instead) is not good for business, because people think this is abandonware and/or that the official website may not be trustworthy, considering it doesn’t seem to be up to date. I know Leif is a very busy man, but for the best of its business, he should really do something about this update version issue as soon as possible. It’s the classic Breakaway situation all over again, where he works in his software for some time, and then poof, gone for months! Very frustrating for his customers, both long time and to become.
I don’t blame you, don’t worry 🙂 I’m just surprised to see this issue not being resolved and being released as-is, despite having been raised during the beta period.
Breakaway Pipeline version 4.31 is now official, as it is now linked in the download page on claessonedwards.com, but this version is still not compatible with Win10 32 bits.
Although the older versions still works fine for me anyways, it’s weird that those beta versions are deemed good for public usage, as new customers may get in trouble trying to install those on their incompatible setup, without being able to download the older, working version (unless guided on this forum for example, but that’s not straightforward).
Eventually, you can use a VM if you don’t have a physical machine anymore, it shows the same problem.
Quick question @LTSings, are you using Windows 10 32 bits?
Any news regarding an updated version of Breakaway Pipeline which supports Windows 10 32 bits, and/or BaOne ?
Just in case, the new Breakaway Audio Enhancer version 1.42.00 is now officially released 🙂
Please, reduce the size of the banner… It’s unnecessarily huge and forces to scroll down to see any piece of information.
Oh, I was asking @Cristian 🙂
The only place I’ve found (which is highly suspicious if you ask me) is there:
(Link to illegal software deleted)Thanks for your reply, @Milky. Personally, my rule of thumb regarding jitter since Breakaway Live and still now with BA1/BAE, is to be less than 60%. This allows me to get the lowest latency and no sound defects. In fact, with a buffer size of 128 I was getting 80% of jitter, which did work but was a bit high for me. I now set it to 160, and I’ll continue checking if it still sounds OK. I know I should try to have the lowest possible jitter, but as long as the sound doesn’t suffer from it of course, I tend to prefer the lowest latency over “performance” (I have plenty of CPU time to spare).
BTW I’m using Voicemeeter to check latency: I route the input channel from Voicemeeter to both Breakaway and the output sound card, and I use a click sound to measure the actual latency (by ear or using my phone).
Well, after further testing, I solved both of the problems I was having in my first post at once, that was: bad latency and didn’t work with Voicemeeter.
The answer resides on this page: https://vac.muzychenko.net/en/manual/advanced.htm#ChooseKsProtocol
As you can see, since version 4.50, VAC implements PortCls port/miniport interfaces differently. You now have the choice between three modern interfaces: WaveCyclic, WavePci and WaveRT. In my case, in Auto, it was WaveRT that was selected. And this choice doesn’t work with Voicemeeter, and it doesn’t have a good latency.
I had to switch both “Capture port” and “Render port” for my cables to WavePci (the best latency), and it worked fine! I can use 128 blocks again, no problem. If you use Breakaway Audio Enhancer though, you have to leave the “Render port” as “Auto” or “WaveRT”, as BAE only recognizes its driver through this implementation. Other than that, I’m finally happy with my new Breakaway Pipeline driver. Still doesn’t want to install on Win10 32 bits though 🙂
After further inspection, it appears that even the Breakaway Pipeline Removal Tool doesn’t work properly on Windows 10 20H2 32 bits (which is not surprising when you think about it), it says that it is uninstalled but in fact it isn’t. So when you try to install the new version it says that it needs to uninstall the previous version first… And when you use the regular “Uninstall Breakaway Pipeline” to effectively uninstall it, then the new installer tells there was an error while installing the driver.
Also, I tried installing BP 4.30 or 4.31 on Windows 10 20H2 32 bits and it doesn’t work. 4.15c still installs, but not the recent versions. It simply says there was an error during the installation and that’s it, no other detail. Looks like it’s the driver installation itself that doesn’t work (wdmdrvmgr.exe).
