Yeah, those lazy Japanese......always cuttin' corners.TheoM wrote:First to Korg.. if predator can provide it's FX section so could have Korg.. they were just too lazy to program it within the RE SDK gui limitations..
And I guess they haven't released another rack extension since (June, 2013) out of that same laziness?!?
Yes, it wasn't the obvious money-making choice.TheoM wrote:Secondly, Gforce's mistake was releasing an $100 mellotron Re as their first. No offence but who cares. There are countless soundfonts of good quality, and refills that coast a third of the price that have enough mellotron for anyone.
And I guess you're suggesting that this mistake, and the lack of sales that resulted from it, is the reason why they've back-burnered their second rack extension, even though they were seemingly really close to releasing it?!?
Yet there's still a lot of clamoring for the Satin rack extension......which they can't stop from crashing, apparently......as well as their synths in rack extension format.TheoM wrote:Thirdly, U-HE's mistake was releasing buggy plugins that eat DSP for breakfast, and all with latency. So if his sales aren't good, it doesn't matter how cheap they are. I have also seen many comment , including myself, that they refuse to buy them because they are more than the VST for less (bugs and 10 - 20x the cpu usage). His mistake.
You've clearly got an axe to grind with the man. Yes, Rough Rider was a stupid first choice, but I love BigSeq2, and I think more AD plug-ins would have been a most welcome addition to the rack extension shop.TheoM wrote:Chris Randall released one of their weakest plugins as the first.. again, his mistake.. not that he is some sort of coding genius anyway, and he certainly doesn't keep his 30 day refund policy or answer emails. His AU's were bug ridden for many years with ignored repeated support requests. He is not anyone whose opinion means anything to me.
You're trying to lay 100% of the blame for these shortcomings/failures at the feet of the developers, but I think a lot of these "mistakes" were, more than anything, down to SDK limitations (see: the Sugar Bytes fiasco).
If you're trying to launch a new plug-in format, I think you need to go out of your way to teach and support third-party devs, and nurture relationships.
We obviously don't know if Props' has done this, or to what degree they have, but there have certainly been several rumblings to the contrary.
You've named the three threads rack extensions are hanging by.TheoM wrote:Softube and synapse have some of the most expensive products on the store (with antidote and tsar) and yet keep on releasing.. softube are porting their tube tech next.. a $489 channel strip.. Rob Papen is making an RE exclusive synth even that is coming in a few weeks... The developers that release the right stuff that is bug free are doing well and want to continue to support the platform.
Let's see if they hold.
And why didn't you mention latency with Softube's rack extensions?
" - In 44.1 khz, all softube due to oversample - there is also a bug with the softube that they don't bypass their latency when the plugin is bypassed. therefore the easiest way to mix with them is just insert "bypassed" versions on parallel channels where the latency causes issue."
