-
Notifications
You must be signed in to change notification settings - Fork 72
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
Export to Guitar Pro format #350
Comments
Does ascii export relate to this coding wise or is that an entirely different job even though technically an export? Creating a .txt file and..? |
Ascii export is fairly unrelated since it's exporting to a very different format |
So for now its a one or the other proposition and exporting to GP would be more useful as the GP file you end up w can export to ascii, though i do hope to see import/export of ascii too eventually |
Currently this creates the zip contents, with the version entry and an empty score.gpif xml file Refactored the Gp7::Document header a bit so that the code for converting to XML can belong in a separate file. #350
The .gp files can now successfully load in Guitar Pro! #350
- Add enum <-> string conversions for the Note::Accidental enum - Fixed a couple issues with roundtripping chord diagrams that caused different results to be produced. On import, identical diagrams from different tracks are consolidated, and we avoid inserting duplicate chord text items at the same position Bug: #350
This would be useful for exporting to other applications, websites etc which may not understand
.pt2
files.The best approach is probably to create
.gp
(GP7) files, since this mirrors how the guitar pro importer works. (The importers for versions 3/4/5/6 parse the file and then convert to our internal representation of the GP7 data, which is then converted to a .pt2Score
)The text was updated successfully, but these errors were encountered: