clicking around the waveform also gives some fun results in 1.2.4:
I don’t need to make a living out of DJing, but the occasional club night becomes far more, uhm, interesting with this problem in mind. After all, I got most of my DnB and House from iTunes. As long as you specifically know what tracks you’re looking for, you can find them there. Sound quality is good, price is good.
Yes, it did happen to me with mp3s. Just not that often.
WTF are you banging on about? Or are you talking about torrents?
That looks very bad.
I know this may be asking you to repeat but what is your setup when you are doing that. CD timecode ? File type ? etc.
I have tried and failed to reproduce this following the description at the NI forum but its clearly ‘seems’ a bad bug.
It should be in his Service Centre already or in his Personal Download Manger on the Support Site…
Or …
no timecode, AAC bought off of itunes, the rest is in my sig .. i filed a bug report with NI ([Ticket#2010011610002698]). i can send you the file if you want so you can try it in your setup.
Ill try it again with an iTunes aac file now and see what happens.
Can you reprodude this with internal mode and software only ?
I know you have been over this before but what exactly is the procedure to reproduce.
not sure what you mean by internal mode. i guess you mean not using timecode. like i said i am not using timecode. i tried to reproduce the above issue. it seems to not be limited to AAC bought on itunes .. i tried various aac that i ripped myself in itunes to AAC and i see the same issue. i reproduced it on a couple more AAC tracks (seems like its atleast half of my tracks that behave this way). havent been able to get this behavior with an mp3 though.
By internal mode i mean Internal soundcard (sorry i wasnt clear. my bad).
Im not at home i just have the laptop until later on.
Are you just clicking around the waveform or do you play the track first and then click the waveform.
Are you using the vci to scrub backwards through the track (i read that at NI)?
i was using my AK1 soundcard. i do play the track and so far i have only gotten it to misbehave if i let the track run out to the very end. letting it run out inside a loop seems to sometimes be the tipping point, but it also happens with out a loop. i am not touching the midi controller at all.
Hmm, just tried an iTunes aac track.
Let it play out to the end then clicked in the waveform and i cant see any issues .
I have the same Mac as you by the look of things.
Ill keep looking into it.
Ill forward your ticket to support now and put an advise on it that its ongoing.
If that helps: I tried my macbook’s internal soundcard, the Audio4, The Otus built-in soundcard and an M-Audio Transit. I also tried it with timecode, Midi-commands and mouse-only for transport and fiddling with the soundcard buffers. It all boils down to one thing: It doesn’t have anything to do with soundcard drivers or anything else that is hardware related. It just happens with quite a few, but not all m4a files (and a few mp3s for that matter).
I read somewhere (NI forum maybe, can’t find it again) that this problem is related to a new cache scheme that was introduced with version 1.2. Don’t know how much truth is in that but it kind of makes sense.
Yeah that makes sense. What doesnt make sense is that only some users are experiencing it. Even those with similar setups.
Ill see what support tell me. Probably on Monday now.
Okay, now we’re either getting closer to the disappearing m4a waveform problem - or completely confused. Lengthy post, but please read.
I tried to find a file to upload which shows the m4a problem and I could legally share with you guys. As I couldn’t find one I tried to create one myself. So I took a Creative Commons tune from someone I know (Levelheads - Definition - source: www.supafeed.net) and tried a couple of recompression methods. Source File is mp3.
When reencoding from mp3 to m4a with itunes, the resulting file didn’t show the problem.
When using another encoder that is ffmpeg based - the resulting file had the problem in traktor. Both files are included in the zip file that is linked at the end of this post. It would be great if someone tried them to see if the problem can be reproduced with the same files on different systems.
Another thing: After creating a wav file from the non-working, ffmpeg-encoded m4a and then reencoding the resulting wav in itunes to m4a, that file also worked again perfectly in traktor.
BUT: I tried this with another tune that I bought from iTunes and for obvious reasons won’t share. The m4a-wav-m4a-route via iTunes resulted in a file that again showed the problem in traktor. The wav file worked fine though, and so did mp3 files that were re-encoded from the original, non-working m4a.
Sorry if this is a little confusing, I hope you guys can follow me. I don’t know if I was able to describe the situation properly with the remains of my formerly average skills in writing english.
Here’s the link to the zip file with working and non-working m4a:
http://rapidshare.com/files/336313241/levelheads_definition.zip
(Edit: Original files were distributed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.0 License, plus I know the rights owner, so I think he’ll be okay with this)
(Hope rapidshare is okay for you and forum rules allow it)
Rapidshares servers are overloaded at the moment.
I get on it as soon as i can get the download.
Does it fix Blue Screening my laptop during a live set???
No, not on YOUR laptop.
Seriously, WTF? How are we meant to answer that.
Words… mouth… out of…
You can’t and I can’t. I only know that 1.1.2 was the most stable version that “hasn’t” crashed my laptop, or cut out during a set.
Can you give us a little more to go on.
Say … oh i dunno EVERYTHING ?
Let’s see.
Hardware:
Compaq Presario v2582us/ AMD Turion CPU
2gig Rams
100g internal hdd
500 ext hdd
WinXP Pro 32bit
Using a NI Audio2 dj, ext mouse, with a Behringer VMX-200 Mixer.
I’ve already went and tweaked the audio latency to where there’s no crackles, hiss or pops.
Problem I recently had with v1.2.3 was I was playing a track (6min long) and around the 4min mark the laptop just dumped and there was a BSOD.
Whenever I load a new track I get that moment of freezing when the track gets analyzed. The music still plays, but the deck either a/b will be froze.
I even un-checked “Analyze New Tracks on Loads”
ATM, I’m creating play lists and scanning them to get the track stripe. I used BPM Analyzer to get the bpms.
I have the deck cache for decks a/b to 128. Since I don’t used c/d I left that at default.
Only thing I haven’t tried just yet is to load a track directly off my internal hdd and one off the ext to see if the track is analyzed more quicker.
Any Ideas??