- This topic has 50 replies, 16 voices, and was last updated 5 months, 3 weeks ago by
.
-
Posts
-
Nice video! Thanks for that.
I would like to add a request for more metering. Specifically, I want to see the AGC doing its thing across its multiple bands. I also see the Omnia.9 MKII has a post-multiband and digital out scope in the video, and I would be interested in seeing the waveform at more points in the chain like this.
A note about the brushed metal skin (the heather grey with grains): it inflates PNG screenshots. There’s too much detail and one has to either recompress with jpeg or reduce the color depth to make it a reasonable file size. Would it be possible to enable a ‘simple’ option that makes it mostly a single shade of grey? Or better yet, can you allow us to pick primary and secondary colors (to change from grey and green) so we can match them with our PC theme?
I would also like to be able to modify the Outmix without having to edit a preset file (sometimes I like to reduce the limiter drive even further than the slider allows, even though it’s very clean when peaks hit it).
I would love to see a harder bass clipper on BaOne. With more agressive shaping. and highpass filtering before processing.
A -30 to +12 final limiter drive would be welcomed so people won’t have to mess with the outmix in a preset file.
Things like Clunk and Slam are hard to understand what they do. This is why I think plenty of descriptive popups or right-click info menus would be invaluable for BreakawayOne. In other software, I can “solo the difference” of the effect (aka the Delta) and identify what they do more easily, which would also be amazing.
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 discussed this with Leif once before and his reasoning was that a lot of VSTs crash and it is easier to keep 16 bit VSTs in their own memory space so that it doesn’t crash Breakaway One as well.
I’ll raise it with him again. Maybe the tides have turned since then.
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!
Heya. So I recently realized the AGC in BA1 is not necessarily multiband like the Omnia software is capable of. At least not always..? Can we get clarification on this?
I’ve been experimenting with another multiband AGC and I love how it sounds. If it’s not already capable of multiple bands, I would be interested in (and even willing to pay for) a multiband upgrade to the wideband AGC currently in the software.
If it does exist, can we get metering for each band? I realized I already asked for this last part in another comment, but I’m putting it together with this request since it doesn’t necessarily make sense on its own if the AGC is not multiband.
@MrKlorox
I will forward your query on in its entirety so it maintains context. I’ll post any response here.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?
Hmm. Sounds like a teeny bug, possibly a caching issue. I know that Breakaway One scans each time it starts, in case a new encoder has just been installed, so it is odd that you need to re-boot to force it to update.
Are the relevant exe files in the BA folder?
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.
@MrKlorox This is the answer directly from the man who made it.
“The Input AGC in the breakaway core, as used in both BreakawayOne and Omnia.9, is _not_ multiband, and never was.
The reason is quite simple — it would suck the life out of the music.
For example, Orban processors use a coupled 2-band input AGC – BASS and MASTER. The coupling means that the bass can never be boosted more than the rest, but bass _can_ be reduced more than the rest, which is the entire purpose, because in a wideband AGC, if you suddenly have lots of bass in the input, you will hear the overall audio getting much quieter due to how much energy bass has compared to the perceived loudness of said bass.
The disadvantage of doing it this way is that when you play bass heavy music, particularly of the electronic variety, all the bass gets sucked out of it right at the Input AGC stage, resulting in wimpy sound.So, the breakaway core uses an in my opinion much better compromise. I use a wideband AGC with a _sidechain filter_ to essentially _desensitize_ the Input AGC to heavy bass. This way, excessive bass goes right through the Input AGC without causing much gain reaction, making the Input AGC response much more closely to how we _perceive_ loudness. This in turn means that excessive bass will enter the Multiband AGC section (which indeed both BreakawayOne and Omnia.9 has, of course!) which is actually equipped to handle it.
I made sure my audio processors can handle deep bass for the simple reason that I like music with heavy bass, as well as a whole lot of other genres. This is not the case with every audio processing developer, and if it’s not part of your playlist when you’re designing the audio processor, chances are the processor you’re designing won’t gracefully handle it.
Anyway, the Input AGC in BreakawayOne is in fact identical to Omnia.9, with the exception that Omnia.9 lets you adjust the sidechain filter exactly. Believe me when I say that this is not a limitation – I _never_ adjust it myself, it already handles everything I throw at it (from Pat Metheny to Count Basie to Infected Mushroom), I haven’t had to touch that slider for a decade.”
@timmywa I was able to run this query past Leif in a Zoom session this week. This is a summary of his comments.
“BreakawayOne scans the global environment path for installed encoders, and populates the list with all known encoders it finds. I have never seen this fail, but the order of operations of a Windows startup is a complicated beast.
This is the reason for the Post-Boot Delay slider in the config window, under Miscellaneous. That may solve the issue.
The logic behind it sets a volatile registry key after the first time the delay is performed, so it will not slow down every BreakawayOne startup, only the first one since a reboot!”So, I would make sure that you have the relevant encoder folders included in your global variable settings. If you already have that, try adding a delay to the startup of BreakawayOne after a re-boot.
- You must be logged in to reply to this topic.