I'm willing to hear arguments against this, but if it all boils down to "accessing a .wav file is
quicker than accessing an mp3", and other performance related explanations: I've heard it all
before. What I want, is the option of accessing the mp3 directly, so as to avoid the decoding
cache route for scenarios like DJing. As far as full tunes go, there is a limit to how many clips
you'll be running at any given time, so why the unnecessary detour? This limitation, in addition
to Traktor's seemingly more accurate analysis is my main reason for looking to Traktor for this
use.
Warp directly from MP3
Re: Warp directly from MP3
BIG +1
Jared-F
MacBook Pro 17 Unibody 2.6 4GB Ram 500GB 7200RPM
Mac Pro 2x2.8Quad
MOTU Ultra Lite
UC33E, AKAI MPD24.
Novation Remote SL
2xKorg NanoPad
Korg NanoKontrol
AKAI APC40
SL3 Scratch Live 1.9.1
Traktor Scratch Pro 1.21
MacBook Pro 17 Unibody 2.6 4GB Ram 500GB 7200RPM
Mac Pro 2x2.8Quad
MOTU Ultra Lite
UC33E, AKAI MPD24.
Novation Remote SL
2xKorg NanoPad
Korg NanoKontrol
AKAI APC40
SL3 Scratch Live 1.9.1
Traktor Scratch Pro 1.21
-
davepermen
- Posts: 2198
- Joined: Thu Mar 05, 2009 3:38 pm
- Location: Switzerland
- Contact:
Re: Warp directly from MP3
big +1. having an ssd that has cost me 700$ or so, half of it used for the decoding cache means i have payed around 350$ just for ableton not being able to decode mp3s on the fly (and, as the mp3 would fit better into ram, and we wouldn't need hdd/ssd accesses, then, it would perform better than wav-from-disk anyways..)
http://davepermen.net my tiny webpage, including link to bandcamp.