New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update xwax to 1.2 #6095
Comments
Commented by: starlily xwax is now on version 1.2 as of March :) |
Commented by: rryan How time flies! :) |
Commented by: ywwg Done and tested with Serato and Traktor V1 Vinyl (lp:mixxx/1.11 commit 3413) |
Commented by: ywwg Ah I misread the bug report and put this in the wrong branch -- the API changes are very minor, however (check out diff to vinylcontrolxwax.cpp) -- should I revert the commit? |
Commented by: rryan Nope -- I just figured you didn't have time before the 1.11.0 release. Thanks! Instead of Q_ASSERT'ing in VinylControlXwax is there a way to fail gracefully (i.e. just disable vinyl control or something?). I'm trying to get rid of all the Q_ASSERTs. |
Commented by: rryan Also, the Windows build is broken :). |
Commented by: rryan
I assume because Windows is not supported? Or maybe this is a patch we put in place on top of xwax. |
Commented by: ywwg Good catch, yeah we tweaked the file a bit for windows. I should really make a diff that I can just apply to xwax's source to make this easier. |
Commented by: ywwg Fixes applied. The vinyl control code currently doesn't have a failure mode, so I did what we do elsewhere and default to serato side A. |
Commented by: ywwg OK the build server finally likes the win32 versions of the files now. I'm going to make a diff so this doesn't happen again |
Commented by: ywwg OK the build server finally likes the win32 versions of the files now. I'm going to make a diff so this doesn't happen again |
Issue closed with status Fix Released. |
Reported by: ywwg
Date: 2011-11-09T16:36:51Z
Status: Fix Released
Importance: Undecided
Launchpad Issue: lp888155
Xwax has released version 1.0, bring that into mixxx so we're up to date. (also need to check for api changes, etc)
The text was updated successfully, but these errors were encountered: