Skip to content

Conversation

@brunchboy
Copy link

I just realized that I have made many important additions and fixes to these formats since I last shared them with this project.

James Elliott and others added 15 commits November 19, 2018 19:12
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.
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.
@generalmimon
Copy link
Member

This supersedes #116, right?

@brunchboy
Copy link
Author

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?

@brunchboy
Copy link
Author

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants