Ah, maybe that’s my problem…that not all the lower-case ops are online yet.

I’ll give your idea a shot though, thanks!

Think I might also try it via the Timber parameters, instead of the triggers.

1 Like

This ‘kinda’ works! The button triggers a bang consistently, but the ‘c’ changes intermittently on the bang. I’m still playing with the right D settings, but I think once the code is ironed out, this approach will work!


Also, I think setting up a grid row as a slider, and returning numbers instead of bangs will open up a solution.

1 Like

Updates

  • = OSC operator: locks each consecutive eastwardly ports. Unlike original, this takes full paths. Use ; delimeter to specify values, eg =grid/led/set;x;y;z
    Havent fully tested yet.

  • ‘^’ operator: rate changed to mode, now operates on bang by default. Set mode to 0 for random in-scale notes. Values > 0 will set corresponding scale note.

  • All passive operators working

:new_moon:

13 Likes

Is there a chart for the scales somewhere?

Also: looks like the grid ‘slider’ option (leaving x or y blank) is broken.

Are the saved projects deleted every time I git pull an update? No big losses yet, but good to know how to backup stuff

dont think so saved projects are in dust/data/orca so git pull on dust/code/orca wont change it. :wink:

No, but there are still may be breaking changes prior to 1.0 release

Is there a way to reset the frames/counter, similar to the desktop version?

Is it possible to use a midi keyboard to control one of the timber operators melodically, as you would with timber keys?

I’ve added midi in operator, but it only outputs values 1-z for now. Havent really tested any sound operators in original orca :upside_down_face: Btw, you can also use grid sliders for this

2 Likes

How would one go about getting the 16n faderpack to interface with this app? Via midi? I haven’t been down that road yet…YET.


Loaded up the stems for a track into Orca. Sample triggers on the left side of Grids, two loopers on the right side. Played this down live, although I did edit it down from a longer jam…thank god!
11 Likes

@dudadius that’s a great idea using the loopers :slight_smile:

I have a quick question for @its_your_bedtime Im not quite sure how the midi operator works

  • & midi in : Outputs midi note

Is this for playing with a midi keyboard? If so does it need to be banged?
Hoping to incorporate a faderfox slider which I guess is midi CC?
Would like to bend and warp a few short looped samples with the slider from inside Orca

1 Like

Jason, tnx! Yea, there are so many modulation possibilities, I’d like to get my 16n fader or at least Arc routed to some of them.

2 Likes

Updates

  • added channel input for & midi in
  • new midi cc in operator - ^
  • ^ r.note is now $

These ( & and ^ ) listen to incoming events on specified channel

12 Likes

!! thankyou in 20 characters

1 Like

Someone was asking over in a help thread…

Does MIDI Clock IN work to control tempo/bpm?

I did a quick test and bpm did not change.

EDIT - also a request - can the MIDI Channel param be moved to the top of the params page (below bpm). Currently Its buried at the bottom which involves scrolling for days. :smirk:

I was also wondering about this, tried to no avail

I’ll check midi in (i was sure that handled by beatclock lib itself).
You can hold shift+arrow for fast scroll to the bottom

Did some testing… Beatclock was not getting passed the midi data so it was not handling clock.

I was also seeing a nil table error on orca.vars.midi[m.ch] = m.note so I made the following changes.

This works with external clock OK

  orca.midi_out_device.event = function(data)
    clock:process_midi(data)
    local m = midi.to_msg(data)
    if m.type == 'cc' then
      orca.vars.midi_cc[m.cc] = m.val
    elseif m.type == 'note_on' then
      orca.vars.midi[m.ch] = m.note 
    end
  end

NOTE: bpm counter in params will not update with the incoming clock bpm. Still not sure how to make that work properly

4 Likes