Forum Replies Created
-
Posts
-
You’ll need to read up on how to get an SSL cert added to your server. There should be plenty of documentation out there.. Are you using IceCast or ShoutCast?
Usually the stream provider/host will offer SSL as an option to add to your streams. Shouldn’t be a big issue. I don’t think you’re hosting your own streams, so you would only need to update the encoder to send the stream to the new https url they provide to you. You would then need to update all your stream links on all the listing services. Ultimately, it’s on your stream host to get that setup for you.
I assume Windows 10 and 11 are similar enough that they would just update the verbiage as opposed to some software update. I may be wrong, but 10 and 11 are quite similar. Also, 10 will not die on that date, just will be no longer supported/updated. Again, I don’t mean to speak for Leif and team when it comes to this, but this is my take on it.
I’m fiddling some more.. I’m finding that the long cache/delay of my stream host was keeping me from seeing the new stream right away. In other words, I was being impatient. I was wrong. It does appear to be working… i’ll keep an eye on things… Thanks again.
I appreciate your help! Yes, everything on my system from the automation output, to the outboard processing I’m testing (Chameleon C6s) into BaO is all 48000 Hz. When i selected the stream settings for the encoders to 48000 Hz, and hit connect, it connected and was streaming, but the players (several) all reported 44100 Hz. I have used other streaming tools, like altacast, BUTT, etc, and they all allowed 48000. So it’s not a limitation of my streaming host/provider. I’ve taken a screenshot of all the audio settings I could show on one screen. I switched it back to optimum now as I gave up on tweaking with a “production” stream that I don’t want down for long. It’s not a huge deal, but for some reason, if I want/need to go to 48000, I should be able to?
Here’s that screenshot: https://drive.google.com/file/d/1MC514wFhryKjIoGNyIlYiQRtpTeQgTUD/view?usp=sharing
Aside from the fact it shouldn’t be the case, any reason you are against upgrading to the latest release? Likely some Windows Update changed something and caused the instability. My first thought would be to get the latest release (came out a few months ago) and work from there. New release is posted here: https://ceaforum.net/?topic=breakaway-one-3-30-93-released
Thank you @milky!
I double checked all that. The files are all in their default locations. It’s just odd that the encoder dlls don’t load on a fresh boot and require a restart of the app to be there.. Again, to be clear, i don’t reboot it again. just an app close and restart.
I noticed the new version doesn’t always “see” the added encoders and when my LC-AAC and HE-AAC streams try to start after a reboot, they fail because they’re not showing in the encoder drop-down. I have to close the app and re-launch it, then it sees them and starts my streams just fine. Any thoughts on this?
Yeah, but 64 bit VSTs are so much more stable and from what I’ve heard from developers, much easier to code and work with various hosts. I don’t know of any 16 bit vst plugins… Thanks for chatting with Leif!
I would request for Leif to consider upgrading or offering in addition, 64-bit VST hosts. 32-bit VST is mostly terrible and standards are not a thing. Offering 64-bit hosts would move BreakawayOne into the modern world of software.
I can’t answer all your questions, but #1, the big difference is BA1 is a 5 band processor where Omnia.9 is 7 bands. Also there are many other added features and technologes in the 9 vs BA1, like Undo and more advanced clippers, etc…
Hey Milky, do you get any sense as to whether there will be further iterations/updates based on any comments here? Or is this kinda “the update” we’ve all been waiting for? I’m not complaining because this is wonderful, of course!
I have two streams, a 64kb/s he-aac and a 128kb/s lc-aac. I was attempting to get all my audio path to 48000Hz/24-bit. But I was pointing out that “optimum” wasn’t following the rest of the path and stayed instead at 44100Hz. Again, not a huge deal, but I was trying to learn the meaning of “optimum” in this instance. If it is truly optimal to stream at 44,100Hz, then that’s fine with me… But if “optimum” is supposed to be “smart” and chose the best setting based on the internal audio settings, then it’s not working correctly. I hope that clears up my above comment.
