From the original SynthMaker forum (2004–2014), with its members’ names and dates.
tektoog ·
Hey, This bugs me (I think it's a bug...)
If you go thru the presets backward it goes fine, but as soon as you go forward, the data is not written to the array... It seems the preset data is sent before the number of point has been set... I tried S&H, selectors to fix that but no can do... It does the same with Ver 1.1.7... Any idea....???
Mo ·
The wave size can't be adjustable with preset.
tektoog ·
Really? why not? any particular explanation? That really bugs me in numerous projects.... I recall the same thing happens with the StepLFO if you change the number of steps...it can't be changed dynamically either... it seems obvious to be able to do that...
Mo ·
It would be the same as change the parameter amount. It will mess up presets and compatibility for VST's.
tektoog ·
OK I see... Thanks for your answer... but that still really bugs me !!!
Mo ·
Well, you can use the resample primitive to change the array size. Just keep an array size for the array preset primitive.
DigitalWhiteByte ·
workaround here VST Parameter Array - Max Length Variable
tektoog ·
Haha !! Thx DWB... you've been there before... You save me quite some work it looks like.... I have to study this now... Thx again !
infuzion ·
Seems all the workaround does is find the largest array size. You can avoid all that extra work by simply hard-coding the max array size yourself.
The only other way around this is by having one huge single array that you bite off the pieces you need as you need them.
tektoog ·
infuzion wrote: You can avoid all that extra work by simply hard-coding the max array size yourself.
If you do that and set it up to a big number of samples, then all your presets will have that big array to manage and all the presets will be as slow as hell... And if you wanna do a random on the array then the whole array will be randomized, bringing in the visible area, some data that are out of the selected chunk of array... I've been on that for a while, and my logic brings me each time to a feedback loop that just crashes SM 100% I think DWB's module is a good workaround...but I still have problem to implement it in the WaveDraw OSC... The problem comes in when I want to restore the hand drawn data
DigitalWhiteByte wrote: workaround here
I've tried 2 different methods; the first one consisted in taking your module and inserting it instead of the WaveDraw preset parameter In the second one I just replaced the wave display by the WaveDraw... But I couldn't make it to work.... I've been struggling all night long... and each time my logic brings me to insert the FLoat Array Draw output to a float array switch before your module... which create a feedback loop that crashes SM.... Do you think you could show in an OSM how to implement your module within the WaveDraw OSC? Please, that woud be nice...
Mo ·
tektoog wrote: If you do that and set it up to a big number of samples, then all your presets will have that big array to manage and all the presets will be as slow as hell...
I don't find for example an 1024 array on 32 presets slow.
tektoog ·
I don't know what kind of harware you've got Mo, but the slower the cpu is and the smaller the ram is, the worse it gets... Drawing a line of 2048 samples with an old P3 1Ghz with 512mb of ram becomes really slughish and glitchy... almost unusable... The number of presets is not relevant here. what matters really (for me at least), is that if you have a preset with a large array, and which can be slow, it's better if the following (or previous) preset acts faster, so as a user you can select which array size suits your system better... Also, if you sync the WaveDraw OSC to a host, different array sizes can match different loop lengths like 4bars, 8bars etc...
Mo ·
tektoog wrote: Drawing a line of 2048 samples with an old P3 1Ghz with 512mb of ram becomes really slughish and glitchy...
Yes 2048 is slow drawing. If you keep the array on 1024 or 512 and everything would work. Also optimized the load and save array module to not contain big array text file, which would slow down loading.
tektoog wrote: Also, if you sync the WaveDraw OSC to a host, different array sizes can match different loop lengths like 4bars, 8bars etc...
Maybe multiplying the frequency instead?
tektoog ·
Mo wrote: If you keep the array on 1024 or 512
Yeah...I've been living with it until now... but it would be really nice to get this working... As I said before, many of my projects would benefit from this...
Mo wrote: Maybe multiplying the frequency instead?
But a combination of both would offer a lot more flexibility for sound design...
I'll get more into DWB's workaround whick works very well in his example...I just need to implement it correctly in the WaveDraw OSC and the dynamic hand drawing ... Must work....
DigitalWhiteByte ·
tektoog wrote: I'll get more into DWB's workaround whick works very well in his example...I just need to implement it correctly in the WaveDraw OSC and the dynamic hand drawing ... Must work....
I reduced and rearranged some things. Here is an example of how to apply it to draw wave.
tektoog ·
Brilliant !!!
tektoog ·
Hey DWB, There is a little something that bothers me in your system... I would expect that when changing the array length, I would see some kind of screen redrawing...actually nothing happens..it's only when you click on the screen that something happens...and what happens is that either the array resets itself (with the changes I made) or the already drawn shape has to be altered (damaged I should say) by a click on screen which inevitably add some unwanted points to the shape... As a end user, this looks like a bug... I tried many tricks to get it to work this way but was unsuccessful... It looks to me that it will be a bit more complicated than to add a few triggers in order to function this way... Do you think you could have a look on this please ???
I've made a small video showing what I'm talking about. There is also my own module, which works the way I described above. You'll see also that after changing presets in your module, the array length written doesn't match the array actually used.This shoud also be fixed IMO.
Sorry it has to be RARed to be posted.
infuzion ·
OSM?
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker