From the original SynthMaker forum (2004–2014), with its members’ names and dates.
bManic ·
Hi Jorge and fellow synthmaker enthusiasts,
I'm back from a very interesting week of accoustics studies. SynthMaker has made some leaps forward I see but one thing worries me. Splitting the program into a standard and advanced mode is probably not very wise to do as it doubles the amount of beta testing that needs to be done. Why not just organize the modules in a more sensible fashion? Maybe make a single Toolbox for newbies called "Basic modular synth components" which would contain ready made highlevel objects. Atleast in version 0.78p I couldn't see the inside of knobs in standard mode which is very bad indeed. Limiting options makes it harder to learn by seeing how the things really work.
IF the LP89 'code' switches modes immediately and quickly at any point in the creation process and it doesn't involve duble beta testing then I guess I'll give in and admit that the idea might be good but please Jorge, do reconsider.
Cheers!
bManic
PS. wow, new versions are flooding the site hehe.. get some sleep Jorge 😉
jorge ·
Hi bManic, good to have you back.
I value your opinion and I will consider reconsidering 🙂 but I'm not yet convinced.
I'll explain my way of thinking:
I think there are 3 main types of users interested in synthmaker
1) Users that want to use synthmaker to "make synths" in a modular way like reaktor etc.:
2) Users that want to learn some DSP stuff.
3) Users that want to create functionality that previously was only possible with a programming language.
I think 9 out of 10 users fit categories 1 or 2 and they get scared by the tons of low-level components.
The reason you dont like the idea of the standard mode is because you'd be the other 1 out of 10 that would
require the advanced mode most of the time.
The LP89 code does switch modes immediately and quickly at any point. I can easily change the way you swap
modes to a menu option, toolbar button, dialog box setting etc.
Please note that the low-level components just replace programming, they're used to define the internal
functionality of the application. What you'd normally call advanced features, like DSP stuff, digital filter design
etc would still be part of the standard version. Maybe a better name for Advanced mode would be Module-Developer mode.
Having the low-level components showing all the time would be like having an application showing the C++ code
behind it mixed with the high-level features you want to use, which would be fine if you're a c++ developer, you'd
learn with it, but not otherwise.
I'd like to point out here that synthmaker started from the very beginning as a visual-programming application
for general use ( I'm using it internally for other application not sound related ), there's a never ending
list of other interesting applications. I decided I had to target a specific area in order to get users interested enough
to try the different visual-hierarchical-modular way of working.
Atleast in version 0.78p I couldn't see the inside of knobs in standard mode which is very bad indeed.
You just had to type LP89 to get into advanced mode which allows you to go inside every module. Modules that
have the Lock component inside, are locked in Standard mode. It's up to the modules developer to choose wether to
allow the standard user to go inside the module.
Limiting options makes it harder to learn by seeing how the things really work.
I disagree at the moment. When I finish creating a new module, I dont really want to look at the internal schematic
anymore, I even forget how it works ( the same happens with writing code ), all I want is a nice properties dialog
box where you can edit the parameters you're interested in. In the latest version you can define your own dialog boxes
which avoids having to go inside the module looking for the parameters you want to change.
new versions are flooding the site hehe.. get some sleep Jorge
I'm actually doing just half days. The way synthmaker's framework works allows me to implement new functionality
quickly as each low-level component represents a small unit of code, quick to implement, test etc
Please keep sending feedback, I need to know if synthmaker and its VSTi and Standalone synths work for other people.
I will shape synthmaker according to the feedback I get.
bManic ·
Hi Jorge,
I've now played around with the newest version (0.78q as of today). Forget what I said earlier. Your idea works VERY WELL! =) I love the way it immediately goes into 'advanced' mode. I love the new properties thing, it's amazing! Actually, I had a blast yesterday creating some new sliders and learning what is possible and had NOT A SINGLE CRASH! This has gotta be the most stable version sofar (It used to crash atleast twice/hour).
Today I'll start building a basic synth but I need to find some working coefficients for a biquad filter as I do not have the time nor knowledge to do the calculations myself. I'll get back to ya with my usual bug reports. I'm now at school so it's easy to use the forum but from home I have such a bad connection that I usually just use a simple SSH terminal to school and can send simple emails only so I'll get back to you by email when I'm home. Feel free to quote and post anything and everything in my emails to the forum!!
Oh, btw. there is one bug I found yesterday and it's been there since v 078p: After disconnecting a wire from an object or module the 'mouse hover' in the schematics stops working untill you left-click on empty part of the schematic.
Cheers!
bManic
For other people, here's my main computer setup:
AMD Athlon XP 1700+
512mb of Kingston PC2700 RAM
VIA KT266 chipset, ABIT KR7 motherboard
Windows XP, SP1 and DirectX 9.0a
M-Audio Delta 2496 (Audiophile) running latest drivers
I use ASIO with a 512 sample buffer
VSTi host: FL Studio
jorge ·
Thanks a lot for your feedback.
The latest version has a new lowpass filter.
[old link]
I can implement a biquad if you want.
Wrote something here? To have a post removed or your name hidden, write to [email protected].