Re: midi2ly produces 8*5, can we do better?
2014-07-19 17:59 GMT+02:00 Francisco Vila paconet@gmail.com: Yesterday I was messing with a MIDI imported in Rosegarden and edited a bass segment with the event editor, and one of the first events was a clef event. Let me look at it again tonight. Maybe the clef event was generated by Rosegarden on import? It was, and clef events are not exported back to midi files, not even as text events. Rosegarden events are not MIDI events. Sorry for the noise. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
James writes: Does it also matter that the clef is different when you run it back through midi2ly (at least it was for me running 2.19.8) Yes, for 2.16.2 also. I assume so in which case that is a second bug report right? If so, indeed a second report. For this one, the qualification of bug is even more disputable. If MIDI has a way to encode clef information, then it's a bug. Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
El 19/07/2014 15:58, Jan Nieuwenhuizen jann...@gnu.org escribió: If MIDI has a way to encode clef information, then it's a bug. Yes it has. Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Jan Nieuwenhuizen jann...@gnu.org writes: James writes: Does it also matter that the clef is different when you run it back through midi2ly (at least it was for me running 2.19.8) Yes, for 2.16.2 also. I assume so in which case that is a second bug report right? If so, indeed a second report. For this one, the qualification of bug is even more disputable. If MIDI has a way to encode clef information, then it's a bug. I don't think Midi can encode clefs. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Francisco Vila paconet@gmail.com writes: El 19/07/2014 15:58, Jan Nieuwenhuizen jann...@gnu.org escribió: If MIDI has a way to encode clef information, then it's a bug. Yes it has. Sure? I know there is a message for encoding the key signature, but the clef? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Francisco Vila writes: If MIDI has a way to encode clef information, then it's a bug. Yes it has. That's nice. If you have documentation you can point at, that would help. Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
2014-07-19 16:19 GMT+02:00 David Kastrup d...@gnu.org: Francisco Vila paconet@gmail.com writes: El 19/07/2014 15:58, Jan Nieuwenhuizen jann...@gnu.org escribió: If MIDI has a way to encode clef information, then it's a bug. Yes it has. Sure? I know there is a message for encoding the key signature, but the clef? Yesterday I was messing with a MIDI imported in Rosegarden and edited a bass segment with the event editor, and one of the first events was a clef event. Let me look at it again tonight. Maybe the clef event was generated by Rosegarden on import? -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Francisco Vila writes: Maybe the clef event was generated by Rosegarden on import? That would not surprise me. There is a lot of smart heuristics you can think of to amend midi2ly. Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
On Sat, 19 Jul 2014, Francisco Vila wrote: Sure? I know there is a message for encoding the key signature, but the clef? Yesterday I was messing with a MIDI imported in Rosegarden and edited a bass segment with the event editor, and one of the first events was a clef event. Let me look at it again tonight. Maybe the clef event was generated by Rosegarden on import? As far as I know there is not a commonly accepted MIDI file event for Clefs, like there is for Time Signature (FF 58 04) and Key Signature (FF 59 02). But I guess it is possible for a Sequencer like Rosegarden to put a special message in a Sequencer Specific Meta-Event (FF 7F). Or in a text event (FF 01) which, according to the Standard MIDI-File Format Spec 1.1 that I'm looking into now, can contain Any type of text containing anything. Personally I would not choose to let Lilypond/midi2ly be able to export or import such a non-standard Clef event. -- MT ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Martin Tarenskeen writes: As far as I know there is not a commonly accepted MIDI file event for Clefs, like there is for Time Signature (FF 58 04) and Key Signature (FF 59 02). But I guess it is possible for a Sequencer like Rosegarden to put a special message in a Sequencer Specific Meta-Event (FF 7F). Or in a text event (FF 01) which, according to the Standard MIDI-File Format Spec 1.1 that I'm looking into now, can contain Any type of text containing anything. Yes, that's an interesting perspective. Why not talk to the Rosegarder guys and gals? Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
On 19/07/14 15:18, David Kastrup wrote: Jan Nieuwenhuizen jann...@gnu.org writes: James writes: Does it also matter that the clef is different when you run it back through midi2ly (at least it was for me running 2.19.8) Yes, for 2.16.2 also. I assume so in which case that is a second bug report right? If so, indeed a second report. For this one, the qualification of bug is even more disputable. If MIDI has a way to encode clef information, then it's a bug. I don't think Midi can encode clefs. http://code.google.com/p/lilypond/issues/detail?id=4018 James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
