I understand the ideas but I'm thinking I don't want to go too far away from sinus waves so the concept falls. But I'm trying the roundiness atm. I could on one hand just make another logo from the start with shapes doing all kinds of crazy shnizzle with S's twisting all over the place. I'll continue and see what happens.bjporter wrote:I like it already, but I concur sir, that this is a worthy idea to explore.z.prime wrote:Agree about the yellow one being my favorite, too. Yellow roxx0rzWould love to see a more rounded version of it, and ideally with the S in the middle somehow twisted a bit to be more like an S? Would. Be. Amazing.
One-Synth-Challenge: General discussion thread
-
- KVRist
- 112 posts since 22 Apr, 2015
-
- KVRist
- 112 posts since 22 Apr, 2015
Here's a round version with some tests below. Looks ok I think, but kind of lost it's edge
.. attitude I mean. Maybe that could be added with somethine else. I'll continue on other logos tomorrow maybe. Now I has gots to sleep.


- KVRAF
- 2228 posts since 29 Sep, 2011
Right, maybe somewhere in between. To me the original looks more like a triangle wave than a sine, the new one looks some better but funky because the waves aren't the same. Definitely the white outline is money.
-
- KVRAF
- 2725 posts since 19 Dec, 2010 from North America
I freakin love the top right one. I think the sharpness actually attracts ones eye.Meakaale wrote:Here's a round version with some tests below. Looks ok I think, but kind of lost it's edge.. attitude I mean. Maybe that could be added with somethine else. I'll continue on other logos tomorrow maybe. Now I has gots to sleep.
One Synth Challenge: https://sites.google.com/site/kvrosc/about
- KVRian
- 1125 posts since 30 Oct, 2013 from Scarborough
I too would vote top right, it jumps right off the page at you! 
https://rjsemper.wixsite.com/website
One Synth Challenge - https://sites.google.com/site/kvrosc/about
One Synth Challenge - https://sites.google.com/site/kvrosc/about
-
- KVRist
- 112 posts since 22 Apr, 2015
Another concept
The idea here is the Olympics rings to refeer to OSC being a challenge/competition and waves to give it a sound/synth vibe. The big circles are O and C tied together by the most important part, the S.

Also a "bonus" pic with some playingaround ideas of the other logo. Got some very minor adjustments to the waves. Non of the "additions" to this I think are worth continuing on.

The idea here is the Olympics rings to refeer to OSC being a challenge/competition and waves to give it a sound/synth vibe. The big circles are O and C tied together by the most important part, the S.

Also a "bonus" pic with some playingaround ideas of the other logo. Got some very minor adjustments to the waves. Non of the "additions" to this I think are worth continuing on.

