Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,216 through 1,230 (of 5,965 total)
  • in reply to: Preview 2.31: Slide/zoom key shortcuts #18332
    Zynewave
    Keymaster

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

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18331
    Zynewave
    Keymaster

    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.

    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.

    in reply to: MIDI note preview problem #18330
    Zynewave
    Keymaster

    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?

    in reply to: MIDI note preview problem #18326
    Zynewave
    Keymaster

    In the piano roll editor:

    Menu: View > Customize Region > Piano Roll

    Disable the “audition selected and edited notes” option.

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18319
    Zynewave
    Keymaster

    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.

    Zynewave
    Keymaster
    in reply to: Preview 2.31: Slide/zoom key shortcuts #18315
    Zynewave
    Keymaster

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

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18311
    Zynewave
    Keymaster

    @Conquistador wrote:

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

    A muted track will of course mute any soloed drum notes on that track.

    In your original post you wrote:

    @Conquistador wrote:

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

    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.

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18308
    Zynewave
    Keymaster

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

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18304
    Zynewave
    Keymaster

    A couple of general questions:

    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?

    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?

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18303
    Zynewave
    Keymaster

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

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18299
    Zynewave
    Keymaster

    @Conquistador wrote:

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

    I wanted the default map to include all 128 notes, in case you have a specialized drum map that goes beyond the GM convention. Or even if you just switch to the drum map for a regular note sequence, for specific editing.

    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.

    How should Podium know which ones you want to use? When you start out with an empty sequence, it can’t hide all drum lines. For specific drum map layouts, the way to do it is still with drum kit presets, where you can arrange the keys any way you like. I’m going to improve that feature as well, so that you don’t have to do it the old way.

    3. Mute Solo for drum note lanes as well please?

    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.

    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?

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18296
    Zynewave
    Keymaster

    @Conquistador wrote:

    @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

    The two “Timeline” profiles you have in your screenshot are the piano-roll and drum-map. In previous versions these profiles were never listed in the same menu, so that’s why they don’t have the editor type in the profile name. In the latest beta I have extended these profile names to “Piano Roll – Timeline” and “Drum Map – Timeline”. Use the “restore default editor profiles” setup command to get the new names.

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18292
    Zynewave
    Keymaster

    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.

    I know some of you have waited a long time for updates to the drum map editor. For various reasons, I made some experiments, and found that it was fairly easy to make the above adjustment. Now you no longer have to resort to voodoo magic to conjure the drum map editor 😉

    Note that the track flag for drum map editor is not yet saved in the project file.

    To keep the momentum going: Which drum plugins do you know that support custom drum key names?

    in reply to: Preview 2.31: Slide/zoom key shortcuts #18291
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Does it not bother you that the mouse cursor changes to the vertical zoom cursor, when you hold down Ctrl+Shift for transposing octaves?

    That never bothered me. I won’t be standing in the way if you want to change it, just want to say again that Ctrl (moving notes) together with Shift made sense to me, while Alt doesn’t really fit. I don’t have any alternatives to offer, either. 😐

    I need to check the code for conflicts with other key shortcuts, but how about Shift+Up/Down instead of Alt+Up/Down for transposing octaves?

Viewing 15 posts - 1,216 through 1,230 (of 5,965 total)
© 2021 Zynewave