(the product formerly known as) Epoch

Official support for: loomer.co.uk
Locked New Topic
RELATED
PRODUCTS

Post

Wouldn't it make more sense to have the Clock trigger output from the Array? Seems a bit odd to me to have the logic modules activate on triggers rather than filtering the information they receive. Is the "Contains" node sending a query upstream to the Array to get the output from the Array? If so, then the orange links appear to be bi-directional, which seems to have potential for confusion, but maybe I'm misunderstanding. Or does the Array constantly output to any downstream modules, and the trigger merely causes those modules to decide whether to open their gates? That would make more sense but still seems... odd. Plus it requires a lot of extra cables to pass triggers along.

Post

The orange Array connections still flow downstream, but rather then sending numeric CV or MIDI data they send a reference to an array object. All modules connected to the same upstream source act on the same array object, of which only a single instance exists. By allowing modules to pass the array reference downstream, we can guarantee execution order. For some graphs, it won't matter if, for example, a read occurs before a write, or vice-versa. But in a lot of cases, module execution order is critical, and by flowing like this, it's easy to both visualise and specify the order.

Regardless of whether a (for example) Erase module erases anything, it will always share the same array object source downstream so that further potential actions can act upon the array.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.

Post

colin@loomer wrote:
bungle wrote:When you create a container of a node structure, is this added to the library so it is available in the browser and right click ?
Yes. Collections of nodes are termed 'Macros', and are available everywhere a standard module is, including in the quick-add browser. Macros do have a little icon in the corner to help you distinguish them from the built-in modules though: it's nice to know at a glance that you can dive into a collection's innards.
Excuse my language but shit hot ;)
I know i will be moaned at, but looking forward to when this will be a modular midi and audio generator/effector, sequent on steroids hah
Duh

Post

Macros are stored as json files in the library directory, so they are very easy to distribute and share. I'm envisioning a good community of user-built macros that will quickly bolster the factory selection. And I'm sure it goes without saying, but you can have macros in macros (in macros, in macros.)
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.

Post

colin@loomer wrote:Macros are stored as json files in the library directory, so they are very easy to distribute and share. I'm envisioning a good community of user-built macros that will quickly bolster the factory selection. And I'm sure it goes without saying, but you can have macros in macros (in macros, in macros.)
Does this mean that you can have JSON files with in-line LUA, or does the LUA have to be in separate referenced files ?

Post

If you export a macro containing a script module, the script will be embedded in the json.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.

Post

colin@loomer wrote:If you export a macro containing a script module, the script will be embedded in the json.
Nice 8) :phones:

Post

How universal is LUA just out of interest ?
I mean in terms of somebody learning it from scratch, will the knowledge you build up be useful when scripting in Reaper and Renoise, is the language standardised at all so that you could prototype scripts in formely known as and then port easily to said other packages, or is it just a skeleton language and each implementation is completely different ?
Duh

Post

bungle wrote:How universal is LUA just out of interest ?
I mean in terms of somebody learning it from scratch, will the knowledge you build up be useful when scripting in Reaper and Renoise, is the language standardised at all so that you could prototype scripts in formely known as and then port easily to said other packages, or is it just a skeleton language and each implementation is completely different ?
It's completely universal, although obviously any platform API (so, I would imagine, !Epoch specific commands) would be distinct.

If you learn it for !Epoch, you will be well informed for other products that embed it - it's a well-used language.

Post

If you want to quickly get up to speed with Lua, you can't go far wrong with Programming in Lua. The first edition is free to read online. I'd guess that if get through the first five chapters, and then glance over the chapters on the standard libraries - which'll probably take anyone with programming experience just a couple of hours - you'll know enough Lua to get by in most situations.

For those who are interested in these things, Epoch uses Lua 5.2.3. Once 5.3 has had a few stability releases under its belt, I'll probably upgrade things to the 5.3 trunk.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.

Post

colin@loomer wrote:Epoch uses
So... Epoch? :o
CU
VK

Post

Sorry, that was an abbreviation for (the product formerly known as) Epoch! :P

Over the last and next few days, I have and will be polishing the panel view. This is where you build custom UIs for your creations. Expect some exciting new screenshots soon.

As far as possible, I've made the panel optional; for those who like the PureData / Max style of mixing UI components and code, the UI components are useable on the graph directly, and for simple patches I tend to not bother with panels. But once you start having tens, or more, rotaries, buttons, and grids, it's nice to group and arrange them into a control panel.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.

Post

Will there be LUA hooks such that the controls / feedback can easily be mapped to a 'generic' midi device like Ableton Push, allowing both display of parameters and colour feedback ?

;)

Post

Not for the initial release, but user-scriptable controller support a la Bitwig - a system of which I constantly hear great things about - is one of a handful of things that are pencilled in for an early 1.n release.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.

Post

colin@loomer wrote:Not for the initial release, but user-scriptable controller support a la Bitwig - a system of which I constantly hear great things about - is one of a handful of things that are pencilled in for an early 1.n release.
Excellent. As a recent Push & Bitwig owner, the Push4Bitwig example is a great incentive - it works superbly well, and shows how useful Push *can* be with other applications. :tu:

Locked

Return to “Loomer”