One Synth Challenge #176: Wavetable by SocaLabs (MyLoFy Wins!)

[NeuKatalYst]

So, is there a way to achieve slide notes (portamento, glissando or whatever...) without the envelopes retriggering? I didn't find out how...

Legato, in any synth.

Nope, still triggering the envelope in this one... even though I have the latest version (1.0.15)

Mm. I'm AFK at the moment (I'm typing this on mobile), but which type of envelope are you using: the mono (per voice), or global modulator? It's the two different types of symbols I asked about earlier. Maybe they make a difference: the global modulator on an LFO doesn't reset, for example.

[SeBaer]

[...] which type of envelope are you using: the mono (per voice), or global modulator? It's the two different types of symbols I asked about earlier. Maybe they make a difference: the global modulator on an LFO doesn't reset, for example.

Amp and filter envelopes are hard wired, so this distinction does not apply.

[ontrackp]

What's your opinion?
Though I love to see SocaLab Wavetable grow, I start to see a problem with it during the challenge month. I choose to be early this month with my track, thinking the Synth is stable in terms of features. That even more because I have missed the contribution deadline for #174. But now the synth grows with each day, latest addition new distortion algorithms.

I don't think this is a good approach for a level playing field. What happens when by the mid of october we start to see a phaser, or as people suggested, cross oscilltor FM/AM/RM ... then we have a second challenge: who can make the most convincing "feature requests" and get the feature she wants ...
I would suggest to freeze the version at 1.0.15 feature wise and only allow for furthre bug fixes.
What do you think?

I do see your point. From a competitive perspective this would be more balanced. However this would take away a unique opportunity for the developer to get one of high user feedback to test the new features that he implements. We have to make a tradeoff between either having a even competition or an accelerated development of a freeware synth. I can't answer that question.
Maybe as a compromise people could write their version number used in the final submission ?

I did update the version where osc retrigger was added. As I couldn't get a consistent kick before. But I will not update my Submission now that I have submitted.

My feeling is that part of OSC is helping the developer -- and if the developer is able to implement changes it's a good thing. Worrying about the extra efx or whatever and how a track is going to place seems less important than improving the synth which will ultimately benefit everyone.

[MadMcMan]

What's your opinion?
Though I love to see SocaLab Wavetable grow, I start to see a problem with it during the challenge month. I choose to be early this month with my track, thinking the Synth is stable in terms of features. That even more because I have missed the contribution deadline for #174. But now the synth grows with each day, latest addition new distortion algorithms.

I don't think this is a good approach for a level playing field. What happens when by the mid of october we start to see a phaser, or as people suggested, cross oscilltor FM/AM/RM ... then we have a second challenge: who can make the most convincing "feature requests" and get the feature she wants ...
I would suggest to freeze the version at 1.0.15 feature wise and only allow for furthre bug fixes.
What do you think?

embrace the changes peter IMHO. i personally love the extras added.

[Double Tap]

What's your opinion?
Though I love to see SocaLab Wavetable grow, I start to see a problem with it during the challenge month. I choose to be early this month with my track, thinking the Synth is stable in terms of features. That even more because I have missed the contribution deadline for #174. But now the synth grows with each day, latest addition new distortion algorithms.

I don't think this is a good approach for a level playing field. What happens when by the mid of october we start to see a phaser, or as people suggested, cross oscilltor FM/AM/RM ... then we have a second challenge: who can make the most convincing "feature requests" and get the feature she wants ...
I would suggest to freeze the version at 1.0.15 feature wise and only allow for furthre bug fixes.
What do you think?

It's a fair point. But I have a quibble with your solution because it would mean dictating to a developer what they're allowed to do with their product for the rest of the month, ie only fix bugs and not add features they may have been working on for a while. That seems wrong to me, and probably not what you meant, so really it would be "stop at 1.0.15" or somewhere.

