Also it’s affected by the resolution of the Orca, if in its full screen I need to set resolution on the Orca really low or minimize the Orca window to a smaller size, the larger the space Orca occupies when using a high resolution the more it delays the signal.

Are these both running on the X200? Is one of them a VM inside the other?

Yes, I didn’t notice before because I was pausing and resuming a lot but I can easily reproduce it with the following parameters.

image

Sending to pilot via UDP, if I hold an arrow button to move around while it’s running the timing is thrown off.

Not a VM but on a separate partition and installation. I think it has to do with the resolution. Not sure if it’s the same case on high spec computers? No problem if you’re not moving @ around even on full screen but when you start doing anything that’s when the glitches start. I thought it had to do with my setup.

Yeah Orca’s timing is not an accurate science. It’s currently not async, that means that the longer the frame takes to render, the more delay will be injected in the timeline. I have not really looked into this yet since I usually work in small sizes, but that’s something that’ll have to be addressed at some point.

In the meantime, the Orca-C port is a good solution for slower devices.

Aah, so do you mean to say the Orca timing is affected by a computer’s specs? My total CPU load is actually really low especially for a low powered machine, doesn’t go over 50% on my core 2 duo CPU in most times and the same thing with a 4gb ram. So I thought it’s got nothing to do with the specs of my computer.

I’d like to work on Orca in full screen since I don’t want to see any distractions and I want it to be in focus. Part of the Orca’s appeal to me personally is the aesthetics, I find it really beautiful to look at. I’t also what I intend to project live.

Oh wait, I just re-read your original question.
Is it possible that you have a really old version of Orca?

The weird delay, midi note spacing issue was fixes maybe 2 months ago. Could you try downloading a new build and test this again.

I think I installed the latest installer, the one that’s uploaded the other day since this are both newly installed OS yesterday. But I’ll try that again now just to be sure.

1 Like

Keep me posted :slight_smile: If you need more interactive help, join me in the Orca Chatroom.

The weird thing is I don’t remember having this problem before besides some minor delays from time to time but not as bad as it is now. I was thinking maybe something was changed with the latest version.

What I don’t like about Orca is that every time I watch Allie’s awesome tutorials and replicate it with some modifications to make it my own, I usually end up making something I fall in love with by accident and then just listen to it for a while without doing anything else lol, it’s so counterproductive! And with the randomizations, it takes a long time for me to get tired of listening to what I have just done.

6 Likes

I just pushed a new build that should be tons faster :slight_smile:

9 Likes

Just learned about ORCA a couple days ago (thanks to this thread) and have really enjoyed playing around with it! Such an inspiring piece of software! Here’s a little sequence I cooked up this morning using ideas from @Allieway_Audio’s tutorial videos.

24 Likes

it’s beautiful, well done :slight_smile:
Very interesting use of G to create E projectors, never seen that one before!

what are your thoughts on an operator to mute a given midi channel? I like using lots of different sequencers combined to send midi to single midi channels and i think it would be cool to have an operator like this to block a midi channel. would be cool for performance and sequencing!

something like:

! .

where:

! n

flip flops mute state of midi channel n on bang

Well, this might be possible using the midi operator :0.

  • Do you want to send noteOffs for all the active notes that are still playing?
  • Or do you just want to stop any notes sent to a channel from being played?

second one! 20chars******

Ah! Okay, in that case, you should try to just make a switch that acts as that mute operator, for example:

..aV*.....
..........
.Va.......
.*d4......
...:03C...

The d operator will only bang the midi operator every 4th frame if the a variable is set to bang(*). Paste this in your patch to see it in action :slight_smile:

3 Likes

Thanks! That use of G is an example of an idea borrowed from one of @Allieway_Audio’s videos.

2 Likes

Working much better, ran it through my test scenario and didn’t see the stuttering and timing issues.

1 Like

Heya! Just realized, I shared this in the chatroom a while back, but figured it might be fun for people here to play around with as well, so here is a Linear Feedback Shift Register (LFSR) I made in ORCA using the loop object. It generates a pseudorandom rhythm that will only repeat it’s 7-bit state every 127 ticks! Try sending the bangs down to some midi triggers with jumpers and you’ll get some nice pseudorandom rhythms - change the X value on the offsets to get some variant rhythms which will repeat more often. Have fun :slight_smile:

..........................................................................
..................27O.....................................................
..........................................................................
.............15O....J.....................................................
...............*Y*Y*......................................................
...................JJ.....................................................
..................F*......................................................
.................F........................................................
...............7L..***.*..................................................
..........................................................................
15 Likes