Cross AUDIO CACHE

[Blackbrook]

Did you tried to play with the audio cache in Cross ?

It is at maximum. In German there is a saying: Much helps much What is the best configuration for this?

[Blackbrook]

I don't know what is best, honestly mine is set to... ZERO !

Damn, that is the best solution! The gui freezes hardly half a second and no glitches or drop outs. Wohoooooo!

hemskoc my dear friend, if you are reading this I hope that you have not set your audio cache to zero, because this seems to solve some problems.

Thanks a lot support@vibes! Btw. what's your real name? Calling you support@vibes is so impersonal

Greetings,

Steve

[UncleVibes]

About setting to 0 the cache it's for me strange (for me only?) that it works better like that.
It smells like an unwanted action from the developers. Please explains again why 0 works better with small files... (less than 12 mn)
0 means full streaming for what I understand...

[UncleVibes]

Back to the audio cache, honestly with todays computers, I don't see why you would need to cache so small data.
I mean a mp3 converted in wave format on the fly in ram won't take a big amount of memory, so why bother to add an operation (ie caching) that will also add a write/read in the chain.

I will ask one of the dev an make a clear post about it.

[sylMV]

About audio caching.

If the audio cache amount of memory is big enough to hold the entire decoded track, Cross will decode and cache it as fast as possible so that you can reach any position in the file asap.
This operation of course require a lot of CPU power (making one core usage reach 100%) and often lasts a few seconds.

If the audio cache amount of memory is too small, Cross will directly stream from the file by decoding small chunks in a background task. Of course, less CPU usage peak at load, but a bit more CPU usage all along the playback and more risk to have "cache miss" issues (decoded audio unavailable when seeking far from the current position) resulting in small "blanks".

Audio cache at 0% is the extreme case for which all the files are streamed (like in Cross 1.2.5).

Moreover, keep in mind that track analysis is a separate task and then, if you load an unanalyzed file, Cross will need to decode it twice (one for caching or streaming, one for analysis) !

Hope it's a bit clearer now.

Of course you shouldn't have drop-out issues by a loading a file, and something seems to be messing up the CPU usage repartition...

[UncleVibes]

I'll stay with 0 because :
- I don't jump any where in a track before complete load
- I prefer to have a stable average cpu load @70% than 40% with peak to 100%

But it's my taste...

[polocorp]

typically a user with a lot of locators in various parts of his songs will need to load tracks in the cache memory for immediate access to these locations...

a user who plays tracks from the beginning (house mix) doesn't need this feature... especially if he has a very powerful computer. he should have absolutely no GUI micro freezing in this case...