I’ve run into this issue in the past but either a full import or making sure traktor is shut seems to have resolved it but not now.
I use traktor as my main place to grid and set cue points and typically add to library first in traktor if I’ve used an external tool (Nuo-stems) to create a m4a stem file as adding these tracks into lexicon first stops traktor from recognising them as stem files if they haven’t first been added to traktor.
I then sync to lexicon and use custom tags and smart playlists to add them into a bunch of playlists.
What I am now noticing is that most tracks now have the beat grid shifted nearly half a beat left. If I sync back to traktor the grid is as expected, so it’s a lexicon thing, but if I also sync to RB the beat shift propagates there too. I wondered if this was a beat shift issue so tried that on a couple of tracks, synced back to traktor and then back to lexicon but that didn’t make a difference.
I also fixed the grid on the test track and synced that to RB and weirdly it was still shifted there too.
any ideas what’s going on here?
the issue may have been around for a while as I typically don’t pay much attention to the grids in lexicon as I DJ using traktor primarily. Im only noticing this now as I want to sync to RB to get a CDJ USB ready.
At this point Im thinking I need to start looking at other tools such as DJCU as I cant manually adjust this many grids in time for weekend
Interestingly, and annoyingly, I have purchased DJCU and found the same issue with that too. It is all my m4a tracks, other formats seem unaffected.
OK, so I think I’ve worked it out. Im using Nuo-Stems outside of traktor and hadn’t been using its inbuilt functionality to add the newly created stems to traktor, Id been doing this manually. Nuo-Stems has a default option of adding a 100ms offset to prevent beatgrid issues, so it was this non default behaviour that was causing the issue.
I’ve never used nuo stems but that’s good info to know
Sorry, I need to resurect this again as I thought I’d solved it but haven’t been able to replicate it since. whatever I try the m4a stem grid is offset compared to the original wav when imported. Both the original and stem have identical grids in traktor. speaking to Nuo, the guy behind the Nuo-Stems software ,he is saying it is a bug in your software. Im not sure either way. Is it possible I can upload a sample track/nml for you to take a look at?
What are you doing exactly with your files and Traktor? Lexicon does correct beatgrids sometimes so might be that it is doing that but not for the stem files
im converting a wav/aif file to a stem m4a file using Nuo-stems, adding it and the original to traktor and gridding/cueing and adding to a test playlist. I then close traktor and import that playlist from traktor into lexicon. the grids are shifted left, on the original they are not.
Can you send me one of those combined stem files? I’ll give it a test here
You can upload with this link: http://upload.lexicondj.com
done. thanks
not sure if I posted both files, so just uploaded the original file plus the stem m4a in case you wanted to directly compare
Thanks, I will check later this week or next week
just wondering if youve had a chance to look at this?
Yeah, the aiff file is not affected by a beatshift but the m4a is. Problem is that the m4a file is not detected as beatshift file. The problem could be at the encoder nuo-stems uses but I can’t say that for sure.
so, just had a conversation with Nuo Stems developer and he has confirmed that his software uses the default encoder that was included as part of the NI Stem Creator tool from many years ago. So nothing has changed on this front.
As I mentioned, I didn’t use to have this problem, so it is odd. The only other possibility I can think of is something having changed in Traktor as there have been a couple of recent updates, but it feels unlikely. Is there any way you can accommodate this beat shift issue with these stems?
Okay but your original file wasn’t encoded in the same way, but the m4a was encoded by nuo stems. So there is a difference in the files. You can try running the Beatshift Fixer utility on the m4a file and see if that helps. My advice is to run it on one m4a track first, then delete it from Lexicon and import it from Traktor again.
just tried the beatshifter utility on that 1 track, deleted from lexicon collection and reimported and the grid is still shifted by the same amount.
are you able to replicate the issue with the test files I uploaded? Im using traktor 4.3, but had the same issue with 4.2 as well
I’ve just tried this with TP 4.1.1 and the same issue, which makes me doubt it has ever worked if nothing has changed in Lexicon that could impact this.
Yeah with the m4a I had the same issue. I don’t think the Traktor version matters, the beatshift problem has existed for a long time and it’s not something anyone can simply fix, not even Traktor. Sadly I don’t have a solution for these files right now. Most are auto corrected and fixed by the beatshift fixer, but some fall through and your files appear to fall into that last category 