A Roland Super JX / MKS-70 / JX-8P emulation - This is EightyTen!

[tumface]

If you read the post that jamcat is replying to, you'd see the reply is actually pretty restrained, all things considered.

[jamcat]

We would get a less lot unnecessary drama on this forum if you could just take yourself a little less serious and stop acting like you are the defender of the faith. In your own crusade.
Lighten up, think before you post. Maybe you would get more respect.

People asking valid questions and making legitimate requests shouldn't be attacked or dismissed by the developer. I have never had an interaction anything like this with any other developer here.

[Morphoice]

Version 1.0.0 is out.
As announced and stated in the plugin description, the free betas have been pulled and are no longer offered.
We haven't hit any issues in testing across various machines here, but something will turn up sooner or later — that's how it goes. If you do run into anything, please use the ticket system on my website rather than this thread, as I am not constantly monitoring all forums. That way it gets tracked properly and we promise to fix it as quickly as possible.

[jamcat]

"A free Roland Super JX / MKS-70 / JX-8P emulation - This is EightyTen!"

[slackhead]

"A free Roland Super JX / MKS-70 / JX-8P emulation - This is EightyTen!"

Take another look drama queen

[jamcat]

Great. If he had fixed it 3 days ago, he would have avoided a lot of contention.

But can you believe it's only been 3 days?

And just a week since he posted this:

With the Jupiter-8 emulation nearing the finish line, a JX-10 just came in for repair — which feels like it could be the next project. Given what I've learned building the bi-timbral Jupiter, how would you all feel about a Super JX emulation? Working title: EightyTen.

Who goes from thinking about developing a new plugin to a full commercial product in one week?

A respectable developer spends weeks testing before releasing a new commercial product. They certainly don't release an untested product the same day they're adding new features.

[iPlogger]

PlugInGuru showed them during yesterday's Livestream. They sounded great and he gave a good review. I ended up getting both EightyEight and EightyTen. Haven't tried them out yet. Will try and install them tonight.

[simmo75]

Version 1.0.0 is out.
As announced and stated in the plugin description, the free betas have been pulled and are no longer offered.
We haven't hit any issues in testing across various machines here, but something will turn up sooner or later — that's how it goes. If you do run into anything, please use the ticket system on my website rather than this thread, as I am not constantly monitoring all forums. That way it gets tracked properly and we promise to fix it as quickly as possible.

Congratulations!

[antto]

And just a week since he posted this:

With the Jupiter-8 emulation nearing the finish line, a JX-10 just came in for repair — which feels like it could be the next project. Given what I've learned building the bi-timbral Jupiter, how would you all feel about a Super JX emulation? Working title: EightyTen.

Who goes from thinking about developing a new plugin to a full commercial product in one week?

A respectable developer spends weeks testing before releasing a new commercial product. They certainly don't release an untested product the same day they're adding new features.

there seem to be these New developers now, who are somehow extremely knowlagable and they write code faster than you can make a sandwich

i'm not familiar with those specific synths mentioned, but a bunch of years ago i wanted to make just a "synth that's inspired by JP-8000 and D-50" without claiming of accurate emulation because i don't even have any of those two (nor will ever have them), and so i mostly worked with dry recordings of these plus the user manual... that took much more than 1 week, but i'm no magician
also, with everything i've made so far, i've needed mountains of extra help, as you can see if you search the forums
some of these New developers can do just about anything and they don't need help, they already know how things work.... there's a Bright Future ahead of us!

do i understand correctly that he didn't realise until yesterday that the oscillator phase shouldn't be reset on every NoteOn?

[Morphoice]

The terms for each plugin are stated on its page. In the case of that EightySix beta, expiry on final release was clearly part of the deal at download — that's what a beta is, and it's also a good thing to pull faulty software. Fixes and working versions were always available at the agreed upon terms. No one's production got interrupted.

On the timeline: this EightyTen DSP has been in development for over two years. What happened in the last week was simply the decision to release it into the wild and the finishing work — a few all-nighters while a Super JX sat on my bench for repair, which let me calibrate directly against the hardware and I whipped up the GUI. That's not a plugin built in a week; that's a plugin that got its final calibration in one and drew from years of learning how to make these. All of this has been explained before multiple times.

If the development pace is too fast for your liking, you're welcome to use products that ship fixes more slowly. No hard feelings either way. The professional producers I work with prefer things fixed fast, as often productions depend on it. So I sleep less, move fast, and take pride in my job well done.

There's a working trial sitting right there for anyone to install and confirm it does exactly what it says. Which brings me to the thing none of this touches: does it produce the sound it is supposed to? That's what a synth is for. Load it up and judge it on that.

[bk]

And by that, I mean this conman took everybody for a ride.

I spent $60 and have 3 new synths that look great, sound great, and work great on my system.
Trying to figure out what the "con" is exactly.
Had I acted more quickly, it would have been $30.
Stop trying to "save" me

[Morphoice]

