Forum Replies Created
-
Posts
-
Nah it’s local only, there’s no firewall between BA1 and my broker, I think BA1 simply can’t talk SSL which is fine. I tend to use SSL whenever I can if available but since it’s on my local network it’s fine I guess 😉
I gave BA1 a try again with HA discovery and it works fine now, I don’t know why I couldn’t see it before.
That way I was able to export the Speaker Preset Name so I can automatically adjust the preset depending on the current time, using the Selector action instead of calling the API via HTTP, which is cleaner.
I can’t connect to the SSL version of the broker though, I’m stuck with “normal broker”, which I guess is normal.
I got HomeAssistant to set my speaker preset by using REST plugin. I’ve included this to my configuration.yaml file and I can then use it in scripts or automations:
rest_command: baone_bore_speaker_normal: url: "http etc" method: GET baone_bore_speaker_low_bass: url: "http etc" method: GETMaybe you can use that instead of your batch file and have Google Assistant to switch it back and forth for you 😉
One way I would use that for example is to change my speaker preset automatically for the evening – using a lower bass preset for the neighbors 😉 I know I can already do that via HTTP but if I can do it via my Home Assistant installation that would be even better. But I don’t think I can right now, it doesn’t support changing presets yet I guess.
I’m using the Keyboard Volume Control in the “Common – Monitor Output – Main” controls. It allows the volume of the common output to be set using the volume keys on your keyboard. It doesn’t work on service mode because the service doesn’t have access to the keyboard (it’s not running in a user session).
Another workaround could be to write an app that would take control of the volume keys and set the volume using the BA1 API, but again this is overkill. This feature already exists (I asked Leif about it because I was already using it on BA Live btw), so I’d like to make use of it, now that I’ve got a nice keyboard with volume keys again 😉
Hi Milky, and thank your for your answer.
No this is not what I’m looking for. When I start BreakawayOne, it opens the main window and also adds its icon in the system tray. I can close the window and BA1 stays open in the system tray, but what I want is to not open the window when BA1 starts. I want it to start in the background, in the systray only immediately.
Right now I’ve set up a Batch script that does that but it’s clearly a hack and not ideal. I was wondering if there’s an option or a command line switch to make it start in the systray without opening the main window.
Well I’ve looked on the website and I think I have my answer by the paragraph:
“Separate Low Latency processing with the same settings as the main processor, so that you can use the highest-quality processing for your stream or digital on-air feed while also providing a low-latency headphone feed for the studio.”
I guess then the streaming gets the same treatment as the main processor, and if I want both streaming high quality and low latency realtime processing, I need the Separate Low Latency feature. I’ll check on that and see what I do with the upgrade. I tried it on trial mode and I see it uses double the CPU and RAM, so I don’t know if it’s worth the upgrade considering the low use-case I have for this.
Yes I know that, but latency isn’t part of the preset, it’s part of the core, hence my question. I would assume the stream will get the same quality, but I want to make sure, as I don’t think there’s an easy and convincing way to test it by myself.
Well that’s not a big deal, it’s on a test gear anyway that I run occasionally on trial mode, I wanted to upgrade it because why not but I can still use the older version, it’s good enough 🙂 Well, at least the doc will be up to date 😉 Just keep the 32 bits compatibility please, I still use it daily on a repurposed tiny client running Windows 7 Embedded, and it’s perfect for my Home Cinema setup 😉 (especially the fact that I can shut it down brutally without breaking the system).
@Milky No no, it’s BreakawayOne 3.30.93 that will refuse to start on Windows XP. BAE 1.44 doesn’t run on XP either but it’s by design, there’s even an error message when you try to run the installer, so that’s good. But BA1 should run in my opinion, at least the documentation says it will. The error message when you start BA1 on XP SP3 is: “The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll”
It looks like compatibility with Windows XP SP3 is broken right now: “The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll”. The documentation says it should be compatible, and the installer doesn’t complains on install, like BAE 1.40+ does.
(Oh and off-topic, but Milky, please fix the forum: reduce the banner height, and fix the weird blank space in the homepage, between title and forum content)
Thanks for the update! Quick little thing I saw just now: “WDM device buffer count can now be adjusted” but not in Common Monitor Output 🙂
(And I think what @timmywa was saying is that the “Optimum” choice would’ve picked the best option, as the name would imply)
Sorry, I didn’t see this thread, and I have a small bug to mention.
Regarding this old problem I had: https://ceaforum.net/?topic=new-version&paged=2#post-16316
I noticed that BAE doesn’t find Breakaway Pipeline (Virtual Audio Cable) when it isn’t configured as WaveRT. I’ve got mine set to WavePCI and BAE tells me that I don’t have the Breakaway Pipeline installed, which is wrong, it’s simply not configured as it wants to. Maybe make it aware of WavePCI mode (and maybe WaveCyclic too).
