Here are some screen shots of those modes…with velocity values on the notes..
Triangles
Diamonds
Standard blocks…
Different shapes
Definitely something I would like to see in Podium after a quick play with it in Reaper.
Velocity values
I quite like the velocity values on the notes. Just drag the handle to adjust. But on the notes not beside them IMO. I see no harm in offering a choice between the two, like Reaper does though. I also like Podiums existing visual vertical resizing of drum notes (to reflect velocity changes) a lot , so I don’t want to lose that. Velocity values on drum notes would be something in addition to what we have already.
Highlighting
The horizontal highlighting would be similar to that in the images but it would include the drum row name on the far left (not necessarily the same colour) as more subtle standard highlighting (found elsewhere in Podium) would be fine for the drum row names but a simple horizontal band / highlight across the notes in a drum row that is the same colour as the tracks designated colour would help.
@Zynewave wrote:
I’ve now changed it so that the note audition will stop when you release the mouse button. Clicking shorter notes will still only audition the true note length, even if the mouse button is still being pressed.
Thanks! 8)
@Zynewave wrote:
@Trancit wrote:
A very elegant way I think, is the integration in the piano roll editor and to be able to switch via the “View” menu between the classic piano roll and the drum editor…the best integration at the moment is in Reaper, imho.
Is there anything in Reapers drum map handling that you prefer over the changes I’m currently making? If you want Podium to improve, you’ll need to give me some more details.
I don’t use Reaper so I personally cannot say but after a quick check maybe Trancit is referring to this menu in Reaper?
Maybe the modes (which are similar to the Editor Profile timelines in 2.31) which seems unlikely or maybe the Rectangle and Velocity options in that screen shot which would be nice to have.
But I guess Trancit can confirm or deny 🙂
Am I getting colder or warmer? 😉
Freezing 😯
Nah just kidding 😛
I like those ideas personally, the tie in with track templates makes sense and custom note naming looks equally useful.
Quick reminder though…
Please do add some kind of highlighting to the drum rows. Or a horizontal highlight when a drum row is selected. Currently a note or all notes on a row will be highlighted but the drum row to the left where the name is currently is not.
Ignore the Info box suggestion with the undo / redo buttons…the text is already there. 😛
@Zynewave wrote:
Beta4:
• Added a “note enable mode” option button to the drum map editor. When the option is selected all drum keys show an enable/disable button. When the option is deselected, all disabled drum keys are hidden. This is useful for setting up a compact drum map with only the drum sounds you intend to use.
• Added a menu button to the drum map editor. The menu contains commands for enabling all GM drum keys or enabling only notes used on the track. There are also copy/paste commands for applying the enable/solo/mute states to other tracks.
• Added solo and mute buttons to each key in the drum map editor. The solo/mute state is applied to all sequences playing on the track.
Excellent thanks!
Note that the new stuff is still not saved in the .pod file. The enable/solo/mute changes are also not added to the undo history yet. It’s a bit tricky, because the changes are applied to the tracks in the arrangement editor, but the edit action is done in the drum map editor. I think the undo should be done in the drum map editor, and not be listed in the arrangement editor undo history :-k.
I’m interested in your comments and suggestions.
I think…
…that it should be contained wthin the Drum Map Editors undo history. When you right click on those (undo / redo) buttons the history should include enable/solo/mute changes.
I will say though that it’s not nearly clear enough that right clicking is necessary to see the undo history list funnily enough.
💡 A small button could be placed next to those buttons to make it more obvious.
💡 Or….alternatively when you hover over either of those undo/ redo butttons the right click action can be suggested in Podiums info box (bottom left of the Podium UI). This seems the easiest way forward and maybe all that is needed…but at least that much is needed IMO for the arrangement view and Editor undo / redo buttons. 🙂
The drum rows
Could you please add a subtle highlight to drum rows when the mouse cursor is over them and when a row is clicked?
@Zynewave wrote:
I can add a preview on/off button on the left side panel of the piano roll and drum map editors. Would that solve the problems?
That would be useful definitely thanks…but in addition to that…
@LiquidProj3ct wrote:
The time that preview note is sounding should depend only of mouse click, and it should be independent of event lenght.
I totally agree with this. Good point.
@Zynewave wrote:
A muted track will of course mute any soloed drum notes on that track.
Ok on the same page…
When you emphasized “within a drum MIDI event” I thought you suggested that the solo/mute should be local to only that clip, and other clips on the same track should not be affected. From your latest comments, I take it you didn’t mean that.
Nooooooo. So that is where the confusion started. That was simply an example with one MIDI event. No more no less. Thats all. 🙂
We are definitely on the same page. 8)
@Zynewave wrote:
When I say they are properties of the track, then I mean they are just stored as hidden properties of the track object instead of the sequence object. They don’t interfere with normal track solo/mute. The difference is that when the drum map editor stores the note solo/mute states as track properties, then all sequences placed on that track will adopt the same solo/mute state. Like LiquidProj3ct, I prefer this behaviour.
That sounds like we are talking about the same thing…
“when the drum map editor stores the note solo/mute states as track properties, then all sequences placed on that track will adopt the same solo/mute state.”
I would definitely want a mute / solo command for a drum row to affect all MIDI sequences for that track but…if I then decide to Mute the Track (that holds the MIDI drum sequence/s ) that would override (so the drum lane would not interfere with the track mute) the drum row Mute track command, is that not what you are referring to here?
If not can you give me an example that explains / clarifies your suggestion?
@Zynewave wrote:
Ok, then the mute/solo state are properties of the note sequence object. Is this preferrable over having them properties of the track? And why?
Not sure what you mean here sorry. I don’t want to choose between the functionality of the track mute / solo over the drum row mute / solo can they not co – exist in Podium? With track Mute overriding drum row mute if need be ❓ ❓ ❓
Most drum plugin editors have mute/solo buttons in their UI, but I assume it’s more convenient to have the buttons close at hand when working with the pattern in the drum map editor. Is convenience the primary reason for you to have mute/solo in the drum map editor?
It is definitely much easier for me to work with the Mute Solo buttons like those in the drum map editor in the image I posted instead of a plugins M/S buttons. Also having dedicated drum rows with their own controls also paves the way for other drum lane specific settings like per lane /row quantise e.t.c Like Logic and Samplitude have.
Besides having mute/solo as a way of auditioning elements in a drum loop, would you use the mute/solo states as a fixed part in the final loop? In other words, would you leave some notes soloed/muted once you’re done working on the loop?
Yes defintely in some cases.
@Zynewave wrote:
LiquidProj3ct suggested this too. How should this work:
Should the note mute/solo work like the track mute/solo in the mixer? In other words, what should the mute/solo information be attached to? If the mute/solo state is a property of the track, then all sequences on the track will play with that mute/solo state. Switching back to a piano-roll editor, should then reset the solo/mute states I assume, or else you could get confusing situations where some notes in your piano-roll mysteriously is not playing.
Mute / Solo for drum rows (Kick Snare e.t.c) could work this way…
1. If you click on a MIDI track and it has three drum MIDI parts /events, and then you click on the Tracks Mute button the whole track and all parts of the MIDI events on the track are Muted as expected.
2. Using the Drum row Mute Solo buttons would solo or mute a single row within a drum MIDI event. So if I had snare and kick notes inside a MIDI event but then used the Kick row Mute button….
… that would mute the Kick notes within that MIDI event.
3. If the Track is already Muted then that should overide the drum row lane Mute / Solo controls to avoid confusion.
Edit: Ok, I see you added some info to your post about the “fold” button. I’ll consider that. What happens in Live when you remove the last event on a drum line: Does the line automatically disappear, or do you have to press “Fold” again?
I have to press Fold again.
This is the description Ableton have for the function…
An important feature of the MIDI Editor is the Fold button, located in the upper left corner.
Activating this button will immediately hide all rows, or key tracks, that do not contain MIDI
notes in any clips in the track. This is very useful when working with percussion kits, for
example, which are oftentimes mapped out along a keyboard in sections corresponding
to percussion type (e.g., snares grouped together two octaves down from hi-hat cymbals,
etc.). When working with a MIDI _le created by such a mapping, sometimes only one or two
of each type of percussion sound is used, and it becomes unnecessary to view the entire
keyboard range.
The Fold Button Extracts
Key Tracks Containing
Notes.
Ok thanks got it now, the dual “timeline” “timeline” commands confused me.
Now that your developers mouse cursor is hovering over drum maps 🙂 could you add the following functionality please…
1. Allow unused notes to be hidden by default? At the top and bottom of a list of drum note names is a list of notes that really should be hidden….
2. When using 5 or 6 drum lanes / notes it would be much easier to hide drum note names that are not being used. So all you see is the notes being used. Just 5 o 6 in this example. Ableton Live for instance has a fold button that will hide all rows that do not contain MIDI notes….
3. Mute Solo for drum note lanes as well please?
@Zynewave wrote:
Beta2 is up:
• A note sequence can now be shown in the drum map editor without having to create drum kit presets. The drum map will default to showing GM2 drum key names. The View menu in the editor lists both piano roll and drum map profiles. The selected profile type is remembered for each track.
Thanks for looking into this Frits. However I cannot find the Piano Roll and Drum Map profiles in the View Menu in the editor. What am I doing wrong? :-k
@Zynewave wrote:
I’m not a big keyboard shortcut user myself.
Me neither >handshake< tea or coffee? :P
So if you ignore the fact that I’m trying to make key shortcuts available, are there anything in my suggestions about snap, nudge, shuffle, etc. that is confusing?
No the commands in isolation are fine.
I’m not sure what you mean with “different types of markers”. If you compare the blocks lane in the video, with the marker lane in Podium, they are similar in appearance, except in Podium the markers are indicated by flags, and not bars that extend to the next marker. That is purely a visual presentation that I could change easily.
I said marker numbers in that post or earlier and should have just stuck to that. I did mean numbers of markers instead of different marker types sorry.
But yes… “That is purely a visual presentation that I could change easily” that would be a very nice change though, and would make a big difference visually. Thankfully it’s not difficult to do based on your comments.
Besides that, then my suggestion in the other topic indicated that there should be a marker at the start of each section. So if you in the blocks example would drag out a block to repeat 4 times, in Podium you would have 4 separate markers. If that turns out to be a problem, I can add a “length” setting to the marker properties, which will make it behave like in the blocks video.
Yes please. That could work. Thanks!
I have not seen evidence in the blocks video, whether it is possible to overlap blocks. An example: In one section of a song you may want to use repeated 2-bar patterns for drum loops, but in the same section you may want to have 4-bar longer evolving synth or bass patterns. The idea I described with marker linking would allow for that.
Not sure about overlapping in Record /Reason either with blocks :-k but ok…so Podium can / will be able to do that for sure with your marker idea. Sounds good on paper of course using it would be the best way to try it out. 🙂
@thcilnnahoj wrote:
Yay, CQSD’s posting again!
Hee hee… 🙂 I do read a lot of posts threads on this forum even though I don’t post so much 😛
Though I wonder if there really is a sudden need for some kind of “pattern-like” functionality in Podium.
Well..you could say that about pretty much any feature really. 😛 it’s all subjective at the end of the day but clearly that way of working is popular 🙂
Funnily enough I did post this FR back in 2006! 😯 So definitely not “suddenly”. 😉
Markers….
The idea/s you shared in tumults thread about markers IMO might best be used for this instead.
Part 2
Mutilple clips on a single Cell / Pod track
If you want to record another clip to the same track Podium could simply start recording from the edge of the last event or where a user specifies (Cursor placement). A grid /cell/pod could be used to store these clips to keep them tidy on the same track… optionally at least.
Bouncing
Simply route the Cell / Pod track to another track to bounce (to a group track for instance). I guess one could even convert any track anywhere in the signal chain into a cell track and go from there. One can also bounce any created ideas from Pod tracks into other tracks to arrange them further up the tree. Should you wish to work this way it could eliminate the need to move clips into place to arrange.
Simply start the song then trigger your Cell track clips and record them all into tracks further up the tree to create your arrangement which brings me to…
Trigger Headers
If you want to bounce say an Intro (keys and drums) for instance then a “Group Cell track” with headers (over cell tracks) could be renamed to suit. Click on those headers to trigger the cells vertically within the cell tracks beneath it.
Summary
There is much more that can be added here but I want to keep this simple. The idea here consists of two parts. Cell track to create ideas…other track types to record / bounce those ideas to.