Variable beatgrid bug (deck going crazy)? And where are the variable beatgrids saved?

Miles Hi

Hi, I've had this issue 3 times so far, so I think it must be a bug. After panicking the first time for 2 whole minutes I found a quick fix.
After loading a track with variable beatgrip to the deck and pressing play, that deck then goes crazy, goes faster or slower, and the beatgrid is totally off in sync, or without sync. when this happens it´s impossible to mix either manually. The first time I panicked as I was in the middle of a wedding, but then I found how to fix it, and this is by changing that deck to live input (or any other input) and then selecting track input again and re-loading the track to it.
After that it works fine again.
I use S4Mk3, but this has nothing to do with it as I couldn´t fix it directly using my macbook either.

The other question I have is about where the beatgrids are actually saved.
My workflow has me doing all my preparation (playlists, beatgrids, cue points, etc) on my home PC and once I have made all the changes I filesync the music folders and collection file to my 2 macbooks. Obviously, after this, I have to search for the music files inside Traktor, but that´s not a big deal.
Since variable beatgrids have been introduced, I seem to lose the beatgrids that I made on my PC, or they are there, but not in synced to the beat correctly as I have them on my home PC.
Are these stored in a different way from the "normal" beatgrids?

lord-carlos

After loading a track with variable beatgrip to the deck and pressing play, that deck then goes crazy, goes faster or slower, and the beatgrid is totally off in sync,

Mhh, it somewhat sound like master clock was turned on and the deck synced to it?

The other question I have is about where the beatgrids are actually saved.

In the collection.nml just like before.

But maybe the normal grid was also saved in the files itself? I don't know if anything changed.