#363

The keyboard is QWERTY but the layout doesn’t look the same, I don’t think it’s the keyboard, after a while ORCA hangs even without that. It seems to weigh a lot on the CPU.

#364

i was having problems using a random operator in this position, if R gave it one of the later letters it would kill the sound card and a restart was required to get it back. it seemed to be fixed with one of the Timber updates, but now i wonder if it really was, i haven’t been using it lately, it definitely used to work. i will try it here and see what i find, i haven’t updated in awhile either.

#365

Timber position operator: I am on ver 200328 and this operator works but it has a problem that an enterprising soul with more coding knowledge than I might fix. currently it will work as long as you give it 0-9 or a-g. giving it an ‘h’ locks it to one position being triggered, even if you are running a ‘T’ sequence over it with in bound parameters also in sequence. if you go in while the pattern is running and change that ‘h’ to something in the allowable set it will recover and go back to alternating start locations. but if you pass it a ‘z’ it is unrecoverable and will lock that sample to the one position until you change the value, restart the unit and reload the pattern. I haven’t tested at what point between ‘h’ and ‘z’ the operator becomes unrecoverable requiring a restart.

not sure that Orca on Norns/Fates/Timber is something anyone is working on. when I asked about this bug previously in the Timber thread, @markeats said he didn’t know much about how Orca was using Timber. it would amazing to get this feature working well and it would be cool if you could go in and set position times more precisely, I haven’t found out how the sample gridding is cut up by the operator values.

#366

I have a German keyboard and since the last update around April, plugging it in crashes my Fates. So perhaps there’s a correlation with non-U.S. English keyboards causing issues.

1 Like
#367

For the most part, non-US keyboards are exactly the same inside. They just change the keycaps for different locales. (and then localization is handled by the computer. However, in the case of norns, it’s using the Raw HID info and not looking at localization at all)

I don’t think we did much followup on your crashing situation - if you want to DM me we can try to work through that. It’s very odd that a keyboard would crash the device though.

1 Like
#368

Could you post some samples of orca code that cause the problem? I’m not entirely clear based on your description.

Also it’s very likely newer updates of Timber could have a conflict or problem with your norns OS version. I’d suggest updating to the most current unless there’s a known incompatibility somewhere.

(last Timber commits were after the 200424 update)

#369

whats the best way to mute sequences on here, so far I am just deleting the * in the T operator. thought there might be an easier way I am overlooking.

1 Like
#370

yes, it looks this, where T is switching the start position. if you replace that ‘g’ with a ‘z’ it will evidence this problem. it seems like it could be solved with some boundary protection at minimum.

image
image730×378 86.6 KB

i do plan to update and concede it might be a version problem, but i thought that if the OP was not getting it to work at all, maybe my older version, working as it is, might be educational as to when this problem showed up. i remember it behaving this way or a little worse in the previous version, possibly locking up all sound until restarted.

#371

Hey y’all. I updated my branch with W/Syn functionality. Right now it only works with ar mode on. I added all of the w/syn parameters to the settings (Thanks @midouest I bit this from your Just-Play-With code :slight_smile: ).

The op is `… That is (octave),(pitch),(level)
I’m gonna be messing with this a lot more, so it will be changing, but I thought I’d share now for anyone that is really excited to play with this.

6 Likes
Yggdrasil
#372

https://www.instagram.com/p/CCUNKKlhjot/?igshid=1jrzjmwjm3znk Here’s a sample. 16n controlling w/syn parameters.

3 Likes
#373

Thanks everyone, I’m getting position changes with the operator, but only with samples that are of a certain length. Really long samples don’t seem to work…

#374

can you describe what is not working about it? how long a sample? i finally updated to 200604 and it does seem to be working better for me. it will still not function out of range and if i throw it a ‘z’ and then an ‘a’ i can get the sample to lock in position but if i delete it and use something in range instead it’s fine again and i don’t have to restart.

it is kind of clunky. it would be cool if you could set the points with some fine granularity and toggle between them.

#375

I’ve updated my branch to use the new clock system. I also got the keyboard shortcuts (cmd+> and cmd+<) working, so they will increment bpm +- 10bpm. Syncing to crow isn’t working, but after some testing that seems to be a global issue. I have the same problem with less concepts. I’ll test out syncing to MIDI today, but it should work. I’m planning on seeing if I can get insert mode key entry working next.

3 Likes
#376

@TanSaturn Would you be able to add your branch to the Maiden Library ?

1 Like
#377

I can try to look into that, or maybe I can bug @its_your_bedtime. I would probably have to make some changes since I replaced the OSC op to add one of my JF ops. I can probably resolve that without too much trouble by adding the OSC op back to = and change my jf op to | or - maybe. I’ll play around with it.

2 Likes
#378

since my update to 200604 the ‘V’ operator doesn’t seem to be working. input other than 1, 3, 4 and 5 produce no output and those numbers produce a different output than their input. then if i put in an identifier it doesn’t work at all and greys out the output. can i get a sanity check please?

#379

I cannot reproduce this error. Could you please show an example?

#380

edit: wasn’t paying attention!

#381

Try putting an H above your A. That made it work for me. You don’t need it when you call the variable.

#382

Sorry I don’t ve seen the reply:(
I confirm that the problem still exists. after a few lines of script, ORCA crashes and I have to force the restart to exit the app. what kind of information could help you to understand the problem?

Thanks