Zynewave's Forum Page

Beta5 is up.

@LiquidProj3ct wrote:

– Is there any way to unmute and unsolo all keys? If there isn’t, please add one.

You can now do it by Shift+clicking the enable/solo/mute buttons, similar to how it’s done with the track solo/mute buttons.

@Zynewave wrote:

Can you confirm that, when used in other host software, the plugin will update the drum key names accordingly?

I can confirm you (with Drumazon/Nepheton) that FL Studio piano roll updates automatically each time you do a rename inside drumazon. Reaper piano roll updates when you re-open the piano roll, keeping the user names instead plugin keynames.

I had a quick look at Drumazon/Nepheton pdf manual, but could not see how you would change the note names. How do you do it?

Crash: Trying to open any Drum Roll made with previous Podium versions

Fixed. 😳

2. Ghost notes for drums are showed now in regular Piano Roll (and they shouldn’t)

Fixed.

@LiquidProj3ct wrote:

Thanks 🙂 I’d like to point that autocenter when opening an editor doesn’t work with Drum Roll

Are you sure? It works fine here.

If there are any selected events, they will be centered. If the selected events extend beyond the vertical space, then the topmost selected event is aligned to the top of the display. If there are no selected events, then all events within the displayed zoom range will be centered.

Beta3 is up. Some bug fixes, and:

Added a vertical zoom slider to the drum map editor. This replaces the “line height” setting in the drum map region properties.

Tomorrow I’ll start experimenting with solo/mute.

@thcilnnahoj wrote:

I must confess I’ve never used the drum editor before, so it’s entirely new to me.

Oh no!, I’m going to be flooded with bug reports the coming days! 😉

– Why are the “keys” arranged bottom to top compared to the piano roll?

You know, it made sense years ago when I implemented it :-k . I guess I was thinking that the most prominent drums (kick, snare, etc.) should be at the top when you first open the editor. If I implement a feature to hide unused drum lines, I think it’s ok to swap them around so low notes are at the bottom. If anyone objects to this, please post why.

– The grid/snap value seems to adjust all notes’ visual length – huh? A 1/16 note looks like a 1/4 note if you select that grid setting.
I don’t know how other sequencers’ drum maps work, but for me it’s important to be able to set note lenght (and see it). For example, Poise has a “note on” mode, in which a sample pad is triggered only as long as the note is held.

All events are displayed with a minimum size of the grid value. There’s a historic reason for this: Years ago many MIDI drum files had very short note durations, because drum machines back then usually only needed a trigger note to play the entire drum sound. So if those ancient MIDI drum files should be displayed with true durations, you would only see very thin drum notes that would be difficult to click and edit.

Maybe this need to be updated as well. Instead of using the grid value as the minimum duration, it is perhaps better to have a minimum pixel width setting, and a way to display that the true length of the event is perhaps shorter than the clickable event. Suggestions are welcome.

@Conquistador wrote:

@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 lane mute / solo can they not co – exist in Podium? With track Mute overriding drum lane mute if need be ❓ ❓ ❓

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.

@Conquistador wrote:

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

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?