#61

Amazing update! Love having more snapshots and the snapshot sequencer is too fun! Great implementation of the alt pad. I hate to even ask for more, but could there be a way to quickly clear a snapshot without having to manually clear each sequence? Maybe alt + the pad to its left + snapshot pad? Certainly not necessary with all the other functionality you’ve added, but it would be the sprinkles on the icing on the cake. This has developed into a spectacular composition tool.

2 Likes
#62

Was just thinking about this actually!

Currently the norns K3 button acts as a “clear all” if you’re on the main sequencer view, and basically resets the entire app. What if instead it only cleared the current selected snapshot? This could be a simple solution. Not sure you really need to clear the whole app state (could just reload it).

Edit: @hypnosapien just pushed a small update implementing this clear behavior.

Other updates:

  • Fixed a bug related to saving presets
  • updated clear to clear out sequencer params (intersect and clock divisions). Was previously retaining these values when you cleared a sequence.
3 Likes
#63

Solid. Another great update. Wasn’t a fan of the complete clear all so this is a really clever implementation.

1 Like
#65

Yes, this new clear selected snapshot behavior is perfect! Thank you!

2 Likes
#66

This sequencer is fantastic, very musical, I discovered it yesterday, thank you :pray:t2:

Today I’ve added support for the Er-301, it sends a pair of SC.CV and SC.TR_Pulse per sequence (using the same kind of Round robin you use for Crow but with up to eight voices) and there’s an additional param to set the first port (in the Settings menu). It works fine like I’ve said on IG. I’m ready to send a PR for that (tested with 7 voices on the 301). I was thinking about also sending the random velocity used for Midi with an additional set of SC.CV but I’m not sure this would be useful. If it’s random, it can be done on the Modular side, unless the velocity is sequenced too ? Or is it a kind of “humanize” feature ? I’ve noticed there are a few combinations of possible outputs but I’ve only added “Er-301” and not “301 + audio” for example. I didn’t know which combination of output I should do so it’s just 301 at the moment :slight_smile:

Some random thoughts : There are a few other things that came to my mind while playing with this great sequencer. I’ll probably work on the first one tomorrow (unless I’ve missed something and the feature is already implemented) because I’d like to control the snapshots from Ableton Live as well.

  • Triggering the snapshots with midi notes (from C3 on channel 16 for example, eight white notes corresponding to the eight snapshots ?) just to be perfectly synced.

  • The other option would be snapshot chaining directly on the grid maybe.

The following ones would be fun but not necessarily needed And might over complicate things :slight_smile:

  • “Momentary gates” for each of the eight sequences, I mean starting and stopping a sequence with a midi note (from C5) or finding some place on the grid to put that, each sequence could be played manually either with the grid or with Midi notes. With the new clock system it seams doable, that would be fun but not easy… only because I was looking for a way to start and stop the sequencer, I thought: “ globally or individually ?“ ^^
  • A third alt page for transposing each sequence immediately ?
2 Likes
#67

Thanks! so glad you’re enjoying it.

It’s basically a “humanize” feature, mostly because I couldn’t think of a good way to “sequence” the velocity with the current interface. I took the idea from Loom, and made it a random number between the min/max velocity parameters.

I think that’s fine. I don’t have an ER-301 myself, and I’ve sort of just been adding options as people request them. If someone wants to combine 301 with something else in the future it should be easy enough to add.

Snapshot presses are currently quantized. You can turn this on/off and set the quantization div in the settings. I’m not opposed to triggering them with midi but maybe you want to try this first? I can see how syncing them with ableton clip launches would be desirable though.

I’m also planning on adding a way to trigger snapshots with crow (random trigger, trigger sequentially, or trigger a recorded pattern).

Would this be different from the “snapshot pattern record” feature? Are you imagining more of a way to metasequence snapshots, instead of recording patterns manually?

I like this idea. I initially wanted a way to start and stop individual sequences (or even just “mute” them), but wasn’t sure what the interface would look like for doing this directly from the grid. I’m open to triggering via midi, though you’re right that it might be a bit of work to implement.

In general, I like being able to interact with the grid as much as possible. I want Animator to feel like a “performable” sequencer that you can improvise with on the grid without a lot of additional midi setup. So, my overall preference is to add any new features to the grid, if it’s possible to do without overcomplicating things. That being said, I’m definitely not opposed to adding any of the new midi features you bring up, and happy to accept PRs!

I guess I’m not entirely sure what this would look like. Would this be like a new sequencing interface which would enable you to sequence transpositions?

1 Like
#68

I’m glad to receive your feedback, thank you very much for your reply, I don’t want to interfere with your own view, you’re the creator of the app :slight_smile:

For the outputs available, maybe some kind of checklist (on/off) In the params would give the user the ability to check the output(s) wanted, I don’t know.

