Stem beatgrid offset between desktop and laptop

DJEEka Member Posts: 10 Newcomer
edited November 2022 in Traktor Software & Hardware

Hi all, weird beatgrid problems with my stem files.

When the stems were first extracted using Nuo Stems, the grid and cuepoints were off by a bit, so I corrected them all, working on my desktop for ease of use and saved the library and files on my external HD.

When I open the library on my laptop, the beatgrid and cuepoints are offset again, as if I didn't fix them, and they are correct when opened on my desktop, with the same library and files from the external HD.

If I try to correct the grids on my laptop, it will now be offset and off-mark when loading files on my desktop.

Has anyone seen this?



  • DJEEka
    DJEEka Member Posts: 10 Newcomer

    As a side note, if I clear the library on my laptop and re-import it, the beat grids are now correct on the laptop and offset on the desktop.

    My stem beatgrids on my laptop and desktop are in two parallel universes, slightly offset from one another.

  • DJEEka
    DJEEka Member Posts: 10 Newcomer

    In the end, it's because the stem audio tracks are trimmed at the start, probably to cut silence, and that's enough to shift the whole grid.

  • zephry
    zephry Member Posts: 424 Pro

    Yep I have had that happen with samples in Remix Decks that should be offset. The silence lined them up with the kick.

  • zephry
    zephry Member Posts: 424 Pro

    I haven't worked with Stem tracks creation for a long time. But if I remember correctly, you should have been able to fix the file when making the track.

    Mainly I did the stems in Ableton and had to make sure warp was off and my start and endpoints were all the same lengths.

  • DJEEka
    DJEEka Member Posts: 10 Newcomer

    Yeah, I believe it's a bug/feature of the NuoStem extraction pipeline.

    I'm still dumbfounded on why the grids show up differently depending on what computer I open them.

    Oh well...

  • dj_estrela
    dj_estrela Member Posts: 154 Pro

    The offsets are ttpically caused by different mp3 libraries that interpret SOME mp3 headers differently


  • Patch
    Patch Member Posts: 191 Advisor

    Okay - this is interesting! I'm sure I've seen this in Track Decks too, when using .mp3 files across my laptop & my desktop (but, both share a single Collection.nml that is stored on a network drive...)

Back To Top