Andrey,
I really like UI for the track selection and "operations". Often the
tracks are unlabeled so seeing exactly which staves disappear in the
score with each check mark is quite helpful. It will also encourage more
exploration for other MIDI settings and hopeful helps users get a nicer
score. Below are some thoughts as I used the new GUI for the first time.
Main UI issues
1. When I went to Display > MIDI Import Panel nothing happened
initially. Then I noticed I needed to drag the panel up from the bottom.
Is the panel height set to zero by default?
2. My main concern is that this UI does not use the typical File > Open
method that is standard for every other file type. I would recommend
removing the custom file picker UI (the left side of your mockup).
Instead, the rest of your UI could appear after the user opens a MIDI
file via File > Open. The current "Import" button would be relabeled
"Apply" (or something similar).
This approach would also eliminate the need for a menu item in
the Display menu (this menu is already crowded). In other words the new
MIDI import UI would appear automatically when someone imports a MIDI
file (when it is needed and helpful), but not distract when it is unneeded.
Minor issues:
1. When I dragged the panel up from the bottom, it shrunk the Navigator,
instead of the page view. I expected the Navigator to stay the same
height (so it would remain usable) and the page viewing section (which
has the most available space) to become smaller.
2. The MIDI panel close button uses a different image than the Edit >
Find close button. Also the MIDI panel title and close button is
right-aligned while the Edit > Fine close button is left-aligned
3. I noticed the "Instrument" column is often blank (since the MIDI file
often does not label each track). I wonder if there is value in showing
the sound name (based on General MIDI), either in a separate column or
as a substitute when the instrument label is missing. Of course this
would be a low priority feature compared to tuplet recognition and other
MIDI import features.
Other thoughts:
1. Having it as a docked panel is nice but not strictly necessary. If
some of the issues mentioned above (such as default height and
competition with the Navigator) or not easy to solve, a floating dialog
would suffice.
2. I haven't had a chance to read over the features planed for MIDI
import but it would be worth thinking through the UI for the completed
feature set. Some questions that came to mind were how the LH/RH
separation would work if you wanted to select a different split point,
where the quantization settings would go, etc. Probably you have some
preliminary thoughts on this already.
David
On 5/2/2013 11:13 AM, andrey.m.tokarev wrote:
> This is a GUI panel for MIDI import - frontend for different midi import
> functions:
> https://github.com/musescore/MuseScore/pull/325
>
> One can choose midi file to import and specify operations to perform on
> each midi track (selectable) during the import. More operations can be added
> in the future.
>
> Here is how the panel looks like:
> http://imageshack.us/photo/my-images/849/midiimportpanel.png/
>
> It can be toggled in Display menu. Also it appears when midi file import is
> invoked.
>
> Thanks David Bolton-2 for his thoughts on instant feedback for midi import:
> http://dev-list.musescore.org/GSoC-MIDI-proposal-draft-tp7578046p7578048.html
>
>
>
> --
> View this message in context:
> http://dev-list.musescore.org/A-GUI-panel-for-MIDI-import-tp7578066.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
