1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE
NOTICE:

Our Traktor Pro Public Beta is available again in our new online community. Join us if you want to try new features.

MORE INFO

MP3s wont play!

Discussion in 'Technical Issues (Archive)' started by gatdec1, Jul 6, 2009.

Thread Status:
Not open for further replies.
  1. gatdec1

    gatdec1 New Member

    Messages:
    1
    Hi
    Im just after buying and successfully downloaded traktor duo but my mp3s which were all bought from beatport will not play, this message keeps coming up: warning, the track - - - - - - could not be played due to a missing or corrupt file, can anyone help?
     
  2. ricko

    ricko Forum Member

    Messages:
    65
    yeah i've got the same problem. I've tried renaming them, reinstalled traktor, they're not set to read only, no drm protection, and they're all mp3s and they still work in windows meadia player. but the worst thing is they used to play in traktor! I just emailed NI tech support, you should do the same if you can't get it sorted. i'll let you know when i hear back.
     
  3. Rasmuffin

    Rasmuffin NI Product Owner

    Messages:
    1,584
    Try running the MP3's through this:
    http://mp3val.sourceforge.net/
    Beatport has many header errors in their tracks. I don't find Traktor as picky as iTunes with errors, but it's worth a try.
     
  4. ricko

    ricko Forum Member

    Messages:
    65
    any hints on how to get that software to work?
     
  5. rainerh

    rainerh Well-Known Member

    Messages:
    2,465
    the message you get seems to be a strange bug. most of the times the second try to load the file will succeed. Any changes to the mp3 file itself won't solve the issue, because it is not track dependent.
     
  6. Rasmuffin

    Rasmuffin NI Product Owner

    Messages:
    1,584
    I'll count myself lucky for not coming across that bug.

    No chance the tracks were moved since import and there is an "!" next to them?

    Although it seems it's not the fix for your problem it can be a good idea to get rid of header errors in your collection. Just download the program, drag the files into it, hit the magnifying glass icon to analyse and then the sprocket icon to fix them. This cured the problem I had with iTunes not liking many Beatport downloads, but I haven't noticed Traktor having an issue with the same errors.
     
  7. rainerh

    rainerh Well-Known Member

    Messages:
    2,465
    It's not the problem that the file has been moved, so no !.
    It happens here mostly when I load a track directly from the Explorer node (i.e. not from the Collection node). As far as I know there are a lot of users having the same issue.
     
  8. ricko

    ricko Forum Member

    Messages:
    65
    yeah i've come accross that problem as well but this one there is no such luck loading it a second time. I've got a bunch of tracks that just no longer play. They deffinatly used to play and i've tried everything i can think of to make them play again but they just won't.
     
  9. nitroman

    nitroman New Member

    Messages:
    1
    Hi, i witnessed the same thing the other day. Analyzing tracks while adding them to collection was accompanied by various blinking red messages and as result whole lot of mp3's were left non-playable (otherwise perfectly playable in various players) and marked with that nasty (!) mark in playlist.

    However, on my own amazement, i managed to get them ALL working by a simple (and equally desperate) drag&drop of selected folder from Mac's Finder to Traktor's (1.2.1) playlists in the folder tree area :| As result the tracks lost the nasty(!) mark, and started to be playable, as they should be in the first place. So, i suppose there is some kind of issue regarding importing/allocating of files via Traktor's own import function? Haven't tried that in Windows yet, but hopefully it works the same. ;)
     
  10. lehestro

    lehestro New Member

    Messages:
    14
    similar problem, but only with mixes

    I am having a similar problem, but to complicate things, it only occurs with native mix recorder. The tracks load fine and play fine, but when I try to play back a native mix that I recorded, I get the error everyone else is having. These are on DRM mp3s as well.

    To help you guys out, did any of you transfer your files to a different hard drive, or load your files from a backup drive? I've read that that can be a problem. I did that, but that does not explain why for me the problem is only with my native mix playback and not regular playback.

    This sucks, its' a complicated mix, and I only had to correct a few small things. Any help appreciated.

    (15" macbook pro 5,1; OSX 10.5.9; 4GB RAM; 2.8Ghz Core 2 Duo; Traktor 3.4.1)
     
  11. lehestro

    lehestro New Member

    Messages:
    14
    a question

    Have any of you guys ever transferred some of the files you are having problem with to a new drive? I wonder if that is the tie that binds us with this issue...

    i looked at my .nmx file (the file type for native mixes) in TextEdit (aka Notepad for macs), and all of the files I'm having a problem with have incorrect directories attached to them in the metadata. The only problem is that if I edit the text in TextEdit the file is will not open in Traktor anymore. Great.

    Don't know if this could be the issue with some of you guys. Whatever the problem it is, from what I have gathered it has to do with Traktor, with certain action with certain files, always tries to process the files through older sets of metadata that are no longer applicable. That's all I got. Will let you guys know if I find a fix.
    ---
    So I figured out my issue. I was right. Despite the fact that I have relocated my tracks and they load fine regularly, they will not load in my mix because of outdated metadata. I get the same error you guys get. I tried to edit the metadata, but couldn't, so instead recreated the directories where Traktor believes my track should be located, and this has solved the problem. No more error!

    For you guys, I would check your collection.nml file, or, if you are trying to load your track from a specific playlist (itunes, e.g.) then check the metadata. See if it lines up with how your files are actually organized. I wish I knew of a better solution than to recreate directories (anyone know how to edit .nml or .nmx files?), but at least it works again. Hope you guys have the same, er... luck?
     
Thread Status:
Not open for further replies.