-
Notifications
You must be signed in to change notification settings - Fork 119
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
Manual: explain what the different waveform types are? #603
Comments
Here's a simple summary for the parallel waveforms:
The additional attributes (legacy, GLSL) just specify the technology the waveforms are using. Generally once you have chosen your preferred style, you should select the non-legacy GLSL waveforms as they should be the fastest. Those might not work on your hardware, which is why the legacy and non-GLSL waveforms are still provided. Those are usually more robust, but also more expensive to run since they deliberately don't make use of the same acceleration possibilities. Does that summary make sense to you? Do you have suggestions before we add something like this into the manual? |
Some suggestions: use signal instead of track (entire track has the connotation of time), maintain the order of R G B, low instead of bass, mention L channel = up , R channel is down. Plus some changes for clarity / grammar (abusing quote):
I think you are right about RGB Stacked (but I didn't port it, so not sure). I agree with you that HSV makes little sense. Even knowing what is behind it, I don't find it intuitive. I wouldn't say the legacy and non-GLSL are more robust :-). Proposed:
BTW, when it comes to amplitude, the description of the waveform types only holds really true, at least for the GLSL waveforms, when we merge mixxxdj/mixxx#12205 , which I created after investigating why, as @ronso0 pointed out inconsistencies in the amplitude here mixxxdj/mixxx#12115 . I didn't fix these inconsistencies in the legacy waveforms. |
On a side note, I think that there are much more interesting uses of the HSV color model than what is currently done with the HSV waveform type. See: m0dB/mixxx#7 |
@mxmilkiib I have just added some changes to my PR mixxxdj/mixxx#12466 to attempt to make the amplitude more similar across all waveform types. Still not perfect but similar. At last all the GLSL non-legacy waveforms now have the same amplitude (except for filtered, which is conceptually too different). It is unfortunate that there are so many types, and we should really get rid of most of them. I have been digging deep to try to understand the code and but it's a bit of a mess with lots of legacy. But until we do a full clean up, there will be some inconsistencies here. My recommendation is that you pick the GLSL non-legacy one and set a visual gain that works for you. |
Feature Description
I really don't understand the differences.
I'm autistic and blindly trying to figure this all out has been making me rather disregulated. I have just realised though this has been in part due to the bug mixxxdj/mixxx#12226, which has made trying to interpret the states quite the logic puzzle..!
Related: mixxxdj/mixxx#11915, mixxxdj/mixxx#11838, mixxxdj/mixxx#11615, mixxxdj/mixxx#6428
The text was updated successfully, but these errors were encountered: