- This topic has 22 replies, 8 voices, and was last updated 1 year, 6 months ago by
.
-
Posts
-
I am pleased to be able to announce that there is a new release of Breakaway One available from their website (https://www.claessonedwards.com/downloads/BreakawayOne_installer_3.30.93.exe
)Please provide any feedback via this forum.
Version Update History: Version 3.30.93 – 24th February,2023
General Improvements:
• Startup crash on some systems fixed
• Input 2 level trim added
• Monitor out separate Mute button added
• Diversity delay now adjustable down to one sample
• ReadMetadata watchdog grace periods extended to 10 minutesBreakawayOne Config:
• WDM device buffer count can now be adjusted
• Adaptive Sample Rate Conversion toggle switch added for each WDM device in config (was previously always on)FM:
• FM MPX: Range-limited pilot level control added – 8.75 to 9.25%
• FM BS-412 custom preset loading bug fixed
• New Combo FM MPX test tone added. Combines quick sweep with 50 Hz square wave, for easy, at-a-glance transmitter calibration.
• Combo Phase also added, inverts phase every second, to verify DAC, transmitter and modulation monitor LF performance.
• RDS CT flag disabled, was not supposed to be on as the PC clock is not necessarily synchronized to anythingStream Receiver
• Gain range increased, now -24 to +24
• Stream receiver bug fixed – could skip when first receiving a stream from a server with long burst-on-connectStreaming Encoders:
• https:// URLs supported as metadata source
• Connection duration display added
• Downtime duration display added (can be reset by double-clicking)
• Number of encoders increased to 6 (mgmt package req’d)
• Output Sample Rate now selectable
• MP3 encoder output now 48 kHz if bit rate is 256 kbps or above and main processing is at 48 kHzGUI improvements:
• Core / Instance buttons now revert to droplists before they get too small,
• Core / Instance button tool tips implemented
• maximize=xx command line option added (see BaRemote.txt)
• BaRemote again works under WINE
• BaRemote front panel mode custom size and position supported
• Input meter (ITU-1770) numerical readout implementedManagement Package improvements:
• MQTT support (Homie v3.0.1 compliant) to allow for advanced automation and scripting. (mgmt package req’d)
• Freeze Watchdog timeouts and grace periods extended to account for internet connectivity issues
• BaRemote RTA display low frequency delay significantly reduced
• File recorder added (mgmt package req’d)Livewire:
• AES67 address display mode selection addedPass-Through Core:
• PT core primary stream receiver now has preset buttonsAwesome! 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!
Are you using HE-AAC or AAC? HE-AAC is optimised for low bitrates (up to 160 kbps), so I’m not even sure that 48 kHz is relevant.
If you are using AAC, why not just select 48 kHz from the drop-down box?
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)
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.
Yes, I see your point. I’ll ask the question and get back to you.
My guess is that 48K is probably only possible/allowed at the higher bitrates, so 44.1K is the best you can get i.e. the “Optimum” sample rate. Wiki tells me that AAC can handle sample rates to 96kHz, so I need to research further.
@timmywa I have a response which explains why the sample rate “optimised” at 44.1 kHz
From Leif,
“Codecs tend to have more artifacts at 48 than at 44.1, but once the bit rate is high enough, it becomes a non-issue.
For AAC-LC i set that cutoff point at 160kbps. Anything over that, I pass through the audio engine sample rate to the encoder without conversion, meaning 48 kHz in = 48 kHz out.The sample rate converter in BreakawayOne is very, very good — miles ahead of what you find under the hood in Windows. Frequency-sweep artifacts are like 90dB down in the FFT analyzer. So, in short, I wouldn’t worry about it. ”
Is there any way you could up the bit rate past 160 kbps? Alternatively, just select 48 from the selections, rather than leave it at “Optimised”, which will actually down-convert.
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)
@Mwyann
Is this a Breakaway Audio Enhancer 1.44 problem? If so, I’ll move it over there. Please provide some additional information. I assume that you are trying to install BAE 1.44 on an XP PC?On the point of this forum layout, I am not the webmaster, but I have brought it to their attention.
@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”
Ah, sorry, your reference to BAE 1.40+ threw me.
I wasn’t even aware that Breakaway One would run on a 32 bit device as I thought that it was developed exclusively for a 64 bit environment. Certainly, since I have been using it, I have always installed on 64 bit machines.
I’ve referred it on to see if it can be downward compatible. It might just be a compiler switch which Leif needs to use when he does a new build.
@Mwyann
Sadly, the news isn’t good. Leif has confirmed that the latest development tools and other libraries used to develop the BA1 3.30.93 version increasingly depend on operating system functions that didn’t exist 21 years ago.Your only options are to upgrade your OS, or stay on the version of Breakaway One that you are on. Reference to XP compatibility will be removed from the Website.
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).
- You must be logged in to reply to this topic.