Vinyl control crashes in absolute mode (Mixxx 1.8 Beta2, r2447)

Bug #599012 reported by RAFFI TEA on 2010-06-27
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Albert Santoni

Bug Description

Using vinyl control along with absolute mode causes a crash in Mixxx.

Fatal: []: ASSERT: "start_sample >= 0" in file src\engine\readaheadmanager.cpp, line 60

I used Serato control vinyls. The crash can be reproduced as follows:
1. Set lead in time to 20 s
2. Load a song and drop the needle down
3. If the neddle is in the lead in area and you try to scratch Mixxx crashes.
    In other words: Drop the needle down such that Mixxx is at ---let's say --- play position 5s.
    Spinning back the vinyls below position 0s cause the crash

Tested on Windows XP and 7 with NI Audio 4 DJ at 5ms latency
on Dual Core 2 Duo with 1.67 Ghz and 2.67 Ghz

RAFFI TEA (raffitea) wrote :

The bug happens only with pitch-independent time-stretch

RAFFI TEA (raffitea) wrote :

However, using vinyl emulation mode I get a similar crash for a couple of songs

Fatal: []: ASSERT: "start_sample >= 0" in file src\engine\readaheadmanager.cpp, line 60

The songs can be provided on request...

RAFFI TEA (raffitea) wrote :

After cleaning the needles, viny control has worked fine in vinyl emulation mode. All my former "problem songs" work now. However, such a crash should be avoided in final 1.8 series

jus (jus) wrote :

A lot of improvements has been made in Owens xwax branch

Tested some times ago and found a really stable ( with Serato timecode, some timing problems with Traktor though).

Might be worth to check out...

Albert Santoni (gamegod) wrote :

Should be fixed in the 1.8 branch, r2477.

Changed in mixxx:
assignee: nobody → Albert Santoni (gamegod)
importance: Undecided → High
milestone: none → 1.8.0
status: New → Fix Committed
RJ Skerry-Ryan (rryan) on 2010-10-05
Changed in mixxx:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers