Please familiarise yourself with the forum, including policy on feature requests, rules & guidelines

Global controller assignment for all presets ?

0

Global controller assignment for all presets.
That would be so important.

Comments

  • 0
    rezareza los angelesModerator, Beta Tester Posts: 645

    could you elaborate how this behaves in practice?

  • 0
    pitchblenderpitchblender Glasgow, ScotlandPosts: 36

    I think @bunkim means a kind of MIDI controller template which could be exported and imported between projects, or permanently available for all projects, perhaps also as an option in the settings menu? We could map our controllers to say the synth parameters once and it would work for any other synth preset on the same MIDI channel(s).
    Perhaps a MIDI implemetation chart could be er... implemented as a standard for external mapping too.
    I'd love to see this happen although the lack of any sort of manual for the community firmware and its rapid evolution makes it difficult enough for me!
    Hope this is what's being said, apologies if not.

  • 0
    seangoodvibesseangoodvibes Beta Tester Posts: 56

    @pitchblender said:
    I think @bunkim means a kind of MIDI controller template which could be exported and imported between projects, or permanently available for all projects, perhaps also as an option in the settings menu? We could map our controllers to say the synth parameters once and it would work for any other synth preset on the same MIDI channel(s).
    Perhaps a MIDI implemetation chart could be er... implemented as a standard for external mapping too.
    I'd love to see this happen although the lack of any sort of manual for the community firmware and its rapid evolution makes it difficult enough for me!
    Hope this is what's being said, apologies if not.

    This is already exists in the community firmware. It’s called midi follow.

    https://github.com/SynthstromAudible/DelugeFirmware/blob/community/docs/features/midi_follow_mode.md

  • 0
    pitchblenderpitchblender Glasgow, ScotlandPosts: 36

    Wow thanks for pointing that out! I noticed this feature but hadn't looked properly at its features.

    BUT! I thought MIDI follow only works for the active or selected clip (hence the word 'follow')?

    I now know we can set up MIDI learn (from the old firmware) for each clip but we lose these settings with new projects (and old projects without same MIDI learn done).

    I've just read the MIDI follow github page and my point is that I don't want some MIDI controllers to follow the current clip (even if you can press any clip to then focus the MIDI follow mode on another clip/track) because often I want both hands free for playing notes/controlling non-selected multiple clip MIDI data.

    MIDI follow does seem powerful (I'm going to test it out with MIDI Fighter Twister) but it seems to be only for whatever clip/track is currently active (or is being focussed on by keeping finger down on main pads to select specific clip/track) and all other clips/tracks can only be MIDI accessed by using the old MIDI learn function, which cannot be transferred to other projects.

    Am I still missing something here?

  • 0
    seangoodvibesseangoodvibes Beta Tester Posts: 56

    @pitchblender said:
    Wow thanks for pointing that out! I noticed this feature but hadn't looked properly at its features.

    BUT! I thought MIDI follow only works for the active or selected clip (hence the word 'follow')?

    I now know we can set up MIDI learn (from the old firmware) for each clip but we lose these settings with new projects (and old projects without same MIDI learn done).

    I've just read the MIDI follow github page and my point is that I don't want some MIDI controllers to follow the current clip (even if you can press any clip to then focus the MIDI follow mode on another clip/track) because often I want both hands free for playing notes/controlling non-selected multiple clip MIDI data.

    MIDI follow does seem powerful (I'm going to test it out with MIDI Fighter Twister) but it seems to be only for whatever clip/track is currently active (or is being focussed on by keeping finger down on main pads to select specific clip/track) and all other clips/tracks can only be MIDI accessed by using the old MIDI learn function, which cannot be transferred to other projects.

    Am I still missing something here?

    @pitchblender said:
    Wow thanks for pointing that out! I noticed this feature but hadn't looked properly at its features.

    BUT! I thought MIDI follow only works for the active or selected clip (hence the word 'follow')?

    I now know we can set up MIDI learn (from the old firmware) for each clip but we lose these settings with new projects (and old projects without same MIDI learn done).

    I've just read the MIDI follow github page and my point is that I don't want some MIDI controllers to follow the current clip (even if you can press any clip to then focus the MIDI follow mode on another clip/track) because often I want both hands free for playing notes/controlling non-selected multiple clip MIDI data.

    MIDI follow does seem powerful (I'm going to test it out with MIDI Fighter Twister) but it seems to be only for whatever clip/track is currently active (or is being focussed on by keeping finger down on main pads to select specific clip/track) and all other clips/tracks can only be MIDI accessed by using the old MIDI learn function, which cannot be transferred to other projects.

    Am I still missing something here?

    I don’t think you’re missing anything

    I think I misunderstood what you’re looking for

    To confirm: you want a way to quickly learn the non midi follow way all the parameters for a specific instrument

    Almost like a midi learn preset

    The other alternative would be to midi learn all the same cc’s as midi follow but only to the active instrument

  • 0
    pitchblenderpitchblender Glasgow, ScotlandPosts: 36
    edited October 7

    Yes I think, but I'll describe what I'd like in a different way;

    If I have a certain MIDI controller set up to behave like a Roland SH-101's physical sliders mapped to it (for example) and have a synth preset on the Deluge that I can control with same MIDI setup (say a synth preset or MIDI clip controlling a Roland S-1 external synth), I'd like to just have it linked to the clip/track permanently within each project, so I can develop muscle memory when using that preset across all instances in all projects, effectively using the external MIDI controller like it was a hardware synth. Maybe if the user maps a controller using the existing LEARN+AUDITION shortcut, these learned MIDI settings could be saved with that same preset to be accessible in other projects? Maybe with a dot or extra suffix or something after the name of the preset?

    I'd rather have that available than having to remember which shortcut to press on the Deluge to engage the follow mode for a specific track on the Deluge, as well as having to memorize the ridiculous shortcuts on the S-1 as well. In this case I'm used to using the Roland SH-01a but had to sell it, so I eventually got an S-1 to replace it and used a picture of an SH-101 to copy the layout to an external controller as best as I could, but it's all on paper currently and I thought I'd see if the Deluge could easily be mapped in this way as MIDI mapping any device takes ages. Hence my query about keeping permanent, static MIDI mappings across projects, which the 'MIDI follow' does not do as it only applies to currently selected clip/track and only one MIDI channel at a time.

    Phew! Please let me know if this is now 100% clear and if it's worth suggesting for the Community firmware as I'd really like the Deluge to do this and think other folk would benefit from this feature too.

    EDIT: p.s. I just thought that another function of this approach would be the conveninece of being able to share system-wide MIDI mappings with other folk. I have used DJTechTools MIDI maps in the past and controller-specific maps for DAWs but it would be so much less hassle to have a simple single file for each controller which the Deluge can read on boot-up and be ready to go in any project without programming or further faffing about with key combos. I know some folk are offering Deluge MIDI maps already but they're also too complex for me to implement and use. And yes I do still appreciate all the effort so far, it's truly amazing :)

    Post edited by pitchblender on
  • 0
    bunkimbunkim germanyPosts: 6
    edited October 13

    no, I mean only the 2 deluge controllers mapping intern for vol, cutoff, etc.. **
    **thats nothing to do with eleborate midi follow and extern controlls

    give all these synthpatches the same 16 controllmappings intern automaticlly .
    cutoff, reso ,vol1 vol2, attack, lfo ...like a hardware synthesizer.
    otherwise, you will have to spend 3 weeks configuring all sounds.
    easy same 16 parameter for all patches for deluge

    Post edited by bunkim on
  • 1
    seangoodvibesseangoodvibes Beta Tester Posts: 56
    edited October 20

    @pitchblender @bunkim

    So I added a fix that partially addresses this issue.

    Basically if you midi learn a synth or kit affect entire params and then change the preset after, previously you would lose your midi learn and would have to do the learning all over again.

    Now your midi learn will persist across preset changes.

    So that’s one issue.

    The other issue that I think you’re mentioning is about having to go through this midi learning process for new projects or for new instruments you add to a song.

    One way we could achieve this is by having a dialog window open when you hold learn + send a cc that asks you if you want to learn midi follow mappings or a specific midi learn preset

    If you select the latter, it will prompt you to browse and load a midi learn preset

    After making your selection your controller will be automatically learned to that clip and to the parameters that have been loaded per midi follow or the midi learn preset

    For the midi learn preset, you could hold save + press learn to save a midi learn preset

    Saving the midi learn preset would save the current midi learn settings learned to the clip

    The midi learn preset would also need to distinguish between song midi learn, synth midi learn, audio clip midi learn, kit affect entire midi learn and kit row midi learn so that when it gets loaded it loads the right stuff

    Post edited by seangoodvibes on
Sign In or Register to comment.