- This topic has 22 replies, 4 voices, and was last updated 3 years, 9 months ago by
.
-
Posts
-
I was hearing rumblings of a new version of Pipeline coming out due to some recent Windows updates causing issues with audio drivers. I thought I also heard something about a new release of BaOne coming soon as well… Anyone here have some info on any of these rumors?
In a recent emal from Leif, he indicated that he was working on the changes necessary to incorporate the new VAC, and “other things”. However, he gave no delivery time commitment, so all I can say is that something is in the pipeline (bad pun).
I shall seek further clarification.
I have news!
Leif has developed an update to BAE which incorporates the new VAC release and it is in beta testing currently. He hasn’t ported the changes to BA1 yet, but progress has been made.I’ll let you know when the new release is official, and would expect BA1 to follow soon afterwards.
Oh rad! Can we speculate about what it might contain?
Hopefully an improved tray icon that shows when the app is disabled, or offers a simple way to disable by right click or something.
Possibly the improvements to the bass clipper that some Omnia products received.
Perhaps some new or updated presets?
Also, when suggesting BAE to friends, their most common complaint is that it doesn’t support multiple outs. I try to then direct them to BA1, but they assume they’ll get sick of the nag/reminder every few hours. If they could leave their headsets plugged in and get sound from their speakers at the same time using just BAE, I think they would be more likely to buy a license.
Just a thought that crossed my mind after posting, and I seem to be unable to edit.
But really, any updates to either app would be appreciated. Folks like them, even when nothing is technically busted.
edit test: Okay. somehow I’m able to edit this one, whereas in my last post, the button disappeared after I clicked it.
Getting an extra Speaker out for the Pass-Through license would also be excellent, and I’d buy one to have extra outs for sure, even though the native version of BA1 supports Common + asio in addition to the cores.
Sorry to prick your Bubble of Hope, MrK, but Leif focussed on resolving the VAC compatibility issue quickly, so there are no major updates in this rushed out release. The same will be for BA1 initially.
Perhaps we should start a thread as a “wish list”?
Fair enough. Yes, that’s probably a good idea. I’ll let you do the honors of creating it though, so you can outline what’s reasonable to wish for (ie fixes/QOL improvements as opposed to new features, etc) in the opening post.
@Milky, I was wondering if there’s any way to be a part of the beta testing somehow? I’m also having trouble with my sound on Windows 10 and BA1, I don’t know if it’s related to the same issue or if it’s something else but it would same me some time in testing things if the answer is already there 🙂
You can ask to access the beta by emailing Milky, as suggested in this thread: https://ceaforum.net/?topic=breakaway-audio-enhancer-update-v1-41-0
This only fixes the Breakaway Pipeline incompatibility for Windows 10 version 20H2. If you are not on 20H2, then you will not need to test the beta.
Yes, I saw that post a few moments ago, so I did write to him. And indeed, I’m using 20H2 (Windows Insider beta even) so that applies to me 😉 Thanks for the heads up!
There has been a new BETA release of BAE – version 1.42.0, which addresses a couple of minor bugs picked up by the testers. There is also a minor update to VAC 4.31 which is now correctly signed. Here’s the link to a dropbox.
- https://www.dropbox.com/sh/lkxar5d2wfcsonk/AAAhHJniGGmNffmzBSNvpXFAa?dl=0
Download ONLY version 1.42.0 and VAC 4.31. If you do not uninstall your previous version of VAC, the BAE installer will place a removal tool on your desktop, and you should run this first. The BAE installer will set up and configure VAC as well.
For those of you also running BA1, I have not received the updated version of it yet, but it appears in my testing that VAC 4.31 works well with it. However, the current production version of the BA1 installer will see VAC 4.31 as “foreign” and try to uninstall it, so you should uninstall VAC and install 4.31 independently of the BA1 installer.
Well, I just gave it a go, and I must admit it works fine, but for me there’s some regressions compared to the 4.15c version. I guess it’s not entirely the fault of BP/VAC as I’ll explain further, but it’s enough for me to stick with the previous version.
One weird issue I’m having with BP 4.31/VAC 4.64 compared to BP 4.15c is the jitter performance I get on Kernel Streaming. With the previous version, I can easily set my BP input/output to 48 kHz 128 block, and I get a jitter value of around 30-40%. This leads me to a latency of 0.09 seconds. But with the new version, the minimum buffer I can set is 240, with jitter as high as 60-70%, and a latency of 0.14 sec. The “Wave” method is even worse, I have to set a block size like 1700 or more for it to work. So that’s the first issue I have, with both BP 4.31 and VAC 4.64 (latest). Difference in performance, in the wrong way.
The second issue, I guess is because I’m using Voicemeeter Potato to route my audio on my computer. And with both BP 4.31 and VAC 4.64 again, I can’t use the virtual audio cables with Kernel Streaming inside Voicemeeter! That leads to two problems: I have a slightly higher latency because I have to switch to WDM or MME, and the biggest problem is that the audio stops if I switch Windows accounts (it still works if I use KS). But I guess these problems are more about Voicemeeter itself, and I’m currently contacting the author to see with him what is it about.
So for me right now, because of these issues, 4.15c is still my preferred version. I also downgraded BAE of course, because it won’t work if I don’t. BTW, when you upgrade BAE, all the settings (including your preset selections) are lost, and the only way to recover them is to downgrade. Don’t forget to keep a note of them when you’re about to install the new version!
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).
- You must be logged in to reply to this topic.