-
Notifications
You must be signed in to change notification settings - Fork 11
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
enabling debug dumping-as-json mode for v6 files #25
Comments
Super interesting! Do you have an example of what such a file looks like? I don't have access to my ReMarkable at the moment since it's bricked :x |
Sorry to hear that! I'll get a sample one together soon, but they can be pretty huge. Its the entire file in plain JSON format. For example here's block type 13:
and block type 8:
patches incoming :D |
Oh my Did you discover this debugging flag yourself? It's stupidly useful for what we're doing here 😅😅 I did a bit of digging a while ago, even went as far as downloading ghidra and even getting a book on it.. but I felt it was a bit much given my other responsibilities.. glad to see there are other people digging! |
yeah, just found it this afternoon! I'd spotted there were some interesting strings which were clearly tracing from functions about "writing scene files out as JSON" so I went poking about.. and there it was! |
Awesome! You should really share this discovery in the remarkable discord! |
Good plan: done! Here's a simple sample of the RM file and its matching json file. 2584527c-7667-4b1c-994c-ae70215653e4.rm.gz |
@adq that's great! Thanks for sharing and for the patches. |
I've added a link to this issue in the README and so will close it here. |
If you set
SCENE_FILE_V6_DEBUG=1
prior to running xochitl will start dumping the rm files as json files for debug when it saves them - it'll output in journalctl what the filenames are.If you wanna enable this persistently:
The text was updated successfully, but these errors were encountered: