#142

New Update v0.3.0

  1. Now midi notes can access to submenus on complex patches.
  2. Fix init led indicator.
  3. Midi rework
  4. Minor bug fixes

Update via “Update Mother” on sidekick menu.

Example of submenu patches:

Try submenu feature on this patch: LFOmlog

9 Likes
#143

hmm, I’ll look into a way of you doing this so that you don’t have to overwrite the sidekick files, or end up with mother being loaded for every pd patch.
as i think both of these are undesirable …
(as when I release a new version of sidekick i will be overwriting this stuff)

also i should probably have an externals directory, as for similar reasons we don’t really want patches to have my NuiPd.linux distributed with them, as this will prevent the newer version being picked up.

perhaps some way of having ‘organelle’ patches all in a sub-directory which inherit properties from that directory, might be the solutions , as supporting sub-directories is a useful feature for sidekick anyway.

… in other related news,
I pretty much done the new NuiLite, with a new pd interface and also an osc interface using sidekick - both have a much wider set of graphics calls :slight_smile:
hopefully next day or so, my plan is to make some tweaks to orac, in particular add aux button and auxline support - which’ll help with quite a few modules (sequencers in particular)

oh… and im considering something brand new and exciting too…

4 Likes
#144

It receives and additionally does indicate that it’s sending midi out near the O on certain patches like arpeggio synth.

Here’s what‘s showing with the my Mio midi interface connected to fates via USB so that I can send midi back out to the QuNexus via Bitwig:

~ $ aconnect -l
client 0: ‘System’ [type=kernel]
0 'Timer ’
1 'Announce ’
Connecting To: 128:0
client 14: ‘Midi Through’ [type=kernel]
0 ‘Midi Through Port-0’
client 20: ‘mio’ [type=kernel,card=1]
0 'mio MIDI 1 ’
Connecting To: 129:0
Connected From: 129:1
client 129: ‘Pure Data’ [type=user,pid=5618]
0 ‘Pure Data Midi-In 1’
Connected From: 20:0
1 ‘Pure Data Midi-Out 1’
Connecting To: 20:0

When experimenting with modifying the “amidiauto config”, “post-patch.sh” or “midi.txt” - what do I need to do in testing if changes have helped make this work? Stay at the currently open patch? Restart the patch? Restart Fates entirely? It is currently working fine with Qunexus connected directly, just not via the Mio usb midi interface.

Thank you!!

#145

if your using amidiauto then you can delete post-patch.sh, since you do not need it for connecting midi,
since amidiauto is doing this.

from the above it looks like your MIO is connected to puredata.

so if the qunexus works when connected directly to fates (so midi channel is ok),
then id say its likely your mio config, something like its not routing the midi thru.

when experimenting, usually just relaunching the patch from sidekick is enough.

1 Like
#146

I know it’s not the mio, as it’s plug-and-play and it was working perfectly fine before this most current update. Additionally, I know that it could still potentially work as my configuration has not changed otherwise. Here is another thing, maybe this is patch specific - for instance, the one that I’m using is Arp-III (AAARRRPPP), and it doesn’t actually show midi data going out on the indicator next to the O. I feel like that is somehow related. Yet it works (the led feedback) with QuNexus connected directly… shrugging. I mean, the indicator still shows no midi out, but the led feedback works anyway with QuNexus directly plugged in. Hmmmmm.

1 Like
#147

Ok, I think that I know what is going on… The reason that the midi out indicator does not respond to some patches is how the patches send the notes to midi…I think I could fix it on the next releases.
Thanks for the feedback @static !

2 Likes
#148

ok, how to make the pokemons!!?!!?!?!? hahaha

i installed mother/sidekick/orac seems to work. put the pokehex in the patches folder. it shows up but gets stuck loading. do i need something else?

1 Like
#149

New Update v0.3.1

  1. Adapted structure to new Sidekick v0.2
  2. New patches folder “/home/we/sidekick/patches/Organelle”
  3. Deleted “Update Mother”, future updates have to be made using the Sidekick “Check for Updates” function.

Unfortunately, this update has to be made by hand, so log in to Norns via terminal and paste the installation code:

sudo curl https://raw.githubusercontent.com/oxbown/NornsMother/master/install.sh | sh
5 Likes
#150

has anyone gotten any of those morphagene patches working/are they worth it?

#151

-I updated to Sidekick v0.2 without problems. I could see the new menu structure.
-Then I updated to Norms Mother v0.3.1 with your instructions. Everything OK.
-I lost the 3-4 pure data patches I had installed, so I tried to access the SD card to copy a few patches, but now I had only access to the Dust folder. (I sucessfully did a few days ago the modifications Oxbown explained in message 37), but maybe this was broken by the new installations. So I decided to do again the instructions from message 37, the rebooted and now my Fates only shows a black screen. I can do nothing. I tried pressing the 3 encoders and nothing. Nothing shows in the screen.
I can access Norms via ssh normally. What can I do so I can see again the menus?

#152

Norns updates overwrite Samba configuration, you have change the folder one more time…

#153

Yes. This is what I did. But now my Fates doesn’t start. I see nothing in the screen when I turn it on.

1 Like
#154

I thought, id install NornsMother to see I could see if there were any issues

so I did

but I get

The following packages have unmet dependencies:
 nornsmother : Depends: amidiauto (>= 1.01-2) but it is not installable

is this a manual step? or are you installing it?

2 Likes
#155

I d be so great to have a pre compiled norns/shield image with sidekick and mother on, this is getting so complex… but totaly amazing work.

Do the patches from Shreeswifty / fluidsynth work? Like count2five and jupiter etc?
Or is theres any reason they would not?

2 Likes
#156

Same issue here. Carefully followed all steps, but now I’m at a blank screen.

1 Like
#157

sidekick is installed with one line … (same with nornsmother)

building a 4GB+ image and hosting that , is not really viable :wink:

k, I know we some ‘teething issues’ but really Norns Mother is pretty new, so its not that surprising.
(even norns updates are not without issues and regressions)

2 Likes
#158

Could you log in to Norns via Terminal?

#159

Should I be able to just put patches in nested subdirectories inside Organelle directory? That’s what I did and they just get stuck on Launch… patch name.
CA Additive gets stuck beyond pressing three buttons to go back.

#160

for those with a blank screen,

ssh into it, and type the following:

journalctl -u sidekick

this will display the log file.

you can paste contents here
inside the discourse details tags
e.g

[details]
paste stuff
[/details]

also try deleting ~/sidekick/sidekick-state.json

this would stop it trying to load last patch…
(though that should not crash anything)

also you an reinstall sidekick, that should clean it up again
(but getting log file above would be useful for us to see whats going on)

#161

Yup but i just stumbled into norns actually so a bit over my head, yet these organelle patches are pretty much up my alley and resemble that i want my norns to be a very flexible library of things, totaly minimalized setup…