Chord Display from Band In A Box SGU
How do I get MS to display the same Chords as BIAB ?
Thanks.
Attachment | Size |
---|---|
Song_30m_Pop_8_A_JazzChords.zip | 1.88 KB |
musescore_biab.jpg | 184.42 KB |
Biab_Chords.jpg | 117.19 KB |
Musescore_Chord_Display.jpg | 140.41 KB |
Comments
I believe I have not understood, perhaps it may be useful to you: http://musescore.org/en/handbook/known-incompatibilities#Font-problem-o…
If you're using 1.3
With Nightly (1d90b26) I get as in the attachment.
It is preferable to provide more details for more precise answers ... http://musescore.org/en/handbook/how-ask-support-or-file-reports
I don't quite understand your question. Are you asking about importing a score from BIAB *into* museScore, or creating a score from scratch in MuseScore? What specific aspect of the BIAB chords are you asking about? And which version of MuseScore are you talking abut?
In general, chord symbols are entered in MuseScore by selecting a note, pressing Ctrl+K, and typing the chord. For 1.3, you have to type chords the way MuseScore expects given your current style selection, see Chord name in the Handbook for more info on the different styles available. For 2.0, you should be able to type whatever you want (within reason), and you'd just need to select the "Jazz" style in "Style / General / Chord symbols" to get them to display in that type of font.
In reply to I don't quite understand your by Marc Sabatella
Looking a little further, I think perhaps you are talking about MuseScore 1.3, and you are talkng abut actually importing the file. I think what happened is that for whatever reason, BIAB exported the third chord as Cbbm7/D, and MuseScore 1.3 doesn't support double flats in the chord symbols, so it is displaying only the C. No idersa why BIAB exported the chord that way - seems it should have been simply F#m7? But in any case, it looks like you'll have to just double click the chord and enter it correctly by hand. Same for any other chrods thqt were exported/imported incorrectly.
In reply to Looking a little further, I by Marc Sabatella
Tried the 2 Beta it's the same with another SGU
The midi file has the exported chords in it as a track.
This is the chords from BBTools.exe http://www.alfwarnock.info/alfs/biab.php
Just rename to MGU and use "Extract Chord from BIAB file".
It gets the F# Not Cbbm/D so I think MS is not interpreting it correctly.
Song_30m_Pop_1_A_PopChords (A)
| A / / / | F#- / / / | D / / / | E7 / / / |
| A / / / | E7 / / / | F#- / / / | D / / / |
| A / F#- / | D / E7 / | A / F#- / | D / E7 / |
| A / E7 / | F#- / D / | A / E7 / | F#- / D / |
| F#- / / / | / / / / | B- / / / | / / / / |
| C# / / / | / / / / | F#- / / / | / / / / |
| A / / / | / / / / | D / / / | E / / / |
| A / / / | / / / / | D / E / | A / / / |
Here are all the keys n chords SGU's
http://www.pgmusic.com/zip/Pop%20UserTracks%2030%20minute%20template.zip
In reply to Tried the 2 Beta it's the by midimaker
That is possible; the BIAB format import function hasn't been touched in a very long time, and it's possible that BIAB has changed something about their format from when this was implemented so that something that used to work no longer does. Or something else might be unusual about this file. In any case, the workaround remains, fix up by hand whatever few chords get messed up.
In reply to That is possible; the BIAB by Marc Sabatella
Thanks, I don't need the workaround as I have the correct chords but others that have any SGU's need the correct Chords showing as the don't have BIAB and any files they create from MS will have the wrong progression.
Thanks everyone for your help it is much appreciated.
ps. the download link has the 27 pdf correct chord charts for these particular SGU's so to help work out the problem.
In reply to Thanks, I don't need the by midimaker
You might want to post an actual bug report to the Issue Tracker (in 2.0, Help / Report a Bug; for 1.3, just use the "Issue tracker" link in menu at right of this page). Include the relevant files and a link to this discussion.
I took a quick look under the debugger, and it sure seems like the file is specifying something very different form the F#m7 chord. But it display correctly in BIAB so obviously our understanding of the BIAB format is incomplete in some way. If you find any actual documentation on the internals of the format, that would be great to include in the bug report as well. If you can find some good documentation of the format within in the next few days (pictures of the chords is not the samel I need details on the internal representation) I could probably fix it for 2.0.
When I import a file from BIAB the chord symbols are one bar out of sync (to the left) with the notes. Are there any tricks to shift the chords one bar along (to the right) to marry up with the notes
In reply to When I import a file from by george w
You can select them all (right click, select similar element), Cut them (Ctrl+X), select the right note to start and paste (Ctrl+V). If it happens for every single BIAB file, it could be a bug in the biab import code, is it the case?
In reply to You can select them all by [DELETED] 5
Yes it is the case but I've just highlighted the start of the melody (second bar) by shift and left click on each bar (leaving the first one clear) then copy and highlight the first (clear bar with just the first chord above) and left click and paste. All the melody notes are shifted back one bar.
It seems a long drawn out process but it works and I'll try to find some short cuts...thanks for your help
In reply to Yes it is the case but I've by george w
Not sure what you mean about clicking each bar. To select a range takes only two clicks no matter how many measures: click the first, shift-click the last. This will select (and therefore move, when you do the cut and paste) the chord symbols along with the melody so it won't help directly. But you can then use the Selection Filter to exclude the chord symbols. Or, do as lasconic suggests above: select and move *only* the chord symbols by right-clicking one of them then choosing Select / All Similar Elements. Either way, the whole operation takes only a handful clicks total, regardless of how many measures.
In reply to Not sure what you mean about by Marc Sabatella
That worked...thanks a lot
Thanks for that, I'll give it a go