#54

ddi a quick look at the Dark Energy manual and perhaps you need to set it up using MIDI Learn to be on Channel 1 (assuming Dunes is using channel 1)?

1 Like
#55

Thanks! I did try the midi learn button without any luck. Oddly I’ve run Orca from my laptop into the DE without having to use the learn function, mysterious.

As I’m thinking about it today I’m guessing there’s a specific power-on vs usb connection sequence? I’ll try again tonight.

#56

Problem solved with a hard reset of the dark energy using the learn button on power up, sorry for dragging you into what was a simple issue. I’m super excited to have this functionality now. Messy and out of tune IG post below.

Thanks again for making Dunes! Love that it’s generative and so well documented from within the script.

1 Like
#57

Oh, fantastic! Thanks for the kind words, and for trying it out. Looking forward to hearing more :slight_smile:

#58

Any chance of crow integration for Dunes?

1 Like
#59

Hey Matt! Would you mind explaining how did you get Dunes to sequence the Minilogue? I’m trying the exact same thing but it seems I’m missing something. It works really well with my OP-1, but when I try to hook the Minilogue via USB>DIN cable nothing happens. I’d like to use Dunes for sequencing both instruments at the same time. Cheers!

#60

I’ve been so focused on Compass that I forgot about Dunes! Thanks for the reminder. I won’t likely have much free development time in the coming weeks, but I’d love to prioritize a few small crow-friendly tweaks at some point…

4 Likes
#61

Sure! I’m using an iConnect Midi USB–>DIN, and always make sure to connect both IN and OUT to the Minilogue. It’s doubly fun to then route the audio out of the ML and back into Dunes. I try to always make sure that I’ve got the midi device I want to use mapped to #1 in the SYSTEM menu. If it’s still not working, sometimes it’s helpful to modify the script by changing line 25 to read local midi = midi.connect(1).

But please take that last suggestion with a grain of salt because I am, like, way out of my league once we start diving into code.

2 Likes
#62

Awesome, problem solved! Thanks for leading me to the solution, man. I had MG mapped to # 2 in the midi device menu, so I just changed it to # 1 and it worked. I’ll definitely try routing the audio out back into Dunes! Thanks for the tip!

1 Like
#63

Am digging revisiting Dunes/Compass @Olivier. Here’s Dunes sending midi to modular (Rings/Plaits/Tempi/Ornament & Crime) with the audio coming back into Dunes for some softcut love.

5 Likes
#64

Love this script. What would it take to get the ability to save a sequence? Also, any potential to add clock out?

1 Like
#65

It would be amazing if there was a update at some point after which Dunes could work with Crow!

1 Like
#66

No promises, but I was working towards a save feature. Been sidetracked getting my launchpad mini running as an alt. grid.

I have also changed the UI quite a bit, I’m not sure it’s dunes anymore…

4 Likes
#67

Took much longer than I expected but I have sequence saving working.
Need to figure out sequence loading, but for now I need some sleep. :slight_smile:

2 Likes
#68

@lanserdj - Glad to hear you’re digging it :slight_smile: I tried implementing midi clock out a few months back, but struggled to maintain stability when the clock rate was being multiplied/divided. Could take another look when I have time, but that might be a ways off…

@bereenondo Agreed! Clocking via crow would be great, though I’m curious if you have other ideas.

@JaggedNZ - That’s amazing. Can’t wait to check this out. If the UI has been changed in a significant way, it might be best to create a spin-off.

1 Like
#69

I started this from a fresh fork and left my UI experiments in another directory.

My thought is to get file save and maybe HID devices working and then maybe look at reworking the UI. Happy to discuss if it’s an enhancement or a new thing if/when I get there.

1 Like
#70

@Olivier maybe hold on merging the PR

@lanserdj @Olivier should I just save the notes + pattern or just the pattern? Current PR just saves the pattern. I was thinking to add a separate save notes feature… but that might be over complicating it?

Should it be called sequence? Or pattern? Currently labelled “< save sequence” but for example P operator is “New patt.” Which makes me think Pattern is the correct term, but if I add notes then Sequence might be right, with the sequence being the combination of the patterns and notes.

@Olivier any objections to renaming step to pattern?

1 Like
#71

I think it probably would be good to first dial in the pattern. Notes could be cool too, but perhaps would be better to add later.

1 Like
#72

Awesome! Will hold off on merging for now. Thanks a ton for putting this together.

In terms of terminology, my preference would be to use the following for clarity:

command sequence
note sequence

I probably used pattern (for notes) due to limited visual real estate, but that’s not a good enough reason I think :slight_smile: Will think on this a bit!

#73

That PR should be ready, might pay to test, includes late night hacking.

I settled on command sequence and note pattern. I think that makes the most sense, try it out and see.

1 Like