- This topic has 8 replies, 6 voices, and was last updated 16 years, 1 month ago by
.
-
Posts
-
Hi Leif,
I just upgraded to version 1.20.04 and it seems to be working just fine except one annoying visual issue. When I stop a song or when a song ends (no matter what player I use), the AGC and Mutiband visualizations in the Simple and the Meters views freeze at the point they were at the time I stopped the song or at the time the song ended respectively. There is no visual effect in the Osciloscope view after finishing a song or stopping it. These two fields in Simple and Meters views should be cleared i think since the song that was played is no more here – it was stopped or finished. The rest of the fields – Input, Limiter and Output don’t seem to be affected and are always cleared. I don’t remember such visualization issue with the older 1.01a version. I know you want to release 1.20.04 on Monday so I would like to see your comment before that.
Thanks,
MikeThis sounds like the proper operation. If you were to pause a song you don’t want it to kick back in any different than it was when you paused it, do you? I believe BreakAway is telling you what settings/levels are currently active and will be active when you restart the music. This being said, BreakAway has a very fast response time, therefore any sound you start to process will be corrected quickly.
Yep, it’s supposed to do that, when there’s digital silence on the inputs. The reason for this is so that it doesn’t use CPU when it’s not being used. Which will allow you do to things like put Breakaway in bypass, and play a 3D game, without any precious CPU going towards Breakaway.
The GUI of Breakaway can take up anywhere from a little to most of the total CPU that Breakaway uses, mainly depending on what video-card you have (the Breakaway GUI is *HIGHLY* optimized and accelerated by your video-card). Updating just the INPUT and OUTPUT levels metering would only update that small portion of the GUI, and seeing as even though it’s only really a cosmetic thing, I don’t see why Leif couldn’t do it. I’m not sure about how optimized the explorer toolbar one is, but the pixel count is WAY smaller than where most people will have the main Breakaway GUI at (which only updates the pixels it needs to, like i said: highly optimized)
So, that’s the main reason it "freezes" when there’s no input audio. But yes, also… it does have some benefit to keep the same processing "action" frozen too, in case you are only pausing the music, for instance.
There’s also the issue of power conservation, and if Breakaway was running 24/7 it would have an effect on your CPU’s power consumption, some more-so than others. So having Breakaway "freeze" like it does is a very "green" thing to do, don’t you think?
Hello!
I am a registered user of the 1.0 release – I notice my license code does not work for this Beta – is that by design?
Thanks for the help!
Yep, if you check the thread where Leif announced the new version (as release candidate), it mentions that you’re going to have to email support for a new one.
That’s an interesting point you make. The installer or Breakaway itself should detect that you have a key, but that it’s old, and inform you that you need to email support for a new one.
There’s a similar problem I reported by email a while ago but is still present: If you bring up the Settings window and then close it by using <Alt-F4> or clicking on the "X" icon in the title bar, Breakaway doesn’t restart but it leaves the system default sound device set to Breakaway Pipeline 1.
TVholic: Your email must have slipped through the cracks. Sorry about that — this sounds like a very real bug. I’ll look into it right away!
Thank you.
///Leif
- You must be logged in to reply to this topic.