For the snapshots triggered via midi, it’s just that the sequence I was trying to record earlier today became so complex in terms of polyrhythms and randomness that it was hard to trigger the snapshots In time on the grid and play some synths on top of it at the same time, that’s why I wanted to automate that a little bit. To be honest, I haven’t played with patterns yet, Only snapshots with various transposition but it might be what I was looking for. Regarding the snapshot chains I was thinking about one alt key on the grid + n press on a snapshot key (alt + 3 press on snapshot one and two press on another snapshot for example) by I totally forgot the patterns and I should use this option maybe :slight_smile:

Yes, this is very interesting. Somehow like the Tapographic Delay switches and morphs between maps, basically each time it receives a trigger it switches to the next sequence or selects a random one if it’s not empty. But will the second input of Crow ever be available or will they add some kind of reset input for the new clock system ?

About the momentary gates, it would rely on the new clock system but yeah it’s hard to implement while keeping the grid interface as clear as possible. The Animator is already great like it is, it’s just that I was looking for a way to stop it at the end of my recording haha. The transport should stop if Crow doesn’t receive a clock after N seconds but at the moment it does not, but that’s not related with Animator.

About the transposition page: well it’s really not absolutely needed, I can set the global transpose to a higher setting or set the basis frequency of the oscillators on the 301 to a higher level. I was just thinking about an immediate way to switch between octaves, musically speaking it’s quite interesting too, I’ve done that in a sequencer but it was not sequenced. But now that you speak about sequencing it… haha no let’s not over complicate things, since it’s going to the modular, this can be done on this side too :slight_smile:

Anyway, I’ll post the PR tomorrow for the 301 after some new tests. And if I find any other thing useful, I’ll share them. I’ve tried to respect your clean way of coding /general code structure/ as much as possible :slight_smile:

1 Like
#69

Thanks for building this–it’s terrific. I am struggling a bit figuring out how to use the outputs via Crow. It works fine using the internal engine or JF, but when it comes to trying to use Crow’s outs, I am having no luck. Any advice? (If it helps, I tried flipping back and forth from Less Concepts to Animator using Crow outputs for both, and although Less Concepts worked, Animator didn’t.) I wonder if others have had similar issues.

#70

could you try running crow.reset() in maiden and then restarting the script?

I’m not sure why this happens exactly, but crow does seem to get “stuck” sometimes and not respond to new script commands until you reset it. Maybe I should be running this reset command when the script initializes, I’m not sure best practice on this…

Let me know if that doesn’t work, because if not I might’ve broken something :sweat_smile:

#71

This is a good idea, thanks! I haven’t really seen anyone do it this way yet, but it makes sense. It would definitely be cleaner than hard coding every possible option. Maybe if the outputs list grows much larger I will refactor it to work this way.

I’m glad you’re diving in. Let me know if you come up with any more ideas!

2 Likes
#72

@crim I was hoping you might look into a possible bug. I was trying to use Animator with MIDI out. Everytime I increased the minimum not lenght past 0.07 animator would freeze and stop running. reloading the script got it running again, but with the same result:freezing when trying to increase the minimum note length. heres a little vid of the behaviour. thanks in advance

#73

oof sorry about that! Ill take a look and try to get that fixed today

edit: @gnome666 fixed! Good catch.

It was throwing an error in maiden: bad argument #1 to 'random' (number has no integer representation). I guess Lua’s math.random doesn’t like the float 8.0, but fine with the integer 8. Sort of a mystery to me why this was happening with some floats (all ending in .0) and not others, but hey it should work now.

#74

awesome! thanks. I’m assuming update via maiden? :metal:

#75

yes - update via maiden should fix it

#76

Fun session today with Animator into AUM syned by Link. with Enso loopers, Quanta, field recordings and piano.

4 Likes
#77

very nice! love the detuned piano sound. Different instrumentation, but the textures and mood remind me a bit of some of Yellow Swans stuff, especially after 5:00 when the field recording becomes more prominent. I could imagine zoning out to this performed live in a dark venue with the volume cranked up.

1 Like
#78

Glad you enjoyed it, thanks again for the endlessly inspiring tool!

1 Like
#79

Merged a pull request from @Nordseele to add support for the ER-301 as an i2C output!

Thanks @Nordseele! Now I wish I had an ER-301 to play with it :slight_smile:

3 Likes
#80

Sorry for the late reply—I had to borrow a computer. No luck here, although strangely I can get clock pulses out of Crow or through JF. But no v/8 via either. And further, nothing using the internal engine now. So maybe this is something on my end?

#81

hmm… you should definitely be getting audio from the internal engine. What do you have the output set to in the params (in the “settings” group)? You should only be getting sound from the internal engine if it’s set to “audio,” “audio + midi” or “audio + cv + jf.”

Otherwise I’m kind of at a loss… The only other thing I can think of is if you’re using a DIY norns and something is not soldered correctly, but it sounds like you aren’t having any issues with other scripts? Do you see any errors in maiden while the script is running?