Re: Selig Gain RE new version 1.2.3
Posted: 11 Oct 2015
How about thanks to everybody and we can end this pointless bickering?
me too i own them all and i thank all of them.normen wrote:People thanked Selig for the fact that he offered compensation for the problem - something that is solely his decision. In fact, if I wanted to be mean I could say Pitchblende made the mistake and Selig did the damage control - all the more reason to thank Selig specifically. That said, I am grateful for Pitchblende enabling Selig to put out such fantastic devices.submonsterz wrote:then when praising people should praise the team as a whole yes not just selig but maybe a thanks selig and team or thanks selig and pitchblend for the fix .
if I do a job with someone they take the same credit as me its a joint effort not a sole venture.
You only have yourself to thank for that!submonsterz wrote:even though fixes and updates make no difference to me as my res are in 6.5 and cant be updated or fixed now days.
I do not code in C++, that is David's department. But not all bugs are in the C++ code, so not all bugs are fixed by folks who know C++, as C++ is not the only coding language used to build REs.submonsterz wrote:do you code in c++selig wrote:Except it is not correct, because I code in XML and .lua for all of these products. So quite literally, I DO code. Now if you want to get specific and ask if I code in a specific language or not, go right ahead and I will answer!submonsterz wrote:you think rude i think correct .challism wrote:Care to edit your comment any more before I reply? I'm not here to argue with you. I think your post was rude. I think my post speaks for itself. I'm done.
and was the fix a fix that had to use c++?
and did you code the fix yourself or did pitchblend make the fix?
no props for not allowing me to transferre my re to my 7.1 account for that one not myself there either...challism wrote:You only have yourself to thank for that!submonsterz wrote:even though fixes and updates make no difference to me as my res are in 6.5 and cant be updated or fixed now days.
I'm lucky to have access to the re sdk and documentation along the line so I know what it takes no need to tell me there .selig wrote:I do not code in C++, that is David's department. But not all bugs are in the C++ code, so not all bugs are fixed by folks who know C++, as C++ is not the only coding language used to build REs.submonsterz wrote:do you code in c++selig wrote:Except it is not correct, because I code in XML and .lua for all of these products. So quite literally, I DO code. Now if you want to get specific and ask if I code in a specific language or not, go right ahead and I will answer!submonsterz wrote:you think rude i think correct .challism wrote:Care to edit your comment any more before I reply? I'm not here to argue with you. I think your post was rude. I think my post speaks for itself. I'm done.
and was the fix a fix that had to use c++?
and did you code the fix yourself or did pitchblend make the fix?
As for the your points being made here, you are making what I would call "Straw Man" arguments.
No one has claimed I code in C++.
No one has claimed the fix did not involve C++.
No one has claimed I was the one who made the fix.
To say otherwise would be disingenuous IMO.
I hope this puts the subject to rest.
That being said (and hoping to move on now), we could sure use the help of anyone who experienced this bug to test the fix - contact me if you are able to help!
Here's my List of Product's i would like to be compensated with ' for the Trouble i ENDURED whilst my Machine CRASHED !selig wrote:If anyone affected by this bug would like some form of compensation for their troubles, please contact me at
gilesreaves@seligaudio.com
to discuss getting a free license for any Selig Audio product that you don't already own. If you already own all of our products (and thank you if you do!), I will either provide a free license for the product of your choosing to another user, or give you a rain-check for a future Selig Audio product.
Please accept my sincere apologies for anyone affected by this nasty bug and for the chance to make it up to you!
Giles Reaves
Selig Audio, LLC
Thanks for the help, let me know what you find (good and/or bad) at gilesreaves@seligaudio.com.Majestik Monkey wrote:Here's my List of Product's i would like to be compensated with ' for the Trouble i ENDURED whilst my Machine CRASHED !selig wrote:If anyone affected by this bug would like some form of compensation for their troubles, please contact me at
gilesreaves@seligaudio.com
to discuss getting a free license for any Selig Audio product that you don't already own. If you already own all of our products (and thank you if you do!), I will either provide a free license for the product of your choosing to another user, or give you a rain-check for a future Selig Audio product.
Please accept my sincere apologies for anyone affected by this nasty bug and for the chance to make it up to you!
Giles Reaves
Selig Audio, LLC
which took all but One Millionth of a second . . . But who knows what i could of wrote in that milli second?
as it wizzed past me, like my life was coming to an end & the four horse men of the Apocalypse had turned up ! / Gain 1.2.4
Ps it did crash my system ' & i am up for Retesting it ! / JpPropellaed Intel Quad core 8 gig Ram Win 7 Pro .....
I do QA software testing (among other things) in my day job, so I have a perspective on this.meowsqueak wrote: <snip> My apologies to everyone affected by this issue. It turned out to be related to a change in "undefined" behaviour in the SDK. The bug concerned has always been present in Gain, but was benign and therefore undiscovered until now. Version 1.2.3 involved an update to SDK2.2, and something changed with the SDK2.2 compiler in Windows that now triggers the crash on that platform. It's a bit nasty that it sometimes brings down Reason too - but that's what undefined behaviour means I suppose! I'm sorry to anyone that has lost work because of this issue.
This is exactly how I understand what happened, and I want to be 100% clear that it was MY call to not test on Windows machines, in that I was the only tester after the last change because of mistaken assumptions (which I have previously mentioned) made on my part! I now have access to a few Windows machines for future testing to avoid this very issue!doctecazoid wrote:I do QA software testing (among other things) in my day job, so I have a perspective on this.meowsqueak wrote: <snip> My apologies to everyone affected by this issue. It turned out to be related to a change in "undefined" behaviour in the SDK. The bug concerned has always been present in Gain, but was benign and therefore undiscovered until now. Version 1.2.3 involved an update to SDK2.2, and something changed with the SDK2.2 compiler in Windows that now triggers the crash on that platform. It's a bit nasty that it sometimes brings down Reason too - but that's what undefined behaviour means I suppose! I'm sorry to anyone that has lost work because of this issue.
If I understand correctly, the real issue here is that the Props made a change to the SDK. Compiled with the previous SDK, the Gain code had a 'bug of no consequence' (i.e. a bug that did not affect the behavior of the RE in Reason) and was thus never caught in testing. The bug became consequential when the SDK was changed.
I don't know how well the Props communicated this change in how the SDK handled "undefined behavior" to developers when they made the updated SDK available. But if it wasn't communicated clearly to RE devs, then I see this as a case of collusion: the Props are at fault for changing a fundamental bit of logic in the SDK, with regard to the handling of "undefined behavior", and not fully communicating the consequences to developers; and Selig got caught by this change because after the update to Gain was compiled using the newer SDK, Gain was not then loaded and tested on both the Mac and Windows platforms.
Word to the wise: if you are a developer of REs, and Props make a change to the SDK, you need to at the very least compile your RE with the new SDK and then check to make sure it loads into both the Mac and Windows versions of Reason.
Well from what I saw it was somebody taking issue with a software company outsourcing its coders?gak wrote:What the hell happened here?
Yeah, I agree it's far better to hold on to resentment and make snide remarks at people you don't like for years on end than it is to have it out with them once and for all.JiggeryPokery wrote: This is the age of social media! We need to completely stamp that kind of logical, sensible, rational behaviour out!! :p
Very gentlemanly, Giles. This would be a perfect opportunity to be... well, opportunistic. Truth is, I haven't lost money because of the buggy Gain.selig wrote:If anyone affected by this bug would like some form of compensation for their troubles, please contact me at
gilesreaves@seligaudio.com
to discuss getting a free license for any Selig Audio product that you don't already own. If you already own all of our products (and thank you if you do!), I will either provide a free license for the product of your choosing to another user, or give you a rain-check for a future Selig Audio product.
Please accept my sincere apologies for anyone affected by this nasty bug and for the chance to make it up to you!
Giles Reaves
Selig Audio, LLC
It's not as cool as your gorilla, but.....JiggeryPokery wrote:"Ostermilk: One of the last bastions and hold-outs of common sense remaining on the Internet!"
This is the age of social media! We need to completely stamp that kind of logical, sensible, rational behaviour out!!
No totally wrong I made the point to begin with no one was bothering to thank pitch blend even in the thread after they even had came here to say it was fixed just praise to selig .... The rest was the lash caused by those that wanted to make a fight over it . So look how it progressed from the point I was trying to make then look at reply to see why that all came about and you'll see I have no problem with out sourcing etc etc. If people want to go getting all funny then ill say truth and ask truths and that's all that was done from my end. People just get on the wagon cause I questioned thier obvious religion.Ostermilk wrote:Well from what I saw it was somebody taking issue with a software company outsourcing its coders?.gak wrote:What the hell happened here?
No interrogation at all others sparked that.GRIFTY wrote:Dude wtf don't be a dick. It's a simple bug, nobody has any right to a freaking interrogation here. Bugs happen act like a grown up
No, this isn't very grown up.submonsterz wrote:And I ain't got no problem with selig I have a problem now with the god like status everyone seems to put on him now from this.
Nor have been the way you all swung my comment elsewhere ....normen wrote:No, this isn't very grown up.submonsterz wrote:And I ain't got no problem with selig I have a problem now with the god like status everyone seems to put on him now from this.