Elektron-Users

What date did 1.2 come out?

Looks like someone already did this... 60 pages ago.
http://elektron-users.com/index.php?option=com_fireboard&Itemid=28&func=view&id=161839&catid=9&limit=10&limitstart=260#126112

license wrote:
Looks like someone already did this... 60 pages ago.
http://elektron-users.com/index.php?option=com_fireboard&Itemid=28&func=view&id=161839&catid=9&limit=10&limitstart=260#126112




buried under a dusty library of ideas. Elektron could use all these ideas from their active customer-base to their advantage, and maybe they do. in my opinion, they should bring more structure into that process, but then again, we need them to think about music machines not website design.

They read the forums regularly, I don't think you have to worry about them not knowing what their customers want.

Alright, I will happily drop this idea then

With that,
+1 for MIDI scenes.
+1 for slide between MIDI locks.
+1 for swapping FX1 and FX2 positions. I don't want to use 2 tracks to compress reverb!
+1 for (somewhat) freely routable LFOs.
+1 for stream recording to disk.
+1 for making neighbors routable - using them as sends would be awesome.

These may have been mentioned already:

+ Make Amp page for Neighbor machines functional.

+ Preview a step's locks. Better yet, have a lock trig mode (like sample/slice trig mode), with a row of p-locked trigs for a track mapped to the trig keys. This would be great for filter/amp locks, particularly for live sampling/processing.

+ Increase pitch range an octave or two, at least up (with rate, down isn't needed)

license wrote:
+ Preview a step's locks. Better yet, have a lock trig mode (like sample/slice trig mode), with a row of p-locked trigs for a track mapped to the trig keys. This would be great for filter/amp locks, particularly for live sampling/processing.

Now that I'm thinking about, much of the work for that is already in place with teh LFO designer.

anigbrowl wrote:
license wrote:
+ Preview a step's locks. Better yet, have a lock trig mode (like sample/slice trig mode), with a row of p-locked trigs for a track mapped to the trig keys. This would be great for filter/amp locks, particularly for live sampling/processing.

Now that I'm thinking about, much of the work for that is already in place with teh LFO designer.
Hmm? How so? Sorry, I probably didn't describe this well... I was thinking of something where you can store a sort of palette of trigs. These might (or not) have the same sample, but they could each have different locks on each param page.

Right now you can do this by toggling and copy+pasting trigs between patterns but it's a little inconvenient, and there's no way to (edit: individually) preview them or input them in real time. And of course this eats up a pattern slot.

What I meant was that with the LFO designer (and arguably the arpeggiator) there's already a graphical preview of a 16-step sequence. It wouldn't be too difficult to represent a set of plock triggers (for a single parameter) with a similar interface.

Ohh, gotcha, you meant design/code work. That's an interesting idea.

I was thinking it would be very similar to the pattern editor, except pressing trigs would sound the locked trigs assigned to the slots, rather than toggling trigs like in the pattern editor. The interface wouldn't need to look much/any different from the main parameter screen, either.

A row of 16 locked trigs to trigger per track per part would be plenty, although with the 4 pattern pages it may as well be 64.

How about a post master fx loop capture on track 8 when used as master with a simple level control and xfade volume. This would put a "dj transitioner" where it logically belongs and give us a track back.