MIXVIBES Dj Community old forum

Just had this error. couldn'd find back the topic where UncleVibes mentioned it.

Was in autoplay with videos only. Somewhere like 15th video track. Pretty sure happened at end of transition period deck B to A in 2 deck mode, 1 output screen. Music kept playing, video frooze at/close to beginning of track. Cross responds to MIDI, not to screen.
Audio ended normal at end of track; however no switch to Next.

So click OK in error message and crash...

remarkable points: one apostrophe in title, no artistname in one but last track. Stop time was written in history for this track, not for last track.

this was the title:
Don't Be Stupid (You Know I Love You)

Could not duplicate with a smaller set of videos.
Did however notice that the clicking in 'end of track period' does not always trigger the EOT warning. Last fix might not have fixed all.

rverzuu@qmcgroup.nl wrote:Just had this error. couldn'd find back the topic where UncleVibes mentioned it.

Was in autoplay with videos only. Somewhere like 15th video track. Pretty sure happened at end of transition period deck B to A in 2 deck mode, 1 output screen. Music kept playing, video frooze at/close to beginning of track. Cross responds to MIDI, not to screen.
Audio ended normal at end of track; however no switch to Next.

So click OK in error message and crash...

remarkable points: one apostrophe in title, no artistname in one but last track. Stop time was written in history for this track, not for last track.

this was the title:
Don't Be Stupid (You Know I Love You)

Could not duplicate with a smaller set of videos.

Don't you saved a screenshot of the error window or the exact message that was shown? Several users seem to encounter this issue, but we are unable to reproduce and do not have reliable info about it so far. Any clue is welcome

rverzuu@qmcgroup.nl wrote:Did however notice that the clicking in 'end of track period' does not always trigger the EOT warning. Last fix might not have fixed all.

Yes , this one had already been reporter and fixed for 3.1.0!
Thanks anyway

Good we are hunting this one

no debug info or specific error. pretty sure it was the exact vague message I noted by daddyvibes .will try running in my dev environment to see if debugger catches more. if it happens again...