Forum Replies Created
-
Posts
-
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.
Awesome! I noticed that the streaming encoders now have the sample rate option, and it defaults to Optimum. I went through and changed all my audio settings to 48000 from 44100 and when my streaming restarted, it was still streaming at 44100. Unless the point is that 44100 is “optimum” regardless (unless as mentioned the bitrates are above 256kb/s). I would have thought that optimum would adjust to match what the rest of the audio system is set to as well, but that isn’t the case. Otherwise, it’s just great to have some updates and see some action with BaOne! Thanks all!
All good, I appreciate it! It doesn’t do Metadata. I was fiddling with it, though. And it worked otherwise. Thanks!
