MUFF WIGGLER Forum Index
 FAQ & Terms of UseFAQ & Terms Of Use   Wiggler RadioMW Radio   Muff Wiggler TwitterTwitter   Support the site @ PatreonPatreon 
 SearchSearch   RegisterSign up   Log inLog in 
WIGGLING 'LITE' IN GUEST MODE

New Audio Damage Sequencer
MUFF WIGGLER Forum Index -> Eurorack Modules  
Author New Audio Damage Sequencer
landmax
Looks very interesting indeed!

http://www.analogindustries.com/b1873/
ignatius
awesome. super dope.
nearly ghost
Looks like another very powerful eurorack sequencer. So many great options available now! applause
KONTAKT1968
Wow looks great more details please!
Hainbach
Wow, awesome! Looks like a great live sequencer.
EarlJemmings
Damn, I believe something of a sequencer orgy has happened, so many released all about the same time

This looks neat, I'm sure tons of people will have use for it. Not quite improvisational looking enough for my taste
horstronic
applause applause applause applause
pinhole_sunrise
Jeez, first Metropolis then this! Looking forward to more info.
qu.one
Looks super legit. The fact that the three cv outputs can go up to 10v means they can double as trigs/gates for drum programming.
kingspill
This looks awesome. And its much appreciated when the manufacturer shows a cool module like this with hopeful release dates and info.

We're hoping for US$599.00, and about two months. But both those numbers are subject to change.[/i]
EternalTurtle
Looks like a lot of fun. I am missing something? where does the sd card go? There seems to be no slot on the front. Do I have to slide that baby in the rear? hihi
ben_hex
Looks great. Lots of empty panel space I hope they add a bigger robot logo hihi
SunSpots
hmm plocks please and sample engine and 4 tracks... Jk
grimley
I'm not kidding ... p-locks please!
As soon as I saw this I thought "Elektron inspired euro sequencer" which is what I have been dreaming about since I got into euro.
carlosnyb
This and the Metropolis can rachet -- any others out there that can rachet easily?
thetwlo
carlosnyb wrote:
This and the Metropolis can rachet -- any others out there that can rachet easily?


http://www.orthogonaldevices.com/er-101
Crandall1
Basically the only way this is programmed is via parameter locks. We don't call them that, though. Since it's the only way, we just call it "programming."

Regarding the SD card, it's in the back. You hardly ever will need to access it; the only real reason would be to update the OS, which isn't going to happen every day. It will store literally thousands of complete states (which are only a few K) so there's no real need to get to it often. We thought that the cost and mechanical nightmare of putting the SD card slot on the front (which we would merrily pass on to you) wasn't really warranted in this particular case. You can thank us later. :-)

Regarding getting it in ModularGrid, we haven't finalized the terminology of some of the artwork yet; I'll go ahead and send him art when I get home, with the caveat that it, like the price and release date, are not set in stone. The HP size won't change, in any event, so it will serve as a good placeholder for the time being.
nedavine
Maybe I can sell my A4 and get this!!!!!!
thetwlo
does it have voltage controlled step select?
gonkulator
How did I miss that yesterday...
VanEck
Quote:
"There are several ratcheting features; you can program a ratchet of various lengths per step, or you'll note the 6 buttons labeled "REP." These will repeat, in order, the last 8, 4, 2, or 1 steps as a loop, or cause the step you hit them on to repeat in half or quarter time."


Now we're cooking with gas. Being able to "switch" this REP function on/off via CV would be awesome... as well as if there is any randomized/chance control over when REP is on or not, just like in Replicant. That would be gnarly as all hell.
onthelees
Spent some time lobbying these guys at the Wiggler grand opening yesterday. First, some features that I didn't see mentioned:

There is one "Tuned" CV output and 3 gate outputs per preset.
It was also implied that there was a Roland System 100-style repeat feature in addition to the ratcheting, or that ratcheting could be configured to behave that way, but I wasn't entirely clear.

I think in general this is very cool and quite full-featured for the proposed price point. However, I lobbied hard for MORE THAN ONE CV TRACK IN PARALLEL, :bananaguitar:with independent lengths to allow polyrythmic behavior and overlapping, complex sequences. Throwing a clock divider in there would be nice also. thumbs up I would gladly trade 64 presets for 16 presents and turn those bank select buttons into track select buttons for editing. 64 steps is nice but I would take 16x4 any day. As always, a manufacturere has to weight features against cost and time to market, but that's my two cents anyway.
kuxaan-sum
gonkulator wrote:
How did I miss that yesterday...



I was thinking the same thing...
It's because that whole area was jam packed.
oops
Neo
Will it do legato or 303 slide?
Crandall1
Our intention is to have a top level of easily accessed features that are the base operation of the unit, and then a deeper level of features that comprise basically everything ever. We are not finished coding this yet, so if you have feature requests (that don't involve huge hardware changes like putting the jacks on the top, putting the SD card on the front, etc.) now is the time to let us know. I won't address all these "will it have" questions at this time, because I simply don't know the answers to most of them right now. But if you want something, the next few days in this thread are the place to ask. We won't get to everything, but if there's something we haven't thought of that is implementable, we'll certainly give strong consideration to adding it.

TL;DR: Keep 'em coming. We might do some of them. We might have already done some of them.
computer controlled
thumbs up thumbs up thumbs up thumbs up

How is it programmed? More like a 303 (Analog4) or more akin to a 101? At least as far as slides and rests are concerned. Would be great to have it more 101 style.
Crandall1
It's programmed more like a 606 than either of those, honestly. It is very much in the Elektron style; you just turn the steps on you want, select the note they should be, and go on your merry way. There are (currently) 9 parameters for each step:

1. 1v/Oct quantized value (set with the little keyboard and the +/- 1 oct buttons.)
2. CV1 value
3. CV2 value
4. CV3 value
5. Gate state (gate on off, aux gate on off)
6. Gate length
7. Aux gate length
8. Repeats (the Roland system 100 style ratchetesque thing)
9. Probability (the likelihood the step triggers; defaults to 100%, but can be set.)

These are accessed via three easily reached pages and the three encoders, with the exception of #1. We can add more pages at the risk of adding confusion.

But anyhow, how you program is you activate the note programming mode (essentially the same as hitting the record button once on an Analog Four, MonoMachine, or MachineDrum.) Then you turn the notes you want on or off, and set them in the same manner you would on an Analog Four or MonoMachine. The programming method is very similar to those devices.

The two CV inputs can be set per pattern, and can control all the parameters that it would be appropriate to control with CV. They are essentially modulation sources, and each gets one destination, chosen from a list, that can be any number of things.

We're working out how to add ties (legato) and slide; I don't have an answer for that at this point.
microfauna
Ratchet definition

Is there a bit of confusion here.
I understand ratcheting in the Tangerine Dream style as gate division or (multiple triggers without the step length changing).

Repeat in Roland100 (RYK)/Metropolis is multiple triggers at the clock speed ie step/stage length increases. Is it confusing to be calling this ratcheting?
oscillateur
Having an option to use all these outputs to get several tracks (either 2 with gate/cv/cv or 3 with gate/cv each) running at once would obviously be great It's peanut butter jelly time!
paperCUT
Looks fantastic thumbs up If there's one thing I'd like its big, easy to read text on the panel. The current design looks quite good but if you can squeeze a bigger font that would aid usability.
KONTAKT1968
Does it have force to scale for the CV with both preset scales and user definable?
kstl
Looks really interesting... the SD card option is really useful!
suicidelane
Crandall1 wrote:
It's programmed more like a 606 than either of those, honestly. It is very much in the Elektron style; you just turn the steps on you want, select the note they should be, and go on your merry way. There are (currently) 9 parameters for each step:

1. 1v/Oct quantized value (set with the little keyboard and the +/- 1 oct buttons.)
2. CV1 value
3. CV2 value
4. CV3 value
5. Gate state (gate on off, aux gate on off)
6. Gate length
7. Aux gate length
8. Repeats (the Roland system 100 style ratchetesque thing)
9. Probability (the likelihood the step triggers; defaults to 100%, but can be set.)

These are accessed via three easily reached pages and the three encoders, with the exception of #1. We can add more pages at the risk of adding confusion.

But anyhow, how you program is you activate the note programming mode (essentially the same as hitting the record button once on an Analog Four, MonoMachine, or MachineDrum.) Then you turn the notes you want on or off, and set them in the same manner you would on an Analog Four or MonoMachine. The programming method is very similar to those devices.

The two CV inputs can be set per pattern, and can control all the parameters that it would be appropriate to control with CV. They are essentially modulation sources, and each gets one destination, chosen from a list, that can be any number of things.

We're working out how to add ties (legato) and slide; I don't have an answer for that at this point.


I would love if ties were implemented akin to the FR Möbius: press and hold the step where the tie is to start, and then press the step where the tie is to end. I love all things elektron, but I hate hate hate the way they have implemented legato (ties) and slides on both the A4 and MnM. Anyway, I'm looking forward to the release is Seq1.
Crandall1
I agree with your statement. The Mobius was way better with that. (Although the note entry _sucked_!!!) However, when there's more than 16 steps, that becomes a bit of a problem. That'll take some thinking.

-CR
filtermod
This looks really nice and deep. I really dig the AD plug-ins that I own, and I've been meaning to grab a grainshift, but I think I'll be saving my pennies for this. It should play quite nicely alongside my metropolis! Mr. Randall makes inspiring stuff. thumbs up
exper
Looks cool.

How about Axon VST as a module next! hihi
carlosnyb
microfauna wrote:
Ratchet definition

Is there a bit of confusion here.
I understand ratcheting in the Tangerine Dream style as gate division or (multiple triggers without the step length changing).

Repeat in Roland100 (RYK)/Metropolis is multiple triggers at the clock speed ie step/stage length increases. Is it confusing to be calling this ratcheting?


The concept is new to me but if I understand, sounds like two kinds/modes of ratcheting, one that expands a step and one that is within a step -- it is hard to tell which sequencers do which and how, but options are nice.
maudibe
Holy Bejesus it looks freckin' wicked smile

Seriously you guys, I have your grain shifter and it is lovely… however for this module can we have pots / encoders that are panel mounted please?

Pretty Please?

Now… the question is, what to ditch from the system to make space … another rack? Noooooooo….

Rockin' Banana!
soup
Might the note buttons output CV/Gate when the sequencer isn't (or maybe is) running?
SunSpots
hmm... 3 more cv outs would be a great use of overkill and p locks.

active record of knob movements ... drool... knob recording please!

and yes some scale quantization. at least as many/same as metropolis so they can easily play together.

tick per step gate in, not dependent on consistent clock. I think u have this already.

cv controlled step addressing. so not 1-2-3-4 from a gate, but I send a wonky lfo and get 6-1-3-4-4-8-2 or whatever the lfo shape is.

maybe internal lfos or various kinds to p lock even more mad glitchy stuff? not sure if necessary, but might make it require less cv inputs? stick with two cv inputs for some meta functions, and access 3 internal lfos for other madness.
...but I would rather have more cv outputs FOR SuRe.
Royalston
One thing I love doing with the metropolis is just moving one step pitch while the sequence is playing back - like a melodic development within a held melody. It would be great if one aux assign destination could be assigned to a specific step's pitch, giving CV control over this idea.
Kirk Degiorgio
this looks ace… all i humbly request is that it stops & starts with no glitches when receiving external clock and resets 100% accurate to the final stage, so it starts upon Stage 1 when restarted.

simple requests but quite a few sequencers I've tried fail these simple tasks.

(and judging by the amount of sync/reset threads I'm not the only one who comes across these issues).
itege
Might have to sell my microbrute for one of these...
meatbeatz
Brilliant! and right when I'd almost given up on euro sequencers. The most important thing for me is 100% reliable resetting via external clock and with the option for resetting on both first and last step. And.. by "many other deep features", I hope you mean some tricks found in Numerology and Cirklon. wink
SunSpots
PShh. I ight as well ask for generative mode? with some kind of crafty cv in influence on the way it generates the melody and how it plays the note sequences.

I figure you guys are apt to handle this request. won't be surprised to find that it is not in the unit lol
SunSpots
so... maybe it picks some scaled notes and sticks them in some pattern somehow. then, when I hit a gate in, the unit will slightly modify the pattern. not fully, just a little. hit another gate in... more modification generated.

I am thinking random might not be best. hmmm..... maybe someone more genius can develop this idea further and rap on it with me?
SunSpots
SunSpots wrote:
so... maybe it picks some scaled notes and sticks them in some pattern somehow. then, when I hit a gate in, the unit will slightly modify the pattern. not fully, just a little. hit another gate in... more modification generated.

I am thinking random might not be best. hmmm..... maybe someone more genius can develop this idea further and rap on it with me?


so maybe a gate in takes the current pattern, no matter how it was created. and it can randomly do one of the following
double up a high note
double up a low note
do both
mute the mid range
mute highs, lows, or both
lengthen 2 notes, starting with any notes that have more distance between them than other notes.
shorten all gates, a few gates, all high gates
take 3 notes and shift up an octave... 2,1 notes up Or down
created beat repeats (multiple gates per note) on certain notes. think retriggering but shorter gates maybe? maybe not?
some combination of all of these, a few of these, or maybe one at a time depending on what you set it to. if you set it to 1, it changes one, set It to 10 it changes 10 or less at a time to give more dramatic changes.

you can call it pandora's mode
Crandall1
That's asking a lot for the initial release. :-)

However, software updates in this thing will be relatively simple (just pop out the SD card, jam it in your 'puter, swap out the OS on the card for the new one, back in, flash it, and Bob's your uncle.) We will continually develop it, and I, for one, will strongly lobby for generative features. No real chance of them _not_ showing up, because that sort of thing is our bread and butter.

But for the initial release, we have a lot on our plate already, so it is unlikely that sort of stuff will get in there, other than the note probability I already mentioned.
dslice1
bad ass!
GoneCaving
Looks amazing! Are there any videos of this in action?

Hmm, this or Metropolis? Yeah, yeah, I know, both! Dead Banana
Funky40
Crandall1 wrote:

2. CV1 value
3. CV2 value
4. CV3 value

1. what is the resolution of the programming ?

if it is something like a 0-127 Value, i´d like to request a "fine" parameter addon for at least one of the CVs.
....something like: you set the parameter value first and have the ability to add with a press of a "shift"button or something similar a finetuning to it afterwards.
good to set up wavetable on wavetables VCOs in case you have glitch,
or to control things like "metamode" on a Braids
( i´ve had for examples problems to control the metamode on my braids with my octatrack and a Kenton2000 midi2 CV with the wanted accuracy)


2. when i sequenze, modern wavetable VCOs easily can eatup all the 3 aux CVs just alone.
Thus, a request for 1-2 aux CVs more. well, or make it 3 more lol

3. +1000 to:
proper clock and restart behave is first priority in my book.
and also good visual readabilty of printed Fonts and display. ( a much underrated aspect IMHO )

edit:
4. ahhh, "small" slide times, possibly just added by on/off switching.
for example for velocity CVs, and especially for things like controlling Panorama and crossfaders to avoid clicks !!
Crandall1
All our parameter changes in all our products, both hardware and software, have smoothing. Other than the serious buffer looping stuff (where clicks are nearly unavoidable due to the nature of that effect) our products are generally click-free. This will be no different.

(This is something that we, as plug-in developers, bring a lot of experience to the Euro table with. I don't think we'd be out of line by saying we have the largest codebase of DSP of any Euro developer, just by nature of our main business.)

The resolution of the three CV outputs (and there can't be more; we're using all the I/O that this CPU is capable of, sorry) is 1024 steps. So plenty fine for every digital module currently available in Euro, and most future ones.

We're still working on the slide; I don't have answers about that yet.
Funky40
1024 steps is cool.

you refer to "smoothing"......and "slide" in the other sentence
what i meant is the problem of audio clicks when CVing things like "pan", thus refering to " small slide times".
not shure if your "smoothing" would solve that problem, respectivly saving one to patch a CV over a separate "glide" module
stromcat
In terms of feature-request thoughts...Some kind of handy elektron-machinedrum-MIDI-esque chord mode based on specifying root notes and semitone +/- amounts for the other two CV outs - like 'Chord' MIDI device in Ableton since I don't understand actual musical scales?

Not sure if I've missed if it already does this.
Crandall1
We were talking about something like that. We may add it down the road, but it won't be in the initial release.

We have, however (with respect to the earlier conversation in this thread) added this: each of the three CV outputs will now have four ranges:

1. 0V to 5V
2. 0V to 10V
3. -5V to +5V
4. 1V/Oct

The displayed value as you program will reflect the setting. So if it's set to 0V to 10V, the display will read 0.00 to 10.00. If 1V/Oct is selected, it'll read C0 to whatever the top note is, C5, I think. This is selectable per output. So the first output can be 0-10, the second one 1v/Oct, the third one -5 to 5, or whatever.

It's not a stretch to add a chord mode from there (where, if it's in chord mode, the CV outputs are all 1V/Oct, and you'd select + or - semitones), but we have a _lot_ on our plate to get it out the door in a quick-like fashion, so that may have to hold off for a later update. It is a very good idea, though.
studionebula
Thanks, everyone, for your enthusiasm, and thanks also to the folks who stopped by to say hello at the T_A meet.

As Chris said, our sequencer is in a late stage of development. The hardware, if not cast in stone, is in rapidly setting cement. The software, on the other hand, is (and will be) ripe for additions and alterations. Obviously we cannot accommodate every suggestion and request; as with our plug-ins, we are striving to provide a good balance of power and usability. Philosophically, a synthesizer module shouldn't have an LCD at all--it should be a one-control-per-function sort of thing. However, adhering closely to that dogma would mean never moving beyond the rows-of-pots architecture of sequencers of yesteryear, and that's such a limiting architecture in the presence of today's microcontrollers. So, once you accept the presence of an LCD as a necessary evil, the challenge is to build a user interface that doesn't require menu-diving to get music made. We want this sequencer to feel at home in a modular rig, and not feel like a computer that was shoehorned in next to your VCOs.

To address some specific points:

Ratcheting: Yes, although as microfauna mentioned it seems that there are two things called ratcheting being discussed in this thread. The first is what I think of as ratcheting: the gate goes through two or four cycles in one step, rather than one. I think this is what's necessary and adequate to recreate the classic Tangerine Dream motif, but please set me straight if I'm wrong. (References to specific TD albums/tracks/times are welcome--yes, I have most of them, at least from Stratosfear through Optical Race.) Our sequencer already does this, both programmable per step and triggerable on the fly with two of the step buttons. Yes, it could be a CV destination also.

The second thing is (apparently) repeating a single step N times. We kind of have a facility for that now, but it's only a live function: holding down one of four of the step buttons causes the thing to repeat the last one, two, four, or eight steps as long as you hold the button. When you release the button, it drops in at the appropriate point within the pattern. This means that the repeats do not alter the overall length of the pattern, unlike (in my understanding) the behavior of the RYK unit.

We could, of course, add a repeat feature like that of the RYK unit, which I guess would have to be a step parameter separate from the first mode I described...? I can see arguments in favor of having both modes. I'll probably regret saying that. Discussion is welcome.

Multiple tracks/channels/patterns running in parallel: we didn't envision this originally, and I'm hesitant about the complexity that it would entail from both a UI and a coding perspective. It's going to become a topic of internal conversation, however.

Legato/slide/glide: Yes, will do. Details to be nailed down, as Chris said.

Preset and user-definable scales: Depends on what you mean. If you mean forcing to major/minor/Mixolydian/whatever, I suppose we could work that in somehow. If you mean scales as in non-equal-tempered tuning, Chris is gonna hate me for mentioning this, but my long-term intention is that it will load Scala files from the card. That's not going to be a version 1.0 feature, however.

Knob recording: sure would be fun, wouldn't it? No promises, but yes, we've thought about it.

Tick-per-step gate in: that's the only clocking mode which fits my head, so yes, it will that.

CV-controlled step addressing: absolutely. I think that's actually the very first use for the CV inputs we came up with. (The second, at least in my mind, is modulating the durations of the gate outputs.)

Internal LFOs: yes, at least one.

More CV outs: no, sorry.

CV control over one step's pitch: wow, good idea. Kind of complex to set up, but we'll consider it for sure.

Starts and stops with no glitches: what, man, you think we have no pride? eek!

Generative stuff: absolutely. This is the stuff that makes me want to build a sequencer in the first place. (Well, that and the blinky lights.) What sort of stuff, exactly? TBD.

Thanks again for your enthusiasm and your suggestions. Keep 'em coming!
twospartans
looks beautiful!
w00t
sloth713
It would be cool if the software allowed the user to choose between V/Oct and Hz/Oct for the CV output
gliiitches
Apologies if I've missed something in the discussion so far, but I have some questions if that's OK...

The three CV outs. If I'm understanding correctly I could set each of these to 1v per oct? And on each step these could be independently set to different values?

So I could use this sequencer to drive three seperate oscillators each playing a different melody / part? The limitation would be that all three CV outs are (currently) tied to the same pattern, clock speed, and gate?

Cheers!
Crandall1
Yes, you've pretty much got it, with one exception. There are _two_ gate outputs. (Gate and Aux.) The main Gate output is turned on and off with the step buttons, in the manner you'd expect. The Aux output is turned on and off in the settings for that step. (One menu deep.) We're trying to come up with a more elegant method, but that's what we have right now.

EDIT: In reading that back, you're a bit off. If you'd like, you can actually control the 1v/Oct inputs of _four_ separate oscillators. The 1v/Oct output is _always_ that, then you have three CV sequences that can be set to 1v/Oct. Note that the 1v/Oct and CV outputs send whatever values are set whether or not there is a gate present. So you could conceivably hit your EGs some other way, and use the two gate outputs for some other task.

But, long story short, if you want to run two independent melodies, you can. They will, of course, have the same pattern length and sequencer settings, but you can, with fairly minor programming, have, e.g., a melody and a bassline, or a kick and snare pattern, or whatever. Two Sequencer 1 units, with the second slaved to the first, will give you four complete monophonic lines, with four additional CV sequences. Pretty slick, in my opinion.

Two further bits of errata: first, they now have a mockup of the current state of the panel graphics in ModularGrid now, so you can add a reasonably nice looking iteration to your racks. This is, of course, subject to change, but the size won't be any different at release.

Second, this unit will also have internal LFOs and envelope generators (we're not 100% on the EGs, as we may run out of CPU, but definitely LFOs) that can either affect internal parameters or be sent to the CV outputs or whatever. The LFOs can either be tempo-locked or free-running. So there's that to consider, as well. This will be an extremely powerful sequencer.
djempirical
Very much looking forward to this! (As I've said elsewhere.smile )
keef321
I was thinking of getting a metropolis, but I realised I would have to get a secondary sequencer for it to control the note length with via a CV aux in. Now this sequencer pops up, it looks very interesting and I think has all the functionality (including note length) that I would want (including quantiser from what I understand).

I have never used this style of sequencer!! I nearly bought an analog four, but was not that bothered about it's sound, but was interested in the sequencer.

Just hope I don't have to wait to long, lol.
eskobaba
just got a metropolis, already have the a155 154 + tirana, cant fit more now but looking forward to hear it in action.
flo
This is looking great! applause

Any chance for a tap write mode for note entry? Acidlab has done this nicely. You could use the octave of small keys, + / - octave buttons, and then maybe shift + bank buttons for slides etc...
kstl
flo wrote:
This is looking great! applause

Any chance for a tap write mode for note entry? Acidlab has done this nicely. You could use the octave of small keys, + / - octave buttons, and then maybe shift + bank buttons for slides etc...


+1 on this please, good idea!!
koyl
I sold my Analog Four to fund my modular and the thing I knew I would regret is its sequencer.. not anymore it seems ! It's peanut butter jelly time!
Crandall1
I like the tap mode idea. We'll add it to the list of potential feature updates.
flo
Cool! It's motherfucking bacon yo If it has the tap mode, I won't be able to resist. That'll make it killer for impro on the fly.
suicidelane
I've told my buddy Holografique about Seq1. He said he would love to be able to output Hz/Volt. He is currently using his A4 solely for that duty.
Crandall1
We've added Hz/Volt to the list. However, S-Trig might be problematic, as it involves an open line. Our output buffers for the two gates have the ability to do that, but we hadn't planned on it. So we'll see about that. Hz/Volt definitely, though.
SunSpots
I love you Crandall. please make my dreams of a generative sequencer come true. even if it is in a future update... which I totally don't trust due to elektron burning that bridge for everyone else... wink
Stancotey
Hey Chris,

Regarding S-Trig outs, can you use 3.5mm TRS jacks for the gate outs and wire the ring to an open collector NPN transistor for the S-Trig part? While it would take a special cable to use for S-Trig, the other end of that cable has to have a Cinch connector on it - so pretty special anyway. This would let you keep compatibility with standard patch cables with gate signals but still access S-Trig when needed. Small HW change, no FW change.

Stan
dmod
You guys are killing me!(my wallet that is) lol
studionebula
Regarding S-trigger outputs, we should be good to go. As Chris mentioned, the output buffers I chose happen to have three-state outputs, which means that with a small change to the PCB we can take advantage of the hi-Z state to create something that should work for S-trig. Hopefully I'll be able to find someone locally with hardware that I can test with, since I don't happen to have anything with an S-trig input.

Hz/V scaling will be even easier; no hardware changes needed for that. I'll probably seize this feature as an excuse to buy a MS-20 Mini for testing purposes. hyper
clusterchord
studionebula wrote:

Ratcheting: Yes, although as microfauna mentioned it seems that there are two things called ratcheting being discussed in this thread. The first is what I think of as ratcheting: the gate goes through two or four cycles in one step, rather than one. I think this is what's necessary and adequate to recreate the classic Tangerine Dream motif, but please set me straight if I'm wrong. (References to specific TD albums/tracks/times are welcome--yes, I have most of them, at least from Stratosfear through Optical Race.)


yes, please.. we're not worthy hihi




studionebula wrote:
Preset and user-definable scales: Depends on what you mean. If you mean forcing to major/minor/Mixolydian/whatever, I suppose we could work that in somehow. If you mean scales as in non-equal-tempered tuning, Chris is gonna hate me for mentioning this, but my long-term intention is that it will load Scala files from the card. That's not going to be a version 1.0 feature, however.

Knob recording: sure would be fun, wouldn't it? No promises, but yes, we've thought about it.


a big resounding YES on both accounts. i still wait, and seems i'll wait forever, for a sml quantizer module that can load Scala files from a card.. and of course be uberfast and have usual host of standard features.. gate, 2 or 4 channels.

knob recording will push this sequencer from purely digital/xox/elektron world a little bit towards the realtime inspiration we find in pure analog step sequencers. to be able to record wiggling would be fantastic.

all in all to say i am excited about this sequencer would be an understatement..

for future developments <dream mode ON> something like this with more of everything, especially more CV i/o and 16 knobs.. in a full 3U 19" rack/tilteddesktop..


Crandall1 wrote:
S-Trig might be problematic, as it involves an open line. Our output buffers for the two gates have the ability to do that, but we hadn't planned on it. So we'll see about that


it's easy enough to modify all S-Trig inputs with that simple circuit from dotcom site. ive done so on all my moogs for a few cents. its passive and it works like a charm. one could even modify one pair of jacks on a multiple to do this function.
Crandall1
See Adam's comment above. Apparently, S-Trig is no problem. It will be a selectable mode. (In much the same way as the Analog Four does it.)

Regarding the Scala file thing, I'm gonna have to go to the dentist after testing that shit. Alternate tunings make me grind my teeth. But yeah, apparently we're doing that. Because Adam hates me.
kao:be.
would be very useful if it could utilize the CV bus and could e.g. switch preset in sync with TipTop stuff like Circadian Rithm and Trigger Riot
djempirical
How about a pie-in-the-sky feature request? grin

As I know you guys like chance settings, how about a setting to adjust the percent chance a given note will hit early/late? And maybe there could be a range to how early/late the hits happen, too?

I'm thinking something that could maybe make things a little "looser", sequence-wise. (I'm thinking ahead to drums sequences.)
maudibe
Hey, no extra suggestions here. Let's just get it in our racks smile as it already sounds fantastic spec.

Since software updates are going to be so easy in the future lets just get it now applause

Meanwhile, extra function 'packs' could be available as 'add-on' products.

Otherwise feature creep might make this two years in the coming? By which time, statistically some of us are going to be dead. LOL

** and needless to say, by which time, some other product will have jumped in on the coat tails…. it happens.
itege
First sequencer that I've actually been excited about since I got into modular.
Crandall1
I'm fucking brutal with the feature creep. (Or, as we call it at Audio Damage, creature feep.) Believe me when I say that I adhere to the Steve Jobs maxim: Real Artists Ship. This bitch will be at the assembly plant by the end of next month (we've started ordering the parts already; the switches will be here 7/16, then the build can start) or else.

Long story short: we have the functionality we originally specced all done; we have many of the features requested here implemented as well. We're moving in to alpha testing, which is where I and a couple of the Alpha Dog Euro guys do usability testing, and then we change around user interface stuff to fit our ideals. Then the boards are built, then beta testing, then RC testing, then the assembly, then it ships.

Basically, this (like our other modules) is more of a software product than a hardware one, and follows normal software release schedules, for the most part. The hardware part has been finalized for some time now, and is more or less ready to be built.
dmod
Man I really am impressed by your style sir! I love your stuff and I love the fact that you get the ball rolling. It is hard to get teased by a great product then wait........and wait...... Good work! Consider my money already gone on this one! Looks amazing! Cant wait! Cheers! Dead Banana
acidbob
Yes this is really something I have been looking at a lot lately
studionebula
Yeah, Chris is usually the one that holds the reins on feature creep. He's a good influence on me in that respect. There will be software updates in the future which will add features, but we do need to (and will) draw a line on the list and say "this is what ships as version 1.0."

It helped that much of the hardware design came from stuff I've done previously for personal projects. There are next to no changes planned between what we showed at Trash Audio and the production units, and nothing that will be externally visible other than the S-trigger modification.
j.william.case
This is very similar the sequencer logic in tattoo, am I right?
Crandall1
Well, putting notes in a row can only be done in a few ways. Tattoo follows the x0x paradigm via Elektron (in its case, the MachineDrum), and so does this (via the Analog Four). But at the end of the day, we have to make something people are comfortable with.

Basically, we think the Elektron method (which is a pure refinement of Roland's x0x sequencers) is about as good as a step sequencer can be done, and that's the method we choose to use for most of our sequencer-based products. Now that you bring it up, though, this will have some of the randomization features of Tattoo. And if it proves popular and we iterate it to a multi-lane drum sequencer, we will essentially add all of the Tattoo randomization (both mod and note sequencers). Which would be, in the Euro context, what the Silicon Valley types call a "game changer."
clusterchord
another thing i forgot to ask earlier:

as with all sequencers, i hope enough room was left in CPU and optimized code, that this machine will have rock solid timing, both as master, and especially when slaved to incoming analog clock/din ?
studionebula
I consider rock-solid timing to be the most important aspect of this project. Both the hardware and software are designed around this consideration.
clusterchord
awesome, music to my ears thumbs up
maudibe
Studionebula - consider my money in your account smile

I can't wait for this one and I am pleased you are handling feature creep sensibly - i.e. getting the product in place now, rather than dithering about.

Based in the UK - are you intending to ship to europe/uk at the same time as a stateside release?

This sequencer of yours is either going to mean a new rack…or something has to go! But, yup, it is going in Rockin' Banana!
Crandall1
We are shortly going to begin accepting direct orders via our website. We'll ship worldwide, day of release.
djempirical
maudibe wrote:
Otherwise feature creep might make this two years in the coming?


I'm pretty confident Chris & Adam know how to avoid feature creep. smile
hpsounds
@ Crandall1

How is handled the pattern change ? Is it like in the Octotrack ? two choices : 1) at the end of the pattern 2) in-sync on the next step. Are patterns change CV-able ?

Deactivating a step seems just done by pushing the relevant step button (I guess). Does deactivating a step kills all the associated parameters of the step ? I hope not, because that's how it works on the Elektron products - at least on the A4 and on the Octotrack - and it was a deal breaker for me (had an A4 for a week) ...

BTW, this sequencer looks ACE ! thumbs up

H.
clusterchord
Crandall1 wrote:
But, long story short, if you want to run two independent melodies, you can. They will, of course, have the same pattern length and sequencer settings, but you can, with fairly minor programming, have, e.g., a melody and a bassline, or a kick and snare pattern, or whatever. Two Sequencer 1 units, with the second slaved to the first, will give you four complete monophonic lines, with four additional CV sequences. Pretty slick, in my opinion.


a question: when you are using a single machine in this resource sharing manner, pulling off two independent monophonic lines.. i understand they have to have the same pattern lenght and setting, but:

will there be a way, or a workarround to change the meoldy pattern on just one of these two, while the other keeps playin the same?

for example , same bass line going on, yet with two or three different lead line sequneces, that i change manually thruout the song/piece/jam ..



also, interested in question by previous poster hpsounds, but would like to add: will we be able to change the pattern lenght on-the-fly, jumping from 2 to 8 etc,, for some berlinshule-sque improvisation?



thanks
Crandall1
To your first question, nominally you'd do this by copying the pattern to another memory location (or two or ten or whatever) and do it via pattern switching. But yes, in that manner, it's possible.

To the second one, not in the manner you're describing. The pattern length is set in the settings for that pattern, so it's a couple button presses away from front-panel access. We pondered how to pull this off, and couldn't come up with a convenient method that didn't add to the existing control complement. (And we have _maxed_ what this rig can do, controls-wise. 40 LEDs and 45 front panel controls plus an LCD display is really pushing things to the limit here.)

So yes, you can change the pattern length on the fly. No, you can't jump from, say, 32 steps to 8 steps. This isn't really the sequencer you want for Berlin School stuff, for fairly obvious reasons. This is better for making longer melody and basslines and having memory recall. If you want to do Berlin, I'd suggest one of the many 16-step analog sequencers, since that's what they're designed for.

@hpsounds: I assume you're asking whether the pitch and CV are decoupled from the gate settings. The answer is yes. Whether the gate is on or off doesn't affect the pitch and CV, WITH THE FOLLOWING EXCEPTION: in a blank pattern, the first time you turn on a gate, it will get whatever the last note pressed on the keyboard was. So you can just whack C3, then go through and turn on the gates you want, for instance.

We're still finalizing how one turns the main gate on and off, though. Adam did it one way, and that's the way we demoed it at the T_A meet in PDX. But there were some things about that method that made me uncomfortable. When we demo it this Saturday at Analogue Haven, we'll have it set up a way more to my liking, and I'll get the opportunity to see if that works better in a high-pressure environment.

Long story short, we haven't quite decided yet. I don't yet have a unit here for usability testing, and Adam is still putting in the original feature set and tuning everything for the beta run; once the betas are built, we'll be able to spend more time playing it, and make a decision at that point.

Regarding the pattern change, I'd like to have it like Maschine, where you can set a quantization value for the scene changes globally. So if you set it for "pattern" it'll play out the current pattern, then go to the next one. If you set it for 1/4 Note, it'll switch at the next quarter. See above re: implementation of this feature. Currently, it switches at the next step after you press the pattern select.
evs
I'm not sure if this had been already asked... Is it possible, that the different cv outs could have different pattern length?
Or is it just one pattern length for everything?
clusterchord
Crandall1 wrote:
To your first question, nominally you'd do this by copying the pattern to another memory location (or two or ten or whatever) and do it via pattern switching. But yes, in that manner, it's possible.

To the second one, not in the manner you're describing. The pattern length is set in the settings for that pattern, so it's a couple button presses away from front-panel access. We pondered how to pull this off, and couldn't come up with a convenient method that didn't add to the existing control complement. (And we have _maxed_ what this rig can do, controls-wise. 40 LEDs and 45 front panel controls plus an LCD display is really pushing things to the limit here.)

So yes, you can change the pattern length on the fly. No, you can't jump from, say, 32 steps to 8 steps. This isn't really the sequencer you want for Berlin School stuff, for fairly obvious reasons. This is better for making longer melody and basslines and having memory recall. If you want to do Berlin, I'd suggest one of the many 16-step analog sequencers, since that's what they're designed for.


thanks for the reply. yeah i was thinking of those (as well), but i didn't want the exact replica, meaning no pattern memory. when performing things live there is a limit to how much control of every aspect one has time to address, so i like the idea of something in between Orbital, one on extreme, and ER-101 on other extreme. and AD fits the role, but then a lot of other things on top. suppose if i plan things for given track, i could copy the pattern to a several locations, making one 2 step, 4step and 8. and switch btwn em in performance.

AD Seq has many other things that i wanted out of euro seq. the berlineseq is just a side idea, not the sole intended purpose. started thinking about that after you announced rachetting Mr. Green. i like/want the scalas, and the xox/elektron elements too which reminds me..

the 303-ish glide... is it done in the exact same manner? - slide starting on previous step, expo rise to new pitch/step? many manufacturers tackled 303ish sequencing and somehow manage to hit n miss with the exact curve/timing needed. close but no cigar.

Crandall1 wrote:
Regarding the pattern change, I'd like to have it like Maschine, where you can set a quantization value for the scene changes globally. So if you set it for "pattern" it'll play out the current pattern, then go to the next one. If you set it for 1/4 Note, it'll switch at the next quarter.


awesome, that is the best option.
Crandall1
We're not cloning a 303, or the 303 style of sliding. There are lots of things that do that. (I'm thinking specifically of Future Retro's products, but there are lots of others.) We've come up with our own schema for note slides that we're happy with. It can ape the 303 method if you'd like, but it has its own personality.

(Which is, I think, the ultimate goal here: a sequencer that pays homage to its predecessors, but doesn't slavishly ape them, thus enabling a familiarity when it comes to programming it, but a new place when it comes to results.)

When given the choice between an exact clone and something that does its own thing, I'll choose the latter every time, and our designing at AD reflects this.

To your previous point, yeah, that'd work. Just copy the same pattern to a new memory location, and give it its own length. If you consider the entire state of the machine as one song, you have 4 x16 locations to work with. (The memory of the unit holds that many at instant access, with effectively unlimited variations given the 2gb SD card, and that each state is only a few hundred K.)
maudibe
I am salivating for this module Drunken Homer Simpson

Do we have a ball park release date yet? Checking the Audio Damage Site daily has got to be unhealthy seriously, i just don't get it
Crandall1
Here's a quick demo of the slide and per-step ratcheting as it currently stands. After a bit the tempo is slowed way down so you can hear how the slide is working. Then super fast, because why not?

[Edit: I can't remember how to embed Soundcloud doo-dads. Just go to the page or whatever.]

[Edit 2: We had to iterate the hardware to account for some changes to the SD card bit; as soon as we have built the second prototype and verified all the hardware, we'll be moving to production. Call it two months?]

https://soundcloud.com/audio-damage-inc/sequencer-1-slide-and-ratchet- test

The point of the test was to demonstrate the slide stuff working when a ratchet was also selected. As you can hear, the slide works in entirety on the first step of the ratchet, so you don't get annoying half-way notes.
dmod
FYI soundcloud embedding has not been working on Muffs for some time. Can't wait for this to come out though! looks amazing! Release dates? hyper Cheers!
evs
evs wrote:
I'm not sure if this had been already asked... Is it possible, that the different cv outs could have different pattern length?
Or is it just one pattern length for everything?


well, i guess i am mostly asking for more than one track, and thats not going to happen, is it?
if the 3 cv outs could be treated separately, with different pattern length and so on, that would make it like three tracks..
maudibe
Any updates on this guys? we're not worthy
Crandall1
Waiting for the boards for the second (and third) prototypes. As soon as we build 'em and test, it'll be off to the factory.
maudibe
Ah, so a few weeks yet then? Financial relaxation moment smile
Crandall1
I'd be _shocked_ if we got it to people sooner than 8 weeks. I'd like to be shocked. I doubt I will be.
maudibe
Thanks Chris, it's good to know an approximate date - even if it is a while away. I'm sure people appreciate the info rather than being in the dark.

It's great to have this wonderful creation to look forward to thumbs up

Do you have a roll out strategy to the UK / Europe? Or will it be exclusively on your web shop initially?

Best, Steve aka Maudibe.
voidshell
OS Feature thought: Random option where you can select specific steps and then an overall level of random?

So for example, you can engage random mode and then press any or all of the steps that you want (The notes would highlight), then allow 1%-100% random to be processed on said selected steps?
Crandall1
maudibe wrote:

Do you have a roll out strategy to the UK / Europe? Or will it be exclusively on your web shop initially?


It'll be available at our web shop and whatever retailers do up-front orders in a timely fashion. (Sometimes, they can take _weeks_ to get around to ordering, and, well, we have to front a metric fuck-ton of money for these things, and we're interested in getting it back so we can, you know, pay our mortgages and stuff.)

I think I can say with certainty that day-of-release it'll be at AH, and most likely a couple of the other American shops. It's difficult to coordinate a release day for hardware, but we'll attempt it. As for Europe, it takes a little while to filter out to the stores that Alex4 distributes, so those will run a bit behind. And obviously the vagaries of international export come in to play.

But, long story short, we'll do our best to make it available in as many venues as we can on the day of release.

@voidshell: Pretty good idea, but I don't like your implementation concept. I do like the idea of grabbing groups of notes and Doing Stuff, though. That's pretty tricky to do, so I'm not gonna put it on the List for the initial 1.0.0 OS release, but we'll consider it for a future update.
maudibe
Hi Crandall1 - yes, completely understand the financial outlay of such projects.

Thanks for getting back to us all on this (esp. the EU/UK crowd). Personally I may well order direct. Cash in your pockets then, straight off.

Thanks, Maudibe. Guinness ftw!
studionebula
For those of you hanging on every bit of news: I got the tracking number for the PC boards; they're arriving tomorrow. It'll take a few days of building and testing to verify that this board design is ready for production. I can't tell you how much I'm hoping that I don't have to revise this board again because of some dumb mistake. very frustrating

There's still a good deal of software to write, and we really don't have any idea of the production time yet. We are getting closer, however.
mapmap
nice!

may the gods of PCBs be with you.
obviousless
May the PCB be with you. And also with you.
studionebula
Brief update: apparently the gods of PC boards are smiling upon me. I've built up two sequencers with the new boards, and everything seems to be good. I sent one to Chris; he received it today. Assuming that he doesn't find any problems with it, it looks like our board is ready for production. It's peanut butter jelly time!
sonicwarrior
studionebula wrote:
I sent one to Chris

You are working at different locations? eek!
studionebula
sonicwarrior wrote:
You are working at different locations? eek!


Yes, as we've done for the last 10+ years. Chris lives in Arizona, I live in Colorado.
maudibe
Hi Studionebula... very pleased to hear all is going well.

applause

Any chance of an early manual (even if subject to corrections)

It would get the juices going, and for those of us that actually like manuals it would be quite a treat smile

Cheers Guinness ftw!
stillvisions
Best of luck to the coding stage. That can always be a fun thing. Looking forward to seeing the results though.
studionebula
stillvisions wrote:
Best of luck to the coding stage. That can always be a fun thing. Looking forward to seeing the results though.

Thank you! I actually starting writing the code back in January. I had to have at least some of the code in place before finalizing the hardware in order to verify that the hardware could meet our timing requirements etc.
studionebula
maudibe wrote:

Any chance of an early manual (even if subject to corrections)

It would get the juices going, and for those of us that actually like manuals it would be quite a treat smile


I am also one such person. In the rather unlikely event that there is a manual available early that's worth public distribution, we'll make it available.
juvation
i will definitely buy one of these on release, however i have one question - why the jackfield at the bottom? the trend (eg Rene, Metropolis) seems to be at the top, so that in an ergonomic situation for a sequencer (toward the bottom of the system) cables don't impede operation.

thanks for quality shit, guys. i have your plugs and some hardware.
maudibe
Hi Juvation... yup I get you on this... but there is no standard as such... for example, my Moskwa's have the connections at the bottom as does the Mutamix (which I tend to use as a sub-sequencer).

It indeed is 'one of those things'

How frustrating when a VCA cv input is on the left... but so is an ADSR's output... so the cables have to cross the ADSR - if the ADSR's outputs had been on the right then.... you get my drift.... this even happens on modules from the same manufacturer confused

I think I can manage fine with the outputs on the bottom. This bit of kit is going to be awesome Rockin' Banana!
Bonobo
This looks extremely powerful, I've been planning on getting a metropolis but I'm now not so sure!

Looking over the two metropolis looks like it'll be more suited to hands on accidents and messing and seq1 will be far more powerful.

I really like the idea of 3cvs tied into each step, with metropolis I was thinking of getting frames in seq mode to do something similar, but having it tied into the sequencer is so much more powerful and logical.
maudibe
Different beasts though Bonobo.

To me the new Audio Damage job will be something to have 'planned' sequences in place ready to employ, where as the Metropolis is more of an instant (and wiggle-able) groover.

I have the Metropolis and it is great fun to 'play'. I used to have a SEQ-02, which I always considered as much more of a 'programmed to do its stuff' sort of module ( a shame it was flawed).

So I am looking forward to the Audio Damage unit to fill this gap. It is either this of something else similar. I have even considered the E101 or a Kilpatrick module. But I reckon to hold out a while for this one smile
juvation
i'm thinkin' this too -- Rene is my twiddleable focused-random thing, and the AD unit will be more for prepared stuff - aka when i've messed things up too much and need rescuing :-)
maudibe
Like it juvation applause
kingspill
Hi Adam, I'm really looking forward to this new sequencer. You folks make some great stuff.

I just saw that you're in Boulder. Me too. Hope to see you around town.

Dave A.
Crandall1
juvation wrote:
i have one question - why the jackfield at the bottom? the trend (eg Rene, Metropolis) seems to be at the top, so that in an ergonomic situation for a sequencer (toward the bottom of the system) cables don't impede operation.


Just personal preference. I put all my control modules in the top of my rig, because I don't like cables hanging over them. Most sound sources are set-and-forget, but control modules need to be touched quite a bit, and at the bottom of a rack, they have a whole patch draped over them. If it's at the top, with the jackfield at the bottom, it's always clear.

Basically, it has to be one or the other, so we went with what we liked. We briefly thought about putting it on the side, so nobody was happy, but then it would be 8HP wider.

In any case, an update: I'm pleased to report that we have revved the prototype hardware, as we spoke about a couple weeks ago, and cleared all major hurdles in both the hardware platform and the code. Adam just has to smooth out a couple UI issues, then we're moving to production. I should have the first beta software today or tomorrow, and you'll start to see a lot of demo videos. The first one should be coming before the beginning of next week; I'll post it in this thread, of course. I don't yet have a release date, but we're moving things along nicely, and basically it's clean-up and usability at this point.
meatbeatz
Great news! Can't wait to see demos of this baby in action.
juvation
Crandall1 wrote:
juvation wrote:
i have one question - why the jackfield at the bottom? the trend (eg Rene, Metropolis) seems to be at the top, so that in an ergonomic situation for a sequencer (toward the bottom of the system) cables don't impede operation.


Just personal preference. I put all my control modules in the top of my rig, because I don't like cables hanging over them. Most sound sources are set-and-forget, but control modules need to be touched quite a bit, and at the bottom of a rack, they have a whole patch draped over them. If it's at the top, with the jackfield at the bottom, it's always clear.


hehe, i think my rig and yours are completely opposite :-)
Crandall1
Making some progress on the UI front. This little pattern has a lot of swing on it, a couple slides, and a couple ratchets. (Also the DSI filter module.)

http://instagram.com/p/q19oHwn6dL
akrylik
Rene and Metropolis are not a trend lol And I think Audio Damage has put the jacks on the right side.

It's hard to satisfy everyone on the jacks on top vs bottom debate for sequencers. Personally, I think modules that are meant to go in a "controller" skiff should have jacks on the top (like Rene and Pressure Points) but everything else should have jacks on the bottom. In a way, skiff-oriented modules should be almost considered a different format. Just my 2 cents.
joey
dying for this thing!!!
ether
Joining in the fun on this thread. Looking forward to some demos that convince me that it can out 185 the Metropolis.

May the best sequencer win (I can only buy one)... fight!
Crandall1
Just a little update:

We're firming up the firmware at this point, but the sequencer is mostly done, and we're about to pull the trigger on the production run. If you want to see it running a 64-step loop, I put up a video last night. The video is more about tape loops and such than the sequencer, but there you go.

We have a plug-in release this week, so I'll largely be concentrating on that, but after that's done, prepare yourself for a deluge of Sequencer 1 videos; it is definitely far enough along that it can be demonstrated in full now.

flo
Good times! SlayerBadger!
dmod
Cool vid! Can't wait to get that sequencer though! Can I resist the euro gas a little longer? That Orbitals is looking good but I know it aint no Sequencer 1 son! SlayerBadger!
cbeefheartuk
I will buy this the minute I can send my pennies somewhere.
Boddhisattva007
What software??
Crandall1
What software for what?
madcap
What's on first
filtermod
No, What's on second. Who's on first.
thelizard
So the patterns are saved to an SD card? Fun thought: write a script to generate algorithmic patterns and copy them over.

Will the pattern files be something easy to read (like XML, JSON, etc.), or is that tough to pull off in an embedded situation like this?
Crandall1
thelizard wrote:
So the patterns are saved to an SD card? Fun thought: write a script to generate algorithmic patterns and copy them over.

Will the pattern files be something easy to read (like XML, JSON, etc.), or is that tough to pull off in an embedded situation like this?


Adam will have to answer the technicalities of that, and what you can do with the files and such-like, but yeah, the patterns are saved to SD card. The SD card is one of the "micro" ones and lives on the back of the unit. It will also be the method for user-upgrading the OS.
Crandall1
We're about to ordering the panels for the production run, and I thought you guys might like to see the final artwork. Here it is.
juvation
looks great! just have to move all the jacks to the top and it'll be done!

hihi
Crandall1
I'll note that nobody's giving the Stepper Acid people a hard time about jacks on the bottom.
maudibe
Jacks at bottom be fine... just put the sequencer at the top QED.

For griefs sake... this is a brilliant module - why the hassle about the jack placement really. Not *everyone* want this in a skiff. It really is a system module so the jacks at the bottom makes sense.

Left to right, top to bottom is a nice way to work IMHO

Thanks for all your hard work Crandall1

Guinness ftw!
juvation
you did see the smiley, yes?

sequencer at the top is a great way to get RSI. sequencer at the bottom either sloped or horizontal is a great way not to get RSI.

just noticed the Stepper Acid. i don't plan on buying one, therefore i won't air my views on jack placement in the thread. if other people care, fly, fly, my lovelies :-)
Crandall1
I was joking too; just forgot the smiley.

As an aside, though, one thing I've noticed about the Euro scene, such as it is: since there's no "right" way to do things, everyone becomes convinced that the way they've landed on is the "right" way and all other ways are stupid.

I've noticed this in many threads, but especially those where someone is seeking advice about a particular technique. Someone will say "well, this is the way to do that." Then someone will chime in about how stupid that way is, and their way is the right way. Etc.

Of course, we see this in the wider music tech world; it's especially bad in guitarland, where hero worship is the order of the day. But suffice it to say, the only "right" way to do something is the way that achieves the result you want, and is enjoyable in the meantime.

All this by way of saying to each is own, and the cobbler to his last. 8_)
juvation
sorry, i was largely responding to maudibe. miscues all round in this thread :-)

i remember RSI from vertically racked gear in the 90s.
studionebula
thelizard wrote:
So the patterns are saved to an SD card? Fun thought: write a script to generate algorithmic patterns and copy them over.

Will the pattern files be something easy to read (like XML, JSON, etc.), or is that tough to pull off in an embedded situation like this?


I considered using XML to save pattern files, but couldn't see that the development cost (i.e. time) was worth it. If there's enough interest it could be added later.

I'll just mention in passing that designing and prototyping the hardware, and writing the software, has occupied virtually all of my working hours since late December. This is a big project for a two-person company. Bells and whistles like XML file formats will have to be deferred at least until a post-initial-release update. It will be a great sequencer as of version 1.0, and it will get better after that. But we have to get 1.0 out the door first.
maudibe
RSI? Repetitive Sequencer Injury smile

OK... see your point there Juvation.... ah the things we do for modulars eh?

hihi
sonicwarrior
Crandall1 wrote:
I'll note that nobody's giving the Stepper Acid people a hard time about jacks on the bottom.

It's because it's made by a girl. Nobody wants to discourage girls who are into module making. wink
windspirit
sonicwarrior wrote:
Crandall1 wrote:
I'll note that nobody's giving the Stepper Acid people a hard time about jacks on the bottom.

It's because it's made by a girl. Nobody wants to discourage girls who are into module making. wink


Here we go Dead Banana
windspirit
So sorry to harp on the top vs bottom jack thing but if the jacks are duplicated with an expander pin set on the back you could have a breakoit/ diy a breakout that goes on the side/ in a 1u row on the top. I realize this is waaaay too late to change anything but i figured id share my thoughts on the subject anyways.
Crandall1
Jacking off aside (SEE WHAT I DID THERE??!?!) today's build has the best feature of Sequencer 1 totally working, and it is, in my opinion, shit-hot. It might have been difficult for some to discerne what we were talking about when we mentioned the REP latching modes. Those are all good now, and I just busted out a couple Instagram videos a few minutes ago to show them in action.

In this first one, I'm triggering the REP modes from the front panel, as if in a live performance situation. As you can see, there are 6 modes in all: last 8 steps, last 4, last 2, and last step, as well as 1/2 (which ratchets at double time) and 1/4 (which ratchets at quadruple time.) The cool thing about these modes is when you let up the button, the sequencer picks up where it would have been, not where you left off.

http://instagram.com/p/rYEmoEn6b7/

In this second video, I'm triggering the REP modes via CV. When "REPEATS" is set as a CV target, positive voltages (1 through 4 volts) trigger the latches, and negative voltages (-1 and -2V respectively) trigger the ratchets.

http://instagram.com/p/rYGT1xn6eh/

I'm going to do a long HD video this weekend showing programming the unit from a blank pattern to crazy CV control, but until then, hopefully these two little iPhone videos will give you an idea of what madness we're creating here.
qu.one
Can't wait for this!!!!
windspirit
i think im in love! Lotsa Love
flo
SlayerBadger! I think I'll have to throw a couple of at this soon we're not worthy
granville
Yeeeeeehaw! w00t w00t w00t
juvation
this looks fab! i love the resuming at the correct spot, prevents timing headaches. and controlling the ratchets via CV is great, as i won't be able to see or operate the module once it's patched up.

(ok i'll stop now)
maudibe
Looks great. Can't wait Guinness ftw!
the untitled
Oeh this is nice too!
skeller047
I have just one question.

When?

Oh and a second, much less important, one: How many 's?
windspirit
Nodular grid says $600 but i think after a little more time on the forum you will learn that asking module makers when an in-developement module is being released can be a fools errand smile
flyingMono
Seeing so many cool sequencers makes me regret having 2 Klees.
Crandall1
Like windspirit says, it's difficult to line all this up and say "It'll be out on $date." So many variables. (In that regard, I vastly prefer dealing with software releases, which are much easier to predict.)

Now, with that said, here's where we're at:

1. The 1.0.0 version of the software is not done; it is not feature complete. It is very close, however. I'd say that 90% of the features are in place, and it is very usable at this point. Probably a solid week of work and testing will get us a release candidate worthy of the name.

2. All the parts for the production run have been purchased, and are at WMD, except the front panels. (This includes knobs, switches, jacks; all the stuff that comes from either Europe or China.) We've been holding on the panels because we didn't want to end up with a button named "X" that actually did "Y." We'll almost certainly order the panels next week.

3. The build itself takes four weeks, and some parts of it can be done without the panels. I am comfortable saying that we will _PROBABLY_ start the build next week or the following.

4. Once the build is done, we get the modules in groups of 50 or so. Since we have so many dealers, we'll have to decide how to send them out, and how many to hold for direct sales. But expect there to be rolling shortages until the full run is done.

5. During that time, the 1.0.0 release of the software will get updated as we get reports from customers. We'd like to say it'll be perfect when it leaves the shop, but that's not the case. However, this unit is easy to update, and we are, at root, a software company, and are very good at dealing with minor bugs.

That's the current roadmap. The tl;dr version: two months? The price will be $599; of that we're certain. (We ballparked that before we'd received quotes on the build. However, we were spot-on, so that will definitely be the price.)
Kent
Panel art idea:

Ditch the "REP" parts of "REP 1", "REP 2", "REP 3", etc. It is obvious what they are for once the manual is read. Use the gained space to increase the size of the numbers to make it easier to read for live performances in low light. The "REP"s are redundant.
obviousless
Well done audio damage. This module looks awesome to me. I am looking forward to seeing what music people create with this sequencer. we're not worthy
windspirit
I really want this. Selling off some stuff in anticipation.
Crandall1
The usual bi-weekly update:

1. Front panels are ordered from MPC.

2. All parts are here.

3. First Article being built tomorrow to verify the programming on the SMT 'bot.

4. Code is 95% done. Just codifying the feature set and killing bugs at this point.

We're pleased to announce that Sequencer One will have, at shipping, three (!!!) tempo-synced LFOs with at least 9 waveforms, attenuators, +/- voltage, and phase offset. We were a little nervous about these guys, so we hadn't committed to them, but Adam got all that working yesterday, and it rocks like a champ.

So, long story short: for the last 6 months, I've been saying "two months!" For the next 2 months, I'll be saying "one month!" At some point in the future, I'll switch to "weeks" instead. Eventually, we'll get there.
ignatius
really great Chris! 3 LFOs.. wow.. what a bonus. 9 waveforms.. fuck. that's hot.

that'll be quite nuts w/the ratcheting step repeat chumbawumba
dmod
In have a fund set aside just for this sequencer. I have full faith this will be the shiat! The Chewbacca Defense And 3 LFOs what!?!? Wow! Only problem is the waiting game...... hyper
cbeefheartuk
This really sounds brilliant.. probably the most excited I have been for a module - was looking at buying another LFO so that sounds perfect for me..
Isolde and Isobelle
This sequencers features sound great. I have been sitting on the fence about which new sequencer I am going to buy... still not decided between this/Klee/ or even the Sequentix Cirklon.

I guess it may come down to what the UK retail price is for the Audio Damage unit - I intend to place it in its own case alongside a few other suitable modules.

Decisions, decisions. very frustrating
Crandall1
I just put up a video on YouTube of some of the more esoteric features of Sequencer 1. This video shows:

1. Hz/V and inverse triggering, by driving a Yamaha CS-5 directly. Sequencer 1 can output either V/Oct or Hz/V, and the Gate output can be normal gates, inverse gates (what Yamaha analogs use) or true S-Trig (what Korg and Moog analogs use).

2. Live latching and ratcheting. You can see me pressing the REP 8/4/2/1 and RAT 2/4 buttons on the front panel while the sequence is running. You can also clearly see that the sequence picks up where it should have been when you release. These can also be triggered via CV input.

3. External sync. Sequencer 1 is being driven, in this video, via an Expert Sleepers ES-4 module, using Silent Way Sync. The clock output of the Sync plug-in is going to Sequencer 1's clock input, and the Run (high) output is going to Sequencer 1's Reset input. (In this manner, Silent Way Sync will start and stop Sequencer 1 in sync with the DAW.)

maudibe
SlayerBadger!

More demos appreciated smile keeps us all happy
flyingMono
I need to stop watching these demo videos and going to this forum in general. My bank account can't keep up. Needless to say this is pretty sweet! Dead Banana
Crandall1
We're making some monster progress this week. Almost all the features are in at this point. I'm feeling very sanguine for an Oct. 1st release date.

But yeah, you're about to get so many videos you'll be all "Jesus, will you stop already?"
dmod
Crandall1 wrote:
We're making some monster progress this week. Almost all the features are in at this point. I'm feeling very sanguine for an Oct. 1st release date.

But yeah, you're about to get so many videos you'll be all "Jesus, will you stop already?"
Ah yeah some good news! Can't wait! This one is pre-order worthy!
w00dw0rth
Looks super interesting. May have to make this my 2nd sequencer. Gotta touch it first though. Any sense of who might have a "floor model" first?
Crandall1
I imagine that Muff's, Big City, and AH will all get theirs around the same time. The midwest, Canadian, and East Coast dealers will be a couple days later, and Europe a week or so after that.

(EDIT: It should be noted that it is really up to the retailers. We'll begin shipping when we begin shipping, and either they get their orders in or they don't. We don't actually have any control over that. Some of them take longer than others.)
flyingMono
dmod wrote:
In have a fund set aside just for this sequencer. I have full faith this will be the shiat! The Chewbacca Defense And 3 LFOs what!?!? Wow! Only problem is the waiting game...... hyper


and the depth of my wallet. hihi
VanEck
9 waveforms is a lot... what are the shapes? Any S&H or random types?
flo
And how slow/fast will they go...?
Crandall1
The shapes right now are:

Sine, Ramp Up (saw), Ramp Down, 1/8 Pulse, 1/4 Pulse, 3/8 Pulse, 1/2 Pulse (square), 5/8 Pulse, 3/4 Pulse, 7/8 Pulse, 1/2 Sine, 1/2 Ramp Up, 1/2 Ramp Down, 1/2 Triangle, and Random.

So currently 15 shapes, and we may add more. The LFOs don't free-run; they are tempo-synced. So the length controls the number of steps, from 1 to 256 steps (essentially 16 measures.) The other controls for each LFO, besides shape and speed, are Amp (0-100%, where 100% is the maximum you've set the output for), Range (+/-, +, -), and Phase (0 - 360). The settings for the three LFOs are stored per pattern.

In short, these are some pretty bad-ass LFOs.
knobbyfischer
So excited for this - I really love the layout and....I'm really getting sick of waiting around for a Metropolis SlayerBadger!
obviousless
Awesome demo! I knew that I liked the concept of this, but seeing it in action cemented my feelings that this is a really powerful, but intuitive sequencer. It is nice to have this level of control and flexibility of your sequence in a modular environment. we're not worthy
SunSpots
Need a third 12u...
Dogma
Having an A4 I cant see much bar a vague visual similarity but apart from that functionality wise this looks like a much deeper affair. So whats the link between them?
ignatius
pretty awesome! bad ass LFOs indeed.

congrats to you and Adam applause Guinness ftw!
Crandall1
Dogma wrote:
So whats the link between them?


Well, they both put notes in a row. For this product, we said "well, we like the A4 sequencer okay. Wouldn't it be cool if it was actually in the rack and not a separate box?" Then we just added shit to it until it was fun. And left off the stuff that wasn't fun. Not much more to it than that. (He said, making light of 8 months of design and coding.)

Anyhow, I just banged up a quick video showing what the LFO can do. Have a gander.

Dogma
i really like what Im seeing. Has this been priced yet?
windspirit
Dead Banana want
flo
Those LFOs look like a ton of fun. I reckon you routed it to CV1 out? Can it be routed to any of the CV outs, including the V/Oct (in addition to the internal parameters you mentioned)? For easy addition of vibrato I mean... Luckily, 1 step is just slow enough at the BPMs I usually work for some nice vibrato thumbs up
VanEck
Nice... the time synched LFO's work just as I had hoped and imagined. Reminds me of the time synched LFO's I used to muck with on my TEMPEST. Very useful addition.
warmtape
...that sad moment when you resign yourself to dishing out hundreds of dollars
lilakmonoke
a time synched variable shape lfo + sample/hold IS a step sequencer. if you have about 3 lfos involved my guess is you can do every melody in the known universe and you are not limited to 8/16/32 steps.
ben_hex
Dead Banana Dead Banana Dead Banana Dead Banana

Those LFO additions are ace!
Crandall1
flo wrote:
Those LFOs look like a ton of fun. I reckon you routed it to CV1 out? Can it be routed to any of the CV outs?


There are three LFOs, one for each CV out. At shipping (and I'm not saying this will always be the case, just the v1.0.0 version of the software) if you want to route one of the LFOs to an internal parameter, you need to patch it (with a patch cable) to one of the CV inputs.

So, tl;dr: LFO1 goes to CV1, LFO2 goes to CV2, and LFO3 goes to CV3.
flo
Ok... So no internal vibrato added to the V/Oct... Thanks for the clarification!

Would be really cool if in a future update they could be freely routed (to the outputs, but maybe also to internal functions?) - that way in addition to my vibrato fetish, you could for example route all three to CV1 out for some whackyness etc...

Cheers!
studionebula
flo wrote:
Ok... So no internal vibrato added to the V/Oct... Thanks for the clarification!

Would be really cool if in a future update they could be freely routed (to the outputs, but maybe also to internal functions?) - that way in addition to my vibrato fetish, you could for example route all three to CV1 out for some whackyness etc...

Cheers!


Okay, you just touched on one of my patching fetishes, which is to combine two or more LFOs to create complex modulation signals. Yeah, I want that now, too.

As Chris said, for the initial release each LFO is hardwired to its corresponding output, but that could change in the future. Currently we are entirely focused on completing and delivering a solid product without letting feature creep derail us from that goal. However, now that we've been working with the system for awhile (including the LFOs), I have verified that we have plenty of horsepower left in the CPU to do other things in the future. I really don't want to go down the road of selling a product based on promises of what it will be someday, but I will say that it's a safe bet that this sequencer will gain features over time. Which features and when, exactly? No way to say. Maybe we'll have to take polls or something to establish what people most want after they've spent some time with version 1.0.0.

In any case, thank you all for your feedback and enthusiasm!
flo
Good to hear that! hihi

I think you're doing a great job so far of balancing openness and feature creep thumbs up
Endorfinity
read the whole tread... oh shit this is amazing sequencer. the thing i liked most in it is the balance between features and playability, its great in both regards!
dreamtrak
This looks so good. Perfect way to get my CS-10 involved too grin
flyingMono
Feature Creep is my new band name.

Seriously though, I'm happy this is being rolled out as an already solid sequencer with room to grow. I just hope all the updates will be easy for V.1 people.
Crandall1
The Weekly Update: the sequencer software is now in feature freeze, and we're on to bug hunting. A pair of "first article" units have been built. (These are the ones that the contract assembler makes to test the programming on the pick-and-place robotics.)

As you can see from the video below, which I put up in my personal YouTube account yesterday afternoon, the sequencer is in a very usable state, other than a couple little weird things I've come across that Adam is addressing. In this video, Sequencer 1 is controlling two different sounds simultaneously, and I'm doing pattern switching on the fly. It is also running in sync with Ableton Live via Silent Way and an ES4. (The drums are coming from a custom monome live performance sequencer patch for Max4Live that I'm showing off; the true purpose of the video.)



Anyhow, the first beta unit is going to our main tester for this product on Tuesday; he's the first one outside of Adam and I to get a unit, and hopefully he won't find anything ugly. So, we're definitely in the home stretch.
flyingMono
Nice video, keep em coming!
maudibe
Nice applause

It is swaying me back to the original plan to get one of these d'oh!
dmod
The Chewbacca Defense
Crandall1
Time for my bi-weekly status update:

1. The software is in RC1, and is now being beat upon with vigor. The only thing remaining to be coded is the bootloader/field upgrade modus.

2. The hardware is at assembly. Panels will be here on the 17th, and we assume we'll start getting hardware shortly thereafter.

So, I don't think you'll be able to _start_ October with a Sequencer 1, but you'll definitely be able to finish October with one. I'll have some more video on Sunday evening; I'll cross-post here when I do.
dmod
oh yeah baby! I am turning into such a fan boy! Look out! lol Seriously though I am excited!
mikecameron
Any chance one of these will be at Knobcon?
windspirit
KNOBKAAAAAAAAAAHHHNN!!!!
Crandall1
No, Sequencer 1 will not be shown at Knobcon, sorry.
Crandall1
Time for the bi-weekly update.

1. The panels arrived from MPC today, so I can start doing proper videos and photos.

2. The only part we're waiting on is the little micro-button-things (I forget what they're called; tact switches?) that are the octave up/down controls; they were back-ordered, but should be here in a couple days.

3. The PCBs have been made, and are ready to go. The 'bots have been programmed.

4. RC1 of the software is being tested.

So basically, the fat lady is singing at this point. As soon as she wraps it up, we'll be shipping these bad boys.
clusterchord
looks fantastic, love the design.. thumbs up


and cudos for using the "Waldorf" knobs. these are some of my favorites.. really nice grip/feel to edit things. i have them on XT and Q, and some spares in different transparent colours ,,, so i can customize the AD Seq hihi
KrisM
Oh my.
wirelesswine
Great news. Can't wait to see new demos!
Kummer
@Crandall1

Wondering if you would care to comment on the Synapse in your system. Have you by chance tried using it with the Keith McMillan Qunexus? I have one coming tomorrow (for that very reason) and while I don't see why it wouldn't work, I guess you can never be sure.

EDIT: Almost forgot, GO SEQ1! It's on my list for sure.
Crandall1
I don't have a Qunexus, so I can't comment.
Kummer
Crandall1 wrote:
I don't have a Qunexus, so I can't comment.


Shot in the dark, thanks anyways.
KrisM
"In the same manner that the MIDI triggers in Replicant work, basically, if you own that plugin"

if I buy two, will you make Axon next? applause
maudibe
Love to see a manual for this… even if it is just a draft.

Looks great applause
Crandall1
KrisM wrote:
if I buy two, will you make Axon next? applause


We have two other products in the pipeline first, but Axon can easily (for values of "easily" that include weeks of swearing and existential crisis, wondering why we bother, sobbing to ourselves quietly in the corner, and financial meltdowns) be iterated from the Sequencer 1 platform, and is very much in our mind.

There will _definitely_ be a neural network sequencer in our product line, in other words. Probably a year away, assuming this is successful. If this isn't successful, well... we tied up the entire company's resources for a year, and we're broke now. So, you can do the math on that.
Crandall1
I ran a sync test overnight for 12 hours, starting at 7PM yesterday. This Instagram video shows the results. No skipped steps, no drifting, still in perfect lock, Sequencer 1 -> Sequencer 1 -> uStep -> RCD.

http://instagram.com/p/tSq7Mun6Ra/

With the three synced internal LFOs and the "accent" out, in addition to the clock output, Sequencer 1 is a _ridiculously_ powerful master clock.
NoMoreNightmares
That's awesome! For my part, I am gladly waiting for your sequencer. It just seems the most inline with my previous experience and how I envision sequencers in general.
Kummer
Crandall1 wrote:
KrisM wrote:
if I buy two, will you make Axon next? applause

There will _definitely_ be a neural network sequencer in our product line, in other words. Probably a year away, assuming this is successful. If this isn't successful, well... we tied up the entire company's resources for a year, and we're broke now. So, you can do the math on that.


Kickstarter?
KrisM
Kummer wrote:
Crandall1 wrote:
There will _definitely_ be a neural network sequencer in our product line, in other words. Probably a year away, assuming this is successful. If this isn't successful, well... we tied up the entire company's resources for a year, and we're broke now. So, you can do the math on that.


Kickstarter?


This could be the start of Skynet nanners
maudibe
and the manual..... draft is good, 'cos perhaps we can help / comment / clarify / ask applause
djempirical
Oh man am I excited for this....
dmod
Have some lettuce set aside for this one! Never maintain cash savings again
mysterymachinestudio
Super eager to see more demos and check this out. It looks like it works the way my brain wants sequencer to work.

Will these be showing up @ the Muff retail store when they get released? Was a final price ever stated? (I read this thread some time ago and can't recall...)

Thanks! Rockin' Banana!
Bogus
Looking forward to this still
Crandall1
Bi-Weekly Update, version 456:

1. As I mentioned last week we got the panels. Unfortunately, over half of them were damaged in shipping and need to be re-done. So the first shipment of Sequencer 1 will be... limited. We're still trying to figure out how to deal with this.

2. The software has been fully tested, and found to be pretty much ready-to-ship. The only programming that remains for v1.0.0 is to write and test the bootloader that enables field programming. (So you can just put the new OS on the SD card, and it flashes itself.) This has been started, but it needs to be fully tested.

3. The first production units will be rolling off the line this week. So, once we have figured out #1 and #2, we can ship, basically. I will be adding Sequencer 1 to the Audio Damage store this week, with the first draft of the manual; I'll also be making the product glamour shots and programming tutorial videos. (Although, if you're used to this thing, the functionality should be pretty self-evident. If you own an Elektron product, you know how to run Sequencer 1 already.)

Anyhow, with that out of the way, here's a video of me programming a "Berlin School" (sorta) pattern from bare metal. Patch is WMD PDO -> DSI Curtis Filter -> WMD Multimode VCA -> Circuit Abby, with a send to DubJr at the end. EG for the VCA is from the Doepfer Quad ADSR. All modulation is from Sequencer 1.

Bonobo
That is a pretty tempting video hyper

When this was first announced, I didn't imagine it being so instant. Seems like you could get a nice groove going very quickly!
dmod
I am excited as hell. I think this type of sequencer will compliment my other more old school style sequencers perfectly. Take my money!
flo
Great video! Programming really seems to be super easy and intuitive. Looking forward to this!

I really think you should look into a tap programming mode soon hihi That would make it a total nobrainer IMO. SlayerBadger!
VanEck
Really digging the new video and the chance to check out some of the CV/LFO assignment functionality.

I think the Sequencer 1 and my Metropolis will make very good companions... is the first batch of sales going to be direct through your website, or divided up between direct sales as well as distributors?
dubonaire
flo wrote:
Great video! Programming really seems to be super easy and intuitive.


Don't forget this guy knows electronic music making inside out as well as the design philosophy of the sequencer. YMMV.

I guess that's not a helpful compliment but Crandell really is very adept.
flo
Yeah man I'm aware of that, but since you could see each step in the video, I was concluding that I got most of it on the first watch and that it thus should be rather easy...
Crandall1
For what it's worth, I don't know the sequencer as well as I'd like to think I do, as the video shows. (When I hook up CV1 Out to CV1 In at 2:00, I merrily start programming LFO3, which isn't hooked to anything yet, and does exactly nothing.)

In any event, while it may be true that I've been doing this sort of thing for a couple decades, and so has Adam, the side benefit of our cumulative 50+ years of experience making electronic music and the 100+ commercial software and hardware products we've designed between the two of is is that we know how to make things easy to use.

Or at least we think we do. dubonaire's point that YMMV stands. The side effect of all that experience is that some things that are ridiculously obvious to us are not at all obvious to others. *shrug* You take the good with the bad.
flo
When you've learned to operate a MC202, no sequencer can scare you anymore hihi I'm positive that this is the shit interface-wise hyper

EDIT: still interested in intentions regarding tap-mode programming though hihi
gonkulator
I will keep my eye on this. I like the results of the video, and if there is a significant level of operation that avoids combo keys, I will probably stay interested.
Crandall1
Yeah, virtually every major feature has either a direct button or an alt-press. For features that require more than one screen, you just push one of the encoders to go to the next screen. Most multi-screen features are only 2 screens; there are two that are three screens, but we put the least-used info on the third one.

Ultimately, it's a trade-off, because if you try to do one button per feature, you end up with the Zeit. So we are fighting space and cost (which, in Euro, are essentially the same thing) on one side and usability and directness on the other. It was a fun challenge, and I am of the personal opinion that we made it as direct as possible given the context.

I'll do a melodic programming video this afternoon so you can see how, with a little practice, you can quickly enter a melody. But that said, this unit really excels in the sort of "what would happen if we..." kind of exploration we all love in modular. That's what we made it for, and it's really easy to experiment with it.
gonkulator
Crandall1 wrote:
..., this unit really excels in the sort of "what would happen if we..." kind of exploration we all love in modular. That's what we made it for, and it's really easy to experiment with it.


That itself is very encouraging. Thanks.
dubonaire
Crandall1 wrote:
For what it's worth, I don't know the sequencer as well as I'd like to think I do, as the video shows. (When I hook up CV1 Out to CV1 In at 2:00, I merrily start programming LFO3, which isn't hooked to anything yet, and does exactly nothing.)

In any event, while it may be true that I've been doing this sort of thing for a couple decades, and so has Adam, the side benefit of our cumulative 50+ years of experience making electronic music and the 100+ commercial software and hardware products we've designed between the two of is is that we know how to make things easy to use.

Or at least we think we do. dubonaire's point that YMMV stands. The side effect of all that experience is that some things that are ridiculously obvious to us are not at all obvious to others. *shrug* You take the good with the bad.


My comment certainly wasn't intended to criticise your sequencer which looks very cool (and I should have said that). I've just watched many of your videos and know how quickly you can create a well resolved track.
Daisuk
Looks pretty damn good. applause Can you play the mini-keyboard manually, or does it just set the notes for the steps? And can you record the keyboard notes unquantized "live" as you can with the Analog Four?

I sold my A4 a few months back, and now I'm tempted to get this, goddamnit. lol
Crandall1
You'll be able to play the mini-keyboard manually in a future update; the shipping software will not have that feature. As for live recording, we're working on it. That's a very tricky thing to get right.
Kummer
In some ways the workflow sort of reminds me of the matrix sequencer in reason (which I love!).
studionebula
Many thanks to my partner Chris for keeping things ticking along while I was out of the country on a much-needed vacation with my SO. I managed to write a good chunk of the manual on the flight home, so yeah, we'll start posting drafts soon.

I personally am delighted with the solidity and feature set of the software at this point. Yes, we have a substantial wish-list of things we intend to add with future updates, but the system works beautifully right now and easily satisfies my own selfish desires regarding what a modular sequencer should do. I will indulge in an uncharacteristic expression of hubris and say that I'm incredibly proud of this product. Dono-Kun Dance

The bootloader is the last remaining substantial hurdle. It's mostly done, but we need to be absolutely sure that it's bulletproof before we ship since, as Chris put it eloquently in private conversation, it's the the one part of the software which we absolutely cannot fuck up.

So, thanks again for your patience and your enthusiasm. We're almost done.
flo
Crandall1 wrote:
As for live recording, we're working on it. That's a very tricky thing to get right.


SlayerBadger!
Daisuk
Crandall1 wrote:
You'll be able to play the mini-keyboard manually in a future update; the shipping software will not have that feature. As for live recording, we're working on it. That's a very tricky thing to get right.


Cool, thanks! thumbs up Looking forward to seeing this thing more in action. smile
dubonaire
studionebula wrote:
Many thanks to my partner Chris for keeping things ticking along while I was out of the country on a much-needed vacation with my SO. I managed to write a good chunk of the manual on the flight home, so yeah, we'll start posting drafts soon.

I personally am delighted with the solidity and feature set of the software at this point. Yes, we have a substantial wish-list of things we intend to add with future updates, but the system works beautifully right now and easily satisfies my own selfish desires regarding what a modular sequencer should do. I will indulge in an uncharacteristic expression of hubris and say that I'm incredibly proud of this product. Dono-Kun Dance


That's awesome. It's not hubris. It's just pride. There is nothing wrong with being proud.
jsousa
how would you pitch this seq to someone looking into a Rene or something similar?
Crandall1
jsousa wrote:
how would you pitch this seq to someone looking into a Rene or something similar?


Other than the fact that they both put CV/gate info in to some sort of linear time cycle, they are very different beasts. Sequencer 1 has _far_ more features and functions than René, and it will pick up even more over time. On paper, it's not even funny. (This is largely a function of the fact that the CPU is 5 years further along on the Moore's Law timeline, though; just the way things work out.)

On the other hand, the design of René makes it very good for exploration and experimentation without a set goal; this is quite important in the Euro world, and isn't to be taken lightly. Sequencer 1 is much more direct and traditional in its approach.

Other than that, it really depends on your personal taste. On the one hand, you don't have to lick your fingers to use Sequencer 1. On the other, it doesn't look as cool. *shrug*
Crandall1
I have some news, which some of you may not be thrilled about, but there's nothing to be done. We did all the books for the sequencer, now that we've paid for everything, and we're going to have a final MSRP of $699.

This is very disappointing to me, as I really wanted to come in under $600, but there's no way that could occur. But it is what it is.
dmod
Crandall1 wrote:
I have some news, which some of you may not be thrilled about, but there's nothing to be done. We did all the books for the sequencer, now that we've paid for everything, and we're going to have a final MSRP of $699.

This is very disappointing to me, as I really wanted to come in under $600, but there's no way that could occur. But it is what it is.
Ya ouch! I still want one but may have to sell an extra module for this or just hope they are still available in a month? cry
Bonobo
I don't think anyone will be that upset, I think most would rather the constant updates and info with the understanding not everything will pan out exactly as planned than have to wait for it to be set in stone before getting the details.

I'm in the UK so converting that to GBP still seems like a steal at £430, but of course US-UK prices seem to be more 'switch the $ to a £' than a 'convert the currency' very frustrating
djempirical
$699 is tough, but frankly, this thing is feature-packed, and will only get more so. (Not that it's always safe to pay for *future* features, but you know what I mean.)

Now if I could just sell these "extra" modules I have, I'd be set. razz
Crandall1
Bonobo wrote:

I'm in the UK so converting that to GBP still seems like a steal at £430, but of course US-UK prices seem to be more 'switch the $ to a £' than a 'convert the currency' very frustrating


Yeah, the shipping and tariffs really eat you guys alive. (Not to mention the current currency disparity; the dollar is quite strong right now.)

That said, you're always welcome to order from the AD site, which is a direct conversion as we charge in dollars; of course, you'll have to pay the customs fee on your end, but *shrug*.

(Edit: I feel like I'm gonna be paying for that comment down the road; we actually sell very few modules direct through the site, as people prefer to go to their retailer they know. But I'm virtually assured angry letters from Euro retailers for this. THE THINGS I DO FOR YOU!!!!)
Bonobo
haha I appreciate the offer, your right though customs fee's are a bit of a mystery to me. Sometimes its nothing, sometimes its huge. I gave up with it and just go for a retailer with a set cost now to avoid the nasty surprises.
filtermod
Crandall1 wrote:
I have some news, which some of you may not be thrilled about, but there's nothing to be done. We did all the books for the sequencer, now that we've paid for everything, and we're going to have a final MSRP of $699.

This is very disappointing to me, as I really wanted to come in under $600, but there's no way that could occur. But it is what it is.

I currently only own some of your software products, but they have all proven to be worth every penny. Your hardware looks to be no exception to this rule.
I will absolutely be picking this up when I have the funds. It should provide the perfect counterpart to my Metropolis. Hell, I'll probably use it to clock the Metropolis!
Kummer
Bonobo wrote:
I don't think anyone will be that upset, I think most would rather the constant updates and info with the understanding not everything will pan out exactly as planned than have to wait for it to be set in stone before getting the details.

I'm in the UK so converting that to GBP still seems like a steal at £430, but of course US-UK prices seem to be more 'switch the $ to a £' than a 'convert the currency' very frustrating


While on occasion it does work to your favor, in general it seems you guys get over charged a lot.
dmod
Well I guess I am one of the guys who is not happy about the price but I do have a lot of faith in this sequencer that it will be the most powerful one money can buy in eurorack. I know it will be awesome so even though $700 is a chunk of hard earned change for me I will still make this investment because from everything you have put into this it most definitely looks like THE SHIT! SlayerBadger! Now if you could please give me a rough but somewhat accurate timeframe of when this will be ready to ship or take pre orders I would love to know so I can plan out how I am going to pay for this bad boy! Cheers! Guinness ftw!
Crandall1
We won't be doing pre-orders. It will be shipping in about 2 weeks. The first run from the assembly plant is getting tested as we speak (type?), and will be here in a few days. We then have to blow in the final software and do our own testing. The first batches will be going to Analogue Haven and Control, and they will also be in our online store.

Side note: due to the nature of the Massive Front Panel Disaster Of 2014, the initial quantity is _very_ limited. There will be enough for everyone eventually, but in the first couple weeks, they're going to be in short supply. The vast majority of the first run are going to AH and Control; we'll only have a few units for sale in our store.
dmod
Crandall1 wrote:
We won't be doing pre-orders. It will be shipping in about 2 weeks. The first run from the assembly plant is getting tested as we speak (type?), and will be here in a few days. We then have to blow in the final software and do our own testing. The first batches will be going to Analogue Haven and Control, and they will also be in our online store.

Side note: due to the nature of the Massive Front Panel Disaster Of 2014, the initial quantity is _very_ limited. There will be enough for everyone eventually, but in the first couple weeks, they're going to be in short supply. The vast majority of the first run are going to AH and Control; we'll only have a few units for sale in our store.
Ok great! thanks for the heads up that is about a good as answer as I could hope for. I bet Control will do pre orders they usually do. Time to cough up some extra lettuce! Cheers!
Funky40
just wateched the video: Great !

Q: is there a visual feedback while the sequenze is running which note is set at each step ?

the thought that immediately came to mind is:
it would be cool if the little keyboard would "highlite" the programmed Note, according to each step, while the sequence is playing .
not shure if that would be doable or "disturb" the programming ?


next thought:
so you can do a elektron style sequenzer ?,
please make a multitrack CV sequenzer as a desktop unit.
my feel is that it would make more ...or lets say ---> much sense space vs. money vise.

Cirklon is great for its own, but to my taste can´t be compared to something elektron style like which is much faster and much more immediate,
though much more Eurorack-suited. my opinion, YMMV

if my english was not clear enough, probably someone might translate lol
mysterymachinestudio
Love the video. The price will keep me at bay for a bit, but the functionality and sound will have me coming back sooner or later. Beautiful work!
euromorcego
It shows up at Schneidersladen, late October the page says:
http://www.schneidersladen.de/en/audio-damage-sequencer-1.html

Quote:
so you can do a elektron style sequenzer ?,
please make a multitrack CV sequenzer as a desktop unit.

yes, please!

And: Would it be possible (at least in theory) to add a serial midi output (maybe hidden on the back, via a breakout module). At some point i would love to have such a sequencer also for some of the midi gear, running in sync with modular percussion. Probably not feasible this time, but in general it should be possible to generate a midi signal, given that the whole things runs on some processor with digital output.
Elguapo505
All about this! Yes please!
Kummer
Don't mean to criticize, but there are two things I would change. 1st there doesn't seem to be a clear distinction between outputs and inputs. A black box or ring around the outs or ins would help people differentiate between the two. 2nd something should be written above the 3 multi function knobs. Even if it's just "multipurpose knob 1", "knob 2", etc.. Or something to that effect. It seems to bare in the upper right and no connection between the knobs and what they are used for specifically... Obviously I and most people here can figure all this stuff out, but to someone not familiar with modulars and maybe buy this as their first sequencer, it would help. Just my .02

Edit: upon further inspection it does appear there is a color or value difference between the inputs and outputs. Could be the lighting though, I'm not sure.
spritepixie
Crandall1 wrote:

This is very disappointing to me, as I really wanted to come in under $600, but there's no way that could occur. But it is what it is.


Still a good deal for an Audio Damage button
Crandall1
Kummer wrote:
Don't mean to criticize, but there are two things I would change. 1st there doesn't seem to be a clear distinction between outputs and inputs. A black box or ring around the outs or ins would help people differentiate between the two. 2nd something should be written above the 3 multi function knobs. Even if it's just "multipurpose knob 1", "knob 2", etc.. Or something to that effect. It seems to bare in the upper right and no connection between the knobs and what they are used for specifically...


I'm not sure what "Knob 1, etc." would help, since it's ridiculously apparent. Every single page has three values, left to right. There are three knobs. If someone can't figure that out, well...

As far as coloring the I/O goes, yes, the inputs have rings around them (as does every fourth step in the sequencer buttons.) I did it in a halftone, rather than black, and honestly, it didn't come out as dark as I'd like. It's pretty obvious in real life; it just doesn't photograph well. (It is ludicrously hard to take a good photo of a reflective surface.)
windspirit
Especially a reflective surface with a bunch of light sources coming out of it!
thetwlo
Crandall1 wrote:
It is ludicrously hard to take a good photo of a reflective surface.)


a good scanner is usually better for this, although, newer ones have very limited DOF.
Kummer
Crandall1 wrote:
Kummer wrote:
Don't mean to criticize, but there are two things I would change. 1st there doesn't seem to be a clear distinction between outputs and inputs. A black box or ring around the outs or ins would help people differentiate between the two. 2nd something should be written above the 3 multi function knobs. Even if it's just "multipurpose knob 1", "knob 2", etc.. Or something to that effect. It seems to bare in the upper right and no connection between the knobs and what they are used for specifically...


I'm not sure what "Knob 1, etc." would help, since it's ridiculously apparent. Every single page has three values, left to right. There are three knobs. If someone can't figure that out, well...

As far as coloring the I/O goes, yes, the inputs have rings around them (as does every fourth step in the sequencer buttons.) I did it in a halftone, rather than black, and honestly, it didn't come out as dark as I'd like. It's pretty obvious in real life; it just doesn't photograph well. (It is ludicrously hard to take a good photo of a reflective surface.)


True. I just think it might look a little nicer is all I was trying to say. But it is what it is and I still will eventually buy one.
studionebula
thetwlo wrote:
Crandall1 wrote:
It is ludicrously hard to take a good photo of a reflective surface.)


a good scanner is usually better for this, although, newer ones have very limited DOF.


I'm trying to imagine balancing my Eurorack cabinet face down on a flatbed scanner... hmmm.....
dmod
Any timeframe updates? hyper
Crandall1
Time for a bi-weekly update. We got the first shipment of Sequencer 1 retail units in the office today. They look fantastic and everything is in order. We have to go through and program and test each one; for that, I am waiting on a final software update with a couple of minor fixes from Adam to bump the software from RC3 (v0.9.x) to the shipping version (v1.0.0)

EDIT minor change of plans. News shortly. /EDIT

We've also codified the roadmap for feature updates; there are some truly spectacular things in store for this unit. At shipping with the v1.0.0 software it will be, by a country mile, the most sophisticated Euro sequencer available, and some of the things we have in store for it will make it essentially untouchable. There is a long roadmap of feature additions ahead to look forward to; we future-proofed this unit to within an inch of its life, and are extremely pleased with the result.

So, long story short, warm up your credit cards. Shit just got real.
dmod
Crandall1 wrote:
So, long story short, warm up your credit cards. Shit just got real.
w00t Paypal locked and loaded! Bananallama!
studionebula
Funky40 wrote:
just wateched the video: Great !

Q: is there a visual feedback while the sequenze is running which note is set at each step ?

the thought that immediately came to mind is:
it would be cool if the little keyboard would "highlite" the programmed Note, according to each step, while the sequence is playing .
not shure if that would be doable or "disturb" the programming ?


Thanks for the suggestions. This is a feature I thought of awhile ago and agree that it would be cool. However, I had to postpone it until an update because it was important to "freeze" the code so that we could make sure that it's ready to go without continuing to fiddle with it until the last moment. It is indeed doable but there is indeed a potential to disturb things. So, it won't be a feature of the initial release but it will very likely be added in the first update.
SunSpots
'Jackson 5'
I'll be there... I'll be there...
spin
twirl
yeah baby
I'll be there... The Chewbacca Defense
Crandall1
Sequencer 1 now available for direct purchase, shipping Friday. Free shipping worldwide. Come and get it!

http://www.audiodamage.com/hardware/product.php?pid=ADM06
SunSpots
done... cannot wait. so hot. future updates are just ice, pure ice baby
spritepixie
SunSpots wrote:
done... cannot wait. so hot. future updates are just ice, pure ice baby


"pfftt"

https://vine.co/v/MuhebjA2Z2D
jsousa
my first euro module; ordered it.

rabbit hole here i come...
Crandall1
Oh, boy. Busting your Euro cherry with this is like... I don't know... :-)
ignatius
congrats to CR and Adam!

looks really great! pretty awesome you have the future proofing on your side.

this module is sure to have a long exciting life.

It's motherfucking bacon yo nanners It's motherfucking bacon yo nanners applause applause
burnn_out!
Yeah this might be replacing my Rene. ..
jsousa
Crandall1 wrote:
Oh, boy. Busting your Euro cherry with this is like... I don't know... :-)


Figured id start with some power and future proofing
DSC
Order placed!
VanEck
Order number AD1117519771

Stoked!
Kummer
I'm hoping these sell out and it's successful so you can quickly move on to what's next. An Axon mode in Seq 1 or a full on Axon drum module would be amazing! Im poor at the moment but will eventually get one of these badboys myself.
kuxaan-sum
It's peanut butter jelly time! It's motherfucking bacon yo w00t Rockin' Banana! nanners
cbeefheartuk
Has it sold out already ? - can't add it to cart.
Crandall1
There seems to be a little hiccup with the store. If you're having problems adding to cart, write me at info at audiodamage dot com and we can do the order manually. We currently (as of 7:30AM PST on Thursday) have 10 units left from this initial batch, so if you want one of the first round, get on it.
Crandall1
Another update: almost all the orders that came in last night are shipped; most of the US people will have them on Saturday, with Europeans getting them (I imagine) Tuesday or so, if you ordered yesterday. All the remainder will ship tomorrow morning, for Monday/Wednesday arrival.

There are 3 units left in the initial "soft open." After they're gone, direct sales will be out of product for a while as we work to stock the retailers.
Slomen
hyper should be just two or less left now!
kuxaan-sum
Crandall1 wrote:
Another update: almost all the orders that came in last night are shipped


applause w00t screaming goo yo SlayerBadger! Rockin' Banana! nanners

...wait. I already said that didn't I?
lol
Crandall1
Slomen wrote:
hyper should be just two or less left now!


Yup. Two left right now.
gonkulator
one fewer
SunSpots
so happy to have this on Sat. looking forward to it. Still gotta figure out what leaves the system for it though...
dmod
SunSpots wrote:
so happy to have this on Sat. looking forward to it. Still gotta figure out what leaves the system for it though...
What you taking bout' willis? The obvious answer is get a new case hihi
flo
SlayerBadger! nanners It's peanut butter jelly time! I'm in!
Crandall1
All the Sequencer 1 units set aside for the soft launch are sold out. We'll be shipping to retailers soon. 'Til then, you'll have to live vicariously through the lucky few that got one of this first batch.

I'll be doing some real tutorial videos this weekend (as opposed to what I've put up so far, which is largely me just dicking about with various features as we got them working.)
flo
Guess I snapped the last one of them applause
Crandall1
flo wrote:
Guess I snapped the last one of them applause


Sure did. It's funny, because that last one sat there for like 4 hours, all by its lonesome. Then you bought it and about 5 minutes later people started writing me asking when more were coming because they missed it.

Anyhow, for those of you that did get one, if you didn't receive a tracking email from the USPS today, then your order is shipping Friday and you'll get tracking info then.
cbeefheartuk
I won too!
well.. my bank account lost - hope it's not too cold this winter.
flo
Crandall1 wrote:
flo wrote:
Guess I snapped the last one of them applause


Sure did. It's funny, because that last one sat there for like 4 hours, all by its lonesome. Then you bought it and about 5 minutes later people started writing me asking when more were coming because they missed it.


Yeah I couldn't let the poor module sit there all lonely hihi First thing I did this morning in the office. Maybe all Europeans that were writing you?

Anyways looking very much forward to this beautiful sequencer! SlayerBadger!
sonicmayhem
Oh darn it. I didnt know it was a soft launch. Already promised Shawn i buy it from his shop. Hope the retail units wont take too long! wink
hamildad
you know those modules that where you first hear about, the first thing you do is go onto Modular Grid and start "well, I if sell those, and swap that one there....."

This is one of those modules...

applause
cbeefheartuk
Get that manual online!
Crandall1
Manual will be done today. It's a lot of writing, and we were busy trying to finish the thing for the last few weeks. :-)

Right now I'm trying to make the text on the website less pompous and hyperbolic, because people elsewhere on the internet (*cough* Synthtopia *cough*) that don't know how I am think it's asshole-ish. Which is probably right, when I think about it, although not in the way they think. After that, I'm going to box up the remaining soft-launch units and get them to the post office.

A few people wrote and asked about customs and shipping methods. All our products ship USPS unless you write me specifically and ask for a different method, or the order weighs enough to get it in to the area where UPS is less expensive to ship (which won't happen unless you basically order two of everything we sell.)

Regarding customs, let's just say that I've been running mail order businesses for almost 20 years now, and I know how to take care of things, and let's leave it at that. You won't get smacked. And every order that leaves here is insured and has a tracking number.
Crandall1
Double-posting like a n00b.
cbeefheartuk
I was joking about the manual as I imagine it was some serious work to get the sequencer ready to ship and I would much rather have that than the manual to read (I do like reading manuals though..)
I think it is great you are excited and confident with what you are selling - I can't wait to get it and if it goes through customs no trouble I will be pretty damn happy.
DSC
Crandall1 wrote:


Right now I'm trying to make the text on the website less pompous and hyperbolic, because people elsewhere on the internet (*cough* Synthtopia *cough*) that don't know how I am think it's asshole-ish. Which is probably right, when I think about it, although not in the way they think.


Don't change for those assholes. You've got part of your life and soul into this brotha, don't sweat the bullshit! "The nail that sticks out, always gets hammered down" (Japanese Idiom)
flo
I LOLed at those Synthopia comments. If you took them seriously, you'd need to do an iPad version too hihi lol
Crandall1
I "LOL" at almost all Synthtopia comments. That site breeds a special sort, for some reason I can't figure. It does me no favors to wake up and read it first thing in the morning, though.

Anyhow, all remaining orders boxed up and heading to the PO now. If you ordered in our "soft launch," you'll have your Sequencer 1 shortly. I note that Control is allowing pre-orders if you write them. Do with that what you will. The units for retail will be arriving starting Monday, and we'll be turning them around as fast as we can and getting them to their brick-and-mortar homes.
mr.freeman
Crandall1 wrote:
I "LOL" at almost all Synthtopia comments. That site breeds a special sort, for some reason I can't figure. It does me no favors to wake up and read it first thing in the morning, though.

Anyhow, all remaining orders boxed up and heading to the PO now. If you ordered in our "soft launch," you'll have your Sequencer 1 shortly. I note that Control is allowing pre-orders if you write them. Do with that what you will. The units for retail will be arriving starting Monday, and we'll be turning them around as fast as we can and getting them to their brick-and-mortar homes.


any news on EU price/availability?
Crandall1
The pricing is up to them. We have a US$ MSRP that we figure margins against, but we don't force them to adhere to any particular pricing structure. For individual retailers in Europe (most of whom get their product from Alex4), it really depends on shipping costs, tariffs, what sort of profit margin their customers can stomach, that sort of thing.

Long story short, no idea on the pricing. As far as availability, we're getting the units from the manufacturer in 30-module drops every few days. Two dealers in particular order more than that, and two others order about that many. So we're kind of in a first come, first served scenario right now.

So to answer the other half of your question, no idea. Weeks, not months. But how many weeks? Hard to say at this point.
studionebula
cbeefheartuk wrote:
I was joking about the manual as I imagine it was some serious work to get the sequencer ready to ship and I would much rather have that than the manual to read (I do like reading manuals though..)
I think it is great you are excited and confident with what you are selling - I can't wait to get it and if it goes through customs no trouble I will be pretty damn happy.

I'm pounding away on the manual, I promise. I got derailed by some administrivia this morning but I'm still on track to produce a document today which will at least be enough for the early adopters to learn how to use the thing.

I like reading manuals also. I always have, I don't know why. I even made my living by writing them for awhile, and earned a little trophy from the Society of Technical Communications for my efforts. (I keep it around as a reminder that being good at something isn't reason enough to do it full-time professionally.) I almost always read the manual for a piece of gear before I decide to buy it, so I'm in complete agreement with those of you who are anxiously awaiting such a document.
euromorcego
Quote:
any news on EU price/availability?

Schneidersladen has it listed for quite a while now: http://www.schneidersladen.de/en/audio-damage-sequencer-1.html

699EUR, almost 900$ ...
Crandall1
Youch. A robust dollar and that VAT kills you guys. (Also, it is more expensive to ship things to Germany from the US than virtually anywhere else on the planet. I could ship the same weight box to some uninhabited island off the coast of Antarctica for cheaper.) Whelp, it is what it is.

The only way around it would be to have a separate batch made in the Czech Republic or something just for Europeans, but that's not really doable at these volumes. Also, a logistical nightmare.
mr.freeman
Crandall1 wrote:
The pricing is up to them. We have a US$ MSRP that we figure margins against, but we don't force them to adhere to any particular pricing structure. For individual retailers in Europe (most of whom get their product from Alex4), it really depends on shipping costs, tariffs, what sort of profit margin their customers can stomach, that sort of thing.

Long story short, no idea on the pricing. As far as availability, we're getting the units from the manufacturer in 30-module drops every few days. Two dealers in particular order more than that, and two others order about that many. So we're kind of in a first come, first served scenario right now.

So to answer the other half of your question, no idea. Weeks, not months. But how many weeks? Hard to say at this point.


thank you, I think I will drop 'em an email later and ask if they any idea thumbs up
Crandall1
We've put up the rough draft of the manual on the Sequencer 1 product page. Still a lot of cleaning and tuning, but it's pretty complete at this point.

http://www.audiodamage.com/hardware/product.php?pid=ADM06
dmod
Aaaahhh...Nothing like a hot ot cup of coffee and reading a manual. Its a good day. smokin'
conscious
euromorcego wrote:
Quote:
any news on EU price/availability?

Schneidersladen has it listed for quite a while now: http://www.schneidersladen.de/en/audio-damage-sequencer-1.html

699EUR, almost 900$ ...


ussualy the stuff in germany costs in .e what it costs in Dollar in the US, number wise.
So 400$ for a Rene will bei 400€ in europe.
exper
Taking into account that eurpean taxes are included in that price, whereas US prices do not. For instance, if I were to drive up to Control in NYC to purchase that module, it would cost me about $760. Of course, in the US we have lower taxes (and less benefits from taxes, but that is another thread) compared to europe...

So the prices over there, while they might initially seem unfair, are on the mark...
euromorcego
Quote:
So the prices over there, while they might initially seem unfair, are on the mark...

indeed. Basically for all modules it's a one-to-one conversion in numbers. If a module is $179 at Analogue haven (like some Audio Damage ones), then it is 179EUR at Schneidersladen. The sequencer 1 is $699, so it's 699EUR in Schneidersladen (and most other european retailers).

Actually, when you order from US to Europe, because a module is not available in Europe, it usually also amounts to the same (shipping plus import taxes add up to a 1-to-1 conversion of $ into EUR).

Still, 700Eur is still almost $900, which is a lot of money ... (but, to be fair, DPO costs almost the same).
dmod
Read the manual. Well done. Sure a complex sequencer but laid out in a user friendly fasion. Everything made sense to me. Cant wait to get mine thumbs up
dmod
euromorcego wrote:
Still, 700Eur is still almost $900, which is a lot of money ... (but, to be fair, DPO costs almost the same).
Try finding something you like but it is ony available in the UK. $700 turns into like $1200! woah Just saying.
Crandall1
I see that quite a few were delivered today. I keep checking back hoping someone posts a video or something.
studionebula
dmod wrote:
Read the manual. Well done. Sure a complex sequencer but laid out in a user friendly fasion. Everything made sense to me. Cant wait to get mine thumbs up


I'm very happy to hear that impression. Thanks, and thanks for posting it.
DSC
Received mine today. Immediately connected it to my XOXheart.
Lovin' my euro303! love
cbeefheartuk
Thanks - I read the manual too so looking forward to getting this even more now.. just got a Pro 2 and the sequencer is a bit too straight for my taste so this should spice things up a bit.

Give us a mini review DSC if you get chance!
VanEck
recorded two videos today before going to work. the first one linked below isn't too interesting, but demonstrates the versatile ability of the seq 1 to sequence and modulate multiple sources simultaneously. all gate triggering and modulation from the seq 1 with the time synch lfo's routed to its ratcheting and repeat functions and mult'd to other modules. accent used as a second gate trigger. braids and equation composer as sound sources. piston honda mkII for modulated waveshaping. mmf-6 for filtering. halls of valhalla cart for side chained reverb, modulated by the a-119. audio damage grainshift for granular processing.

VanEck
video #2, a more interesting and musical patch this time.



day 1 jam with the audio damage sequencer 1. pitch out to braids, processed by halls of valhalla cart. gate out to dual adsr for vca and ripples filter envelopes. accent out to equation composer for percussion, processed by grainshift and erbe verb. all modulation and gate triggers are from the seq 1 internal lfo's, routed back into itself to cv input parameters and mult'd to other modules in the patch via stackables.
Crandall1
Please note: one of our users has found a small bug: if you double-press the pattern clear (ALT-MEASURE) the unit will lock up. Power cycling it unlocks it, it seems, but just be aware of this until we have a hot-fix, which will hopefully be tomorrow morning. Until then, try to just press CLEAR once, instead of double-tapping it.

-CR
VanEck
Crandall1 wrote:
Please note: one of our users has found a small bug: if you double-press the pattern clear (ALT-MEASURE) the unit will lock up. Power cycling it unlocks it, it seems, but just be aware of this until we have a hot-fix, which will hopefully be tomorrow morning. Until then, try to just press CLEAR once, instead of double-tapping it.

-CR


Ran into this already myself. Had to power cycle. Also had my pattern clear on its own after running for a couple of hours... not sure what caused that one. I left the modular going for a while after recording that demo only to come back to it and found the pattern back to the default settings, all steps and parameter settings cleared.
Crandall1
Grrr. Well, there's only so much we can test. Luckily, it's really easy to update the firmware; we'll have a hotfix ASAP. (Adam is working on it now.)

I'll make a video tomorrow of how to do firmware updates. I had planned to do this when we rolled the first update out, but it looks like it needs to be sooner. :-)
kuxaan-sum
VanEck wrote:
Also had my pattern clear on its own after running for a couple of hours... not sure what caused that one. I left the modular going for a while after recording that demo only to come back to it and found the pattern back to the default settings, all steps and parameter settings cleared.


I had this happen to me in some manner.
I saved some settings and then modified some others (most notably tempo)
Walked away for about 30 minutes and I noticed tempo was back to 120 but I think it kept some step settings that were not previously saved.
kuxaan-sum
I should add that this is a very fun module.
I found it pretty intuitive and had a sequence going in less than a few minutes. I am not sure I understand what the cv outputs are doing but I haven't really read the manual. d'oh!

Was working yesterday and only got a few hours to play with it today but I hope to dig into it more this week. nanners
Crandall1
Okay. We'll figure that out. I've left two of them running (in sync, natch) for 4 days solid, without any trouble. If we can figure out a way to get this forgetting "feature" to be repeatable, that would be extremely helpful in solving it.
rollmottle
SEQ1 has quickly become the core of my system. Super intuitive interface. Packed to the gills with features. I'm lovin it. Few vids of my first minutes futzing around with it on my insta: http://instagram.com/rollmottle

Clap
stromcat
VanEck wrote:
video #2, a more interesting and musical patch this time.





Cool - would like to see more musical demos like this please!!
studionebula
Bugs that happen rarely, after a long period of time, are such fun to fix. sad

For those of you who have experienced problems, there are a couple of bits of info which might be helpful: 1) were you using external clocking? 2) were you using the CV ins for something, and if so, what?

Just trying to narrow the search. Thanks, and thanks for your forbearance.
VanEck
studionebula wrote:
Bugs that happen rarely, after a long period of time, are such fun to fix. sad

For those of you who have experienced problems, there are a couple of bits of info which might be helpful: 1) were you using external clocking? 2) were you using the CV ins for something, and if so, what?

Just trying to narrow the search. Thanks, and thanks for your forbearance.


In my case, I was using internal clock and had CV outs 1 and 2 routed to CV in 1 and 2, modulating the ratchet and repeat functions if I recall. The pattern never stopped playing, but everything in the pattern was just gone as if I had hit the clear button.
kuxaan-sum
Hmmm...I still have it patched.
I can check when I get home.

I was using internal clock and not using clock/reset/run inputs.
Was using all 3 CV outs to various filters, fx and envelopes in Linear CV mode.
I was using both CV inputs on transposition and step mode.

Using pitch, gate and clock outputs. (no accent, reset or run)

I think I left it for about 30 min. (maybe more I was working in another room)
As mentioned it kept some settings but definitely things that weren't saved defaulted to "x"/

The pattern was playing continuously and I don't recall what of the note value stuff was missing or previously saved.

I plan on testing tonight.
studionebula
Thanks for the reports. We still haven't been able to reproduce a similar problem, but I have a theory to explore.

In brighter news, I've fixed the double-click-on-ALT-MEASURE bug.
kuxaan-sum
OK....I am open to theories.
I left it for nearly an hour while making/eating dinner and no repeat of the clearing/defaulting.

I thought maybe it had to do with the screen it was on as the patch is exactly the same except that I am on Bank A-02 (versus Bank A-01).

Before I may have had it on the Seq screen and I realized tonight it was on a modulation screen although I switched it after the hour had passed I was impatient and wanted to wiggle.

seriously, i just don't get it

I will keep an eye out as I play some more this week.
I was just having too much fun to walk away as I did before.
Rockin' Banana!
OK...off to upload the videos I took while playing around.
Crandall1
I've tried everything on two units simultaneously to get it to happen, and haven't been able to. If we aren't able to replicate it here by tomorrow morning, we're going to go ahead and push the update with the double-click fix, because we're going to be turning retail units starting tomorrow afternoon. So, a hot-fix for Tuesday, regardless, and I'll also run out a quick video of how to flash the firmware.

(It's super easy, fwiw.)

-CR
flo
Mine isn't even here and I already start to feature-creep after reading the manual... hihi An easy suggestion:

I think it would be cool if the three CV outs could be switched to quantized / keys as well. The different modes (linear, LFO, etc.) are already there so I guess it should be easy to add "key" or something. That way it would be very easy to get a second voice going with the accent out and one of the CV outs. It's possible already with volts displayed in two decimal places, but quantization would certainly make it easier...
Crandall1
We're definitely adding that feature. It is on the Big List Of Updates. It just didn't make it in to the v1 release, which was necessarily time-constrained. Adam has been working on this code 7 days a week for months, and needed a little reset.

As soon as we have the initial round of retail units out the door, and make sure there are no mission-critical bugs remaining, we'll get back to adding things, and that's definitely absolutely something that will be added.
flo
SlayerBadger! Hell yeah!
Daisuk
Is there any way you could make the sequencer go beyond 64 steps (on a specific pattern), AND be able to set loop points somehow, say set the sequencer to loop from step 17 to 32? Those are two things that's annoyed me a bit with the Elektron sequencers.

But I have to say, this thing looks amazing. I have a Rene and a Metropolis already, but damn, I can't see myself resisting this for too long!
Crandall1
Not currently, no. I'll add that ask to the pile, though.
rollmottle
Here's another one for the pile:

Would like to be to shift around a pattern within a sequence. Sometimes you get in a groove without setting up a proper reset and your 1 gets all fucked up. So you have to shift all the steps around once you've started and stopped again. Plus, it would be just a cool feature for messing with a pattern regardless if you get your shit in order before you start patching.

we're not worthy
studionebula
Daisuk wrote:
Is there any way you could make the sequencer go beyond 64 steps (on a specific pattern), AND be able to set loop points somehow, say set the sequencer to loop from step 17 to 32? Those are two things that's annoyed me a bit with the Elektron sequencers.

Going beyond 64 steps would have to involve shortening other patterns. In other words, it's doable but somewhat complicated.

Loop points are somewhat less complicated, and are something which I considered at some point. I agree that it would be nifty to be able to modulate the loop position with a CV, for example.

So, as Chris said, we'll put 'em on the pile. After folks have been able to use the things for awhile and provide feedback we'll have a better sense of how to start prioritizing all of the stuff in that pile.
Crandall1
Okay. Version 1.0.1 of the firmware is now available for download on the Sequencer 1 product page on the AD site.

Here's a short and somewhat silly video demonstrating the process:

studionebula
rollmottle wrote:
Here's another one for the pile:

Would like to be to shift around a pattern within a sequence. Sometimes you get in a groove without setting up a proper reset and your 1 gets all fucked up. [...]

we're not worthy

I guarantee that that feature will get added sooner or later because I desperately want it myself. Regardless of the system, I seem to always end up with my 1 in the wrong place when I'm making patterns/grooves/loops/etc.
rollmottle
studionebula wrote:
rollmottle wrote:
Here's another one for the pile:

Would like to be to shift around a pattern within a sequence. Sometimes you get in a groove without setting up a proper reset and your 1 gets all fucked up. [...]

we're not worthy

I guarantee that that feature will get added sooner or later because I desperately want it myself. Regardless of the system, I seem to always end up with my 1 in the wrong place when I'm making patterns/grooves/loops/etc.


Radical. thumbs up
djempirical
Crandall1 wrote:
Here's a short and somewhat silly video demonstrating the process


Only 3 twss's. Not bad.
VanEck
Just had my pattern wipe out again. Wasn't even touching the module. Programming a patch, had a good sequence going on and was messing with it for about an hour. Started tweaking my erbe verb then *poof*... pattern gone. Instead of playing the 8 steps that I had repeating, it was suddenly playing 16 steps with no data in the sequence anymore.

It also switched from external clock back to internal, and all the CV out and in configuration was reset.

This time I was using external clock. CV 1 out routed to CV 1 in - transpose, and CV 2 out routed to CV in 2 - repeat. waah
Crandall1
Our working theory right now is that your power supply sucks. Can you verify whether that is the case or not?

EDIT: Since my sense of humor isn't always apparent here, I was being funny. What I mean to say is that if your PSU is right on the edge, and the power is dipping, it may cause a reboot. If the pattern wasn't saved, when it reboots it has nothing to load, hence blank.
Daisuk
studionebula wrote:
Daisuk wrote:
Is there any way you could make the sequencer go beyond 64 steps (on a specific pattern), AND be able to set loop points somehow, say set the sequencer to loop from step 17 to 32? Those are two things that's annoyed me a bit with the Elektron sequencers.

Going beyond 64 steps would have to involve shortening other patterns. In other words, it's doable but somewhat complicated.

Loop points are somewhat less complicated, and are something which I considered at some point. I agree that it would be nifty to be able to modulate the loop position with a CV, for example.

So, as Chris said, we'll put 'em on the pile. After folks have been able to use the things for awhile and provide feedback we'll have a better sense of how to start prioritizing all of the stuff in that pile.


Cool. Hate to sound like a demanding little dick though, since this thing already looks packed with incredibly useful features, and I'll probably get one sooner rather than later anyhow! thumbs up
VanEck
Crandall1 wrote:
Our working theory right now is that your power supply sucks. Can you verify whether that is the case or not?


That's a good theory, but doesn't measure up when I crunch the numbers (unless my math is wrong which is entirely possible). This case is a Doepfer P9, purchased new straight from Doepfer about 6 months ago and features their latest and greatest PSU.

According to Modular Planner, my power consumption is as follows:

Power Consumption: 838 mA +12V | 203 mA -12V | 236 mA 5V

None of my other modules (almost all digital) are showing any signs of power fluctuation or strain or losing their settings, such as my two Braids osc's. My cases are all plugged into a battery powered uninterruptible power supply to condition the current and protect from surges, brownouts, and power loss. seriously, i just don't get it
Crandall1
Okay. Let's rule that out, then. I too have a loaded P9 and have never experienced this issue. Back to the drawing board.
studionebula
Thanks for the detailed info on your power supply; it's a big help to know that we can rule that out at least for now. I'd much rather blame this problem on software, which can be fixed--even though we're currently quite stumped.

Since we still haven't been able to reproduce it even once (my unit has been running with two LFOs driving its CV inputs for about 30 hours now), here's a question for you: what was on the LCD before the pattern vanished, and what was on it afterwards?
Crandall1
Just a quick update: we found the source of the pattern blanking bug. Just waiting for a build from Adam to test, and I'll put it up for download.

Side note: I have a big pile of Sequencer 1 units just sitting here in my living room; they were going to go ship today to Control, but we held them for the new firmware. So they're going to Control tomorrow, with the latest OS installed.
Crandall1
Okay. The fix is in. Firmware revision 1.0.2 is now available for download on the AD site.

The "pattern clear" bug has been found and destroyed with extreme prejudice, and this will no longer be a problem. One other bug (tempo not saved) was fixed, as well. All retail units shipping from here on out (which is all retail units, because none have shipped yet) will have at least v1.0.2, and we strongly recommend updating to this version if you already have a Sequencer 1.
sonicmayhem
Hey Chris

What about Analogue haven? Are you shipping to them soon as well?
psyclone001
Just ordered 1 can't wait.
Audio damage kick ass. Have had all their plugins for years and they are amazing and this sequencer seems no different.
Awesome customer service it seems also with fast addressing of bugs etc..
Rock on Audio damage dudes SlayerBadger!
cbeefheartuk
Hi - has anyone in the UK that ordered from that first batch got it yet?
My last tracking info says - international dispatch ready 12/10/14.

Something strange happened with my Paypal account when I ordered it and mine is being shipped to an old address.
kuxaan-sum
Updated mine this AM...was easy as π
"that's what she said..."
hihi


Seriously...thanks for making it so damn simple.
It's motherfucking bacon yo
granville
cbeefheartuk wrote:
Hi - has anyone in the UK that ordered from that first batch got it yet?
My last tracking info says - international dispatch ready 12/10/14.

Something strange happened with my Paypal account when I ordered it and mine is being shipped to an old address.


I'm in the same boat, although mine's only said that since October 15th. In my experience stuff from the US takes about 2 weeks to turn up, and arrival is usually preceded by a long period of tracking radio silence. I wouldn't worry about it yet. Guinness ftw!
Crandall1
The Analogue Haven order is going out shortly. Shawn wanted a larger quantity than we were initially able to provide (we're just getting them a few units at a time).
paults
Curious how the firmware is loaded in (not in manual?).
Crandall1
Via the SD card. On boot, it checks the card to see if there's new firmware, and if there is, it loads it. (To reduce what we're actually doing to such a pithy statement will no doubt give Adam the cold sweats, but that's the gist of it.)

Regarding the overseas orders, I know of at least two (both in France) that received their units today. The USPS tracking stops at the border, so it'll look like it's sitting in Los Angeles until it shows up at your door. Don't sweat that.
paults
Sorry, unaware there was SD card lurking under the hood! Cool!
Patate le mage
Receive mine today in France,

What a nice thing it is !!!
The update was a piece of cake : took me 3 minutes.

Very well thought for live performance.

Now i have four big sequencers :

The René : the punk one very nice for exploration , experimentation and unexpected paths.

The Metropolis : the obvious one in Berlin style, the only default : it's not easy to select a note with the sliders in live performance, the mini keyboard on the seq1 is a big +.

The ER-101 : For the music composer, it does all you want but you have to work hard.

The Sequencer 1 : For live composition and live performance applause
cbeefheartuk
Cheers.
I'm only concerned about roughly when it arrives as I have to try to get it from a flat I don't live at anymore so if you could post when yours arrives Granville it would be much appreciated.
psyclone001
Just a question regarding programming.
I have a Nord G2 modular that has great sequencing modules.
One of my easiest ways for generating new melodies is to hit the randomise button to greate random values of all steps, and used with quantising is an endless source of new fantastic melodies. I find this method an incredibly easy way to generate interesting sequences.
I haven't studied all the features of the new AD Seq1 but am hoping that the module may have some sort of randomiser built in, or if not maybe an option in a software upgrade down the track. love
Also expanding on that thought is there onboard quantisation proposed for the unit, and Is there an option in the menu to change the root key of the sequence you have programmed, similar to the metropolis?
Sorry for all the questions but it seems like the ultimate sequencer to potentially rule them all thumbs up
studionebula
I'm very glad to hear that firmware updates are going smoothly. Thank you for your patience with us; that "pattern wipe" bug was a tricky one to track down. I am happy to say, though, that once its origin was found it was easy to correct, so we are quite confident that the problem has been eliminated for good.

A new revision of the manual will appear very soon (as in tonight or Saturday). I still won't call it finished, but I believe that it now covers every feature of the sequencer. It also has pretty pictures of the LFO shapes. w00t

Thank you also for your enthusiasm and your kind words. It's very much appreciated after the end of a long project--or at least the end of this phase of the project.
Crandall1
New manual revision on the AD site. As Adam said, still not finished, but more finished than not now.

@psyclone001: we have quite a few more features to add, and several of them directly address your comments. We're loath to speak about them until we've implemented them and verify they increase the usability of the unit, without making it less immediate.

But yeah, the entire point of this exercise is to make a Euro sequencer that will cover virtually all the bases. That is our intent, and the future additions to the platform will further that goal.
flo
Mine arrived today It's peanut butter jelly time! Beautiful module. But I won't find the time to install it until tomorrow waah
flo
Ah what the heck, I installed it anyways. Guinness ftw!

Looking good:



Updating was a breeze. Luckily my card-reader has a micro-sd slot.

Operating the basics is very easy as well. This thing is FUN! Hell yeah! SlayerBadger!

Not sure whether this is intentional or not: when holding repeat, then additionally ratchet (while still holding repeat), releasing ratcheting but still holding repeat will not result in further repeats, but the seq will exit the repeat mode completely... I'd prefer if it stayed in there. Just a thought thumbs up

Thanks for this amazing product! It's motherfucking bacon yo
studionebula
flo wrote:

Not sure whether this is intentional or not: when holding repeat, then additionally ratchet (while still holding repeat), releasing ratcheting but still holding repeat will not result in further repeats, but the seq will exit the repeat mode completely... I'd prefer if it stayed in there. Just a thought thumbs up


Arg. very frustrating

I agree that it should work the way you describe. Good catch.

flo wrote:
Thanks for this amazing product! It's motherfucking bacon yo


Thanks for the kind words, and the business!
Crandall1
Just a little update: the retail build is proceeding at a punk-rock clip. It'll be a couple weeks before all the current orders are filled. But Control's ready to rock, and AH will be in a bit. Going to be about 2 weeks before units propagate to the European retail shops, though.
dinesh23
6 business days ... and it has arrived It's motherfucking bacon yo

OS is updated (drag and drop a file!)
I have my screw driver in hand - I probably won't be seen again for some time!?

Doctorin' the Tardis
Patate le mage
After 3 days, and nights, with this sequencer :

First of all : it's incredibly well design : a pleasure to make live music with it.

what are the stengths of this beast :

- All the parameters you really need are immediatly under your fingers in live : gate, note, accent, ratchet, slide etc....

- The LFOs wich are synchronized and can be phased out as you want. ( First time i can do that with my modular system ) Have a look at the manual, section LFO, it opens mind.

- Let's do maths : 10 BPM minimum : its 40 quarters note per minute : one quarter note every 1.5 sec. If your LFO is set to length 256 : the cycle will take :256*1.5=384 sec wich is 6 min 24 s, and all that perfectly in tempo.
And you have three of them : and they are totally smooth, and you can dephase them and so on.....
You can make a drone quasi infinite and totally reproductible.
Oh, i love this thing applause applause applause
granville
Mine arrived this morning (NB @cbeefheartuk, keep an eye out). Bit of extra to pay to Her Majesty but could've been worse.

So far, s'all good, syncs nicely, UX is clear & straight forward but simultaneously allows for a real depth of control. GOOD WORK! screaming goo yo
cbeefheartuk
thanks Granville.
I will go to my old flat tonight and see if I can get my sequencer or a least a not delivered card.
Patate le mage
A drone make with the 3 LFO's of Seq 1.

Automatic Saw

Sequencer1 is the best friend of reproductible Drone.
Bogus
Has anyone patched this with a chord machine?
wxyz
Loving this so far. Great for sax like lines. Does anyone have a step by step for creating the racheting? Does one just push the rachet button when it is in step mode?
zam
Anyone have this and Metropolis? Just wondering how they compare
gonkulator
zam wrote:
Anyone have this and Metropolis? Just wondering how they compare


Yes, and they are quite distinct from each other. The Metropolis is really what you would expect in a modular device: hands on, immediate, easy to edit while playing. Contasted to the Seq 1, it is limited on steps, lacking any internal mod, limited outs. The Seq 1 is more of an independent module. I think it is more redily compared to the Electribe or the Elektron sequencers. It has many more steps, and a lot of internal mod capability. However, it is a lot more tedious to work with, and it is easy to make mistakes pushing the buttons while navigating. More useful in creating longer, more complex sequences and songs (you can play patterns in sequence )but not so much as an instrument to play on the fly. My 2 cents.
zam
Cheers gonkulator
granville
I've got both, and both are great in different ways.

Metropolis: very immediate, inbuilt quantizer makes it really good with melodic stuff, modulating root note & step in particular. The 2 auxes open up loads of possibilities. You can jiggle the sliders and switches around until you find something that works. Which is kind of the opposite to...

Sequencer 1: which is deeper, more 'programmy', the ability to save is definitely a useful thing. It's got loads more outs (cv x4, gate x2) so you can do much more complicated sequencing. 3 x internal lfo's open it up even more, lfo's can run super slow or be triggered per step which gives you a palette of different envelopes to muck about with. The other plus with this one is that extra features are planned and upgrading the OS is easy peasy.
Crandall1
wxyz wrote:
Does anyone have a step by step for creating the racheting? Does one just push the rachet button when it is in step mode?


Yes, when you're in step mode, you just set the ratchets like you set the accents or slides.

Note that you need a pretty quick envelope to even hear them. If the envelope hasn't decayed a bit before the second (and third and fourth) ratchets have happened, then you won't even know they occurred. Quick-ish decay and a maximum 50% sustain are the keys to successful ratcheting, on this and all sequencers. The best results are on percussive hits that mostly decay quicker than 32nd notes (which is the lowest ratchet; the "4" ratchet is 64th notes.)

Side note: I have 5 Sequencer 1 units here that aren't slated for retail distro; I have added them to the store. So if you're European, you might want to jump on one of these, as I still haven't sent the Alex4 order, and thus it will be some weeks before the European retailers have units. (This is due to a paperwork snafu; the units are in our office, ready to ship.)

Further side note: Control and Analogue Haven are fully stocked for immediate shipping on Sequencer 1, and Muff's will be later this week.
Crandall1
I guess I should add to the ratchet bit above. There are two other ways to make ratchets occur: either via the front panel controls when the unit is not in a programming mode (step buttons 15 and 16), or via CV input. So three ways in all. But in all of them, you need to have an envelope setting that is capable of ratcheting at all.
mwvm
I really like the x-cv feature with rene. Can you do similar stuff with this?

How does this compare with er-101?
knobbyfischer
Saving up for this!
Slomen
Trying to use the Sequencer-1 with Pamela´s Workout but I seem to be doing something wrong. Is anybody using these two together?

If I send "clock" and "run" out to Pamela, then Pamela thinks the tempo is 25 bpm even though seq-1 has tempo of 110.. I have also tried sending clock from Pamela to Sequencer-1 and a steady pulse (--) from Pamela to Seq-1´s "run". (Also tried splitting that signal and send it to both "run" and "reset") but they do not sync properly. I have changed clock to internal and external when appropriate.

Can anyone help me with this? Sorry for the possible noobness

(on a sidenote I decided to finally try that scary Pamela firmware update.. aaand oh man oh man it is hell! Really love the easy firmware update of seq-1!)
qu.one
i dont have either, but it sounds like Pam is not set to the correct ppq


Slomen wrote:
Trying to use the Sequencer-1 with Pamela´s Workout but I seem to be doing something wrong. Is anybody using these two together?

If I send "clock" and "run" out to Pamela, then Pamela thinks the tempo is 25 bpm even though seq-1 has tempo of 110.. I have also tried sending clock from Pamela to Sequencer-1 and a steady pulse (--) from Pamela to Seq-1´s "run". (Also tried splitting that signal and send it to both "run" and "reset") but they do not sync properly. I have changed clock to internal and external when appropriate.

Can anyone help me with this? Sorry for the possible noobness

(on a sidenote I decided to finally try that scary Pamela firmware update.. aaand oh man oh man it is hell! Really love the easy firmware update of seq-1!)
dmod
Yep! Look at Pam manual for how to change the ppq( how it reads clock timing).
Crandall1
Yes, Sequencer 1's clock I/O is (currently) 1 pulse per step, or 4PPQ. It sounds like Pam is set to 24PPQ (Roland DIN Sync rate) which would result in the division you are seeing.

Sequencer 1 will be getting a gearbox on both the in and out, and will speak 24PPQ and 48PPQ both in and out. It doesn't currently, though.
flo
BTW, is the "run" "din sync style", always high while running? Or "analog sequencer style", a trigger on start and another on stop? Guess I could check it on mine but I'm a bit lazy hihi Haven't tried syncing it yet. Anyways I assume the old trick of hitting "play" (without any input at "run") before a clock is sent would work either way...
Crandall1
Yes, the old trick works. RUN is high on running (Roland style). And it responds the same way. RST is pulse on start, pulse on stop, the "analog sequencer style" you refer to. So Sequencer 1 can deal with all comers.

There's some confusion in the terminology in Euro-land, so we just stuck to the Roland method for the most part, since that's the most common use case. Once the gearbox is in place, Sequencer 1 will sync to pretty much anything, and also sync pretty much anything; you'll just have to experiment with what PPQ setting and combo of RUN and RESET you need.

Nominally, to slave a Sequencer 1 to another Sequencer 1, you'd just jump all three jacks. When I slave Sequencer 1 to Silent Way Sync with an ES-4, I put clock to clock, with SW Sync set to 4 PPQ, and SW Sync's Run output to Sequencer 1's RST input. Put Sequencer 1 in play mode, and then it'll start and stop with the DAW no problem. You can then use Seq 1's CLOCK, RST, and RUN outputs to drive other stuff.
flo
Cheers mate! SlayerBadger! we're not worthy thumbs up
Slomen
Setting Pams ppq fixed it! Cheers guys! Guinness ftw!
psyclone001
I notice one of the modulation destinations is 'transposition'.
What is the easiest way / best signal / module to send to this input to accurately control the transposition in semitones?
I have just received my unit today, saved a few sequences written in the key of D# and want to now transpose the whole sequence down to key C. In other words change the root note of the sequence from D# to C (-3 semitones)?
As I mentioned earlier this would be a great setting in a menu to be able to transpose existing patterns from one root note to another. If I can't modulate the transposition easily enough I will have to copy and re-write the sequence in another key which is obviously a slow and tedious process.
Awesome module BTW thumbs up
SunSpots
Finally been able to crack open the manual and figure out the rest of the functions smile

Suggestions: (please correct me if these have changed in recent firmware)

1) let the "quick tap" select the step instead of muting it. I would rather "hold" to mute. If I'm performing, then I am moving fast and a quick tap is much easier to do to select and is standard? Seems like it's more intuitive. Like clicking a mouse button, or touching an ipad. quick tap is select usually...

2) implementing some kind of record function to record knob twists. that is quintessential elektron sequencing smile
flo
1) You can quickly double click it as well (muting / unmuting) to select the step... Maybe that's more convenient than holding?

2) I vote for a full on tap writing mode, all included hihi
SunSpots
Some more feedback...

Suggestion 1: Okay here's some more feedback. I would like some kind of ability to visually know which steps have the accent function, and which do not. As it is right now, adding accent is EASY. I was having a great time using the accent to trigger my drum module. I was thinking I will also use the occasional accent to gate my modcan dual delay on certain notes and see what fun can be had there smile

But I don't know where I put them. Where are my accents? So far as I know, I have to memorize where I put them, or watch the sequence and listen in order to remember. That's all fine, but I thought it might be easy enough to make the accented steps slowly fade/on/off, and the slide steps to blink? I dunno... any other idea would be nice to know what I left where... especially when coming back to a pattern after a few days or weeks. I won't remember anything after that time.

Suggestion 2: When I am in the mode that shows CV1,2, and 3 I can see the cv value I change. That's all fine and good, it works as expected. However when I switch to another step, it visually shows the value from the step I *last* edited. That is if I change step 1 to 500, the display shows 500 no matter what step I select until I turn the knob. Once I turn the knob it seems to reset to the steps value... that's okay I guess... not a huge deal but would be slicker and more easy to understand if the display changed when I clicked on the next step, to show that step's value and not the value from the last edited step.

.... also the ability to record knob twists would be bad ass.
Crandall1
Okay, that "suggestion 2" is a bug. Don't know how we missed that; I use the CV stuff a lot. Fix in the next build.

Regarding the other stuff, putting it on the Big List Of Suggestions that we shall conquer in time.
Bogus
SunSpots wrote:
1) let the "quick tap" select the step instead of muting it


+1 for this

I would also like to be able to see the Piano LEDs flash the notes of a sequence as it runs through the steps (perhaps it could default to this while in menus not correlating directly to step editing since the piano buttons don't get used otherwise). It would be cool to be able to visualize note progressions like that.
Crandall1
That feature is on the table now. We actually wanted to have that working before release, but it takes some finesse to have it happen without affecting timing, so we thought it'd be better to not have it, and have rock solid timing out of the chute, than to add it just for the light show and risk the timing.

But yeah, it'll be in there. Don't need to ask for it, as it is a definite addition that will happen sooner rather than later. We're just tidying up our next release, then Adam will turn back to S1 software.
Bogus
That's good to hear. I'm very much looking forward to these upcoming updates, it seems you guys have a lot of heavyweight additions in the works as you promised. Any mention yet of CV over pattern selection?
Crandall1
I don't understand. That feature's already in there...?
Bogus
d'oh! yeah I just found it during my latest patch! Sorry for that.
SunSpots
Crandall1 wrote:
That feature is on the table now. We actually wanted to have that working before release, but it takes some finesse to have it happen without affecting timing, so we thought it'd be better to not have it, and have rock solid timing out of the chute, than to add it just for the light show and risk the timing.

But yeah, it'll be in there. Don't need to ask for it, as it is a definite addition that will happen sooner rather than later. We're just tidying up our next release, then Adam will turn back to S1 software.


Ps... I really like this sequencer work flow, which is why I give the feedback. ... so yeah record knob twists..If it is possible... fuck yeH
psyclone001
psyclone001 wrote:
I notice one of the modulation destinations is 'transposition'.
What is the easiest way / best signal / module to send to this input to accurately control the transposition in semitones?
I have just received my unit today, saved a few sequences written in the key of D# and want to now transpose the whole sequence down to key C. In other words change the root note of the sequence from D# to C (-3 semitones)?
As I mentioned earlier this would be a great setting in a menu to be able to transpose existing patterns from one root note to another. If I can't modulate the transposition easily enough I will have to copy and re-write the sequence in another key which is obviously a slow and tedious process.
Awesome module BTW thumbs up


G'day Chris. Any ideas on the easiest way to transpose a whole sequence as I explained above? I have a quantizer but it is generally serving other purposes in my rig
Cheers
Crandall1
We'll be adding a keyboard transposition feature per pattern.

I know it seems like I'm saying a lot of "that feature is coming," but really, most of these things mentioned are part and parcel of the same basic single feature: utilizing the keyboard in a more fluid fashion, including control over the state and visual reflection of that state. It may sound odd and disparate, but you're all basically asking for the same thing. (At least as far as the code is concerned.) So most of them are definitely on the list for inclusion, sooner rather than later.
gonkulator
I really appreciate the openness to suggestion applause applause
Crandall1
Wait 'til you see what we're adding that you _haven't_ asked for. All that other stuff will seem mild. :-)
gonkulator
Guinness ftw!
psyclone001
Crandall1 wrote:
Wait 'til you see what we're adding that you _haven't_ asked for. All that other stuff will seem mild. :-)


Oh man that's cruel. TELL US NOW GOD DAMMIT angry
granville
As well as the keyboard lighting up per step when running would it be possible to have gate/accent/ratchet/slide do that too?
Crandall1
Yeah, that'll happen. (Again, all part of the same root feature.)
clusterchord
Crandall1 wrote:
Wait 'til you see what we're adding that you _haven't_ asked for. All that other stuff will seem mild. :-)


woo hooo.. the previously mentioned feature i'm looking forward to the most is microtonal quantizer..



PS do the units that just showed up at Muffwiggler store have all the upgrades, including the wider holes for those two buttons ?

i'm thinking of pulling the trigger soon..


thanks
Crandall1
The units that went to Rhythm Active (plus the one that went to the guy in England) were all part of the very first box. 100% of the mechanical bugs that have been mentioned were in that first box of 15. Everything since then has been perfect. This includes all the units shipped to AH, Control, Muff's, and yesterday's shipment to Alex4.

100% of the retail units shipped have software v1.0.2 currently, so you won't need to do an update until we rev the software. The units we sold direct on the first day (25 in all) shipped with v1.0.0, and those early adopters helped us track down the two bugs that resulted in the v1.0.2 software. Only those units shipped with anything but v1.0.2. Every direct unit I've sold since then ships with v1.0.2.

So, tl;dr: yes. The units at Muff's are the current latest in all respects.
Ras Thavas
gonkulator wrote:
I really appreciate the openness to suggestion applause applause


This. The enthusiasm, openness and general involvement with the MW community that Audio Damage has shown has been awesome. And of course, the sequencer looks pretty damn amazing too.

I plan to be buying one within the month, and am definitely waiting with anticipation to see what you have up your sleeve for the next O.S. update.
saldiamond
Sorry for cross posting but I thought you might see this here.

Will you have these available at the Western Electro Music Fest today?

Maybe you're already out there, with mine on display, waiting for me to come pick it up hihi
Bogus
Manual says:
Quote:
The Reset output emits a short +5V pulse when you press the Stop button.


I'd really like to be able to configure the reset output to pulse on the first step of a sequence in addition to when the stop button is pressed.
flo
Crandall1 wrote:
Wait 'til you see what we're adding that you _haven't_ asked for. All that other stuff will seem mild. :-)


SlayerBadger! hyper nanners applause
SunSpots
flo wrote:
Crandall1 wrote:
Wait 'til you see what we're adding that you _haven't_ asked for. All that other stuff will seem mild. :-)


SlayerBadger! hyper nanners applause


The Chewbacca Defense Dono-Kun Dance
Bogus
Can someone help me understand how to get the LFOs to output a signal? I thought I could access them by patching into the CV1-3 outputs but I'm not seeing any response from modules connected to these outs. The display on the sequencer reads 100% amplitude on all three LFOs.

Edit: Once again I have found the answer to my own question. In case anyone else is having troubles just hit Alt+Seq (07) and then click in any of the knobs.
studionebula
Bogus wrote:
Manual says:
Quote:
The Reset output emits a short +5V pulse when you press the Stop button.


I'd really like to be able to configure the reset output to pulse on the first step of a sequence in addition to when the stop button is pressed.


I was quite sure that our initial configuration for the transport jacks (which, as Chris mentioned, basically follows Roland conventions) would not satisfy everyone. If people have other requests similar to this one, please sing out so that I can start thinking about how to accommodate them. There's no need to mention clock divisors on the inputs and outputs (i.e. handling of 24/48ppq clocks)--that's always been on the list.
Bogus
After several patches and recordings I've noticed that the internal clock on my Sequencer 1 is a bit slow. I've run several tests at all BPMs and every single one turns up the same result.

All I'm doing is recording the square wave coming from the clock output directly into my DAW in the form of audio. When I set the DAW to the same tempo displayed on the Sequencer 1 I notice that the square wave slowly drifts out of phase with the DAW clock.
Crandall1
Bogus wrote:
After several patches and recordings I've noticed that the internal clock on my Sequencer 1 is a bit slow. I've run several tests at all BPMs and every single one turns up the same result.

All I'm doing is recording the square wave coming from the clock output directly into my DAW in the form of audio. When I set the DAW to the same tempo displayed on the Sequencer 1 I notice that the square wave slowly drifts out of phase with the DAW clock.


No offense, but this is something all electronic musicians discover eventually: there are not two pieces of gear made, ever, that will run in sync without some sort of mechanical intervention. That's why we put sync jacks on it. :-)

Or to put it another way: perhaps your DAW's tempo is a little fast.
wxyz
https://soundcloud.com/strangeattractor/deep-space-reggae
dmod
Crandall1 wrote:
Bogus wrote:
After several patches and recordings I've noticed that the internal clock on my Sequencer 1 is a bit slow. I've run several tests at all BPMs and every single one turns up the same result.

All I'm doing is recording the square wave coming from the clock output directly into my DAW in the form of audio. When I set the DAW to the same tempo displayed on the Sequencer 1 I notice that the square wave slowly drifts out of phase with the DAW clock.


No offense, but this is something all electronic musicians discover eventually: there are not two pieces of gear made, ever, that will run in sync without some sort of mechanical intervention. That's why we put sync jacks on it. :-)

Or to put it another way: perhaps your DAW's tempo is a little fast.
Agreed! I have spent the last 25 years syncing everything from CV, tape, din-sync and midi. I would bet my money its the DAW that is lacking as DAWs seem to be the sloppiest of them all but either way that is what clock pulses are for. Guinness ftw!
Bogus
Crandall1 wrote:
Bogus wrote:
After several patches and recordings I've noticed that the internal clock on my Sequencer 1 is a bit slow. I've run several tests at all BPMs and every single one turns up the same result.

All I'm doing is recording the square wave coming from the clock output directly into my DAW in the form of audio. When I set the DAW to the same tempo displayed on the Sequencer 1 I notice that the square wave slowly drifts out of phase with the DAW clock.


No offense, but this is something all electronic musicians discover eventually: there are not two pieces of gear made, ever, that will run in sync without some sort of mechanical intervention. That's why we put sync jacks on it. :-)

Or to put it another way: perhaps your DAW's tempo is a little fast.


Just ran home to test again, this time I put an analog clock and my cell phone's stopwatch in front of the Sequencer 1 and ran it at "Tempo: 60" starting on the tick of the clock. Same result is happening... by the end of the first minute the sequencer 1 is more than a full step behind.
flo
You simply cannot run tests like that. You need sync.
cbeefheartuk
What I would really love would be knob recording where you could change the length of the loop like the LFO's from one step to many steps after recording it.. if it could loop the recorded knob wiggle then have one button as a punch in to record extra stuff on top - a bit like the super synthesis ph01 - that would be incredible having a choice of the LFO's or knob recording for the 3 CV outs.
Slomen
When I send clock to Pamela (using 4 ppq on Pamela) I get a slower bpm reading on Pamela than what I´ve set on Sequencer-1. 70 on seq-1 is 69 on Pamela. 129 on se1-1 is 128 on Pamela. Is this something that will be better when seq-1 gets 24ppq? Or maybe Pamela is a bit off?
flo
Pamela's BPM indication is not accurate when slaved.

And Pam will definitely sync better with higher ppqn, but the BPM indication is just not 100% correct in slave mode AFAIK.
Slomen
Thanks Flo!
Bogus
flo wrote:
You simply cannot run tests like that. You need sync.


My reason for pointing these things out about the tempo is based on a note I read in the manual reguarding the swing feature:
Quote:
This parameter has no effect if Sequencer 1 is using an external clock source. Note, however, that Sequencer 1’s Clock output is affected by this parameter, so you can pass the ability to swing on to other modules.


I'd really hate to lose the internal swing (which I really like) simply because I need an external clock source to get the sequencer running at round BPMs.
flo
Well, what else is involved in your setup - if no DAW, why not make the Seq 1 the master?

IMO, it's always preferable to swing on the master so everything downstream gets that rhythm... In my case, an Innerclock Sync Gen Pro 2 does the job extremely nicely.

Trying to get any two machines to work together without sync connections will only be frustrating...
Bogus
flo wrote:
Well, what else is involved in your setup - if no DAW, why not make the Seq 1 the master?

IMO, it's always preferable to swing on the master so everything downstream gets that rhythm... In my case, an Innerclock Sync Gen Pro 2 does the job extremely nicely.

Trying to get any two machines to work together without sync connections will only be frustrating...


That is currently what I am doing, using the Sequencer 1 as the master clock. The issue arises when I load a recording into Ableton Live and have to dial in Live at hundredths of BPMs in order to avoid the need to timestretch/pitch shift back to the tempo I desire. Also wouldn't the use of an external module such as the Innerclock still disable the swing feature?
Crandall1
You know you can just clock it with audio or whatever, yeah? Just grab a single cycle square wave, drop it in Simpler, sequence it to 16th notes, give it the amount of swing you want, and slam it out one of your audio outputs. It'll clock like a champ off that. Voltage is voltage. You can also get fancy with the RESET input on a separate channel if you want, so it'll start and stop in sync.

Just use your imagination. Or get Silent Way or Volta. Or whatever. There are about a thousand ways to deal with this issue, but hoping that two different pieces of hardware will stay in some sort of lockstep without any sync mechanism isn't going to happen. Period. Ever. Full stop.
Bogus
I was just trying to submit what I thought was a bug report about the internal clock of the sequencer 1 being slow. Sorry if I seem to be slamming your product, that is not my intention. I enjoy it very much and only want to see it improve with future updates.
dmod
Bogus wrote:
I was just trying to submit what I thought was a bug report about the internal clock of the sequencer 1 being slow. Sorry if I seem to be slamming your product, that is not my intention. I enjoy it very much and only want to see it improve with future updates.
I dont think you were slamming the sequencer and I know excactly where you are coming from but I think the point may be that you will be hard pressed to find anything sync perfectly in free run mode without actually syncing it with clocks. Try running two DAWs at the same tempo from two different computers and see if they stay in sync hihi
Crandall1
Yeah, I didn't think you were slamming it. I think you were just confused about how things should work. This isn't a bug, but rather the Way Things Are.

It's easy to get around, though. Like I said, we put that sync jack on there for a reason, and there are numerous ways to utilize it.
psyclone001
I am going to chime in here and say the Seq1 is the most stable clock wise out of my three euro sequencers. The clock stability was the first thing that amazed me when I started using this module. My other sequencers have required a little experimenting to achieve the same clock stability as the Seq1
As mentioned if you are having clock issues I think you will need to look elsewhere in your system as the Seq1 is rock solid in its timing
wxyz
https://soundcloud.com/strangeattractor/bossa-seq1

Loving the ratchet
synthmind
I don't think this has been mentioned yet, but is there already a way to save tempo settings per pattern, rather than just one universal tempo setting? If I'm missing something please let me know!

I'm also with that one suggestion of holding the step button to mute and pressing to select, rather than the opposite.
Bogus
Is it possible to duplicate the contents of a measure/range of notes onto other parts of a sequence? If not a feature to select a range of notes and paste them anywhere on the same sequence would be really great for building progressions quickly.
Slomen
Bogus wrote:
Is it possible to duplicate the contents of a measure/range of notes onto other parts of a sequence? If not a feature to select a range of notes and paste them anywhere on the same sequence would be really great for building progressions quickly.


+100
This is on top of my wishlist!
Crandall1
I agree, but it's a tricky problem. It's on the list of things we have to figure out, anyhow. I would very much like that as well, as I tend to do a lot of two-measure patterns, where only the last step or two of the 2nd measure is slightly different.
Slomen
What I´d like it being able to use the copy function "internally" in a sequence. So for instance if I copy my first 16 bars, when I press paste in the same sequence it would paste the 16 bars to the next 16 bars (17-32). And if I copied and pasted again I would copy my 32 bars and pasting that to 33-64.
kisielk
Crandall1 wrote:
I agree, but it's a tricky problem. It's on the list of things we have to figure out, anyhow. I would very much like that as well, as I tend to do a lot of two-measure patterns, where only the last step or two of the 2nd measure is slightly different.


The DSI Tempest handles this fairly well. You can work on a 16 step sequence and then later change the length to 32. When you change the length it just duplicates the first 16 steps. Similarly if you go from 32 to 64, or 64 to 128. It makes it fairly easy to build up variations.
Parametex
kisielk wrote:
Crandall1 wrote:
I agree, but it's a tricky problem. It's on the list of things we have to figure out, anyhow. I would very much like that as well, as I tend to do a lot of two-measure patterns, where only the last step or two of the 2nd measure is slightly different.


The DSI Tempest handles this fairly well. You can work on a 16 step sequence and then later change the length to 32. When you change the length it just duplicates the first 16 steps. Similarly if you go from 32 to 64, or 64 to 128. It makes it fairly easy to build up variations.


Same workflow as with Rytm.
Crandall1
We'll probably end up doing something like that. Although it's semi-funky as there's no real concept of "measure" as such in Sequencer 1, while both those units are beholden to the God Of Measures.
SunSpots
when should we expect the next update with all the amazing? smile
Crandall1
Working on it now. It'll be done when it's done. :-)
juvation
is quantisation in-key on the list? i'd like to be able to transpose via external CV while staying in key.

thanks for great product :-)
granville
juvation wrote:
is quantisation in-key on the list? i'd like to be able to transpose via external CV while staying in key.

thanks for great product :-)


+1
juvation
not sure about the tap to select and hold to mute/unmute. i can see wanting to mute or unmute in a hurry, but not really select.

i think i like it the way it is
Bogus
granville wrote:
juvation wrote:
is quantisation in-key on the list? i'd like to be able to transpose via external CV while staying in key.

thanks for great product :-)


+1


+2

Also, a scale locked note editing mode would be killer. Like if I could select a scale and sequencer 1 wouldn't respond to requests of note changes that aren't within that scale. I could stop paying for piano lessons and just funnel that money into more audio damage gear hihi
Crandall1
You might as well, at that point, just buy me a plane ticket and I'll come to your house and write your music for you. :-)

Seriously, though, we're trying to balance simplicity, ease of use, and power. Not that easy a task; I don't have any particular problem putting little-used features deep in the menu tree, but then it ends up with everyone trying to get to the one feature they want to use, and 100% of you complaining about menu diving.

So, to some of these, I can only answer "we'll think about it but no promises." If we add the Scala feature, I'll note that there is a Scala file for every single key, mode, tuning, scale, and batshit-insane idea to replace dental work that some grad student came up with. Ever. In the history of music. So that will totally conquer any and all of your tuning/scale/whatever wishes. That's a big "if," though. And boy, do I not look forward to testing that. I really don't like alternate tunings and forced scales. They make my teeth hurt in the worst way.
SunSpots
Crandall1 wrote:
You might as well, at that point, just buy me a plane ticket and I'll come to your house and write your music for you. :-)

Seriously, though, we're trying to balance simplicity, ease of use, and power. Not that easy a task; I don't have any particular problem putting little-used features deep in the menu tree, but then it ends up with everyone trying to get to the one feature they want to use, and 100% of you complaining about menu diving.

So, to some of these, I can only answer "we'll think about it but no promises." If we add the Scala feature, I'll note that there is a Scala file for every single key, mode, tuning, scale, and batshit-insane idea to replace dental work that some grad student came up with. Ever. In the history of music. So that will totally conquer any and all of your tuning/scale/whatever wishes. That's a big "if," though. And boy, do I not look forward to testing that. I really don't like alternate tunings and forced scales. They make my teeth hurt in the worst way.


quantization would be sweet and might put it up with metropolis for ease of good sound creation without me having to think.

but yeah knob recording would be hawt...
psyclone001
Hello Chris
Just wanting to confirm. It seems the 3 x LFO's can be programmed and saved per preset (or pattern) although the 2 assignable CV inputs are assigned globally to all presets?
Crandall1
That's correct. IN GENERAL outputs are per pattern and inputs are global.
psyclone001
Cheers thumbs up
nidas
This looks great!
Slomen
It is great! I am having a blast with mine Rockin' Banana!
Bogus
To those asking for knob recording, what parameters have you found that you want to use this feature with the most?
tekzon
Sorry but i don't get it,
cv outs are quantized or i need an external quantizer?
thanks
psyclone001
tekzon wrote:
Sorry but i don't get it,
cv outs are quantized or i need an external quantizer?
thanks

Are you referring to pitch cv out or assignable cv outs 1-3
Pitch cv out sends the pitch of whatever you have programmed with the mini onboard keyboard. No need for a quantiser if these programmed notes are what you want. Of course if you want to transpose the sequence the easiest way at the moment is to use a quantizer
SunSpots
Bogus wrote:
To those asking for knob recording, what parameters have you found that you want to use this feature with the most?


anything and everything. mainly the 3cv outs and the gate times or pitch, the lfo amplitude or speed... the way knob recording is used on elektron boxes is to allow,the user to really glitch out their sequence and even create something totally different. also, so we can modulate the filter in just that perfect organic way the lfos aren't doing, but our wiggling fingers are doing just fine,

short answer, anything you can... and yes I used to record so many knob twists it would negatively impact the performance of the elektron box... which was sometimes desirable.
Bogus
I see now, that would lead to some very interesting results. Do you know of any demos showcasing that particular feature of the elektron box?
Octopanner
SunSpots wrote:
Bogus wrote:
To those asking for knob recording, what parameters have you found that you want to use this feature with the most?


anything and everything. mainly the 3cv outs and the gate times or pitch, the lfo amplitude or speed... the way knob recording is used on elektron boxes is to allow,the user to really glitch out their sequence and even create something totally different. also, so we can modulate the filter in just that perfect organic way the lfos aren't doing, but our wiggling fingers are doing just fine,

short answer, anything you can... and yes I used to record so many knob twists it would negatively impact the performance of the elektron box... which was sometimes desirable.


Yessssssss,
Take many many notes from Elektron
VanEck
Really digging this sequencer. Flawless performance since the firmware upgrade. No more patterns vanishing. Probably my favorite hardware sequencer ever, and I've owned quite a few. No complaints.

To add to the heaping pile of wishful feature suggestions, only a few come to mind.

1. add a random sine waveform to the possible LFO waveshapes for some tempo synched wobbly goodness.

2. random pattern generation and/or pattern mutation like possible in Reason... if the mutate could be controlled via CV and mapped to the onboard LFO's, even better.

3. probably not possible, but add the ability to have a second sequence going out by assigning another pitch CV out to one of the CV outputs. I'm not talking about a multed output, but an entire second programmable sequence similar to what my Kilpatrick step sequencer could do.

4. be able to program only certain steps to randomize or mutate within a sequence, or have probability of that step being on/off.
psyclone001
VanEck wrote:
Really digging this sequencer. Flawless performance since the firmware upgrade. No more patterns vanishing. Probably my favorite hardware sequencer ever, and I've owned quite a few. No complaints.

To add to the heaping pile of wishful feature suggestions, only a few come to mind.

1. add a random sine waveform to the possible LFO waveshapes for some tempo synched wobbly goodness.

2. random pattern generation and/or pattern mutation like possible in Reason... if the mutate could be controlled via CV and mapped to the onboard LFO's, even better.

3. probably not possible, but add the ability to have a second sequence going out by assigning another pitch CV out to one of the CV outputs. I'm not talking about a multed output, but an entire second programmable sequence similar to what my Kilpatrick step sequencer could do.

Yes no.2 has been my top request along with quantizing/transposing, and now that I have been using the LFO's more no.1 was the next on my wish list thumbs up
psyclone001
Oh and by the way, it has become my favourite sequencer also.
Audio Damage kicking ass big time. I guess we may seem ungrateful to poor Chris, I'm sure he's sick of us already demanding new features and what not, but he should take it as a huge compliment I reckon. He's created a monster, and I think we are all realising how huge the potential is twisted SlayerBadger!
flo
VanEck wrote:
Really digging this sequencer. Flawless performance since the firmware upgrade. No more patterns vanishing. Probably my favorite hardware sequencer ever, and I've owned quite a few. No complaints.

To add to the heaping pile of wishful feature suggestions, only a few come to mind.

1. add a random sine waveform to the possible LFO waveshapes for some tempo synched wobbly goodness.

2. random pattern generation and/or pattern mutation like possible in Reason... if the mutate could be controlled via CV and mapped to the onboard LFO's, even better.

3. probably not possible, but add the ability to have a second sequence going out by assigning another pitch CV out to one of the CV outputs. I'm not talking about a multed output, but an entire second programmable sequence similar to what my Kilpatrick step sequencer could do.

4. be able to program only certain steps to randomize or mutate within a sequence, or have probability of that step being on/off.


I requested 3) as well, the easiest way is to just allow the cv outs to be in key (like the pitch out) as well. No big deal as there are already different modes for it (LFO etc.), just add "key". I think this is on the list.

You can already get two voices going though, V in 2 decimal places is ok to tune the sequence. And there's the accent out for your second gate...
granville
VanEck wrote:

2. random pattern generation and/or pattern mutation like possible in Reason... if the mutate could be controlled via CV and mapped to the onboard LFO's, even better.


VanEck wrote:
4. be able to program only certain steps to randomize or mutate within a sequence, or have probability of that step being on/off.


Loads of good ideas here. I particularly like these two suggestions.

I really like the way the M4L step sequencer works with randomisation possible, as a percentage change from previous pattern, with the ability to keep the notes in key. If Seq1 could do that then I would eat my copy of Ableton.
psyclone001
The Nord G2 patch mutator / randomiser rules.
Applying this to its built in sequencer modules with quantization enabled is endless madness twisted
Slomen
I really liked that feature where Chris comes to my house and writes the music for me! I´ll provide the booze Chris! wink

But seriously, a BIG +1 to this:

psyclone001 wrote:
Oh and by the way, it has become my favourite sequencer also.
Audio Damage kicking ass big time. I guess we may seem ungrateful to poor Chris, I'm sure he's sick of us already demanding new features and what not, but he should take it as a huge compliment I reckon. He's created a monster, and I think we are all realising how huge the potential is twisted SlayerBadger!
Crandall1
If you're okay with everything sounding like Pretty Hate Machine, then I'm on the next plane.

Anyhow, some minor news: we have feature-frozen the v1.1 update (nerd-speak for "we've decided what's going in it") and are coding that bitch up now. You'll have to look back through about 30 pages worth of feature requests to find what we've decided to put in 1.1, but suffice to say that several asks are in there.

So, give us a bit to get everything nice and tidy, and another bit to test, and we'll have a v1.1 for you.

Regarding the random sine, I assume that it would be like the existing Random Ramp, where the amplitude is randomized from zero crossing to zero crossing? I'll bring this up to Adam. He likes this sort of thing.
flo
Sweetness! Especially looking forward to those ground breaking features no one has requested so far hihi SlayerBadger! nanners
Crandall1
flo wrote:
Sweetness! Especially looking forward to those ground breaking features no one has requested so far


I'm sad to report that none of them will be in v1.1, which is still trying to catch up to stuff you guys have requested that are excellent ideas. (And there are quite a few.) There are three major feature additions in all, and they'll knock your socks off. They're slated for v1.2, v1.3, and v1.4. We haven't proofed them yet, so I'm not going to talk about them until we've added them.

We had originally slated the first major one as v1.1, and were about to begin work on it, but I put the kaibosh on that, by dearly wanting (for myself, because I'm a selfish bastard) a programming mode where the unit acted like a standalone groovebox, where the pitch CV is not "live" all the time, but held from gate to gate. That's a big enough programming change that it becomes a version unto itself. So we went through and found some of the more popular feature requests from this thread that we could roll in with that one change, related to it, and that became v1.1. Adam is working on it now.

I don't have an ETA, but I don't think it'll take too long.
granville
Crandall1 wrote:
a programming mode where the unit acted like a standalone groovebox, where the pitch CV is not "live" all the time, but held from gate to gate.

Rockin' Banana! Rockin' Banana! Rockin' Banana!

Yeehaw!
juvation
Crandall1 wrote:
a programming mode where the unit acted like a standalone groovebox, where the pitch CV is not "live" all the time, but held from gate to gate.


reading my mind here. a switch for essentially "digital sequencer" mode for not updating the pitch if there isn't a gate on that step - fabuloso. i'm already terribly weary from copying pitches from a gate step to succeeding non-gate steps ;-)
flo
For immediate remedy: stick a S/H after your pitch CV, triggered by the Seq 1 gate out thumbs up
Crandall1
Yeah. A couple of the professionals that got early units have conversed with me in private about that bug/feature. We made it act like an analog sequencer on purpose, but as it turns out, if people wanted an analog sequencer they'd have bought one.

So, it'll be a global on/off option. That's the main thing in this update. It'll also have three of the features that have been asked for here the most. We actually keep a spreadsheet with a running tally, so you guys don't ever have to be reticent about asking for new things. The ones that most people seem to agree on, or, well, either Adam or I think are a logical extension, are the ones that get rolled in the soonest.

I'll be intrigued if someone hits on the three Big Ones. So far, it hasn't occurred to anyone that Sequencer 1 is capable of them.
juvation
i don't suppose there's any chance... of digital sequencer pitch mode being programmable per sequence? i can see situations where i'd want both.

i'm still exploring my Seq1 so i'm definitely not sure of its full capabilities as yet. are you going to tease about the Big Ones? :-)

one thing that did occur to me -- it's odd that half the step switches are effectively dead in the top mode. if i was designing this i might have used the note keys for repeat & ratchet, and used the step switches for sequence selection in the current bank (and sequence chaining by holding multiples, like 606 et al).
Crandall1
We have plans for the keyboard that preclude doing it as you said.
flo
Crandall1 wrote:
I'll be intrigued if someone hits on the three Big Ones. So far, it hasn't occurred to anyone that Sequencer 1 is capable of them.


Let the guessing begin! It's peanut butter jelly time! Dead Banana

1) Complex multi-stage envelope generator, PEG style. Trigger input somewhere for triggering, time between stages determined by clock input (or internal clock). Smoothing between stages.

Oh wait we can kinda do that already with some helpers It's motherfucking bacon yo

2) Complex quantizer + microtonality. Maybe other forms of CV mangling...?

3) hmmm..... seriously, i just don't get it
Bogus
Crandall1 wrote:
I'll be intrigued if someone hits on the three Big Ones. So far, it hasn't occurred to anyone that Sequencer 1 is capable of them.


1) trigger resets for LFOs assignable to the CV ins
2) master sequence mode that lets the user select their pre-programmed subsequences from the banks and assign them to steps (please)
3) out of nowhere: multicolored LEDs
Ras Thavas
Just curious if the other 3 cv outputs will get the ability to output 1 volt 1 octave in the 1.1 update? If I remember right this was a feature that was due to arrive relatively soon.

I'm thinking Seq 1 could be used for sequencing 3 separate voices, using the basic 1v1oct output, 2 cv outs as 1v1oct, and the last cv output as a gate to go along with the regular gate and accent.

Really liking the potential flexibility with all the outputs.
Crandall1
That's coming in a bit (it rides on the back of one of the Big Features, actually.)
juvation
if the LFOs only triggered on steps when there was a gate, and accents made them bigger, then i could get rid of a few modules :-)

seriously though, great stuff as it is now. getting off the ground was really easy, and the capabilities are dazzling.
studionebula
Bogus wrote:


1) trigger resets for LFOs assignable to the CV ins
2) master sequence mode that lets the user select their pre-programmed subsequences from the banks and assign them to steps (please)
3) out of nowhere: multicolored LEDs


1) That's an intriguing idea. Yes, I'd like to add that eventually.
2) We've debated a bit about whether this would be necessary sooner rather than later. So far it's slated for "later" but we're open to input.
3) Won't happen, sorry. I'm not even sure whether the buttons we use are available with multi-colored LEDs, but even if they are, two colors doubles the wiring complexity for the LEDs and adds three more chips, and I had a hard-enough time laying out the PCB as it is.
studionebula
juvation wrote:
i don't suppose there's any chance... of digital sequencer pitch mode being programmable per sequence? i can see situations where i'd want both.


Oh dear. I was hoping that people would be satisfied if it was a global option rather than a per-pattern option, but after your post, upon further discussion Chris and I agree that it's probably better as a per-pattern setting. So it shall be, then.
studionebula
juvation wrote:
if the LFOs only triggered on steps when there was a gate, and accents made them bigger, then i could get rid of a few modules :-)

Would you then spend the money you made on a second Sequencer 1? Mr. Green

juvation wrote:
seriously though, great stuff as it is now. getting off the ground was really easy, and the capabilities are dazzling.


Seriously though, thanks very much for the kind words, and the business. Glad you're enjoying it! By "bigger" do you mean that the amplitude of the LFO would increase if there was an accent programmed on the same step with the gate which triggers the LFO?
studionebula
Crandall1 wrote:
Regarding the random sine, I assume that it would be like the existing Random Ramp, where the amplitude is randomized from zero crossing to zero crossing? I'll bring this up to Adam. He likes this sort of thing.


Yes--to whomever wrote the OP, is what Chris described what you mean, or did you have something else in mind? He's right, I like this sort of thing, and it's relatively easy to add new shapes to the LFOs.

Okay, I'm gonna regret saying that. lol It's "relatively easy" within a number of constraints, the biggest one being that it becomes not-easy if calculating the next cycle of the wave requires knowing something about the previous cycle, or even knowing something about past values within the current cycle.
extra testicle
Crandall1 wrote:
That's coming in a bit (it rides on the back of one of the Big Features, actually.)


polyphonic ("graphic") vco? lol how fast does that thing go?
juvation
studionebula wrote:
juvation wrote:
if the LFOs only triggered on steps when there was a gate, and accents made them bigger, then i could get rid of a few modules :-)

Would you then spend the money you made on a second Sequencer 1? Mr. Green


well that depends on how many modules are rendered unnecessary, doesn't it? :-)

studionebula wrote:
Seriously though, thanks very much for the kind words, and the business. Glad you're enjoying it! By "bigger" do you mean that the amplitude of the LFO would increase if there was an accent programmed on the same step with the gate which triggers the LFO?


yes -- it would be rad to apply the accent to one of the CV outs. saves me a VCA.... more money for Seq1 #2!
VanEck
studionebula wrote:
Crandall1 wrote:
Regarding the random sine, I assume that it would be like the existing Random Ramp, where the amplitude is randomized from zero crossing to zero crossing? I'll bring this up to Adam. He likes this sort of thing.


Yes--to whomever wrote the OP, is what Chris described what you mean, or did you have something else in mind? He's right, I like this sort of thing, and it's relatively easy to add new shapes to the LFOs.


Kinda sorta. I was thinking more randomized time synched frequency more than amplitude... kind of like what I could do with my PEG when in bi-polar mode, tempo synched to the main tempo but changing the division/multiplication of the cycle.

Could program it so that every 8 steps (or whatever) the tempo synched division/multiplication of the sine cycle randomly changes.

For example, let's use the old "Dubstep" filter trick as an example. Could have the Random Sine mapped to the cutoff frequency of a filter, have a 16 step sequence going, and make it so every 16 steps the tempo synched frequency of the Sine changes randomly... WUB...WUB...WUB...WUB.WUB.WUB.WUB.......WUB.......WUB.......WUB
Crandall1
Ah. So not at all what I thought. Well... I don't think it's set up for that but we'll talk about it. If it was just the random amp, that would be pretty simple (the mechanism is already there, since that's how RANDRAMP works) but what you're asking is actually somewhat outside what we have going on.
psyclone001
Crandall1 wrote:
Ah. So not at all what I thought. Well... I don't think it's set up for that but we'll talk about it. If it was just the random amp, that would be pretty simple (the mechanism is already there, since that's how RANDRAMP works) but what you're asking is actually somewhat outside what we have going on.

Well I for one would be very happy with just a random sine to start with. Probably one of my favourite modulation sources actually. Nice and easy tweaking a filter etc thumbs up
studionebula
VanEck wrote:
Kinda sorta. I was thinking more randomized time synched frequency more than amplitude... kind of like what I could do with my PEG when in bi-polar mode, tempo synched to the main tempo but changing the division/multiplication of the cycle.

Could program it so that every 8 steps (or whatever) the tempo synched division/multiplication of the sine cycle randomly changes.


Okay, that's interesting. hmmm.....
As Chris said, it requires things that are outside what's currently going on in the code, and my first thought was that it's difficult to do because it requires introducing a new parameter which applies only to this particular mode. However, one approach which does not require such an addition would be that the Length parameter of the LFO specifies the interval at which a new random frequency is picked, i.e. Length corresponds to your "every 8 steps (or whatever)". I think that this would necessarily mean that the randomly chosen values would range from one (the shortest possible LFO period) to whatever Length is set to. Would that behavior do what you want?
SunSpots
1) quantization
2) knob recording
3) I don't know the first two are my main wish list

smile
VanEck
studionebula wrote:

However, one approach which does not require such an addition would be that the Length parameter of the LFO specifies the interval at which a new random frequency is picked, i.e. Length corresponds to your "every 8 steps (or whatever)". I think that this would necessarily mean that the randomly chosen values would range from one (the shortest possible LFO period) to whatever Length is set to. Would that behavior do what you want?


Yeah that sounds like it could definitely yield some interesting results. When you say a minimum of 1 as the shortest cycle, do you mean 1 step? So for example, with the length parameter set to 8, the Sine would randomly pick a cycle anywhere between 1 step to 8 steps? And for example if it randomly selected the minimum of 1, it would keep repeating its cycle of 1 until it reach the end of the 8 step length and then randomly select a new cycle speed? That is indeed very close to what I was thinking.
Bogus
Just a thought: You should consolidate the CV input menus to one button that cycles between the two ins (similar to how Alt+Mod cycles between the three lfo menus) to open up an extra button for these new projected features.
Crandall1
I think it would work best if it randomly chose between musically relevant intervals. Powers of two and trips only, maybe? I think we'd have to try it, honestly.

Regarding stacking the CV input buttons, well then you'll end up with something mis-labeled, plus those need quick access.
studionebula
VanEck wrote:

Yeah that sounds like it could definitely yield some interesting results. When you say a minimum of 1 as the shortest cycle, do you mean 1 step? So for example, with the length parameter set to 8, the Sine would randomly pick a cycle anywhere between 1 step to 8 steps? And for example if it randomly selected the minimum of 1, it would keep repeating its cycle of 1 until it reach the end of the 8 step length and then randomly select a new cycle speed? That is indeed very close to what I was thinking.


Yes, that's what I meant on all points. One step is the shortest cycle length, i.e. the fastest that the LFOs run is completing one wave cycle in one step. So it might go through eight cycles, then four cycles each two steps long, etc.

Here's the problem, though: what happens if, for example, the Length value is 8 and a cycle length of 3 gets randomly picked? The third cycle would get cut off 2/3 of the way through, creating a discontinuity when the next 8-step cycle starts. That's not the end of the world, but it does kind of defeat the purpose of using a smooth sinusoid for modulation.
Crandall1
Perhaps if it chose between values that fit evenly in to step numbers. So if you had a pattern of, say, 7 steps, it would only choose 1 or 7 as the cycle. If your pattern was 16, it could choose 1, 2, 4, or 8. 12 steps would get 1, 2, 3, or 4.
studionebula
Crandall1 wrote:
Perhaps if it chose between values that fit evenly in to step numbers. So if you had a pattern of, say, 7 steps, it would only choose 1 or 7 as the cycle. If your pattern was 16, it could choose 1, 2, 4, or 8. 12 steps would get 1, 2, 3, or 4.

Yeah, it could do that. It gets to be an interesting math problem, though, when you realize that our LFO Length parameter has a max value of 256.
Crandall1
Sounds like a job for someone that knows math! Someone entirely unlike, you know, me.
psyclone001
Seems like you're on the case boys. Good work thumbs up
Crandall1
Welcome to the Audio Damage development process. Please wear your nametag, and remember that the smoking lounge is on the back patio.
studionebula
Crandall1 wrote:
Sounds like a job for someone that knows math! Someone entirely unlike, you know, me.

Ooh, a brief bit of googling suggests that finding all of the divisors of a number is an NP-complexity problem. woah
Math-geeking aside, another solution would be to allow the LFO to have a fractional length, so that it could complete seven cycles in the span of eight steps, or three cycles in eight steps, or whatever. Off the top of my head I think that we have that kind of precision available to us; I did spend a good deal of time getting the LFOs to run accurately. nuts I'm not sure how "musically useful" that might end up sounding, however.
clusterchord
1. quantizing. microtonal.
2. knob recording per step
3. moving the sequence horizontally and vertically,.. i.e. changing what is step1, and transposing in-key.

those are three big ones for me.



Crandall1 wrote:
So, to some of these, I can only answer "we'll think about it but no promises." If we add the Scala feature, I'll note that there is a Scala file for every single key, mode, tuning, scale, and batshit-insane idea to replace dental work that some grad student came up with. Ever. In the history of music. So that will totally conquer any and all of your tuning/scale/whatever wishes. That's a big "if," though. And boy, do I not look forward to testing that. I really don't like alternate tunings and forced scales. They make my teeth hurt in the worst way.


i hope you dont find me unreasonable for bringing it up, after all the initial mention of this came from Adam hihi . i'm just riding along this phenomenal idea, since there is an obvious vacuum in the whole euro market - no user editeable microtonal quantizers. except expert sleepers, but thats a whole different ballgame and convoluted.

this is after all eurorack, where one can do things from pop and mainstream to fullout experimental and contemporary stuff. why limit such a powerful weapon like sequencer to only equal temperament?


anyways, perhaps we don't need all the endless permutations,,, 16 or 32 user editable preset scales, in cents, would be fine, even if there is no support for scala files per se. of course, if scales can be saved/loaded, all the better. so once we do the tedious chore of editing one of these, we don't have to do it ever again. possibly even share interesting ones with others etc.


fwiw, i want seq1 regardless. with or without microtonality. but, hope springs eternal..
Crandall1
Let me state this for the record: it will absolutely have user scales. That much is beyond question. Quick poll, for the people that care about such things:


Would you rather have

A - A couple dozen user-editable scales, where it might be slightly ridiculous to edit them on the machine. (I assume we could come up with a file format that was human-readable, and thus editable on your computer.)

B - Scala, with all that entails.

We could do the former sooner. The latter would obviously be more comprehensive.
Kummer
Crandall1 wrote:
Let me state this for the record: it will absolutely have user scales. That much is beyond question. Quick poll, for the people that care about such things:


Would you rather have

A - A couple dozen user-editable scales, where it might be slightly ridiculous to edit them on the machine. (I assume we could come up with a file format that was human-readable, and thus editable on your computer.)

B - Scala, with all that entails.

We could do the former sooner. The latter would obviously be more comprehensive.


Though I don't have one... yet. I vote for: User Editable

Edit: Ok both. with User Editable first and full Scala later on down the line
Bogus
User editable and simple please hihi
spritepixie
I'm a soon-to-be-owner and I would love to have Scala integration. I'm excited to hear that it will have user editable scales.
psyclone001
For me this is the only feature the Metropolis has the edge over Seq1, and because I am used to their system something like metropolis's would be great.
Basic transposition up/down of the existing pattern is a must and also preset scale selection would be great, but if not possible at first, then user programmable scales would be fine as I tend to only use a few anyway (various minor scales by the way) thumbs up
juvation
my quantisation in-key requirements are pretty modest :-)

right now i pipe sequences through an Intellijel uScale, which gives visual feedback of the scale in use and lets me add new notes when i feel like it. adds a lot to the mileage i can get from a sequence :-)

if a sequence had a tuning table associated with it that's editable from the hardware keyboard on the Seq1, that would be fab -- though i understand there are Big Plans for the keyboard that may well not gel with this.

if i had to enter a mode to get to editing the scale, that would be fine.

i've no requirement for alternate tunings or microtunings or anything like that. if i have to author scales on my computer, then OK, as long as i can author a hundred of them and easily choose from them from the Seq's front panel while a sequence is running.
kuxaan-sum
Both A and B.... hihi

Would be fine to edit on computer before hand but I too would like to have a decent selection on hand that can be selected in real time.
Kummer
Honestly though, to me scales wouldn't be a must have right away thing. As long as you know the keys of the scale you want to work in (which isn't hard to find or figure out) you have total control on a per step basis as to what notes are being played.
juvation
indeed -- the problem is that if you transpose via a CV input, any scale you happened to be in is lost.
clusterchord
Crandall1 wrote:
Let me state this for the record: it will absolutely have user scales. That much is beyond question.


those are fantastic news applause


Crandall1 wrote:
Quick poll, for the people that care about such things:

Would you rather have

A - A couple dozen user-editable scales, where it might be slightly ridiculous to edit them on the machine. (I assume we could come up with a file format that was human-readable, and thus editable on your computer.)

B - Scala, with all that entails.

We could do the former sooner. The latter would obviously be more comprehensive.


if by A, you mean microtonal user editable scales, so we can input the offsets via text edit or something, then i'd be content with A, bcs given i put enough time into it, i could load practically any tuning in existance, or do a completely custom affair.


and like others, perhaps down the line if you ever got arround to it, i definitely wouldn't say no to B.
psyclone001
I would actually be quite happy at this stage with just transposition of preset patterns up/down in semitones. I have programmed a bunch of patterns in D# Phrygian for a track I was working on, and now just want transpose down 1 semitone to D Phrygian. Only option at the moment is to copy the pattern, then shift manually all notes down 1 semitone. There is a 'transpose' modulation destination but haven't figured out how to send a reliable signal to that cv input to control semitone up/down transposition of the whole pattern hmmm.....
Octopanner
psyclone001 wrote:
For me this is the only feature the Metropolis has the edge over Seq1, and because I am used to their system something like metropolis's would be great.
Basic transposition up/down of the existing pattern is a must and also preset scale selection would be great, but if not possible at first, then user programmable scales would be fine as I tend to only use a few anyway (various minor scales by the way) thumbs up


The core of the metro is a totally different beast, it emphasizes keeping everything in scale, rather than specific notes, makes it the ultimate improvisational machine.

The seq-1 should maybe be more compared to the ER-101
http://www.orthogonaldevices.com/er-101
[/list]

Still... looks pretty cool, just kind of expensive and I wish the jacks were on the top and not on the bottom, I just see my wrists constantly hitting the spaghetti wire when I am trying to play around. Any chance of a version where the inputs/outputs are placed on the top??? I think that would be way more ergonomic for many setups and I could be convinced.

On the whole, I think sequencers should almost always have jacks in the middle or on the top, I like to do a lot of things on the fly and I hate it when they put the jacks on the bottom for seqs.... my only gripe with my ER-101.
Crandall1
psyclone001 wrote:
For me this is the only feature the Metropolis has the edge over Seq1, and because I am used to their system something like metropolis's would be great.
Basic transposition up/down of the existing pattern is a must and also preset scale selection would be great, but if not possible at first, then user programmable scales would be fine as I tend to only use a few anyway (various minor scales by the way)


I'm not going to just say "someday we're gonna do X, Y, and Z" because I've done enough of that in this thread to where it's starting to be comical.

I'll just say this much and leave it: in a very short time, you will no longer be sad.

There is apparently some confusion here, though, because I mis-typed "scales" in my poll, when I meant tables. Scala files are largely concerned with tuning systems, not scales and modes. I was specifically asking about user tuning tables, not the ability to constrain the unit to Dorian in A or whatever. Adam and I had a long discussion today, and we came to the conclusion that trying to shoehorn in a method to make tuning tables on the unit itself would be incredibly ungainly; as such, it would be easier to implement Scala. So we'll aim at that, for an update down the road.

So, to clarify: scales/modes/root/transposition are all one thing, which will be dealt with promptly, as it is the single most requested combination of features in this thread, and Scala tuning tables for, say, JI or 17-TET, or any other ridiculous teeth-grinding method for displaying one's cleverness, are an almost entirely, but not completely, unrelated thing.

(I will not even attempt to hide my personal disdain for such tomfoolery. But we're all about customer service, and Audio Damage Caresâ„¢!!!)

Anyhow, to the factory floor. We have our marching orders, and we shall emerge shortly, with a shiny new software update for your firmware-burning pleasure.
psyclone001
Yeah baby yeah SlayerBadger!
Octopanner
Crandall1 wrote:
psyclone001 wrote:
For me this is the only feature the Metropolis has the edge over Seq1, and because I am used to their system something like metropolis's would be great.
Basic transposition up/down of the existing pattern is a must and also preset scale selection would be great, but if not possible at first, then user programmable scales would be fine as I tend to only use a few anyway (various minor scales by the way)


I'm not going to just say "someday we're gonna do X, Y, and Z" because I've done enough of that in this thread to where it's starting to be comical.

I'll just say this much and leave it: in a very short time, you will no longer be sad.

There is apparently some confusion here, though, because I mis-typed "scales" in my poll, when I meant tables. Scala files are largely concerned with tuning systems, not scales and modes. I was specifically asking about user tuning tables, not the ability to constrain the unit to Dorian in A or whatever. Adam and I had a long discussion today, and we came to the conclusion that trying to shoehorn in a method to make tuning tables on the unit itself would be incredibly ungainly; as such, it would be easier to implement Scala. So we'll aim at that, for an update down the road.

So, to clarify: scales/modes/root/transposition are all one thing, which will be dealt with promptly, as it is the single most requested combination of features in this thread, and Scala tuning tables for, say, JI or 17-TET, or any other ridiculous teeth-grinding method for displaying one's cleverness, are an almost entirely, but not completely, unrelated thing.

(I will not even attempt to hide my personal disdain for such tomfoolery. But we're all about customer service, and Audio Damage Caresâ„¢!!!)

Anyhow, to the factory floor. We have our marching orders, and we shall emerge shortly, with a shiny new software update for your firmware-burning pleasure.


You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW
Crandall1
Octopanner wrote:

You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


How so? We're implementing virtually everything that has been asked for in this thread. You asked for the jacks to be moved. That's not going to happen, of course. If you're referring to the microtuning capabilities, even Adam (the person actually coding it) wants that. I'm the only person on the planet that doesn't, and we're doing it anyhow.

EDIT: I am nearly positive, from the grammatical foibles and other posts, that new wiggler "octapanner" is actually our just-banned friend from the recently locked thread.

EDIT 2: Yup. Absolutely sure now. "octapanner" is "nblazer201"
akrylik
Crandall1 wrote:
Octopanner wrote:

You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


How so? We're implementing virtually everything that has been asked for in this thread. You asked for the jacks to be moved. That's not going to happen, of course. If you're referring to the microtuning capabilities, even Adam (the person actually coding it) wants that. I'm the only person on the planet that doesn't, and we're doing it anyhow.

EDIT: I am nearly positive, from the grammatical foibles and other posts, that new wiggler "octapanner" is actually our just-banned friend from the recently locked thread.


If so then an IP-address ban is appropriate IMO.
Crandall1
I'm ignoring him. If he can prove he isn't nblazer201, I'll unignore, but someone else will have to tell me. I don't have to put up with that shit in this thread, which is entirely for actual owners and prospective buyers of Sequencer 1.
nblazer201
Crandall1 wrote:
Octopanner wrote:

You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


How so? We're implementing virtually everything that has been asked for in this thread. You asked for the jacks to be moved. That's not going to happen, of course. If you're referring to the microtuning capabilities, even Adam (the person actually coding it) wants that. I'm the only person on the planet that doesn't, and we're doing it anyhow.

EDIT: I am nearly positive, from the grammatical foibles and other posts, that new wiggler "octapanner" is actually our just-banned friend from the recently locked thread.


???

Calm down now with the personal stuff.

It's a public forum, and I am not flaming. I am simply saying, you shouldn't discourage feature requests, its a wonderful free piece of advice for your sequencer.

There, a calm opinion I carry. That's not ban worthy. You put your product up on a public forum to be discussed. I respect your efforts, lets put the bad blood behind.
LeCCComte
nblazer201 wrote:
Crandall1 wrote:
Octopanner wrote:

You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


How so? We're implementing virtually everything that has been asked for in this thread. You asked for the jacks to be moved. That's not going to happen, of course. If you're referring to the microtuning capabilities, even Adam (the person actually coding it) wants that. I'm the only person on the planet that doesn't, and we're doing it anyhow.

EDIT: I am nearly positive, from the grammatical foibles and other posts, that new wiggler "octapanner" is actually our just-banned friend from the recently locked thread.


???

Calm down now with the personal stuff.


Go away.
spritepixie
Octopanner wrote:


You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


I'm pretty convinced. Even a cursory glance at this thread would show that AD is totally receptive to suggestions, from outlandish to realistic.
nblazer201
LeCCComte wrote:
nblazer201 wrote:
Crandall1 wrote:
Octopanner wrote:

You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


How so? We're implementing virtually everything that has been asked for in this thread. You asked for the jacks to be moved. That's not going to happen, of course. If you're referring to the microtuning capabilities, even Adam (the person actually coding it) wants that. I'm the only person on the planet that doesn't, and we're doing it anyhow.

EDIT: I am nearly positive, from the grammatical foibles and other posts, that new wiggler "octapanner" is actually our just-banned friend from the recently locked thread.


???

Calm down now with the personal stuff.


Go away.


Stop, I am not flaming, I am just discussing the seq, please stop with the hate.
psyclone001
This thread just got weird. Let's move along. Where were we before we were so rudely interrupted lol
nblazer201
Crandall1 wrote:
psyclone001 wrote:
For me this is the only feature the Metropolis has the edge over Seq1, and because I am used to their system something like metropolis's would be great.
Basic transposition up/down of the existing pattern is a must and also preset scale selection would be great, but if not possible at first, then user programmable scales would be fine as I tend to only use a few anyway (various minor scales by the way)


I'm not going to just say "someday we're gonna do X, Y, and Z" because I've done enough of that in this thread to where it's starting to be comical.



It's whatever, just pointing it out to future consumers.

Cool sequencer tho, do actually really like the keyboard and cv in options.
nblazer201
psyclone001 wrote:
This thread just got weird. Let's move along. Where were we before we were so rudely interrupted lol


Yes pls
LeCCComte
nblazer201 wrote:
LeCCComte wrote:
nblazer201 wrote:
Crandall1 wrote:
Octopanner wrote:

You are not making me so confident for the future patch updates.....
People are throwing you incredible suggestions for the future, I would be a little more receptive or at least fake it...
Free crowd sourced instrument engineering FTW


How so? We're implementing virtually everything that has been asked for in this thread. You asked for the jacks to be moved. That's not going to happen, of course. If you're referring to the microtuning capabilities, even Adam (the person actually coding it) wants that. I'm the only person on the planet that doesn't, and we're doing it anyhow.

EDIT: I am nearly positive, from the grammatical foibles and other posts, that new wiggler "octapanner" is actually our just-banned friend from the recently locked thread.


???

Calm down now with the personal stuff.


Go away.


Stop, I am not flaming, I am just discussing the seq, please stop with the hate.


Yeah "calm down with the personnal stuff" was a good point about this sequencer.
LeCCComte
Sorry guys, don't want to ruin this thread. Keep going.
SunSpots
I would vote for the same selection of quantization/scales as the metropolis. then whatever else you out in there would be nice. I don't know anything about scala.
Crandall1
SunSpots wrote:
I would vote for the same selection of quantization/scales as the metropolis. then whatever else you out in there would be nice. I don't know anything about scala.


I was joking with Adam today that if we consider each note of the scale a bit, and scales as 12-bit words, there's 4096 possible scales in 12-TET. We could, theoretically, put all of them in there. But of course many of them won't be useful; most would be downright stupid. There's about 25 that are commonly used (more or less the selection in the current Metropolis software) and another 40 or so that are used infrequently.

But it'd be kind of funny, from a complete-failure-of-uX kind of standpoint. "Was Half Diminished #2356 or #1172?"

Not funny "ha ha" though. More like funny "Sling Blade."
nidas
Are there or could there be any kind of arpeggiator in this?
juvation
ladies and gents, i was the guy who suggested the jack field move to the top (a la Rene and Metropolis, et al), and didn't much like the tone of the resulting conversation.

BUT i bought a Seq-1 anyway, and certainly appreciate the receptiveness to feedback and feature suggestions for what is already the most capable sequencer in Euro.

@needstochill, there has been no personal content in this thread, whatsoever.
VanEck
Concerning the random LFO, I think it might be interesting if an even length was programmed and an odd cycle length was selected. Might yield interesting rhythmic results... or might sound like total ass. Hard to call. The thought is intriguing, and I know I have programmed similar odd timings of LFO's in software like Massive as well as with modules like PEG and such... just not sure how it would translate to the Seq 1.

Concerning scales and quantizing, I would say whatever is more user friendly, quick to program. There are more than plenty deep sequencers and quantization modules out there capable of a million different scales and such. Seq 1 has a good workflow. I'd say whatever prospective features that jive best with work flow should take precedence over the complex and cumbersome ones.

As much as I love options and features... I hate menu diving and feature overload. If I wanted limitless possibilities, I'd stick with programming on a computer. When it comes to modular, I want to be able to work fast and efficiently without getting lost in menus or needing to pull up a manual for every move I make. thumbs up
flo
psyclone001 wrote:
I would actually be quite happy at this stage with just transposition of preset patterns up/down in semitones. I have programmed a bunch of patterns in D# Phrygian for a track I was working on, and now just want transpose down 1 semitone to D Phrygian. Only option at the moment is to copy the pattern, then shift manually all notes down 1 semitone. There is a 'transpose' modulation destination but haven't figured out how to send a reliable signal to that cv input to control semitone up/down transposition of the whole pattern hmmm.....


For immediate remedy, why not tune your oscs down 1 semitone for that particular track? Just for now of course, I want transposition in the Seq 1 just as anybody else obviously... thumbs up
psyclone001
flo wrote:
psyclone001 wrote:
I would actually be quite happy at this stage with just transposition of preset patterns up/down in semitones. I have programmed a bunch of patterns in D# Phrygian for a track I was working on, and now just want transpose down 1 semitone to D Phrygian. Only option at the moment is to copy the pattern, then shift manually all notes down 1 semitone. There is a 'transpose' modulation destination but haven't figured out how to send a reliable signal to that cv input to control semitone up/down transposition of the whole pattern hmmm.....


For immediate remedy, why not tune your oscs down 1 semitone for that particular track? Just for now of course, I want transposition in the Seq 1 just as anybody else obviously... thumbs up

Not that easy unfortunately. I am sending various signals to my oscs simultaneously by different sequencers etc. so obviously tuning up/down osc's puts out all my other sources by that amount. The immediate remedy for me at the moment is a quantizer for the seq1 which works fine for now thumbs up
Crandall1
VanEck wrote:

As much as I love options and features... I hate menu diving and feature overload. If I wanted limitless possibilities, I'd stick with programming on a computer. When it comes to modular, I want to be able to work fast and efficiently without getting lost in menus or needing to pull up a manual for every move I make. thumbs up


Yeah, and that's why some things are kind of a puzzle. Ideally, we want everything to be a button push away; we're trying to keep everything that is useful to live performance at a single step from the front. So transposition/root note will be a front-panel one-push affair. (We do have that handy keyboard right on the panel!) Scales, since they're not something you'll need to change on the fly during a performance, or really at all once you've selected what you're using for a particular pattern, can be down a bit.

It's an interesting exercise, I'll say that much. And the feedback here is incredibly valuable.
tony d
Just wanted to chime in and express how awesome i think this open discussion with Audio Damage is.I don't own or honestly have a need for this sequencer but i have been following this thread because i am just very impressed with the way AD is open to these feature requests and actually implementing them.

I have a buddy who is starting to do research on putting a system together so i will definitely have him check seq1 out.
Bogus
VanEck wrote:
As much as I love options and features... I hate menu diving and feature overload. If I wanted limitless possibilities, I'd stick with programming on a computer. When it comes to modular, I want to be able to work fast and efficiently without getting lost in menus or needing to pull up a manual for every move I make. thumbs up


Yeah menus can suck the creativity out of a patch quick, though that's inevitably what you'll wrestle with working a sequencer in this weight class. For me at least, as I'm getting more comfortable with the Sequencer 1 and it's menu layout, the speed at which I'm able to manipulate it has been increasing dramatically.
studionebula
SunSpots wrote:

Suggestion 2: When I am in the mode that shows CV1,2, and 3 I can see the cv value I change. That's all fine and good, it works as expected. However when I switch to another step, it visually shows the value from the step I *last* edited. That is if I change step 1 to 500, the display shows 500 no matter what step I select until I turn the knob. Once I turn the knob it seems to reset to the steps value... that's okay I guess... not a huge deal but would be slicker and more easy to understand if the display changed when I clicked on the next step, to show that step's value and not the value from the last edited step.


I am unable to reproduce this problem. The CV displays appear to update correctly. Are other people observing this behavior?
Bogus
studionebula wrote:
SunSpots wrote:

Suggestion 2: When I am in the mode that shows CV1,2, and 3 I can see the cv value I change. That's all fine and good, it works as expected. However when I switch to another step, it visually shows the value from the step I *last* edited. That is if I change step 1 to 500, the display shows 500 no matter what step I select until I turn the knob. Once I turn the knob it seems to reset to the steps value... that's okay I guess... not a huge deal but would be slicker and more easy to understand if the display changed when I clicked on the next step, to show that step's value and not the value from the last edited step.


I am unable to reproduce this problem. The CV displays appear to update correctly. Are other people observing this behavior?


Yes, this happens on mine as well
flo
Jep, here too... Changes as soon as you touch the knob...
Crandall1
Adam's able to reproduce it. I talked him through the steps. Working on that fix right now.
studionebula
Bogus wrote:

Yes, this happens on mine as well


Thanks. With the aid of Chris and a second cup of coffee, I now see the problem. eek!
Slomen
Happens here as well!

EDIT: Im a slow poster, sorry very frustrating
Bogus
Several patches have left me wanting the ability to shift sequences on the pattern grid. For instance I might write a riff that sounds like the "1" is on step 7, so I'd like to be able to move it backwards 6 steps to align the perceived on beat with the first step on the sequencer.
studionebula
Bogus wrote:
Several patches have left me wanting the ability to shift sequences on the pattern grid. For instance I might write a riff that sounds like the "1" is on step 7, so I'd like to be able to move it backwards 6 steps to align the perceived on beat with the first step on the sequencer.

Yes indeed. It's been mentioned here previously. It's on the to-do list.
Bogus
studionebula wrote:
Bogus wrote:
Several patches have left me wanting the ability to shift sequences on the pattern grid. For instance I might write a riff that sounds like the "1" is on step 7, so I'd like to be able to move it backwards 6 steps to align the perceived on beat with the first step on the sequencer.

Yes indeed. It's been mentioned here previously. It's on the to-do list.


w00t
djempirical
Crandall1 wrote:
(I will not even attempt to hide my personal disdain for such tomfoolery.


I for one would be disappointed if you were to do so.
SunSpots
Any eta on this next magic update? smile
studionebula
SunSpots wrote:
Any eta on this next magic update? smile


I'm coding as fast as I can. There are some fun problems to solve in order to build fun new features. hyper

I'd say after Thanksgiving, but in plenty of time for Kwanzaa.
psyclone001
Thanksgiving?
Can I have an Aussie date translation? lol
Oh and thanks for giving thumbs up
Barlov
Thursday, November 27
Bogus
studionebula wrote:
SunSpots wrote:
Any eta on this next magic update? smile


I'm coding as fast as I can. There are some fun problems to solve in order to build fun new features. hyper

I'd say after Thanksgiving, but in plenty of time for Kwanzaa.


Mr. Green

this is exciting news, thanks for the tease Adam
keef321
Another new owner of a Sequencer 1 here. Loving it for rythmic results, a lot packed in, I can see this being the main brain of my system.

So onto a little feature request that I think would be cool. It would be great if for example on CV1 with it set to LFO, that we could change the LFO shape and speed per step. This would be awesome, as it would allow you to have a NI Massive style performer modulator, all in synch, opening up loads of crazy possibilities.

My fingers are crossed, very tightly!!!
studionebula
keef321 wrote:
So onto a little feature request that I think would be cool. It would be great if for example on CV1 with it set to LFO, that we could change the LFO shape and speed per step. This would be awesome, as it would allow you to have a NI Massive style performer modulator, all in synch, opening up loads of crazy possibilities.


'Fraid that qualifies as more than a "little" feature addition. dizzy

Not that it isn't a good suggestion, mind you. We intend to expand the modulation features in the future, but how exactly is up in the air. One thing I've thought about is adding a sort of programmable ramp option, so that the control CVs could slide from one value to the next rather than jumping. This would be like the existing slide feature of the pitch CV, but would let you choose the slide time and perhaps the curvature of the slide per step. Hence it would be somewhat similar to what you suggested, but it would be independent of the LFOs.
Ras Thavas
studionebula wrote:
...We intend to expand the modulation features in the future, but how exactly is up in the air. One thing I've thought about is adding a sort of programmable ramp option, so that the control CVs could slide from one value to the next rather than jumping. This would be like the existing slide feature of the pitch CV, but would let you choose the slide time and perhaps the curvature of the slide per step. Hence it would be somewhat similar to what you suggested, but it would be independent of the LFOs.


This please along with the 1V1Oct option for the control cv outputs!
flo
Another feature request: it would be great if copy/paste could be used to copy measures instead of patterns only somehow. I sometimes like to start with 1 bar and then copy to a second bar and change just a few little things there... Seems obvious but as far as I see it's not possible ATM.

Pretty please hihi Guinness ftw!
keef321
studionebula wrote:
keef321 wrote:
So onto a little feature request that I think would be cool. It would be great if for example on CV1 with it set to LFO, that we could change the LFO shape and speed per step. This would be awesome, as it would allow you to have a NI Massive style performer modulator, all in synch, opening up loads of crazy possibilities.


'Fraid that qualifies as more than a "little" feature addition. dizzy

Not that it isn't a good suggestion, mind you. We intend to expand the modulation features in the future, but how exactly is up in the air. One thing I've thought about is adding a sort of programmable ramp option, so that the control CVs could slide from one value to the next rather than jumping. This would be like the existing slide feature of the pitch CV, but would let you choose the slide time and perhaps the curvature of the slide per step. Hence it would be somewhat similar to what you suggested, but it would be independent of the LFOs.


The programmable ramp option sounds interesting, I think I can visualise this. Would this provide similar results to say ramp up, ramp down shapes etc, similar to the envelope outputs on the 4ms PEG? (not got that module, but on my wish list).

Either way, looking forward to seeing how the sequencer develops. I primarily got this module for it's sequencer capabilities, but synched modulation is a huge bonus smile Will still keep dreaming about my NI Massive Style performer in Euroland though Om
keef321
flo wrote:
Another feature request: it would be great if copy/paste could be used to copy measures instead of patterns only somehow. I sometimes like to start with 1 bar and then copy to a second bar and change just a few little things there... Seems obvious but as far as I see it's not possible ATM.

Pretty please hihi Guinness ftw!


+1 totally agree on this one, I was trying to figure out how to do this for ages. I even started searching this thread to see if it was a bug.
nblazer201
http://www.orthogonaldevices.com/er-101

This has all the copy paste and snapshot goodness that a sequencer meant for live play could ever ask for.

Maybe u need a backup seq?


flo
Seriously nblazer, stop posting in this thread not this shit again
Bogus
flo wrote:
Another feature request: it would be great if copy/paste could be used to copy measures instead of patterns only somehow. I sometimes like to start with 1 bar and then copy to a second bar and change just a few little things there... Seems obvious but as far as I see it's not possible ATM.

Pretty please hihi Guinness ftw!


I'm fairly certain that Adam and Chris said that feature is on the list for the next update
nblazer201
flo wrote:
Seriously nblazer, stop posting in this thread not this shit again


This is a public forum not a promotional circle jerk.
simply mentioning a sequencer with the features u guys want is out and cheaper and called an ER 101, that is a totally fair post.

It is better to actually buy a module that has the features you guys want instead of banking on promises from the manufacturers. The ER-101 is built ground up to make the workflow of arranging sequences a breeze with really excellent copy, paste, and snapshot features.

seriously, everything you guys are asking on the "wish list" already exists here

ER-101

http://www.orthogonaldevices.com/er-101



Not saying the seq-1 is bad, looks like a great mod, but for really easy copy past and snapshot , and 4 tracks, er-101 is the way to go.

The point of this forum is to educate each other, not to be promotions.
usw
You're totally off the line, the er-101 doesn't need such an embarrassing promotion, especially in a thread used by chriss and Adam to communicate with their users confused
narwhal
Russian Roulette
rico loverde
nblazer201 wrote:
flo wrote:
Seriously nblazer, stop posting in this thread not this shit again


This is a public forum not a promotional circle jerk.
simply mentioning a sequencer with the features u guys want is out and cheaper and called an ER 101, that is a totally fair post.


The point of this forum is to educate each other, not to be promotions.


typical trollish behavior, he pokes and pokes and pokes and then when people finally bite back he can't understand why. Start your own damn thread about "nblazers favorite sequencer" and let CR and the people who actually use and are interested in this seq be...

yes its a public forum but that being said people generally have a little bit of respect around here and its painfully obvious that you have some sort of issue with CR.

plenty of manufacturers promote their wares here i really don't get why your giving these guys so much shit.

yet another person to use the "ignore" button on
nblazer201
usw wrote:
You're totally off the line, the er-101 doesn't need such an embarrassing promotion, especially in a thread used by chriss and Adam to communicate with their users confused


Really?
I think it is embarrassing to ship a $700 sequencer without what most people would call sequencer essentials.

Why don't they just set up their own forums?
This is the general eurorack discussion forum where modules are compared against each other all the time.

The point being, many users here are asking for more advance copy paste features, and this is a forum for eurorack users, not audio damage, and I am very simply saying that you guys don't have to wait on promises, there already exists what you want.

The ER-101 has all of that. Make your own choices I am just throwing some knowledge out there.


Barlov
Play Him Off, Keyboard Cat.
jdkee
not this shit again

There is no why.
Crandall1
Yes, the paste-in-place feature (what we call the "copy from one measure to another" thing requested above) is in v1.1, coming shortly.

Regarding nblazer, he was amusing in the "design" thread, but he has nothing to offer to this discussion; I've long since ignored him, and I suggest you do the same. Unless you feel like helping him learn the bassline to "Baby I Got Your Money," that is. He is "kinda musicly retarted" [sic] but as we all know, "best way to learn is immitation" [sic]

EDIT: I just looked at the task list for 1.1, and actually the paste-in-place feature might not be in 1.1. Adam has moved it to the "Bonus Round" since last I looked, which means one of the other features is taking longer than he expected. I'll poke him with something sharp and see if we can't get that in this round.

FURTHER EDIT: On reflection, I know what he's going to tell me. He's going to say "well, the update will take longer, because this isn't as easy to implement as you seem to think." So, how about it? Would you like v1.1 sooner, but without paste-in-place (which will then definitely go to v1.2) or would you like to wait what would probably be a couple days but possibly a week, and have it in v1.1?
Bogus
I'd prefer 1.1 sooner to later without paste-in-place, if the code jockey says it's best to wait I wouldn't gas that fire
nblazer201
Crandall1 wrote:
Yes, the paste-in-place feature (what we call the "copy from one measure to another" thing requested above) is in v1.1, coming shortly.

Regarding nblazer, he was amusing in the "design" thread, but he has nothing to offer to this discussion; I've long since ignored him, and I suggest you do the same. Unless you feel like helping him learn the bassline to "Baby I Got Your Money," that is. He is "kinda musicly retarted" [sic] but as we all know, "best way to learn is immitation" [sic]

EDIT: I just looked at the task list for 1.1, and actually the paste-in-place feature might not be in 1.1. Adam has moved it to the "Bonus Round" since last I looked, which means one of the other features is taking longer than he expected. I'll poke him with something sharp and see if we can't get that in this round.

FURTHER EDIT: On reflection, I know what he's going to tell me. He's going to say "well, the update will take longer, because this isn't as easy to implement as you seem to think." So, how about it? Would you like v1.1 sooner, but without paste-in-place (which will then definitely go to v1.2) or would you like to wait what would probably be a couple days but possibly a week, and have it in v1.1?


Ok wow, you just made this incredibly personal.

I was suggesting picking up an ER-101 in combination to the sequencer-1 to fill in the gaps.
I am pretty sure you are retarded for taking 10 years to make a sequencer with out basic copy and paste.

"We wish we were kidding when we say that we've been working on this product for almost 10 years. But we aren't. Sequencer 1 is the culmination of a lot of thought about how we'd like a modular sequencer to work, and we are incredibly proud of the result. " .... fucking idiot
http://www.audiodamage.com/hardware/product.php?pid=ADM06

To all the rest:
It is NOT wise to trust "promises" of a mediocre and slow developer. You will be waiting many many patches and promises
If you want:
- 4-track sequencer
- stepped and smooth voltage transitions
- each track has 3 outputs: 2 CVs + 1 gate
- each track has its own adjustable loop points
- each track contains up to 100 patterns and each pattern can contain up to 100 steps
- each step can be individually adjusted to have 0-99 clock cycles in duration
- each gate can be individually adjusted to have 0-99 clock cycles in duration with or without ratcheting
- configure each track to output gates or triggers
- configure each track to have its own clock multiplier (1x to 99x)
- CVs are chosen (indexed) from voltage tables of which there are 2 per track (A & B)
- 8 built-in and 8 user reference voltage tables for initializing the track tables
- voltage tables are user-editable and have 100 entries per table
- voltages between 0.000-8.192V at 2mV increments can be dialed in
- each voltage table can be configured to use note display or numeric display
- smoothing can be enabled for individual steps, entire patterns and/or entire tracks
- smoothed transitions are NOT simply slews but are adjusted to match the current tempo in real-time
- hold feature (complete double-buffering of device state) allows you to edit-and-commit on the beat while the sequencer is running
- while in hold mode, committing changes to a running sequence can be either immediate or quantized to the beat
- reset can be either immediate or quantized to coincide to with the ending of the current track, pattern, or step
- stores up to 16 snapshots of the state of the entire device
- arbitrary insert/delete of patterns/steps with clipboard style copy/paste
- math button allows you to specify a mathematical operation to apply to a step, a pattern or a track.
- note repeat (aka ratchet) any step
- shuffle (aka swing) any step
- expansion port
- last saved snapshot is loaded automatically on power-up
- firmware upgradeable via USB



It would take another decade for the sequencer-1 to implement 1/5th of these features

EDIT: The ODB fucking rocks u tool
Muff Wiggler
ok shit for brains, it's officially time for you to stop trolling.
ether
Someone's on a fast track to getting themselves banned.

Ancient Chinese Proverb : Those making awesome sequencers shouldn't be interrupted by twats, like, ever.
granville
Bogus wrote:
I'd prefer 1.1 sooner to later without paste-in-place, if the code jockey says it's best to wait I wouldn't gas that fire


+1
newgreyarea
Yikes! This kid has definitely made me not want to even consider that other sequencer. Does he work for that company?

Anyway, I'm still loving my Seq1. Self modulating the Modes with an internal LFO is ace! Sending Accent out to trigger another synth is ace as well! I still don't feel fast with it in the way I do with my Analog Four. I think it's the long hold to select steps.

Great module!
usw
please, don't drag innocent people into this wink
Crandall1
Please don't hold the nblazer nonsense against Brian. The ER-101 is a work of art. Obviously, the ER-101 and Seq1 are very different approaches to the problem, and you'll end up with very different results. (Which goes to show, when you have the same goal of putting notes in a row, how the UI can drastically affect workflow.)

Just as a comparison, the main ER-101 demo, where Brian programs in the Axel F melody, well, you can get that sequence in about as fast as you can play it in Seq1. Point to Seq1. However, the fucking amazing modulations and melody transformations he does later in the Axel F video are impossible on Seq1. So point firmly to the ER-101. I personally look at it this way: the ER-101 is very much a left-brained sequencer, and will appeal to left-brained people, while Sequencer 1 is extremely right-brained. Good to have variety in life.

nblazer's goal in this is not to engender an honest conversation about the relative merits, and why you would need either or both. His goal is to get attention, and get back at me for stomping on him so thoroughly in the "design" thread. He doesn't own an ER-101, obviously. Neither does he own a Metropolis. And I wouldn't sell him a Sequencer 1 if he showed up at my door with cash.

So, as I said, just hit that "ignore" button and let him wither. No attention = no posts. Mike and Brian and I had a nice conversation about him last night (yeah, another thing he doesn't seem to understand: this entire business is only about 35 people, and we're all friends, for the most part) and I asked Mike not to ban him. We'll see how it plays out, I guess. But if he continues to troll this thread just for the lulz, Mike will do what he will do. He has less patience than me, and it's his site.
Jimmersound
newgreyarea
"Ignore" hit.
Didn't mean to drag the "innocent people" in. I've into really looked into that sequencer and they way he was talking about it came off as really shitty promotion.

Back to the sequencer at hand! I suppose I should go get a microSD adapter if that update is gonna be dropping soon.

I could definitely see the need for 2 of these in one performance system.

Maybe after I get a new case!
SunSpots
wait what is required to update?
Crandall1
SunSpots wrote:
wait what is required to update?


It's pretty easy. All you need is a microSD to normal SD adaptor.

I made a tutorial video, here:

keef321
Crandall1 wrote:
Yes, the paste-in-place feature (what we call the "copy from one measure to another" thing requested above) is in v1.1, coming shortly.

Regarding nblazer, he was amusing in the "design" thread, but he has nothing to offer to this discussion; I've long since ignored him, and I suggest you do the same. Unless you feel like helping him learn the bassline to "Baby I Got Your Money," that is. He is "kinda musicly retarted" [sic] but as we all know, "best way to learn is immitation" [sic]

EDIT: I just looked at the task list for 1.1, and actually the paste-in-place feature might not be in 1.1. Adam has moved it to the "Bonus Round" since last I looked, which means one of the other features is taking longer than he expected. I'll poke him with something sharp and see if we can't get that in this round.

FURTHER EDIT: On reflection, I know what he's going to tell me. He's going to say "well, the update will take longer, because this isn't as easy to implement as you seem to think." So, how about it? Would you like v1.1 sooner, but without paste-in-place (which will then definitely go to v1.2) or would you like to wait what would probably be a couple days but possibly a week, and have it in v1.1?


Me personally I would prefer to wait longer and get it in v1.1, as it pretty core to the way I work. Either way though, it's great to know that it will be implemented. Will make it an awesome sequencer for me.
studionebula
Crandall1 wrote:
Yes, the paste-in-place feature (what we call the "copy from one measure to another" thing requested above) is in v1.1, coming shortly.

[...]

FURTHER EDIT: On reflection, I know what he's going to tell me. He's going to say "well, the update will take longer, because this isn't as easy to implement as you seem to think." So, how about it? Would you like v1.1 sooner, but without paste-in-place (which will then definitely go to v1.2) or would you like to wait what would probably be a couple days but possibly a week, and have it in v1.1?


Since this is a feature I want also, I dispelled my post-Turkey-Day fog with an extra cup of coffee and banged out the code. Copying & pasting measures within a pattern is now definitely a part of the forthcoming v1.1 update. Coffee Addiction FTW

Had I not done this I probably would have spent much of the day looking at Black Friday ads, so the schedule (which is sort of an abstract notion, honestly) will not be affected.
Bogus
studionebula wrote:
Copying & pasting measures within a pattern is now definitely a part of the forthcoming v1.1 update. Coffee Addiction FTW

Damn... Props
kuxaan-sum
studionebula wrote:
Crandall1 wrote:
Yes, the paste-in-place feature (what we call the "copy from one measure to another" thing requested above) is in v1.1, coming shortly.

[...]

FURTHER EDIT: On reflection, I know what he's going to tell me. He's going to say "well, the update will take longer, because this isn't as easy to implement as you seem to think." So, how about it? Would you like v1.1 sooner, but without paste-in-place (which will then definitely go to v1.2) or would you like to wait what would probably be a couple days but possibly a week, and have it in v1.1?


Since this is a feature I want also, I dispelled my post-Turkey-Day fog with an extra cup of coffee and banged out the code. Copying & pasting measures within a pattern is now definitely a part of the forthcoming v1.1 update. Coffee Addiction FTW

Had I not done this I probably would have spent much of the day looking at Black Friday ads, so the schedule (which is sort of an abstract notion, honestly) will not be affected.


Sweet!
What better way to spend BFSD.

I have lost track of everything in this next update.
Was the task list posted?
burnn_out!
As a former user of the ER-101, I found it extremely difficult to wrap my head around. A module could offer all that's under the sun but if the UI sucks , it's worthless. The AD seq1I believe bridges enough gaps even with short comings to be to the most useful sequencer in euro
Crandall1
We haven't posted an actual list of what's coming in 1.1. I'll just repeat what we _have_ said will be in it, in various posts either here or on our Twitter accounts:

1. The "Elektron" programming mode, where the pitch CV is held from gate to gate. This is probably the single most requested thing. This is selectable per-patch (you'll still be able to "free" the pitch CV if you'd like, so that it is always live, and this is stored per pattern, but its default operation now will be to be held from gate to gate.)

2. The paste-in-place mode Adam mentioned. He finished this entirely and put it in place today. So that's done. I haven't fully tested it yet, though.

3. LED chasing. The keyboard LEDs show the note being played when the unit is not in an edit mode, and is playing.

4. About 15 bugs (some mentioned here, some nobody but us have seemed to find) fixed. The main interest here will be where hitting one of the live ratchet buttons while holding a repeat button would cancel the repeats. This doesn't occur any more, so you can hold a repeat, and ratchet it at will. The other bug that was fixed that most owners know about is the one where CV values on the screen aren't updated when going to edit a new step. That is fixed.

So all that is done, and much of it is tested and ready to go. There is one final feature addition we're working on now, and it is about 3/4 done, according to Adam's chart. We haven't really mentioned it here, though, and I'll just continue to let it be a surprise.
SunSpots
no knob recording? waah
Crandall1
Not in this update, no. We said that wouldn't come in this one some time back, though. It's on the list.
Slomen
Sounds very good! Good job Adam and Chris applause
juvation
thanks for Elektron mode
keef321
[quote="studionebula"]
Crandall1 wrote:
Yes, the paste-in-place feature (what we call the "copy from one measure to another" thing requested above) is in v1.1, coming shortly.

Since this is a feature I want also, I dispelled my post-Turkey-Day fog with an extra cup of coffee and banged out the code. Copying & pasting measures within a pattern is now definitely a part of the forthcoming v1.1 update. Coffee Addiction FTW

Had I not done this I probably would have spent much of the day looking at Black Friday ads, so the schedule (which is sort of an abstract notion, honestly) will not be affected.


Thanks guys!!
flo
Good list! Looking forward to that update.

One bug I've noticed recently is that ties do sometimes not tie, but retrigger on the consecutive steps... Randomly more or less as far as I can see.
Crandall1
flo wrote:
One bug I've noticed recently is that ties do sometimes not tie, but retrigger on the consecutive steps... Randomly more or less as far as I can see.


Okay. I verified this by the expedient of making a 2-step pattern, where the first step is "TIE" length and the second is 50%, and sitting there and listening to it for half an hour. Which was, let me tell you, incredibly awesome! A+++ Would listen again!

Added it to the bug list.
flo
lol Glad I'm not going bonkers and you could recreate it. It happened on standard 16 and 32 step patterns in my case, ca one third or so of all hits I would say. Noticed while preparing for a live gig but it gave some nice variation in the end hihi applause

Wasn't sure at first whether one needs to program the gate on the subsequent steps, but it certainly needs to be there...

Thanks mate! Guinness ftw!
studionebula
flo wrote:
lol Glad I'm not going bonkers and you could recreate it.

I'm having such a Monday-ish Monday. First my main computer completely screws itself up, probably requiring me to reinstall everything from scratch, and then you guys find this bug. Dead Banana
Bogus
Yeah I've been getting that no tie bug as well, it's good to know it'll get changed!
newgreyarea
Does this thing have a clock divider in it? I can't seem to find it. Must be thinking of another sequencer. Would be cool to have though. Then I could leave it perma-patched to the fastest out on my RCD and divide down as needed.
Bogus
newgreyarea wrote:
Does this thing have a clock divider in it? I can't seem to find it. Must be thinking of another sequencer. Would be cool to have though. Then I could leave it perma-patched to the fastest out on my RCD and divide down as needed.


It has no dedicated clock divider circuit built in
Crandall1
Bogus wrote:

It has no dedicated clock divider circuit built in


That's coming. I actually wanted it in this update, but not a single person has asked for it (here) until now, so we decided to load v1.1 with stuff that people had asked for.

It'll get gearboxes on both the input and the output; this will come sooner rather than later, as I want this feature badly, and I have a little bit of pull with the company. We'll have 48 and 24ppq in, in addition to the current 1 clock per step, and clock that bypasses the swing out, as well as 24 and 48ppq out and all the usual divisions.

Now, that said, you can _EASILY_ use one (or all three) of the LFOs as clock dividers. The 1/8th pulse is perfect for this, and you can get pretty whacky with your divisions, and they don't respond to the swing.
newgreyarea
Crandall1 wrote:
Bogus wrote:

It has no dedicated clock divider circuit built in


That's coming. I actually wanted it in this update, but not a single person has asked for it (here) until now, so we decided to load v1.1 with stuff that people had asked for.

It'll get gearboxes on both the input and the output; this will come sooner rather than later, as I want this feature badly, and I have a little bit of pull with the company. We'll have 48 and 24ppq in, in addition to the current 1 clock per step, and clock that bypasses the swing out, as well as 24 and 48ppq out and all the usual divisions.

Now, that said, you can _EASILY_ use one (or all three) of the LFOs as clock dividers. The 1/8th pulse is perfect for this, and you can get pretty whacky with your divisions, and they don't respond to the swing.



thumbs up
I'll dick around with the LFO as a clock divider. See what weirdness I can come up with.
Bogus
Something I noticed with ratcheting that could be benifit a change: with a double ratchet engaged there is no difference in output between any gate length setting above 50%, for triple it's 34% and quadruple 25% (as you might imagine). It would be great if when a note is set to ratchet it's gate length setting becomes more precise so as to have 100% be the maximum length for the ratchets thus doubling, tripling and quadrupling the available lengths for ratcheted notes. I hope that makes sense!

Also I'm glad to hear that a clock divider will soon be built in! That's going to save me a little money (money I promise I'll spend on another Audio Damage module).
VanEck
Doing some more Seq1 LFO experimenting tonight with a rhythmic noise track, and an idea popped in my head. Hard to explain, but ill try...

Would it be possible to have the LFO's also "repeat" whenever the sequencer repeats? For example, you have an LFO going that is a 16 step sine wave. You have the sequencer do a 4 step repeat, and when that occurs, the LFO also repeats where the voltage was at that step in the sequence.

Or perhaps a better way to explain, you have a random step LFO going set for 1 step... its chugging along spitting out random voltages every step, then you hit the repeat 4 function on the step seq (or via CV), and then the LFO also repeats the last 4 random LFO steps it spit out over and over while the repeat is active.

Basically it would not just be a repeat of the step sequencer, but also a LFO looper as well. Then when the repeat is off, the LFO picks up where the voltage would have been just like the step sequencer does, so everything is still on track. This, to me at least, would be incredibly useful.

I imagine this would require some sort of buffering to accomplish, but I figure there already is some sort of buffering going on anyhow when you are using repeat on the sequence itself... perhaps it is possible to incorporate the LFO's into that as well?
muffstuff
VanEck wrote:
Doing some more Seq1 LFO experimenting tonight with a rhythmic noise track, and an idea popped in my head. Hard to explain, but ill try...

Would it be possible to have the LFO's also "repeat" whenever the sequencer repeats? For example, you have an LFO going that is a 16 step sine wave. You have the sequencer do a 4 step repeat, and when that occurs, the LFO also repeats where the voltage was at that step in the sequence.

Or perhaps a better way to explain, you have a random step LFO going set for 1 step... its chugging along spitting out random voltages every step, then you hit the repeat 4 function on the step seq (or via CV), and then the LFO also repeats the last 4 random LFO steps it spit out over and over while the repeat is active.

Basically it would not just be a repeat of the step sequencer, but also a LFO looper as well. Then when the repeat is off, the LFO picks up where the voltage would have been just like the step sequencer does, so everything is still on track. This, to me at least, would be incredibly useful.

I imagine this would require some sort of buffering to accomplish, but I figure there already is some sort of buffering going on anyhow when you are using repeat on the sequence itself... perhaps it is possible to incorporate the LFO's into that as well?


+1
Crandall1
The LFOs themselves are wavetables (except, obviously, the random ones), so this should be possible in theory, no buffering necessary. We'll have to explore and test, though, and it strikes me as one of those things that sounds simple, but turns out to be really fuckin' hard.

That aside, a quick update: Adam had a major computer failure last week; the development machine's main hard drive went tits up. So this put us back a couple days, for obvious reasons. All is rebuilt and back on track now, though, and he's busy finishing up the v1.1 update.
studionebula
Getting caught up on some stuff here... As Chris said, I had a major computer failure recently and lost much of last week to getting that straightened out.

Bogus wrote:
Something I noticed with ratcheting that could be benifit a change: with a double ratchet engaged there is no difference in output between any gate length setting above 50%, for triple it's 34% and quadruple 25% (as you might imagine).


That sounds like a pretty simple math mistake or something similar. I'll investigate. Thanks.
studionebula
VanEck wrote:

Or perhaps a better way to explain, you have a random step LFO going set for 1 step... its chugging along spitting out random voltages every step, then you hit the repeat 4 function on the step seq (or via CV), and then the LFO also repeats the last 4 random LFO steps it spit out over and over while the repeat is active.

Basically it would not just be a repeat of the step sequencer, but also a LFO looper as well. Then when the repeat is off, the LFO picks up where the voltage would have been just like the step sequencer does, so everything is still on track. This, to me at least, would be incredibly useful.

I thought about this when I built the repeat stuff. I'll freely admit that I decided to not attempt making the LFOs work as you describe because it seemed difficult at the time, and getting the LFOs to work in the manner that you currently see proved to be more time-consuming than I expected. So yes, I wimped out on that one. Smacked in the head with a trout

VanEck wrote:

I imagine this would require some sort of buffering to accomplish, but I figure there already is some sort of buffering going on anyhow when you are using repeat on the sequence itself... perhaps it is possible to incorporate the LFO's into that as well?

It's possible, certainly. The trick would be to keep track of the state of the LFOs at each step, so that they can be reset to that state when a repeat happens. I agree that it would indeed be a useful feature, although I can also imagine situations in which having it work the way it currently does is also useful, which means introducing yet another pattern-level parameter.

So, I'll put it on the to-do list, but it will definitely not be part of the upcoming v1.1 update.
studionebula
Crandall1 wrote:
The LFOs themselves are wavetables (except, obviously, the random ones), so this should be possible in theory, no buffering necessary. We'll have to explore and test, though, and it strikes me as one of those things that sounds simple, but turns out to be really fuckin' hard.

Actually all of the LFO functions are calculated on the fly, rather than using wavetables. There are several reasons for this but they're somewhat beside the current point, which is yes, it's theoretically possible, but more difficult than I wish to tackle for v1.1. Whomever said "the devil is in the details" could easily have been talking about embedded programming. evil
Ras Thavas
Agreed. When I first read this suggestion I thought there'd be times I'd want to loop both cv/gate and the LFOS, and other times I'd want the LFO's to continue un-looped. And now that it's been brought up, it might be nice to just loop the LFO's and not the CV/Gate info too. I'll trust AD with the difficult job of figuring out the right balance of features vs complexity, as Seq 1 is currently a pleasure to use.

studionebula wrote:
...The trick would be to keep track of the state of the LFOs at each step, so that they can be reset to that state when a repeat happens. I agree that it would indeed be a useful feature, although I can also imagine situations in which having it work the way it currently does is also useful, which means introducing yet another pattern-level parameter...
VanEck
studionebula wrote:

It's possible, certainly. The trick would be to keep track of the state of the LFOs at each step, so that they can be reset to that state when a repeat happens. I agree that it would indeed be a useful feature, although I can also imagine situations in which having it work the way it currently does is also useful, which means introducing yet another pattern-level parameter.

So, I'll put it on the to-do list, but it will definitely not be part of the upcoming v1.1 update.


Awesome! thumbs up thumbs up thumbs up

Yes I agree it would be beneficial to be able to have this enabled or not depending on the situation.
Bogus
studionebula wrote:
Bogus wrote:
Something I noticed with ratcheting that could be benifit a change: with a double ratchet engaged there is no difference in output between any gate length setting above 50%, for triple it's 34% and quadruple 25% (as you might imagine).


That sounds like a pretty simple math mistake or something similar. I'll investigate. Thanks.


Thanks Adam SlayerBadger!
newgreyarea
I'll go ahead an be the guy that doesn't quite get the point of this would be LFO/Repeat feature. I would think that with just the note/gate/LFO repeating and the rest of my patch going all over the place still, that it wouldn't be necessary. A Repeater style module that captures and repeats the final audio output would seem to be more beneficial. . . Something along the lines of Replicant hint hint!
All of for more features so long as the module remains functional and not a massive, menu diving, pile of clump!

thumbs up
Crandall1
I can plainly see that newgreyarea and I are on the same wavelength. :-)
VanEck
newgreyarea wrote:
I'll go ahead an be the guy that doesn't quite get the point of this would be LFO/Repeat feature.


To create rhythms. The same benefits you get from repeating audio, like with Replicant as you mention, but with control voltage instead to create repeating fragments that can create rhythmic chunks of modulation.

newgreyarea wrote:

I would think that with just the note/gate/LFO repeating and the rest of my patch going all over the place still, that it wouldn't be necessary.


Not sure I follow. Having notes and gates going all over the place is something else entirely, and would not give the same results from breaking up low frequency oscillations into structured tempo synchronized repeating segments that can be performed with a touch of a button, or by self patching the Seq 1.

Seq 1 is more than just a sequencer. You can ignore the note sequencing completely and with a little creativity and self-patching, turn it into a powerhouse of time synched modulations and gate sources... a true rhythmic monster. My suggestion was to improve upon that side of it, opening up more possibilities of the repeat and LFO features, and really isn't related to the "notes and gates going all over" element of it.

newgreyarea wrote:
A Repeater style module that captures and repeats the final audio output would seem to be more beneficial. . . Something along the lines of Replicant hint hint!


While I would like to see Replicant as a module, this type of functionality already exists to some degree in the form of the Tyme Sefari, or the Phonogene, etc... and if those modules were patched with the feature I suggested added to the Seq 1, it would open up a lot potential. I don't think think repeating audio would be "more beneficial" over repeating control voltages. It would be something else entirely, and subjective to the style of music/patching someone is doing, and the other modules in play.

EDIT: For example, think of a sine wave looping at an non-4/4 time signature patched to the cutoff of a filter or something, which you can then self patch the seq1's repeat feature to grab that lfo at random points of that sines cycle and repeat on a 4/4 grid... can easily start creating polyrhythmic modulations. Or looping time synched chunks of the random LFO...
Crandall1
Just a quick stock update. We are totally sold out in our shop of Sequencer 1, so no more direct sales or through Amazon. (All the other modules are currently available, except DubJr, which I'm waiting on panels for.)

I know that Analogue Haven still has a few. I just sent 10 more to Control Brooklyn, so they're in good shape. I think Muff's has one unit left. That's it for North America. I just restocked Alex4, who distribute the European units, many European retailers who were out will have a couple in stock shortly, and those that didn't have any will be getting them soon.

Long story short, they're still available here and there, but going fast. Between AH and Control there's still quite a few available in the US, and European dealers should generally be okay on stock. We just don't have any ourselves.
newgreyarea
Here's a new one. Stepped away from the modular for a couple of days, came back and the Seq1 is no longer giving GATE, ACCENT, RATCHET, REPEAT feedback on the buttons. Those functions are still happening in my sequence but if I select a step it doesn't tell me what's going on anymore.
Not a huge deal and I imagine that a power cycle will fix it but I'm in the middle of something and that's not an option yet.

How close is the update? Should I go hunt down a microSD reader?
Crandall1
Adam just cut me off a line of update about an hour ago. However, there are known problems with it, and I am hosting a synth meet today, so I don't have any time to test it.

That said, the only thing I can suggest is saving the pattern (which, regardless of the state of the LEDs, should just be the programmed note data) and power-cycling.
Bogus
Tell Adam to send it to me I'll beta test!
Crandall1
Monday morning progress update: we're very close. I believe we'll have RC1 today. If one of you has time this afternoon/evening, and would like to pressure-test it, drop me a line at info at audiodamage dot com. I could use an active beta-tester for Seq 1 updates.

(Side note: people are often way more gung-ho about the _concept_ of beta testing than the actuality. If you aren't dead serious on installing it when I give it to you and going through it with a fine-toothed comb trying to break it, and getting back to me in a timely fashion, for basically only the joy of doing so, you'll be happier waiting for the actual release, I think.)
flo
Now that you're getting close, some further wishful thinking hihi

I'd love if there was a way to save an "init" pattern, so that deleted or new patterns will default to that setting...

For example, I sometimes control ADSR level with one of the CV outs, and I have to go through every step first, making sure it's > 0 so the envelope gets through... Could imagine many more situations in which it might be useful.
flo
Also one question that came up lately, the manual is somewhat ambiguous on it: when saving, is strictly only the current, selected pattern safed? Or all changes / new patterns since the last power cycle / last saving? I guess I could test it myself as well but thought asking couldn't hurt...

Thanks so much and cheers! Guinness ftw!
Crandall1
It is only the pattern that is currently live.
flo
thumbs up Thanks! I can see justifications for either way, so it's good to know Guinness ftw!
studionebula
flo wrote:
Now that you're getting close, some further wishful thinking hihi

I'd love if there was a way to save an "init" pattern, so that deleted or new patterns will default to that setting...

Thanks, that's an excellent idea. I suppose the way it would have to be done would be via a special command somewhere, possibly in the Globals pages, which said "save the current pattern as the default."

flo wrote:
Also one question that came up lately, the manual is somewhat ambiguous on it: when saving, is strictly only the current, selected pattern safed?

If there are other points in the manual which need clarification or elaboration or correction, now would be a good time to say so. I'm attempting to finally move the manual out of its "preliminary" state, to go along with the v1.1 update. Yes, it's high time. oops
flo
studionebula wrote:
flo wrote:
Now that you're getting close, some further wishful thinking hihi

I'd love if there was a way to save an "init" pattern, so that deleted or new patterns will default to that setting...

Thanks, that's an excellent idea. I suppose the way it would have to be done would be via a special command somewhere, possibly in the Globals pages, which said "save the current pattern as the default."


Yeah, that's exactly how I was thinking about it! Kinda like DAW init startup states. I like using those hihi

studionebula wrote:
flo wrote:
Also one question that came up lately, the manual is somewhat ambiguous on it: when saving, is strictly only the current, selected pattern safed?

If there are other points in the manual which need clarification or elaboration or correction, now would be a good time to say so. I'm attempting to finally move the manual out of its "preliminary" state, to go along with the v1.1 update. Yes, it's high time. oops


I think that was the only thing that was not entirely clear for me, at least as far as I remember. And even there, the way it is framed now in the manual points in the direction of saving only the life pattern, I just wasn't 100% sure.

And now that I got the attention of you guys, something else that was on my mind lately, I'm not sure whether this would be super simple or mega complicated... Maybe worth a thought for any future firmware version. I'd love if one could select "negative octaves", at least a -1 would be very nice. Could be a problem with quantizers afterwards, but in that case one doesn't have to use it. If one uses VCOs with octave switches, this would come in extremely handy. Not so much needed if there's only a coarse tune anyways... I personally love octave switches Mr. Green

Ha, after writing that last paragraph I quickly checked the manual again and actually nevertheless found another tiny mistake: it's written in the manual that the octaves are numbered 1 - 5, but of course they are actually 0 - 4, which makes much more sense. I'd love them to be -5 - 4 ideally wink

Cheers and thanks again for everything! SlayerBadger!
Crandall1
And now the moment you've all been waiting for: the first major update to Sequencer 1 is now available on the AD site.

Bug Fixes:

-Tied steps sometimes didn't really tie. Fixed.

-CV values (and other things) now displayed correctly in LCD after switching edit step with a button tap.

-Extraneous percent symbol removed from Swing display.

-Pressing and releasing the REP 1/2 or REP 1/4 while holding another REP button would cancel the effect of the first REP button, or vice-versa. This no longer happens.

-Random LFO shapes always started with the same not-particularly-random value. They're more random now.

-The Gate and Accent Length parameters didn't work correctly for steps with ratcheting. Now they do.

Feature Additions:

- "Elektron mode" programming added, as a per-pattern setting. Unit defaults to this mode, where the pitch CV is held from gate to gate, to eliminate the need to program every step's pitch in a legato/long release situation. The original operating mode is available as a per-pattern option menu on the fourth page of the SEQ menu tree.

- Front panel and per-pattern transpose added. When the unit is in playback mode (i.e. when it is not in an edit mode) the keyboard and octave buttons on the front panel can be used to transpose the sequence in real time. This is a per-pattern setting that can be saved. It is available as a new menu item on the first page of the SEQ menu tree.

- Scales/Modes/Tonic quantization added. You can now quantize the pitch of your sequence to a particular scale/mode and tonic. These are per-pattern settings stored with the pattern, and available on the third page of the SEQ menu tree. There are 45 preset scales and 8 user scales. CV transpose input is quantized to the currently selected scale and tonic. Each pattern defaults to chromatic.

- Paste-In-Place added. Use the existing copy and paste functions to copy/paste measures within a pattern, in addition to their normal functionality of copying/pasting entire patterns.

- Chase lights added. When in playback mode, the keyboard LEDs chase the currently playing pitch.

One note: once you've updated your unit to v1.1, if you then decide, for some whacky reason, to go back to 1.0.x, the 1.0.x software will not load patterns saved in v1.1. I can't possibly fathom why (a) you'd want to do this, or (b) it would be a problem, but Adam wants me to mention it, so I'm mentioning it.

Enjoy!

Slomen
w00t

Thanks! You guys are awesome!! we're not worthy
flo
Fucking hell yeah! SlayerBadger! SlayerBadger! SlayerBadger!
sonicmayhem
Awesome update! Esp. the Transpose function smile Im happy now!!
Bogus
v1.1 is one hell of an overhaul, it makes the Seq1 feel like a whole new beast. Great work Adam and Chris!
synthmind
excellent!
Crandall1
Aaaaaaaand... the Sequencer 1 manual has been _finished_ (!!!!) and updated to reflect the changes in v1.1.

Get it here.
SunSpots
cool update. I sold mine, but want to request next update to major on recording options.
record what I play on keyboard
record my knob movements for whatever parameters
go back mode to erase all recording if possible

if this happens, I'll reinvest into this module.

good job on update!
psyclone001
Not sure if it is a cache issue or something but when I download the update it is still the v1.02 download? Weird cause I've tried on 3 different computers seriously, i just don't get it
Crandall1
Oh, Jesus Christ. My bad. I changed the text on the download page but not the link. Refresh the page; fixed now.

Terribly sorry, everyone. It has been a Dayâ„¢ here.
VanEck
Thank you for the measure copy "paste in place". I thought that was how it worked originally and accidentally pasted over the whole pattern I was working on while trying to paste to the second measure last week d'oh!
VanEck
Think I found a potential bug with 1.1

When scrolling through cv input assignments, the parameters you scroll on all seem to take effect even with nothing plugged into the cv input jacks. I don't recall the previous version behaving this way, and would potentially be an issue if performing with it, etc.

Captured a quick video demonstrating this. The video is not public, only those with the link can see it.



Bug? Feature?
ranzen
thats absolutely brilliant! Thanks for the update!
Crandall1
@VanEck: Some (most?) of the CV inputs are multipliers on internal values, and if you're multiplying by zero (which you would be with no input) it's going to drop those values to zero as you scroll through them. So this isn't a bug, as such.

I've personally thought of a way around this, but I haven't bothered Adam with it yet, as it is semi-complex, and requires some re-architecturing of the way the modulation is structured.

So, long story short, not a bug, really, but I am aware of the issue, and I absolutely see your point, and have a way around it in mind. Just have to see if it can be done.
VanEck
Crandall1 wrote:
@VanEck: Some (most?) of the CV inputs are multipliers on internal values, and if you're multiplying by zero (which you would be with no input) it's going to drop those values to zero as you scroll through them. So this isn't a bug, as such.

I've personally thought of a way around this, but I haven't bothered Adam with it yet, as it is semi-complex, and requires some re-architecturing of the way the modulation is structured.

So, long story short, not a bug, really, but I am aware of the issue, and I absolutely see your point, and have a way around it in mind. Just have to see if it can be done.


Right on. It actually doesn't bother me much. Much rather see you guys focusing on my important and interesting things!

Just wanted to do my duty and bring it your intention in case it actually was a bug. Other than coming across that, I spent a couple hours breaking in the new features... top fucking notch man. Rock solid, really opening up new possibilities.
studionebula
VanEck wrote:
Crandall1 wrote:
@VanEck: Some (most?) of the CV inputs are multipliers on internal values, and if you're multiplying by zero (which you would be with no input) it's going to drop those values to zero as you scroll through them. So this isn't a bug, as such.

I've personally thought of a way around this, but I haven't bothered Adam with it yet, as it is semi-complex, and requires some re-architecturing of the way the modulation is structured.

So, long story short, not a bug, really, but I am aware of the issue, and I absolutely see your point, and have a way around it in mind. Just have to see if it can be done.


Right on. It actually doesn't bother me much. Much rather see you guys focusing on my important and interesting things!


The basic problem is that the microcontroller has no way to tell whether or not there's anything plugged into the jack. If it could do that, it could ignore the CV assignment if there was nothing plugged in. But it can't do that, and since an empty jack reads as zero volts--which is a valid value for a modulation signal--it can't tell whether there's nothing connected or an intentionally zero-volt signal is connected.

I suppose one solution would be to add a "depth" or "amount" parameter to the CV assignment, probably expressed as a percentage, which defaulted back to zero when the assignment was changed. Then the assignment would have no effect until that depth parameter was increased to something above zero.
VanEck wrote:

Just wanted to do my duty and bring it your intention in case it actually was a bug. Other than coming across that, I spent a couple hours breaking in the new features... top fucking notch man. Rock solid, really opening up new possibilities.

Yes, please do tell us about such things when you find them--we very much appreciate the feedback. I'm glad to hear you're enjoying the new stuff!
Patate le mage
hyper w00t
Thank you very much for this fast and very usefull update.
I appreciate particularly the live transpose.
modul acht
Hey Chris & Adam,

my first post here at MW. Hope I´m welcome to all...

Coming from Germany, but there´s not that hype (like in my head) about adm06 (cant explain). I want to say thanks for 1.1.!!!!
Was bored about using my T/H for sequencing notes. now its fine...

without wanting to much...

may it be possible to select "hold" also to Lin CV values?

If u could implement, it would be amazing. e.g. filter programming per step/step/step should be better to drop value per note.

thumps up for your awesome work!

appreciate

Jesko
synthmind
Crandall1 wrote:
Oh, Jesus Christ. My bad. I changed the text on the download page but not the link. Refresh the page; fixed now.

Terribly sorry, everyone. It has been a Dayâ„¢ here.


Ah ha! That's why I'm not seeing any changes since I did the update! I'll try again. Thanks.
flo
modul acht wrote:
Hey Chris & Adam,

my first post here at MW. Hope I´m welcome to all...

Coming from Germany, but there´s not that hype (like in my head) about adm06 (cant explain). I want to say thanks for 1.1.!!!!
Was bored about using my T/H for sequencing notes. now its fine...

without wanting to much...

may it be possible to select "hold" also to Lin CV values?

If u could implement, it would be amazing. e.g. filter programming per step/step/step should be better to drop value per note.

thumps up for your awesome work!

appreciate

Jesko


Yeah, this would be very nice, plus the "key" mode for the CV outputs...
juvation
thanks so much for 1.1 - quantisation + transposition + transposition by CV = endless wanking for me.

one thing i have noticed is that the transposition value in the display doesn't update if it's set via a CV input. intentional?

i was going to let the seq 1 go in my downsizing plan. not any more.
psyclone001
Great update. Thanks applause
I mentioned once before but still not sure if possible but is a pattern randomiser an option in a future update? Combined with the now quantizer and transposition, its extremely easy to create great patterns on the fly.
I must admit I still use my other software and nord g2 sequencers more than the seq1 but if randomisation was implemented in seq1 this wouldn't be the case. Although a fantastic sequencer I still find it a little time consuming inputting notes on the fly
wxyz
Sterling update! Would be nice to have cv ins feed scale modes. Also having trouble trying to use the internal lfo's to change the programs. Is a step by step tutorial for this a possibility/
renasent
juvation wrote:
thanks so much for 1.1 - quantisation + transposition + transposition by CV = endless wanking for me.


Yep. This takes this sequencer into whole new territories. Feeding the cv inputs with another sequencer clocked at slower rates makes for endless evolving sequences.

One thing I am a bit unsure about is using cv ins for gate length. When setting all the step lengths individually to low (short gate length) values and sending positve voltages in, should this not make the gate lengths longer? It doesn't seem to be doing this for me.

I may be doing something wrong here. hmmm.....
Crandall1
In the case of gate length, the modulation is relative. Figure this:

At 50% gate length, 5V will send it to 100%, -5V will send it to 1%.

Just hold that in your head, and the rest will be easy. If you send anything over 5V (which is the max), you'll not be able to add more than 50% to the gate time, so if you make all the gate times their minimum, the most you'll be able to mod would be 50%. It is a digital device, not an analog one, and more voltage doesn't equal more of whatever, it only means you went over the maximum.

So, long story short, know your source's voltage range, and use its attenuators (or a VCA or whatever) accordingly, and you'll be good to go.
maudibe
Juvation wrote:

Quote:
i was going to let the seq 1 go in my downsizing plan.


Fuck me... it's only been on the market a month and you considered selling?

seriously, i just don't get it

The auto equivalent would be to buy a Ferrari, drive it 20 miles and then trade it. woah

Pleased to hear you are hanging on to it smile
djempirical
I've joined the fold!

Here's a quick snippet of my first patch using Sequencer 1.
renasent
Crandall1 wrote:
In the case of gate length, the modulation is relative. Figure this:

At 50% gate length, 5V will send it to 100%, -5V will send it to 1%.

Just hold that in your head, and the rest will be easy. If you send anything over 5V (which is the max), you'll not be able to add more than 50% to the gate time, so if you make all the gate times their minimum, the most you'll be able to mod would be 50%. It is a digital device, not an analog one, and more voltage doesn't equal more of whatever, it only means you went over the maximum.

So, long story short, know your source's voltage range, and use its attenuators (or a VCA or whatever) accordingly, and you'll be good to go.


Thanks. So using the standard 50% gate length and a bipolar modulation source probably gives the best results.
juvation
maudibe wrote:
Juvation wrote:

Quote:
i was going to let the seq 1 go in my downsizing plan.


Fuck me... it's only been on the market a month and you considered selling?

seriously, i just don't get it

The auto equivalent would be to buy a Ferrari, drive it 20 miles and then trade it. woah

Pleased to hear you are hanging on to it smile


my modular plan has been very fluid over the past year and several iterations have been the flavour of the month before being obsoleted. to use your analogy, it's like buying a Ferrari and then, upon trying to offroad in it for 20 miles, swapping it out for a beach buggy :-)

but yes, somehow i think it will pay to keep the Seq around!

(and to be really honest, the jacks on the bottom are still an issue no matter how i lay things out.)
extra testicle
any plans for axon like functionality?

when it came out i noticed it was similar to how i often like to run my sequencers and the interface seemed really elegant and appealing. tbh, i never bought it because with independent midi boxes or cv you can get feedback. smile

i could see using the mini-keys to select the "nodes" and the steps to set the divisors/multipliers or something like that, maybe.
newgreyarea
extra testicle wrote:
any plans for axon like functionality?

when it came out i noticed it was similar to how i often like to run my sequencers and the interface seemed really elegant and appealing. tbh, i never bought it because with independent midi boxes or cv you can get feedback. smile

i could see using the mini-keys to select the "nodes" and the steps to set the divisors/multipliers or something like that, maybe.


I'm gonna go ahead, pretend I know everything and say that Axon will be a totally new module. I have ideas on how I'd like to see it turn out but who cares what I think!! I'm sure WHEN they do it, it'll be great!
studionebula
newgreyarea wrote:
Here's a new one. Stepped away from the modular for a couple of days, came back and the Seq1 is no longer giving GATE, ACCENT, RATCHET, REPEAT feedback on the buttons. Those functions are still happening in my sequence but if I select a step it doesn't tell me what's going on anymore.

Obviously anything that takes a couple of days to manifest itself is gonna be difficult to track down. Did you happen to notice whether any other LEDs were not lighting up?
studionebula
wxyz wrote:
Also having trouble trying to use the internal lfo's to change the programs. Is a step by step tutorial for this a possibility/

Sorry, there's no mapping for using the internal LFOs to change the programs, or any other parameters. You'd need to drive one of the CV outputs with an LFO and then use a physical cable to route that output back into one of the CV inputs.
studionebula
psyclone001 wrote:
Great update. Thanks applause
I mentioned once before but still not sure if possible but is a pattern randomiser an option in a future update?

Yes, absolutely. Chris and I both want to add more randomization/generative sorts of stuff.

This gives me the opportunity to say something I've meant to say previously, which is this: obviously not every suggestion was incorporated into v1.1. This doesn't mean we thought that those suggestions were not good ones. As with any software release, you have to draw a line somewhere and say, "this is gonna be what's included." If you don't do that, you're shooting at a moving target and you never release anything.

Quote:
I must admit I still use my other software and nord g2 sequencers more than the seq1 but if randomisation was implemented in seq1 this wouldn't be the case.

Are there particular randomization features in the G2's sequencers which you like? I used to have a G2 (and the original Nord Modular).

Quote:
Although a fantastic sequencer I still find it a little time consuming inputting notes on the fly


We've got some ideas for addressing that also. So many ideas, so little time...
studionebula
juvation wrote:
thanks so much for 1.1 - quantisation + transposition + transposition by CV = endless wanking for me.


Heh. I suppose I can consider consider inspiring "endless wanking" in a customer to be a mark of success. lol

Quote:
one thing i have noticed is that the transposition value in the display doesn't update if it's set via a CV input. intentional?


Yes. The LCD doesn't update in response to the CV input(s) because those inputs do not change the parameter value itself. The CV data is added to that value or modifies it, but doesn't change it directly. It could be done either way, obviously, but that's how we did it.
cger
I read entire thread and Seq1 is now on my shopping list to become best friends with Metropolis.
studionebula
modul acht wrote:
Hey Chris & Adam,

my first post here at MW. Hope I´m welcome to all...

You are welcome!

Quote:
may it be possible to select "hold" also to Lin CV values?

Yes, that is possible. To be honest I'm not sure why we didn't think of doing that already. hmmm.....

I have a question for everyone: would it be okay if the new "hold" parameter applied to both the Pitch CV and the other CVs? Or do we need to add another "hold" parameter which applies to the other CVs?

Quote:
thumps up for your awesome work!

appreciate

Jesko

Danken Sie für Ihre freundlichen Worte!
modul acht
It's peanut butter jelly time! thx guys applause
studionebula
flo wrote:

Yeah, this would be very nice, plus the "key" mode for the CV outputs...

Yes, I knew that people would ask for the ability to run the other CVs through the key mapping as soon as this release went out the door. We decided (well, I decided, anyway--I won't make Chris share the blame for this) to not add it to v1.1 because there are some things about it which are somewhat complicated. For one thing, it would be fun to be able to have the key mapping applied after the LFO is combined with the CV, if selected, so that the LFOs could be used to generate/modify patterns of pitches. Another thing is that currently notes are represented one way internally, and the CV values are represented another way, so some way of dealing with that has to be constructed. (Suppose, for example, you switch a CV from its current "Lin" behavior to a note-oriented behavior, or vice-versa. What happens to the values entered for that CV?) So, lots of details like that added up to something which looks complicated enough that I decided it should be postponed for the sake of finishing and delivering v1.1.

So, maybe it will be part of v1.2. As with v1.1, the features that go into v1.2 will largely be determined by what y'all ask for, and we recognize that people were asking for a note-oriented mode for the CVs even before v1.1 came out.
newgreyarea
studionebula wrote:
newgreyarea wrote:
Here's a new one. Stepped away from the modular for a couple of days, came back and the Seq1 is no longer giving GATE, ACCENT, RATCHET, REPEAT feedback on the buttons. Those functions are still happening in my sequence but if I select a step it doesn't tell me what's going on anymore.

Obviously anything that takes a couple of days to manifest itself is gonna be difficult to track down. Did you happen to notice whether any other LEDs were not lighting up?



I feel as though some of the 16 steps were dimly lit but the sequencer didn't move follow the steps. It basically looked frozen except the screen still worked, I could still use everything, program etc but no visual feedback.
It could have just been a power glitch. seriously, i just don't get it I've not seen it since.
-b
flo
studionebula wrote:
I have a question for everyone: would it be okay if the new "hold" parameter applied to both the Pitch CV and the other CVs? Or do we need to add another "hold" parameter which applies to the other CVs?


I'd be fine with a global select for hold.

studionebula wrote:
flo wrote:

Yeah, this would be very nice, plus the "key" mode for the CV outputs...

Yes, I knew that people would ask for the ability to run the other CVs through the key mapping as soon as this release went out the door. We decided (well, I decided, anyway--I won't make Chris share the blame for this) to not add it to v1.1 because there are some things about it which are somewhat complicated. For one thing, it would be fun to be able to have the key mapping applied after the LFO is combined with the CV, if selected, so that the LFOs could be used to generate/modify patterns of pitches. Another thing is that currently notes are represented one way internally, and the CV values are represented another way, so some way of dealing with that has to be constructed. (Suppose, for example, you switch a CV from its current "Lin" behavior to a note-oriented behavior, or vice-versa. What happens to the values entered for that CV?) So, lots of details like that added up to something which looks complicated enough that I decided it should be postponed for the sake of finishing and delivering v1.1.

So, maybe it will be part of v1.2. As with v1.1, the features that go into v1.2 will largely be determined by what y'all ask for, and we recognize that people were asking for a note-oriented mode for the CVs even before v1.1 came out.


Thanks Adam. No hurry. I mainly want it to be able to easily sequence two voices on the fly. Actually I already do it, it's accurate enough with two decimal places of V. But fiddly to dial in (and must also be done on all muted steps so far without the "hold" function).

As for the "LFO arpeggiator" option, that is a very nice idea. I suppose you could do it the same as for the "lin" values, add one option "key" that is just key steps as well (either w/ the knobs for the cv, or maybe you can even figure out a way to use the keys as well for inputting notes to the cv outs...), then "key+" that is key plus the LFO...? It would cry for quantization options though...

Regarding the already stored values in a "lin" cv out, which you then change to "key": ideally for my situation, it would quantize to the closest key.

Those two options, the hold mode and key for cv outs, along with some way of realtime input would be my three biggest wishes.

Anyways, love the Seq1 as it is already! SlayerBadger!
flo
flo wrote:
Regarding the already stored values in a "lin" cv out, which you then change to "key": ideally for my situation, it would quantize to the closest key.


I also just thought: the other way around it could also switch to the nearest lin cv value; that way one could easily input notes, then switch it over to throw just some steps off the 12TET tuning applause
VanEck
Just want to reiterate how much I am digging this 1.1 update. It was only a .1 version increase, but I feel like it really opened up the Seq1 musically.

Very pleased to see notes function like a digital sequencer now as opposed to analog, and that the option is on by default. The built in scaling/quantization/transpose functionality are superb. The options/interface for them were very well implemented. Easy to navigate, visually expressive, efficient, and only 1 more level deep to navigate to.

Seq1 has quickly become my "go to" module for note sequencing, cv sequencing, gate\trigger sequencing, tempo synched modulation, and random modulation. Can't wait for generative functions to be added... screaming goo yo
wxyz
studionebula wrote:
wxyz wrote:
Also having trouble trying to use the internal lfo's to change the programs. Is a step by step tutorial for this a possibility/

Sorry, there's no mapping for using the internal LFOs to change the programs, or any other parameters. You'd need to drive one of the CV outputs with an LFO and then use a physical cable to route that output back into one of the CV inputs.
Thanks for the response. I understood the hardwire connection but have difficulty setting the lfo's. They aren't global so when the pattern changes does the new lfo reset? For example I find with a ramp down setting of 16 steps my patterns will jump from A1 to A8 to A6 to A8 to A11 to A8 and then stay on A8 and not change.
ps Changing the modes is great. Can it be cv controlled?
Crandall1
Oh, duh. I see what you're asking now. LFOs and CV outputs are per pattern, so yeah, if you're using an internal LFO to change the patterns, obviously, unless the new pattern has exactly the same LFO and CV output settings, it's going to modulate differently or not at all.

Honestly, without changing the architecture of the unit, that's going to be the way that is. I suggest using a modulation source other than the unit itself if you want to modulate patterns. That feature is in there with the idea of changing the unit's patterns via Pressure Points or something, not just spraying random values at it from the internal LFOs. There are plenty of other ways to achieve that same effect. Since the unit is necessarily quantized to per-step or per-pattern-length for the switching, any random source will work fine, as it will quantize it in to a useful ballpark automagically.

Regarding changing the mode/scale with CV, someone will have to make a strong, well-argued case as to why that's a good idea, because I don't think it is. Just having a feature to have it just in case is not, historically, something we do at Audio Damage. If something is an edge use case, more often than not, I lean towards not having it at all.
studionebula
newgreyarea wrote:

I feel as though some of the 16 steps were dimly lit but the sequencer didn't move follow the steps. It basically looked frozen except the screen still worked, I could still use everything, program etc but no visual feedback.
It could have just been a power glitch. seriously, i just don't get it I've not seen it since.
-b

Hrm. Okay, well, for the moment I guess we'll have to leave it as something to watch for, but nothing which can be diagnosed at this time. Thanks for the info.
studionebula
flo wrote:
studionebula wrote:
I have a question for everyone: would it be okay if the new "hold" parameter applied to both the Pitch CV and the other CVs? Or do we need to add another "hold" parameter which applies to the other CVs?


I'd be fine with a global select for hold.

I feel like this would work for most people, but I always try to avoid breaking stuff which customers have previously created. The conservative approach would be to have a separate parameter for the other CVs which defaulted to behave as it does currently, so that existing patterns were unaffected. That's starting to wade into overkill waters, though.

flo wrote:

As for the "LFO arpeggiator" option, that is a very nice idea. I suppose you could do it the same as for the "lin" values, add one option "key" that is just key steps as well (either w/ the knobs for the cv, or maybe you can even figure out a way to use the keys as well for inputting notes to the cv outs...), then "key+" that is key plus the LFO...? It would cry for quantization options though...

It seems to me that there wouldn't be much reason to not quantize the LFO when it's combined with the CV, simply because it wouldn't be useful for much besides adding pitch bends on top of notes. I suppose that's useful, but it seems like a somewhat extreme case--and could be achieved in other ways if you really wanted it (e.g. by using two LFOs).
Quote:

Regarding the already stored values in a "lin" cv out, which you then change to "key": ideally for my situation, it would quantize to the closest key.

Yep, that's what it should do. Also, it has to work for both Pitch CV modes, i.e. V/oct and Hz/V. That complicates matters slightly.
studionebula
flo wrote:

I also just thought: the other way around it could also switch to the nearest lin cv value; that way one could easily input notes, then switch it over to throw just some steps off the 12TET tuning applause

Heh. See, awhile back when I was considering the issues inherent in using the CVs for pitch control, I realized that it should do exactly that. Then I thought, "nah, nobody's going to want to do something that fiddly..." So, cheers for demonstrating that I should not underestimate the imagination of our customers. Chugging Beers
studionebula
VanEck wrote:
Just want to reiterate how much I am digging this 1.1 update. It was only a .1 version increase, but I feel like it really opened up the Seq1 musically.

Thanks! Flattery will get you somewhere. lol

Quote:
Can't wait for generative functions to be added... screaming goo yo


Okay, on that topic: I've always envisioned that random/generative features could fall into one of two categories. The first category would be a set of commands which did something to the existing data in a pattern. Examples might be: randomize all of the notes, randomize the order of the steps, randomize the octaves, reverse the order of the steps, etc. Basically they could be thought of as "higher level" commands that operate on the entire pattern, as opposed to the currently available low-level manipulations (e.g. setting individual notes and CV values). Note also that this sort of command could also include one for rotating the entire pattern to change which step is first in the pattern, something which at least one person (besides myself) wants.

The second category would be perhaps more what people describe as "generative" in that they'd cause the pattern to change as it played, largely without further intervention on the part of the user. For example, there might be a mode (without getting into the details of how you'd bring about this mode) in which a randomly chosen pair of steps would swap position after each time the pattern played through once. Another example might be that, once per cycle of the pattern, the note of a randomly chosen step would change by a randomly chosen interval. In other words, these modes would describe what will happen to the pattern in general terms, and what exactly happens would be up to chance.

The exact effects of these two categories would overlap, obviously. The difference would be how they're applied. One way to think about the difference is that the first category of operations could be used either when the sequencer is playing or stopped, whereas the second category would only have an effect when the sequencer is playing. The first category would happen only when you explicitly asked it to happen. The second category would happen every time the pattern played, once you'd asked for it to happen.

So, my question is: are you--and everyone else--thinking about the first category, the second category, or both? Either answer is okay. I'm just trying to get a sense for what people are thinking about.

It's probably also worth mentioning that anything along these lines is going to require at least a modicum of menu-diving. That's also always been part of our intent: basic stuff that everyone always uses should be as easy to reach as possible, esoteric stuff can (and will) necessitate a little bit of digging.
Ras Thavas
When generative functions have been suggested, items like the second category came more to mind for me, as the ones in the first category seem more like existing live cutting abilities already present.

Obviously I'd want and use any of the suggested items, regardless of category. Some are processes I'd essentially "steer", and others are ones that would "steer themselves" once initiated.

I'd imagine the second category items, the self steering ones, might require some minimal menu diving, while the ones from the first category might be nice to be able to momentarily engage, like the repeats and rachets.

Seeing as there are 6 functions that could be assigned to buttons 11 - 16 (by holding "alt"), it'd be fun to assign some of these there. Even better would be the ability for us to assign the functions we want, while menu diving, to alt 11-16, if possible. Everyone can set up there own performance toolset that way.

And now for a hopefully simpler request, would it be possible to get a rachet 3 by holding down the rachet 2 and 4 buttons at the same time? Along those lines, a repeat 6 and a repeat 3 by holding down the appropriate button sets simultaneously?

Again big thanks to Audio Damage for their engagement with the MW community, you guys have been great.
studionebula
Ras Thavas wrote:

Obviously I'd want and use any of the suggested items, regardless of category. Some are processes I'd essentially "steer", and others are ones that would "steer themselves" once initiated.

That's a good way of putting it.
Quote:

I'd imagine the second category items, the self steering ones, might require some minimal menu diving, while the ones from the first category might be nice to be able to momentarily engage, like the repeats and rachets.

Seeing as there are 6 functions that could be assigned to buttons 11 - 16 (by holding "alt"), it'd be fun to assign some of these there.

Oho! That I didn't think of at all. That would be quite fun: hold down a button and the pattern mutates in one of several ways for as long as you hold the button, release the button and it returns to its original form. Or maybe it doesn't return to its original form. Excellent suggestion in any case. applause
Quote:

Even better would be the ability for us to assign the functions we want, while menu diving, to alt 11-16, if possible. Everyone can set up there own performance toolset that way.

That would be nice, too. That is similar to something else which I'd like to implement eventually, which is to enable the user to assign functions to the three encoders, so that they do something useful when you're not in any edit mode.
Quote:

And now for a hopefully simpler request, would it be possible to get a rachet 3 by holding down the rachet 2 and 4 buttons at the same time? Along those lines, a repeat 6 and a repeat 3 by holding down the appropriate button sets simultaneously?

Ah, good idea also. Yes, that shouldn't be hard to do.
Quote:

Again big thanks to Audio Damage for their engagement with the MW community, you guys have been great.

Thank you, and thanks for the feedback.
newgreyarea
Ummmmm........ I want all that!!! I always like the evolving sequences I could get in Numerology. That plus key constraints make for some great fun! It would be cool if we could engage the random/generative stuff via CV in as well. Then we could trigger when we want in live situations without diving.

I must say that I'm very impressed with AD's willingness to engage with their users. Some companies take personal offense to the idea that we might want something they didn't put in a product already. When I have room, I will probably add another Seq1. Especially if this stuff is added. 2 separate sequences controlling two VCO's modulating each other!?!? Ahhhhh!! It's like one of my all time favorite Reaktor patches from way back.
djempirical
studionebula wrote:
Oho! That I didn't think of at all. That would be quite fun: hold down a button and the pattern mutates in one of several ways for as long as you hold the button, release the button and it returns to its original form. Or maybe it doesn't return to its original form.


oh, I love this idea!

And +1 to the triplet ratchet idea.
DSC
newgreyarea wrote:


... I will probably add another Seq1. Especially if this stuff is added. 2 separate sequences controlling two VCO's modulating each other!?!?


Yes, THIS, THIS and THIS!!! Turning out to be the best euro sequencer, PERIOD!
VanEck
studionebula wrote:

So, my question is: are you--and everyone else--thinking about the first category, the second category, or both? Either answer is okay. I'm just trying to get a sense for what people are thinking about.


I'm going to say "both". My favorite sequencer in Euro, up until the Seq1, was the Kilpatrick Step Sequencer. This was mainly due to how well it could handle generative functions. It had the options to go all out, generating completely random patterns manually, or having it set to rotate completely random patterns every cycle (like the AD BigSeq2 reset function).

But it also had the ability to be more "controlled", for example you could configure just a single step to be random in a pattern, and even that randomness could be controlled to be quantized within the scale selected, so it could be very musically useful. This ability to control the chaos was great. The only reason I ultimately sold this sequencer was it was far too menu divey for me... lots of options and power, but all trapped behind a tiny LCD, 2 buttons and a rotary knob. It felt very tedious to program and doing anything performance wise with it was out of the question... but I do miss some of those generative features which it nailed.

I think a combination between those types of functions, combined with the type "mutate" functions you can do with Reason's Step Sequencer, all wrapped up in Seq1 would be great. As you said, adding these features will definitely bring about a new level of menu diving on the Seq1, but since these could be considered "advanced options", I think that is to be expected and won't be a problem really... the "meat" of the sequencer is still very much up front and quick to program.
flo
studionebula wrote:
flo wrote:

I also just thought: the other way around it could also switch to the nearest lin cv value; that way one could easily input notes, then switch it over to throw just some steps off the 12TET tuning applause

Heh. See, awhile back when I was considering the issues inherent in using the CVs for pitch control, I realized that it should do exactly that. Then I thought, "nah, nobody's going to want to do something that fiddly..." So, cheers for demonstrating that I should not underestimate the imagination of our customers. Chugging Beers


Just wanna say thanks to Adam and Chris again, it's getting very interesting in here lately! Guinness ftw!
psyclone001
It was asked to me earlier what I liked about the Nord G2 sequencer randomisation and it is actually very simple but extremely effective. The G2 sequence modules have a simple randomise button that when pressed simply randomises all the step values within the sequence. The sequencer can be used to send gate, pitch signals etc throughout your patch and combined with the G2 quantiser module it is an endless way of generating cool sequences.
I simply keep pressing the randomise button till it comes up with a cool pattern then save that as a new preset on the G2 for future use. Within a few minutes I can save a bunch of great patterns via this method.
With the seq1 now quantising, if this simple randomise 'button' was introduced I would be in euro sequencer heaven and could nearly retire my Nord G2 sequencer thumbs up
djempirical
I just had an idea, and figured I'd throw it out here; maybe it'll spark other ideas.

In conjunction with the randomization, what about a setting that would adjust how much the randomization would favor the tonic of the quantization? So like, at 100% you'd get just the tonic in your randomization, and at 0% the tonic would be equally likely to occur as the other notes.
wxyz
Another vote for the second category. Allowing cv control of modes could be like a jazz improviser running different scales over a progression. Or it could be randomized a create a musically structured chaos.
granville
I now feel like I need both categories!

I'm down for anything generative or random, whether that's whole patterns, or chosen steps. Love the morph button hold idea too.
renasent
Loving this sequencer more each day.

w00t

I'm well up for both types of generative randomness. I wonder how easy (or difficult) it would be to implement a category 1 (or 2) randomize that includes random slides, held notes, gate on/off and accents alongside the random notes?

This would be similar to the kind of randomize feature you get on the BassBot TT-303. It has two kinds of randomize: randomize the entire sequence (generate an entirely new one) or slightly modify an existing one. The only problem with this is it doesn't necessarily generate notes that are in key.

Really keen on a rotating the entire pattern function like Adam suggested. Like, shift the whole sequence forward by one step.
juvation
my idea for generative would be that steps contain probabilities rather than certainties. so a step could have a bell curve around its programmed pitch, the curve having programmable width - a width of 0% being effectively the static pitch we have now. the step could have a similar curve around gate length, etc, and a linear probability of an accent, slide, ratchet, all that.

for the generative stuff that affects the entire pattern, like rotate or similar, i might suggest that a positive-going transient on a CV input would trigger it. so you could have comparators linked to S&Hs etc decide once in a while to do it.

(oh and that's my suggestion for another LFO shape - like the current random, but it produces only a gate, which goes high if the random output exceeds a configured threshold. gated comparator mode.)
studionebula
Thanks for all of the comments, everyone. I'm getting caught up here after Christmas etc.

newgreyarea wrote:
Ummmmm........ I want all that!!! I always like the evolving sequences I could get in Numerology.

Historical trivia/brag: I was the first person to purchase a Numerology license. That should tell you something about my obsession with sequencers. Unfortunately I switched from using a Mac to a PC for music-making shortly thereafter, so I've never spent the time with Numerology that it deserves.

Quote:
It would be cool if we could engage the random/generative stuff via CV in as well. Then we could trigger when we want in live situations without diving.

Yeah, that would indeed be cool. CV input is interesting in this context because it could control the amount of change in some manner.

Quote:

I must say that I'm very impressed with AD's willingness to engage with their users. Some companies take personal offense to the idea that we might want something they didn't put in a product already.

Bah. It's bad business to be offended by your customers. Besides that, we've always known that this product would grow over time. That's why e.g. I chose an MCU with more than enough storage and horsepower to do what we initially planned.
studionebula
VanEck wrote:

I'm going to say "both". My favorite sequencer in Euro, up until the Seq1, was the Kilpatrick Step Sequencer. This was mainly due to how well it could handle generative functions.

I don't know of that one; thanks for the pointer.
Quote:

But it also had the ability to be more "controlled", for example you could configure just a single step to be random in a pattern, and even that randomness could be controlled to be quantized within the scale selected, so it could be very musically useful.

The "controlled" aspect is what I think becomes key in these sorts of things. Just randomizing everything sometimes produces useful results, but often doesn't. The Access Virus has a nice patch randomizer which has a sort of intensity control. The higher you set that control, the further the resulting patch deviates from the original. It works very nicely for creating new patches which are sort of like an existing patch. This is the kind of behavior I'd like to achieve with Seq1.
studionebula
psyclone001 wrote:
It was asked to me earlier what I liked about the Nord G2 sequencer randomisation and it is actually very simple but extremely effective. The G2 sequence modules have a simple randomise button that when pressed simply randomises all the step values within the sequence.

Ah, okay, I do remember that behavior.
Quote:

I simply keep pressing the randomise button till it comes up with a cool pattern then save that as a new preset on the G2 for future use. Within a few minutes I can save a bunch of great patterns via this method.
With the seq1 now quantising, if this simple randomise 'button' was introduced I would be in euro sequencer heaven and could nearly retire my Nord G2 sequencer thumbs up

Building such a 'button' would be easy enough, but I think we're gonna set our sights a bit higher. There's a certain amount of overhead involved in doing any sort of update (e.g. debating what the update will constitute, testing it, making sure we didn't break anything). So in other words, if we do anything at all, we try to make it pretty interesting. This means more time between updates, yes, but higher-quality results, hopefully avoiding the vicious cycle of hastily created updates followed by even more hasty bug fixes. At least that's the idea.
studionebula
djempirical wrote:
I just had an idea, and figured I'd throw it out here; maybe it'll spark other ideas.

By all means...
Quote:
In conjunction with the randomization, what about a setting that would adjust how much the randomization would favor the tonic of the quantization? So like, at 100% you'd get just the tonic in your randomization, and at 0% the tonic would be equally likely to occur as the other notes.

Bonus points if you recognize this quotation: "Step on the tonic and step on the tonic again!"
Anyway, yes, this fits into the notion of a "strength" sort of parameter for any randomization. This strength would have different effects depending on what sort of parameter is being randomized. For notes, it might favor the tonic as you describe. For gates, it might determine how many randomly chosen steps within the sequence get their gate flipped on/off.
studionebula
renasent wrote:
I'm well up for both types of generative randomness. I wonder how easy (or difficult) it would be to implement a category 1 (or 2) randomize that includes random slides, held notes, gate on/off and accents alongside the random notes?

It's really no easier or more difficult than randomizing notes. It's all numbers on the inside. Randomize those numbers, random slides/gates/whatever comes out. spinning
Quote:

This would be similar to the kind of randomize feature you get on the BassBot TT-303. It has two kinds of randomize: randomize the entire sequence (generate an entirely new one) or slightly modify an existing one.

I think that those two kinds can be the same if the "strength" parameter I keep going on about works properly. If strength is 100%, then whatever is in the current pattern gets obliterated by randomness. If strength is say 10% the existing pattern is only slightly modified.
Quote:
The only problem with this is it doesn't necessarily generate notes that are in key.

Now that we have the scale/key stuff in place, there's no reason that any sort of randomization/generative process won't use it. Rockin' Banana!
Quote:
Really keen on a rotating the entire pattern function like Adam suggested. Like, shift the whole sequence forward by one step.

This has been talked about it for awhile; I can't take credit for mentioning it first. I did say that I want it for myself, though, because I always seem to end up with "one" on the wrong step, regardless of whose sequencer I'm using.
studionebula
juvation wrote:
my idea for generative would be that steps contain probabilities rather than certainties. so a step could have a bell curve around its programmed pitch, the curve having programmable width - a width of 0% being effectively the static pitch we have now. the step could have a similar curve around gate length, etc, and a linear probability of an accent, slide, ratchet, all that.

And Chris tells me that my ideas are too complicated... applause
Actually this is not entirely dissimilar to something he and I tossed around awhile back. The big consideration is this: obviously the user interface additions necessary for something like this would be fairly involved; we're somewhat constrained with what can be done on a 3x16-character LCD. Given that, how many people would be interested in expending the effort to set up all of this stuff? So far what I'm mostly gleaning is that people want fairly simple-to-use sorts of randomization features which Do Stuff upon the press of a button or the pulse of a CV input. But now that this idea is out there, well, what do y'all think?

Quote:
(oh and that's my suggestion for another LFO shape - like the current random, but it produces only a gate, which goes high if the random output exceeds a configured threshold. gated comparator mode.)

Oh, good one. Easy to program, too.
Ras Thavas
studionebula wrote:

Oho! That I didn't think of at all. That would be quite fun: hold down a button and the pattern mutates in one of several ways for as long as you hold the button, release the button and it returns to its original form. Or maybe it doesn't return to its original form. Excellent suggestion in any case. applause


This brings up a question/request I've thought of; would it be possible to "hold" an arrived at state?

A very simple example is occasionally I'll hit a "repeat 4" that I want to hold and do some wiggling over. Currently I'm limited to one handed wiggling; as soon as I let go my 4 note ostinato vanishes. Of course, with the repeats I can always catch the same 4 notes next time around, but as the software expands and adds new generative functions that's not going to be the same case...

For any of the "hold the button and mutate" functions, it'd be nice to be able hold the state without having to keep the button depressed, if desired. Some way to "freeze" or "lock" the state if you decide to. Since this in essence is a buffer type function, it'd be great to be able to flip back to that last used buffer at will, or perhaps even several "on-the-fly" saved states?

One other thought; perhaps two new CV destinations- "first step" and "length"? First step simply picks the starting note of a sequence, allowing you to change from say a 1 thru 16 to something like 4 thru 16. Length sets how long the sequence is, just like on the existing sequence page, except it'd stop at the existing last step, and not add unprogrammed steps. The changes are quantized to clock steps. There are probably better ways to do this sort of thing, but what I'm looking for is more ways to get in and modify, cut-up, and really get the most out of an existing sequence on the fly. The repeats are a great start, I'm wondering if there are even more in depth ways to do this sort of thing while staying "in time" when you stop?

I just did the upgrade for my Seq-1 last night, truly as easy as pie and I'm very excited about the direction this sequencer is going, 1.1 is already top notch, can hardly wait to see what a version 1.5 or 2 will look like!
djempirical
studionebula wrote:
Bonus points if you recognize this quotation: "Step on the tonic and step on the tonic again!"


No bonus for me, I'm afraid. smile
newgreyarea
studionebula wrote:
Thanks for all of the comments, everyone. I'm getting caught up here after Christmas etc.

newgreyarea wrote:
Ummmmm........ I want all that!!! I always like the evolving sequences I could get in Numerology.

Historical trivia/brag: I was the first person to purchase a Numerology license. That should tell you something about my obsession with sequencers. Unfortunately I switched from using a Mac to a PC for music-making shortly thereafter, so I've never spent the time with Numerology that it deserves.

Quote:
It would be cool if we could engage the random/generative stuff via CV in as well. Then we could trigger when we want in live situations without diving.

Yeah, that would indeed be cool. CV input is interesting in this context because it could control the amount of change in some manner.

Quote:

I must say that I'm very impressed with AD's willingness to engage with their users. Some companies take personal offense to the idea that we might want something they didn't put in a product already.

Bah. It's bad business to be offended by your customers. Besides that, we've always known that this product would grow over time. That's why e.g. I chose an MCU with more than enough storage and horsepower to do what we initially planned.



I was also thinking it would be cool if the sequence moved further from the original with higher CV values and back to the original with zero CV. Like a scatter type function that's non destructive. That could be so cool if it was able to keep it in the same key. Ahhhhh!!! I just got so excited for something that doesn't even kind of exist. Hah!
flo
Ras Thavas wrote:
studionebula wrote:

Oho! That I didn't think of at all. That would be quite fun: hold down a button and the pattern mutates in one of several ways for as long as you hold the button, release the button and it returns to its original form. Or maybe it doesn't return to its original form. Excellent suggestion in any case. applause


This brings up a question/request I've thought of; would it be possible to "hold" an arrived at state?

A very simple example is occasionally I'll hit a "repeat 4" that I want to hold and do some wiggling over. Currently I'm limited to one handed wiggling; as soon as I let go my 4 note ostinato vanishes. Of course, with the repeats I can always catch the same 4 notes next time around, but as the software expands and adds new generative functions that's not going to be the same case...

For any of the "hold the button and mutate" functions, it'd be nice to be able hold the state without having to keep the button depressed, if desired.


Yeah, this crossed my mind as well. Could be as simple as holding down "alt" for example, while holding the appropriate function SlayerBadger!
Crandall1
Sidebar: I have one single Sequencer 1 unit left in the office. I was holding it for someone that flaked. So I've added it to the AD store. This is the very last one of this run that will be available direct.

Some of the stores still have stock, of course.
wxyz
granville wrote:
I now feel like I need both categories!

I'm down for anything generative or random, whether that's whole patterns, or chosen steps. Love the morph button hold idea too.
The RS-200 has a feature where a step can be overridden with a skip in cv, which could be random or another sequence.
Bogus
I'm curious what methods others are using to form chords with the Sequencer 1. One really great way I've found has been to dial in step CV and send that information to the Piston Honda mkIIs wavetable selection inputs. Also using accent to bring in the Shapeshifter in Chord Mode but that seems pretty standard.
VanEck
Reviving this thread since the more recent thread and posts seem to be inaccessible now on forumx.

Last i recall, OS v1.2 was going to be featured at NAMM showing off the new generative functions to some degree? Did that happen? Any first hand reports? Any proposed release dates?
Ras Thavas
I think AD was asking for input because they planned to get to working on the next update when they got back from NAMM, if memory serves.

Good news is there's still time to make suggestions, AD's been very good about assessing community input. Bad news is I think the next update will take just a little longer to get out in the wild.
Crandall1
Ras is correct. We would never show a prototype at NAMM. That's for smaller events. :-)

We will begin the v1.2 update in earnest later this week (Adam is still in Anaheim) and will, of course, be updating this thread with the feature set as it becomes codified. Early next week, I'll provide a list of the features we're definitely adding.

Side note: it was great meeting many of you at NAMM. Sequencer 1 owners are a wonderful bunch!
VanEck
Ah my bad. Could have sworn I read that on forumx while it was up. Wishful thinking on my part d'oh!
Crandall1
One note not related to the upcoming update:

As Muff's readers no doubt know, Paul Schreiber is releasing his E620 USB-CV device soon. We will be providing a Max4Live device to directly drive Sequencer 1 using the E620; you'll just drop it on a channel, and it will change the E620 to the correct mode, and sync Seq1 perfectly with the DAW.

So, if you were considering the E620 for other purposes and own Sequencer 1 and are a Live user, this is something you might want to keep in mind.
newgreyarea
Tech Support: I am having a an issue where my Seq1 won't play! I've tried INT, EXT, and several different clock sources. It was working fine last night. Where is the stupid thing that I'm somehow forgetting because I am a sleep deprived new parent zombie monster!!??

Still my fave sequencer! Is that other thread lost forever? Do you (Chris & Adam) have a copy of all that was discussed there? Can't wait to see where it goes next!

-b
newgreyarea
Um. . . . . . so I turned off everything at the CV inputs and it worked again. I didn't have anything plugged into them but they were assigned. Do they keep assignments even when switching to new unused patterns? I was way too sleep deprived to deal with it at the time, but sat up in bed and went to try it first thing this morning.

-b
Fite
Hello,

i'am new and i like AD1
phutureboy
Crandall1 wrote:
Paul Schreiber is releasing his E620 USB-CV device soon

I didn't find any info about that one. What are the differences with the Expert Sleepers FH-1 ?
http://www.expert-sleepers.co.uk/fh1.html

And while I'm at it, any chance you could add this interesting feature added in the Moog SUB-37 they call "LFO swing" ?
https://www.youtube.com/watch?v=pPwSMW08BNA#t=13
Crandall1
@newgreyarea: As it clearly states in the manual (heh!) the CV inputs are globals, not per pattern. The outputs are per pattern. The reasons for this should be pretty obvious if you plan to use more than one pattern in a live performance situation, or if you're using an external LFO to drive, say, pattern switching. (Switches to a pattern that doesn't have that programmed? That's the end of your fun!!!)

This can, as you discovered, create some confusion if you're not used to it. But now you are. Problem solved!

Protip: if your Seq1 is not playing, the FIRST THING TO CHECK is to see what's assigned to CV1 and CV2 inputs. The second thing to do is to go to the AD site, grab the latest firmware, and reflash it.

The third thing is to write us immediately at info-at-audiodamage-dot-com. I don't check this site every minute of every day, but I almost always see those emails immediately, and chances are, it's something simple that can be solved with a couple questions.
newgreyarea
Crandall1 wrote:
@newgreyarea: As it clearly states in the manual (heh!) the CV inputs are globals, not per pattern. The outputs are per pattern. The reasons for this should be pretty obvious if you plan to use more than one pattern in a live performance situation, or if you're using an external LFO to drive, say, pattern switching. (Switches to a pattern that doesn't have that programmed? That's the end of your fun!!!)

This can, as you discovered, create some confusion if you're not used to it. But now you are. Problem solved!

Protip: if your Seq1 is not playing, the FIRST THING TO CHECK is to see what's assigned to CV1 and CV2 inputs. The second thing to do is to go to the AD site, grab the latest firmware, and reflash it.

The third thing is to write us immediately at info-at-audiodamage-dot-com. I don't check this site every minute of every day, but I almost always see those emails immediately, and chances are, it's something simple that can be solved with a couple questions.


I'm the worst with manual retention! I read them. Forget everything and figure it out on my way. It's a reading retention thing. I've always learned by doing. Now I've done. . . . and learned.
I knew it was probably user error so posted here so that someone could point out that I'm too tired for electronic stuffs and should stick to mouth harp or something!

-b
Crandall1
For what it's worth, I'm the same exact way. I _never_ read the manual unless I'm like "WTF?" about something. And when I do, I promptly forget it.

As a designer, I try to make our products so they're pretty self-evident. Sequencer 1 is, by far, the most complex product we've ever made, and while I'm doing my damnedest to keep it fairly obvious, at the end of the day, with all the functionality we're shoving in this bitch, stuff like this is gonna happen.

Long story short: don't feel bad. I'm just like you. The first time this exact thing happened to me, I immediately hopped on chat with Adam all "HEY ZOMG I FOUND A BUG?!!!?!"
phutureboy
Hey Chris, did you miss my questions ? Mr. Green
Crandall1
phutureboy wrote:
Hey Chris, did you miss my questions ? Mr. Green


I did, sorry.

Regarding the first, I'm not gonna compare-and-contrast the E620 v. the FH-1; the E620 thread has a ton of that sort of thing. They're pretty different, suffice to say. One thing the E620 does that the FH-1 doesn't do at all is act as a class-compliant MIDI->CV interface, which is what concerns us here. I'll make an M4L instrument for Live that will, assuming the output of the channel is set to the E620, put it in the proper mode and set up the jacks to talk to Sequencer 1, and then send the correct start/stop/clock/reset values to keep Seq1 in perfect sync with Live.

Regarding the second question, that's very tricky to do; I'd actually like that swung LFO feature quite a bit, but we'll put it in the Pie-In-The-Sky folder for now, as it would take quite a bit of development time to make the LFOs respond to swing, and calls in to question a lot of usability issues.

tl;dr: I'd like to do it. Whether Adam _can_ do it is up to him.
phutureboy
I see, thanks.
SlyFrank
I'm loving this sequencer, but one thing that I just figured would go away because I was missing something obvious (and maybe I am..) but is still there because I can't figure it out, is this:

Whenever I power on the Seq1 the display is borderline illegible. And it's not due to it being set too low. I have it set to 28 in global options. It is very legible for me at that setting. When I power it on it says 28 but it is all washed out - about equal to a setting of 10 or 11. Luckily at that level I can see it well enough (or at this point I can do it blindfolded) so that I go into the 3rd page of global options and just toggle the knob one click right or left, then back to 28. So, it powers on at "28" but displays a level more like "10" until I go in and just jiggle the knob to 29 or 27 then back to 28. Then all is good. I keep re-saving patterns to try to make it stick, no luck. Am I missing something? seriously, i just don't get it
hpsounds
In SEQ mode, dialing the Tonic parameter is crashing the sequencer ... ?

waah
Ras Thavas
New Sequencer-1 update looks to be be including "reps" feature ala Metropolis pulse counters-

http://instagram.com/p/y-zDxmH6dI/

http://instagram.com/p/y_JSMaH6em/

-and we haven't even got into the generative stuff yet, impressed.
renasent
Didn't expect this. This just keeps getting better and better!

Sniper
phutureboy
Ras Thavas wrote:
"reps" feature ala Metropolis pulse counters

is great but if that is the case please make sure you don't forget the best part of it : the FIXED Modes...
granville
Woah, what a cool surprise!

+1 for fixed mode for the pulse counter repeat thing, makes it double the fun.

Can't wait to see the generative stuff.

Dead Banana
Bogus
Oh man that repeat feature looks great. Is there going to be CV control over repeat amount?
granville
Also re: the pulse repeat thing, would be extra good if there was a choice between retrig and hold.
phutureboy
Bogus wrote:
Is there going to be CV control over repeat amount?

+1
Bogus
granville wrote:
Also re: the pulse repeat thing, would be extra good if there was a choice between retrig and hold.


Ooo yess and CV control over repeat or hold (like a built in VC switch).

Also, I'd like to know if you guys ever gave my suggestion about linear CV hold any thought? It's almost every patch now where I find myself needing that sort of function.
Ras Thavas
I was watching videos from the recent Serge 40th anniversary gathering in S.F., and it struck how powerful using the TKB keyboard to control start and end points for a sequence was.

I have a suggestion that doesn't really relate to the generative focus of the next update, but it is a performance oriented one, and being performance oriented is a big strength of Sequencer-1.

Would it be possible to have mode in which the 16 buttons don't toggle gates or access steps, but instead control start and stop points for the sequence? Obviously this would work great with 16 step or less sequences. For sequences larger than 16 steps each button could control a proportional amount of steps, i.e. a 32 step sequence means each button toggles two steps, so the granularity of control adjusts to the number of steps.

Just a thought for consideration. I had suggested earlier adding control of the start step to go along with end step, thinking of using the knobs to accomplish this, but doing it on the fly on the 16 buttons would be much more fun.
Crandall1
@SlyFrank, I assume you wrote this before you wrote me directly?

@hpsounds, and anyone else: I don't check this thread every day, and it's not the place for the inevitable back-and-forth that finding a problem entails anyhow. If you are having a problem, the way to get a prompt reply and hopefully a quick resolution is to write the AD support email, info at audiodamage.com. That goes right to me. There's no layers of support or anything. I'll get you sorted as quickly as possible that way.

Anyhow, on to the pulse counter thingie. The way I read the RYK-M185 operation is that there are four gate modes: off, single pulse, retrig, and continuous. The first one and last two are the normal operating modes of Seq1. You can easily get the continuous hold by changing the step's gate time to TIE. Anything less gets you retrig. And obviously, if no gate is selected for that step, the first mode is the one you get. So it's just that second mode that's been puzzling us. Adam just told me that mode was now his bitch, so I imagine the next internal build will have the entirety of the RYK-M185 functionality. Obviously, it is not as immediate as the RYK-M185 (or, for that matter, Metropolis) but if you prefer that method of sequencing, it will be available to you.

@Bogus: Your CV hold request will _definitely_ be in the next update. Adam is actually working on it as I type this.

We're running in to some time constraints as we try to balance the increase in business we've had lately with production schedules for new and existing products. We haven't decided for certain yet, but it is looking like we will push firmware update 1.1.9 (not sure on that version number; might be 8 or 10, depending on how Adam numbers things) with all the above, plus some other new shit and bug fixes, very soon, then the 1.2 Generative update down the road a bit after things have settled down.

The reason for this is that, with all the requests and our own ideas, the Generative update is a real bear, requiring a major rewrite of some existing sections, and we would very much like to take the time to get it right and have it fully tested before we put it out.

I'll keep you posted on developments on that front.
DSC
Excited! These will be a very useful feature set!
SlyFrank
Crandall1 wrote:
@SlyFrank, I assume you wrote this before you wrote me directly?


Yup, after reading an earlier post of yours advising to write to infoAT... I wrote you directly. Thanks for your response. I'll wait until the next firmware release and see if that resolves it.
Bogus
Crandall1 wrote:
@Bogus: Your CV hold request will _definitely_ be in the next update. Adam is actually working on it as I type this.

We're running in to some time constraints as we try to balance the increase in business we've had lately with production schedules for new and existing products. We haven't decided for certain yet, but it is looking like we will push firmware update 1.1.9 (not sure on that version number; might be 8 or 10, depending on how Adam numbers things) with all the above, plus some other new shit and bug fixes, very soon, then the 1.2 Generative update down the road a bit after things have settled down.

The reason for this is that, with all the requests and our own ideas, the Generative update is a real bear, requiring a major rewrite of some existing sections, and we would very much like to take the time to get it right and have it fully tested before we put it out.

I'll keep you posted on developments on that front.


That's great to hear Chris, that one change will help me past many pitfalls I've run into recently, thank you both! I'm excited for all the other announced features too, it's looking like another complete overhaul. I'll be watching like a hawk for a post asking for beta testers hihi
joey
This sequencer solved so many problems with my live set. Simply perfect!
.supercollider.
Maybe I am missing it, but is there a possibility to change the PPQN resolution?
Crandall1
Okay, we have this M-185 mode whipped. See this Instagram clip:

Instagram

These are the third page in the STEP menu. The first entry is the number of pulses the step does; default is 1 (normal current operation), and max is 8. The second item, Retrig, is on/off. If it's on, you'll hear all the pulses. If it's off, you'll only hear the first one.

So, basically, you get all four possible step modes on the M-185.


M185 and Corresponding settings for Sequencer 1
0- No gate set for this step.
l Gate set, Retrig off.
ll Gate set, Retrig on.
l- Gate set, Retrig on, gate time set to "Tie."

These, of course, correspond to the four GATE MODE options in the Metropolis.

Adam has one minor change to make to the CV Hold feature that I requested after using it, and one other minor change (possibly) to make to the SEQ page, and then we'll most likely push this update out. So a couple of days.

@.supercollider. : Currently, it is one clock per step (or 4PPQ, in your parlance). We'll be adding a gearbox (both in and out) sooner rather than later.
granville
Awwwyisss w00t
newgreyarea
Noice!!!
Bogus
Adam and Chris have really lived up to the promise of consistant new features. The Seq1 is eclipsing every other sequencer on the market. Might have to go in for that second one here soon.
ben_hex
Bogus wrote:
Adam and Chris have really lived up to the promise of consistant new features. The Seq1 is eclipsing every other sequencer on the market. Might have to go in for that second one here soon.


Yep! thumbs up

Been playing around with the sequencer 1 a few times (only had a few brief bits of time for Modulsr the past few weeks) and it's a stunning bit of kit.
.supercollider.
Crandall1 wrote:
@.supercollider. : Currently, it is one clock per step (or 4PPQ, in your parlance). We'll be adding a gearbox (both in and out) sooner rather than later.


Nice, sounds great. Good work on the continuous feature additions / improvements. You're really delivering the goods.

From my perspective it'd also be nice to see a global gate length control (which preserves the ratio of the individual gate setting of the individual steps). Meaning that if I have two steps, one at a gate length of x and one of y, the I turn the global length up by ten, my first step is now at x+10 and my second at y+10.

cheeeeeeeers....
Bogus
I'm so excited for the firmware update, Adam and Chris are on a roll.
bratley
damn it, this not spending any more money on the modular isn't going well.

I've ordered one, should be hear tomorrow hopefully.
Anyone using one alongside a Metropolis?
Bogus
You've made the right decision bratley. You might not even need that Metropolis when the update drops.
Crandall1
@.supercollider. We're _definitely_ adding a global gate length adjustment to the Generative update. This is actually the first item on my wish list. It won't be included with this upcoming update, but will absolutely be in the next one.

Regarding update progress, after testing we made some changes to the CV hold feature, and Adam is coding that right now. As soon as that's done, and he finishes the random LFO amp stuff, we'll push this one. So not long.
cosmic_son
bratley wrote:
damn it, this not spending any more money on the modular isn't going well.

I've ordered one, should be hear tomorrow hopefully.
Anyone using one alongside a Metropolis?


No kidding. Haha. I am planning on using this along the metropolis for sure. I love that this has patch mem, but metropolis is more 'playable' to me, so it seems like they work well together.

On another note, are the separate CV outputs capable of outputting separate sequences? cause making this a multi-track sequencer would be bonkers. Right now I'm considering using my monomachine with yarns to do multi-track cv sequencing.

Thoughts y'all? razz
newgreyarea
cosmic_son wrote:
bratley wrote:
damn it, this not spending any more money on the modular isn't going well.

I've ordered one, should be hear tomorrow hopefully.
Anyone using one alongside a Metropolis?


No kidding. Haha. I am planning on using this along the metropolis for sure. I love that this has patch mem, but metropolis is more 'playable' to me, so it seems like they work well together.

On another note, are the separate CV outputs capable of outputting separate sequences? cause making this a multi-track sequencer would be bonkers. Right now I'm considering using my monomachine with yarns to do multi-track cv sequencing.

Thoughts y'all? razz



You can do something to that effect with the CV outs. You only get one sequence length and one gate out though. So not separate but cool for changing pitch on multiple VCO's when doing chord type stuff.
thumbs up
cosmic_son
newgreyarea wrote:
cosmic_son wrote:
bratley wrote:
damn it, this not spending any more money on the modular isn't going well.

I've ordered one, should be hear tomorrow hopefully.
Anyone using one alongside a Metropolis?


No kidding. Haha. I am planning on using this along the metropolis for sure. I love that this has patch mem, but metropolis is more 'playable' to me, so it seems like they work well together.

On another note, are the separate CV outputs capable of outputting separate sequences? cause making this a multi-track sequencer would be bonkers. Right now I'm considering using my monomachine with yarns to do multi-track cv sequencing.


Thoughts y'all? razz



You can do something to that effect with the CV outs. You only get one sequence length and one gate out though. So not separate but cool for changing pitch on multiple VCO's when doing chord type stuff.
thumbs up



Ah gotcha, yes, still incredibly cool. Thanks for the info. Even though it's a bit overkill, I still think this would be a good buddy with metropolis, but Yarns might have to be the one for me for multiple cv/gate seqs. I just love the A4 style on this module. So intuitive and awesome.
flo
I have been constantly using the Seq 1 live for two voices - use the accent out as gate for your second gate (instead of an LFO) and you have gate length twice (there's accent length!). CV resolution is just enough to get stuff in tune. So that also gives me another CV out per voice for accents / "velocity". Or you could do a third voice with those!

The "key" mode for the CV outs is one of the first things I requested I think hihi thumbs up Mainly for convenience though as scrolling through the CV values is a bit cumbersome.
cranleigh
.supercollider. wrote:


From my perspective it'd also be nice to see a global gate length control (which preserves the ratio of the individual gate setting of the individual steps). Meaning that if I have two steps, one at a gate length of x and one of y, the I turn the global length up by ten, my first step is now at x+10 and my second at y+10.

cheeeeeeeers....


+1 for this! And a corresponding way of adjusting the individual slide amount of particular steps as well as the overall amount.

Just got mine 2 days ago, have dug in with it and am overall having a great time. I wish there were multicolored LEDS though, it can be tricky to distinguish the active step sometimes. And dedicated buttons for step and sequence modes would have sped things up in terms of navigating the thing. But otherwise it's awesome, and does sooo many things really well.

I would also love to see a more detailed slide section: maybe different slopes/curves, more detailed speed control (constant vs relative to tempo etc). Especially at slower tempos, these things can really make a difference to the groove.
cranleigh
Oh, and if swing could work while it is being externally clocked that would be fabulous too!
cranleigh
A very rough n ready acid video with the sequencer1

Mainly posted to show that the frostwave resonator I'm selling is working ok, but it has the sequencer1 in there so someone might find it useful.
apologies for the dodgy audio, blurriness etc...
cosmic_son
cranleigh wrote:
A very rough n ready acid video with the sequencer1

Mainly posted to show that the frostwave resonator I'm selling is working ok, but it has the sequencer1 in there so someone might find it useful.
apologies for the dodgy audio, blurriness etc...


Nice! with the osc 303 and 606 smile dig it.
Crandall1
Sequencer 1 Firmware updated to v1.2.1.

What’s New in Version 1.2

1. Multiple Pulses Per Step
Steps can now be programmed to repeat up to eight times. The Gate output can either fire on each repetition, or only once.

2. Random LFO Amplitude
A new LFO parameter makes the output levels of the LFOs to vary randomly, by an adjustable amount.

3. Two New Stepping Modes
Two new Stepping modes, Random Even and Random Odd, provide quasi-random variations of the pattern.

4. CV Hold Options
To relieve the tedium of having to set CV values for every single step, each auxiliary CV output now has a Hold parameter. This parameter has several different options which affect whether the CV output holds its current value or changes to a new one as the sequencer advances.

5. New CV Mapping: User Scales
A new CV-input mapping allows you to switch between the pattern’s programmed scale/mode and the eight user-programmable scales.

6. Reload Pattern
You can now reload a pattern from the MicroSD card, reverting to the version of the pattern you last saved.

7. UI Tweaks
We made a couple of small but helpful changes to the user interface. The rotary encoders have a smoother response, making it less fiddly to reach the value you’re trying to dial in. When switching between different edit modes, the page within each mode is remembered and restored.

This firmware is now available for download on the Sequencer 1 product page.
http://www.audiodamage.com/hardware/product.php?pid=ADM06


ben_hex
New features sound great, looking forward to installing the firmware and trying them out.
.supercollider.
Nice update, looking forward to playing later. Here's my first evening with the beast, and my little lad learning on my knee smile

granville
Awesome update, great work. At last I can throw my metropolis under a truck (not really folks, I sold it ages ago)

I have a problem though.. My ALT to reload doesn't work. Pressing ALT when prompted does nada, the edited pattern keeps playing. If I hold ALT and press a pattern number, the seq goes out of time.

hmmm.....
schege
How is the reset situation with this sequencer. I use an ACME-4 to sync all my machines.
(Midi clock, DinSync, Analog Clock). This box fires a reset on the 1 (when it starts). This works fine with my other sequencers like Klee and Metropolis. It leads to problems with the RCD, cause the RCD needs a reset before the 1 (reset on the last step). So I have to give the RCD a manual reset before I start the hole system.
How is the Sequencer1 is handling this?
Crandall1
@granville: I fucked up in the video. I didn't actually do the second step. The steps to reload a pattern:

1. Press the bank button.

2. Hold down ALT.

3. Press the pattern you want to reload. (So if you're on A01, click bank A, hold down ALT, click 01.)

Sorry about that; my mistake. The manual is updated to v1.2 on the product page, and explains all the new features in their appropriate locations.


@schege: That same exact thing has bit me with RCD over and over again. I always forget it has that behavior, and I'm like "why is it offset?" Grrr.

Anyhow, Seq1 will be perfectly happy with your ACME-4. It works the way Klee and Metropolis work with respect to the reset.
granville
Crandall1 wrote:


1. Press the bank button.

2. Hold down ALT.

3. Press the pattern you want to reload. (So if you're on A01, click bank A, hold down ALT, click 01.)



When I do this the pattern goes out of sync - seems like it starts (resets) when I hit ALT + pattern number. Is it just me?
daybed33
I cant wait! Getting Mine on Monday! if I didn't have to work i'd probably not leave the house all next week. hihi
DeWalta
[quote=".supercollider."]
Crandall1 wrote:
@.supercollider. : Currently, it is one clock per step (or 4PPQ, in your parlance). We'll be adding a gearbox (both in and out) sooner rather than later.[/quote

From my perspective it'd also be nice to see a global gate length control (which preserves the ratio of the individual gate setting of the individual steps). Meaning that if I have two steps, one at a gate length of x and one of y, the I turn the global length up by ten, my first step is now at x+10 and my second at y+10.

cheeeeeeeers....


++++1 To the global gate length control!
DeWalta
Hey,
I just bought one of those bad boys and i have to say i am quite impressed with the amazing modulation capabilities this sequencer offers. there is nothing out there in the euro-market, that can produce such alive and self-, or externally modulating sequences and patterns. I am very happy with it.

However i really miss the ability to swing the whole shebang if the sequencer runs as a slave off of a straight clock. I understand that some people prefer to swing the master clock and have all slave sequencers use the master swing, but in my case it be great to choose. i am really really missing the Audio Damages Sequencers internal swing for sequenced melodies when externally clocked. I would really love to be able to choose to activate swing in slave-mode!!
I presume its not possible to implement that?

Thanks anyways
Crandall1
@DeWalta: It is possible. However, it is difficult for a number of reasons. Since this has been asked often enough to enumerate those reasons, that's exactly what I'll do:

1. The only way this really works well is if you're sending the unit a higher resolution clock than 1 pulse per step. For reasons that should be fairly obvious (chief amongst them being the uni-directional linear nature of the space-time continuum, at least as we currently understand it) Sequencer 1, despite its power in other aspects, is unable to predict the future. So in order to swing off a 4PPQ clock, it has to make an educated guess as to when the next clock is going to come, in order to determine the correct time to delay the swung clocks. Long story short: we go from our super-tight clocking from external sources to an averaging algorithm. Averaging is not super-tight. Far from it. It is, in fact, the opposite of tight. This doesn't make me happy.

2. In order for Sequencer 1 to clock against higher resolution clocks so it doesn't have the averaging timing slop (24PPQ and 48PPQ, or Roland and Korg DIN sync, respectively) it needs a gearbox on the front end. And you need the ability to send it a high resolution clock.

3. If you have the ability to send it a high resolution clock, chances are fairly good that you also have the ability to send it a swung 4PPQ clock.

At this point, I'd be okay with just saying "QED," but I'll go a bit further: what is your goal, exactly? If your goal is to use some other device than Sequencer 1 as the master clock, it should be noted that clocking, like AD/DA conversion, is not something you want to skimp on. We can add a ginned-up gearbox and averaging algorithm on the front end, but you'll lose timing accuracy. It would be better to ensure that your master clock, whatever it is, has the ability to generate a master swing. Your best choice is the Inner Clock system. Your second best choice is Silent Way Sync. If you'd prefer to not rely on your DAW, there are several master clocks in Euro that can send swung 4PPQ.

The solution, as I see it, is to have the following settings for external sync: 4PPQ No Averaging (how it works now), and 4, 24, and 48PPQ With Averaging. You'd have to choose the one appropriate to your use case. This solution sucks, honestly. But it's a solution.
Bogus
Curious if anyone else out there is having troubles getting their Sequencer 1 to clock/reset properly with Pamela's Workout. I've tried everything and no matter what it seems that the reset just will not hit at the right time.

When I clock the Sequencer 1 with my Time Runner for instance the sequencer loops perfectly. But with Pam the reset almost always hits late causing an elongated first note.

Stranger still is that when I record Pam's channels as audio they come out looking perfectly fine, no drift in either the clock or reset channels seems to be occuring.
granville
Am I the only person having problems with the ALT to reset pattern function?

The reverted pattern starts from the moment I select it rather than in time (as when changing patterns normally). It behaves this way with both internal and external clock.

I want this feature to work, it'll be so useful... Can someone else check pls?
Crandall1
granville wrote:
Am I the only person having problems with the ALT to reset pattern function?

The reverted pattern starts from the moment I select it rather than in time (as when changing patterns normally). It behaves this way with both internal and external clock.

I want this feature to work, it'll be so useful... Can someone else check pls?


Congratulations! You found the first bug in 1.2!!!

(I was trying to make that sound more fun than it is.) Fix incoming.
cranleigh
Still having enormous amounts of fun with my Seq1. This may be covered elsewhere, but is there a way, when the external clock stops and starts again, to set the Seq1 to default to restarting at step 1 rather than whatever step it was on when the master clock was last stopped?
cranleigh
Another feature request for the pile: I think this was mentioned earlier in the thread, but it would be great to have a way to offset the steps of a sequence, so that what was the 3 or 4 or whatever could be shifted back to being the 1. I find myself restarting sequences sometimes and realizing that the beginning of a beat no longer lines up with that of a sequence. Sometimes this can be serendipitous techno goodness, mind you... SlayerBadger!
ben_hex
After a short time with the sequencer 1 I feel I'm really starting to learn and love it. It did take a short while to get to grips with where the basic things are before exploring the other mass of features but it's obviously no analogue 8 step, 8 knobs quick and simple sort of thing.

I've been making notes and trying things for my video of the module and it really is immense! I encourage anyone on the fence to grab one thumbs up
renasent
cranleigh wrote:
Another feature request for the pile: I think this was mentioned earlier in the thread, but it would be great to have a way to offset the steps of a sequence, so that what was the 3 or 4 or whatever could be shifted back to being the 1. SlayerBadger!


This would really be good, especially once the randomize feature comes into play. I too often find sequences that sound even better starting on steps other than the first.

With regards your question about restarting on the first step once the clock starts again. This would also be good but don't know if it would be possible because how would the sequencer know it just wasn't a long pause in the clock? I think the reset has to be used for this.

I love the reset in on the AD. It is pretty infalible because it simply tells the sequencer to go to the first step upon the next clock signal. This allows for imperfectly timed restart triggers. If it was set to restart immediately then if the trigger was slightly behind the main clock then it has potential to glitch.
cranleigh
renasent wrote:
cranleigh wrote:
Another feature request for the pile: I think this was mentioned earlier in the thread, but it would be great to have a way to offset the steps of a sequence, so that what was the 3 or 4 or whatever could be shifted back to being the 1. SlayerBadger!


This would really be good, especially once the randomize feature comes into play. I too often find sequences that sound even better starting on steps other than the first.

With regards your question about restarting on the first step once the clock starts again. This would also be good but don't know if it would be possible because how would the sequencer know it just wasn't a long pause in the clock? I think the reset has to be used for this.

I love the reset in on the AD. It is pretty infalible because it simply tells the sequencer to go to the first step upon the next clock signal. This allows for imperfectly timed restart triggers. If it was set to restart immediately then if the trigger was slightly behind the main clock then it has potential to glitch.


Good point -although maybe there would be a way to build in a user-definable timeout for that? So that, after the sequencer hasn't gotten a clock signal for, say 10 seconds, it then resets to being ready to start again from the top?
vathan
Just received a fresh Sequencer 1 last night, and I have to say that it's probably going to ruin me to all other sequencers in the euro format. After a quick read through the manual over the weekend and playing with the device for a night, I was pleasantly surprised to find anything I was looking for rather intuitively. Not bad for such complex device. Well done!
pinky snare
The S1 looks super fun and tempting (especially since I already am familiar with this style of sequencing from elektron), but anyone have any thoughts on a direct S1 vs metropolis comparison??
I know they are different beasts but I'm in the market for either so would be interesting to hear anyone's opinions..
StoneLaw
I have both the seq-1 and metropolis and they are very different sequencers for different uses.

The metropolis for one doesn't save patterns.... it has one pattern that you alter with sliders It can only do 8 notes a sequence so it's a touch limited but you can get a lot of fun patterns out of it by controlling aspects of it via the aux inputs or resets etc. I like the metro for live jamming and for coming up with ideas when I'm writing a song.

The seq 1 is more like the analog 4... it can store 64 four measure patterns and it saves them on power-down. You can even transfer them to the computer easily. It's way way more powerful than the metropolis but also slower and less experimential (experimental in the way that on the metropolis you play with it until you get something cool, on the seq 1 you more or less have to actually write your music with notes on a keyboard etc.)

Not that one is better than the other, but they are just totally different.
studionebula
Apologies for my lengthy absence from this thread. It seems like I've been busier than a one-legged man at an ass-kicking contest ever since the beginning of the year.

Apologies also for the problem with the ALT-reload feature; that was just a stupid oversight on my part. It has now been fixed. Before we push out the update, though, I'm adding a little enhancement to the CV outs, and I'll probably also add the CV->repeats mapping which I somehow managed to forget when putting together the v1.2 update. Figure on seeing a new version sometime early next week.

Thank you all for your ongoing enthusiasm!
flo
Key mode for the CV outs pretty pleeeeeease! wink hihi SlayerBadger! Guinness ftw!
daybed33
Help! Something weird happened... Maybe I pressed something wrong but now all my saved sequences are the same tempo, does the sequencer 1 save the tempo for the pattern your working on? If not I should have been jotting them down. very frustrating
cranleigh
Crandall1 wrote:
It's not a stretch to add a chord mode from there (where, if it's in chord mode, the CV outputs are all 1V/Oct, and you'd select + or - semitones), but we have a _lot_ on our plate to get it out the door in a quick-like fashion, so that may have to hold off for a later update. It is a very good idea, though.


If this could be implemented at some point that would be amazing -maybe 3 note chords using the Pitch out for the root note and CV outs for the added notes?

The Zaquencer (BCR2000 sequencing firmware) has a neat chord mode –it lets you use the knobs to scroll through various chord shapes. From its manual:

6.8. Chord
This parameter selects a chord from the chord pool.

The chord is being built upon the note present for this step in the NOTE PITCH parameter. With Chord=0 you get a monophonic note for this step (the default). The LEDs in the encoder ring display the semitones above the base note. The first LED is always on, as that reprents the base note from NOTE PITCH. Then for example if the 4th LED and the 8th LED are on it means that a chord is built upon the base note with 3 semitones and 7 semitones distance.
There are the following chords (LCD: 0-14);
0: base note only
1: 3,7
2: 4,7
3: 3,6
4: 4,8
5: 3,6,9
6: 3,6,10
7: 3,7,10
8: 3,7,11
9: 4,6,10
10: 4,7,9
11: 4,7,10
12: 4,7,11
13: 4,8,10
14: 4,8,11

Each is found again then with an octave of the base note down (LCD: 100-114) and with an octave of the base note up (LCD: 200-214).
flo
daybed33 wrote:
Help! Something weird happened... Maybe I pressed something wrong but now all my saved sequences are the same tempo, does the sequencer 1 save the tempo for the pattern your working on? If not I should have been jotting them down. very frustrating


Tempo is stored globally. Ya should read the friendly manual thumbs up wink
Crandall1
flo wrote:
daybed33 wrote:
Help! Something weird happened... Maybe I pressed something wrong but now all my saved sequences are the same tempo, does the sequencer 1 save the tempo for the pattern your working on? If not I should have been jotting them down. very frustrating


Tempo is stored globally. Ya should read the friendly manual thumbs up wink


Yup. There are very good reasons for this. Chief among them: this is meant for a modular synth environment, and as you're exceedingly unlikely to want to (or, for that matter, be able to) recreate a patch, we felt it was pointless. Also, we took in to account the general nature of live performance on modular synth, where people tend to have a more fluid idea of repeatability. We weighed the benefits of per-pattern tempo storage (almost none, in this context) versus accidentally hitting the wrong patch during a performance and kicking your track to the wrong tempo, and decided that tempo should be global.
granville
Hey is there a 1.2 manual? Webpage seems to still have 1.1.

Glad to hear the alt/reload thing is fixed, look fwd to the update.
Crandall1
Ah, shit. My mistake. I uploaded the 1.2 manual, but obviously didn't actually attach it to the page. Done and done.
zvonx
First night with my sequencer 1. Wow, what an awesome sequencer! I only made it half way though the manual before I started having way too much fun.

This is a Gypsy Scale, Tonic D, Walk Mode, Pitch Hold off. CV 1 out LFO to VCA modulation.

Pitch out to a Rubicon and Pittsburgh Synthesizer Block. Rubicon straight to VCA. Pitts to Mutable Shelves then into the VCA. I also used the shelves expander and ran the HP and BP out to a stereo out with the HP and BP panned hard left and right and added some delay.

Master clock was an Elektron Analog Rytm. Rytm sent din sync to a 606 which then clocked the Sequencer 1 through the LT out. Fun thing about clocking the Seq 1 from a drum machine is turning off steps on the 606. I start this demo at half time then add and remove steps eventually ending up with all steps being used.

[soundcloud url="https://api.soundcloud.com/tracks/198189890" params="auto_play=false&hide_related=false&show_comments=true&show_use r=true&show_reposts=false&visual=true" width="100%" height="450" iframe="true" /]
Crandall1
Happy Sunday, everyone! How about some new firmware? We've just put v1.2.3 up for download on the Seq1 page. Changelog:

Fixes:
-Reloading a pattern with the new ALT-click command no longer resets the step index.

Changes:
-The Pitch and CV1-3 outputs are now "live": the voltages now change while editing. Note that the CV Hold modes are respected. For example, if a CV's Hold is set to Gate, and the step's gate is turned off, the CV output will not change when its value is adjusted.

-There is a new CV mapping: Pulses. For input voltages near zero, each step's programmed Pulse count and Retrig mode is used. Positive voltages override the Pulse parameter; the higher the voltage, the more pulses per step, up to eight pulses for +5V. Negative voltages work the same way, but only the first pulse generates a gate output. In other words, negative voltages have the same effect as if Retrig is turned off.
ben_hex
Crandall1 wrote:
Happy Sunday, everyone! How about some new firmware? We've just put v1.2.3 up for download on the Seq1 page. Changelog:

Fixes:
-Reloading a pattern with the new ALT-click command no longer resets the step index.

Changes:
-The Pitch and CV1-3 outputs are now "live": the voltages now change while editing. Note that the CV Hold modes are respected. For example, if a CV's Hold is set to Gate, and the step's gate is turned off, the CV output will not change when its value is adjusted.

-There is a new CV mapping: Pulses. For input voltages near zero, each step's programmed Pulse count and Retrig mode is used. Positive voltages override the Pulse parameter; the higher the voltage, the more pulses per step, up to eight pulses for +5V. Negative voltages work the same way, but only the first pulse generates a gate output. In other words, negative voltages have the same effect as if Retrig is turned off.


Oh yeah!
Crandall1
Manual updated to 1.2.3 as well...
danielraffel
@Crandall1 i appreciate you guys not just updating the firmware but also reflecting the changes in the manual. thanks so much for being one of the few in euro who do both. ps really looking forward to the random/generative feature!
edgek8d
Great thread........so nice to see the developers working hand in hand with their customers. I don't own any Audio Damage hardware, YET, but do use several of their software plugins. They are excellent value, and Chris was overly helpful when I experienced a problem, and then extremely generous to compensate me for my "trouble".

I wouldn't hesitate concerning the quality of their stuff and their customer service was incredible. applause Keep up the good work Audio Damage!
phutureboy
danielraffel wrote:
i appreciate you guys not just updating the firmware but also reflecting the changes in the manual.

+1 applause
synthmind
Not entirely sure if this is the best place to ask this, but I think it's related..

I've been using the Seq 1 to control a couple CV synths and that's been great. But will soon be running another sequencer (along with the Seq 1 - not replacing it!) which is MIDI and want to clock them together. I'm wondering if it's best to have the Seq 1 be the master clock, and if so, what would y'all recommend as a CV > Midi clock converter? Or do I use an external clock that has both CV & Midi clock outputs? Thanks!

On a separate note, if Chris Randall is checking this out, do you anticipate the CV outs on the Seq 1 to be programmable via the keyboard - like the Pitch out? Would be way easier to program those CV outs when specifically using them to program notes (vs a LFO, for ex).

THANKS!
Crandall1
synthmind wrote:
I've been using the Seq 1 to control a couple CV synths and that's been great. But will soon be running another sequencer (along with the Seq 1 - not replacing it!) which is MIDI and want to clock them together. I'm wondering if it's best to have the Seq 1 be the master clock, and if so, what would y'all recommend as a CV > Midi clock converter? Or do I use an external clock that has both CV & Midi clock outputs? Thanks!

On a separate note, if Chris Randall is checking this out, do you anticipate the CV outs on the Seq 1 to be programmable via the keyboard - like the Pitch out? Would be way easier to program those CV outs when specifically using them to program notes (vs a LFO, for ex).


Generally speaking, if your system is Euro only, your "biggest" sequencer should be the master. In a hybrid system, or one that is controlled from a DAW, you're better off syncing your Euro from that. (With the caveat that there are no real rules here.)

I would submit that it is generally easier to sync Sequencer 1 from an MIDI sequencer than the other way around. You can even clock Sequencer 1 with audio clicks if you'd like. Anything over about 0.73V or so will cause a clock event. (For a sampling sequencer like an MPC, you could just sample a single clock from the output and sequence it right on the MPC; give it its own output and boom, done; DC issues notwithstanding, a click is a click.)

As for the second half of your question, I understand the general idea, but I couldn't for the life of me come up with a way to do it that didn't involve menu diving of a rather extreme sort, to the point where it would be fundamentally more trouble than it's worth. So, unless a bolt of inspiration strikes us, no, not likely.
flo
cry I want the key mode for CV as well. It doesn't even need to be via the keyboard, scrolling through notes (instead of CVs) would be awesome already. It's a bit fiddly to dial in with 500 values (though the CV hold mode is extremely helpful already, at least it doesn't have to be done on all steps now). I imagine this could be pretty straightforward, what issues are bugging you guys with it?

That said, thanks for another great update! SlayerBadger!

Regarding a pulse sample to clock stuff, this one from Makenoise works very well from a DAW or sampler: http://www.makenoisemusic.com/manuals/modular-pulse.WAV
flo
Just some suggestions for the key mode... Who knows, maybe it can strike some of that needed inspiration Mr. Green
  • Select it as an option "key" for each CV, just like "LFO" now... Could easily be just that instead of the "LFO+key" stuff etc. that Adam and me were thinking about earlier in the thread...
  • If it makes things easier, don't use the keyboard, just scrolling through notes in the respective fields - just like scrolling through the values right now
  • Not using the keyboard would also mean there doesn't need to be any fancy blinkenshow for these outs...
  • The transposition and key / scale settings and features would be global and thus automatically also apply to each CV out with an assigned key mode

  • Changing from CV to key would do the following to the values:
    • Quantize them to the closest key. The value to choose would be the actual value dialed in at a step (so the offset for LFO+, the amplitude offset for LFOx, the direct linear value, etc.).
    • Zero CV equals C, or the base key if a scale / key has been selected... Just like the Hz/V vs V/oct (see below), the base key that would be considered when changing this mode would need to be set before changing the mode. Not 100% sure on which would be better here (although with the latter way of working one could leave key and scale at C and chromatic to get the former result).

  • Changing from key to CV would also quantize to the closest CV value, automatically making it a Lin CV...
    • In both directions, the setting of Hz/V vs. V/oct is considered before the mode is changed and Volts would be interpreted and adjusted accordingly
    • This would allow quickly coming up with a sequence, then change the CV out to linear to throw some steps of the 12TET scale


As far as I can see, this would only require one UI change (an additional CV mode, the function is even there already!) and it would be "non-destructive" towards what people have done so far already. Anything that I missed and is giving you headaches?

Sorry for my stubbornness but this feature would make life so much easier for me... And it's a logical next step IMO thumbs up Plus the real time tap recording mode of course wink

Cheers! Guinness ftw!
Crandall1
Flo, that's generally what we're planning. (We've even taken a couple runs at it here so far.) Selecting notes for the CV outs will be a feature in the not-too-distant future.

Selecting those notes from the keyboard, however, is unlikely, as that would just require some weird shit, unless there's an idea out there nobody's had yet.

The only hiccup to what you're asking above is that the LFOs are generally added to the CVs _after_ all the sequence stuff (including notes, quantization, etc.) has been computed. My inclination is to have the option in the SEQ page for each CV output be Lin / LFO / LFO+ / LFOx / Note and leave it at that. In this case, the LFO for that CV would be turned off, and the value would be quantized per the scale / tonic / transpose values for the sequence.

The reason this feature has taken a while to add is that we have to be very, very careful at this point. This is a fairly complex chunk of code, and lots of facets are interdependent on each other; changing one thing affects lots of other stuff. So every feature we add, we need to consider, in order:

1. The usefulness / usability / UI aspect. Does it make the unit more complex or less? If it's "more," then the next question is "does the feature merit the added complexity?"

2. What else depends on this feature? For instance, just adding note quantizing to the CV values goes right up the stream, until you get to the point where every step is computed. (The headwaters, as it were.) Some things are far later in the process, and thus easier to implement (see: copy/paste functions, shit like that), as less realtime events are dependent on them.

3. Does it affect timing? We can't determine this until the feature has been implemented, but if it performs a block in any way, it's kicked to the curb. Perfect timing is the deal-breaker in this unit, and anything that adversely affects that, or performs an interrupt on the linear course of events doesn't happen.

4. We then return to #1 once we've implemented. Is it going to be a commonly-used feature or an edge case? If the former, is it easy enough to get to? If not, should we move things around in the menu tree to make it easier? At this point we rely on our own instincts and experience as musicians, and that of our testers, and see how things "feel."

So, as you can see, we are loath to just throw things at the wall and see what sticks. We are very deliberate in the process.

tl;dr: we'll definitely add this feature, but we're not sure how yet. Simple things get added quickly. Complex things like this take some time.
flo
Thanks a lot Chris we're not worthy For a second there I already thought you guys abandoned the idea altogether, but I definitely see the problem with using the keyboard. If that's the (only) thing that gets dropped I'm more than happy! SlayerBadger! One could think about alt+pressing the keyboard or something like that, but that would only work smoothly with one additional note CV, not two or three...

The "testing" procedure is also very sound, you guys sure take a lot of care in this! And I like that you value tight sync so highly hihi

Now that I got your attention, where in the list of possible feature additions is real time recording at the moment...? (hides)

Cheers and thanks again! nanners
studionebula
Crandall1 wrote:
tl;dr: we'll definitely add this feature, but we're not sure how yet. Simple things get added quickly. Complex things like this take some time.


Adding a small comment to Chris's excellent explanation of why this feature doesn't exist yet: as things stand right now, internally notes are represented as notes and octaves (i.e. numbers from 0 to 11 and 0 to 4) and CVs are represented as voltages as seen in the display (i.e. numbers from -500 to 500). This makes it easy to quantize notes to a scale, then apply the appropriate scaling (1V/oct or Hz/V), then spit out the voltage. In order to add a quantized note mode to the CVs, the code has to convert back and forth between those representations--potentially for for every step, for all three CVs, on the fly. There should be plenty of CPU horsepower available to do this, but building it up requires writing quite a bit of new code and touching quite a bit of old code. This is the sort of thing which makes software engineers nervous, particularly when they think about their code running on stage in front of large audiences. So, we are proceeding with caution, but yes, it will happen.
studionebula
phutureboy wrote:
danielraffel wrote:
i appreciate you guys not just updating the firmware but also reflecting the changes in the manual.

+1 applause

Thanks for mentioning it. Manuals aren't the most interesting part of this job, but they are something of a personal point of pride for me, so I appreciate the feedback.
synthmind
Thumbs up for being able to select notes via the CV outs in the not too distant future. Yeah keyboard would be nice, but not essential. Thanks CR.

By the way, I think I found one small bug. In the new Pulses / Retrig menu, it appears that the Octave read out in the lower left hand corner does not accurately reflect what octave that note is actually set to.
zvonx
I have been continuing to use a TR-606 to clock the Seq 1 to keep it in time with my traditional drum machines and synths.

Any suggestions on what I could possibly use to reset the Seq 1 when I hit stop on my master clock?

My signal chain is:

Analog Keys Master Clock sends Transport and Clock to Analog Rytm
Din from the Analog Rytm to 606
606 LT trigger out to Seq 1

I'm guessing I need to buy some midi clock module that can extract Clock and Reset from a midi signal?

Or is there an option to autoreset in the Seq 1?
flo
The RUN input is a dinsync style "high while running" gate. You could split the din sync lead to the 606 and use a breakout cable for pin 1 to go to RUN.

Or without anything just hit stop / start before hitting play on the master clock.

Cheers Guinness ftw!
SunSpots
Any chance we get knob recording? Or did that get implemented already?
Crandall1
@zvonx: As Flo said. You can use a Stackable or mult or whatever and send the run high signal to both RUN and RESET inputs on Sequencer 1, and that'll put you in perfect lockstep.

But yeah, you either need a dedicated module to break out the DIN sync, or some other solution, because what you currently have rigged is missing the key component.

@SunSpots: _IF_ we add real-time recording features (which is by no means certain, as it's a very big change to the architecture to add this), we'll also add knob recording. We don't currently have this feature on our timeline, though, as there are bigger fish to fry at this point.
sonicmayhem
Hey Chris

Quick question.

I have some pattern going on and for some reason CV1 lfo is spitting out nothing.CV2 and 3 work fine and strangely, other patterns have all 3 cv's working just fine. I checked the seq settings. All set to go. Im not sure what I could be doing wrong?
Crandall1
Assuming the setting for CV1 in the SEQ page is set to LFO or LFO+, and assuming the amp value on the first page of LFO1's settings is not 0%, it should Just Work. Never had a problem with that, nor a report of one.

Maybe save the pattern and try power-cycling your system?
nostalghia
Have you tried manually setting CV1 (and its LFO parameters including Shape and Length -assuming you don't have CV1 on Linear) on the pattern you're having the problem with to the same settings that work for CV1 on other patterns? Maybe it's just set to cycle so slowly that you can't hear its effect without listening for a minute or longer?

And what are you using the CV1 output to control? What do you have it patched to modulate?

Other things to check (apologies if you've already tried some or all):
Try swapping patch cables so CV2 out is patched to the same module input, and try using CV1 out to control something else-if you can make the problem move, might be a bad cable or input jack.
Make sure you don't have CV1 set to generate a sine LFO if you're trying to clock something with it, etc.
Do you have an O'Tool or multimeter you could check the CV1 signal with?
sonicmayhem
Hey guys

Yeah I checked all of those things. So strange. Only one pattern that wont let me use Cv1. All others and newly programmed work just fine.
Crandall1
Hey, I bet the hold mode of CV1 is set to something that requires a trigger or gate or something. Have a look at that.
continuum
DIN Sync RUN has to also serve as the reset to be compliant. On a modern device the rising edge of RUN is perfectly fine for reset - the wobbly old TR gear resets on falling edge due to shitty programming by Roland.
zvonx
using LFOx for the CV outs should I be able to generate a trigger pulse for a drum module?

Possibly with these settings:

Shape Rect 1/8
Length 1
AMP 100%
Range +
flo
Yes that works perfectly fine thumbs up Then make sure it's set to LFOx and use the CV on steps to program your triggers. The Seq 1 is also an awesome 5 channel trigger sequencer hihi
Crandall1
Any drum voice that triggers on the rising edge (which is most of them), you can just use the voltage steps. You don't even need to bother with the LFOs. If you're looking to _clock_ a drum machine (like, say, DrumDokta II) you can use an LFO, or just use the clock out. (Probably the easiest solution.)

If you watch one of my many, many Instagram or YouTube clips where I'm using Sequencer 1 to sequence drum sounds, I usually use the Accent output to trigger the kick, and just program voltage out of CV3 Out to trigger the snare (using a function generator like Maths or Mini Slew as the EG, set to exponential). For the hi-hat, it depends on what I'm trying to accomplish. I'll generally use an LFO for that, set to Ramp Down (if I want a bit of decay) or Curve Down (for a tighter sound), with the channel set to LFO+. In this manner, I can use a 2-step LFO for the main high hat part, then program the incidentals and ghost notes with the voltage, straight to the CV input of a VCA, no EG required.

The reason I use the Accent and raw voltage for the kick and snare, instead of an LFO, is so that the swing will be picked up, and the front panel Repeat functions will affect the kick and snare. (These don't affect the LFOs.)

But, as with most things on Sequencer 1, there are several ways to skin that cat.
zvonx
Thanks guys. I tried both ways and both work well. Different modules seem to trigger at different thresholds and depending on the CV value it can be used as an accent control (although a very small range and you have to spend a bit of time finding where each module's threshold is)

I'll try out the different LFOs on hats as you suggest Chris.

Might be worth adding to the manual some sort of drum triggering suggestions?
granville
Any news on the random/generative functions? There were all sorts of cool ideas floating around earlier in this thread, would be good to know whether (/when) any are likely to see the light of day... thumbs up
Crandall1
Adam is currently in his Time-Out corner. When he gets back, we're finishing ADM08, then we will return our attention to Sequencer 1's generative update. We do have to actually generate income occasionally to remain a viable concern. :-)
Bogus
Would it be possible to create some kind of menu inside the LFO parameters to allow chaining multiple LFO shapes/speeds for a single output? Something akin to the performer on Massive. For example, I could have a 16 step Sine followed by two 4 step Ramps then an 8 step Triangle?

I've got an idea how the menu could look for something like that, let me know what you think Chris. hihi
ngarjuna
I've been lusting after this guy for a while now, finally placed my order this morning. Very excited, so many features! One question (and I apologize if it has been answered in this thread already, I've only been keeping up with it a few weeks on and off but it's a fairly long thread): is there any particular recommended Micro SD device for keeping up with firmware updates? Or will pretty much any of the cheap-o's from Newegg do the trick?
zvonx
I use a SanDisk microSD to SD Memory Card Adapter.

I'd imagine just about anything would work fine.

Have you watched Chris's video on updating the firmware? Super easy
Crandall1
It comes with an SD card. All you need is the adaptor. (And some units come with an adaptor; the second order of SD cards we made included them unknown to us, so I just put 'em in the boxes.)

The SD card is also used to store patterns, scales, and globals, so it needs to be in the unit whenever it is in use. Basically, the only time you take it out is for firmware updates, or to back up your patterns/scales/globals.
ngarjuna
Crandall1 wrote:
It comes with an SD card. All you need is the adaptor. (And some units come with an adaptor; the second order of SD cards we made included them unknown to us, so I just put 'em in the boxes.)

The SD card is also used to store patterns, scales, and globals, so it needs to be in the unit whenever it is in use. Basically, the only time you take it out is for firmware updates, or to back up your patterns/scales/globals.

Okay cool, I'll wait until mine shows up to see if it maybe has an adapter already. But the adapters do seem to be widely available for cheap so no big there.
Dogma
Ive got a analog Keys that Im keeping for Overbridge and I like it...
Does anyone rock both the a4/keys and ad1? While it sems there is a lot of overlap and there seems to be in a few areas, the ad1 does a whole bunch of shit the elektron will never do and is actually modular in that its got cv/gate in whereas the keys doesnt....

Powerful combo or clumsy duo?
zvonx
I use both the ad1 and analog keys. each has their dedicated cv and gate mult. I have 7 oscillators so there can always be a use for 2 different sequencers.

The ad1 is much more powerful than the elektron sequencer.

My biggest gripe with the analog keys is - just playing the keyboard - if playing fast it seems to treat the playing as legato and doesn't retrigger envelopes and I can't seem to find any setting to adjust that.
Dogma
zvonx wrote:
I use both the ad1 and analog keys. each has their dedicated cv and gate must. I have 7 oscillators so there can always be a use for 2 different sequencers.

The ad1 is much more powerful than the elektron sequencer.

My biggest gripe with the analog keys is - just playing the keyboard - if playing fast it seems to treat the playing as legato and doesn't retrigger envelopes and I can't seem to find any setting to adjust that.


Hmm cool so it sounds like they gell well...Im coming from a rene which i love I just got room for a on sequencer to ruke them all and he ad1 looks to be made for that task much more than rene
phutureboy
When it's feature request time again I'd be very happy to see these happening:
- 12V gates
- ratchet 3 & 6 in addition to the current 1, 2, 4 & 8
- Euclidian algorhythms
VanEck
Any news about the generative update? Still happening? ETA? screaming goo yo
renasent
VanEck wrote:
Any news about the generative update? Still happening? ETA? screaming goo yo


I'd be really interested in hearing about this too. I would use this feature all the time.
Crandall1
Keep in mind that Audio Damage is only two people, and only one of us can code worth a shit. :-) It became obvious that the generative update was going to take much more time than we had originally intended; we had to put it on the back burner for a little while to develop some new products. Adam will return to Seq1 updates here in a month or so.

@phutureboy: No 12V gates, sorry. That's not possible with this platform. (Hardly anything in Euro does that, for electromechanical reasons that we have no control over, physics being what it is.) When you say "ratchet," I assume you mean "repeat"? Since the Repeat feature is a front panel control with labels, what you have is what you get; there's nowhere to put 3 and 6 step repeats. As for Euclidian stuff, mathematically those are simple, but I don't see a convenient place to put them.
phutureboy
Hi Chris, thanks for your reply.
Too bad for the 12V, so maybe 10V at least ? The Soundmachines RC1 allows 5V or 12V via a jumper on the back...
By rachet yes, I mean repeat, maybe we could get 3 and 6 by pressing shif+repeat 2 and shift+repeat 4, etc... ?
Re the Euclidian algos, if I find a place would you include them ?
Crandall1
I have a thought about how we might include Euclidian. It could use the CV outputs as triggers, and on the Sequence page where you assign the CV outputs, they'd go, like:

Lin / LFO / LFO+ / LFOx / Euclid

Or something like that. But I'll have to talk that over with Adam. That sort of thing is of questionable utility in this; it'd be neat, but would it be there just because it's neat? I don't know; have to try it and see, I guess. We also wanted to add a note mode to the CV outs, for the people that want to sequence chords, so we're getting in to some hairy-ass programming here that sort of defies the structure of the thing, and would require some re-architecturing.

So, it's not something we can just add for the fun of it; it would be a big feature that would require a lot of thought and testing. If others here think it would be useful, let us know. You're the first that has asked for anything of this sort, which is usually the purview of trigger sequencers.

Anyhow, regarding the voltage stuff, Adam would have to speak to the technicalities. I'd be in serious danger of talking out my ass if I were to speculate. As for alt-repeats, I don't think that's in the cards.
ngarjuna
Crandall1 wrote:
We also wanted to add a note mode to the CV outs, for the people that want to sequence chords, so we're getting in to some hairy-ass programming here that sort of defies the structure of the thing, and would require some re-architecturing.

So, it's not something we can just add for the fun of it; it would be a big feature that would require a lot of thought and testing. If others here think it would be useful, let us know. You're the first that has asked for anything of this sort, which is usually the purview of trigger sequencers.

Anyhow, regarding the voltage stuff, Adam would have to speak to the technicalities. I'd be in serious danger of talking out my ass if I were to speculate. As for alt-repeats, I don't think that's in the cards.

Is note mode for the CV outs something that's being actively worked on? Or something that required so much re-architecturing that it was not feasible? Just curious but that feature would get a lot of use by me.
Crandall1
ngarjuna wrote:

Is note mode for the CV outs something that's being actively worked on? Or something that required so much re-architecturing that it was not feasible? Just curious but that feature would get a lot of use by me.


Yes, that's a high priority; probably the single most requested feature that we haven't yet addressed. The reason it's a problem, as it was explained to me: the way the code was originally designed precludes sending the voltage values of the CVs through the quantizer, as it exists for the Pitch output. We _can_ do it, but we have to be super careful, as it requires re-writing the core engine where all the values are computed, and touches a whole lot of other code.

How we would like it to work: you'd select "NOTE" mode instead of LFO or LIN, and, in the same way you program CV values per step, you can dial in notes that will get sent through the quantizer.

How it will actually work: can't answer that yet. Adam has taken a couple runs at it already, but it gets in to Danger Close territory for a lot of other features.

Edit: I had another thought about Euclidian; we could just add them as LFO shapes, perhaps. I'll talk to Adam about it, but I think that may very well be a simple solution.
phutureboy
Crandall1 wrote:
We also wanted to add a note mode to the CV outs, for the people that want to sequence chords

Well not necessarily, I was only asking Euclidian to trigger rhythms, if note mode not possible personally I wouldn't really care... It would be sad to not have it because it's not possible to also do something else...
Crandall1 wrote:
As for alt-repeats, I don't think that's in the cards.

Well any combination of keys is fine by me...
Ras Thavas
Crandall1 wrote:
... Since the Repeat feature is a front panel control with labels, what you have is what you get; there's nowhere to put 3 and 6 step repeats...


Suggested back in the original generative update thread before the big MW data implosion; pressing Repeat 2 & 4 simultaneously could give a result of 3, and pressing Repeat 4 & 8 simultaneously could give 6. Seems logical, works with the front panel labeling, and preserves the ability to use shift Repeat for something else later if you want.
flo
Ready to take it out the rack for the note mode update hihi SlayerBadger!
echochorus
Looks very interesting, thank you!
stevenb
I've had the Sequencer 1 for a couple of weeks now, and I'm having an issue with pattern selection via CV input. According to the manual the pattern is supposed to be selected from the current bank, but in my case, the pattern selected is always from the A bank. For example, I am playing pattern D3. I navigate to the CV1(2) menu and select Pattern. I then plug in a DC voltage to the CV1(2) input. The pattern jumps to a pattern in the A bank. Happens with CV1 or CV2 inputs. v1.2.3.78 firmware. Any thoughts or suggestions?

Enhancement request - A way to program a sequence of patterns internally in the Sequencer 1. Let's call it a playlist.
Crandall1
Verified. I'll put it on the fix list for the next update.
Bogus
Ooo will that stepped voltage thing I suggested be added to the step CV feature with the next update? I'm keeping my fingers crossed Mr. Green
stevenb
Crandall1 wrote:
Verified. I'll put it on the fix list for the next update.


Awesome. Thanks!
cutterfiltoff
+1 for holding multiple repeat buttons for triplets!
Crandall1
cutterfiltoff wrote:
+1 for holding multiple repeat buttons for triplets!


You spelled "dotted eighths and dotted quarters" wrong. :-)
flo
I just had an idea - would it be possible that, in "play" mode (i.e., where you can repeat and ratchet manually), the ABCD buttons (plus ALT or something, otherwise it'd change the pattern bank) could "mute" the programmed gates, accents, slides and ratchets respectively? Would be nice to bring the programmed stuff in and out manually applause

Cheers Guinness ftw!
synthmind
I've got a clock issue with the Seq 1 I'm trying to figure out....
I'm using an E-RM Midiclock as my master clock and am using their modular whip to slave the Seq 1. The issue is that the Seq 1 is just running WAY faster than the other sequencer also connected to the Midiclock (which is connected via Midi). Is there a way to qualify what counts as a clock event with the Seq 1 or perhaps this is some issue I need to figure out with E-RM?
Crandall1
I assume you're using output 1 of the E-RM? It sounds like you're sending it DIN sync, which is 24 (or 48) PPQ. Sequencer 1 needs 1 pulse-per-clock 16th note inputs.

So, just set ChnMode for Channel 1 to ANALOG, then fool with the Divider value on the ANALOG settings page until you get the right result. Not having a unit, I don't know exactly what that value will be. In reading the manual, my feeling is that it will be the "4" setting. But their manual is pretty thin on data, so hard to say. You'll have to mess around.
synthmind
Thanks Chris. That was very helpful. DIN Sync setting was part of the issue. The other issue being that I wasn't doing this (and this is not in the manual for some reason):

"The auxiliary alternate function is Modular Analog Clock. Push the encoder while connecting power to set it up.
The display shows Euro for three seconds. This setting is non-permanent.
Clock rate is 8ppq, Reset pulse is positive."

I'm not sure where to find the Analog settings page, but I am at least getting both sequencers (Seq 1 being one of them) clocking together now! Yay!
ElCampesino
Is there an ETA for the next update? Looking forward to being able to select patterns from any bank using pressure points. stevenb already mentioned the issue in that regard. I'm having the same problem.
flo
No comments for this idea?

flo wrote:
I just had an idea - would it be possible that, in "play" mode (i.e., where you can repeat and ratchet manually), the ABCD buttons (plus ALT or something, otherwise it'd change the pattern bank) could "mute" the programmed gates, accents, slides and ratchets respectively? Would be nice to bring the programmed stuff in and out manually applause

Cheers Guinness ftw!
Crandall1
flo wrote:
No comments for this idea?


We have other plans for those buttons. :-)

Regarding the next update, it's coming. We're working on something else that, as such things go, took much, much longer* than we'd intended. Adam is going to order the boards for it next week, and once he's done that, he's going to do the next update, which will have that fix, plus a couple other new features that have been requested.

(* And by "much, much longer" I mean "we started it in December, thinking it would be in prototype by, say, early February, and look, here it is August, and it bears no resemblance whatsoever to the original idea! Yay, us!")
renasent
Crandall1 wrote:

Regarding the next update, it's coming.


w00t

Fantastic. I hope you are out of the woods with your other project now. Looking forward to seeing what it is.

Really hope the generative/random stuff will be on the Sequencer1 update.
suthnear
Is it poor form to ask here what the advantages of seq1 over the new arturia sequencer are? Or should this be a new topic?
renasent
suthnear wrote:
Is it poor form to ask here what the advantages of seq1 over the new arturia sequencer are? Or should this be a new topic?


I've got both and the Seq1's advantages are non-static patterns. You have cv control over all sorts of aspects of the sequence and this makes standard patterns really come alive.

All the arturia has to break up sequences is it's randomise feature but this is pretty poorly implemented. Each sequencer has its strengths but its the cv control I think that really sets Seq1 apart.

Once Sequencer 1 has randomise and generative abilities it will be an amazingly inspirational device. I think it is here where the advantages lie.
Crandall1
suthnear wrote:
Is it poor form to ask here what the advantages of seq1 over the new arturia sequencer are? Or should this be a new topic?


Yes, it's poor form. But that said: one is a piece of Chinese crap that mostly works most of the time, and the other is a handmade-in-Colorado high-end bespoke Eurorack sequencer. Of course, my opinion on the matter might be biased.
VanEck
Crandall1 wrote:
suthnear wrote:
Is it poor form to ask here what the advantages of seq1 over the new arturia sequencer are? Or should this be a new topic?


Yes, it's poor form. But that said: one is a piece of Chinese crap that mostly works most of the time, and the other is a handmade-in-Colorado high-end bespoke Eurorack sequencer. Of course, my opinion on the matter might be biased.


Currently only 1 of the 2 comes out of the box with generative functions though... hihi
Crandall1
VanEck wrote:

Currently only 1 of the 2 comes out of the box with generative functions though... hihi


Well, that depends on what you mean by "generative." Random step? Check. Chromatic transpose as a CV target? Check. Scale quantization? Check. Three tempo-synced LFOs with a whole heaping pile of randomization? Triple check. Honestly, everything else is just us getting fancy with those four things.

If you mean "randomly destructively fill a pattern," well, you got me there. But it's coming.

EDIT: I might be coming off as a little cocky here; apologies for that. I won't edit it out, but in reading back, I think the fact that I'm speaking tongue-in-cheek might not come through. Rest assured I was just taking the piss. The Arturia folks make some fucking nice kit.
suthnear
Chris, apologies for making that post. The reason why I made it here rather than a new topic was that I was after seq1 advocacy and I figured that a new topic would probably result in a fair bit of drive-by posting and I knew that I'd get better SNR here.

I am a sequencer idiot. I like the idea of them but have not really got on with them in practice (so far). I can pretty much tell what the arturia sequencer does (and am aware of its shortcomings), but I know that yours would be far more considered and deep. And renasent's post was very helpful in this regard.

Anyway, again apologies. I may make a new topic at some point so you may consider this question closed.
Crandall1
Oh, no need to apologize. This is Muff's. A third of this thread is me defending Seq1 against drive-by Metropolis comments, something I shouldn't have to do because they're so different. *shrug*

I'll say this much: the Beatstep Pro is probably way better for drums than Seq1; it's kind of difficult to program drums on Seq1, but it can be done. And obviously Beatstep Pro has more lanes. That I can't deny. Sequencer 1 is, as you say, quite a bit deeper, but you have to dive a bit. Beatstep Pro is new and therefor rather buggy, while Seq1 is pretty solid at this point (other than that one outstanding pattern switch over CV bug referenced above.)
renasent
Crandall1 wrote:

If you mean "randomly destructively fill a pattern," well, you got me there. But it's coming.


It's peanut butter jelly time! nanners Rockin' Banana!

I love how you can make a pattern, then constrain its notes then apply cv to shift the sequence all over the place, all in key. This is the kind of stuff the arturia can only dream of. The arturia doesn't even have a reset in FFS.

I nearly didn't buy the arturia because of previous bad experiences due to buggy products, both software and hardware.

I definitely see the BSP as more of a straight sequencer, whereas the Seq1 is more interactive and creative. You can end up with really dynamic and exciting patterns and have synced lfo's making all sorts of good stuff happen. screaming goo yo
Bogus
renasent wrote:
I love how you can make a pattern, then constrain its notes then apply cv to shift the sequence all over the place, all in key.


Educate me please : o
Crandall1
Bogus wrote:

Educate me please : o


Set a scale and tonic of your choice (just for instance, Melodic Minor and D), then make a pattern of notes that is pleasant to you. Set CV out 1 to "LFO." Set LFO 1 to "Rand Step," and adjust the amplitude to like 25% or whatever. (This will necessarily be to taste, following the next step.)

With a short patch cable, jump CV1 Out to CV1 In, and set CV1 in to "Transpose."

Now, random notes all in D melodic minor. The amp and step of the LFO determine the randomness. You can actually do this with a two-step sequence, where the first step has a gate and the second one doesn't. Make a second LFO of Rand Step and send it to CV2 In, and set that input to "step," and put the sequencer in "Halt" mode, and you have an entirely random sequence, all in key, with two steps and a couple parameter assigns.

This sort of self-patching of Seq1 is where it really shines, and the majority of the "Generative" features we plan to add are just macros for doing these things that can already be easily patched. So, like I said, Sequencer 1 is already perfectly capable of doing most of the things you guys want in a generator; we're just endeavoring to make them more obvious.

EDIT: I feel like I should make a tutorial video to show off these tricks. Is that something people would be interested in? "Advanced Programming of Sequencer 1" or something?
Bogus
Could this method be applied to a single step in the sequence while leaving the others in tact?
Crandall1
Bogus wrote:
Could this method be applied to a single step in the sequence while leaving the others in tact?


Absolutely. Just use the LFOx feature, and "turn on" the LFO outputs with the voltage-per-step for that output. Or use the accent out and an external logic gate to trigger it, or whatever. Lots of ways to pull that off.

One thing to remember with Sequencer 1 is that most obvious things are CV targets, and it has three extremely powerful LFOs; we tend to think "well, you can do pretty much anything" but if you don't actually have the unit, that might not be immediately obvious.
justin3am
It's crazy how flexible this sequencer is. As Chris mentioned, a lot of cool things can be done by self-patching the CV outputs back to the CV inputs to use the LFOs or CV sequencers to change internal parameters.

I've only saved like three patterns, 'cause I can get so many variations on a single sequence by using the ratchets, repeats and pulses.

I'm sure Chris is sick of my 'Demos' by now hihi , but this whole track was done with a single pattern, just repeating certain sections and using CV to control ratcheting. Not the most intersting sounds but lots of rhythmic variations.
[soundcloud url="https://api.soundcloud.com/tracks/203678387" params="auto_play=false&hide_related=false&show_comments=true&show_use r=true&show_reposts=false&visual=true" width="100%" height="450" iframe="true" /]
nostalghia
Crandall1 wrote:
I feel like I should make a tutorial video to show off these tricks. Is that something people would be interested in? "Advanced Programming of Sequencer 1" or something?


Yes please! It's peanut butter jelly time!

Have had mine for months now but would not have thought to try the self patch you described (going to play around with that this weekend).
I'm sure there's plenty of other things I have yet to do with the Seq 1 as well. Tips and techniques "beyond the basics" are always welcome!

Also, would like to ask (possible someone else already has and I missed it): would it be possible in a future firmware update to add a "rotate" feature which would (during playback) shift all notes in a sequence forwards or backwards one step per click of a rotary knob?

I use this feature often in my Schrittmacher (rackmount hardware sequencer from Mannikins).
Here's how Rotate is described in the manual: "Using Rotate you shift all steps of a line to any position to the left or right. Since the step modes (play, mute/hold, skip) are not shifted, this function is also useful for live operation."
continuum
Never mind.
Bogus
Crandall1 wrote:
Bogus wrote:
Could this method be applied to a single step in the sequence while leaving the others in tact?


Absolutely. Just use the LFOx feature, and "turn on" the LFO outputs with the voltage-per-step for that output. Or use the accent out and an external logic gate to trigger it, or whatever. Lots of ways to pull that off.

One thing to remember with Sequencer 1 is that most obvious things are CV targets, and it has three extremely powerful LFOs; we tend to think "well, you can do pretty much anything" but if you don't actually have the unit, that might not be immediately obvious.


Thanks Chris! I didn't even realize LFOx worked like that.
Bogus
I'd like to use this double post to remind everyone:
srsly never
suthnear
I'd also be interested in an advanced video, thanks
Slomen
Me too thumbs up
ngarjuna
Crandall1 wrote:
EDIT: I feel like I should make a tutorial video to show off these tricks. Is that something people would be interested in? "Advanced Programming of Sequencer 1" or something?

Hells yeah! I've learned a ton of cool tricks from this thread already.
daybed33
Advanced video please! Would love it.
SlyFrank
Crandall1 wrote:
Set a scale and tonic of your choice (just for instance, Melodic Minor and D), then make a pattern of notes that is pleasant to you. Set CV out 1 to "LFO." Set LFO 1 to "Rand Step," and adjust the amplitude to like 25% or whatever. (This will necessarily be to taste, following the next step.)

With a short patch cable, jump CV1 Out to CV1 In, and set CV1 in to "Transpose."

Now, random notes all in D melodic minor. The amp and step of the LFO determine the randomness.


I've been playing around with this tip this afternoon, and all pretty straightforward (and cool), but I'm noticing something unexpected - not sure if it's me being dumb or something else (probably the former).

The CV1 in set to Transpose is ignoring negative voltages from the CV1 out LFO (no matter what the shape of the LFO is). Using alternative targets for the LFO that respond to negative voltages, like gate length, works fine - the gates go from shorter than normal to longer. I also further noticed that with a sine wave with +/- setting the target spends longer at "no change" or, I guess 0V, whereas with + setting it moves up from 0V immediately upon hitting it, which all makes sense for a target that doesn't respond to negative voltages and those voltage ranges.

Using all sorts of AMP ranges. Setting of - means that nothing happens. Transpose is behaving like a target that doesn't respond to negative voltages. And I have the sequence set to a mid-frequency one-octave line at Octave = 2. Plenty of room for my Osc to go down too; if I change the sequence down using the octave buttons, those low notes appear, so the frequency range is fine.

I went into Alt/Seq and monkeyed with the Transpose setting, and that doesn't help either, although I didn't expect it to - I always figured that's a manual way to transpose? hmmm.....
REwire
I'm having trouble clocking this from host midi. Both used Silent Way Trigger to send clock and reset and also the STG Sync24 bus. the same thing happens every time: The first note is always sustained, no matter what the gate time is set to. Loops fine as it should, just messed up first note.

Does getting the Reset and Start command at the same time mess with this? Silent Way Trigger has settings to delay or stop the first clock pulse to stop interference but this does nothing. Should I invert the Reset pulse to the SEQ 1? Does it want high to low vs low to high?

Thanks, Dan
ranzen
Quote:
EDIT: I feel like I should make a tutorial video to show off these tricks. Is that something people would be interested in? "Advanced Programming of Sequencer 1" or something?


Please do! I love the seq1 & having these advanced tricks in one place would be really helpful!
Crandall1
REwire wrote:
Does getting the Reset and Start command at the same time mess with this? Silent Way Trigger has settings to delay or stop the first clock pulse to stop interference but this does nothing. Should I invert the Reset pulse to the SEQ 1? Does it want high to low vs low to high?


When using Silent Way, use the Sync version, not the Trigger one. You can jump the Run and Reset inputs on Sequencer 1 with a Stackable, and here's a screenshot of the settings that will give you perfect sync. (Note that the "Offset" setting will be dependent on your system.)

REwire
Thanks Chris. I was using Sync (mistakenly said Trigger) and multing the Reset and Run together and changing a few parameters seems to have helped.

But, new problem. My LCD screen is dark. Seems to come on only for moments when I am pushing the encoders or buttons and goes dark when I let go. Repowered just now and tried 5v on rail to see if that helped. nothing. Is it defective?

EDIT, I can get the LCD to come on when I am squeezing the front top panel and PCB by the LCD. There must be some broken connection (?)
Crandall1
REwire wrote:
Thanks Chris. I was using Sync (mistakenly said Trigger) and multing the Reset and Run together and changing a few parameters seems to have helped.

But, new problem. My LCD screen is dark. Seems to come on only for moments when I am pushing the encoders or buttons and goes dark when I let go. Repowered just now and tried 5v on rail to see if that helped. nothing. Is it defective?

EDIT, I can get the LCD to come on when I am squeezing the front top panel and PCB by the LCD. There must be some broken connection (?)


Yes, this needs repair/replacement. I'll contact you offline.
phutureboy
Crandall1 wrote:
Is that something people would be interested in? "Advanced Programming of Sequencer 1" or something?

thumbs up
stevenb
I had a look at the enhancement posts in this forum and couldn't find these so here I go:

1) I'd like the sequencer to power up in the last mode it was in. This would include bank and pattern as well as play, or stop mode. Yes, I understand you'd have to cache these parameters as an ongoing background task.

2) I'd like a "delete all patterns" choice to clear out all patterns to default.

3) I'd like a user defined default pattern that gets loaded when I clear a pattern.

BTW, I just love this sequencer.

Thanks,
Steven
Slomen
stevenb wrote:

1) I'd like the sequencer to power up in the last mode it was in. This would include bank and pattern as well as play, or stop mode. Yes, I understand you'd have to cache these parameters as an ongoing background task.


I also really want this thumbs up
flo
stevenb wrote:
3) I'd like a user defined default pattern that gets loaded when I clear a pattern.


This would be great, I've asked about it many pages ago and there was some enthusiasm for it from Adam:

studionebula wrote:
flo wrote:
Now that you're getting close, some further wishful thinking hihi

I'd love if there was a way to save an "init" pattern, so that deleted or new patterns will default to that setting...

Thanks, that's an excellent idea. I suppose the way it would have to be done would be via a special command somewhere, possibly in the Globals pages, which said "save the current pattern as the default."
ranzen
Hi, I just have a little question so I didn't want to start a new thread:

When using CV for pattern change the seq-1 doesn't stay in the same bank:

i.e.: I'm in bank C pattern 3 and want to switch to C-2. Applying and LFO to CV in: when the LFO is high the pattern switches to bank A, pattern 1. I thought it should stay in the same bank?

confused

Cheers
Crandall1
Yeah, this is a known bug. Currently, CV pattern switching will only switch bank A (where it is supposed to switch in whatever bank you have active.)

This will definitely be fixed in the next update (which is actually coming soon-ish.) Along with the CV-to-transpose only responding to positive voltages and a couple other things that have turned up.
ranzen
@Crandall1 alright, thanks for clarifying!
xonetacular
you know I initially wrote this off from the price and I thought it would be a pain to program and not be very immediate

I'm glad I decided to pick one up on an impulse- just wow... I don't know what I'm doing yet and it is very quick and inspiring and super hands on/fun to use and spitting out sequences I couldn't dream of getting from my other sequencers.

now if there is an update in the future that would let me program chords that would be just nuts
flo
Use the CV outs for further v/oct (for chords) thumbs up

Still waiting for the "key mode" hihi
stevenb
Another feature request:
I'd like the ability to change the tempo with a knob from the "home screen" when the clock is set to internal. it's kind of a bother to navigate to the Tempo menu to do this.
atimbral
I've looked through this thread and the manual, but can't seem to find out if the internal clock can be vc'd from the CV1-3 outputs. Doesn't look like it, going by the CV1-2 menu options, but this would be really great, saving having to do this with an external clock. Am I missing something?

If not, could this be a feature request?
VanEck
atimbral wrote:
I've looked through this thread and the manual, but can't seem to find out if the internal clock can be vc'd from the CV1-3 outputs. Doesn't look like it, going by the CV1-2 menu options, but this would be really great, saving having to do this with an external clock. Am I missing something?

If not, could this be a feature request?


Not sure what you mean. What type of modulation are you trying to perform to the clock? You could route one of the CV outs directly to the clock input or reset input, no need for the clock to be selectable as one of the CV in's. Unless you are talking about clock dividing/multiplying. If that's the case, then no there are no built in functionality for that. I believe it was mentioned before from a couple people requesting it, and I don't think it was regarded as something in much demand, as there are already a lot of options out there as far as modules for clock manipulation goes. Could just route the CV out to an RCD, etc.
Bogus
atimbral wrote:
I've looked through this thread and the manual, but can't seem to find out if the internal clock can be vc'd from the CV1-3 outputs. Doesn't look like it, going by the CV1-2 menu options, but this would be really great, saving having to do this with an external clock. Am I missing something?

If not, could this be a feature request?


You have to physically patch CV outs to CV ins for this. I believe Chris and Adam decided this to encourge further modulation of the output signals with other modules.
atimbral
Just talking about modulating clock speed with a different voltage level (Linear Mode) on every sequence step, to vary the time spent on each step in an easily adjustable way.
atimbral
Quote:
You have to physically patch CV outs to CV ins for this.


Yes, that's my assumption; I'm just not sure which menu assignment on the CV ins would get what I'm looking for. (wish I had one to try it!)
Bogus
Press Alt + 06 (Step) and keep clicking an encoder in until you see the word 'HOLD' appear on the right side of the screen. Select the step you want to edit and use to rightmost encoder to adjust for how many pulses that step will hold.
atimbral
Quote:
Select the step you want to edit and use to rightmost encoder to adjust for how many pulses that step will hold.


hmmm... Well, according to my understanding of the manual, (and to reiterate, I don't yet own one of these; otherwise I'd try your suggestion) this method would get you a step that is at maximum 8 times longer than the previous.

Quote:
5.1. Multiple Pulses per Step
Steps can now be programmed to repeat up to eight times. The Gate output can either fire on each repetition, or only once.


What I commonly use this capability for on the 16X4 sequencers in my DIY system, is to set up a flurry of short notes followed by much longer ones. One of the CV rows is usually dedicated to control clock speed from very quick to very slow. I was just curious if I could do the same with the Sequencer 1 without going to an external clock.

Either way, it's certainly not a deal breaker. This thing is so capable and sophisticated that I'll almost certainly end up getting one!
Bogus
You could ratchet some steps, hold others, and keep some standard. They will be perfect divisions off the clock though, not arbitrary ones selected by manual CVs
atimbral
Quote:
You could ratchet some steps, hold others, and keep some standard.


Thanks! Good suggestions to add rhythmic interest to a sequence.

Still, wouldn't it be nice to look at the CV1 (or 2) Assignment screen, and in addition to Gate Length, Step Position, etc., see Int Clock Rate. CR, Adam; possible?
flo
atimbral, many, many pages back, there was some talk about something similar... For posterity:

Crandall1 wrote:
flo wrote:
Those LFOs look like a ton of fun. I reckon you routed it to CV1 out? Can it be routed to any of the CV outs?


There are three LFOs, one for each CV out. At shipping (and I'm not saying this will always be the case, just the v1.0.0 version of the software) if you want to route one of the LFOs to an internal parameter, you need to patch it (with a patch cable) to one of the CV inputs.

So, tl;dr: LFO1 goes to CV1, LFO2 goes to CV2, and LFO3 goes to CV3.


studionebula wrote:
flo wrote:
Ok... So no internal vibrato added to the V/Oct... Thanks for the clarification!

Would be really cool if in a future update they could be freely routed (to the outputs, but maybe also to internal functions?) - that way in addition to my vibrato fetish, you could for example route all three to CV1 out for some whackyness etc...

Cheers!


Okay, you just touched on one of my patching fetishes, which is to combine two or more LFOs to create complex modulation signals. Yeah, I want that now, too.

As Chris said, for the initial release each LFO is hardwired to its corresponding output, but that could change in the future. Currently we are entirely focused on completing and delivering a solid product without letting feature creep derail us from that goal. However, now that we've been working with the system for awhile (including the LFOs), I have verified that we have plenty of horsepower left in the CPU to do other things in the future. I really don't want to go down the road of selling a product based on promises of what it will be someday, but I will say that it's a safe bet that this sequencer will gain features over time. Which features and when, exactly? No way to say. Maybe we'll have to take polls or something to establish what people most want after they've spent some time with version 1.0.0.

In any case, thank you all for your feedback and enthusiasm!
Bogus
atimbral wrote:
Quote:
You could ratchet some steps, hold others, and keep some standard.


Thanks! Good suggestions to add rhythmic interest to a sequence.

Still, wouldn't it be nice to look at the CV1 (or 2) Assignment screen, and in addition to Gate Length, Step Position, etc., see Int Clock Rate. CR, Adam; possible?


Until something like that is added your best bet for freely modulating clock would be to feed the Seq1 the square output of an LFO. Then, to adjust tempo, you could use the stepped voltages of one of the Seq1 CV output channels to modulate the LFOs frequency.
Crandall1
Yeah, what Bogus said. If you want to modulate the tempo, the easiest way is to use a separate clock source and modulate that. We couldn't come up with a compelling reason to add clock "drift" as a modulation target when it's so much easier to do elsewhere. If Seq1 was a standalone, it'd be a different story, but in the modular environment, well, you know.

Note that Seq1 doesn't have averaging on the clock input like many sequencers. One pulse = one step, no math. The reason we don't like averaging is that if your clock source has swing, trying to clock something that has averaging essentially removes the swing and replaces it with this semi-unpleasant loping. I prefer to have direct control over the stepping, speaking as a musician and not the developer, for specifically the reasons that atimbral mentions. I often clock Seq1 with the Trigger plugin from the Silent Way suite, and just use 16th note MIDI notes. Then I can apply one of the multitude of groove templates I've made in Live to it, no fuss, no muss, perfect lock.
flo
Speaking of it, an additional 24ppqn setting for easy din sync integration would still be welcome thumbs up
RickyT
Crandall1 wrote:

@schege: That same exact thing has bit me with RCD over and over again. I always forget it has that behavior, and I'm like "why is it offset?" Grrr.


I've noticed this as well with the QCD. It's a QCD problem im guessing?

The weirder part is instead of using the RESET i'll use CV3 LIN set to 500 on step 1 to reset my QCD but as soon as i add swing on the Seq1 it makes my QCD triggers ratchet!

Curious if this is a QCD behavior or Seq1? I can record a video as well.
DeWalta
Yeah, unfortunately many sequencers and clock dividers out there can not handle swung clocks. I'm loving the sequencer 1 for the ability to deal with step per step sync, what Chris was explaining earlier here. It's also tight as f***. Why do the QCDs or even circadian rhythms not sync properly to a shuffled clock? Why don't other sequencers out there DO NOT use the good ol "one pulse = one step - no math" approach??

Really looking forward to the generative features as well, even though I've been using the SEQ1 with offset attenuators into the CV inputs live on stage to generate "alive" changes to my saved sequences, only when wanted with direct access to the offset knob.

RickyT wrote:
Crandall1 wrote:

@schege: That same exact thing has bit me with RCD over and over again. I always forget it has that behavior, and I'm like "why is it offset?" Grrr.


I've noticed this as well with the QCD. It's a QCD problem im guessing?

The weirder part is instead of using the RESET i'll use CV3 LIN set to 500 on step 1 to reset my QCD but as soon as i add swing on the Seq1 it makes my QCD triggers ratchet!

Curious if this is a QCD behavior or Seq1? I can record a video as well.
Bogus
Generative please come soon :-)
Crandall1
Hey, all:

New firmware day! We have just published v1.2.4 of the Sequencer 1 firmware. It is available on the Sequencer 1 product page. Changelog:

Fixes:
-Swing now works the way swing is supposed to work, i.e. the correct steps are lengthened.

-CV-induced pattern switching now works within all banks, rather than just Bank A.

-CV-induced pattern switching remains active when the transport is stopped.

-CV-induced transposition now responds to negative voltages

-The octave indicator now updates correctly on the Pulses/Retrig page of the Step pages.

-Mapping CV2 to Pulse Count may have been broken.

-The Measure button now blinks when every fourth step is played, starting with the first, regardless of Stepping Mode.

Changes:
-The hold time for long button presses has been reduced from 500msec to 375msec.

-There is a new Global setting, "Auto-Reset". The default value is No. If this is changed to Yes, the transport will reset to the first step of the pattern when the external Play signal falls from on to off. Hence when the Play signal turns on, the pattern will always start with the first step.

-When the system is in "idle" mode, the Note buttons can be used as a mini CV keyboard. The Gate output is asserted when a Note button is pressed, and the Pitch CV output is set to the appropriate value. The Octave buttons also work as expected. The Scale and Tonic settings of the current pattern are ignored.

-When a pattern is being edited, the ALT button can be used to automatically advance from one step to the next as notes are entered. If the ALT button is held down when pressing a Note button (or, more specifically, if it is held down when the Note button is released) the current edit step is advanced to the next step in the pattern. Only steps with their Gate turned on are used, and the Stepping Mode of the pattern is ignored.

A quick note about Auto-Reset:
I asked Adam for this specifically for me (one of the perks of being co-owner of the company, I guess). I use Silent Way Sync to synchronize Seq1 to Live, with a MOTU Ultralite, and while it worked in general, there was some hackery that had to take place to get a good sync. So I asked him for this minor change to the operation so that I could use a standard 2-cable sync/run connection, and the unit would reset when it was started.

I've included a screenshot below of the correct settings for Silent Way for perfect two-cable sync. (Note that "1st Delay" is on, as Seq1 needs a few milliseconds to figure out that it's playing and such, the PPQ is set to 4, and that the correct "Offset" value is unique to your system.) I don't have any other sync methods to check this with, so I don't rightly know how it will respond to other stuff. Your mileage may vary, but I think this will make things a bit easier if you're using Silent Way Sync. Just run the clock output to the clock input of Seq1, and the run output to the Run input, and make sure that "Auto Reset" in globals is set to "On" and you're good to go.

flo
Crandall1 wrote:

-There is a new Global setting, "Auto-Reset". The default value is No. If this is changed to Yes, the transport will reset to the first step of the pattern when the external Play signal falls from on to off. Hence when the Play signal turns on, the pattern will always start with the first step.

-When the system is in "idle" mode, the Note buttons can be used as a mini CV keyboard. The Gate output is asserted when a Note button is pressed, and the Pitch CV output is set to the appropriate value. The Octave buttons also work as expected. The Scale and Tonic settings of the current pattern are ignored.

-When a pattern is being edited, the ALT button can be used to automatically advance from one step to the next as notes are entered. If the ALT button is held down when pressing a Note button (or, more specifically, if it is held down when the Note button is released) the current edit step is advanced to the next step in the pattern. Only steps with their Gate turned on are used, and the Stepping Mode of the pattern is ignored.


Hell yeah! applause SlayerBadger! Those three are real good. I'm seconds away from taking it out the rack and doing the update. It's peanut butter jelly time!

With the Auto-Reset, a 24ppqn setting for din sync would make a lot of sense. I use it live with my 808 all the time and always lose the cowbell for the trigger. Splitting the din sync out is easy... You could still keep the "one trigger = one step" mode when set to "normal" or 4ppqn or whatever.

Thanks a lot for the update, cheers! Guinness ftw!
Bogus
Oh man thanks for the update Chris :-D
xonetacular
need to get me a micro sd card adapter. can't wait to play with the little keyboard
studionebula
flo wrote:

With the Auto-Reset, a 24ppqn setting for din sync would make a lot of sense. I use it live with my 808 all the time and always lose the cowbell for the trigger. Splitting the din sync out is easy... You could still keep the "one trigger = one step" mode when set to "normal" or 4ppqn or whatever.

Thanks a lot for the update, cheers! Guinness ftw!


You're welcome. Yes, we talked again about clock divisor (multiplier? depends on how you want to look at it) options while figuring out the Auto-Reset feature. Clocking in any manner other than one pulse per step opens a large can of worms, as Chris described previously on this thread. The Auto-Reset addition was fairly easy for me to code, and (we think) addresses the needs of most users.

I'd personally like to implement real DIN sync so that I could slave the thing to my 606, but as usual it's an issue of allocation of resources--namely my time--in an attempt to make as many people happy as possible, and keeping the company moving along at the same time.
flo
Of course Adam, thanks very much! Good to know that you'd find a use for true din sync as well hihi

Cheers SlayerBadger!
Crandall1
....aaaaaaand now the manual on the product page reflects the changes in v1.2.4. Enjoy!
Waldemar
keef321 wrote:
studionebula wrote:
keef321 wrote:
So onto a little feature request that I think would be cool. It would be great if for example on CV1 with it set to LFO, that we could change the LFO shape and speed per step. This would be awesome, as it would allow you to have a NI Massive style performer modulator, all in synch, opening up loads of crazy possibilities.


'Fraid that qualifies as more than a "little" feature addition. dizzy

Not that it isn't a good suggestion, mind you. We intend to expand the modulation features in the future, but how exactly is up in the air. One thing I've thought about is adding a sort of programmable ramp option, so that the control CVs could slide from one value to the next rather than jumping. This would be like the existing slide feature of the pitch CV, but would let you choose the slide time and perhaps the curvature of the slide per step. Hence it would be somewhat similar to what you suggested, but it would be independent of the LFOs.


The programmable ramp option sounds interesting, I think I can visualise this. Would this provide similar results to say ramp up, ramp down shapes etc, similar to the envelope outputs on the 4ms PEG? (not got that module, but on my wish list).

Either way, looking forward to seeing how the sequencer develops. I primarily got this module for it's sequencer capabilities, but synched modulation is a huge bonus smile Will still keep dreaming about my NI Massive Style performer in Euroland though Om


I'm also looking for both Modules. But please i ask you Wigglers that have both PEG and the sequencer 1. Are they redundant in some direction or is this a must have?

Thank you for your comment.

All the best,

Waldemar
Bogus
Waldemar wrote:
keef321 wrote:
studionebula wrote:
keef321 wrote:
So onto a little feature request that I think would be cool. It would be great if for example on CV1 with it set to LFO, that we could change the LFO shape and speed per step. This would be awesome, as it would allow you to have a NI Massive style performer modulator, all in synch, opening up loads of crazy possibilities.


'Fraid that qualifies as more than a "little" feature addition. dizzy

Not that it isn't a good suggestion, mind you. We intend to expand the modulation features in the future, but how exactly is up in the air. One thing I've thought about is adding a sort of programmable ramp option, so that the control CVs could slide from one value to the next rather than jumping. This would be like the existing slide feature of the pitch CV, but would let you choose the slide time and perhaps the curvature of the slide per step. Hence it would be somewhat similar to what you suggested, but it would be independent of the LFOs.


The programmable ramp option sounds interesting, I think I can visualise this. Would this provide similar results to say ramp up, ramp down shapes etc, similar to the envelope outputs on the 4ms PEG? (not got that module, but on my wish list).

Either way, looking forward to seeing how the sequencer develops. I primarily got this module for it's sequencer capabilities, but synched modulation is a huge bonus smile Will still keep dreaming about my NI Massive Style performer in Euroland though Om


I'm also looking for both Modules. But please i ask you Wigglers that have both PEG and the sequencer 1. Are they redundant in some direction or is this a must have?

Thank you for your comment.

All the best,

Waldemar


They're fundamentally different modules
Ras Thavas
Thanks for the update!

At the risk of sounding unappreciative, I wanted to ask where the larger "generative" update is currently sitting in the Audio Damage timeline? I know you guys have a lot going on right now. Looking forward to that update as well as "note" mode for the 3 cv's.
kuxaan-sum
While I do not know if I have a use for this first change the other two are actually really helpful:

When "idle" it is helpful for banging out settings in the patch like tuning, note/envelope length or just rehearsing sound.

I found myself disabling notes when editing before so I have wanted something like the Alt combo to edit and this makes it a breeze both visually and tactiley. (sp?)

So back to the first change.
Guess I need a run signal to make use of this.

Have not been using anything for resets (tried before and was not getting consistent results) and I find myself manually resetting each sequencer and then starting my clock.

Never a problem for shows or jamming as once I start I usually let the clock run along with everything.

What is everyone else doing (for high and low gates/signals/end of/stops) that is not using a computer?

EDITING TO SAY I AM NOT TRYING TO DERAIL THIS THREAD>I WANT TO KNOW WHAT PEOPLE ARE USING WITH THEIR SEQUENCER 1's

-There is a new Global setting, "Auto-Reset". The default value is No. If this is changed to Yes, the transport will reset to the first step of the pattern when the external Play signal falls from on to off. Hence when the Play signal turns on, the pattern will always start with the first step.
flo
I also reset manually.
x2mirko
I'm currently debating buying the sequencer 1 and i've got a question: What's the status on knob recording? My current understanding is that one can program steps individually by selecting each step and then set the value for that step, but that there is no recording-mode in which you can tweak the knobs while the sequence is running and have each step record the current value until you exit recording-mode. It's one of the features i love most about my machinedrum and it seems like an obvious addition. I think this was talked about at some point in here, just couldn't find it anymore. Any updates on this? Is it planned? Or is it maybe already included and i just didn't see the note?

Sorry if this is already answered somewhere in here, but the thread has gotten a bit long by now.
cranleigh
Nice update! Re: the auto-reset feature: any chance of a mode where the sequencer resets to the start after being idle for a few seconds?

I use mine with a TR-606 a lot, which returns to the start of a pattern once stopped and doesn't have a spare trigger output to ping the 'run' input every 16 beats or whenever...
thaneco
I just bought a sequencer 1 and have a question: can I use two seperate oscillators with two independent melodies? For example a bass line and a lead synth.
ElCampesino
thaneco wrote:
I just bought a sequencer 1 and have a question: can I use two seperate oscillators with two independent melodies? For example a bass line and a lead synth.


Yes, you can, but you have to get a little creative. You can enter the second melody using one of the CV outs. Either you judge by ear, or you calculate the equivalent voltages for each note and enter those. You can't use the little 'keyboard' for the CV outs. Then you use the accents to provide the gates for the second melody if needed. Eazy peazy. thumbs up
flo
...and you can even patch a third voice with the remaining two CV outs thumbs up

A "key" mode for the CV outs would make this very easy hihi

Cheers Guinness ftw!
flo
Just noticed while doing the update that the pattern labels on the micro SD card start with 00 and end with 15... Which, while no big deal, requires thinking around a corner when backing them up (which I didn't have to do so far). I guess changing it now is no good idea... hmmm.....
Crandall1
flo wrote:
Just noticed while doing the update that the pattern labels on the micro SD card start with 00 and end with 15... Which, while no big deal, requires thinking around a corner when backing them up (which I didn't have to do so far). I guess changing it now is no good idea... hmmm.....


You have no idea how many times Adam and I have gone head to head on this very thing. I, being a musician, want everything numbered 01, 02, ... while Adam, who is also a musician but first and foremost an engineer, habitually starts at 00 for everything.

(If you peel off the panel of Sequencer 1, and unsolder the first button, something I don't recommend, you'll see that the button is numbered 00. *sigh*)

We got in to a mild argument about this when we were making our Tattoo and Ricochet plugins. I won, but only barely. As you can plainly see in the case of the SD card files, I wasn't paying attention and thus Adam got his druthers.
Bogus
Everyday at Audio Damage headquarters is a fight over 1s and 0s then huh? Freakin' nerds :-)
flo
thumbs up Guinness ftw!

The update rocks BTW, playing the keyboard is loads of fun nanners
Footkerchief
Uh, not to be rude, but why is this rated so low (2.9) on ModularGrid?
Daisuk
Footkerchief wrote:
Uh, not to be rude, but why is this rated so low (2.9) on ModularGrid?


Some guy on here had a beef with one of the Audio Damage guys a while back, when the module first came out, and (this is my theory) registered several accounts on Modulargrid to give it a low rating. The low rating coincided with the beef taking place anyway, so seems logical.
ElCampesino
Footkerchief wrote:
Uh, not to be rude, but why is this rated so low (2.9) on ModularGrid?


I wouldn't be fooled by that. I'm a Sequencer 1 owner and have absolutely no complaints. I usually don't rate on ModularGrid, but if I'd rate the Sequencer 1, I'd give it 4 or maybe even 5 stars.

Dancing Star Dancing Star Dancing Star Dancing Star Dancing Star
Footkerchief
Daisuk wrote:
Some guy on here had a beef with one of the Audio Damage guys a while back, when the module first came out, and (this is my theory) registered several accounts on Modulargrid to give it a low rating. The low rating coincided with the beef taking place anyway, so seems logical.


I was wondering if it might be something like that, because all the other feedback I've read seems much more positive.
Crandall1
Not a "beef" so much as he was a fucking idiot. He bought one 3U boat of Pittsburgh turn-key, and this made him an expert on all three high-end Euro sequencers (as well as a number of other things; I would be happy to provide his trail of idiocy he's left on various music tech forums in the last 10 years.)

I, being me, let him know in no uncertain terms that he should shut the fuck up while grown folks were talking, and for some reason he got offended by that. :-) Needless to say, he's long since banned. You can read back in this thread some 20-odd pages ago for his retardation under multiple screen names here.

(Side note: I have a _lot_ of commercial product design under my belt, including some of the best selling software in the industry. While I am generally a fairly humble dude, I don't take well to being patronized by some random bloke with no pedigree. At least I'm self-aware enough to know that.)
Daisuk
What he said. smile just didn't want to call him that, haha. But yeah, that's probably where the poor rating comes from.
xonetacular
studionebula wrote:
flo wrote:

With the Auto-Reset, a 24ppqn setting for din sync would make a lot of sense. I use it live with my 808 all the time and always lose the cowbell for the trigger. Splitting the din sync out is easy... You could still keep the "one trigger = one step" mode when set to "normal" or 4ppqn or whatever.

Thanks a lot for the update, cheers! Guinness ftw!


You're welcome. Yes, we talked again about clock divisor (multiplier? depends on how you want to look at it) options while figuring out the Auto-Reset feature. Clocking in any manner other than one pulse per step opens a large can of worms, as Chris described previously on this thread. The Auto-Reset addition was fairly easy for me to code, and (we think) addresses the needs of most users.

I'd personally like to implement real DIN sync so that I could slave the thing to my 606, but as usual it's an issue of allocation of resources--namely my time--in an attempt to make as many people happy as possible, and keeping the company moving along at the same time.



seconding support for this

It would really be great if there was just a divide option for the external clock input. Then it could be easily clocked by dinsync gear, and then hopefully you could get a 16th note pulse from the clock output which would be useful to clock other gear without tying up a clock divider.
Footkerchief
The manual says that swing "alters the rhythmic feel of the pattern by delaying every other step relative to the clock." Does that mean there's no way to choose which steps swing gets applied to?
Crandall1
Footkerchief wrote:
The manual says that swing "alters the rhythmic feel of the pattern by delaying every other step relative to the clock." Does that mean there's no way to choose which steps swing gets applied to?


Not currently, no. And chances are we won't add that _particular_ thing. I mean, 16th note swing is only applied to half the steps to begin with. Why make that less intuitive?

What's more likely is a per-step percentage nudge, which is something I'd personally like for my own music. Same net effect; just calling it something different and making it more controllable. I plan to ask for this during the next round of additions, and I have a theory for how it would work pretty nicely.
Footkerchief
Crandall1 wrote:
Not currently, no. And chances are we won't add that _particular_ thing. I mean, 16th note swing is only applied to half the steps to begin with. Why make that less intuitive?


Well, "half the steps" is kinda limiting. Being able to swing only 1 in 4 steps, or 1 in 3 (as with Pamela's Workout), or preferably any arbitrary step, would allow a lot more rhythmic variation.
Crandall1
Footkerchief wrote:

Well, "half the steps" is kinda limiting. Being able to swing only 1 in 4 steps, or 1 in 3 (as with Pamela's Workout), or preferably any arbitrary step, would allow a lot more rhythmic variation.


I agree with you, but "any arbitrary step" (which is what I'm proposing above) is not swing. It's just fucking with the timing. While that's well and good and musically useful, calling it "swing" is counterproductive.
Footkerchief
Ah, I see the swing/nudge distinction now. I guess Pamela's abuses the term for lack of a better standard ("nudge" works though). Sounds like a great addition, especially if it fits in the UI with other per-step options.
studionebula
Ras Thavas wrote:
Thanks for the update!

At the risk of sounding unappreciative, I wanted to ask where the larger "generative" update is currently sitting in the Audio Damage timeline? I know you guys have a lot going on right now. Looking forward to that update as well as "note" mode for the 3 cv's.


You're welcome. I think that the "'generative' update" is the next big thing on my engineering to-do list. The Note mode for the CVs will be part of that update, because my current vision for the generative stuff makes it sensible to do both at once. (I was actually considering doing the Note mode in the most recent update, but I decided to do the note-entry and keyboard stuff instead because, well, I wanted those features more than I want the Note mode. Yeah, call me selfish.)

Now, what does that mean in terms of actual time? Hell if I know. I spent the first several months of 2015 on R&D of a product that we decided to shelve at just about the time I got the first prototype running. I've spent the time since on R&D of another product which is now running far later than even my pessimistic estimates, still isn't finished, and yet we intend to debut at NAMM in January. Hence it would be pretty silly of me to make public statements about how long it will take me to do something when I can't even make accurate statements about such things to my own business partner.

That's the bad news. The good news is that getting away from the sequencer code for awhile enabled me to look at it with fresh eyes when I did the recent update. This renewed perspective gave me an idea of how to approach the whole "generative" thing in a manner different than I'd previously envisioned it--a manner which is both easier to build and I believe both simpler and more interesting to use.

I'll stop waving my hands now.
studionebula
flo wrote:
Just noticed while doing the update that the pattern labels on the micro SD card start with 00 and end with 15... Which, while no big deal, requires thinking around a corner when backing them up (which I didn't have to do so far). I guess changing it now is no good idea... hmmm.....


Yeah, it's ugly, but I think that changing it now is uglier.
studionebula
x2mirko wrote:
I'm currently debating buying the sequencer 1 and i've got a question: What's the status on knob recording? My current understanding is that one can program steps individually by selecting each step and then set the value for that step, but that there is no recording-mode in which you can tweak the knobs while the sequence is running and have each step record the current value until you exit recording-mode. It's one of the features i love most about my machinedrum and it seems like an obvious addition. I think this was talked about at some point in here, just couldn't find it anymore. Any updates on this? Is it planned? Or is it maybe already included and i just didn't see the note?.


It's not yet included. We've had a hard time coming up with a design for this feature that doesn't seem like it would suck in the end. (We try to avoid sucking in the end.) There are several problems, but they mostly have to do with the fact that the encoders have to span a rather wide range of values, and that (being encoders) they provide changes in values, rather values themselves.

However, while we're on the topic, and since I sold my Machinedrum long ago, here's a question or two: Does the MD have encoders also? If so, how does it decide what value to start with when you're in this recording mode? And can it span the entire range of values for a parameter with a single rotation?
Ras Thavas
studionebula wrote:
...That's the bad news. The good news is that getting away from the sequencer code for awhile enabled me to look at it with fresh eyes when I did the recent update. This renewed perspective gave me an idea of how to approach the whole "generative" thing in a manner different than I'd previously envisioned it--a manner which is both easier to build and I believe both simpler and more interesting to use...


Not necessarily bad news at all, just glad to get a general sense of where it is in the pipeline, and certainly understand how the universe consistently screws up our best plans.

Besides, you had me at "both simpler and more interesting to use..."

Thanks for taking the time to update us!
studionebula
cranleigh wrote:
Nice update! Re: the auto-reset feature: any chance of a mode where the sequencer resets to the start after being idle for a few seconds?

I use mine with a TR-606 a lot, which returns to the start of a pattern once stopped and doesn't have a spare trigger output to ping the 'run' input every 16 beats or whenever...


So... I'm confused. How are you synchronizing the two devices without some sort of common Run signal? hmmm.....

It seems like a reset-on-idle feature would cause annoyance almost as often as being helpful, since inevitably you'd occasionally restart something within the idle-time window and hence get out of sync, but I think I don't entirely understand what you have in mind.
studionebula
Bogus wrote:
Everyday at Audio Damage headquarters is a fight over 1s and 0s then huh? Freakin' nerds :-)


There are days like that, yes. More frequently there are days in which Chris accuses Adam of being too literal-minded, and Adam accuses Chris of being too vague in his product-design directives.

The filename thing was just a dumb mistake on my part. Yes, I habitually start numbering things at zero because this is how microprocessors and their associated support chips do things. The buttons are numbered (on the PC board) starting at zero because the first pin on the chip that they're connected to is designated as zero. However, this is internal stuff; the end-user sensibly expects things to start at one because that's what we're taught in grade school. The filenames should start at one since they're visible to the end-user and they should match the pattern numbers on the panel.

In other words, yes, I'm an engineer first and a musician second, but I try to think about this stuff from the musician's perspective as much as I can--and I lean heavily on Chris to keep me honest in this respect. This one got by both of us.
flocked
studionebula wrote:

However, while we're on the topic, and since I sold my Machinedrum long ago, here's a question or two: Does the MD have encoders also? If so, how does it decide what value to start with when you're in this recording mode? And can it span the entire range of values for a parameter with a single rotation?


The MD has encoders. When you start recording the knob movements the value/encoders start at the value you set before. To make a full 0-127 movement you need a few full 360° encoder turns…which of course sucks if you want to make full value changes. Thats why you can also push the encoders (they have buttons inside). If you push and move the encoder it makes full value changes much faster. You only need 1 full turn while pressing for full value changes from e.g. 0 to 127.
cranleigh
studionebula wrote:
cranleigh wrote:
Nice update! Re: the auto-reset feature: any chance of a mode where the sequencer resets to the start after being idle for a few seconds?

I use mine with a TR-606 a lot, which returns to the start of a pattern once stopped and doesn't have a spare trigger output to ping the 'run' input every 16 beats or whenever...


So... I'm confused. How are you synchronizing the two devices without some sort of common Run signal? hmmm.....

It seems like a reset-on-idle feature would cause annoyance almost as often as being helpful, since inevitably you'd occasionally restart something within the idle-time window and hence get out of sync, but I think I don't entirely understand what you have in mind.


Hi Adam,
I am syncing them up by setting up a constant stream of 16th note triggers on the 606's hi tom channel (which doubles as one of the 606's trigger out channels). I have external sync enabled on the Seq1, and, before starting the 606, I press stop then start on the Seq1's transport buttons. Then starting the 606 (which always returns to step 1 when restarting after stopping) makes the two start perfectly in time.
So what I'm really hoping for is not to have to do that step of pressing stop and start on the Seq1 before restarting each time. It's not a dealbreaker, naturally, but some version of that kind of sync would be handy to me...
thanks!
Ras Thavas
studionebula wrote:

However, while we're on the topic, and since I sold my Machinedrum long ago, here's a question or two: Does the MD have encoders also? If so, how does it decide what value to start with when you're in this recording mode? And can it span the entire range of values for a parameter with a single rotation?


If the use of the encoders becomes too problematic, being able to record an external voltage thru the cv ins would be just fine, for me at least. I'm thinking things like real time recording (within the sequence length) of an external keyboard cv and gate, 2 axes of joystick movement, etc...
synthmind
I don't think this has been discussed before, but I'm curious if there is a reason that inputs for CV 1 / CV 2 are global rather than specific to a sequence?

It'd be most ideal if they were either directly linked to a sequence, OR perhaps even could be set Global OR Pattern. Thanks!
flo
Ras Thavas wrote:
I'm thinking things like real time recording (within the sequence length) of an external keyboard cv and gate


That's not necessary, just make a realtime entry mode for the keyboard please!
Crandall1
synthmind wrote:
I don't think this has been discussed before, but I'm curious if there is a reason that inputs for CV 1 / CV 2 are global rather than specific to a sequence?


Pretty obvious if you consider that Sequencer 1 is designed primarily for live performance.

Imagine this scenario: you're grooving on pattern A01, which has CV1 input set to ratchets. You switch to pattern A02, which has CV1 input set to pattern or transpose, but you didn't pull out the cable before you switched. Oops. Worse yet, you have a pattern with the input set to "step" but you don't have anything plugged in the input, and your sequence just stops.

After thinking about it long and hard, we decided that two things were obvious:

1. If you don't remember what you programmed the inputs for that particular patch to be, you're gonna be really confused if you haven't visited it in a while.

2. Most people will use one or two CV input features constantly. (Like me with self-patching a random LFO to CV1 programmed to Repeats. This way I can have per-pattern control over random repeats; I never unplug this.) In this manner they can basically configure Seq1 to be how they want and leave it and it'll always be that way.

Long story short: per-pattern gets confusing very quickly. Global is never confusing. I'll take a lack of confusion at the expense of configurability any day of the week.
synthmind
I understand your opinion here, but I couldn't actually disagree with it more. It's just a difference of opinions. I'd prefer the exactness of settings per pattern, rather than having to remember that for example on Bank B, sequence 14 I need to set the CV In to X, and then manually change that setting on the next chosen pattern if they don't both share that same CV In setting.

I'm using the Sequencer 1 in both studio & live settings.

Perhaps you would consider letting the user make the decision if CV Input values were pattern contingent or Global.
synthmind
For what it is worth - I feel similarly about tempo. (I know we've discussed this before). I'd way prefer having each sequence associated with it's own tempo setting, thus allowing quick tempo changes, rather than having to scroll through the tempo change. I've circumvented this by using an external Midi clock.
hpsounds
synthmind wrote:
I understand your opinion here, but I couldn't actually disagree with it more. It's just a difference of opinions. I'd prefer the exactness of settings per pattern, rather than having to remember that for example on Bank B, sequence 14 I need to set the CV In to X, and then manually change that setting on the next chosen pattern if they don't both share that same CV In setting.

I'm using the Sequencer 1 in both studio & live settings.

Perhaps you would consider letting the user make the decision if CV Input values were pattern contingent or Global.

I have exactly the same opinion. Having the choice seems way better in such a complex and upgradable sequencer.

seriously, i just don't get it hmmm.....

H.
Crandall1
I'll ask Adam if that's possible. I don't see any reason we couldn't have an over-ride per pattern where you select either the global settings or a local one for inputs. For tempo, it would be a bit more difficult proposition.

That said, that SEQ menu tree is getting deep.
synthmind
That would be great. Thanks Chris.
Slomen
I would also love the cv inputs to be tied to the sequence w00t
hpsounds
Thanks Chris for listening to your users ! thumbs up applause

H.
thaneco
Thank you Audio Damage for this wonderful sequencer. I just sequenced my minimoog model d with no problems!
Multi Grooves
I've had this a while but totally unused as I'm taking the time to learn all of my stuff properly.

Its awesome seeing developers and users with this level of interaction; I did follow this thread for a little bit but I can remember the square root of fuck all, so seeing the size of this now is a little daunting.

What is the best way to get stuck into this machine and it's operation? Are there any instructions that are up to date (not appendixes and additions to v1.0)?

I guess I need to get all over this whilst its still being shaped?
Bogus
Multi Grooves wrote:
I've had this a while but totally unused as I'm taking the time to learn all of my stuff properly.

Its awesome seeing developers and users with this level of interaction; I did follow this thread for a little bit but I can remember the square root of fuck all, so seeing the size of this now is a little daunting.

What is the best way to get stuck into this machine and it's operation? Are there any instructions that are up to date (not appendixes and additions to v1.0)?

I guess I need to get all over this whilst its still being shaped?


Honestly you just need to read through the user manual until you find something that's pertinent to your desire for creation and try to apply it. Repeat this until you've found everything, or atleast everything you're looking for. The best way to learn is through use. With this process you may find the Sequencer 1 really isn't all that daunting.

It's perfectly possible to explore the entire menu system of the Sequencer 1 in one sitting. Though, not eveything it can do could be or should be used at once.
Multi Grooves
I thought i would be out of date with all of the feature requests and firmware changes discussed on these pages, no?
infection
Is there a way to slip/slide a pattern to the left or right by one step increments?
If not i would like to request this function as it can be really usefull, especially if you are programming to a beat and forgot to reset all sequencers to the first beat before programming.
Multi Grooves
..
studionebula
Multi Grooves wrote:
I thought i would be out of date with all of the feature requests and firmware changes discussed on these pages, no?


I strive to keep the manual up to date. I believe that every significant change to the firmware since its initial release is covered, both in the main text and in the "What's New" sections near the beginning of the manual.

Requests are not documented in the manual because, well, that would be silly.
studionebula
infection wrote:
Is there a way to slip/slide a pattern to the left or right by one step increments?
If not i would like to request this function as it can be really usefull, especially if you are programming to a beat and forgot to reset all sequencers to the first beat before programming.


This has come up previous, and the bad news is that no, there's no way currently to do this. The good news is that I very much want this feature myself because I seem to end up with "one" in the wrong place more often than not, regardless of whose sequencer I'm using.

Recently, Chris and I have been talking about how to wedge editing operations like this into the user interface. I think we've got something viable sketched out, but coding things that affect the entire pattern at once is a little tricky and something which I'm trying to solve comprehensively for other reasons.
studionebula
thaneco wrote:
Thank you Audio Damage for this wonderful sequencer. I just sequenced my minimoog model d with no problems!


Thank you. Does that model have an S-trig input? We had only so many devices to test that feature with, for obvious reasons.
studionebula
cranleigh wrote:
studionebula wrote:
cranleigh wrote:
Nice update! Re: the auto-reset feature: any chance of a mode where the sequencer resets to the start after being idle for a few seconds?

I use mine with a TR-606 a lot, which returns to the start of a pattern once stopped and doesn't have a spare trigger output to ping the 'run' input every 16 beats or whenever...


So... I'm confused. How are you synchronizing the two devices without some sort of common Run signal? hmmm.....

It seems like a reset-on-idle feature would cause annoyance almost as often as being helpful, since inevitably you'd occasionally restart something within the idle-time window and hence get out of sync, but I think I don't entirely understand what you have in mind.


Hi Adam,
I am syncing them up by setting up a constant stream of 16th note triggers on the 606's hi tom channel (which doubles as one of the 606's trigger out channels). I have external sync enabled on the Seq1, and, before starting the 606, I press stop then start on the Seq1's transport buttons. Then starting the 606 (which always returns to step 1 when restarting after stopping) makes the two start perfectly in time.
So what I'm really hoping for is not to have to do that step of pressing stop and start on the Seq1 before restarting each time. It's not a dealbreaker, naturally, but some version of that kind of sync would be handy to me...
thanks!


Thanks for the description. How are you with a soldering iron? I have not tried this myself, but I'm wondering whether you could use the Start/Stop signal from the Sync jack to, uh, start/stop the sequencer (at the risk of stating the obvious). Yes, I realize that the real solution is to make Sequencer 1 Just Work with DIN sync, but other fish are more likely to get fried first.

I'll try the aforementioned scheme with my 606 when I get a spare moment.
studionebula
Crandall1 wrote:
I'll ask Adam if that's possible. I don't see any reason we couldn't have an over-ride per pattern where you select either the global settings or a local one for inputs. For tempo, it would be a bit more difficult proposition.

That said, that SEQ menu tree is getting deep.


I think it's possible. The trick with adding stuff per-pattern is that we're already using most of the RAM that we have, and the RAM usage of anything that gets added to the pattern gets multiplied by 64. That said, the CV mapping info doesn't represent much data. Thinking off the top of my head, switching CV assignments when the pattern changes shouldn't be difficult. Switching tempo, as Chris alluded, might be trickier. (For the record, Chris and I went back and forth a lot about global vs. per-pattern tempo.)

As for the menu tree, yes, it's getting deeper, and I guess it's up to the userbase to tell us whether or not that's acceptable. This addition would mean duplicating the CV assignment stuff in the Global menu.
flo
studionebula wrote:
cranleigh wrote:
studionebula wrote:
cranleigh wrote:
Nice update! Re: the auto-reset feature: any chance of a mode where the sequencer resets to the start after being idle for a few seconds?

I use mine with a TR-606 a lot, which returns to the start of a pattern once stopped and doesn't have a spare trigger output to ping the 'run' input every 16 beats or whenever...


So... I'm confused. How are you synchronizing the two devices without some sort of common Run signal? hmmm.....

It seems like a reset-on-idle feature would cause annoyance almost as often as being helpful, since inevitably you'd occasionally restart something within the idle-time window and hence get out of sync, but I think I don't entirely understand what you have in mind.


Hi Adam,
I am syncing them up by setting up a constant stream of 16th note triggers on the 606's hi tom channel (which doubles as one of the 606's trigger out channels). I have external sync enabled on the Seq1, and, before starting the 606, I press stop then start on the Seq1's transport buttons. Then starting the 606 (which always returns to step 1 when restarting after stopping) makes the two start perfectly in time.
So what I'm really hoping for is not to have to do that step of pressing stop and start on the Seq1 before restarting each time. It's not a dealbreaker, naturally, but some version of that kind of sync would be handy to me...
thanks!


Thanks for the description. How are you with a soldering iron? I have not tried this myself, but I'm wondering whether you could use the Start/Stop signal from the Sync jack to, uh, start/stop the sequencer (at the risk of stating the obvious). Yes, I realize that the real solution is to make Sequencer 1 Just Work with DIN sync, but other fish are more likely to get fried first.

I'll try the aforementioned scheme with my 606 when I get a spare moment.


I always do it as cranleigh describes as well. I have breakout cables for din sync and will try whether the run will work, don't see any reason why it wouldn't (especially with the auto-reset). But yes, it doesn't make much sense like this if you cannot use the 24ppqn clock stream as well...

I'll report back ASAP.
Crandall1
studionebula wrote:
Multi Grooves wrote:
I thought i would be out of date with all of the feature requests and firmware changes discussed on these pages, no?


I strive to keep the manual up to date. I believe that every significant change to the firmware since its initial release is covered, both in the main text and in the "What's New" sections near the beginning of the manual.


Traditionally, Adam hands a new firmware version to me for testing, and while I'm testing it, he updates the manual. Usually, the new firmware goes live, and then a few hours later the new manual goes up. So unless we released new firmware in the last couple hours, they're almost always in sync.

The problem arises when we do an update and retailers don't update the units they sell, so a new user gets a unit that doesn't have some feature that he bought it for. This happened a lot after the 1.1 update, which had a huge payload of features and updates. People bought a lot of units right after that, as they were waiting to see if we would add those features, and then they got a unit that was running the 1.0 firmware and wrote us asking why it was broken or whatever. This was funny once. After that, not so much.

SO!

If you buy a new Seq1 from a retailer, the first thing you should do on powering it up is to press Alt-01, then whack one of the encoders 4 times to get to the firmware version page and see what it's running. Then head over to the AD site to see what the current version is. If they match, have fun. If they don't, your first task should be to update it to the current version.
cannonball swandive
What is your favorite use of the CV1 and 2 inputs?
cutterfiltoff
cannonball swandive wrote:
What is your favorite use of the CV1 and 2 inputs?


My favorite is the step select! So many possibilities Dead Banana
cannonball swandive
Still haven't dove into the cv inputs. This sequencer is great though! Any ideas on generative patches with it?
cannonball swandive
Crandall1, is it possible in a future update to have the accent and lfo's in a separate "track?". So as to set them to different pattern lengths. Maybe this is already possible but I didn't seem to find it anywhere in the documentation. The feature would be awesome for creating interesting and alternating patterns.
droningsphagettimonster
what module are you guys using for swapping patterns via CV in 1/2? I wish a future update will include some sort of pattern chaining...
studionebula
cannonball swandive wrote:
Crandall1, is it possible in a future update to have the accent and lfo's in a separate "track?". So as to set them to different pattern lengths. Maybe this is already possible but I didn't seem to find it anywhere in the documentation. The feature would be awesome for creating interesting and alternating patterns.


LFOs have a length of up to 256 steps, which is four times the maximum length of a pattern, and cycle independently of the pattern. I don't know whether or not that's what you mean.

As for accents, they're part of the step data (along with the pitch, CV1-3, etc.) and can't viably be separated into something independent.
DSC
Thank you you guys for constantly and consistently working on this. I have two of these and need a third thumbs up The only request I have, is it possible to have a new selection of 'repeats' and 'ratchet steps' other than the originals?
Maybe a 'odd' set, like Rep 7, Rep 5, Rep 3, Rep1 and then an odd Ratcheting, like Rat 3 and Rat 5? Maybe a random set. Something like,
Rep ODD, Rep EVEN, Rep Random 1-3, Rep Random 4-7... etc.
Just some ideas.

Those last six buttons are some of my favorite to use and being able to change them up occasionally would be cool, Thanks again.
studionebula
DSC wrote:

Maybe a 'odd' set, like Rep 7, Rep 5, Rep 3, Rep1 and then an odd Ratcheting, like Rat 3 and Rat 5? Maybe a random set. Something like,
Rep ODD, Rep EVEN, Rep Random 1-3, Rep Random 4-7... etc.


Yep, that's on the to-do list. Someone had the clever idea of using combinations of the existing buttons to achieve some odd-numbered reps and ratchets, so we'll probably do that.
Ras Thavas
studionebula wrote:
DSC wrote:

Maybe a 'odd' set, like Rep 7, Rep 5, Rep 3, Rep1 and then an odd Ratcheting, like Rat 3 and Rat 5? Maybe a random set. Something like,
Rep ODD, Rep EVEN, Rep Random 1-3, Rep Random 4-7... etc.


Yep, that's on the to-do list. Someone had the clever idea of using combinations of the existing buttons to achieve some odd-numbered reps and ratchets, so we'll probably do that.


smile thank you very much & looking forward to it!
cranleigh
studionebula wrote:
cranleigh wrote:
studionebula wrote:
cranleigh wrote:
Nice update! Re: the auto-reset feature: any chance of a mode where the sequencer resets to the start after being idle for a few seconds?

I use mine with a TR-606 a lot, which returns to the start of a pattern once stopped and doesn't have a spare trigger output to ping the 'run' input every 16 beats or whenever...


So... I'm confused. How are you synchronizing the two devices without some sort of common Run signal? hmmm.....

It seems like a reset-on-idle feature would cause annoyance almost as often as being helpful, since inevitably you'd occasionally restart something within the idle-time window and hence get out of sync, but I think I don't entirely understand what you have in mind.


Hi Adam,
I am syncing them up by setting up a constant stream of 16th note triggers on the 606's hi tom channel (which doubles as one of the 606's trigger out channels). I have external sync enabled on the Seq1, and, before starting the 606, I press stop then start on the Seq1's transport buttons. Then starting the 606 (which always returns to step 1 when restarting after stopping) makes the two start perfectly in time.
So what I'm really hoping for is not to have to do that step of pressing stop and start on the Seq1 before restarting each time. It's not a dealbreaker, naturally, but some version of that kind of sync would be handy to me...
thanks!


Thanks for the description. How are you with a soldering iron? I have not tried this myself, but I'm wondering whether you could use the Start/Stop signal from the Sync jack to, uh, start/stop the sequencer (at the risk of stating the obvious). Yes, I realize that the real solution is to make Sequencer 1 Just Work with DIN sync, but other fish are more likely to get fried first.

I'll try the aforementioned scheme with my 606 when I get a spare moment.


Hi Adam,
I am reasonably handy with the soldering iron so I could definitely do up a cable to fit the bill. Although I also often use the Seq1 with Silent Way too, so in an ideal world there would be an OS fix to allow us to reset the sequence to the start after it has been stopped. But it's really not a big deal at all, so no problem if it isn't feasible for you guys.

One other thing I would love to see is more control over the slide parameter. I was just reading the thread about the upcoming SQR sequencer and this paragraph made me drool a little...

"The slide implementation is far more deep than in the beatstep pro too. You can select the slide length for each step and you can even choose length superiour to 100% (a video coming soon will show you how crazy it can be!). You can also select the slide shape (linear, exponential, log, gaussian, ...)."

That's my personal no.1 preference for Sequencer 1 updates! There are so many great midi sequencers out there these days that can do all sorts of cool probablistic stuff (including some ipad apps that have really impressed me lately), but they cannot do the glide thing properly when you move from midi to CV. For me, that's the main reason I hang on to the Sequencer 1, and would love to see more options/control in that department.
DSC
studionebula wrote:

Yep, that's on the to-do list. Someone had the clever idea of using combinations of the existing buttons to achieve some odd-numbered reps and ratchets, so we'll probably do that.


Excellent, thank you for considering this. How much do I love my repeats and ratchets? Enough to dedicate 6 NEW inputs for them!
Keep up the great work!



ranzen
@DSC Is this real?! woah

Looks absolutely fantastic! Not only functionally wise adding 6 INs, but also the reduced typography and potis really make this a huge improvement!
we're not worthy
sempervirent
DSC wrote:

Spotted this on ModularGrid, nice work... has an Elektron look to it.
MA.n
very interesting.. curious about this statement "As I hinted before, SD card for storage and OS updates." - and what this exactly entitles

nevertheless - a module to definitely check out - thanks for sharing!
Crandall1
MA.n Is this a necro-bump? Sequencer 1 has been out for 18 months now. There's a micro SD card slot on the back, where all the patterns and globals are stored. This is also the mechanism for installing the (relatively frequent) OS updates.
synthmind
Hey Chris - it seems like there's a small issue I've found where empty sequence presets show up as lit up, rather than not lit up, when I'm choosing a new sequence number. I've gone through and even done a pattern clear and save for each one that should be empty, but upon power down / up, they are once again lit up - rather than appearing "empty". Thanks!
Crandall1
synthmind wrote:
Hey Chris - it seems like there's a small issue I've found where empty sequence presets show up as lit up, rather than not lit up, when I'm choosing a new sequence number. I've gone through and even done a pattern clear and save for each one that should be empty, but upon power down / up, they are once again lit up - rather than appearing "empty". Thanks!


Sounds to me like the uSD card might be iffy. Try replacing it?
studionebula
synthmind wrote:
Hey Chris - it seems like there's a small issue I've found where empty sequence presets show up as lit up, rather than not lit up, when I'm choosing a new sequence number. I've gone through and even done a pattern clear and save for each one that should be empty, but upon power down / up, they are once again lit up - rather than appearing "empty". Thanks!


This is a tricky one. What's happening is that the saved patterns remain on the uSD card even when they're empty. In other words, if you clear a pattern and then save it, you're over-writing the old file for that pattern, not deleting the file (since "save" means save the contents of the pattern, regardless of what the contents are). So then when you cycle power, the software sees the file on the card, loads it, and marks the pattern as used--even though it just loaded the data for an empty pattern.

So, good find on that one. Offhand I think the fixes are either 1) upon loading a file, if its contents are the same as an empty pattern, don't mark the pattern as used, or 2) upon saving a file, if the pattern is empty, delete the file rather than saving it. That's a remark to myself, obviously.
droningsphagettimonster
droningsphagettimonster wrote:
what module are you guys using for swapping between patterns via CV in 1/2?


you guys? this seems to be a pretty useless feature to me if i don't sent out the excact voltages needed to switch to the right pattern, lets say from 3 to 6 or 4 to 11 or something. any suggestions? gate from maths channel 2 into its mixer is cool but not percise enough. do i need to add a quantizer? been thinking about to grab the brainseed... would it do the trick? hmmm.....

i've also noticed that when the sequencer is externally resetted when clocked the first step seems to have sort of slide to it unless i press the stop button. would be nice to fix this bug even though it does not really matter. MY ASS IS BLEEDING
droningsphagettimonster
droningsphagettimonster wrote:
droningsphagettimonster wrote:
what module are you guys using for swapping between patterns via CV in 1/2?


you guys? this seems to be a pretty useless feature to me if i don't sent out the excact voltages needed to switch to the right pattern, lets say from 3 to 6 or 4 to 11 or something. any suggestions? gate from maths channel 2 into its mixer is cool but not percise enough. do i need to add a quantizer? been thinking about to grab the brainseed... would it do the trick? hmmm.....

i've also noticed that when the sequencer is externally resetted when clocked the first step seems to have sort of slide to it unless i press the stop button. would be nice to fix this bug even though it does not really matter. MY ASS IS BLEEDING


seriously, i just don't get it
flo
Well, you need another programmable precision voltage source to be able to address that destination reliably (maybe clocked by a subdivision of the master clock). Such as another AD Sequencer 1, for example hihi Or any sequencer, really...

Personally, I don't switch patterns via CV.

Cheers Guinness ftw!
TINCT
DSC wrote:
studionebula wrote:

Yep, that's on the to-do list. Someone had the clever idea of using combinations of the existing buttons to achieve some odd-numbered reps and ratchets, so we'll probably do that.


Excellent, thank you for considering this. How much do I love my repeats and ratchets? Enough to dedicate 6 NEW inputs for them!
Keep up the great work!





Can anyone confirm if this image is of the new design to be released in March?
Crandall1
I can confirm it's not. Which is sort of the opposite of what you're asking.

NINstruments hacked his own unit. If you want one of those, you'll have to talk to him.
TINCT
Thanks Crandall smile
xandersingh
Hey guys, I just got my Sequencer 1 this morning and I'm loving it so far. But I'm having an issue with getting it to sync properly in my setup.

I'm clocking/resetting it with the Intellijel uMidi and using ableton. The uMidi works great with the Metropolis sequencer. Syncs and runs/resets in perfect time with ableton. But with the sequencer 1 everything seems to be a half step behind of the ableton clock. It's almost as if its getting all the messages a little bit later.

Is there some kind of setting I can change on it to make it play well? The uMidi seems pretty "turn key" as a module and doesn't have any settings to change. Maybe they just don't work well together, but I would hate to have to get another module to sync the Sequencer 1 with ableton as my case is full.

Thanks in advance!
jvt
Any chance for a future alternate user-selectable editing mode that doesn't require a "press-and-hold" for step selection? All of those delays while editing pitch and other note properties eventually add up. Given that there's already a dedicated Gate button it seems this alternate operating mode should be possible. I can certainly understand the performance aspects of toggling gates in real time, but during the composition phase, it would be most ideal if that process could be as fast as possible. The Sequencer 1 is so close to perfect, I feel that dispensing with the press-and-hold (at least optionally) would get it all the way there!
string56
jvt wrote:
Any chance for a future alternate user-selectable editing mode that doesn't require a "press-and-hold" for step selection? All of those delays while editing pitch and other note properties eventually add up. Given that there's already a dedicated Gate button it seems this alternate operating mode should be possible. I can certainly understand the performance aspects of toggling gates in real time, but during the composition phase, it would be most ideal if that process could be as fast as possible. The Sequencer 1 is so close to perfect, I feel that dispensing with the press-and-hold (at least optionally) would get it all the way there!


I couldn't agree more, and you've expressed it perfectly, in this alternative mode, clicking a step immediately selects that step for editing: this would dramatically speed up entering parameters in the composition stage, whilst toggling back to the existing mode might be preferable for many users in the performance stage. I frequently use CVs 1, 2 and 3 for melodic or bass lines or indeed drum patterns: with this approach, muting entire steps which may be putting out six values each just isn't useful. Logically it should mute Pitch and Gate for the step, but not CV 1 2 and 3. Perhaps that behaviour could be user selectable too? Different muting behaviour on every step is probably taking it too far, but a global option to determine the effect of the gate button, muting gate (of course), and any combination of Pitch, CV1, CV2, and CV3, would be extremely flexible.
Ras Thavas
jvt wrote:
Any chance for a future alternate user-selectable editing mode that doesn't require a "press-and-hold" for step selection? All of those delays while editing pitch and other note properties eventually add up. Given that there's already a dedicated Gate button it seems this alternate operating mode should be possible. I can certainly understand the performance aspects of toggling gates in real time, but during the composition phase, it would be most ideal if that process could be as fast as possible. The Sequencer 1 is so close to perfect, I feel that dispensing with the press-and-hold (at least optionally) would get it all the way there!


Agreed, would like the press and hold for step selection in gate mode, but not in seq mode, so I could quickly select a step without accidentally changing my sequence.
flo
string56 wrote:
jvt wrote:
Any chance for a future alternate user-selectable editing mode that doesn't require a "press-and-hold" for step selection? All of those delays while editing pitch and other note properties eventually add up. Given that there's already a dedicated Gate button it seems this alternate operating mode should be possible. I can certainly understand the performance aspects of toggling gates in real time, but during the composition phase, it would be most ideal if that process could be as fast as possible. The Sequencer 1 is so close to perfect, I feel that dispensing with the press-and-hold (at least optionally) would get it all the way there!


I couldn't agree more, and you've expressed it perfectly, in this alternative mode, clicking a step immediately selects that step for editing: this would dramatically speed up entering parameters in the composition stage, whilst toggling back to the existing mode might be preferable for many users in the performance stage. I frequently use CVs 1, 2 and 3 for melodic or bass lines or indeed drum patterns: with this approach, muting entire steps which may be putting out six values each just isn't useful. Logically it should mute Pitch and Gate for the step, but not CV 1 2 and 3. Perhaps that behaviour could be user selectable too? Different muting behaviour on every step is probably taking it too far, but a global option to determine the effect of the gate button, muting gate (of course), and any combination of Pitch, CV1, CV2, and CV3, would be extremely flexible.


You cannot "mute" CV. What should it do, go sharply to zero? Depending on the "hold" mode, the Seq 1 puts out the pitch and CV information of "muted" (= no gate) steps.

Cheers Guinness ftw! thumbs up
string56
flo wrote:
string56 wrote:
jvt wrote:
Any chance for a future alternate user-selectable editing mode that doesn't require a "press-and-hold" for step selection? All of those delays while editing pitch and other note properties eventually add up. Given that there's already a dedicated Gate button it seems this alternate operating mode should be possible. I can certainly understand the performance aspects of toggling gates in real time, but during the composition phase, it would be most ideal if that process could be as fast as possible. The Sequencer 1 is so close to perfect, I feel that dispensing with the press-and-hold (at least optionally) would get it all the way there!


I couldn't agree more, and you've expressed it perfectly, in this alternative mode, clicking a step immediately selects that step for editing: this would dramatically speed up entering parameters in the composition stage, whilst toggling back to the existing mode might be preferable for many users in the performance stage. I frequently use CVs 1, 2 and 3 for melodic or bass lines or indeed drum patterns: with this approach, muting entire steps which may be putting out six values each just isn't useful. Logically it should mute Pitch and Gate for the step, but not CV 1 2 and 3. Perhaps that behaviour could be user selectable too? Different muting behaviour on every step is probably taking it too far, but a global option to determine the effect of the gate button, muting gate (of course), and any combination of Pitch, CV1, CV2, and CV3, would be extremely flexible.


You cannot "mute" CV. What should it do, go sharply to zero? Depending on the "hold" mode, the Seq 1 puts out the pitch and CV information of "muted" (= no gate) steps.

Cheers Guinness ftw! thumbs up


Yes, you are right, my second point looks erroneous. From the description in the docs, the hold modes do already appear to provide the level of control I describe. Apologies for the misleading comments. And yes, "muting" CV makes no sense, however I often use CV 1, 2 and 3 effectively as gates, set either to zero, or a high positive value, to trigger drum modules, so muting in this case would simply be setting the CV value to zero for that step.
flo
If you use the LFOs for envelopes / gates / accents, make use of the LFOx mode to be able to mute single steps... But you probably know and do that already... Yes, no easy way to mute such gates except dialing down the LFOx value of single steps.
daybed33
droningsphagettimonster wrote:
what module are you guys using for swapping patterns via CV in 1/2? I wish a future update will include some sort of pattern chaining...