![]() if the tracks you generally play are way over that, you are probably a jukebox and rest of the discussion does not apply to you in the first place :] 100MB of memory each (considering length of 5 minutes in stereo at 44.1kHz sampling rate using 32 bits per sample - 32 because this is an intermediate, not final result, and we want to keep it that way until we let go of it ). Of course, generally each track should only take max. with all the other tracks currently being played. However the track, in its unpacked form, needs to fit into memory. Thankfully, this is such a simple operation that the only reason to even mention it is purely academical. Which means that you need a processor that is fast enough to crunch the numbers (while it is at the same time playing another track). This means that the song is decoded into memory while is loaded. Loading the track into memory the software generally loves to have the audio data in memory "as pure waveform" and "as directly random-accessible". Some are better at accessing it than others, sure, but this is usually not a bottleneck (even on ancient computers) if we're not talking about "tens of thousands of tracks" - which most DJs hopefully don't carry with them these days (as an idea, it does sounds interesting "I have all these tracks to play", but in practice I would limit my track collection to a few thousand at max, preferably much less). this is very small in terms of memory footprint and most software do keep all of this in memory all the time. In order to find a song, our software needs to have access to the track's metadata name, artist, bpm, key, duration, etc. To break it down, there are only a few things we should be concerned the speed at which we can find a particular track, load it into memory and use it (or disregard it and start the cycle all over). "what is needed?" - from the software's point of view. On my opinion, way too many DJs tend to think of this as an arms race :) Thankfully, the software we are running - while on a gig - tends to be relatively simple in terms of processing needs.Īs a bit of meta, let's consider.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |