Greg Compiler Convert 2 Midi Issue (Gregorio; TeX; GABC; Chant; Audio; Scores)
  • +JMJ+

    [SOLVED]

    -----------------------
    [Edit 2025-01-06]

    Although I was able to compile a midi file for the originally problematic score fragment by removing all square brackets, "[ ]", and their contents, this solution has not worked for any of the EF II Vespers antiphons for next Sunday, Feast of the Holy Family.

    I've attached my gabc file for the first antiphon
    If anyone would trouble themselves to view it and let me know if they have any ideas as to why this Greg program might be running into issues compiling it, I'd be very grateful!


    -----------------------
    Hello!

    I'm seeking help for a problem I'm having converting GABC to midi.

    Context
    - I installed downloaded Gregorio from here:
    https://github.com/gregorio-project/gregorio/releases/tag/v6.0.0
    - When I opened gregorio-6_0_0-setup.exe, I followed the prompt to download and install install-tl-windows.exe from here:
    https://www.tug.org/texlive/windows.html#install
    (This took all night)
    - Then I unzipped greg.zip which I had downloaded from here:
    https://www.dcmembers.com/bgmcoder/download/greg/

    My Goal
    - To break up EF Sunday Vespers antiphons into little midi files, phrase by phrase.
    I'm not good at sight reading, but I'd like to practice singing these in little pieces when I'm on the go, without having to point and click inside the Neumz app.

    Actual Issue
    - Now, I'd taken the GABC for "Ante Luciferum Genitus" and Greg made the midi of the whole antiphon just fine.
    Then I broke the GABC into five parts/five GABC files.
    - Greg was able to create a midi for all but the fifth GABC file.
    Would anyone be able to help me pursue a solution?

    Below I'll share some screenshots comparing a success against the failure in question, in case anything pops out to more experienced eyes.

    Here is the relevant GABC:
    %%
    (f3) mun(e_[uh:l]f)do(h) ap(g)pá(e)ru(g)it.(f.) (::)

    Thanks for any help!

    AMDG,
    Stephen

    P.S.
    I just solved it, see third screenshot.
    The problem was the text: [uh:l]
    Somehow it had appeared between the e_ and f in the first word as seen at the bottom of original post.
    After the fix, the GABC text reads:

    %%
    (f3) mun(e_f)do(h) ap(g)pá(e)ru(g)it.(f.) (::)

    and the midi compiles fine.

    Thanks anyway!
    Maybe this will help someone else.
    I would welcome comment from anyone who's seen this before or knows where those [uh:l] characters came from.

    Pax Domini,
    Stephen



    success.png
    1152 x 951 - 53K
    fail.png
    1223 x 968 - 59K
    fix.png
    1230 x 648 - 18K
    an--post_triduum--solesmes_1961.1.gabc
    482B
    an--post_triduum--solesmes_1961.1.txt
    482B
  • MatthewRoth
    Posts: 2,440
    I think that it is problematic that it cannot handle [uh:l] for the episema. More is found in the gabc documentation at the Gregorio Project site and in the GregorioRef manual.

    There is some resistance to this code being in the Gregobase version, but I don't mind it; the onus is on projects to keep up with Gregorio, not the other way around, and Jacques has been at it making all sorts of adjustments for years now. The time to complain was then, when we had Olivier Berten's attention (we briefly did, in fact, have some discussion where a lot of problems came up but where nothing was ultimately done, and I find more and more things every time I use the site).
  • Thanks, Matthew! I went ahead and removed any [uh:l] instances from next Sunday's antiphons, but greg can't seem to compile midi files for any of these.
    I'd really love to be able to use this feature.

    Anyone know of an easier way to accomplish this goal?
    Or why the "play midi" function of Illuminare Score Editor seems to have been removed?
  • MatthewRoth
    Posts: 2,440
    They are trying to deprecate the original editor.

    I had no idea that this existed and I only have wound up running full Gregorio on macOS. But getting this to Gregorio 6.0 to include all of that adjustment to the gabc seems to be in order. There may be a way for it to ignore it in the same way that a (Z) or (z) would be ignored. (I assume that this is what it does.) Contacting the developer would be the way to fix it if the developer is interested…