After analysing my tracks the bitrate becomes 0Kbps.?

Heyy.

I use Traktor Scratch Pro 2 and I'm having an issue with my detected audio bit rate.
Although I can't stand iTunes, I use it to rip my CD's, collect audio art and organise my music. I rip my CD's at a slow speed and save them in a Lossless format. I use Apple Lossless.m4a's. Once I have all my audio ripped and organised I open Traktor and click my iTunes tab and get access to all my audio. Then what I like to do is copy my music into my traktor library and make playlists etc and all is well. It shows my audio file as it should. In the browser from left to right all the info is there. e.g Kyoto (feat. Sirah). Skrillex. Bangarang. 3:20. 117bpm. 1200kbps. Apple lossless.m4a.
But soon as I analyse the track traktor changes the audio bit rate to 0Kbps. It does not affect the file in any way or cause me to not be able to use it but I like to always where possible know or at least see the bit rate to the track before I drop it into my set. It's also not just that, to me that does not seem normal and I hate the fact that something is not working like it should be. Any ideas.?

Also one other thing.. I have Traktor set up to show me a Spectrum Waveform (Blue for treble, Green for vocals, Yellow/orange for Mid and Red for bass) so what does it mean when my whole Waveform comes up black.? And I actually mean black not the X-Ray colour setting Traktor can do.

Cheers

Danny.

 

i cant help u with the audio bit rate. but sometimes when loading a song and pressing play, the waveforms go black. you just need to cue it back and the waveform will come back.

hope everything works out.

 

Yea mate I tried what you said with cueing it back but still it stays black. It only goes black for 2 tracks that I have. So I'm thinking it could have something to do with those tracks..?

 

I observe the same behavior. All AAC files (".m4a") show up with a bitrate of 0 in Traktor. It's been like that as long as I can remember.

idk if it is a bug or intended behavior.

 

Hrmm yea I have noticed that too, but with mine it's only 0kbps once I have analised the track.

 

i'm finding the same issue with .m4a! I think this really should be fixed as you would normally use searching for 0kbps to find broken tracks