koalaboy wrote:
Anyway, I think you've already answered as much as I can ask until I actually see how Epoch all hangs together and what it can/can't do.

There are tons of questions from my side also, but its more of the limited informations you gave to us till now, as koalaboy says with more information there will be also more questions.

Examples:
like to have Shift Registers lenght in 4, 8, 16 and 32 steps?
what about a MatrixSwitch with 8x8 and 16 x 16 routing
what about a SwitchSequencer that has an in and out per step that is switched when the step is reached
do they exept any value to get shifted?
If I am on a Mac DAW with AUs can I also load VSTs in this AU?
could AUs and VSTs used together?
Do we have Presets for each module?
are the single steps of a sequencer to be modulated by something like another sequencer, LFO and so on?
is it possible to have several sequencers with their AUs or VSTs in parallel?
is there a CV to AudioModule?
is there a Gatesequencer with outs per step?

The built-in Shift Register only has memory for 1 item, but you can chain them together to make a longer buffer. You can this wrap this in a macro to make your own larger shift register (although I expect I'll probably include bigger shift register macros in the default user library anyway.)

Alternatively, you could write a Lua shift register; it would only be a few lines of code, I imagine.

what about a MatrixSwitch with 8x8 and 16 x 16 routing

You could probably build this with switches, but I imagine the wiring involved would be unwieldy. At the risk of sounding like a broken record, I'd say this would be easily done with a Lua module (and again, probably something I'll include in the user library. Sounds useful!)

what about a SwitchSequencer that has an in and out per step that is switched when the step is reached

Yes, you could do this with a counter, a compare, and a switch.

do they exept any value to get shifted?

Anything can be wired into the shift register, yes.

If I am on a Mac DAW with AUs can I also load VSTs in this AU? could AUs and VSTs used together?

Yes, there is no problem with loading a mix and match of AUs and VSTs. You can host VSTs in the AU version, and vice versa.

Do we have Presets for each module?

Some of them do, mainly the sequencers, macros, and Lua script modules. The sequencers also have various generative functions for randomly populating them. I anticipate extending this to user created generative functions in a future version.

are the single steps of a sequencer to be modulated by something like another sequencer, LFO and so on?

You can't (yet) modulate the actual values in the sequencer directly, but you can modulate the output values, which more-or-less amounts to the same thing (and in many ways, is more flexible.)

is it possible to have several sequencers with their AUs or VSTs in parallel. is there a CV to AudioModule?

Yes and yes.

is there a Gatesequencer with outs per step?

Both the note sequencer and Drum sequencer have gates per step. They also have gate inputs, so you can modulate the gate with another source. Or you can extract the notes as they output from the sequencer, and change the gatelengths. Or skip the sequencer altogether and use a discrete CV to Note module. Or ... and ... or ... plenty of options here!

Great questions, and it's reassuring to hear that this is requests that I've already got covered.

Having crammed on LUA at the weekend (easily manageable even for an old Java hack like myself) I can see the huge potential. Of course, I may never actually make music, but simply play with routing data

jue wrote:is it possible to select the next step within a sequencer to play by a sequencer that sends the stepnumbers?

Yes: all sequencers have a step index input which specifies the step to play. It's easy to use this to write your own play position logic. (They also have a step index output, with which you can chain sequencers together so they both play the same steps at the same time.)

This would be nice to use the sequencers as eventtables or are there some?

For v1.0, the CV sequencers will suffice. I do have some plans for proper event tables modules at some future point. You could also build your own, in the interim; perhaps with rotary controls or constants, and a big n:1 switch?

Whats the maximun stepcount by a sequencer 16 /32/64/128/256

At the moment, you can set a sequencer step count of 8, 16, 32, 64, or 128. I'll probably increase this before beta to 512, or even 1024, depending on the memory requirements. If this still isn't enough steps, you can also chain sequence patterns together. Its probably worth mentioning here that you can zoom in and out of the sequencer display, so you'll have no trouble editing those hundred-odd steps.

Think the solution with the LUA module is not for everyone, please have in mind that it should be a tool for musicians and composers that are no programers.

Sure, I expect that a number of people will use Lua modules without even caring they are editable Lua modules. For all intents and purposes, they work just like the standard built-ins. But with Lua, a little knowledge goes a long way, and writing simple modules is within the realm of anyone. Most are only a few lines of code, after all.

Generally though, I'm relying on Lua to provide modules which I don't want to be part of the core library. Things too obscure or specialised. Things that'd only serve as clutter if they were listed amongst the built-ins. A module which produces MIDI notes based on Conway's Life may be awesome, but probably not the sort of thing I see as a core component. As a script in the Lua library though? Sure!

(I do also anticipate that any Lua modules which prove widely useful can easily be re-coded and included as C++ built-in for a future revision.)

I've been busy refactoring a lot of Epoch's modular code, removing as many limitations as possible. Prior, there were limits to the numbers of modules you could create, limits to the number of connections to a single port, limits to the size of data flowing down a cable. Well, no-one likes limits, so I'm pleased to report most of these are now gone* - and within a few days, all limits will be lifted.

Time well spent: it's the much better product after all this, let me assure you!

I've been busy refactoring a lot of Epoch's modular code, removing as many limitations as possible. Prior, there were limits to the numbers of modules you could create, limits to the number of connections to a single port, limits to the size of data flowing down a cable. Well, no-one likes limits, so I'm pleased to report most of these are now gone* - and within a few days, all limits will be lifted.

Closer, but still not close enough that I'd be confident in giving a date. Pricing is still undecided, but think around the same bracket as say Numerology, or Thesys. The beta will also have a decent 'early adopters' discount too, which I anticipate remaining in play until the official 1.0 release.

MitchK1989 wrote:as someone who uses a eurorack modular and has been jealous of OSX users for the whole numerology thing - I think I love you.

I recently tried to resurrect my daughters old macbook pro just so I could get Numerology A few keys don't work (coffee spill) - including the important enter key - and it costs a fortune to get fixed. I could have run it with an external mouse and keyboard, but about that time I heard about Loomer and Epoch, which I think will suit me better anyway as I like the flexibility of the scripting add-on. So her old machine sits in that old-tech zone where it isn't actually useful but I can't bring myself to throw it away.