From the original SynthMaker forum (2004–2014), with its members’ names and dates.
trogluddite ·
Here's an animated pseudo waterfall plot for frequency graphs etc.
Feed the display module with a float array of your choice, and then send ticks to animate!
Not very tidy at the moment (at least needs a decent properties panel) - I'll try to update later with something a little more versatile.
The frequency correlator is just part of an experiment from the Pitch Detector thread - it shows 4 octaves of semitones starting at the base frequency (no proper scaling) - one of SMs FFT primitives would work equally well, though be careful how many points you plot (the layered graph modules will suck CPU if the graphs are very big).
smokeysteve22 ·
I can never seem to open your .osm files?
Always give me an - schematic type not found error.
trogluddite ·
Hmm, there's been a lot of downloads of this - and no other problems reported.
The only possible causes I can think of are...
-Your version of SM is too old, or installation corrupted.
- .osm file type not associated with SM. You should be able to fix this by using 'Open with...'
- The ASIO primitives in the schematic causing a problem (my soundcard has lots of I/O) - here's a version using DirectSound; maybe you'll have better luck with that...
Let me know if the DS schematic fixes the problem - if so, I will try to upload DS versions in the future.
lesobrod ·
Great, works fine!
Just one question:
- How do you push such complex schematics into so small-sized files?!
Pure schematic should feel some pain... 😈
and one suggest:
- Kinda of "Normalization" for graph plot (fitting peaks to window) will be useful IMO
trogluddite ·
lesobrod wrote: - How do you push such complex schematics into so small-sized files?!
Pure schematic should feel some pain...
He he, I'm always a great believer in taking the path of least resistance.
Actually, the principle here is not so different from some of your recent chaotic oscillator examples - using iteration to make something complex out of a simple one-layer graphic.
The Bitmap Create at its heart receives a translated and faded copy of the previous frame, with the new graph data overlaid on top - constructing a new bitmap which is displayed as the current frame, then passed back around for the next iteration.
I've made a few different designs using this principle, you can find some more examples in these threads...
Light Trails and Psychedelic Screensavers
Goniometer
Analogue style multichannel oscilloscope
cyto ·
lesobrod wrote: - How do you push such complex schematics into so small-sized files?!
Also, regarding file size, remember that the primitives, modules, connections, etc. take up very little memory. It's when you start to add a bunch of "strip" knobs, backgrounds, and other embedded images that the files really start to grow in size.
-cyto
trogluddite ·
Also worth noting that SM schematics are always compressed when saving (I'm sure someone mentioned once which compression system is used, but I can't remember now).
However, when you export as .exe or .dll, the file size will get a lot bigger. They are not exported as 'compiled' binaries; but as a 'bundle' of the schematic plus a run-time version of the SM environment.
This allows the plugin to be optimised according to the CPU's SSE support (kinda useless now that just about all PCs have SSE2), and it also includes the engine for handling green triggers, and allows dynamic re-compiling (e.g. switching off unused stream components when there are routing changes).
But it does mean that .exe's and .dll's are much bigger than comparable plugins that are fully compiled from, say, the VST SDK libraries in C++. It also means that SM plugins are (in principle at least) likely to be more easily 'reverse engineered' by hackers.
smokeysteve22 ·
trogluddite wrote: Hmm, there's been a lot of downloads of this - and no other problems reported.
The only possible causes I can think of are...
-Your version of SM is too old, or installation corrupted.
- .osm file type not associated with SM. You should be able to fix this by using 'Open with...'
- The ASIO primitives in the schematic causing a problem (my soundcard has lots of I/O) - here's a version using DirectSound; maybe you'll have better luck with that...
Let me know if the DS schematic fixes the problem - if so, I will try to upload DS versions in the future.
Thanks for reupload still didn't work though, im going to reinstall but before i do, is there anyway to save 'toolbox' because i don't really want to have to save all again?
trogluddite ·
I would try an 'over the top' repair installation first - could just be that there's a single default module file or something that needs popping back into place.
If you want to back up your modules, you can find them in your 'Application Data' folder. I only know Windows XP, but you should be able to find the correct folder by using the 'System Folders' primitive within SM - Just connect a string box to the 'AppData' output. Within the folder shown there, you should find a sub-folder "SynthMaker/Modules" that holds all your custom module definitions (.hom files).
One other (maybe silly) question - are you trying to load SM schematics into FlowStone? If so, you will need to change the file extension to .fsm, to make FlowStone read the file.
McBarGig ·
Hey Trog can I use this?
infuzion ·
McBarGig wrote: Hey Trog can I use this?
Only if you promise to wear his avatar on the front of a T-Shirt to all the trade shows!
trogluddite ·
infuzion wrote:
McBarGig wrote: Hey Trog can I use this?
Only if you promise to wear his avatar on the front of a T-Shirt to all the trade shows!
He he, now there's an idea - the (very exclusive and expensive) T-shirts all come with one of those RFID 'anti-shoplifting' tags attached and a free web-cam. The plugin then refuses to run unless the tag is detected, and the web-cam can see that you are wearing the T-shirt. (dammit, guess I'll have to get FlowStone after all!).
@MBG...
Yes, I'm always happy for folks to use (and abuse) the stuff I post on the forum - I have nothing to lose as I don't do plugins commercially - and every download is a little bit of karma to offset the debt I accrued when I was a naughty teenager who used 'cloned' ZX Spectrum tapes!
McBarGig ·
Thanks Trog. I'm trying to find some cool way of graphicall representing note sustain so that users can post a graphic of the sustain profiles of their heads. This is about as close as I've seen that would work.. I don't know at this point though because I need to put a lot more thought into what exactly I want to explain graphically, and determine if its useful to the user or not...
Either way great work!
About the shirt and NAMM..🙂 We have only been represented there once, and that was by Acuostica when we supplied them with a Virtual amp for Mixcraft 5. Personally, I think NAMM is a cluster F%^K and probably not very useful for us.... haha
CoreStyler ·
really cool
tester ·
There seems to be inaccuracy error when changing the base frequency. Sine spike which has constant amplitude - sometimes is fine, sometimes is disappears. How to add horizontal (frequency) scaling, to get more octaves per view? How to remove animation and make it just flat spectrum view?
trogluddite ·
tester wrote: There seems to be inaccuracy error when changing the base frequency. Sine spike which has constant amplitude - sometimes is fine, sometimes is disappears
Yups, seems you have spotted a bug. I had a quick play, and I'm pretty sure it's a denormal problem in the code - I hadn't put my usual denorm trap into the smoothing filters. My little netbook's CPU went nuts when I turned the mic' off, which is a pretty sure sign!
The correlation oscillators are also a rather old variation on the 'iterative' theme - so I should check those too, maybe they are not liking sudden shifts in frequency.
The other stuff is pretty simple...
The animation is all of the Bitmap related parts of the GUI (mostly the bottom row of modules) -they can be deleted without disturbing the function of the 'foreground' graph. In the "Fill Graph" part, the 'Clipped' graphs could prabably also go - they are there just for a splash of colour, but a monochromatic graph will be more efficient.
To add extra range, you can simply add more "Octave Correlator" sub-modules inside the correlator - simply append the extra output arrays, and chain the 'Index' connectors. The chain of 'Index' connections essentially re-numbers each new module so that it generates the correct parameters for the next octave up.
I you go inside the 'Parameters' part of a correlator, you'll see that the co-efficients are generated by lots of identical synchronised modules. They take an Index input (count up from zero), and output the centre frequency in Hertz - but because they are synce'd, you only need to edit one of them to change the function if you prefer another scaling.
Whether or not it is an accurate or efficient way of measuring frequency is another point entirely. It was conceived more as a demonstration of GUI programming - the frequency detector came about because at the time I wanted to learn more about using complex numbers in DSP. It was never something I had a particular use for myself.
It is essentially a bank of dicrete single frequency-detectors (albeit with mono4 'parallelism') - so more bands will always mean adding more modules. For only a few frequencies it is reasonably efficient, but for wide bandwidth measurement, I would expect FFT based plotting to be much more efficient (assuming it is only for display purposes, that is).
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker