DSP Robotics Support

tester wrote:I usually try to keep some sort of triggering order and green delays, to not overload things.

Yes i have to quote. In FS/SM you should always find a work-around for things. That is.
Trigger load on start and prevent loops, multi-triggering etc etc.

Maybe it's visual, but still - it's programming. If you work around some simple rules to follow, then you don't have too many problems. I noticed, that green timer delays (set 10 to 500ms, depending where) are useful to separate certain types of events (streams, memory, access) happening in FS. It saved my projects many times, and thus - I can't confirm instabilities.

tester wrote:Maybe it's visual, but still - it's programming. If you work around some simple rules to follow, then you don't have too many problems. I noticed, that green timer delays (set 10 to 500ms, depending where) are useful to separate certain types of events (streams, memory, access) happening in FS. It saved my projects many times, and thus - I can't confirm instabilities.

Well done. I also use timers to trigger events according to logics.
But i still belive that waveloader could be better. Loading files on FS is too much ram/cpu requesting and can be a problem.
I would like to make a dj software but it may be complicated.. Imagine to trigger external conversion than load wav files during the play...

deleted

It loads instantly also here a 64mb wave with an i7 3770k @ 3.5ghz, 8gb ram (dual channel 1600mhz), normal hdd.

But after loading a wave, try to coy and paste the waveplayer! you'll see how the memory leaks happens...
If i do that i get flowstone moving slowly, rendering slowly like a superbig schematic.

So that's the point. A single wave doesn't create any problem, but twice yes.

Are u using stock waveplayer tiffy?

deleted

Check if there are some old primitives no more available and replace them.
I made a video.
http://www59.zippyshare.com/v/80143643/file.html

When i open a single 64mb wave it instantly load. But when i copy paste the waveplayer with the wave loaded it takes longer and starts to render slow flowstone.
So when i move modules it's kind glitching, and i have also problem when i try to multi-select with mouse.
At the end when i remove both 2 additional waveloaders it returns to the normal.

In the past, with Core duo (centrino) and synthmaker, was also worst. When you release something in the market you migth have to be sure that it's working for all with different hardwares...

I didn't test but... Are we sure that if you make a kind of a dj software the schematic won't stop play during the load??
Imagine if it stops when you are djiing and loading next track..

I have not tried this, but there is a primitive called "Closing". Can it trigger wave removal from the schematic before the schematic is closed?

Of course.
I tried to test loading a wave during the play and it crashes..

Trigger stop playback, timer delay, trigger load next file?