Login / Register  0 items | $0.00 New
martin_l
KVRian
 
934 posts since 27 Jun, 2009, from UK

Postby martin_l; Thu Jan 12, 2017 1:53 pm Re: Why do people still code their synths with SynthEdit or Flowstone...

My early versions of PG-8X were made with SynthEdit, but most of the DSP was already done in a custom module which was written in C++/assembler. When I then went over to the WDL-OL version, I could keep most of the DSP code as it was, and simply replaced the SE framework by C++ code for the GUI. In my case, even the SynthEdit version already had a hand-coded Voice allocator, which however just distributed the notes over different MIDI channels and then each voice had it's own SE Midi2CV.
gridsleep
KVRer
 
4 posts since 15 May, 2016

Postby gridsleep; Fri Jan 20, 2017 2:09 pm Re: Why do people still code their synths with SynthEdit or Flowstone...

That's the most passive-aggressive marketing I have read in a long time. It's almost like your annoying brother-in-law trying to sell you some stocks in which he absolutely has no vested interest, not in the least. (Referring to the original post.)
chk071
KVRAF
 
14332 posts since 10 Apr, 2010, from Germany

Postby chk071; Fri Jan 20, 2017 2:11 pm Re: Why do people still code their synths with SynthEdit or Flowstone...

Are you nuts?
xoxos
Mr Entertainment
 
12013 posts since 29 Apr, 2002, from i might peeramid

Postby xoxos; Sat Jan 21, 2017 8:22 am Re: Why do people still code their synths with SynthEdit or Flowstone...

gridsleep wrote:That's the most passive-aggressive marketing I have read in a long time.

read more posts at kvr, this is what we do, it's who we are. this is where kvr posts come from. great handle :) most people don't talk about what we do or who we are. because, they're the people who "gridsleep. it's not just a name." watch out for the black magic.
you come and go, you come and go. amitabha xoxos.net free vst. neither a follower nor a leader be
tagore "where roads are made i lose my way"
where there is certainty, consideration is absent.
User avatar
Jace-BeOS
KVRAF
 
4061 posts since 7 Jan, 2005, from Corporate States of America

Postby Jace-BeOS; Sat Jan 21, 2017 11:12 am Re: Why do people still code their synths with SynthEdit or Flowstone...

gridsleep wrote:That's the most passive-aggressive marketing I have read in a long time. It's almost like your annoying brother-in-law trying to sell you some stocks in which he absolutely has no vested interest, not in the least. (Referring to the original post.)


??????? :?: :?: :?: :?:
- dysamoria.com
my music @ SoundCloud
chk071
KVRAF
 
14332 posts since 10 Apr, 2010, from Germany

Postby chk071; Sat Jan 21, 2017 11:16 am Re: Why do people still code their synths with SynthEdit or Flowstone...

Jace-BeOS wrote:
gridsleep wrote:That's the most passive-aggressive marketing I have read in a long time. It's almost like your annoying brother-in-law trying to sell you some stocks in which he absolutely has no vested interest, not in the least. (Referring to the original post.)


??????? :?: :?: :?: :?:

Exactly what was on my mind when i read the post. :P
User avatar
Nielzie
KVRAF
 
8597 posts since 28 May, 2005, from Netherlands

Postby Nielzie; Sat Jan 21, 2017 11:39 am Re: Why do people still code their synths with SynthEdit or Flowstone...

I love Synth Edit. It's probably my best spent money in the software domain. One GIANT Modular. Many many many free modules still floating around on the net to download, try and combine (win32-bit version obviously) and all the freedom to make my own GUI on my creations with jKnobman, with again many many many free knobs floating around the net. And then being able to export your own creations into vst instruments or vst effects is very satisfying. "NielzieSynth" and "NielzieDelay" are getting much use here, and only here :hihi:

Very recommendable for studying/learning all kinds of synthesis too.

Ohhh and I don't code at all :oops:
None are so hopeless enslaved as KVRians with GAS.
phobik
KVRer
 
16 posts since 26 Sep, 2007

