#141

wow that’s great!! thank you! gonna check this out with my pi 2 lying around…

#142

you might not be excited by the performance you get with a 2, but i assume you will know that

1 Like
#143

Yep I thought so…If the weather is going to be as bad as it announced this weekend I’ll give it a try.

Also I was thinking about getting a pi3 for other projects…so maybe its time now…:nerd_face::grimacing:

#144

A post was merged into an existing topic: Norns: Development

#145

ok, not really rPI related … but I think @jasonw22 was asking about using a virtualbox?!

so the answer is yes, it can be made to work… Ive got it working under vmware :slight_smile:

I actually did all the Push2 dev for matron on Vmware Fusion (mac) hosting Ubuntu 18.04 (64bit) , but I didnt bother trying the audio till this evening (for fun, over a glass of wine)

‘as expected’ jack and the ‘virtual audio driver’ did not work… (Ive logged a support request)

so I went a different route, VMware has excellent usb support,
so I plugged in a portable USB audio interface (Zoom H5 in AI mode) , then gave it to vmware to host, told jack to use this - and viola, the lovely dulcet tones of Norms, using my Push 2 to control it all.
(no xruns or anything, so thats a bonus!)

why? - why not?

no, actually, its useful for development purposes, Ive got better tools on desktop Ubuntu, so its easier for me to try things there, get them working … git push them, then bring them down to the rPI for testing.

so if you want to try norns out on the desktop give it a whirl, as ive mentioned previously in this thread the norns documentation is really good.

1 Like
#146

woohoo! I’m going to try to make time to give it a whirl this weekend.

1 Like
#147

key thing to note… if your building from ‘scratch’, the distros are still on supercollider 3.7 or 3.8,
and you need supercollider 3.9.3, but thats a really easy build (supercollider website gives steps)
apart from that, norns docs covers all thats needed, and theres a few extra hints in this thread (re go, and glide)

#148

Äh maybe a stupid question but why should I not use the kernel from the momome git?

Edit: it‘s for the special soundcard used in norns,right?

#149

A few reasons, I don’t use it:

  • I don’t know what’s in it, or if it’s patched
  • it’s and older kernel 4.9 vs 4.14
  • the version available (003) is not the shipped version 004?

All that said I suspect it would work, (as does the stock kernel, just not with as good performance)

Frankly, once you’ve built a kernel once, you’ll realize it’s not a ‘big’ thing, and being able to tweak it is useful at times.

Brian has said he will post the final kernel image, when he does that I will cross-check it with mine.

1 Like
#150

I’m building my first linux kernel right now! Exciting

4 Likes
#151

+1000 xp to @reijo the elf.

1 Like
#152

haha thx.

while downloading files etc… I checked my backlog and I have a OLED lying around. Unfortunate its a SPI with 7Pins. Would it be difficult to get this working? Or should I get a I2C OLED?

Edit: argh… I followed your instructions from your .txt but now the pi is not coming up after reboot. I have no HDMI here atm so I did everything via ssh…guess I have to start from the beginning haha…although I have no idea what went wrong…
:disappointed_relieved:

#153

Not really been keeping up with this thread, or know if it’s been posted already, but I saw this pop up on my RSS feed today and thought it might be relevant:

01%20am
http://zynthian.org

Open source, built off a fullsized Pi, and what looks to be off-the-shelf I/O stuff.

As an aside, I’m always blown away when I see how other people treat design, after being spoiled by so many years of beautiful monome instruments. (i.e., it’s ugly as shit!)

3 Likes
#154

had you run setup.sh?
I suspect you lost wifi by allowing the etc/network/interfaces get overwritten… at least that’s what happened to me - but fortunately, I have a monitor/keyboard to hand :wink:

@Rodrigo , yeah Zynthian has been around quite a while. (a couple of years?)

yeah physical design is a bit meh, but that’s because its uses off the shelf components… and the standard rPI+hifi berry is quite ‘tall’
what I don’t like about the hifiberry used, is has no input, and rca output , rather than TRS - there has been talk of them switching to PiSound which is much better.

but I wouldn’t be too hard on them, built is 350 euro , or the full kit (which is ‘snap together’ , no soldering) is 250 euros - so pretty cheap, and its a 3.5" touch screen
(I don’t think they make much money on it really)

if they’d switch to pisound id recommend it.

1 Like
#155

yep I did run setup.sh…but even with a ethernet connection to my router the pi doesn’t show up…gonna check if also ethernet gets overwritten…thank you

#156

Nope thats not the problem. Did a fresh install without the interface overwriting line. Same problem… pi doesn’t come up; or at least there is a problem with the network…
I used on both attempts the kernel which comes with rasbian…maybe this is the problem?! Guess not…

Damn I need a HDMI cable…

(If only cloning the image to a sd card wouldn’t take some much time…)

#157

so you didn’t replace the kernel? if so its not the kernel… the std kernel works, just its not preemptive.

unfortunately setup.sh replaces network interfaces file, so it will also take ethernet out as well :frowning:

do you have an sdcard reader and a Linux box (virtual or real) - if so you can mount the sdcard on that to ‘fix’ the issue. (just look in /etc/network/interfaces)

#158

no I didn´t replace the kernel…(I skipped this for now…cause it took so much time…that´s something I thought could be done overnight…)

and yes I can access the the sd card. but the interfaces file was not being overwritten. I deleted this line from setup.sh

#159

odd… so at what point did you lose network access?

really the only chance i can see of losing access is,

  • not installing the kernel correctly.
  • setup.sh (as this is changing things)

the later steps, all do nothing that would harm the network access.

(i wonder if you forgot to remove some of the i2cset, and if this might crash the kernel, I wouldn’t have thought so… but as i removed them i don’t know :wink: )

hmm, probably best bet is to get a hdmi cable and keyboard, then you can see if its starting up… and its just the network down for some reason.

as i said, my only hiccup, was i lost the network, due to the interfaces file being overwritten - i then just got a keyboard/monitor, put it back to what it should be, and everything from that point worked as expected.

lets look on the bright side, hopefully you can figure out what went wrong, and that’s an extra ‘note’ for the instructions.

1 Like
#160

I mean I really don’t know if it´s only a network problem or if the pi doesn’t boot correctly.
This happens when I do the reboot after setup.sh and
cd norns
./waf configure
./waf
cd sc
./install.sh

and yes I did not remove i2cset…hahaha …will do that now! lets see what happens…

what a nice “trial and error”-saturday

jep…getting a HDMI cable tomorrow…in the meantime I give it a last try…:nerd_face:

1 Like