tab-debug

Fix missing or duplicated notes in TEF banjo tablature by performing binary TEF parsing checks to validate the binary data and extract reliable note events. This isolates whether the issue stems from the original TEF data or the parsing logic.

TEF tablature playback timing and articulations become incorrect when binary parsing fails to extract events accurately. You can detect timing mismatches, slurs, ties, and triplets by running playback timing verification and inspecting the converted notation rendering.

The best way to debug TEF to OTF conversion issues is to follow a structured workflow: retrieve the source TEF file, parse the binary data, convert it to OTF, and run rendering checks to verify that the notation displays correctly after conversion.

Yes, you can debug TEF tablature files from Banjo Hangout. The source inspection workflow supports retrieving and inspecting TEF files from Banjo Hangout and other TEF sources to diagnose parsing and rendering issues.

Verify TEF binary parsing by running binary TEF parsing checks to validate the data structure and extract reliable note events. If notes are missing or out of sync, the parsing logic requires adjustment to handle the specific TEF source.