Yet another VCS3 clone (free)

Modular Synth design and releases (Reaktor, SynthEdit, Tassman, etc.)
Post Reply New Topic
RELATED
PRODUCTS

Post

Hskovlund wrote:Another thing: There is remarks in this thread about EMS emu of Synthi A and I guess you know it. Whether it is more authentic or not I could not say but yours do sound much better and much more like hardware in my hear, the oscs has a fine clean sound with no annoying digital sharpness, crunchiness (aliasing?) and glitches. Processing them in the matrix makes them alive and kicking besides from sounding even better.

Ehhh....the EMS remarks was your own post I see! So you know it of course. Forget about it. Too overpriced to make it worth talk about and it doesn't even sound better as I've stated.

I forgot one question in my former post: Will you be able to do something about the tempo range when and if you apply sync functions to the OSCs?


Best Regards
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."

Post

Hskovlund wrote: I forgot one question in my former post: Will you be able to do something about the tempo range when and if you apply sync functions to the OSCs?
The tempo range? Like a sync to host bpm or is it the frequency range of OSC3 you're talking about? I'm not sure I understand you correctly. The frequency range is more or less like the original, with app. 1.5 octave between each number on the outer dial on the frequency knob, while the middle one can fine tune it (perhaps not with 1 cent acuracy, but you can actually get pretty close and a good OSC is always slightly out of tune :hihi:).

Anyway, the phase slide is propably not something I can patent - there's a pin on the standard SE OSC called phase mod and by attaching a slider to that I can change the phase between 0 and 180 degrees ;-)
For the masses: Each pin in the matrix can also (of course) work as a 180 degree phase change by clicking it twice (turns red). If set to millisecond range, the delay module can also do some phaser trick (though that would be frequency dependent and not very precise).

Well... I have to come up with some nice looking knobs and switches for the phase/sync and then the next version will be out. I'll make the package as a zip with 4 files in: A synth/VSTi + an FX/VST edition in both large and small size each. It'll be up to the end users to put the prefered edition in their VST folder then.

cheers

Post

The tempo range? Like a sync to host bpm or is it the frequency range of OSC3 you're talking about? I'm not sure I understand you correctly. The frequency range is more or less like the original, with app. 1.5 octave between each number on the outer dial on the frequency knob, while the middle one can fine tune it (perhaps not with 1 cent acuracy, but you can actually get pretty close and a good OSC is always slightly out of tune :hihi:.
I mean when I use OSC 1 as a modulator the frequency settings controls the tempo of the modulation phase, but is seems restricted in range, thus I can make it modulate in tempi from medium to very fast but no real slow (corresponding to very deep inaudible sub-notes, when used as an OSC). Thus, if the frequency knobs could have a tempo setting-function when used as a modulator which is independent of its tuning function when using the OSC as a soundsource, that would do it! I'm not an expert in the technical terms of this, so sorry if I am hard to catch on this one.

Well a sync to host BMP would indeed makes things a lot easier, but I am trying to be as faithful to your concept of manual syncing as possible and for that I need 1) the phase retriggering and 2) a broad scope of tempo possibilities

The FX version sounds nice to.

I'm going to stick to this thread on a daily basis of course. :hyper:

Well off we go again...back to the beastie :borg:
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."

Post

Hi NC
Got some patches for you. Its compiled in a Zip file. I have PM my mail-adresse. There will be more but this is to show you my gratitude as promised.

Now its all bass stuff and besides from "syntbass 1" and "synthbass 2" it is sequenses which has to be triggered by your favorite bass note (stacatto).
Its basic stuff at this point of course, I need to dig deeper to develope the SEQs further. Head for the "Techno Antique 1 + 2" and "Old Shuffle". Both of them demonstrates what this machine among other things is going to be to me and thus all the sync-talk.

Best regards


PS: When delay is applied, you will have to wait for it to fall into phase. Now thats another sync-issue :roll:
Last edited by Locus M on Sun Mar 02, 2008 8:52 am, edited 1 time in total.
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."

Post

You really need to make this a VSTi rather than a VST. Or is there a VSTi version I missed somewhere? I want to use it as a Synth not as an insert or send effect. The VCS was a Synthesizer you know? :lol: Nice Work though! :tu: 8)

Post

