-
Notifications
You must be signed in to change notification settings - Fork 205
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 rekordbox formats #696
Open
brunchboy
wants to merge
15
commits into
kaitai-io:master
Choose a base branch
from
brunchboy:update-rekordbox-formats
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These have been proven to work in the context of my Beat Link Trigger project, enabling it to retrieve the database over NFS, parse it, and extract all the track metadata it needs even when it is impossible to connect to the database server running on the players because there are four of them in use.
Another good suggestion from @KOLANICH
Trying to use an enum causes unavoidable parse errors in Java and Python when new/unknown FourCC values are encountered. See kaitai-io/kaitai_struct#300
@iamtunzor_twitter found media where there were different values for the artist row, which was causing total database parse failure. Now we should be robust as long as there are no actual structural changes.
Thanks to @iamtunzor_twitter in Croatia for getting his DJ to share a copy of the problematic database file with me!
Now has a much clearer structure in the .ksy *and* provides a single, unified API for the struct user to access the name however it was stored.
This supersedes #116, right? |
Yes, I forgot that that was never merged, we’ve been using these files productively for years now! Shall I just close the old one? |
Alternately, I could merge this branch into #116 and close this one? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I just realized that I have made many important additions and fixes to these formats since I last shared them with this project.