#1789

norns ships with a straight USB cable made my molex, rated for high current. “normal” thick USB cables should be fine. don’t use a super thin cable.

E1 in menu mode has lowered sensitivity (in software) to prevent skipping pages.

don’t use the Librarian, it is likely to cause problems. check out the docs for best methods. there’s a maiden-based-library-manager forthcoming.

4 Likes
#1790

As a follow-up to my post from the other day, I jumped in head first this afternoon and had a blast with Cranes and MLR right out of the gate. What an amazing machine Norns is. Thanks for the advice everyone :slightly_smiling_face:

3 Likes
#1791

thanks for this, orca looks really interesting… maybe not for use while drumming, but this could be a neat way to try generating things. i’ll take a look at it and timber.

1 Like
#1792

For sure!!its actually an interesting script. It is clearly built for programmatic randomness, but the ability to program each key on a grid actually makes it an interesting programming tool for grid instruments. One could remove all randomness all together and just have a very specific grid/softcut sample instrument.

It would work much like the Timber Player, but it’s got a bit more flexibility in build out, while losing some visual specificity. All VERY fun!

#1793

Ok so I’m not sure what’s going on here. I just installed a cm3+ into Norns. Flashed the image and all was good. I decided to update to the most recent version of Norns (since I had flashed to the previous img file that’s available on the norns help page) and also ssh’d into Norns to copy my Audio folder and Script folder from the backup I did before doing the install. However after I did this I am getting an error from Norns “error: SUPERCOLLIDER FAIL”

I Have no idea why this is happening. I can not load any scripts now. Norns just hangs on loading… I have tried resetting from the system page and also tried a hard reset. Any insights would be greatly appreciated so I can continue to use Norns.

#1794

This sounds like a duplicate engine. Can you access maiden? If so click the sc tab, it’s over the REPL. Try loading a script, and you should see an error message naming the problem engine.

#1795

actually i only just now realized they had orca running on norns… woah. i was already on board when i thought i’d have to run it on the laptop.

do you know if you can save your live coded material? could be good for me to enter all the usb keyboard stuff away from the drums and then just play/manipulate things on the fly with the grid?

#1796

Yeah! You can save your patches. There have been a few updates over the last few months that have caused some patch breaks, so maybe find a way to back them up visually or in print so you can rebuild over time if needed. But its fantastic. The extra benefits of orca on norns are: softcut parameters, it triggers both the timber engine (your sampler engine) but also midi, and you can easily set specific grid buttons to fire bangs, making it a sweet way to basically program sample and midi fires AND do softcut params all from a grid and editable from a nearby keyboard. I’d be happy to share any answers I got (I’m still semi newish at it compared to some) and the norns orca thread’s a good place to go.

1 Like
#1797

Orca doesn’t recognize a varibtight/wooden 128 grid on my Norns. You mention they are useful together?

#1798

Are you sure you input the positions correctly and the Norns recognizes the grid? I have a 2010 grayscale that works just fine… what you do is use the

symbol (the positions before it are XY coordinates of the button you wish to use). When you press that button, the > will output a bang below it. That bang then needs to affect something else.

If you wish to see the LED of that button, you need a separate command:

<

This, when hit with a bang (which you can have as a constant bang from some values) will just light the LED.

Beyond that, I would head over to the thread

1 Like
#1799

I opened up maiden but it says “not connected to sc”

I wonder why

#1800

does norns have an error when you boot up?

check out the error section here: https://monome.org/docs/norns/help

generally i wouldn’t suggest just copying a full code folder from an old version as you’re likely to get duplicate engines and all sorts of out-of-date scripts.

we’re nearly done with a maiden-driven management system for scripts so this will get easier soon.

2 Likes
#1801

Is this available for testing or contributions? I don’t see any recent dev on the maiden GitHub.

#1802

Before I upgraded to cm3+ I was on the most current revision so maybe it was because I copied the dust folder before updating my cm3+ to the most recent Norns os? I can’t remember if that is what I had done but it’s possible. Im going to try to flash again

#1803

Ok so I re-flashed Norns and unfortunately now when I boot it up it still gives me the supercollider fail error. I did not copy any of my old dust files over this time. I ran etcher to flash the img and then once it was complete and verified I put norns back into run mode and turned it on.

**edit I have now tried to reflash the cm3+ probably 4-5 times now and keep getting the same result. I tried looking for a SC error in maiden but Norns won’t connect to SC. Im really at a loss here. I’d very much like to use the cm3+ for the extra storage. One thing I’d like to point out that I’m not sure is ok or not is that when I run " sudo ./rpiboot " terminal just hangs at Waiting for BCM2835/6/7 however it does mount so I am able to flash with etcher. Im not sure if this could be a reason im having issues or not. Hope I can get this figured out soon so I can use norns again.

I managed to get past waiting for BCM2835/6/7 but it still had the supercollider fail issue once it was done

#1804

At this point it’s helpful to check maiden for output in the SC tab

Type ;restart and enter in the REPL and report back.

#1806

The current work in progress for project/package management in maiden was merged into master back in July. It currently lacks a degree of UI feedback which is needed (in my opinion) but the basics work.

If folks are interested in helping to push it across the finish line I’ll start another topic for dev and testing.

1 Like
#1807

try rebooting again after the fresh image first boot. i’ve seen an issue where the first boot after flash throws an error.

#1808

(huge guess) wonder if this has something to do with network settings. If the new CM3+ hardware has a new MAC address maybe that’s wrenching network manager somehow?

(I run into a SC: FAIL on my RasPi build process when network manager is not installed yet and SC can’t properly get an address to connect)

#1809

I finally got past it after loading the old cm3 to make sure it wasn’t hardware related. When I put the cm3+ back in it booted without error. Then I expanded the storage and it’s working fine now. Thanks for your help.