#344

Looks like you or GitHub were having network issues - so downloads corrupted.

1 Like
#345

So did the structure io sidekick change i the last few days?
an update seems to have nuked the patches developed for Pd on it.
Is there a proper way to uninstall sidekick?

#346

no, as mentioned in the update… (and known issues)
the update process removes patches, so back them up beforehand :wink:

they will work fine if you put them back.
(note: norns mother had a few of its own issues, but I think these have all been resolved now)

Ive ‘fixed’ this update process in the next release.
however, the way apt works means that the next upgrade will do the same, but after that it will be permanently fixed. (unfortunately, not something I can avoid… apt will run the ‘old’ script before it gets a chance to run the ‘fixed’ script)

(I plan to put out that new release, either today or tommorow … want to get one thing tested, then i’ll release)

wiki explains how to uninstall.

1 Like
#347

If i set up my norns with the current image, load samples in and have sidekick/mother/orac on it, will i kind of mess things up when the official release is out to update and loose the structure and stuff inside my norns?

Especialy since we edited /we/dust to /we

Please some valid info, thanks

1 Like
Norns 2.0 beta
#348

as stated on the original post and wiki - orac/sidekick does not affect ‘normal norns’ at all.
I don’t touch any of the norns software.

as for if norns 2.0 will break orac/sidekick - no idea, i doubt it, but as ive not played with it - I cannot say.

I’ll no doubt have look at norns 2.0, once its been released… and see if there is anything that needs tweaking. - i don’t have time to track the beta.

1 Like
#349

2.0 was released about a year ago. i assume people have been using the two systems together successfully.

1 Like
#350

Yep i mixed sth up again… the shield is allready 2.0

#351

Cool, i assumed (incorrectly) there was a new release ( i thought i saw a thread about a beta, must be going mad ;)) - I’m on a release from a few weeks ago , so guess I’m pretty up to date then :slight_smile:

#352

I saw the same… we are all mad in here

2 Likes
#353

Is there a different method for installing this on fates? Having trouble understanding how to install and what to type where.

#354

Works on fates, install instructions on wiki. ( top post)

#355

I got ORAC on Fates to crash spectacularly several times last night, with a bunch of graphics glitches and it would stop responding then restart after a minute, hanging on the “connecting…” screen.

I also had a problem last week where no matter what patch I loaded it would never let me access S2. I had to reboot and it started working.

Time for a fresh install? or are there any processes I should keep an eye on to see what might be causing this?

This is what I was doing at the time last night, and I assume isn’t related to those problems I had:

  • r_reverb in A1, ext audio thru, nothing after it
  • grids module loaded into B1, nothing after it, sending midi on ch10
  • clock on S2, tempo 10 and ext midi enabled. I couldn’t figure out how to completely disable the internal clock with it still sync’ing. If the external clock stops the lower tempo takes over. Is there a better way to do this where the external clock is the only source? I did not have a midi loop, I know that much.
#356

sorry, didn’t see this @Garfield …

crashes - really I need a way to reproduce the problem, e.g. you could save the patch, and post it here, or tell me some steps that reproduce it.
reinstalling is unlikely to solve the issue - it sounds more like a specific set of circumstances.

an external clock should always override the internal clock - of course,
if its stops, then yes… the internal clock will take over.
this is because currently there is not concept of transport, or the idea that the clock is ‘stopped’.

I do want to at some point look at this, but its not that simple - as it means re-writing the sequencers so that they can sync on startup.

#357

small update to Sidekick/MEC/Orac to resolve a few minor issues.

as mentioned before:

#358

No worries! I haven’t had a chance to dig in again. The glitches/crashes did seem to be exacerbated by having parameters modulated by LFO in focus, but I haven’t tried to reproduce it from scratch. I’ll start the patches fresh and let you know if I continue to have the crashes or graphics issues.

For clock, is the system simple enough to have an internal BPM of 0 as a possibility without a ton of work? I’m fine with basic clock slave with no reset or transport on the sequencers. This is what I (and I think many others?) already deal with in the analog domain for some gear.

#359

I had the same port error as Martin when I tried to restart sidekick from the VNC. I couldn’t figure out what was using the OSC ports, but disabling them in sidekick.json resolved this problem.

#360

Port error is fixed on the update I’ve just released :slight_smile:

( so make sure it’s not disabled after update … it’ll cause other issues later ;))

1 Like
#362

Sorry, been scrolling here for hours but can’t find an answer. Is it possible or not possible to use the grids with Orac? If it’s possible, how do I get it to work?

Thanks a lot!

1 Like
#363

It’s not something I support as I don’t have a grid.

If you can get it to spit out midi, then it’ll work.
( as orac supports midi).

#364

Ah ok. Thank you for your answer. Hope Monome sends you one :slight_smile:

2 Likes