Postby phobik; Fri Mar 10, 2017 7:02 am Re: Why do people still code their synths with SynthEdit or Flowstone...

Can someone explain if dsp-concepts Audio Weaver and JUCE software relate/integrate with this and how?
User avatar
whyterabbyt
Beware the Quoth
 
25335 posts since 3 Sep, 2001, from R'lyeh Oceanic Amusement Park and Funfair

Postby whyterabbyt; Sat Mar 11, 2017 3:07 am Re: Why do people still code their synths with SynthEdit or Flowstone...

phobik wrote:Can someone explain if dsp-concepts Audio Weaver and JUCE software relate/integrate with this and how?


which 'this', precisely?

JUCE is a framework, somewhat like WDL-OL for the subset of it that covers plugins, but much larger in scope, ie a full application framework.

As for Audio Weaver, I dont quite understand why you'd ask; its targetted at embedded systems, so to even be aware of it surely you'd have to have heard of it in that context, which is a completely different context from that of anything discussed here (ie 'audio plugins for DAWs running on mainstream consumer operating systems).

But, for completion, it seems to be a prewritten audio-processing engine aimed at embedded systems, and a RAD application allowing you to configure that engine's behaviour for particular tasks. In that respect, its 'like' Synthedit style RAD tools, but even a cursory look at the manufacturer's webpage would have told you that. :shrug:
"The bearer of this signature is a genuine and authorised pope."
phobik
KVRer
 
16 posts since 26 Sep, 2007

Postby phobik; Sat Mar 11, 2017 4:31 am Re: Why do people still code their synths with SynthEdit or Flowstone...

whyterabbyt wrote:
phobik wrote:Can someone explain if dsp-concepts Audio Weaver and JUCE software relate/integrate with this and how?


which 'this', precisely?

JUCE is a framework, somewhat like WDL-OL for the subset of it that covers plugins, but much larger in scope, ie a full application framework.

As for Audio Weaver, I dont quite understand why you'd ask; its targetted at embedded systems, so to even be aware of it surely you'd have to have heard of it in that context, which is a completely different context from that of anything discussed here (ie 'audio plugins for DAWs running on mainstream consumer operating systems).

But, for completion, it seems to be a prewritten audio-processing engine aimed at embedded systems, and a RAD application allowing you to configure that engine's behaviour for particular tasks. In that respect, its 'like' Synthedit style RAD tools, but even a cursory look at the manufacturer's webpage would have told you that. :shrug:


I'm trying to understand if these RAD tools allow to develop DSP code, in a platform agnostic way, i.e. generate the libraries with one and maybe import them into another/c++ project. Is my thinking too convoluted?
kx77free
KVRian
 
602 posts since 19 Jul, 2005, from Paris

Postby kx77free; Sun Mar 12, 2017 9:11 am Re: Why do people still code their synths with SynthEdit or Flowstone...

Because SE is a modular environment like the real synthesizers, it is cheap, it uses low CPU, it is updated even if the main SE x64 stills beta, it uses the synthesis grammar, its connections work in volts. The first reason it's we can develop own SEM in C++, its can manage in intern several thousand of connections and each modules can go to sleep when we want to decrease the cpu, etc...

You can see my last x64 products here :
http://kx77free.free.fr

Check the CPU use and the quality sounding... I tested the WDL-OL, it's great but I prefer to stay on SE because my projects are very big and I prefer work on the audio DSP code to improve the quality sounding. SE has a community of musicians, not really professional devs. I do not want to be a professional dev even if I code my SEM, SE is a good compromise.
Examigan
KVRAF
 
4194 posts since 15 Sep, 2005, from East Coast of the USA

Postby Examigan; Wed Jan 10, 2018 4:34 am Re: Why do people still code their synths with SynthEdit or Flowstone...

whyterabbyt wrote:The original version of Sylenth was done this way, I believe.


Yes I think it was too. Also OP-X Pro II was (I think it still is.. (?)) and later on they got a 64-bit version working which I use today.
Previous

Moderator: Moderators (Main)

Return to Modular Synthesis