
User Details
Username: | dennisdesantis |
Website: | dennisdesantis.com |
Facebook: | None provided |
Twitter: | twitter.com/dennisdesantis |
Soundcloud: | www.soundcloud.com/dennisdesantis |
Account Status: | enabled |
Member since: | Nov 13 2009 |
About dennisdesantis: | |
(report this profile) |
Devices by dennisdesantis
Total Downloads: 23,138
Comments by dennisdesantis
Comments
Hi davidcaporale, Thanks for the kind words. It might be possible make a device that could select clips in this way, but I think it's conceptually different enough that it wouldn't make sense as a mode of Selection Filter, which is really just about notes. (It's true that Live has no way to select multiple non-adjacent clips, but the device might be able to solve this issue another way. I'll think about this!) Best, Dennis |
Posted on January 04 2023 by dennisdesantis (report comment) (Goto Comment) |
Hi hatyn, I *think* duration is working as expected, but bugs are certainly possible! Can you send me a Set or a video that demonstrates what you're experiencing, and what's not working as you expect? One thing - the device doesn't really have anything to do with the start and end markers in the clip. It operates on the selected notes (or every note if there's no selection), no matter where they are in the clip. Best, Dennis |
Posted on October 11 2022 by dennisdesantis (report comment) (Goto Comment) |
Hi pluto, I'm not sure I understand your request. Is the idea that it should capture a certain number of random values and then repeat them? There isn't really a "state" at all right now; it just picks a new random value when it gets a new note. So there's no way to determine how many values would be in the loop. Something like a parameter sequencer would probably work better in this case. Best, Dennis |
Posted on June 07 2022 by dennisdesantis (report comment) (Goto Comment) |
Hi prizzle9, Unfortunately, that's not really possible. It could be possible to enable keyboard mapping for particular buttons, but not for a multi-button state like the one you've suggested. Best, Dennis |
Posted on April 09 2022 by dennisdesantis (report comment) (Goto Comment) |
Ok, I've just updated the device. The Expand button can now be MIDI or Key mapped. |
Posted on February 10 2022 by dennisdesantis (report comment) (Goto Comment) |
Hi njassal, Are you using Live 11 or Live 10? I think this is working as expected with different skins in Live 11. I'm not sure about 10 though. Best, Dennis |
Posted on February 03 2022 by dennisdesantis (report comment) (Goto Comment) |
Hi folks, Please use https://maxforlive.com/library/device/7871/selection-filter-2 if you're using Live 11.1 or higher. Best, Dennis |
Posted on February 01 2022 by dennisdesantis (report comment) (Goto Comment) |
Hi Pat, The Live 11.1 beta was announced today, and I'm working on a version of the device that I thing should solve all of the compatibility issues with Live 11. If you're testing 11.1 and would like to try out the updated version of the device, please let me know. Best, Dennis |
Posted on September 28 2021 by dennisdesantis (report comment) (Goto Comment) |
Hi markusschloesser, Unfortunately, it's not actually possible for me to update this to be completely compatible with Live 11 yet. The "older process" referred to in that warning dialog is the only way to affect the selection of notes. The updated method for working with notes supports MPE, but it doesn't allow note selection to be managed. As soon as it becomes possible for me to update this, I will! Best, Dennis |
Posted on April 11 2021 by dennisdesantis (report comment) (Goto Comment) |
Hi Drewskee, I wonder if a better solution for this particular case would be to use multiple instances of the device, rather than one mapped to multiple parameters. Since the device also passes the raw MIDI note, any additional instance further down the chain will create a different random value. What do you think? |
Posted on February 19 2021 by dennisdesantis (report comment) (Goto Comment) |
And one more bug...I think the Phaser rate knob is non-functional. The Feedback control seems to work, however. |
Posted on May 01 2015 by dennisdesantis (report comment) (Goto Comment) |
Oh, one more request: it would be nice to see values for the various parameters (especially the synced delay time, envelope/LFO amounts, etc.) |
Posted on May 01 2015 by dennisdesantis (report comment) (Goto Comment) |
This is really well done. Excellent work. One bug and two requests: Bug: - sometimes, the HP branch doesn't work after instantiation. It seems to "wake up" after adjusting the sequencer a bit, but before this, it outputs no sound at all. The BP and LP don't have this issue. Request 1: - in the Reason version, it's possible to disable the individual filters, but still leave the rest of the chain active (meaning the gate and all of the effects.) It would be great to have this option here. Request 2: - in the Reason version, some of the built-in patterns have longer sustained passages where the gate remains open. It would be nice to be able to reproduce this, perhaps using x0x style ties. |
Posted on May 01 2015 by dennisdesantis (report comment) (Goto Comment) |
This is possible to do, and is actually available in the related devices I mention (https://maxforlive.com/images/screenshots/?ss=note%20seq.jpg&id=129 and https://maxforlive.com/library/device/5832/note-trigger-parameter-step-sequencer).
I deliberately didn't put this in my version, though, because I thought it would be a bit complicated to have these options alongside the options for disabling steps.
Can you describe a bit about what you want to do that you can't do by disabling specific steps?