Zynewave's Forum Page

@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.

@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.

@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 small bug when you adjust timming. Don’t know how to reproduce it, but I have a pod file that I could send you if you want:

D’oh #-o

I’ve found that the backup of the original timing is not saved correctly to the pod file. Negative offset adjustments are reset to zero. As a consequence the “undo timing adjustments” command and the “calculate adjustments from original timing” option will not work reliably. I’m fixing this by simply ignoring the original timing backup when loading older project files. Project files saved with 2.31 should save and load the timing adjustment backup correctly.

@LiquidProj3ct wrote:

but… why not allow two movements (velocity & size) while dragging, ie, if you’re dragging towards left then you drag size, but if you actually want change velocity you don’t need to cancel the operation just move the mouse towards up more than left, so it would work in the same way that ALT key while dragging (it restricts movement)

You cannot reliably move one or two pixels either horizontally or vertically. So you end up with the same problem, that you will often adjust the opposite size or velocity than you intended. It’s easier with the Alt key direction lock, because you often move events a fair distance away.