From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
I assume that when a primitive is updated, the old versions are automatically updated (eg when an existing primitive has new features added, not an new primitive is made... like when Timeinfo is superceeded by Tempo...). However, an error was made it seems when Wave Table & Wave Table Read had >256 wavetable capabilities added; new primitives were made with new IDs, so the older wavedraws that have those don't get the new capabilities, causing issues to those who don't always dig deep into every module they use (like...everyone!).
example:
wavemakers!
Workaround: Hand replace all the Wave Table & Wave Table Read.
Acrobat ·
No primitive is automatically updated in SM, they're just marked with that RED & WHITE striping all around.
I recently found even some X (stream multiply) treated that way!!!!!! 😀
oddson ·
Acrobat wrote: No primitive is automatically updated in SM, they're just marked with that RED & WHITE striping all around.
I recently found even some X (stream multiply) treated that way!!!!!! 😀
That's not strictly true. It used to be that primitives were regularly updated and I suspect they still are when it clearly won't break existing schematics. I think the stripping is used when the engine retains the old behaviour for backwards compatibility.
infuzion ·
oddson wrote:
Acrobat wrote: No primitive is automatically updated in SM, they're just marked with that RED & WHITE striping all around.
I recently found even some X (stream multiply) treated that way!!!!!! 😀
That's not strictly true. It used to be that primitives were regularly updated and I suspect they still are when it clearly won't break existing schematics. I think the stripping is used when the engine retains the old behaviour for backwards compatibility.
Yes, infact I think primitives are simply updated with new features without being outdated more often than superseded.
Perhaps those red "multiply" are poly-only or mono-only, since that is how SM worked back in like 0.9.5? Gray "Stream" for audio is a new-ish feature, compared to SM itself, & the older poly-only or mono-only were inferior... though come to think of it I don't know why they both weren't upgraded to stream as well?
Acrobat ·
oddson wrote: I think the stripping is used when the engine retains the old behaviour for backwards compatibility.
OK, so I think there's some ambiguity between pure and simple "mantainance" and a real "update" with new functionalities.
infuzion wrote: though come to think of it I don't know why they both weren't upgraded to stream as well?
That's my guess too.. 😕
I always supposed that if I am not adviced with the stripping, the way the primitive works can either be changed internally but the results have to be the same and if it has new ins or outs, it should have a whole different name.
But maybe I'm just supposing... 🙂
infuzion ·
Acrobat wrote: I always supposed that if I am not adviced with the stripping, the way the primitive works can either be changed internally but the results have to be the same and if it has new ins or outs, it should have a whole different name.
Most of the time, if there are new ins/outs added, but the rest of the primitive is more or less the same, the original primitive is simply & quietly upgraded. The X/Y Drag Acculiminate are perfect examples; since I joined SM, they had about 3 ins/outs added (& one changed a few times), but if you open a 3 year old or a 1 month old schematic, they all have the same Drag Xes etc...
infuzion ·
bump
Wavetable Osc not responding to note 62 and 64
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker