Hi DSPC team,
I noticed in the FFS wrapper guide documentation that it mentions the input must be a system RAM address when it is on the target.
Therefore, I would like to ask about:
if this is the case, does it mean that the WAV file to be played must be pre-loaded into RAM?
If my WAV file is large(like more than 10Mb), or if the RAM size is limited, and the speed of loading the WAV file into RAM is slow, are there any alternative methods to allow the WAV file to be read and played simultaneously?
Additionally, does the FFS wrapper support input from a flash address?
Thanks
Charlie
1:45pm
Hi Charlie,
FFS Wave Players are to be used when you have sufficient RAM to copy the WAV files from the Flash (where they are stored when the power is off). The WAV data is copied into RAM at system initialization time, rather than every time the WAV file is played. Flash Wave Players do not load the WAV file into RAM. Rather, they read the WAV file every time from Flash when the WAV file is played. As a result, they consume additional CPU overhead since the Flash access is slower than RAM. Let me know if this explanation is sufficient.
Thanks,
Gary
3:59am
Hi Gary,
Thanks your explanation, it's very clear for me.
One more question is that what's the difference between the module WaveLoopPlayerRAM and WaveLoopPlayerFFS?
I know that the WaveLoopPlayerFFS should work with the FFS wrapper to get the wav address.
For the WaveLoopPlayerRAM how can this module to get the wav? Or where should the wav placed in RAM?