Adam Wilson

Forum Replies Created

Viewing 15 posts - 121 through 135 (of 164 total)
  • Author
    Posts
  • in reply to: Feature request: Random pick from chord pool #1535
    Adam Wilson
    Participant

    So you will give polyphony larger than 1 for the random-pick-from-pool feature a try, Gabriel? That would be awesome…

    Not familiar with the code, but when the random-pick feature is enabled and thus instructed to pick N notes/rests from the chord pool, a simple approach could be to first create a new local copy of a Step object on the stack, assign it the N notes randomly picked from the actual Step object, assign it the STA values from the first N note/rests, and use that local copy for the rest of the note generating
    code.

    Regarding the hard monophony feature you built into the current beta, I think that can/should go once this new approach is implemented. It would only confuse users, as both UI elements can be used to reach the same goal. Or am I mistaken?

    in reply to: Feature request: effector attribute restart track #1534
    Adam Wilson
    Participant

    LDT wrote:

    Quote:
    Robert, this is what I am refering to:

    http://genoqs.net/index.php?option=com_joomlaboard&Itemid=50&func=view&id=375&catid=6

    And to recap: I think the above could accomodate track trigger as well.

    I think a "unique selling point" (now being a salesman, haha) is that even if you have a small keyboard controller, you can have the 7 pages and 4 tracks (that may be spread all over your matrix) that you want to be able to trigger in your particular project, set up on your keyboard on adjacent keys to your own taste. This is as I see it the only way to achieve some kind of playability.
    Anybody who has ever set up (or played with) multiple sampled loops assigned to a keyboard will know that putting the assigned keys close together is what makes sense. If you have assigned C#1, D#3, B#3, A5 and F5, you do not have playability.
    This playability again transfers to when you want a track in Octopus to trigger pages/tracks via virtual midi: Turn the pitch knob one or two steps, and you trigger another page. Otherwise you would have a hard time "finding" the relevant pitches with your pitch knob.

    Hi Lars, sorry for not being clear enough, but your proposal, extended with track triggering is indeed what I like to see. The idea that you can freely assign up to 127 notes to pages and tracks, in a fashion that allows for range of intuitively assigned notes is very tempting, yes. Much more preferred over a set of statically assigned notes, spread over the full range of the keyboard.

    I truly dig the idea of using a virual MIDI port to trigger stuff in other pages. Oh man, life *can* be good! ;)

    in reply to: Feature request: effector attribute restart track #1529
    Adam Wilson
    Participant

    I REALLY like the feature being discussed here!

    I agree with Lars and would prefer notes for triggering, couldn’t be more direct.

    I agree with Ripe that the possibility to also trigger tracks within a page would yield more fun stuff, whithout the need to lift those tracks out of the page and asign them their own page in order to get the track triggered. It would get messy very soon, data wise. So both pages and tracks should be addressed, imo.

    But could you define what it means to ‘trigger a track’? Will the track get ‘started’ somehow? That is, unmuted and retriggered to the first step? And will the track loop then? How to switch it off?

    in reply to: Feature request: Random pick from chord pool #1530
    Adam Wilson
    Participant

    Nice new approach to the chord data!

    While it definitely can be used to insert some rests in the chord, it could also be used to set the polyphony of a step, also used for the random-pick-from-pool feature, and now for polyphony values larger than 1! I don’t think however it can do both. Let me see:

    chord-size == note-count: normal behavior.

    chord-size > note-count: inserts one or more rests.

    chord-size < note-count: this could be the polyphony indicator as well as well as the trigger for the random-pick-from-pool feature, but… there’s no way to specify rests now, and I want those in.

    I really, really think the random-pick-from-pool with polyphony larger than 1 (random chords!) will be super cool, and you just found a really nice way to specify this. So my suggestion would be:

    1. Use the 5-step button press cycle to set a note as on-1, on-2, on-3, rest, and off in the note circle.

    2. Use your new chord-size approach to set polyphony between 1 and 7. If polyphony is smaller than number of notes+rests defined in the chord, the random-from-chord-pool feature is enabled for that step, with indicated polyphony.

    Btw, the links from the email notification to the replaced threads are all broken.

    Post edited by: robert, at: 2008/05/09 08:18

    in reply to: Feature request: realtime record non-looping, etc #1517
    Adam Wilson
    Participant

    I definitely like the one-shot record suggestion. Great for live situations too. I also like the record-loop-overwrite mode.

    The record trigger mode is the last one on my list atm, but I understand the need.

    All great suggestions, but the list of record modes it getting a bit too long for me to remember, unless the color/blink coding helps me remember somehow. We would get:

    1. record-loop-overdub.
    2. record-loop-overwrite.
    3. record-oneshot-overwrite.
    4. record-oneshot-overdub (while we’re on it, heh).
    5. record-oneshot-overwrite-trigger.
    6. record-oneshot-overdub-trigger (while we’re on it, again).
    7. etc.

    This almost looks like loop/oneshot, and overdub/overwrite, and play/trigger could be preset modes, set somewhere else. That would just give you a single ‘record’ command again, lol. Otoh, I’d like the idea of having a couple of these variations available, quickly. Just not that many I guess. Would I be able to remember 5 different modes?

    in reply to: Step copy/paste in page mode #1510
    Adam Wilson
    Participant

    Lol, looks like the feature is there already!

    in reply to: Step copy/paste in page mode #1496
    Adam Wilson
    Participant
    in reply to: No “undo recording” when in sync #1497
    Adam Wilson
    Participant

    My guess is that adding general Undo functionality will be a lot of work, unless it’s as easy as quickly making a copy of the pages involved before the edit action takes place. That will probably take too much time and memory. So you want to intelligently save the the state of the objects/attributes involved and be able to recover equally intelligent. That’s why I think that IF a general Undo will make it into the Octo, it will be implemented gradually, one edit action at a time.

    Anyway, the record undo function could be the first of the general undo functions indeed. And it would be preferred to find a Undo button (combo) that both is more intuitive than ‘Play’ and reflects the more general nature of the future Undo mechanism.

    Call me a sissy, but I would have really liked to be able to undo that RMX accident, especially in a live situation. Yes, guitarist don’t have an undo, nor do drummers. But they also don’t have this persistance nature of notes in a page. ;)

    Post edited by: robert, at: 2008/05/08 08:21

    in reply to: No “undo recording” when in sync #1493
    Adam Wilson
    Participant

    I see a button in the lower left of the outer circle with a big X. Could that be used, possibly combined with another button?

    in reply to: Feature request: Random pick from chord pool #1489
    Adam Wilson
    Participant

    Yes, I’m aware of the semantic differences of the AMT knob in both cases. You are right, but I kinda liked the posibilities. Suddenly the AMT step event could be used to control the amount of note randomness when picking them out of the pool. But it’s a bit messy yes.

    We need more attributes I guess. And a Shift button that allows a hole new range of attributes selected with the Shift-attribute combo key. :)

    Good news on the rests in the chord pool! You managed to squeeze out a free bit from the note pitch data fields?

    in reply to: No “undo recording” when in sync #1490
    Adam Wilson
    Participant

    I had to look this up in the manual. You actually press Play to undo a record session? That doesn’t sound intuitive at all. IIRC, I have software that recognizes the Play button during record as a ‘okay, recording completed, stop recording and let me listen to the result’ kinda thing. I think it’s Logic.

    Don’t we have another button available for Undo (and maybe a more general Undo)? That would also solve this problem, heh.

    What about a combo like REC and the CLR mutator button? Something along those lines…

    in reply to: Step copy/paste in page mode #1491
    Adam Wilson
    Participant

    Let’s not talk about trading esoteric functions right away, maybe the UI space is already there. I mean, I *like* that stuff! ;)

    So what happens when you grab a step in Page mode? (Still don’t have the Real Thing guys…) Wouldn’t it simply be possible to have the CPY and PST mutator functions enabled then? I would almost think this functionality is already there!

    Post edited by: robert, at: 2008/05/07 20:55

    in reply to: Feature request: Random pick from chord pool #1483
    Adam Wilson
    Participant

    I just read the section on Step events. Cool, will have to play with those. Anyway, it looks like the step’s AMT property is only used to control the effect of the step events on the step.

    I’m proposing to use this same AMT value as a factor on the amount of randomness used to pick another note (or rest) from the pool. The higher the AMT value, the wilder the random pick. With a AMT value of 0, the base note will be picked in all cases.

    I mentioned this before in this thread, but I now think I have a knob for this. I also wonder if the GRV property can be used to play a role…

    Anyway, when using step events, the AMT and GRV properties should work as they’ve always done. Don’t change anything there. Having AMT used for both the random-from-pool feature *and* step events can have fun effects. For starters, it would mean that I can modulate the random-from-pool randomness by using AMT step events… I think, lol.

    Fun?

    in reply to: Page lenght and repeats #1486
    Adam Wilson
    Participant

    Guys, I really think we should find a way to have a track-retrigger-at-page-length feature, enabled by something else than the page-length < 16 condition. I’d love to see the original idea of page ‘cuts’ implemented, but I think that the proposed way to implement this in the UI seriously butchers the free flowing continuun model of tracks of individual lengths.

    In my childish mind, getting the page cutting done would involve two steps:

    1. Enable track retrigger mode some way (some knob).
    2. Start playing with the page length property.

    Isn’t this possible? Please? ;)

    in reply to: Page lenght and repeats #1484
    Adam Wilson
    Participant

    gseher wrote:How about using step skips to adjust your drum track to 8 steps of length and then set the page length to 24? Wouldn’t that work?[/quote]

    That wouldn’t really work with the new page switch mode that I proposed yesterday. ;) Because while in reality the drum track is only 8 steps long, the new page switch mode would keep me waiting for up to 24 steps, only because the page repeat property was sneaked into the page length property.

    I understand the fun that could be had with this feature, and I understand the need for UI space to get stuff like this implemented. The only thing I want to get across is that we pay the price of uniform flexibility this way. Some day someone will report this behavior as a bug, I think.

    But hey, it’s just one guy complaining, and probably many more of you who want it! I also vaguely remember that you run the (software) shop, Gabriel. ;)

Viewing 15 posts - 121 through 135 (of 164 total)