- This topic has 40 replies, 12 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
I was thinking something similar too, because Audio Repeater is handy, but could be done better.
I believe the glitches happen because it doesn’t have Adaptive SRC, something Leif knows much about 🙂
quote :I believe the glitches happen because it doesn’t have Adaptive SRC100% correct. If there’s nothing to pick up the slack, there will be regular glitches. Problems don’t fix themselves 🙂.
///Leif
[quote author=”JesseG”]I find myself sometimes having to use "Audio Repeater" of VAC … and the audio repeater never remembers settings[/quote]
Hi Jesse-
You can get the repeater to start-up with a given set up parameters by specifying them on the command line. I use batch files to switch cables all the time.The parameters to feed to the repeater look something like this:
code :Start "VAC Cable 1" "C:Virtual Audio Cableaudiorepeater.exe" /Input:"Virtual Cable 1" /Output:"M-Audio Delta 1010LT Multi" /autostartThe "Start" aspects just lets the file start without waiting for completion before closing the batch command window, otherwise it will hang there.
If you set this up in a batch along with the RTA, you could start up both the repeater and the RTA in one go 🙂
Yea, me nether. Thanks. 🙂
About the odd shapes thingy for one "meter type" at a time… well two options, you can limit the ratios to the overall gui size… OR…
well for the RTA, knowing some of your gui code personally… it’s pretty easy to make that go vertical.
the scope is a whole other thing though. I guess you could rotate everything before it’s blit, but I know the Leif better than that… and you would want to do a more "proper" reworking to allow for vertical scopes.
you would still want to limit the minimum sizes a bit though, but the ratio should be in the eye of the beholder if there’s only one thing on the screen, unless it’s causing a technical problem. other than that, the auto-vertical code is the only thing there which doesn’t seem like it would be a problem. if someone wants a perfect square and can deal with 2-3 pixels in the "wrong" direction to get the orientation they want, i think they can compromise. 😉
I decided to give the RTA a try to rig the meters to the output of BA Live just to quantify how loud my settings are (since Leif wouldn’t put the ITU meter into the output of BA 😥 ). I seem to be getting in the area of -9 to -8 dB with Plutonium. I’ve never really seen reference to what is considered loud in that standard, but I imagine it’s up there.
Anyway, nice app! I like it!
quote :since Leif wouldn’t put the ITU meter into the output of BAGood thing I released a free one then 😛.
-8 to -9 is VERY loud. I´d say it’s too loud for Breakaway Live (probably causes listener fatigue quickly), although BBP should be able to do it pretty cleanly.
///Leif
[quote author=”Leif”]-8 to -9 is VERY loud. I´d say it’s too loud for Breakaway Live (probably causes listener fatigue quickly), although BBP should be able to do it pretty cleanly.
///Leif[/quote]
I find it plays cleanly and like it that way for low to medium volume background music but when played loud it is a bit overpowering. Unfortunately my P4 2.4 GHz PC is unable to cope with Broadcast without major droputs so I don’t play with it much 😡.
Stuart
quote :Unfortunately my P4 2.4 GHz PC is unable to cope with Broadcast without major droputsReally, even in cpu-optimized mode?
///Leif
[quote author=”Leif”]
quote :Unfortunately my P4 2.4 GHz PC is unable to cope with Broadcast without major droputsReally, even in cpu-optimized mode?
///Leif[/quote]
Nope. I guess there are just too many other processes going on that the bursts to 100% CPU util. ruin the sound quality. BBP alone uses around 60-70% in CPU-optimized mode. Maybe if I killed every other process it would work, but that’s not too practical.
Amazing what a modern processor will do though. My HTPC with 2.6 Ghz quad only needs about 16% in performance mode.
Yeah, it’s amazing how useless a clock-speed is to measure the computing power of a CPU. Even just within the P4 line… if you clocked a new P4 at 500mHz and compared it to the first 500mHz P4, some people might be in for a surprise. 😉
New version – 0.62
New feature: Adjustable RTA target level! This should make it a lot easier to calibrate two speakers separately and still end up at the same relative gain. 🙂
///Leif
[quote author=”celar”]Many thanks!
"Two speakers"… dude, this feature is even helpful in calibrating one speaker.[/quote]
Good point 🙂.
[quote author=”Boki”]is possible to add peek hold for RTA and maybe time adjust for peek hold?
btw.. great tool[/quote]
Thank you!
Well.. The algorithm is inherently insensitive to peaks due to the sharp filtering. It takes a while for levels to register. What would you actually use the peak-hold for?
///Leif
- The forum ‘Breakaway Professional Products – [discontinued]’ is closed to new topics and replies.