Skip to content
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

Added support for more characters in the lyric tracks #112

Merged
merged 3 commits into from
Apr 17, 2023

Conversation

TheFatBastid
Copy link
Contributor

Added support for accents and other extended characters as well as the undertie

Parses '§' in the midi track to '‿'
This allow for accented characters in lyric tracks (changed from just ASCII)
This font didn't have the undertie (U+203F) glyph in it so I slapped in both and had to regenerate the font atlases. Taken from Gnu's freefont.
@EliteAsian123 EliteAsian123 merged commit 1e47b8d into YARC-Official:master Apr 17, 2023
@TheFatBastid TheFatBastid deleted the patch-9 branch May 13, 2023 16:34
Purplo-cf pushed a commit to Purplo-cf/YARG that referenced this pull request May 14, 2024
* Rename _position to _tickPosition

* Make YARGMidiTrack responsible for its own data

* Implement VLQ absorption as alternative to full parsing

Scanning does not use any of the actual positional information, so not having to parse it could provide a benefit

* Re-add MemoryStream special case for MidiTrack

* Remove need for SkipEvent()

* Minor alteration to Non-Meta event handling

* Rename memory variable

* Use constant max vs iterative for loop in AbsorbVLQ conditional

* VLQ magic number removal

* Use switch over list of if-elses for event parsing

* Remove unnecessary byte[] variable

* Account for SequenceNumber event type in process loop

* Midi constant adjustments

+ Use hex representation for bitwise values.
+ Add summary comment describing VLQ_SHIFTLIMIT's functionality
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