One Synth Challenge #192: Six Sines by BaconPaul (johnkhf Wins!)

[ElVincente]

For what it's worth, I don't see any problem in current rules regarding updates during contest. I don't think more features allow for better quality generally, may be even quite the opposite, we're all here because huge restrictions are so liberating, from a creative point of view.
Beside that, you need to be brave to update things with an almost done 40 instances track.
And You still got time to update your track if the new features could make a real difference for you.

[Vospi]

I think a level playing field has some value which should be respected, shouldn't it?

The playing field already is level.

This.
I read this discussion with my eyebrows rolled up all the way. Damn.

[] Peter:H []

I think a level playing field has some value which should be respected, shouldn't it?

The playing field already is level.

Everyone gets the exact same amount of time with/without the new features. And music made on the older feature set doesn't degrade in any way due to the new feature set existing. If you've made a good song it's still a good song.

If there is a way to make your song better using linear FM (which there might be of course), you have the exact same amount of time to make that a reality as the next person does.


Besides, I don't think anyone would want bug fixes to be forbidden during a challenge. And drawing the line between a bug fix and a feature improvement can be tricky sometimes. I really don't think there's any cause for concern here.

I think it's a case of expectation management ... if it's clear that we start with an alpha and that the goal is to test it and bring it to an beta, that should be made clear from the beginning.
Even if a free synth is always a gift and people are grateful for dev time that went into it, other people would not even start to work on a submission, if they'd knew the setup from the start.

[FrogsInPants]

192 - Febnuary - Six Sines

Option 1: Correct the typo.
Option 2: No, "Febnuary" is actually an awesome name. Let's start calling it that.

[Vospi]

I vote for Ferbuany then. It sounds sophisticated. Pronounced fur-byan-ee.

[emikaela]

I think it's a case of expectation management ... if it's clear that we start with an alpha and that the goal is to test it and bring it to an beta, that should be made clear from the beginning.
Even if a free synth is always a gift and people are grateful for dev time that went into it, other people would not even start to work on a submission, if they'd knew the setup from the start.

we know that any synth may be updated at any time. i hope this clarifies things. at any given time, everyone will have access to the exact same features. didn't we have some similar cases in the past already?

i don't think there's any value in making the rules more complicated than they already are. it just sets people up to misunderstand.

[IV!]

You can solve this by "the rules", i.e. restrict the challenge to 1.0.5 and a bug fixing/branching strategy, i.e. bugs are fixed in 1.0.5 and new features go into 1.1 beta. Sure little more overhead to merge 1.0.5 fixes back to 1.1.
I think a level playing field has some value which should be respected, shouldn't it?

It sounds to me like a point where art becomes a sport, and we need rules so strict that we know who running before the starting gun shout and who actually broke the ribbon first...

What conditions are unequal for someone due to the fault of the developer or the organizer? All countries of the world have the same number of days in the calendar. If someone started and finished a track earlier due to circumstances, then it's the fault of the circumstances. I also know a few OSCers who haven't downloaded a synthesizer yet and haven't started the challenge, and who will have 2-3 days to finish it at most for one reason or another. Life is chaos and injustice, driven by hidden laws...

I think for someone who originally planned to spend several hours or days on the track, it would be a good strategy to do this towards the end of the month.

[briefcasemanx]

It's not that serious. If you're worried about extra features coming later, work on your entry later. If you don't have time later, oh well better luck next time, you're not entitled to anything that's free.

[neverbeeninariot]

I also know a few OSCers who haven't downloaded a synthesizer yet and haven't started the challenge, and who will have 2-3 days to finish it at most for one reason or another.

I downloaded Sines on day one, and now I can't stop updating it and I don't have any time left in the day to write music ! I demand a refund ! Or something !

[baconpaul]

One of the most requested features is an easy way to jog harmonics in the sources. I want to make the knob I'm using have quantized drags, but that's a lot of work.

What I've done for 1.1 (and is in the nightly) is add jog buttons. Screenshot attached.

Functionality is: If you click them without a modifier they go by "1", so clicking + from 1/5 gets you 1/4, 1/3, 1/2, 1, 2, 3, 4, 5... If you click them with cmd/ctrl they go by "octave" so starting from 1/5 clicking + you get 1/4, 1/2, 1, 2, 4, 8.... And they quantize. So if you are on ratio 2.714 and you click + you go to 3, and - goes to 2 (and cmd + goes to 4)

[doctorbob]

Perfect. Thank you. Jogs are a decent simple fix to the issue.

dB

[Hanz Meyzer]

This synth seems to be fabulous, very suitable for melodic stuff, too.

I think for editing, it would be nice, if there was a modifier-key + mouse-over shortcut for all the matrix knobs, so once hovered, you would hear the releated operators at that matrix position only. Like a quick solo preview. Then you don't have a hassle with on/off/mute buttons.

Synth seems to sound more precise at 96kHz...?

[baconpaul]

A solo is a good idea and is on the list. I was honestly just gonna put a little solo button below the power button in the mixer list.

As to 96hz, the synth runs at a fixed internal rate and then uses a downsampler. The default downsample (libsamplerate short sinc window) may do a better job going from the default internal rate to 96 than 48. You can play with a variety of oversampling options and internal engine rate options in the settings page. Some are purposefully quite bad.

[empphryio]

Here is my submission, though I'll keep up on the updates and perhaps give it another try.
https://soundcloud.com/anotherjaysherma ... al_sharing
OSC 192 Six Sines
Reaper 6.83
39ish instances
ReaLimit, ReEQ, A1Triggergate, A1StereoControl, Distortion (kiloheartz) and JS:Saturation (these two only for the thunder rumble), Raum, Supermassive Valhalla, ReaVerb, TDR Kotelnikov, OTT, Replika, Loudmax.

Thanks to Exponent for the snare.

LUFS-I=-11.1

Also here's another track I did (NOT my submission) that I thought worth sharing, showing how nice Six Sines can sound, that I'll refrain from throwing the kitchen sink at. Both of these were done using the 2/7/25 nightly. Very nice synth. Thank you Baconpaul.
https://soundcloud.com/anotherjaysherma ... al_sharing

[bzz]

This is my submission in the form of yet another cheesy smooth jazzy something

It is the first time I built up all the sounds myself from init. Big kudos to Taron for the great tutorial videos that gave me the courage!

Made in Cakewalk. 11 instances of Six Sines. Magic7, Deelay, OTT and W1 Limiter as the external FX.

https://soundcloud.com/petr-n-mec/bzz-sine-qua-non