Home › Forums › Breakaway Professional Products – [discontinued] › Peak Limiter not Working in Live .90.93
- This topic has 15 replies, 3 voices, and was last updated 14 years, 7 months ago by michi95.
-
AuthorPosts
-
March 6, 2010 at 7:40 pm #733AnonymousGuest
I’ve noticed in this latest release that no matter how ugly any EQ-induced clipping gets the peak limiters in Live never kick in. The obvious solution is just to turn the output down, but it would be nice to have the limiters to curtail any peaks that might still cause clipping. Am I missing something or is this a bug?
While you’re at it, it would still be great to have that taskbar mode for Live! I mean it’s already in the personal version. How hard can it be?
Stuart
March 7, 2010 at 12:11 am #10105JesseGMemberIt’s a known bug in the speaker controller after v0.90.82, needs to be fixed. I’m using Live v0.90.82 still because of that.
April 3, 2010 at 10:08 am #10106LeifKeymasterFixed for 0.90.94 🙂.
///Leif
April 3, 2010 at 10:15 pm #10107JesseGMemberConfirmed, I’m using it right now. Fantastic sound too.
April 4, 2010 at 12:35 am #10108michi95Member[quote author=”Leif”]Fixed for 0.90.94 🙂 .[/quote]
[quote author=”JesseG”]Confirmed, I’m using it right now. Fantastic sound too.[/quote]So, beta version 0.90.94 is ready for release ?
Or is it not a beta and more or less still an alpha version for bug tracking of the inner circle (Leif and Jesse ?) of beta (alpha) testers ?Call it beta, call it alpha, call it whatever.
There might be small bugs (or some features incomplete) !?
I don’t care.
Let us have a look on this version !
(please give us a download link !)
The typical beta location link……..
/beta/breakaway_live_setup_0.90.xy.exe
works with build 93, but not with build 94 !
Please, make it work.April 4, 2010 at 7:23 am #10109JesseGMemberI simply meant I was using a build of 0.90.94 that includes the speaker controller fixes. 😉 Not the final 0.90.94, because it’s not until it’s on the site. Please don’t make me regret that I’m open with some of the information I share. 8)
April 4, 2010 at 12:34 pm #10110michi95MemberThank you Jesse !
I misunderstood you, because I wanted to misunderstand you .
Now I understand. 💡quote :Please don’t make me regret that I’m open with some of the information I share. 8)I don’t think that you betrayed somebody or something with your information (or was it classified as top secret ?).
So, please keep on bug tracking until it (the final stable beta – before Breakaway I did not know that something like this exists ) is ready.
I will try to be patient.
But please allow me another question (I hope the answer is not top secret ?):
How long approx. ?
Is it a question of days ?
Of weeks ?
Of months ?
(My first intention was to add here a line "Of years ?", but I came to the conclusion that it would be a ridiculous horror scenario.)Happy Easter !
I thought build 0.90.94 would be our Easter egg.
But it seems that there is no Easter bunny here.April 4, 2010 at 10:19 pm #10111JesseGMemberGreat things take time, and more is getting added other than bugs, lol.
Have a great spring time, to everyone in the northern hemisphere who may read this.
April 4, 2010 at 11:00 pm #10112LeifKeymasterApril 5, 2010 at 12:20 am #10113michi95MemberJabbadabbadoo !
Thank you very much Bunny (the artist formerly known as Leif) !
By coincidence ?
Or by demand (not really) ?Oh, Jesse’s answer really darkened my hopes.
But, finally it happened.
I can’t wait to try it.April 5, 2010 at 7:23 am #10114LeifKeymaster[quote author=”michi95″]By coincidence ?Or by demand (not really) ?[/quote]
Mostly by demand. It was getting ready for release, I could have hung onto it a while longer, done more testing etc, but I figured now was as good a time as any. 😉
///Leif
April 5, 2010 at 11:54 am #10115michi95Member@ Leif
As I wrote analogous in my pm a few days ago:
Your "problem" is that most of your beta versions are much more stable and reliable than yearly 1.0, 2.0, 3.0,…. etc. releases of major software companies.A beta version is (normally) a beta version and not a major release !
So if there occurs any problem (I don’t believe in any severe !) it would be okay, because everybody should know what he or she does, when they execute a beta version installer.It seems to me as if you try to redefine the meaning of "beta version" with the type of your stable and reliable beta releases ! 😀
The eggs are really big this year.
And Breakaway build 94 is the biggest ! 😀 😆April 5, 2010 at 1:51 pm #10116LeifKeymaster[quote author=”michi95″]It seems to me as if you try to redefine the meaning of "beta version" with the type of your stable and reliable beta releases ![/quote]
You know what, you’re right.. And it really doesn’t make sense to be spending this much time on 0.0001 worth of a version number increase. I should be making bigger jumps for sure. I guess I’ve kinda painted myself into a corner too. Maybe it’s time I jump out 🙂.
Only thing is.. Let’s say I make the next version 0.91.00… How much do you want to bet that lots of people will confuse it with 0.90.91?
Perhaps I should make the next version 0.95.00 just to be sure? 🙂
Decisions, decisions.
Regarding beta and stability, i wonder if the answer is that I develop differently from how most software is developed?
My development goals are a moving target. I know I’m making an audio processor, sure, but I tend to implement new features as I (or friends, or customers) need them. This means that I don’t have a long feature list to implement all in one go. If I did, I would probably have done that, ended up with something relatively buggy, and that would have been the beta. Then I would work out the bugs little by little until it was ready for release.
Doing it that way would be a tedious way to develop though. The initial development / inventing is the fun part, finding bugs later is no fun at all. Thus, as a survival strategy, I try to spread the fun out, in fact I save it for last whenever I can. When it came to Challenger, I did the gui the first day, without writing a line of the actual audio algorithm. Once that boring part was done, I did the actual audio part the next day. That way, I had the fun part to look forward to, which helped me through the boring part.
This also means that I’m very careful not to pull it apart too much at the same time. I try to keep it stable and properly functioning throughout development, because if it ever doesn’t work, any number of other problems could be hiding behind the currently visible problem, and it’s that much harder to get it working again. Occasionally, bugs do slip through (I don’t know how the 0.90.93 broken limiter in Live slipped past though, that was ugly), but usually it’s pretty stable and usable throughout development.
Sorry, rambling on.. Anyway, I believe the above are a reasonable explanation why the beta label doesn’t mean much when it comes to my projects. My goal in development is a constantly moving target, so I have to tread carefully so I don’t fall and break my leg before I can catch up to it 😉.
Best regards,
///LeifApril 5, 2010 at 5:26 pm #10117michi95MemberOooouuupsss !
I completely changed my mind.
Now I think that you take too big steps with the version numbers.I think it is necessary to compile a 0.90.94b !
I have found an unbelievable "bug". ❗ 😆
There is Zenith (the new version) and Zenith OB (the old version) and other OB presets.
But where is Twente OB (the version before build 87 ? – for sure as it was in build 69, see link) ?Ironically this is missing, though I think that this request for the old version of Twente started (or re-upped) the discussion and the wish to access older presets:
viewtopic.php?f=5&t=872&start=0I don’t need this (old Twente) any longer, because I found a better alternative for my special purpose.
But I don’t know if sven_1968 and Gerrie still need it.But seriously:
When I compare build 69 and build 94 it is absolute ridiculous to name them 0.90.69 and 0.90.94.
There are so many changes that indicate to name them for example 1.00 RC3 and 1.5 RC1.Yes, it is really a problem with your small numbers, because nobody would expect that there are so many changes, improvements and new features inside.
Using this 0.90.xy beta naming scheme I would expect only bug fixes for a buggy (!) software, but not all these changes and new features for an almost stable and reliable application.
From my point view it is time to release a 1.00 version (just wait a few weeks for user feedback – if anybody has a severe problem with build 94).
And then go on with beta versions like this: 1.00.01 beta, 1.00.02 beta, …..
Ten betas should be enough.
When a beta is stable then release it as non-beta, for example: 1.00.07 beta -> version 1.01 !Why selling a good and stable software under a misleading beta label ? ❓ ➡ 💡
April 5, 2010 at 6:23 pm #10118LeifKeymaster[quote author=”michi95″]rom my point view it is time to release a 1.00 version (just wait a few weeks for user feedback – if anybody has a severe problem with build 94).[/quote]
I’ve actually been meaning to do this for a long time now, and then all of a sudden we had a rash of strange things reported from customers, such as BBP using more and more cpu every day until audio starts stuttering — all things I have never been able to reproduce, and which seem to not affect the majority of users. This is why it’s been so long since I even put a new version on the official download page, but I think what I’m going to have to do now is to simply ignore these reports and release anyway, cause I can’t hold the release forever, and I can’t fix what’s not broken.
Good point about Twente though. Will do it for 0.90.95, along with Motor City.
///Leif
-
AuthorPosts
- The forum ‘Breakaway Professional Products – [discontinued]’ is closed to new topics and replies.