It probably spawns a process that cannot have access to your midi devices? Do you have access to the chrome inspector from the jweb object?

1 Like

image
Recreating the old BOUNCE operator that would count to and integer and back down.

Also if anyone wants to pop into my Discord I have a channel carved out for Orca. PM for an invite :slight_smile:

Anyone have some alternatives to recreate the old bounce?

Like this? You might wanna try the tables.orca example to see how the A/B/L/M works side-by-side.

C8..
0B4.
.4.X

Yea, that is exactly what I was thinking too. unfortunatly I don’t seem to be able to access the inspector inside of jweb. Waow that is super limiting. So disapointing when something you think is possible to do is not at all possible.

I think I have to abandone the idea of running orca inside of jweb for now. All of this is totally on the extremely limitid jweb functionality though. I will try write cycling74 and see if there is anyway of fixing this.

Oh well at least we got some cool new commands for Orca! :wink: I think I will continue working on the Leap Motion projekt instead for the time being.

question, sorry if its been asked already, but what would be the minimum acceptable screen resolution to use this. would it be usable on a small screen like this? s-l500

2 Likes

Here’s an example of orca-c on raspi with an adafruit display (320x240 TFT)

It’s pretty small, but doable?

6 Likes

Hi, new to ORCA here after being recommended by a norns user to check it out. Its pretty damn cool but the documentation is a bit all over the place. :slight_smile:

I was wondering if there was a way to send midi to two separate external devices over USB, i tried searching through this thread and i dont see anything. Im running the pi build on a 2.8" tft screen. I can send to one device or the other but not both.

You cannot send midi with the midi operator to two devices, you would need to use the UDP operator instead and make your own router.

Wouldn’t it be possible to have the 2 midi devices on 2 separate midi channels?

Or perhaps the second device would need to be a “Thru” from the first device?

It might be possible to use aconnect on linux to route the midi from one device thru to the other.

if you have a gui on the PI, maybe try the aconnect gui
sudo apt install aconnectgui

or patchage

I made this random looping sequencer similar to the Turing machine/marbles.
It lets you have control over the probability the sequence will change, possible scale/notes, possible octave ranges, velocity, note length and midi channel/note on off values.
Controlling the digitakt/tone with it here.
patch code in the video deception.
EDIT- I updated the code, it now has a central place to set number of steps and clock
Also added directions on how to use it in the video description.

20 Likes

in the video above im controlling the digitone and digitakt by only sending midi to the digitakt and using the digitakt’s midi channles to relay the midi to the digitone. doing it this way because im using overbridge (usb midi out of my computer to the digitakt) then midi jack out of the takt, into the tone. I’m sure the midi through method would work just the same.

3 Likes

Amazing!! Good job @L4COUR

1 Like


I am further investigating the matter. I got in contact with @jeremyc74 through the new slack channel for Max related stuff.
Screen Shot 2020-05-12 at 15.19.24
So webMidi is not enabled currently in jweb currently. He says that he will consider a feature that would allow users access to the remote debugger port.

One should also be able to connect to jweb via chrome’s remote debugger tool. I will have to figure out how this is done first though.

I am excited to see where this is going :slight_smile:

Experimenting with this snippet:
Screen Shot 2020-05-12 at 1.34.32 PM

Trying to dynamically change waveforms in Pilot. But K only seems to read the first 6 characters of an 8 length string. Weridly variables c,d read above if I place them below the K operator but not beside or above

1 Like

Variables always have to be written before they are read.

.....Va
.......
aV5..Va
.....5.
.......
aV6..Va
.....6.

Hey all! New Orca user here- it’s incredibly fun. Seriously the most joy in learning a new tool/software/language that I’ve experienced in a LONG time.

I’m wondering if anyone has done any work on getting a general purpose MIDI to Orca tool up and running? I’ve spent some time tonight forking the aioi companion app (https://github.com/MAKIO135/aioi) since it seemed like a good starting point- both from a visual consistency perspective and it already had some UDP client code setup for sending data to Orca. I worked with the node-midi library (https://github.com/justinlatimer/node-midi) to read midi-data from my beatstep pro and get it sent to Orca in base 36. I have a prototype working, but before I invest more time in it, I’m wondering if anyone has already gone down the road of getting MIDI into Orca.

I’m testing with my beatstep pro because I have it laying around, I don’t mean I want to externally sequence Orca, I just want to have knobs/faders/pads for changing parameters and trigger things in a more tactile way (I can turn two knobs quickly, can’t change two values at once with a keyboard/mouse).

Like I said, I’m also a new Orca user, and since I’m going down the Electron path to achieve this currently, I’m also sensitive to the fact that if I decide to use Orca-c on a dedicated raspberry pi setup or something I might be out of luck. Maybe I should use python or something instead? How would people ideally like to connect MIDI control surfaces to Orca? Or does anyone actually want to besides me?

4 Likes

The best way to do that, since you’re using node anyways, it to make a mini UDP framework that converts your midi notes into orca commander commands. So you can read incoming midi from your beatstep knobs, and write the value into an orca cell via a udp command(wr:5;2;4).

Here are some of the things you can send via UDP.

  • play Plays program.
  • stop Stops program.
  • run Runs current frame.
  • bpm:140 Sets bpm speed to 140 .
  • apm:160 Animates bpm speed to 160 .
  • frame:0 Sets the frame value to 0 .
  • skip:2 Adds 2 , to the current frame value.
  • rewind:2 Removes 2 , to the current frame value.
  • color:f00;0f0;00f Colorizes the interface.
  • find:aV Sends cursor to string aV .
  • select:3;4;5;6 Move cursor to position 3,4 , and select size 5:6 (optional).
  • inject:pattern;12;34 Inject the local file pattern.orca , at 12,34 (optional).
  • write:H;12;34 Writes glyph H , at 12,34 (optional).
  • time Prints the time, in minutes seconds, since 0f .
  • midi:1;2 Set Midi output device to #1 , and input device to #2 .
  • udp:1234;5678 Set UDP output port to 1234 , and input port to 5678 .
  • osc:1234 Set OSC output port to 1234 .
4 Likes

Thanks, I’ve gotten this far already actually. I have successfully written a glyph based on a knob on my controller to Orca. I’m just curious if anyone else already has built a MIDI -> UDP -> Orca utility or something so that I don’t recreate the wheel.

Here’s a video explanation of my little MIDI project. Would love to hear any feedback on what people would like to see from a tool like this. Short demo, then a technical overview. I might end up just implementing this in python with a config file instead of a web view wrapped in electron, as I’d like a more performant option since I intend to use a raspberry pi eventually.

9 Likes

Merging generative elements with intentional playing / musicing is what I’m interested in. So potentionally having not only knobs but notes available to map and use in Orca would be great. Alltough I still didn’t invest much time in Orca yet.

4 Likes