BFunKu wrote:You really need to make this a VSTi rather than a VST. Or is there a VSTi version I missed somewhere? I want to use it as a Synth not as an insert or send effect. The VCS was a Synthesizer you know? :lol: Nice Work though! :tu: 8)
The so-called "cubase edition" posted a while ago (on one of the previous pages of this thread) is the VSTi version... but I didn't write that clearly.

The next days are pretty busy for me, so it will take a couple of days before the next version will hit the forum. That one will include:
  • - Option to sync-to-note-on and phase-mod the 3 OSC (as requested by Hskovlund)
  • - A large and small version GUI (but no possibility to transfer patches between them... sorry. Perhaps at another time)
  • - A VSTi and a VST version: Putney.dll and PutneyFX.dll (the FX version will in some hosts also work perfect as a synth)
  • - The patches made by Hskovlund (thanks :-))

Post

ninecows wrote:
Hskovlund wrote: I forgot one question in my former post: Will you be able to do something about the tempo range when and if you apply sync functions to the OSCs?
The tempo range? Like a sync to host bpm or is it the frequency range of OSC3 you're talking about? I'm not sure I understand you correctly. The frequency range is more or less like the original, with app. 1.5 octave between each number on the outer dial on the frequency knob, while the middle one can fine tune it (perhaps not with 1 cent acuracy, but you can actually get pretty close and a good OSC is always slightly out of tune :hihi:).
Hi NineCows
Forget all about this, though I confused you your answer gave me a hint: If I want sloooow phases I can just use OSC 3 as a modulator instead of OSC 1, the first obviously has a broader range (for reasons unknown to me however).

Best Regards
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."

Post

Hskovlund wrote: Hi NineCows
Forget all about this, though I confused you your answer gave me a hint: If I want sloooow phases I can just use OSC 3 as a modulator instead of OSC 1, the first obviously has a broader range (for reasons unknown to me however).
Yes... OSC3 should be called a LFO in more modern synth-terms, but I wanted to stay true to the original design an label it as an OSC (just like the filter can also be used as a sine-wave OSC, by turning response to max).

