-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add support for the SeratoMarkers_ GEOB tag (Hotcues/Loops/Track Color) #2495
Conversation
79d8cd3
to
2d65a58
Compare
<< (quint8)m_type | ||
<< (quint8)m_isLocked; | ||
return data; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also required a lot comments, including examples.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I almost completely rewrote the parser code using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice changes. Here some more comments.
Merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added some nit picks about possible implementation defined issues.
b76aecd
to
c9a38e5
Compare
Had to remove the last commit since it made the tests fail |
LGTM, Thank you. |
This augments the
Serato Markers2
tag parser that was added in #2323. TheSerato Markers_
contains the first 5 Hotcues, the first 9 saved loops and the library track color.All of this information (and more) is also stored in the
Serato Markers2
tag, but Serato will prefer information from this tag if it's present. If we add support for writingSerato Markers2
, we should also writeSerato Markers_
because otherwise our changes would not be picked up by Serato.