Re: Is anyone maintaining midi2ly?

2018-01-04 Thread David Wright 
On Sat 30 Dec 2017 at 23:11:04 (+), Michael Ellis wrote:
> David Kastrup wrote:
> 
>- I get correct PDF output on 2.21.0 but a nonsensical wash of bar
>checks that appear to cater to 2/4 throughout.
> 
> Thanks for testing it, David.  What options did you use for midi2ly and
> lilypond?  My command lines were:
> 
> ./midi2ly.py -o meter.ly -n -V 1 meter.midi

What's odd to me is that all the midi2ly programs I have
are lacking the .py extension. They also object to being
fed a -n option. (Also, the program wouldn't normally be
found in the same directory as users' data files.)

> lilypond meter.ly
> 
> I only got one bar check complaint when LP processed meter.ly which
> contains:
> 
> TrackA = {
>   \numericTimeSignature\time 4/4  c'4 d'4 e'4 f'4  |  % orig
>   \numericTimeSignature\time 2/4  g'8 a'8 g'8 g'8 a'8 g'8 c''4  |  % orig
>   \numericTimeSignature\time 6/8  c''4 g'8 a'8 g'8 g'8 a'8 g'8  |  % orig
>   \numericTimeSignature\time 2/4  c''4 c''4 r2  |  % orig
> }

…whose format doesn't resemble the output I get from midi2ly with
$ ~/lilypond-2.19.80-1/bin/midi2ly -o /tmp/meter1980.ly /tmp/meter.midi 

Cheers,
David.
% Lily was here -- automatically converted by 
/home/david/lilypond-2.19.80-1/lilypond/usr/bin/midi2ly from /tmp/meter.midi
\version "2.14.0"

\layout {
  \context {
\Voice
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
\remove "Rest_engraver"
\consists "Completion_rest_engraver"
  }
}

trackAchannelA = {
  
  \time 4/4 
  
  \tempo 4 = 120 
  \skip 1 
  | % 2
  
  \time 6/8 
  \skip 2. 
  | % 3
  
  \time 2/4 
  \skip 2 
  | % 4
  
  \time 6/8 
  \skip 2. 
  | % 5
  
  \time 2/4 
  
}

trackA = <<
  \context Voice = voiceA \trackAchannelA
>>


trackBchannelB = \relative c {
  c'4 d 
  | % 2
  e f 
  | % 3
  g8 a g g 
  | % 4
  a g c4 
  | % 5
  c g8 a 
  | % 6
  g g a g 
  | % 7
  c4 c 
  | % 8
  
}

trackB = <<
  \context Voice = voiceA \trackBchannelB
>>


\score {
  <<
\context Staff=trackB \trackA
\context Staff=trackB \trackB
  >>
  \layout {}
  \midi {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2018-01-01 Thread Michael Ellis 
On Mon, Jan 1, 2018 at 5:08 PM Gianmaria Lari 
wrote:

> Ciao Michael,
>
> Thank you for your help, now it works!!
>
Great. I added some more explanatory text to help others not stumble over
it.


> Some suggestion about your test page:
> - The text box where you can write the music is too large. My screeen
> resolution is 1920x1080 but I cannot see at the same time this text box and
> the submit/play etc. buttons
>
I agree about the height when viewed in a wide window.  There are a couple
of ways you can control it.

   1. The text area is resizable. You should be able to drag it from the
   lower right corner to whatever feels comfortable.
   2. The font sizes are all specified in viewport width units so mobile
   users will have at least a fighting chance to read it.  On a desktop, if
   you shrink the width of your browser window the fonts and the rest of the
   layout will shrink to expose more of the vertical page.

The reason for the tall text area is to support users who want to enter
extended music samples.

- The panel with "Choose pitch characters" should be put in the same panel
> with the others buttons (submit, play etc.); IMHO it is too far from the
> rest.
>
That's worth considering.  Thanks!

I've just added a couple of new examples you can paste and try. One is a
few bars of a two part duet voiced for flute and guitar. The other is a
little percussion pattern for bass drum,  snare and ride cymbal.

Cheers,
Mike
-- 
Write music faster with Tbon.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2018-01-01 Thread Michael Ellis 
On Sat, Dec 30, 2017 at 6:08 PM  wrote:

> David Kastrup:
> > Michael Ellis  writes:
> ...
> > > The MuseScore output is correct and matches the tempo and meter items
> > > embedded in the original midi file (attached).  I've also verified
> with 2 different
> > > DAW's (Reaper and Logic X) that the midi file is imported correctly.
>
> The midi file matches your msc2-meter-example.png, I can show you
> (Michael) a dump if you like.

Thanks, Karl. Always good to have a sanity check.


> Nice idea to have c--c mean c8. c16 which is much more error prone to
> type.
>
 Also easier to edit if you change your mind.  To make it a triplet rhythm,
just delete a dash to get c-c, or add a dash to get a quintuplet 60/40
swing, i.e. c--c-

You could probably change your python program to output lilypond code
> directly.
>
I'm hoping an enthusiastic contributor will send a pull request. Ditto for
musicXML.  :-)
Seriously, I decided to focus on midi output because it's the only thing
that almost all the other music software will import, more or less.

Thanks for the interest and feedback and sorry to take a couple of days to
respond.  I'll plead New Years celebrations (and also adding GM instrument
support to tbon.)
Cheers,
Mike
-- 
Write music faster with Tbon.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2018-01-01 Thread Michael Ellis 
On Sat, Dec 30, 2017 at 6:11 PM Michael Ellis 
wrote:

> David Kastrup wrote:
>
>- I get correct PDF output on 2.21.0 but a nonsensical wash of bar
>checks that appear to cater to 2/4 throughout.
>
>
> I'll try upgrading to 2.21 and see if that makes any difference.
>

Hmmm, I don't see a 2.21 binary for OS X.  I downloaded 2.19.80.  Got
bogged down trying to run mid2ly as a standalone under python 3.5.
-- 
Write music faster with Tbon.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2017-12-30 Thread David Kastrup 
Michael Ellis  writes:

> David Kastrup wrote:
>
>- I get correct PDF output on 2.21.0 but a nonsensical wash of bar
>checks that appear to cater to 2/4 throughout.
>
> Thanks for testing it, David.  What options did you use for midi2ly and
> lilypond?

None.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2017-12-30 Thread Michael Ellis 
David Kastrup wrote:

   - I get correct PDF output on 2.21.0 but a nonsensical wash of bar
   checks that appear to cater to 2/4 throughout.

Thanks for testing it, David.  What options did you use for midi2ly and
lilypond?  My command lines were:

./midi2ly.py -o meter.ly -n -V 1 meter.midi
lilypond meter.ly

I only got one bar check complaint when LP processed meter.ly which
contains:

TrackA = {
  \numericTimeSignature\time 4/4  c'4 d'4 e'4 f'4  |  % orig
  \numericTimeSignature\time 2/4  g'8 a'8 g'8 g'8 a'8 g'8 c''4  |  % orig
  \numericTimeSignature\time 6/8  c''4 g'8 a'8 g'8 g'8 a'8 g'8  |  % orig
  \numericTimeSignature\time 2/4  c''4 c''4 r2  |  % orig
}

It was on the 6/8 line in the above which contains 8 eighth-notes.

I'll try upgrading to 2.21 and see if that makes any difference.


On Sat, Dec 30, 2017 at 5:15 PM David Kastrup  wrote:

> Michael Ellis  writes:
>
> > Hi, It's been a few years since my last post here.  I'm wondering about
> the status of
> > midi2ly.  I just tried the version that came with 2.18.2 and it seems to
> handle meter
> > changes incorrectly.  Here's a short example produced from a midi file
> imported into
> > MuseScore 2.1
> >
> > msc2-meter-example.png
> >
> > and here's the result of processing what midi2ly produced from the same
> file
> >
> > ly-meter-example.png
> >
> > The MuseScore output is correct and matches the tempo and meter items
> > embedded in the original midi file (attached).  I've also verified with
> 2 different
> > DAW's (Reaper and Logic X) that the midi file is imported correctly.
> >
> > The application that produced the midi file is called tbon. It's a
> shorthand notation
> > language I wrote for projects where fast notation entry is more
> important than
> > having the full capabilities of LilyPond.  If you're curious about tbon,
> go to
> > https://github.com/Michael-F-Ellis/tbon . The README has a link to a
> live online
> > demo.
> >
> > I'd really rather use LP than MuseScore for the times when I want to
> engrave the
> > output from tbon since LP still produces better looking scores, imo, but
> not being
> > able to handle meter changes is a showstopper.
>
> I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks
> that appear to cater to 2/4 throughout.
>
> --
> David Kastrup
>
-- 
Write music faster with Tbon.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2017-12-30 Thread karl 
David Kastrup:
> Michael Ellis  writes:
...
> > The MuseScore output is correct and matches the tempo and meter items
> > embedded in the original midi file (attached).  I've also verified with 2 
> > different
> > DAW's (Reaper and Logic X) that the midi file is imported correctly.

The midi file matches your msc2-meter-example.png, I can show you
(Michael) a dump if you like.

> > The application that produced the midi file is called tbon. It's a 
> > shorthand notation
> > language I wrote for projects where fast notation entry is more important 
> > than
> > having the full capabilities of LilyPond.  If you're curious about tbon, go 
> > to
> > https://github.com/Michael-F-Ellis/tbon . The README has a link to a live 
> > online
> > demo.

Nice idea to have c--c mean c8. c16 which is much more error prone to 
type.

You could probably change your python program to output lilypond code
directly.

> > I'd really rather use LP than MuseScore for the times when I want to 
> > engrave the
> > output from tbon since LP still produces better looking scores, imo, but 
> > not being
> > able to handle meter changes is a showstopper.
> 
> I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks
> that appear to cater to 2/4 throughout.

And here with 2.19.16.

The bar checks fails because midi2ly puts in barchecks in the wrong 
places, don't know why.

///

Regarding your subject line question, I don't know.
I make my own midi -> ly converter though, currently in an experimental
leap...

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Is anyone maintaining midi2ly?

2017-12-30 Thread David Kastrup 
Michael Ellis  writes:

> Hi, It's been a few years since my last post here.  I'm wondering about the 
> status of
> midi2ly.  I just tried the version that came with 2.18.2 and it seems to 
> handle meter
> changes incorrectly.  Here's a short example produced from a midi file 
> imported into
> MuseScore 2.1
>
> msc2-meter-example.png
>
> and here's the result of processing what midi2ly produced from the same file
>
> ly-meter-example.png
>
> The MuseScore output is correct and matches the tempo and meter items
> embedded in the original midi file (attached).  I've also verified with 2 
> different
> DAW's (Reaper and Logic X) that the midi file is imported correctly.
>
> The application that produced the midi file is called tbon. It's a shorthand 
> notation
> language I wrote for projects where fast notation entry is more important than
> having the full capabilities of LilyPond.  If you're curious about tbon, go to
> https://github.com/Michael-F-Ellis/tbon . The README has a link to a live 
> online
> demo.
>
> I'd really rather use LP than MuseScore for the times when I want to engrave 
> the
> output from tbon since LP still produces better looking scores, imo, but not 
> being
> able to handle meter changes is a showstopper.

I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks
that appear to cater to 2/4 throughout.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Is anyone maintaining midi2ly?

2017-12-30 Thread Michael Ellis 
Hi, It's been a few years since my last post here.  I'm wondering about the
status of midi2ly.  I just tried the version that came with 2.18.2 and it
seems to handle meter changes incorrectly.  Here's a short example produced
from a midi file imported into MuseScore 2.1

[image: msc2-meter-example.png]

and here's the result of processing what midi2ly produced from the same file

[image: ly-meter-example.png]

The MuseScore output is correct and matches the tempo and meter items
embedded in the original midi file (attached).  I've also verified with 2
different DAW's (Reaper and Logic X) that the midi file is imported
correctly.

The application that produced the midi file is called *tbon*. It's a
shorthand notation language I wrote for projects where fast notation entry
is more important than having the full capabilities of LilyPond.  If you're
curious about tbon, go to https://github.com/Michael-F-Ellis/tbon . The
README has a link to a live online demo.

I'd really rather use LP than MuseScore for the times when I want to
engrave the output from tbon since LP still produces better looking scores,
imo, but not being able to handle meter changes is a showstopper.

Thanks,
Mike
-- 
Write music faster with Tbon.



meter.midi
Description: MIDI audio
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user