DSP Robotics Support

To see bug....
new schematic...
bring PM and horizontal slider from toolbox..
set no of presets to more than one...
make a few presets...
now...
select prests and notice that it works..
now move the slider...change preset and then change back again...
notice that the PM now does not work..

Can Someone please confirm or explain..
Thanks

Hmmm - related?... http://www.dsprobotics.com/support/viewtopic.php?f=2&t=2674&p=13641#p13641
Can't seem to reproduce your slider one though - there have been a few folks seeming to struggle with Ruby and the PM lately though.

At work.ATM
think it was there in 3.04. .will check later...

Well, another point to mention:
Using the visual virtual midi keyboard with "hover over" (mouse dragging) feature also causes crushes. When I play with it in my synth as it loaded in FS (even without changing a preset at all!), the audio crushes after few seconds. Don't know if its a part of the same problem or just another one...

Just did a quick test(same as above) using the FS knobs...same issue..
Preset manager is not retaining saved preset if the user changes value,
and then changes preset index.
@nubeat7...
your "multifunctional" slider has same issue as the FS Knobs....
Wow...gonna be long night....

billv wrote:Preset manager is not retaining saved preset if the user changes value

Ok..so I'm the only one seeing this bug that dosn't exist.
Trog/Exo...feel free to delete my posts.
Thanks.

billv wrote:Ok..so I'm the only one seeing this bug that dosn't exist.

Let's wait and see - you know FS well enough for us to trust what you're telling us. And kortezzz is having preset change problems that don't appear elsewhere, too - I checked myself, his synths were fine in v3.0.4.
So something fishy is gong on - I suggest we keep our eyes open for similar weird events, and maybe we'll start to see a pattern emerge.

Maybe some additional retrig (you know, these backward trigger stories for bed Trog told when he was young) somewhere would help?

tester wrote:backward trigger stories for bed Trog

could be...i seemed to stop thinking about backward triggers using ruby a lot..

trogluddite wrote:for us to trust what you're telling us

no need for trust here Trog...thats why I gave easy example to test,
so it could be quickly clarified and sorted.

trog, you wrote that you couldn't produce an error....
ATM I'm finding this a little disturbing... here's why...I'll explain the bug again...

Make 3 prests and save them...
For the rest of the test, you will not use the save button....
using the selector, flick through presets and verify..ok presets are still there intact..
Now go through the prests and change values randomly...
Check prests via selector....they are not the original 3 saved values.
For me this behavior is wrong.
...i just don't get it...

billv wrote:

tester wrote:backward trigger stories for bed Trog

could be...i seemed to stop thinking about backward triggers using ruby a lot..

trogluddite wrote:for us to trust what you're telling us

no need for trust here Trog...thats why I gave easy example to test,
so it could be quickly clarified and sorted.

trog, you wrote that you couldn't produce an error....
ATM I'm finding this a little disturbing... here's why...I'll explain the bug again...

Make 3 prests and save them...
For the rest of the test, you will not use the save button....
using the selector, flick through presets and verify..ok presets are still there intact..
Now go through the prests and change values randomly...
Check prests via selector....they are not the original 3 saved values.
For me this behavior is wrong.
...i just don't get it...

Hey billv, In the top right corner of the properties panel is a little tick box called "Lock", tick this. That will lock the presets from being edited without saving.

I think lock should be on by default because I don't think anyone would be expecting that behaviour. (Maybe it used to be?)

Also "Lock" is a bit ambiguous here, how is anyone supposed to know what they are locking?