wrong midi-sound when saved and engraved about frescobaldi HOT 8 CLOSED

When a new MIDI file is created, it is loaded by Frescobaldi and all channels are reset. The MIDI commands that set the current sound (the program changes) are in the beginning of the file, they are missed when you scroll the music position first. I could improve this situation by searching for certain MIDI commands when scrolling the music pointer and send them to the MIDI port, e.g. program changes.

from frescobaldi.

this would be very nice. it would fastener my speed of composing with frescobaldi.

now, i have a last issue: when frescobaldi/lilypond have engraved, is it possible to have a second play-button that recognized the measure-position? for example: i work at measrue 7 and midi has to play at measure 6. after engraving it resets to zero. but: it would be nice if a kind of marker would be set and midi will play at measure 6 (or at 15 seconds ...) after engraving.

i know, these are no basic function and not really necessary. it would make working with frescobaldi a little bit faster and smoother.

and again: great work! i love frescobaldi!

from frescobaldi.

Some kind of A-B repeat function, like some CD players have might be an idea?

This would add one button 'Repeat'. When clicking it the time-position is stored as start-time. When clicking again, the time-position is stored as end-time. Then the play and stop buttons automatically resume at the start-time and stops at the end-time. These time positions would survive loading a new MIDI file so that they continue to work after engraving. Clicking Repeat a third time would switch repeat off.

Another idea would be some kind of generic time marks that could be set on the slider.

from frescobaldi.

yes, that´s it. a little bit better as i suggested (with AB).

the time marks will be a good idea, too. to compare blocks of music, for example. or simply to navigate in a more complex way through the midi. would be nice to have it for daily work!

i would prefer the AB-solution.

ps: did you hier of this project (a new frontend for lilypond): http://www.laborejo.org/ ... it´s just a kind of pre-pre-alpha ...

from frescobaldi.

did you hear of this project (a new frontend for lilypond): http://www.laborejo.org/ ... it´s just a kind of pre-pre-alpha ...

Very nice, and from a first glance it seems well-designed and promising. It would even be possible to share code as it's license is, like Frescobaldi's, GPL. E.g. the ncwtxt import.

from frescobaldi.

Laborejo is Python3, but that should only be a minor disturbance.
nwctxt import is only a draft and wip btw.

Nils
http://www.laborejo.org

from frescobaldi.

Hi Nils :)
Frescobaldi is already coded very much with Python 3 in mind, and as soon as I get PyQt4 on my machine in Python 3, I'll make it so that Frescobaldi works with Python 2.6 up to 3.2 (and higher).

from frescobaldi.

Good luck with poppler then :|

from frescobaldi.