Jump to content

Production Grand - a 437.5GB VST


Recommended Posts

Of course waveforms vs. samples makes that big a difference.

"waveforms vs. samples" :mrgreen: Samples are stored waveforms, whereas synth presets are just stored values for the knobs/parameters. No waveforms at all, except in special cases like Zebra 2. Even those single periods in a "draw your wave" synth maybe have 100-200 frames in their construction, super tiny.

In most other cases (like most synths that aren't Zebra 2), a preset is just a text file storing the values of each parameter.

Link to post
Share on other sites
"waveforms vs. samples" :mrgreen: Samples are stored waveforms, whereas synth presets are just stored values for the knobs/parameters. No waveforms at all, except in special cases like Zebra 2. Even those single periods in a "draw your wave" synth maybe have 100-200 frames in their construction, super tiny.

In most other cases (like most synths that aren't Zebra 2), a preset is just a text file storing the values of each parameter.

Okay, I'll clarify. Basic waveforms vs. Samples. Squares, triangles, etc. 8)

Link to post
Share on other sites

This is a great sounding piano. There are so many versions of this that are all great sounding that there's no reason to bitch. If you're gonna be doing a full mix with all kinds of drums and basses and bagpipes then you can use a simpler piano and get away with it, but if you're doing a piano piece you definitely want something with this level of detail, and for that it's very worthwhile.

But yeah, I'm definitely picking up one of the lighter versions of this plugin sometime.

Link to post
Share on other sites
Okay, I'll clarify. Basic waveforms vs. Samples. Squares, triangles, etc. 8)

Again, synth presets are not stored waveforms. They're just stored parameter values. A synth preset is like a text file that reads:

"knob1: 50%

knob2: 32%

...

...

...

"

etc. (think of it like a save file in a game. It just stores the state of everything.) That's why these files are insanely small.

Synth presets don't store waveforms unless it's something like Zebra where it needs to save something that the user hand drew into the program. Otherwise, they're generated either through a wave table lookup or through functions. The waveforms in the wave tables are again not stored in a synth preset file, but independently stored for reuse. It's bad software design to generate new waveform tables for every new patch when they're all identical.

Edited by Neblix
Link to post
Share on other sites
Again, synth presets are not stored waveforms. They're just stored parameter values. A synth preset is like a text file that reads:

"knob1: 50%

knob2: 32%

...

...

...

"

etc. (think of it like a save file in a game. It just stores the state of everything.) That's why these files are insanely small.

Synth presets don't store waveforms unless it's something like Zebra where it needs to save something that the user hand drew into the program. Otherwise, they're generated either through a wave table lookup or through functions. The waveforms in the wave tables are again not stored in a synth preset file, but independently stored for reuse. It's bad software design to generate new waveform tables for every new patch when they're all identical.

Well, it's not like I actually know how preset saving works, dude. I don't design synths. Lighten up. Anyways... this topic's more about pianos. [/offtopic]

Edited by timaeus222
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...