MrKlorox

Ok, is there a way to report posts or PM an admin? I’m not seeing how.

Are you asking how to make BreakawayOne startup with Windows in fullscreen display only mode?

Try looking for C:\Users\<USERNAME>\AppData\Local\BaRemote\BaRemote.txt to see what command line shortcut options you can use. I know for certain you'll need the Management Package at least to make it start with Windows.

Basically what you want to do is install the service so BreakawayOne runs in the background at startup. Then you would want to launch BaRemote as a startup item with the command line options you need. These seem relevant. I don't have the management package, so I just use the wheel_adjust=1 setting in my breakaway app shortcut.

• host=xx hostname (or ip)
• password=**** password (not necessary for localhost connections)
• port=xx port number (optional, defaults to 8200 if omitted)
• retry retry connection indefinitely without ever displaying retry/cancel dialog. will also reconnect after connection lost.
• retry=x retry for x seconds then display retry/cancel dialog. if connection lost, will display retry/cancel dialog.
• displays_only Starts up in "Displays Only" mode. Clicking on any display takes you back to normal mode.
• wheel_adjust=x Use mouse wheel to adjust sliders (rather than change page). x=gear ratio, for example wheel_adjust=1

This thread should give you a basic idea of how to add command line options to a shortcut: https://superuser.com/questions/29569/how-to-add-command-line-options-to-shortcut

Just about everything offered is fully functional in its demo state. You won't have to buy anything then discover it doesn't work on your system.

I don't exactly have the option to experiment on that operating system. I also don't see alternate audio interfaces in Altacast, such as Wave or ASIO. Perhaps KS is simply non functional in Server 2019? I've never run a Windows Server OS before.

I figure it's worth trying the Breakaway streaming encoder module to see if it does what you need.

[quote author=lpy7 link=topic=5963.msg20450#msg20450 date=1585159415]
I agree, things could change between now and the final version. But for anyone who relies heavily on virtual cables, it's more or less a notice to just be cautious before you jump to 2004, just in case it's still broken.[/quote]
Thank you for the heads up! I do rely heavily on multiple instances of the Breakaway Pipeline.

Hello! I'm a BAO user, but I'll try my best to help. A while back I was looking into ways to get that dolby driver on standard non-Lenovo PCs, so I have very little experience with it, but I did get it working at one point. But I don't currently have it on this machine and I'm not sure how to go about finding the modified driver and app again. From memory, it seems like a per-application auto-eq and wideband compressor. I believe this was before I found Breakaway Audio Enhancer, so I don't have any experience getting them to work together.

You mention having a Realtek driver installed, but are the traces of the Dolby driver and its effects app completely gone? I'm thinking both BAE and Dolby must be attempting to use the same buffer space or something? @JesseG is likely right though(dude knows the ins and outs of Breakaway). [EDIT: This is not to be confused with Dolby Access]

I'm worried if completely removing the default drivers doesn't help, your friend will need to buy a USB sound card/DAC/interface (this includes USB headphones). You can get a very basic one for like a fifth the price of BAE off Amazon. But like everything, for a better sounding device, you'll end up paying more. Also if the headphones are any good, you'll probably benefit from an external device regardless of whether Breakaway is being used. To do this you would want to look up the Ohm rating (impedance) of the headphones and find a device that can drive them at least that hard.

As far as your music group goes, I've also successfully recommended BAE to about a half dozen friends and none of them have had any issues with BSODs. The most common issue is Windows likes to change devices when they're plugged in; whereas BAE likes to keep its original device until it's changed in the settings. BAOne supports multiple outputs, though, and a different trial mode if you have some friends who are put off by this.

Best of luck!

edit: Or your friend could try BreakawayOne, (and then add ASIO4ALL if BAO doesn't work on its own). Regardless, I gotta go with the USB DAC suggestion, even if it does work.

Thanks Keith and Leif! So how does Processor Latency Mode affect the buffer? [Core> Misc> Processor> Latency Mode] Not talking about the separate LL module.

I notice if I set my new ASIO SPDIF interface to a buffer size of 32 at 48khz, I can only use High Quality in my HD core without noise artifacts. However a size of 64 at 48khz can work fine in Extra Low Latency, but still has audible artifacts when I choose the standard Low Latency mode. I'm guessing it's supposed to be buffer size 1x @ Extra Low Latency, 2x @ Low Latency, and 4x @ High Quality?

Still, it probably shouldn't be making any buffer related noise at standard LL, but not when on Extra LL, right?

Oof, my new ESI U24XL must be defective. It doesn't even go above 48kHz. It straight up refuses to even hold 48 and always downshifts to 44.1 without resampling. It just skips frames and sounds terrible.