Beta 13 is up. A little later than I estimated, but I ended up doing a complete overhaul of the piano roll and drum map editing. This wasn’t on my original plan for 2.31, but I’m glad it’s done. I’m pleased with the face-lift. 🙂
This beta will change the editor setup in the Podium.ini file, so if you plan to go back to a previous release, please first take a backup of your Podium.ini file. Otherwise you will need to use the “restore default editor profiles” command when going back to 2.30.
There are too many changes to list them all, but the major one is:
The old “drum kit” preset option is now gone, and so is the old drum map editor. There is now a “Notes” region which combines the old piano roll and drum map regions.
I still need to do some testing, but I don’t plan to make more changes for 2.31. Only thing missing is to implement the saving of note map properties to the pod file.
Let me know what you think of the redesigned note editor.
Well, here’re some quick thoughts from your resident nitpicker. 🙁 😛
First things first… the rounded edges and velocity-height relationship are a matter of taste, I guess – not exactly my favorite change ever. Have to see if I can warm up to it… 😉
The note row highlighting – besides that it isn’t consistently bright on white and black rows – doesn’t really serve much purpose, and will most of the time clutter the view, in my opinion. I can see the use when hovering over the keyboard, so you get an indication of which notes would be selected.
Notes themselves are highlighted as well, but just barely noticable. So I wonder why at all, especially since you seemed to step away from highlighting individual elements since the new group panel.
Lastly, I think I’d prefer an extra button instead of a menu entry for toggling between piano roll and drum map, for the reason that it’d be more immediately noticable.
Edit: Umm, I must also say that, while the ‘wide event’ mode is a good idea, it doesn’t work as well as Liquid showed in FL Studio (for the purpose of selecting short notes). It still only leaves 1 px to select a really short note, while the resize handles are at least 4 px wide…
Just an observation. I usually don’t use the pencil tool myself. 😉
Bug: there seem to be weird things happening to the key ‘zones’ when some notes/keys are disabled:
@thcilnnahoj wrote:
The note row highlighting – besides that it isn’t consistently bright on white and black rows – doesn’t really serve much purpose, and will most of the time clutter the view, in my opinion. I can see the use when hovering over the keyboard, so you get an indication of which notes would be selected.
Notes themselves are highlighted as well, but just barely noticable. So I wonder why at all, especially since you seemed to step away from highlighting individual elements since the new group panel.
Well I think it’s useful, not to see the key, but to see other far notes that’re in the same row. You could adjust easily relative pitch between notes that’re pretty far, of course, it depends of the music you’re doing 🙂
@thcilnnahoj wrote:
Lastly, I think I’d prefer an extra button instead of a menu entry for toggling between piano roll and drum map, for the reason that it’d be more immediately noticable.
Or change the icon of the button, because all options inside that menu seems relevant to drum roll.
@thcilnnahoj wrote:
Edit: Umm, I must also say that, while the ‘wide event’ mode is a good idea, it doesn’t work as well as Liquid showed in FL Studio (for the purpose of selecting short notes). It still only leaves 1 px to select [<--- I think you want to say MOVE instead SELECT] a really short note, while the resize handles are at least 4 px wide…
Just an observation. I usually don’t use the pencil tool myself. 😉
Yes, it doesn’t work as I thought 🙁 I continue with same problem when i try to move short notes with the mouse, and that’s is pretty frecuent. It’s easiest switch to select tool that use the wide event mode. Select with pencil tool is easy, the difficult part is moving the note.
And the wide option seems irrelevant when the notes have this size, the size with I usually mangle:
Please fix this option so it will be as easy as FL Studio move short notes
About the drum roll seem great newbies will be grateful! 😀 I need to do more testing. I only miss the ability of move up/down each file, but it isn’t very important.
@thcilnnahoj wrote:
First things first… the rounded edges and velocity-height relationship are a matter of taste, I guess – not exactly my favorite change ever. Have to see if I can warm up to it… 😉
The benefit of the rounded edges, is that it’s easier to discern start and end of individual events, if you have a series of joining 16th notes for example.
The note row highlighting – besides that it isn’t consistently bright on white and black rows – doesn’t really serve much purpose, and will most of the time clutter the view, in my opinion. I can see the use when hovering over the keyboard, so you get an indication of which notes would be selected.
Notes themselves are highlighted as well, but just barely noticable. So I wonder why at all, especially since you seemed to step away from highlighting individual elements since the new group panel.
The note highlighting could be made more clear I guess. You have event highlighting in the tracks region as well, so that was what I tried to immitate. I’ll probably add it to the curve editor eventually. It can be helpful if you’re trying to hit a small note event within a series of joining notes.
Lastly, I think I’d prefer an extra button instead of a menu entry for toggling between piano roll and drum map, for the reason that it’d be more immediately noticable.
I’ll consider it. All the buttons that are currently in the side panel are all editor mode buttons. All the commands in the menu will affect the note map properties in the track.
Edit: Umm, I must also say that, while the ‘wide event’ mode is a good idea, it doesn’t work as well as Liquid showed in FL Studio (for the purpose of selecting short notes). It still only leaves 1 px to select a really short note, while the resize handles are at least 4 px wide…
Just an observation. I usually don’t use the pencil tool myself. 😉
Is it not sufficient that the width of the box increases when you zoom out vertically? Even if I implemented the “outside” resize handles, I still think the wide box has its uses. You can be zoomed so far out that even quarter notes will be so thin that it’s difficult to click them. And then there are the ultra-short click events you can get if you import some drum loop MIDI files. This wide event option was meant as a replacement for the previous snap grid minimum size that was used in the old drum map editor. Or the Triangle/Diamond shape options you have in some other hosts.
@Zynewave wrote:
Is it not sufficient that the width of the box increases when you zoom out vertically?
Didn’t know that, however I don’t see any logic relationship between vertical zoom and width increases. It would be more logic if the width would depend on event lenght and horizontal zoom (i think)
Even if I implemented the “outside” resize handles, I still think the wide box has its uses. You can be zoomed so far out that even quarter notes will be so thin that it’s difficult to click them. And then there are the ultra-short click events you can get if you import some drum loop MIDI files. This wide event option was meant as a replacement for the previous snap grid minimum size that was used in the old drum map editor. Or the Triangle/Diamond shape options you have in some other hosts.
Yes it has its use, I was waiting something to move easily notes without switching tools in piano roll windows as I posted before, although
edit: or do the relationship simple. If event < 15 pixels (or any comfortable size to be grabbed without problem) then increase its lengh until 15 pixels.
@LiquidProj3ct wrote:
Well I think it’s useful, not to see the key, but to see other far notes that’re in the same row. You could adjust easily relative pitch between notes that’re pretty far, of course, it depends of the music you’re doing 🙂
I guess so, though I can’t see a personal use for it at the moment. I just hope there’s nothing similar planned for the arrangement view, as I feel that it’ll quickly get annoying if everything under the mouse cursor is highlighted and jumps at you.
@Zynewave wrote:
The benefit of the rounded edges, is that it’s easier to discern start and end of individual events, if you have a series of joining 16th notes for example.
Honestly, I think the difference is pretty small. It’s just an aesthetics thing for me, so don’t mind it unless others dislike it, too. It is easier now to discern overlapping notes (it sometimes looked like there were three instead of two notes before), I’ll give you that.
What annoys me more is the note height now being dependant on velocity levels. This was fine for me in the drum map, where you would probably hide all unused note rows, so the vertical zoom level can be set higher – there’s no doubt that it’s useful in this case.
In the piano roll – with a little higher than default zoom level – the differences are so marginal that I’d rather have full-height notes back instead of sacrificing even a little visibility for something that conveys no information to me (or at worst even ends up confusing, as there’s no guaranteed equal spacing between notes on different rows anymore). Besides, I think the note coloring already does a perfectly fine job at this by itself.
Is it not sufficient that the width of the box increases when you zoom out vertically?
Well, that’s not very obvious now, is it? 🙂
I’ll let you and Liquid work this one out as I don’t experience the problem myself. I just mentioned it because, since I already was giving negative feedback, I thought I might as well take the blame for getting on your nerves with this. 😆
Something that seems to have fallen under the table, or maybe was never mentioned, is the possibility of reordering keys in the drum map. For example, the standard GM mapping has hi-hat strokes and tom-toms on alternating keys (probably because it’s easier to play?). If you don’t use an actual keyboard to play drums, though, you might want to have all of one instrument’s articulations placed next to each other in the drum map. Maybe in a future update? O:)
@thcilnnahoj wrote:
Is it not sufficient that the width of the box increases when you zoom out vertically?
Well, that’s not very obvious now, is it? 🙂
Have you turned off popup help? [-X
Quote: “Widen the clickable frame of note events so that the frame width is minimum the same size as the zoomed line height. This makes it easier to click and edit short duration events.”
Something that seems to have fallen under the table, or maybe was never mentioned, is the possibility of reordering keys in the drum map. For example, the standard GM mapping has hi-hat strokes and tom-toms on alternating keys (probably because it’s easier to play?). If you don’t use an actual keyboard to play drums, though, you might want to have all of one instrument’s articulations placed next to each other in the drum map. Maybe in a future update? O:)
Yes, distant future.
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.
Fixed a bug with displaced piano keys when notes have been disabled.
And more adjustments to the pencil tool on events: When the event is thinner than 16 pixels, then the resize handles are removed from the bottom half of the event. This means it is easier to move the event, and the event can still be resized by pointing to the side edges on the upper half of the event. Perhaps it sounds confusing, but I think it works alright.
Furthermore, I’ve added a resize area on the upper edge of note events, for dragging velocity. I’ve done this because I plan to remove the “drag velocity or size” Alt+Click option. This never works reliably for me, as I probably 1/3 of the time accidentally drag a pixel in the wrong direction of what I really want.
@Zynewave wrote:
And more adjustments to the pencil tool on events: When the event is thinner than 16 pixels, then the resize handles are removed from the bottom half of the event. This means it is easier to move the event, and the event can still be resized by pointing to the side edges on the upper half of the event. Perhaps it sounds confusing, but I think it works alright.
Now I can move events very fast, without struggle. It was a very intelligent idea, thanks! 😀
Furthermore, I’ve added a resize area on the upper edge of note events, for dragging velocity. I’ve done this because I plan to remove the “drag velocity or size” Alt+Click option. This never works reliably for me, as I probably 1/3 of the time accidentally drag a pixel in the wrong direction of what I really want.
I don’t use it either, I use alt+click to delete notes, 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)
I’m sorry to say this, but after few hours using the piano roll I find the upper edge a little disturbing, it eats too much space on medium-thin (height) notes, the same problem I had with resize but now in another direction, could it be optional? I usually set velocity with the regular bars. Or have less pixels? or have some pixel outside the event (and you could do it to resize too)?
Just curiosity, why you don’t like have pixels outside the note? I think you could save lots of adjustments. I hope this proposal doesn’t annoys you, I only try to suggest the most direct and easy workflow from my experience from old hosts. O:)
Now with current drum system I was working on new track templates but I see that editor status (as enabled keys / drum map mode) isn’t saved in template. Could it be possible?
It’s a little boring each time I looking for inspiration for a new song open Poise or Nepheton go inside a menu and select “drum map mode” and then the enabled keys instead starting to write notes right away
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:
http://www.youtube.com/watch?v=u8t7uRAFn-E
I’ll probably make another note map video using the drum map editor as example.
Comments are welcome.
@LiquidProj3ct wrote:
Now with current drum system I was working on new track templates but I see that editor status (as enabled keys / drum map mode) isn’t saved in template. Could it be possible?
It’s a little boring each time I looking for inspiration for a new song open Poise or Nepheton go inside a menu and select “drum map mode” and then the enabled keys instead starting to write notes right away
First time I browsed your post, I thought you meant the exported note map files in the Note Map dialog. Good idea, I thought 🙂 , so I’ve now added a drum map mode setting to these files. Importing a note map file will then automatically set the proper piano roll or drum map mode on the track.
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.
@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.
@LiquidProj3ct wrote:
I’m sorry to say this, but after few hours using the piano roll I find the upper edge a little disturbing, it eats too much space on medium-thin (height) notes, the same problem I had with resize but now in another direction, could it be optional? I usually set velocity with the regular bars. Or have less pixels? or have some pixel outside the event (and you could do it to resize too)?
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.
Just curiosity, why you don’t like have pixels outside the note? I think you could save lots of adjustments. I hope this proposal doesn’t annoys you, I only try to suggest the most direct and easy workflow from my experience from old hosts. O:)
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.
Beta15: All the note map properties are now saved in the .pod file.
Please make a backup of your projects, before saving them with this beta, just in case you need to go back to Podium 2.30.
I think that’s it for 2.31. I’m going to spend a couple of days testing for bugs. Let me know if you find any unresolved issues, or have last-minute suggestions for changes.