OSC2 and OSC3 are basicly identical except for their frequency range: OSC2 ranges from 0.6 Hz to ~16.8 kHz, while OSC3 ranges from 0.015 Hz to 500 Hz.
So OSC3 is a LFO, but with the extra option to go into a part of the audible range (so you can make some really crazy phasing and ringmod by letting OSC3 control the freq of the other OSC's). Thats something I find very clever about the VCS3/Synthi :-)

Post

Hi. A quick word about the patchbay graphics.

I'm actually finding it quite tricky to patch modules together on the pin board because, even though the board is very large, my line of sight is not being guided to find the correct pin hole. It's quite easy for the eye to become confused as it traces all those holes to find the correct connection.

If you look at the original synth (and the EMS and Reaktor clones), you'll see that the patchbay routes are subdivided into dark coloured sectors. Apart from anything else, this actually guides the eye when trying to patch a pin.

I would suggest that ninecows looks into this. It's a simple little aspect of the original design, but it works, and it's there for a reason.

Great plugin. Really looking forward to its continued development!

Cheers

BTW Is the reverb working? I'm having some difficulty patching it.

Post

ninecows wrote:And by the way... Imagine that the EMS making the hardware synths is also trying to sell a 350€ VSTi edition :-o (this one: http://www.kvraudio.com/get/1186.html)

It's propably more pro (but its also made in SE) and is hopefully a better emulation, but still... 350€ for a SE synth?!? I wonder how many they've sold so far :lol:

(nothing bad about SE though - its a fantastic program and makes it so easy for nearly everyone to create exactly the synth they want, so while I'm at it: Thanks a lot Jeff :D )

I will keep my Putney free - don't want all the hazzle with setting up a webshop, having to pay taxes etc, just for squeezing you guys for a few bucks.

Just please credit me if you include the synth (the actual dll-file) in something else or want to do some reverse engineering on it. And dont make money re-selling it.

(and that's the EULA for The Putney - take it and learn MS :P )

Cheers!
Please contact the Micro$oft Learning Department at Phone number:

1 800 000 0000

fax:

1 900 000 0000

Post

Hitchcock Bell wrote:Hi. A quick word about the patchbay graphics.

I'm actually finding it quite tricky to patch modules together on the pin board because, even though the board is very large, my line of sight is not being guided to find the correct pin hole. It's quite easy for the eye to become confused as it traces all those holes to find the correct connection.

If you look at the original synth (and the EMS and Reaktor clones), you'll see that the patchbay routes are subdivided into dark coloured sectors. Apart from anything else, this actually guides the eye when trying to patch a pin.

I would suggest that ninecows looks into this. It's a simple little aspect of the original design, but it works, and it's there for a reason.

Great plugin. Really looking forward to its continued development!

Cheers

BTW Is the reverb working? I'm having some difficulty patching it.
Hi Hitchcock Bell.

I know NineCows is busy, so I will take the liberty to answer your post as good as I can. I understand your suggestion, the matrix is a bitch to be tamed for sure and I use the small version so sometimes my nose touch the screen to find the right pins. However I can live with that because most of the time I feel like kissing this machine anyway. Well, NC seems very open to such suggestions so there is hope I guess.

Now the reverb: It works fine but everything is relative in this matrix so how you patch it really depends on other settings. However if you are up for a basic synth structure in which the envelope pins are the only ones which is patched to the output 1 + 2 (first vertical row)like in the basic synth patch you will have to activate the reverb by 1) the pins in output 1 + 2 (vertical row) and 2) then move to the env signal (horizontal row) and pin in to the reverb (horizontal row). Now to make sure go for the long reverb, the short one can fool you to believe there is no reverb at all. Same principle can be applied to the delay.

I would have showed you with a picture but I don't know how to add pictures in a post, can not find any function to do that...can you tell me how to do that?

Best Regards
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."

Post

Hitchcock Bell wrote:Hi. A quick word about the patchbay graphics.

I'm actually finding it quite tricky to patch modules together on the pin board because, even though the board is very large, my line of sight is not being guided to find the correct pin hole. It's quite easy for the eye to become confused as it traces all those holes to find the correct connection.

If you look at the original synth (and the EMS and Reaktor clones), you'll see that the patchbay routes are subdivided into dark coloured sectors. Apart from anything else, this actually guides the eye when trying to patch a pin.

I would suggest that ninecows looks into this. It's a simple little aspect of the original design, but it works, and it's there for a reason.

Great plugin. Really looking forward to its continued development!

Cheers

BTW Is the reverb working? I'm having some difficulty patching it.
I think that I actually included the guidelines in the small GUI version, but I'll include it in the big one as well - it takes 30 seconds, so why not ;-)

And I think the reverb is working... At least it did in my latest build. But I'll have a look at it.

Try to set up the synth like this:

Image

You should get a short, dry noise on the left channel and its reverb on the right.

And by the way: Images are posted by writing the link to the image (so you'll have to upload it to a server somewhere) between image-tags (click the IMG-button above)[/img]
Last edited by ninecows on Wed Mar 05, 2008 2:39 pm, edited 1 time in total.

Post

ninecows wrote: I think that I actually included the guidelines in the small GUI version, but I'll include it in the big one as well - it takes 30 seconds, so why not ;-

And I think the reverb is working... At least it did in my latest build. But I'll have a look at it.
You did include the guidlines in the small version (though I still have to kiss the screen sometimes but nevermind that) and the reverb is working fine in the big version.

Best Regards
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."

Post

Thanks guys. I'll try the reverb again with the advice in mind. :)

Post

It looks nice.
Its very buggy in FL though (i've tried both the standard "effect" version and the cubase vsti) as well as an enormous CPU hog.

There are a few synthi e-mus out there. I know one i had success with (Synthia by elemusic) although i don't know if its a true emu of the hardware or just a copy of the work flow.

Either way, it didn't give me nearly have as many headaches as this thing has so far.



It is such a pretty interface though :)


Anyway, I did try it in energyXTCore with some limited success (i'll actually chalk most of that up to the fact that i don't know/like XTs interface) however some notes

1 - CPU seems huge, and it spikes a lot.
2 - Stuck notes!
3 - Not only do i get stuck notes that refuse to go away, i actually get a lagged and stuttering delay between pressing play, and the actual playing back of whats in the piano roll. This is for both versions tested.

It ends up being pretty much unusable which is a real shame because I know I have a lot of fun with Ele's version, and I'd like to give yours a real shot (i did test it of course and it sounds pretty neat.)

Anyway, hope some of this helps. You've got a real gem in your hands if you can iron it out :)

Post Reply

Return to “Modular Synthesis”