how to add offset

[tester]

I'm trying to get the thing working, but it crashes.
This time I followed Exo's wiring (I think); also crashes.

[KG_is_back]

The custom wave read is bugy. I ran into multiple problems I couldn't fix:
1. when no mem is connected to mem to address prim, it simply outputs random values
there is no way, to detect whether the mem is valid or not, and when it's not, custom wave read crashes.
2. when address changes (new file is loaded) the address is passed through green and may arrive late - old address is already not valid = crash.

[KG_is_back]

Reworked it completely... This one should be as stable as possible

[tester]

Thanks, I wired it in the whole project and Initial tests are showing that it seems to work. Let's hope that I don't find another hole...

What is for this "-8" int?
Are there any limitations or typical problems to expect?
If wave files have tags (there seem to be a way of tagging) - will/may it cause some problems? (filesize)

[KG_is_back]

Thanks, I wired it in the whole project and Initial tests are showing that it seems to work. Let's hope that I don't find another hole...

What is for this "-8" int?
Are there any limitations or typical problems to expect?
If wave files have tags (there seem to be a way of tagging) - will/may it cause some problems? (filesize)

Filesize is in bytes and you need to limit the index to index of last value (we are speaking of indexing the values in ram where you refer to bytes - not typical indexing where 0 is first sample 1 is second etc.). in case of Stereo wave file, that is filsesize-8 (because value consists of two 4byte floats). it is because indexing starts from zero.

Typical problem might be occasional crashes, when changing the wave file during high CPU load. The address passes partially through green and may arrive late to the custom wave read, while the previous address is already invalid.
Another thing to test is loading the schematic with engaged sound card and with no wave loaded. I've observed that when no mem is connected the address and bytesize is still nonzero and apparently random, so there is no way to tell.


I do not know about the tagging, but when flowstone loads the wav it converts it to RAW PCM data in 32bit float (basically a big float array) so only the raw data survives - all information other than length, the actual values and number of channels cannot be extracted from the mem - you can only read them from the wave file primitive.

[tester]

Hey KG, I decided to buy a 1 year licence support for Flowstone for you (just paid, too late). So in a few days you should have it unlocked (I don't know, maybe you will get some e-mail on this as well) and you will have a breath for the next year. I'm sure, the next update(s) may bring something exciting too.

No obligations. There are people who help me in similar way from time to time, so why shouldn't I do the same?

Have fun, and I wish you luck with album release.

[tester]

And getting back to the topic, I just found one more issue, but I'm not sure yet whether it's related to waveplayer or the FS new release. To play/stop I use selectors; they stop counters, outputs and do the clearaudio to reset positions. After several (few) play/stop operations, exported exe hangs. I need to reexport older version with new release to see if this is FS thing. I don't know, maybe some sort of green delay will fix it.

//edit:

it looks that this is happening with the newer FS release. It isn't happening with older export on the same schematic.

[KG_is_back]

And getting back to the topic, I just found one more issue, but I'm not sure yet whether it's related to waveplayer or the FS new release. To play/stop I use selectors; they stop counters, outputs and do the clearaudio to reset positions. After several (few) play/stop operations, exported exe hangs. I need to reexport older version with new release to see if this is FS thing. I don't know, maybe some sort of green delay will fix it.//edit:it loks that this is happening with the newer FS release.

I've heard stories about selectors doing this kind of thing randomly in the new release. It might be related to the custom wave reading / timing but probably isn't...

Hey KG, I decided to buy a 1 year licence support for Flowstone for you (just paid, too late). So in a few days you should have it unlocked (I don't know, maybe you will get some e-mail on this as well) and you will have a breath for the next year. I'm sure, the next update(s) may bring something exciting too.

No obligations. There are people who help me in similar way from time to time, so why shouldn't I do the same?

Have fun, and I wish you luck with album release.

Man, I don't know what to say ... this really wasn't necessary... Thank you! If you ever need help with something (flowstone or non-flowstone related) just PM me

[tester]

I've heard stories about selectors doing this kind of thing randomly in the new release. It might be related to the custom wave reading / timing but probably isn't...

Selectors and clearaudio cause the same problem (probably audio reset is doing something), and it's very often, makes app exports practically useless. I checked on old wavereads, the same schematic, exported from two FS versions. Could not kill the old one. Now we need to hope for quick fix/release. Very quick.

Man, I don't know what to say ... this really wasn't necessary... Thank you! If you ever need help with something (flowstone or non-flowstone related) just PM me

Necessary maybe wasn't, but it was good to do it. Your "thank you" is enough.

[KG_is_back]

Selectors and clearaudio cause the same problem (probably audio reset is doing something), and it's very often, makes app exports practically useless. I checked on old wavereads, the same schematic, exported from two FS versions. Could not kill the old one. Now we need to hope for quick fix/release. Very quick.

I believe they are working on it - it was submitted. It has something to do with ASIO buffers from what I've heard.

Also we will need to do additional testing and development on this int based wave reading/indexing. I believe many people are interested in loading files longer than 6 minutes without these bugs related to Wave read prim and samplers that use it. Also "waveArray to pointers" prim would be very helpful too. I've already developed a hacky way to extract them and make custom WaveArray read prims (and custom "wavetableArray" oscillators), but it is way too buggy for any use other than experimental.

You know... to submit them to FSguru.