But back to your main point which is really all about the ethos of OSC and making a level playing field - how much is it a personal challenge (in which case, it doesn't really matter) and how much is it a competition (in which case it does)? The fact is that every round is a bit different - we've had some barely useable synths, some Windows only, some paid-for and some in beta - not to mention the different types which are better for some genres than others, so play to some people's strengths more. There's always a tilt, but it changes a bit every round.

The least fair playing field to me is one where you'd have to buy a new computer to take part - but if all it really means is a month off then I can live with that. Not everyone can take part all the time, with the exception of Doctor Bob of course.

[BBFG#]

Let nothing stop or delay its development progress. Especially if it's suggested by a representative of another company.

[FigBug]

I only released this synth on September 23rd, I really didn't expect it to get picked up for OSC so fast. I expected there to be a few in the queue. All my beta testers pretty much said it was fine or reported 1 or 2 small bugs. You all were the first to all really use it in anger, so your feedback has been invaluable in my improving the the synth. I wanted to iterate quickly while you were all still using the synth. That said it is pretty much 'feature complete' now. I have some UI tweaks to do, but no more audio engine changes for a while.

I hope my improvements have made the synth something you continue to use after the competition is over. Thank you for all your feedback.

[FigBug]

So, is there a way to achieve slide notes (portamento, glissando or whatever...) without the envelopes retriggering? I didn't find out how...

You need the latest version, then when you enable mono and port/gliss you will see a little arrow appear on the envelope to disable retrigger.

[] Peter:H []

Let nothing stop or delay its development progress. Especially if it's suggested by a representative of another company.

Huh? What!? Who you mean, bro?

Good opinion poll. thanks for the opnion about stop using newer versions than 1.0.15 in OSC.

Just to correct some reading between the lines and try to make clear what I said and not said. I never suggested that FigBugs stops impoving the synth. The idea was to restrict OSC usage to 1.0.15.
I myself asked for an improvement for better unisono and I'm glad FigBugs is such a fast and responsive dev. I benefit from the oscillator restart. I assisted in testing the SIMD improvement in testing the first version which actually changed sound ... I provided the respective patch to the dev to correct it ... I suggested further improvements, but I suggested them for a 1.1 version after OSC.
What stroke me is that FigBugs is so fast that about every day I open his github page I find a new version. Latest addition was new 3 new Distortion modes and reordering of fx, then Envelope-Restart ... if he keeps up the insane tempo we get a synth kind of capable as Vital by the end of the month. Think about a hypothetical scenario with a bunch of PRs for Phaser, Cross-Oscillator-Mod were all started in september and are ready to be merge only after you submitted your track...Then the synth at the beginning of the month is considerably different to later versions. Can you then call it *one* synth? There might even be different time constraints for different participants ... that's why the challenge streches over a month and should see one synth.
Anyways: That was just to explain things and clarify that there was nothing written between the lines. My track is finished go ahead people and have fun.

[BBFG#]

Wow, that sure clears up things!
Which company do you work for?

I just know that in art or science, that while perfection may be the enemy of progress, that it equally can be killed or stunted by people saying to stop or slow down.

When doing something and in the zone, pay little to no attention to those people.

[z.prime]

... I never suggested that FigBugs stops impoving the synth. The idea was to restrict OSC usage to 1.0.15.
I myself asked for an improvement for better unisono and I'm glad FigBugs is such a fast and responsive dev ...

And, did you use the improved unisono? I don't know for sure, but I'm going to assume so based on a listen to your track (which is quite nice, btw) and also your post:

Synth was updated to 1.0.11 ... thanks @FigBug for implementing my fr for "randomizing" unisono voices phase. Unison with "randomized" phase sounds way more pleasant to my ears! Thanks!
--> https://github.com/FigBug/Wavetable/releases/tag/1.0.11

So, to summarize:
1) you asked for an update to the synth
2) synth was updated during the OSC month
3) you used that update in your track

And now you're saying that people should _not_ use updates but instead stick with a specific version? Seems a bit hypocritical, don't you think?

[] Peter:H []

... I never suggested that FigBugs stops impoving the synth. The idea was to restrict OSC usage to 1.0.15.
I myself asked for an improvement for better unisono and I'm glad FigBugs is such a fast and responsive dev ...

And, did you use the improved unisono? I don't know for sure, but I'm going to assume so based on a listen to your track (which is quite nice, btw) and also your post:

Synth was updated to 1.0.11 ... thanks @FigBug for implementing my fr for "randomizing" unisono voices phase. Unison with "randomized" phase sounds way more pleasant to my ears! Thanks!
--> https://github.com/FigBug/Wavetable/releases/tag/1.0.11

So, to summarize:
1) you asked for an update to the synth
2) synth was updated during the OSC month
3) you used that update in your track

And now you're saying that people should _not_ use updates but instead stick with a specific version? Seems a bit hypocritical, don't you think?

Cool analysis ... from a position of looking back ... clever. And "No" to your question. It misses the point completely. If I'd always knew things from the beginning I'd be a rich man. So clever ... Sometimes making up onses (this type is for you) mind, starting to get a feeling thats growing stronger ... may be something clever people like you don't know these kind of makeing up ones mind processes. rofl. go discord.

[] Peter:H []

Wow, that sure clears up things!
Which company do you work for?

You seem to know, it was your claim. May be you can tell me and all the others.

[BBFG#]

Wow, that sure clears up things!
Which company do you work for?

You seem to know, it was your claim. May be you can tell me and all the others.

You're the one that took it personally. I think I remember, but honestly, it's been too long since I've communicated with you. And you aren't the only one I've had to just let go of.

[NeuKatalYst]

As someone formerly on the receiving end of drama in the past: everybody chill and let's just use whatever version of the synth, since it is within the rules that none of us make. Cool?