Last edited by Meakaale on Sun Aug 21, 2016 10:12 pm, edited 1 time in total.
-
- KVRist
- 112 posts since 22 Apr, 2015
I've double checked with a matlab sine wave and the latest version is tracing it pretty much dead on(seen in bonus pic). Not hughly different from the other one I think though.z.prime wrote:Right, maybe somewhere in between. To me the original looks more like a triangle wave than a sine, the new one looks some better but funky because the waves aren't the same. Definitely the white outline is money.
I've thought about this, trying to make it more playful as maybe can be seen in the "bonus" pic. The "one synth challenge" text could be optional depending on where it's used.Hanz Meyzer wrote:Maybe some emoticons on the logo, like:
or lemmings or something. I mean very small. Like a google-doodle. And the "one synth challenge" removed, it already is on the right?
-
- KVRAF
- 2725 posts since 19 Dec, 2010 from North America
Top left, and the piano one (and the taller one similar) =Meakaale wrote:Another concept
One Synth Challenge: https://sites.google.com/site/kvrosc/about
- KVRAF
- 2110 posts since 5 Oct, 2015 from Swedish / Living in Hong Kong
I never used Wusik V8 and I don't have it. Right now it's given away free thru their Facebook links. I just wonder if this is suitable for OSC perhaps? ..or perhaps it has been used already Before?
Win 10 -64bit, CPU i7-7700K, 32Gb, Focusrite 2i2, FL-studio 20, Studio One 4, Reason 10
- KVRAF
- 2228 posts since 29 Sep, 2011
It's heavily sample-based, which would preclude it from OSC, though it does have some synthesis capabilities.ATN69 wrote:I never used Wusik V8 and I don't have it. Right now it's given away free thru their Facebook links. I just wonder if this is suitable for OSC perhaps? ..or perhaps it has been used already Before?
- KVRAF
- 2110 posts since 5 Oct, 2015 from Swedish / Living in Hong Kong
I see, I didn't know that was the case. By the look of the GUI I got the feeling it was some kind of a modular thing. I never used it so I hardly know what it is, or if it is good or bad even. Well it was just a thought since they give it awayz.prime wrote:It's heavily sample-based, which would preclude it from OSC, though it does have some synthesis capabilities.ATN69 wrote:I never used Wusik V8 and I don't have it. Right now it's given away free thru their Facebook links. I just wonder if this is suitable for OSC perhaps? ..or perhaps it has been used already Before?
Win 10 -64bit, CPU i7-7700K, 32Gb, Focusrite 2i2, FL-studio 20, Studio One 4, Reason 10
- KVRAF
- 2228 posts since 29 Sep, 2011
Right, yeah. Some good sounds. But I've always found it extremely buggy, which is a shame. We've done some other synths that have sample capabilities like Alchemy (R.I.P. in Apple's arms, screwing over the customers who actually bought it, thanks, bastards!!!)... with the stipulation you can't use the sample stuff. It tends to get annoying when you load presets because you have no idea if it's going to load a sample or not (and most of them did)...ATN69 wrote:I see, I didn't know that was the case. By the look of the GUI I got the feeling it was some kind of a modular thing. I never used it so I hardly know what it is, or if it is good or bad even. Well it was just a thought since they give it awayz.prime wrote:It's heavily sample-based, which would preclude it from OSC, though it does have some synthesis capabilities.ATN69 wrote:I never used Wusik V8 and I don't have it. Right now it's given away free thru their Facebook links. I just wonder if this is suitable for OSC perhaps? ..or perhaps it has been used already Before?
-
- KVRist
- 352 posts since 16 Mar, 2013 from Perú
A bit offTopic but maybe someone will find it usefull 
I just found this https://www.packtpub.com/packt/offers/free-learning , Packpub is giving for free the ebook "FL Studio Cookbook", the offer is valid just for today.
I just found this https://www.packtpub.com/packt/offers/free-learning , Packpub is giving for free the ebook "FL Studio Cookbook", the offer is valid just for today.
- KVRist
- 335 posts since 12 Aug, 2016
Hello
I would like a clarification on the rules, specifically this bit:
Say I have a 70 measure frozen bass track and I want to simply change 4 parameters on measures 57 and 58.
On a frozen track I have to risk crashing the DAW on my mixing session when unfreezing the track, add the parameter envelopes to the track, add points before and after the two measures, then try to write in the automation to change the 4 parameters, then cross my fingers and hope it doesn't crash when I re-freeze the track.
Whereas if I was only dealing with stems in my mixing session I could simply split the bass stem, delete the 2 measures, go to the PC where I'm making stems(which is less of a potential disaster if it crashes), make my parameter changes in the VSTi UI, record a new 2 measure stem and shoot it across the LAN and drop the 2 measures right in my mixing session with zero crash risk to my mixing session. No fiddling with automation envelopes either.
So exact same result sound wise but a lot less stress on my mixing PC. But because I touched the original bass stem, it is against the rules
And if I had to 'show my work' it would be a project of many chopped up stems so would be DQed.
Another example, I have 10 frozen tracks. I decide I want to add a 5 measure bridge in the middle. I would have to unfreeze(risking crash), cut and move the remainder of the track 5 measures, refreeze and hope it doesn't crash. And repeat this process 9 more times. I guarantee that if I attempted that in this months OSC it would have crashed at least 6 times before I got all 10 tracks slid over and the project saved.
But if it was all stems I could make my split and grab all ten tracks at once go and slide them over. Zero crashes. But the stems are not then in exact original form, so illegal.
So what is the reasoning behind this rule?
To me it just seems like a penalty for those with less beefy PCs. Like requiring the use of one big person to move your fridge where 2 or 3 smaller people might be able to get the job done just fine instead.
PS: Why is this thread not a sticky?
I would like a clarification on the rules, specifically this bit:
I don't really understand the difference between a frozen track and a stem other than stems are easier for me to work around with a lower end PC.No use of samples, sample libraries or live sounds (like voice, guitar etc allowed). However, for convenience or CPU saving,
synth bouncing are allowed but only where the EXACT same result could have been achieved using
the original synth. This means that for example pitching and reversing is not allowed. Sampling for example
a bass drum in order to get a consistent sound is not allowed either. Samplers used must be host samplers or freeware and easily available.
More Clarification: Audio must not be touched at all once it leaves the DAW (aka after bouncing a track or a stem). For example: One cannot master the audio in another software or service. Also, If you need more performance / CPU a workaround is to freeze all the tracks.
Say I have a 70 measure frozen bass track and I want to simply change 4 parameters on measures 57 and 58.
On a frozen track I have to risk crashing the DAW on my mixing session when unfreezing the track, add the parameter envelopes to the track, add points before and after the two measures, then try to write in the automation to change the 4 parameters, then cross my fingers and hope it doesn't crash when I re-freeze the track.
Whereas if I was only dealing with stems in my mixing session I could simply split the bass stem, delete the 2 measures, go to the PC where I'm making stems(which is less of a potential disaster if it crashes), make my parameter changes in the VSTi UI, record a new 2 measure stem and shoot it across the LAN and drop the 2 measures right in my mixing session with zero crash risk to my mixing session. No fiddling with automation envelopes either.
So exact same result sound wise but a lot less stress on my mixing PC. But because I touched the original bass stem, it is against the rules
Another example, I have 10 frozen tracks. I decide I want to add a 5 measure bridge in the middle. I would have to unfreeze(risking crash), cut and move the remainder of the track 5 measures, refreeze and hope it doesn't crash. And repeat this process 9 more times. I guarantee that if I attempted that in this months OSC it would have crashed at least 6 times before I got all 10 tracks slid over and the project saved.
But if it was all stems I could make my split and grab all ten tracks at once go and slide them over. Zero crashes. But the stems are not then in exact original form, so illegal.
So what is the reasoning behind this rule?
To me it just seems like a penalty for those with less beefy PCs. Like requiring the use of one big person to move your fridge where 2 or 3 smaller people might be able to get the job done just fine instead.
PS: Why is this thread not a sticky?
Win10 x64, Reaper 6.XX x64, i5-3330, 8gb ram, GTX-970, UC-33, Panorama P4, Wharfedale Diamond 8.2 and JVC HA-RX700
- KVRAF
- 2228 posts since 29 Sep, 2011
There are a couple reasons you're not supposed to work with rendered audio:
One main issue is that many synths have free-running oscillators or inconsistent sound, if you could render to audio, say you don't like how one particular phrase came out, you could re-render just that one phrase and circumvent the annoying behavior of the synth. I don't think there have been a lot lately that seem to fall into this category, but there have been some in the past. Especially when it comes to things like percussion.
A secondary issue is reproducibility. If someone checked your track and it was a bunch of waveforms that had been moved around or whatever and no longer match up to the source MIDI or automation or whatever else, it would become practically impossible to determine that the provided project was really where the sounds came from, that the whole track as it stands is something the synth can make...
By freezing a track, you can simply unfreeze them all and re-render the track and see what it sounds like, it should be essentially the same...
At least, I suspect these are some of the reasons.
One main issue is that many synths have free-running oscillators or inconsistent sound, if you could render to audio, say you don't like how one particular phrase came out, you could re-render just that one phrase and circumvent the annoying behavior of the synth. I don't think there have been a lot lately that seem to fall into this category, but there have been some in the past. Especially when it comes to things like percussion.
A secondary issue is reproducibility. If someone checked your track and it was a bunch of waveforms that had been moved around or whatever and no longer match up to the source MIDI or automation or whatever else, it would become practically impossible to determine that the provided project was really where the sounds came from, that the whole track as it stands is something the synth can make...
By freezing a track, you can simply unfreeze them all and re-render the track and see what it sounds like, it should be essentially the same...
At least, I suspect these are some of the reasons.
