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

[doctorbob]

... Don't want to break anybodies automation.

This was always a concern for any updates on synths we are using for these challenges. Good to know someone has their finger on the pulse.

dB

[Tj Shredder]

I experienced some oddity with presets that have MPE stored as switched on. When selecting such a preset it would go wild as if the range is set to something very small, switching off MPE and switching it on again would revert to expected behavior…
This was still on 1.0.9 but I didn’t see anything mentioned in the change logs…

[] Peter:H []

Seem like 1.0.13 is in the making ... I was given the chance to test it a minute ago and it's supposed to improve performance. Not bad, as I almost maxed out Bitwigs DSP load with my track.
By the way, I have updated the mix of my submssion ... viewtopic.php?p=8759533#p8759533

[FigBug]

1.0.14 is out now, fixed a pan bug I introduced in 1.0.13. CPU usage should be lower. SSE2 required on Intel, which should be pretty much every CPU these days.

[ZonderP]

@FigBug:
It's not (yet) listed under https://github.com/FigBug/Wavetable/releases though?
I see last commit refers to 1.0.14.

[GeneralQ]

Here is my Submission: https://soundcloud.com/generalq/generalq-table

This track was created for the KVR OSC Challenge.
Only the freeware synth "wavetable" has been used along with only free fx.
All sounds were created from init. No presets have been used. Only the included wavetables have been used.

wavetable 17
mequalizer 11
masaturator 8
mequalizer 8
mcompressor 8
realimit 8
khs reverb 3
mcharmverb 2
ozone imager 2
rbj highpass/lowpass filers (some js effect native to reaper basic highpass filter)
reacomp
readelay
mtremolo
span
khs limiter

DAW is reaper

[FigBug]

@FigBug:
It's not (yet) listed under https://github.com/FigBug/Wavetable/releases though?
I see last commit refers to 1.0.14.

Oops, forgot to tag the release. Should be there in 15 minutes.

[gethiox]

Here is my submission:
https://soundcloud.com/gethiox/tractor-overdrive

DAW: Bitwig

14x Wavetable
various stock plugins, valhalla supermassive, freeclip, kHs filter, kHs Trance Gate, kHs Transient Shaper

[] Peter:H []

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?

[NeuKatalYst]

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?

Technically I was already happy with whatever version we had when the month started (before the new wavetables were added); and each new version has only made it better, thanks to our feedback.

So I think it's cool that the synth is evolving while retaining compatibility with projects made with older versions. However, I see your point: if new features are added near the end of the month, it's impractical that anyone who would have already submitted by that point take advantage of them.

So I'll take an in-between stance: I'd hold off on updates and new stuff for the last 10-15 days of the month.

[SeBaer]

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

[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.

[emikaela]

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?

Technically I was already happy with whatever version we had when the month started (before the new wavetables were added); and each new version has only made it better, thanks to our feedback.

So I think it's cool that the synth is evolving while retaining compatibility with projects made with older versions. However, I see your point: if new features are added near the end of the month, it's impractical that anyone who would have already submitted by that point take advantage of them.

So I'll take an in-between stance: I'd hold off on updates and new stuff for the last 10-15 days of the month.

i don't really see a problem here, you know that the possibility of further updates is there when you choose to make a track early. same for everybody. it's a trade-off.

anyways, osc is typically in no position to make demands on synth developers, so we can't really create rules for them to follow. and a rule forcing participants to not use the latest version if it's released past a certain date just sets people up to fail and will be difficult to enforce.

[GeneralQ]

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.

[SeBaer]

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)