And by that, I mean this conman took everybody for a ride.

I spent $60 and have 3 new synths that look great, sound great, and work great on my system.
Trying to figure out what the "con" is exactly.
Had I acted more quickly, it would have been $30.
Stop trying to "save" me

Glad you're enjoying them — that's exactly what they're for. Shout through the ticket system if you ever need anything.

[jamcat]

Bait and switch is a type of con job.

A farce in three acts:

LICENSING

This plugin is a free beta. You can support its development using the pay-what-you-want option on Gumroad. Any contribution of $10 or more grants you a lifetime license, should future releases become paid. Note that older versions may stop working once newer ones are released.

As for the 'may stop working' line — that simply means I can't guarantee eternal compatibility with future OS or DAW updates, and I'm not legally liable if something stops working because you fail to update. Just like PG-8X stopped working when DAWs moved to 64-bit. It doesn't self-destruct, this isn't the movies.

BTW, I had a “free” version that became inoperable after it phoned home to find that the free beta was no longer valid. This guy has been playing a con job. And yes, it phones home. Screw that.

So much gaslighting from this dev.

[antto]

On the timeline: this EightyTen DSP has been in development for over two years. What happened in the last week was simply the decision to release it into the wild and the finishing work — a few all-nighters while a Super JX sat on my bench for repair, which let me calibrate directly against the hardware and I whipped up the GUI. That's not a plugin built in a week; that's a plugin that got its final calibration in one and drew from years of learning how to make these. All of this has been explained before multiple times.

you only had to calibrate it against this reference model, which i agree can be a simple task if and only if the model was "right".
this means that the model was already "right", so you made a model in 2 years, and calibrated it in one week or so

color me impressed

If the development pace is too fast for your liking, you're welcome to use products that ship fixes more slowly. No hard feelings either way. The professional producers I work with prefer things fixed fast, as often productions depend on it. So I sleep less, move fast, and take pride in my job well done.

nah, i'm just looking from the POV of a dude who has made an attempt to model/emulate some much simpler synth in the past, so i still remember what i had to go thru, in fact, i've left quite a long trail of crumbs publicly...

i guess this Fast pace maybe correlates with the public relation to the users, inability to answer boring simple questions, slight notion of diplomatic hostility, it makes sense... no one likes dealing with customers
much better to hide it away from a public forum and into a closed "ticket" system

There's a working trial sitting right there for anyone to install and confirm it does exactly what it says. Which brings me to the thing none of this touches: does it produce the sound it is supposed to? That's what a synth is for. Load it up and judge it on that.

see, this is what i find weird
the phrasing here
"does it produce the sound it is supposed to"
i thought it's already "right" and even "calibrated" how come you write this phrase (i saw it earlier in previous posts too, written in a few different ways, but still carying the same uncertainty)
you also said "proud"

anyway, you don't have to answer, i'm not a user, i'm not even a developer anymore (i guess)
you can ignore this whole post just like you ignored the thing about the oscillator phase reset

[Morphoice]

On the timeline: this EightyTen DSP has been in development for over two years. What happened in the last week was simply the decision to release it into the wild and the finishing work — a few all-nighters while a Super JX sat on my bench for repair, which let me calibrate directly against the hardware and I whipped up the GUI. That's not a plugin built in a week; that's a plugin that got its final calibration in one and drew from years of learning how to make these. All of this has been explained before multiple times.

you only had to calibrate it against this reference model, which i agree can be a simple task if and only if the model was "right".
this means that the model was already "right", so you made a model in 2 years, and calibrated it in one week or so

color me impressed

If the development pace is too fast for your liking, you're welcome to use products that ship fixes more slowly. No hard feelings either way. The professional producers I work with prefer things fixed fast, as often productions depend on it. So I sleep less, move fast, and take pride in my job well done.

nah, i'm just looking from the POV of a dude who has made an attempt to model/emulate some much simpler synth in the past, so i still remember what i had to go thru, in fact, i've left quite a long trail of crumbs publicly...

i guess this Fast pace maybe correlates with the public relation to the users, inability to answer boring simple questions, slight notion of diplomatic hostility, it makes sense... no one likes dealing with customers
much better to hide it away from a public forum and into a closed "ticket" system

There's a working trial sitting right there for anyone to install and confirm it does exactly what it says. Which brings me to the thing none of this touches: does it produce the sound it is supposed to? That's what a synth is for. Load it up and judge it on that.

see, this is what i find weird
the phrasing here
"does it produce the sound it is supposed to"
i thought it's already "right" and even "calibrated" how come you write this phrase (i saw it earlier in previous posts too, written in a few different ways, but still carying the same uncertainty)
you also said "proud"

anyway, you don't have to answer, i'm not a user, i'm not even a developer anymore (i guess)
you can ignore this whole post just like you ignored the thing about the oscillator phase reset

The phase issue was already discussed, explained and addressed earlier in this thread. The fix is already in the final release.