Hi

Here [1] a user complains about the MIDI track pane (in the arranger)
allows you to change patch, volume etc settings, but does not store them
automatically, making MusE forget them on a seek.

I consider this as a quirky behaviour, too; maybe we should default to
storing the changes immediately upon change?

For reverting the old behaviour (with the "store it now!" buttons), we
could have a config option, or possibly a checkbox directly in the track
pane?



This one [2] looks like a nasty bug; can someone of you reproduce this
(on your probably non-arch-systems?). Looks like a problem in an area i
haven't digged in yet. If you can reproduce, please fix it, if you
can't, i have an arch linux machine, then just tell me. thx.




[3]: "Bad timing" window needs a "don't show again" checkbox. YES, really :)




Additionally, there are lots of bugs which date back into 2007. Are they
really still an issue, or has just nobody closed them?




btw, how do i assign a bug/feature request to somebody (that is: me)?

greetings,
flo



[1]
https://sourceforge.net/tracker/?func=detail&aid=3569047&group_id=93414&atid=604222

[2]
https://sourceforge.net/tracker/?func=detail&aid=3546803&group_id=93414&atid=604222

[3]
https://sourceforge.net/tracker/?func=detail&aid=3565091&group_id=93414&atid=604225

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer

Reply via email to