The overall per-project sample pool memory allows for 6 minutes of monophonic 16-bit, 44.1 kHz sample files. However, Play can work with different sample playback rates, so you can reduce the required memory of a sample by reducing its sample rate. A sample played back at half the sample rate will use half the Pool memory. Conversely, doubling the sample’s rate will use twice the Pool memory. Because Play can use multiple different playback rates, your sample pool capacity may vary.
Really trying to max out the Play for an upcoming project so I am curious, since Play converts stereo samples to mono when importing, does it sum the stereo channels and write a new WAV file at half the size? Or would a stereo sample stay the same size once imported?
I’ll have to double check but I believe it would take the right channel only and be about 1/2 the size.
Okay I was wrong, it takes the average between the two signals, and only uses 1/2 the stereo memory.
1 Like
Perfect thank you for looking into that Mitch, that’s totally ideal behavior for the device and eases my mind.
1 Like
This is why some form of a ‘Play’ companion app would be handy, when using different sample types, mono/stereo, 44, 48, 32khz, making sample packs to use on Play, especially when trying to use max memory can be tedious, I don’t know how many times I’ve jacked the micro sd card in and out of the play to either delete or convert different samples just to fit into a pack I’ve created.
It would be a hell of a lot easier to drag the samples into a ‘Play sample pack creator app’ which details the memory used before transferring to the card, that way you know your not going to run into the dreaded ‘insufficient memory’ message when importing a sample pack.
4 Likes
I know this is an old thread, and I apologize for the bump.
I really like the Play and had the exact same thought : a companion app to do exactly that:
- organize samples by folders (with the default ones, and up to 20)
- sum to mono stereo samples, change bitrate, sample rate
- rename samples (things like “Sample pack - snares - snare - c# - 01.wav”, and also get rid of possible funky characters that might not be accepted on the machine)
- vizualize things to know what is taking a lot of space.
- with a maximum pool size of around 32MB (31.752MB exactly, which is a bit weird to me, but that’s 6 min of mono 16bit CD quality audio, I wonder if they might have rounded the value up).
- Something else ?
I started to work on a small app to do just that. I am still super early in the process, and things will probably take some time since I do that in my spare time, around work, family etc.
Wondering if other people might be interesting by something like this, what kind of features they would like etc. I am building the thing with Electron/Node in JS so it technically should run on PC/Mac/Windows.
Here are some early screenshots. For now you cannot do much, just drag/drop audio files and folders, create/delete folders and empty them.
4 Likes
This looks awesome. I would definitely be interested.
This is exactly what I need. Great work, please go on.
This would be ace for creating sample packs, nice one mate, definitely interested in this, I like to create my own sample packs and this would be cool for for organising and creating these.