DSP Robotics Support

For those who may overlook - new version is here.

3.04 - bluebird

Update info:
http://www.dsprobotics.com/versions.html

And it looks, that we may have first bugs (or some sort of behavior change). If a bug - then probably reated with preset manager (or trigger / mouse events handling, I'm not sure yet), because everything works correctly with exe files, while it fails within loaded VST plugins. It worked fine in previous compiler, and I made no changes since then (I don't expect issues with "initial states" on prims after FS update, but this possibility is also to check). Anyway just a word of cautions. While CPU bug fix made me happy, mouse click bug introduction ruined my tomorrow.

//edit:

now I'm even more confused. It worked some time ago correctly, and now it is not working on nothing correctly (both, new and old compiler, even old exports don't work as they worked). What is going on? Can it be related to ruby library? Or did the syntax of preset files changed, and values different than "zero default" are messing with something? (I admit - I don't know which preset was exported/resaved under what compiler). Really need to check it.

How can we reproduce the bug Testers?
What is it doing at ur end?
I just compiled a plug and preset switching and mouse clicks are working.
Send a report and test case IMO,
let them know what OS and CPU u have

I'm trying to figure out what the nature of bug is, but you know - it's 5 a.m. here, and I haven't sleep yet...

Right now I was able to limit my thoughts to cross-grade of presets between compiler versions, mouse trigger interference (less probable) and some sort of value pass-through blocking (and this one might be very tricky; values from one setup go through, but S&H from other places - they don't until you don't push anything from the first setup; and I don't see anything, that could block it). As I said - need to run longer diagnostics to find out, because there are many multi-loops in green network. But first what I can check tomorrow, is to check the app in "pure state" on second computer, when is no update yet.

Hope you can find the problem and fix it mate-
did a double check and mouse and presets are working with a cursory look

Maybe it's an error within my app I overlooked, and now - after some pause and routine changes - I start to see it. Okay, time for some nap.

Okay, maybe time for nap will be later.

It appears, that issue I've encountered was on one hand false alarm, on the other - preset related, either bug or a behavior. From the past I remember, that any upgrades in my preset system (like adding new values) - were making all earlier presets "incompatible" to some degree with updated system. Sure - these old presets were loaded, but some sort of unpredictable value blocking was introduced too. I guess it may have to do with the ways of internal value handling within PM system.

Now - I used base preset created in earlier compliler, and then re-saved it with the new compiler, thus ended up with resaved preset only. It appears, that the problem I have - is only on that preset, thus - it looks - it's the case described above. Update info says something about preset system update, so it would explain it.