2014-07-19 17:59 GMT+02:00 Francisco Vila :
> 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
On 19/07/14 15:18, David Kastrup wrote:
> Jan Nieuwenhuizen 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 b
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
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 i
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 | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com |
2014-07-19 16:19 GMT+02:00 David Kastrup :
> Francisco Vila writes:
>
>> El 19/07/2014 15:58, "Jan Nieuwenhuizen" 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 th
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 | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com
Francisco Vila writes:
> El 19/07/2014 15:58, "Jan Nieuwenhuizen" 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
___
Jan Nieuwenhuizen 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 repo
El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió:
>
> If MIDI has a way to encode
> clef information, then it's a bug.
>
Yes it has.
> Greetings,
> Jan
>
> --
> Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
>
> __
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 b
On 17/07/14 22:08, 'Jan Nieuwenhuizen wrote:
> Hi,
>
> Running
>
> lilypond bug.ly
> midi2ly bug.midi
> grep fis bug-midi.ly
>
> produces
>
> fis1
> fis'4. d8*5
>
> While technically correct, duration-wise, in printed output it
> will look as if the d2 has been omitted. In o
12 matches
Mail list logo
