Forum Replies Created
-
Posts
-
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).
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!
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!
@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 🙂
There's algoriths such as (Fast) Fourier Transformation which can help you with that. You give it some waveform signal on the input (a few milliseconds for example) and it gives you a list of frequencies/amplitude in return. You can then read and change the amplitude of those frequencies, then do the reverse transformation to get some waveform signal back and you have your equalizer 🙂
Note: The more data you feed your FFT, the more precise your equalizer gets (you get more detailed frequency ranges) but the more latency you have of course. FFT simply reads a list of levels for each period of time, and it outputs a list of amplitudes of each frequency. You then don't work with time (as a waveform does) but with frequency (as a RTA does).
[quote author=JesseG link=topic=5467.msg19296#msg19296 date=1504122846]
Noted. I'll pass it (possible BaOne sleep issue) on to Leif after I confirm it with some testing here.
[/quote]That reminds me of something…
[quote author=Leif link=topic=1010.msg7044#msg7044 date=1270848582]
The long-standing standby/hibernation crash bug is FIXED. When you hibernate your computer, Breakaway Live now gracefully shuts down the audio engine, and comes back when you turn your computer back on. Breakaway Live is finally viable on both the desktops and notebooks of audio professionals!
[/quote]Tested Breakaway Live in Windows 10 Insider Preview, build 16251 x86 (prerelease of Fall Creators Update) and… it works again. *sigh* I don't know if I'm ready to install Insider Preview on my laptop though 🙂 Well, I bought BAE while waiting foir the official update, it'll do the job.
It's a laptop, so if I don't use deep sleep, my battery won't last very long 🙂 And BAL didn't have a single problem with that, so I'd rather keep using BAL ^^ (if I could anyway).
Hi Jesse,
I already transfered my license to BreakawayOne, but I still prefer using BAL because of its toolbar, and also BreakawayOne (App mode) crashes when the PC goes into deep sleep, so I have to restart it everytime. And if I don't use it in App mode, I don't get the keyboard volume control, which is also annoying.
I still wanna use BAL on my computer, it worked fine on Windows 1607, doesn't work anymore on 1703. I'm even willing to pay a little extra (like $15) to get an updated version of BAL, or even have a version without the protection (I highly doubt on this one but if you don't ask… :)).
Yann
