Guitar Pro files opening with parts

• Jun 27, 2013 - 02:22

In the Guitar Pro files that I've opened so far in MuseScore, they appear with parts for each instrument.

I think they should open just normally without parts, but am I perhaps missing something?

Using MuseScore 2.0 Nightly Build (8eba963) - Mac 10.7.5.


Comments

In reply to by chen lung

But what about the people who *do* want the parts - which I have to imagine is the vast majority of users? After all, why would most people bother opening a file in a notation program if not to be able to get at the notation? And aren't parts are as much of the notation as the score? Seems you might as well say, MuseScore should only open page 1 of a score, because you weren't going to use pages 2-17. One of the huge wins provided by linked parts in 2.0 is not having to go through handstands to get at parts any more - they are now part of the file just as much as the score is. Why go backwards on that count in the special case of Guitar Pro files? What's the harm in having the parts there even if for whatever reason you are opening the file but don't intend to look at the whole thing?

In reply to by Marc Sabatella

What's the harm in having the parts there even if for whatever reason you are opening the file but don't intend to look at the whole thing?

There is at least one reason why you would not want to see parts and that's true for GP or any file. It's for performance reason. Having a score with 10 parts open is like having 11 scores opened. Adding a measure in the score will make a loop on 10 scores to add a measure as well etc...

In reply to by Marc Sabatella

In my opinion, 'Parts' is a non-essential feature that can be optionally used - I don't want it there by default. Everyone will have different uses for them - therefore, the current offering when importing Guitar Pro files won't suit all users and instead, just takes up resources.

I'm not sure if it was an oversight, or deliberate, but I don't think parts appears for any other file type that is imported.

I believe it's better to be 'neutral', I suppose, in the default.

I don't think what you mention regarding pages is the same, as those are essential :).

In reply to by chen lung

I was of course being facetious about the page thing, sorry I left out the smiley :-). But where do you draw the line? Who decides which part of a file are essential and which are not? And on what basis? If the info is there, it's there. If performance is a reason not display it immediately, then that's one thing. Although I wonder - if the parts are present but not displayed and therefore not updated as notes are add, would that really be OK? Would the parts be updated properly when the parts *are* displayed? That would be something to work out I guess.

But it's the various problems that come about from "parts aren't important" thinking that I think of the linked parts facility as trying to *eliminate*. Parts *are* important whether any given person chooses to think about them (perhaps they deal only with computer playback and never deal with human musicians?), just as dynamics are important, articulations are important, etc, whether or not any given person opening the score might be looking at that particular bit of information.

As for why GP and not other types, I'd say that's a bug in the other types - the implementation perhaps isn't complete enough for them to be able to define the parts?

Do you still have an unanswered question? Please log in first to post your question.