#81

Heya, loving this app, I have one question.

I am using this with teletype and JF, I was expecting that once I turn i2c mode off I would be able to use my JF in shapes mode for other patching.

However, it seems to constantly be reacting only to orcas heart.

So if i turn i2c off in orcas heart and then turn JF to Shape/Cycle nothing happens.

#82

So removing JF from the i2c bus works (and isn’t a big deal for me as I layer my patches using a sampler and don’t need a super dynamic configuration change) but wondering if this is expected behaviour.

I know we ask a lot here :stuck_out_tongue:

#83

thanks for the reminder - was going to fix this! will have a fix in the next release.

3 Likes
#84

Here’s a noisey thing using Orca’s Heart and Just Friends -

I’m loving how once you find a matrix setting you like you can lock in momentary mode and play over top without worrying about erasing what you had, super fun. Also +1 for octave up/down buttons! Here I am using TT live mode for just that.

A couple other suggestions-

There’s probably some neat potential using JF in sustain mode, but as it is the minimum gate length feels a bit long for this, maybe you could change it to go down to around trigger length?

I wonder if the RUN voltage would be an interesting candidate for this?

Thanks again for sharing this wonderful creation @scanner_darkly, it’s quickly becoming the heart of my little system.

5 Likes
#85

yeah agreed the range can be extended (right now it’s between 100ms and 4sec, i also need to change it to be based on the clock interval instead of a fixed value).

possibly? from the doc:

The frequency relationship between the modulation & carrier oscillators is set via the RUN jack, though is matched at 1:1 with no cable attached. Positive voltages move toward 2:1 at 5V, while negative sweeps down to 1:2 at -5V giving many grumbles.

is this something that would be an interesting parameter to control? remember that due to grid UI limitations you can only choose integer values between 1-6.

1 Like
#86

while thinking about how to include more scales i also realized it would be really useful to be able to sequence scales in addition to sequencing transposition. i often find that when transposing a sequence i also want to change a couple of scale notes.

this also got me thinking - why not sequence other algo parameters as well then? mod matrixes can certainly provide interesting unexpected results but sometimes you want more control.

here is how i think it could look like. when on any of the parameters pages the 2 rightmost buttons in the 2nd row start/stop the sequencer and enable or disable it for the current parameter.

if the sequencer is disabled you can just edit the parameter value as you do now. if it’s enabled but not running, it becomes a preset system for parameters - when you select a step, it will switch to that step for editing and will immediately apply the step value (and will do that for all other parameters that have the seq enabled). if it’s running, selecting a step selects it for editing but the values applied are determined by the current sequencer step. basically, same as it works now for transpose.

sequencer
sequencer1230×623 35.9 KB

transposition page will change as follows. similar to how it is now, but the sequencer row is in the 2nd row instead of 3rd. this frees space for 4 scales. when the sequencer is enabled for transposition, you will be able to sequence which scale is selected. i marked the buttons to the right of scales as reserved as i have a feeling they’ll be needed for some additional functions. instead of individual scale +octave buttons, the first and the last transpose buttons will now serve as +octave and -octave.

transpose
transpose1226×621 46.9 KB

since there are 4 rows now required for scales i don’t think it makes sense to have scales available on each parameter page. this area could potentially be used for something else.

TL;DR: with this change you will be able to either use it as before if you don’t touch the sequencer at all, or use it as a parameter preset system (for selected parameters) as an additional performance tool, or use it as a way to arrange more complex sequence changes (“sequence the sequences, not notes”).

i also considered extending it to sequencing matrix snapshots / volume snapshots / delays, but i think the complexity of the UI will outweigh the benefits. and i think it might be actually more interesting to have a complex sequence arranged - and then remix it live with matrixes / volume automation / delays.

thoughts?

7 Likes
#87

You were reading my mind! This is excellent and your proposed design looks great to me. Looking forward to it! Thanks!

2 Likes
#88

Still running v 0.3 - I’ve experienced startup crashes a few times. Grid begins to power on, but the lights only make it about 1/5 of the way down from the top left corner before shutting off.

Definitely not a power issue, I have a good bit of room.

#89

which module are you running it on? what happens if you turn it on with grid unplugged?

#90

Hmm I didn’t realize the range was so small. Maybe it would still be interesting with a range of 6 values like 1:2, 1:1.5, 1:1, 1.25:1, 1.5:1, 2:1? I’m not super knowledgeable when it comes to FM stuff so maybe others can jump in here, might offer some nice timbral variety though.

The new sequencer feature looks stellar!

1 Like
#91

Sorry, I’m running it on Ansible. I haven’t tried starting the system with Grid unplugged (the issue isn’t consistent).

When it does occur, unplugging and plugging in Grid does nothing. I need a complete reboot.

#92

can you describe in more details what happens exactly?

once it shuts down, are any other modules in the case affected? and on ansible do you still see output LEDs blinking or are they frozen?

and just to be sure, ansible can consume up to 200mA on +12V rail, is your overall +12V consumption under 80% of what your power supply provides?

#93

Grid begins to power on, but fails to do so completely before all lights go out. The lights on Ansible freeze (some on, some off). No other modules in the case are affected.

I’ll double check consumption later. I’m using a pretty hearty Trogotronic PSU and never had any issues when running the standard Ansible firmware. This also happens relatively infrequently (maybe 5-10% of the time).

#94

yeah doesn’t sound like it’s a power issue.
would you be able to take pictures of every page on the grid and PM that to me?

#95

Surely! I’m at work for the next few hours, but I’ll get you some shots later.

1 Like
#96

Oh, I totally missed this but thankfully got a reminder via Brians newsletter today! It looks great on a first and very short glance!

Before I try it on all my modules and loose my presets - how does Orca’s Heart beat in Earthsea’s body? Two full voices, speed and two (by now) unused knobs? That would be really nice.

#97

right now on earthsea you’ll get 1 full voice and 2 more voices with CVs only, no gates. i’ll consider changing it to 2 full voices.

i would hold off with updating just yet - i’m currently working on a new version which will have quite significantly different UI. i tried to find a way to avoid it but there is no way to fit what i’m planning into the existing UI without it feeling awkward.

i hope the benefits of the change will outweigh having to get used to the new UI - it’ll be both more streamlined / logical AND more powerful. i’m really quite excited about what’s planned and can’t wait to share it with you all.

i will however post one more version before this major update which will have matrix snapshots and 4 scales as well as a potential fix for the ansible issue @gexex reported.

9 Likes
#98

One full voice and two drone voices sound appealing too! Looking forward to see your plans unfold.

1 Like
#99

i have to say, i think OH really shines when used with i2c devices. it’s not just having more voices with complimentary sequences, but once you start morphing or randomizing volume of each voice individually or delaying different voices by a different amount it really comes alive.

5 Likes
#100

new version 0.4 posted:

  • number of scales increased to 4
  • 4 snapshots for each mod matrix
  • fix bug with grid being inactive after bootup
  • JF should be reset to regular mode when choosing another i2c device
  • can now transpose by octave up or down
  • minimal gate length is smaller

there were some UI changes necessary:

  • scales can now only be edited on the transpose page, not shown on parameter pages anymore (since there are 4 scales)
  • transpose seq start/stop button is now in the rightmost column in the 2nd row
  • on the delays page swing and delay span rows are swapped (so that the delay span is closer to individual delays)
  • on matrix pages the momentary mode button is now directly above the clear/random buttons
  • there are no more +octave buttons for scales (these buttons are now reserved for future use). instead you get general +octave and -octave (press again to turn off). see this page.

the wiki has been updated with the latest info.

15 Likes