Beatgrid on the fly causes play/cue broken

[Wuz]

Copy pasted from NI forum: http://www.native-instruments.com/fo...545#post548545
Anyone encounter this or how to fix it, one guy over there said theres a solution but not what the solution was or where to find it.

Ok so i posted about this bug a long time ago (around traktor pro's release time)
Nobody really understood what i meant when i explained it so heres a video.

Basically i load a track into Deck A, line up the cue on a downbeat and attempt to make a grid marker.
Then hit play and the deck becomes broken, cue and play don't work properly and check out the phase meter.

http://www.youtube.com/watch?v=mtzXqPrizxQ

It stays broken like that whenever you hit play unless you drag the waveform with the mouse, at which point the track plays but the play and cue buttons still dont function properly (midi assignments or clicking onscreen)

Traktor needs to be restarted.
Anyone care to shed some light?

this is on windows xp sp2 and has been happening since 1.0
using an NI audio kontrol 1 and a vestax vci-100

[BentoSan]

How are you attempting to make a grid marker ? are you setting an autogrid ?
Or are you droping a cue point, saving it, then turning the saved cue point marker into a beatgrid ?

Try both ways, one might work and not the other.

[Wuz]

got a button on the vci100 thats mapped to set grid marker at the current position.

[BentoSan]

got a button on the vci100 thats mapped to set grid marker at the current position.

An autogrid marker or a cue grid marker ? or a manual marker ?

Also show what midi assignments you trying to use for both your grid button ? Your video does not even show that a grid marker has even being placed where your trying to drop it which makes me think you have some wacked out midi assignments.

[Wuz]

this help?
I'll be happy if i find out this was a problem with a midi assignment but i'm 99% certain its a traktor bug.

[DvlsAdvct]

And just to be clear, cause I can't see it on that screen, you have a button to get back to m1=0, right, assuming the commands are the same but exist in different modifiers? If not then disregard.

[BentoSan]

If autogrids not working for you try creating a few macros to drop a cue point, save it, then turn it into a beatgrid marker.

[Wuz]

And just to be clear, cause I can't see it on that screen, you have a button to get back to m1=0, right, assuming the commands are the same but exist in different modifiers? If not then disregard.

Modifier is set to hold so i hold it down then use the set grid button and release after I have set the grid.

If autogrids not working for you try creating a few macros to drop a cue point, save it, then turn it into a beatgrid marker.

so make it a two stage process?

1. set hot cue
2. convert to beatgrid

...interesting idea and may very well solve the issue, will try something like this later!

Ok so i spoke to bento a bit more about this and he suggested i try something, I have successfully had the bug occur and fixed it so it seems like i can fix it if it occurs but time will tell.
I'll have to grid some new tracks and see how i go but i think its fixed.

for the record, Bento is a magnificent bastard!