Architect beta for macOS, Windows, and Linux. 0.10.5 now available
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Also, am I correct in thinking the [delay] objects want a denomination of 960 PPQN for their input?
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
No, I am! [MIDI to tuple] should output ("controller", 38, 50, 1), as that is that proper name for that MIDI message type. If you use ("controller", 38, 50, 1) to [Tuple to MIDI], that should work.
I'll get this fixed, but probably add "cc" as a valid alias for controller in [Tuple to MIDI] to ease the transition.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
Yes, the delay time is in ticks, and Architect's tick count is 960PPQN.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Cool, thanks Colin!
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Wow, another question: I take it that--although you have the wonderful random list generating objects--you have no explicit [urn] object in Architect? Not sure I can think of a case where this would be necessary; just curious.
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
As I'd not heard of it until you mentioned it, no! So, I take from the (briefly googled) description, it essentially generates a set of numbers in the range [0, n) and outputs them one at a time, without duplication, when signalled?
Yes, I can see the merit in that. Easily added, no problem at all.
Yes, I can see the merit in that. Easily added, no problem at all.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Thanks! I realize after some thought that repeated random sequencing of a list without duplicates is different than repeated random lists, or repeats in the sequence.
It would be great if there was an inlet for the list, and the [urn] object would just repeatedly sequence them without duplicates.
It would be great if there was an inlet for the list, and the [urn] object would just repeatedly sequence them without duplicates.
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
That seems a good approach to take, actually. This way you could use it for numbers (a la [urn]), MIDI tuples, or anything else you could stuff into an array.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Hi Colin- Out of curiosity, I assume it's not possible to build 2D arrays? Like so, for instance:
Arrays in Architect are 1D then? One must use Maps if one wants to work with multidimensional data? But Maps don't guarantee the order of their indices, do they?
(I realize you can do things like create a 2x36 element array by declaring it as 1x72, then accessing it with suitable math.)
Thanks!
Arrays in Architect are 1D then? One must use Maps if one wants to work with multidimensional data? But Maps don't guarantee the order of their indices, do they?
(I realize you can do things like create a 2x36 element array by declaring it as 1x72, then accessing it with suitable math.)
Thanks!
You do not have the required permissions to view the files attached to this post.
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Working on something else ATM, but realize that [shuffle] would work well as the basis for an [urn] macro.
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
One final post for the day: are the [sequencer] objects in Architect essentially read-only? For example, there's no way to dump the current values of the pitch rows as array data?
- KVRian
- 698 posts since 7 Dec, 2009 from GWB
Getting back to 2D arrays, it looks like you can use [select element] to get things from the primary index, but not the secondary:
Using [for each], [join] and a [latch] however, you can extract all elements of a secondary index through iteration:
XML download here: http://vze26m98.net/loomer/arrays-19121 ... 191217.zip
Using [for each], [join] and a [latch] however, you can extract all elements of a secondary index through iteration:
XML download here: http://vze26m98.net/loomer/arrays-19121 ... 191217.zip
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
[shuffle] -> [for each] works well for as an [urn] for arrays. Thanks for the tip.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
In theory it is. The problem in your example is that [build array] interprets a tuple of (index, source-array) as an instruction to place the source-array contents, element by element, into the destination array. So, taking the middle [data] item, it will place 0 at element 0, 1 and element 1, etc.
One work-around is to use an array of arrays as the source, so instead of (0, [0, 1, 2, 3]), use (0, [[0, 1, 2, 3]]). It's not great - and I really need to think about how I can improve this use case - but it does work.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
-
- KVRAF
- Topic Starter
- 2682 posts since 25 Aug, 2003 from Bournemouth, UK
Currently they are; but I've had lots of requests for access to this data via outlets, so it's sure to be added at some point.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.