Home › Forums › BreakawayOne › Requests and BUG REPORTS for new Breakaway One beta!
- This topic has 25 replies, 13 voices, and was last updated 7 years, 4 months ago by aleph99.
-
AuthorPosts
-
December 24, 2016 at 11:32 am #3238camcloneMember
Breakaway One is just great as is and much better than the old breakaway code.
BUT , i believe next betas need some extra code inside 🙂
priorities for me :
1) stereo pilot adjust ?! ( some radiostations need higher stereo pilot because they under-modulate , usualy at 52 KHz for multipath prevention. ( instead of BS regularity they make high dbr presets for undermodulation .
2) VST reboot in case a VST plugin crashes. ( is it already active ? auto reboot of VST plugins and auto reboot of breakaway engine ?
For my opinion Leif made a great decision to create breakaway one because many people will try to make presets and these presets will make Omnia 9 preset collection much better and competitive.
It 's like , having people working for you and helping make your product better.
( just like stereotool creator Hans made, without all these people who test and give FREE FEEDBACK AND FREE BUG REPORTING ….all these features and thoughts of Hans and Leif, Leif and Hans …would not be created.I am here and i will mess every modulators up !! 🙂
heheheheh!
Have fun !
;D ;D
December 27, 2016 at 11:00 am #14721camcloneMemberfinnaly after some testings with the new code of breakawat one i can say that :
for people who want HIGH dbr PRESETS for FM BROADCAST they cannot make CLEAN with NO DISTORTIONS presets using breakaway one. ( after 9 dbr whatever preset i chose i ve got distortions caused by clipper which runs at LOW CPU USAGE ( we cannot change that ! , we need more steps like stereotool does )
please add more cpu power choise especialy for final steps because cpu calculations matter on high dbr presets.
December 27, 2016 at 3:44 pm #14722cyberneticorganismMemberI also want to note that the Perfect Declipper VST plug-in crashes as soon as i activate it in BBO. As long as that is not working, BBO is not usable for me.
And second is that i think the settings for the stereo expander are a bit strange. In BBP you can arrange it band by band, and in BBO they are more general.
I hope Leif reads this too 😉December 27, 2016 at 3:49 pm #14723LeifKeymasterCamclone! How I have missed you 🙂
1) Stereo pilot adjust — no, good riddance. Fewer buttons is a good thing! Fewer things that can go wrong.
If you would like to reduce modulation for multipath prevention (good idea!) there is actually a good way to do it. This is an idea that is successfully used in many countries in Europe. It's called ITU-BS412 MPX Power! Enable the MPX power mode, and you'll find separate versions of every preset that have been specially adjusted for this scenario. You can then set the MPX power slider anywhere you like, and the pilot will stay right where it should be at 9.0%.
2) I thought about it while I was created it, but decided against it. Here's why: if a VST plug-in is crashing on its own (without you being there making adjustments) then really it is not suitable for on-air use. Imagine if it crashed repeatedly — you would then have glitches on the air as I was cycling it off/on! Yes, it would be possible to make the VST host even more intelligent so that if it crashes too often then stop trying to use it.. but at some point, you draw a line and say "this plug-in is garbage". I do that the first time it crashes — problem solved! :). If it crashes when not attended, it is better left off until you can look into it. This way, even if a plug-in crashes, you're still on the air with clean sound.
3) I am VERY happy with the low CPU load of Breakaway! This was an intentional design decision. BreakawayOne is not Stereo Tool. BreakawayOne is when you want quickly get on the air with fantastic sound and then get back to *other* things in your life. If you're looking for something to spend a lot of time tweaking, Breakaway isn't it! It never was.
By keeping the CPU load low, we have several benefits:
A) I can simply say "it'll run on any PC you can buy today" without having to waste your time on details.
B) It will keep running fine even when your CPU fan slows down because it gets clogged up with dust years down the line.
C) Headroom is safety!Best,
///LeifDecember 27, 2016 at 3:50 pm #14724LeifKeymaster[quote author=cyberneticorganism link=topic=5367.msg18973#msg18973 date=1482853496]
I also want to note that the Perfect Declipper VST plug-in crashes as soon as i activate it in BBO. As long as that is not working, BBO is not usable for me.And second is that i think the settings for the stereo expander are a bit strange. In BBP you can arrange it band by band, and in BBO they are more general.
I hope Leif reads this too 😉
[/quote]Hope and you shall receive :).
I've tested ST and it worked perfectly. I didn't test Perfect Declipper but I know others have.
Are you using the 32-bit version?
///Leif
December 27, 2016 at 4:12 pm #14725cyberneticorganismMemberYeah, it's the 32-bit version. As soon as i enable it, it says the BAOneVSTHost has stopped working. And i did close BBP and the Perfect Declipper plug-in before i enable it in BBO.
I'm using Windows 7 64-bit on my "server".
The path is: C:\Program Files (x86)\SpacialAudio\SAMBC\plugins\dsp_perfect_declipper.dll, don't know if that can be a problem somehow. But it's working perfectly in BBP.Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0Problem signature:
P1: BaOneVstHost.exe
P2: 3.16.84.0
P3: 585b929f
P4: BaOneVstHost.exe
P5: 3.16.84.0
P6: 585b929f
P7: c0000005
P8: 00007b21
P9:
P10:Attached files:
These files may be available here:
C:\Users\SERVER\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_BaOneVstHost.exe_d1cb756b9d7cff22567d2bb1472d16cae4d95719_7d49a988Analysis symbol:
Rechecking for solution: 0
Report Id: 8fd53f21-cc4e-11e6-a099-bcaec57c48b8
Report Status: 0December 27, 2016 at 6:27 pm #14726LeifKeymasterWeird!
Are you using the latest versions of Perfect Declipper and BaOne?
I am, and it works here.
Best,
///LeifDecember 27, 2016 at 8:14 pm #14727timmywaParticipantThe perfect declipper 32-bit VST plugin is working great. I recently discussed with Hans if he could update it. He said it should be updated with the new delossifier tonight (12/27) in his latest beta release. You could also use the full ST VST and do a factory reset, which would turn everything off. Then only enable declipper. I've not seen any crashes with either configuration.
December 27, 2016 at 8:37 pm #14728cyberneticorganismMemberEhmmm, i found the problem. Do you see the first 3 letters of the plug-in i posted in my previous post? It starts with dsp… ::) For some reason i always used that one in BBP, and i need the vst_perfect_declipper.dll. That one is indeed working. I "saw that over the head", as they would say in the Netherlands. Sorry guys 😀
Btw. The VST is not updated yet (still 2.00), maybe later tonight.
December 27, 2016 at 11:58 pm #14729cyberneticorganismMemberI also had an issue with the CPU reaching around 100% on 1 thread, which made the stream stutter. I installed the new VAC from the link on the BBO website (4.15c), and rebooted. So far so good. I will test for a few days if it stays this way. Still a shame that BBO only uses 2 cores, and not 4 or more 😛
I think i experienced this issue in the past too, but don't remember if it was after some time or right away. But that's why i start using livelink in SAM to transport the audio to BBP, instead of VAC. It's a 2600K CPU, so that should be fast enough 😉 I will keep you posted. And if someone had the same issue, i would love to hear the cause.
December 28, 2016 at 12:55 am #14730LeifKeymasterAh! That would explain it indeed.
It seemed silly to make a new product with Winamp DSP support, 10 years after everyone else stopped using Winamp, so I wrote a VST host instead. 🙂
That said, it should not have crashed! That's never the right answer, never acceptable. You found a bug. Thank you, and I will look into it.
As for the CPU core usage:
The reason for not evenly distributing the load is one word: latency.
BaOne, if you have less than three FM cores enabled, on a system with two or more cores, will do a benchmark when starting.
It will process half a second's worth of audio, or it will process for half a second, whichever comes first. This way, it figures out the performance of your CPU.
If the speed is less than 1.3x real-time, it will split the high-quality FM processor up into two threads, adding an extra 100ms of latency or so.
Otherwise, the FM processor runs in one core, because the processor is fast enough to do it.Your CPU is just fast enough, that's why you're seeing so much in one core.. but, audio is stable, isn't it?
Once you add more processing elements (HD, streaming encoders etc), the other cores will fill up too.
VST plug-ins execute in their own process so they will also use other cores.Best,
///LeifDecember 28, 2016 at 2:17 am #14731cyberneticorganismMemberAah ok. Thanks for the answer. I thought the stuttering before the reboot and high CPU thread usage was because of it going around the 100%, there should always be some headroom. But i will see if it keeps running stable now. If it is, i can do the upgrade as i only have to activate the license and that's it (and first request it). I must say some other stuff is running on the same CPU too, like the old BBP with the Perfect Declipper, SAM, DanceBoost Silence Detector etc.
I only use the HD core, as i almost never use my FM transmitter (it's also illegal ;D).
And regarding the cause of the bug: It's between the chair and the keyboard lol.
December 28, 2016 at 2:52 am #14732LeifKeymasterHm. What CPU is that, and how much of the 100% CPU load was Breakaway's?
I report the total CPU load because it's what matters.. it doesn't matter if Breakaway is using only 10%, if you have other things in the system filling up the CPU load.
Also, I strongly recommend you run BreakawayOne as a service — then the audio processing runs at Realtime Priority, as it should — it's the most time-critical thing in the system!
As an app, I cannot run real-time for two reasons:
1) Only ADMIN/SYSTEM can run realtime, so you'd have to run it elevated.
2) The user interface would then also be realtime, which defeats the purpose.Running as a service is the best way to do it, all around. The only thing you lose is that you can no longer configure VST plug-ins unless they have a web interface / remote control, but the de-clipper is set-and-forget so this is not a big issue in practice.
Best,
///LeifDecember 28, 2016 at 4:19 am #14733timmywaParticipant[quote author=cyberneticorganism link=topic=5367.msg18983#msg18983 date=1482871075]
Ehmmm, i found the problem. Do you see the first 3 letters of the plug-in i posted in my previous post? It starts with dsp… ::) For some reason i always used that one in BBP, and i need the vst_perfect_declipper.dll. That one is indeed working. I "saw that over the head", as they would say in the Netherlands. Sorry guys 😀Btw. The VST is not updated yet (still 2.00), maybe later tonight.
[/quote]The new VST for declipper was posted tonight: http://forums.stereotool.com/viewtopic.php?f=14&t=13078&start=10#p41524
December 28, 2016 at 11:07 am #14734cyberneticorganismMemberThanks Leif and Timmy! I e-mailed Hans to upgrade my license for the Perfect Declipper. Because that Delossifier is a nice thing for a MP3 stream 🙂
Leif: It's around 12/13% tops, it's now OK since that upgrade of VAC and reboot. We shall see…
Before 1 thread (of 1 core) was around 100%, and also "Max" CPU value in BBP. Very weird.I will take your advise, and run it as a service then, because now it's not.
Nice thing of that Perfect Declipper VST is that you can also choose on which cores you wanna run it, so i configured it to run on 2 cores that where doing there wintersleep ::)
-
AuthorPosts
- You must be logged in to reply to this topic.