@Zynewave wrote:
Those that haven’t tried the beta versions can get an idea of the note map feature from the new YouTube video I’ve just uploaded:
That is a great usability improvement when working with GPO 4. Great stuff Frits. π
@Zynewave wrote:
After reading your post again, I see that you meant track template files. As I’ve previously said, I haven’t yet added the new settings to the pod file format. When I’ve done this, then of course the drum map setting will be remembered for the track.
I didn’t know that! π
@Zynewave wrote:
I’ve adjusted it so that the zoomed event height must be at least 12 pixels instead of 8 pixels, before the velocity hot spot area becomes active.
THanks, much better!
@Zynewave wrote:
It seems unintuitive to me that you can point/click besides something to edit it. It will also present problems if you have events joining the event you want to edit. In that case I guess the outside resize area will disappear in FL, or else you cannot click the joining event? You also can’t click with the pencil tool right next to an event to place a new event. You’ll have to click further away, and then move the event back so that it joins with the other event.
In the way you say it, yes, you’re right, but FL Studio can do it, I don’t know the reason because I don’t have it installed now, but its editors behaviour are almost a reference for the most of hosts. Although podium surpass it with this release in the most of aspects.
edit: question, what’s the purpose of “Note Enabled Mode” button on piano roll? If none it should be hidden/disabled or that it can enable and disable keys without go inside menu.
Frits, there is a bug when you switch between drums roll alt+clicking in a ghost note from another drum roll. It seems that names aren’t updated
@Zynewave wrote:
Anyways, try the new beta 14:
The events no longer change height according to velocity in the piano roll mode.
There is a new “Highlight line when mouse cursor is on timeline” option in the notes region dialog.
Thanks a lot for these changes. I know I’ve been opposed to some changes and only later came to realize their usefulness, but I hope you can see why these ones might’ve not been ideal for everyone.
And the new video is great. Shows how powerful this feature really is, espcially if it works combined with track templates, as expected.
Okay, I got a little lost editing drum maps during testing. It would be nice if the note row highlighting (in the drum map) followed the selected note in the note map properties dialog. Or if the the default (General MIDI?) note names were displayed ghosted in the dialog.
A few more small findings:
– Due to the notes’ height changing in the drum map, it looks and feels like the velocity handle (using the pencil tool) is outside the note. Also, selecting “small” notes can be done by clicking above or below them. I only bring it up because the thing you said is unintuitive is happening here… and it is, at first, but it’s definitely better than having to hunt pixels. π Don’t get me wrong, I really do like the note height feature in the drum map!
– The help text for the velocity edit mode buttons still reads “… to set default velocity of 64.”
– Not a problem, but the area where you can click the “keys” to preview at different velocites seems pretty small in the drum map, compared to the piano roll.
@thcilnnahoj wrote:
The note row highlighting – besides that it isn’t consistently bright on white and black rows […]
Wasn’t very clear on this one, so here’s a big picture to emphasize what I mean. The highlight overlay thingy would need to have different brightness depending whether it’s on white, black, or disabled keys.
@LiquidProj3ct wrote:
question, what’s the purpose of “Note Enabled Mode” button on piano roll? If none it should be hidden/disabled or that it can enable and disable keys without go inside menu.
It will show/hide disabled notes, just like in the drum map mode. It doesn’t have the individual note enable buttons that the drum map mode has. The video I posted shows that notes can be hidden in the piano roll mode as well.
@LiquidProj3ct wrote:
Frits, there is a bug when you switch between drums roll alt+clicking in a ghost note from another drum roll. It seems that names aren’t updated
Confirmed. It’s the key names from plugins that aren’t updated. Will fix this.
@thcilnnahoj wrote:
Or if the the default (General MIDI?) note names were displayed ghosted in the dialog.
Done.
– Due to the notes’ height changing in the drum map, it looks and feels like the velocity handle (using the pencil tool) is outside the note. Also, selecting “small” notes can be done by clicking above or below them. I only bring it up because the thing you said is unintuitive is happening here… and it is, at first, but it’s definitely better than having to hunt pixels. π Don’t get me wrong, I really do like the note height feature in the drum map!
The “outside” focus click problems I commented on was in the cases where the outside area can overlap other selectable events. This is not the case here, as the clickable area is confined within the maximum available line height. Would you suggest that the painting of the low velocity events should be modified to show the larger selectable frame?
– The help text for the velocity edit mode buttons still reads “… to set default velocity of 64.”
Fixed.
– Not a problem, but the area where you can click the “keys” to preview at different velocites seems pretty small in the drum map, compared to the piano roll.
Now corrected. The area shrunk too much when you increased the zoomed line height.
@thcilnnahoj wrote:
The note row highlighting – besides that it isn’t consistently bright on white and black rows […]
Wasn’t very clear on this one, so here’s a big picture to emphasize what I mean. The highlight overlay thingy would need to have different brightness depending whether it’s on white, black, or disabled keys.
I’ve changed the highlighting to use the select color instead of increasing brightness of the background. This also makes it possible to see the highlighting on very bright backgrounds, such as with the “Paper” color scheme.
Beta16 is up, with the latest discussed bug fixes and minor UI tweaks.
@Trancit wrote:
Had that already posted in the support forum, but deleted there, because here is a better place:
For me adjusting velocities is much easier by seeing the current value with numbers…
In the editor we have this nice numeric window for “mouse cursor”…would it be much work to implement a numeric value for note velocity????
I’m sorry, but the velocity value readouts didn’t make it into this round of piano roll updates. I’ll save it for a future update. There have been a lot of changes to the piano roll in this release, so I think it is a good idea to let users work with what we have now, and then provide feedback based on their experience with the new editor.
@Zynewave wrote:
@Trancit wrote:
Had that already posted in the support forum, but deleted there, because here is a better place:
For me adjusting velocities is much easier by seeing the current value with numbers…
In the editor we have this nice numeric window for “mouse cursor”…would it be much work to implement a numeric value for note velocity????
I’m sorry, but the velocity value readouts didn’t make it into this round of piano roll updates. I’ll save it for a future update. There have been a lot of changes to the piano roll in this release, so I think it is a good idea to let users work with what we have now, and then provide feedback based on their experience with the new editor.
No problem…itΒ΄s not a big issue 8)
Trancit
I have rewritten the note sequence chapter in the guide:
http://www.zynewave.com/wiki/doku.php?id=guide:note_sequence