On 7 August 2014 17:04, chen lung <[email protected]> wrote:
> Hi John
>
> Welcome and good work :).
>
Hello, and thanks!
> I was hesitant to pounce if you are exploring things in a certain way, but
> here goes!
>
> 1. Would it be the right time to submit reports on GPX?
>
Almost; I have a pull request in at the moment that adds a lot of new
features and fixes. When that is merged, then certainly it's time to start
finding any issues and putting them in the bug-tracker. There are a few
enhancements I need to make to that PR before it is merged, I intend to
look at these tomorrow.
I'm closing the bug that generally describes that GPX files are not
supported, so that we don't end up with distinct issues under the same bug,
it would be nice to have separate bug reports for each feature which
doesn't work as intended.
Generally, larger GPX files are something I haven't been testing with as
it's often small individual test cases that I've been using to identify and
create support for each unsupported feature. While everything should work
in the larger case in a non-toy score, there are bound to be issues to find
and fix there as there's been less testing in that area.
> 2. Some things you maybe unaware of:
>
> There are issues without a Guitar Pro tag (such as this
> <http://musescore.org/en/node/22438> ).
>
> It might be worth performing a search in the issue tracker (or whatever),
> if
> you haven't.
>
These non-tagged bugs are not specific to Guitar Pro (somebody leap in and
correct me otherwise) and are really bugs which either:
- Affect how text affects other score elements. Unless we want to do
something special with the Guitar Pro case of this, then this bug should
probably be edited to describe the issue as a whole as this issue applies
to Musescore as a whole.
- Beaming, which I think should probably be closed as 'by design'. I'm not
sure that a machinery to modify how beaming is done in Musescore is
beneficial and sounds overly-complicated, and ascertaining how Guitar Pro
does this in all cases could be inherently fiddly.
Certainly welcome all contrasting views though!
> There are threads about Guitar Pro which were posted in the Technology
> Preview section to invite further comment (possibly due to lack of
> knowledge):
>
> http://musescore.org/en/node/21684
This one has certainly attracted discussion. Perhaps there should be a user
option whether or not parts should be created (maybe there already is and
I'm unaware of it). This is perhaps an issue that extends beyond Guitar
Pro, presumably importing from XML brings up the same questions. I'm not
sure there's a right or wrong answer here, and what the general consensus
is on this subject.
> http://musescore.org/en/node/21699
I do think this report is probably still valid. I shall think about this,
thanks!
>
> http://musescore.org/en/node/24653
Artificial harmonics should be supported in the new pull request
(artificial-harmonic.gpx test case). I notice the appropriate functions
still needs to be called by other Guitar Pro versions (one of my current
active tasks is checking that features that have now been added are support
in all relevant Guitar Pro versions and that none have been missed out -
this should be a minor change as the work has been done for another format
so the machinery is there). Certainly they are not supported in Guitar Pro
3 as I cannot locate a copy of Guitar Pro 4 [1] any longer (Guitar Pro
supports exporting to one version previous from its current version). With
the test case you have provided there, I should be able to build a solution
for that version of Guitar Pro too, I will look at this - thanks!
Aside from an issue with key signatures (warnings generated at run-time,
but correct on the score), after I've resolved the issues with the current
pull request and it's merged then all features should be supported in
Guitar Pro 6 too. If something doesn't work in any Guitar Pro version at
that point then it's a bug and we should keep track of that in the bug
tracker. I'll be doing as much testing as I can next week to detect and
resolve any issues.
Any other comments fire away! Thanks for your comments so far. :-)
John
[1] TuxGuitar can export to GP3 but I realized early on that it is not a
faithful implementation of Guitar Pro. I'm focusing support on 4, 5 and 6
and that's what Guitar Pro versions I have found to be available. That
said, generally if something works for version 3 it's very similar in
version 4 and adding support is easy so I'm happy to make any necessary
changes to that format if we have a test case for it.
>
>
>
> -----
> Scott
> --
> View this message in context:
> http://dev-list.musescore.org/Introduction-tp7578717p7578884.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
