#1542

Ive done something wrong and lost SC somewhere (error: SUPERCOLLIDER FAIL) - am I able to “Update” (im on 28/03/08) or best to do a fresh install?
Ive read through all the docs but unsure which way to go

#1543

Interested to hear about this, too, as I have an iConnectivity iConnect4+. I really want to be able to sync my Fates to my MIDI gear.

Having said that, I could just directly connect it to one of the iConnect host ports…

#1544

Midi is only going to work with norns over usb.

1 Like
#1545

Can’t be done. Usb only device recognition is hardcoded in software. I’m using a beaglebone I had laying around to simulate a usb midi device and then map the ports to rtp midi and bluetooth . Bela os already has support for simulating a midi usb device and you don’t actually need a cape to run it. Although cape is so much fun too :slight_smile:

1 Like
#1546

My hotspot password is rejected by Fates no matter what I try.

I’ve tried using a fresh install of 200218 (via disk image provided on Github). I’ve also tried using 200328, and no luck with that either. I’ve tried changing the password in the wifi.lua file. Still no luck. Works fine with my original Norns.

#1547

answering myself - its OK now -without intervention? I turned it off in frustration and left it and woke up and its OK - no supercollider fail and everything looks OK
Im thinking I may have had maiden running in the backgound on a forgotten tab in safari - could that be the cause?

#1548

no - maiden is really “running” anything per se. It’s just a web client to send/receive commands. It will lose connection on it’s own and you’re need to reload to reconnect.

1 Like
#1549

If you installed a script that has a new engine, or an updated script made changes to an engine, you can get sc failures if you don’t sleep cycle

1 Like
#1550

I did that a number of times (the hard reset or reset) - I followed all the guides. Anyways it seems OK now - weird though

I had been updating scripts in maiden and deleting some tapes but then it worked on boot - I shut it down asap im sharing that power source with my OPZ which I needed so I powered down Norns and then it came up with the supercollider fail when I powered back up…

#1551

hi there - i seem to have “bricked” my system by trying to update within the fates system menu. I am seeing a lot of links to fix it and I want to make sure I’m using the most up-to-date fixes.

I must admit I am not experienced in coding at all, so I may struggle to understand what exactly to do here. Thanks in advance to anyone who can help me :slight_smile:

#1552

Nevermind, I think I’ve found the disc img to use.

1 Like
#1553

can anyone tell me what’s going on here? i first noticed that Cheat Codes didn’t seem to be recording any audio to Softcut and now it seems MLR isn’t either, so i assumed an engine error/failure. but all i see here is pset errors as far as i can decipher:

    # script load: /home/we/dust/code/custom64 /mlr64.lua
not playing
not playing
not playing
### cleanup failed with error: /home/we/dust/code/custom64 /mlr64.lua:998: attempt to index a nil value (field '?')
# script clear
metro_stop(): pthread_cancel() failed; error: 
specified thread does not exist
### initializing data folder
mkdir: cannot create directory ‘/mlr64/’
: Permission denied
including /home/we/dust/code/midigrid/lib/mg_128.lua
including /home/we/dust/code/midigrid/config/launchpadpro_config.lua
`midigrid.device` is:
id	8
name	Launchpad Pro 2
event	function: 0x111c220
dev	userdata: 0x103c998
`midigrid.device` is:
id	8
name	Launchpad Pro 2
event	function: 0x111c220
dev	userdata: 0x103c998
midigrid "launchpad pro 2" has 8 rows, 16 cols
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
bpm > 30.0
bpm > 60.0
pset >> write: /home/we/dust/data/system.pset
# script run
>> reading PMAP /home/we/dust/data/custom64 /mlr64/mlr64.pmap
m.read: /home/we/dust/data/custom64 /mlr64/mlr64.pmap not read.
Engine.register_commands; count: 0
___ engine commands ___
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
# script init
q > 0.5
off > 0.0
q > 0.5
off > 0.0
q > 0.5
off > 0.0
q > 0.5
off > 0.0
q > 0.5
off > 0.0
q > 0.5
off > 0.0
q > 0.16304347826087
ERROR (i2c/hp) failed to write
q > 0.16304347826087
q > 0.16304347826087
FILESELECT 1
FILESELECT 2
FILESELECT 3
FILESELECT 4
FILESELECT 5
FILESELECT 6
#1554

to clarify: you can play back softcut buffers, but not record them?

first: have you ensured that input levels are turned up on the mix page?

can you hear the echos in awake? (softcut is working)
can you use simpler, grid-less processing scripts like otis or pools? (ADC is working)

also: you can’t have a space in the path. this is probably causing presets to fail and all kinds of mayhem.

3 Likes
#1555

nothing is playing, so i dont know if they would playback or not. i cant record anything.

levels are up

from the delay in awake? yeah i hear them

Pools works too

I dont know what the problem is, i was just guessing it was softcut because it doesnt seem to be recording audio. or maybe just not playing it back

ok it’s working now. seemed to be a parameter issue. although the levels in the loaded/saved pset were all good. not sure. but the error did indicate it involved psets

#1556

did you see my note about your having a space in the path to the script? that is causing some of the errors in your log.

mkdir: cannot create directory ‘/mlr64/’ , etc

2 Likes
#1557

I did see that earlier but forgot. What path is this? I didn’t create that directory manually. If there is a space between the custom64 folder and the mlr64 script in the parameter set save directory, I don’t know how that would have happened or how to fix it. I think maybe deleting the pset would have fixed it. Or I hope so at least

i’m also not seeing it here:

Untitled
Untitled1030×658 26.1 KB

2
21030×658 28.9 KB

How would i fix that though? you think it’s necessary?

Side note: Anyone else use the Fates as a level meter? I have mine on constantly whether or not I use it because it’s in my chain between my synths/pedals and my octatrack but I find it pretty handy to just keep the levels page open if I’m not using it, like kind of a mixer

image
image2048×1536 589 KB

1 Like
#1558

ah! since your dust/data folder is named custom64-master and your dust/code folder is named custom64 (with maybe a space after it), i’d guess that a space got introduced when you edited the name of the folder.

^ this shows a space after custom64. in maiden, try highlighting the custom64 folder and hit the pencil icon to edit the name – please confirm there’s no space?

1 Like
#1560

hello everybody, nice to meet you all!
it’s my first post here, I hope I’m not mistaking anything :slight_smile:

I was wondering if there’s any way to make what I think could be a good use of the fates’ 4th knob,
otherwise used just for orac purposes: I’d love to have a master volume knob (master out + phones) directly accessible without going into the menu. do you think this could be possible and easy to achieve? is there a way to program and link the master volume parameter to respond to this knob?

I’m a total noob in diy and programming stuff, so apologies if it’s a stupid question
and thank you very much in advance!

#1561

Nope. No easy way.

Your best bet would be using a separate midi controller and map a midi cc to system volume - which should be possible with the new params update. (I’ll test this and report back)

UPDATE - mapping LEVELS for in/out/etc works fantastic from a MIDI controller. Use the MAP section of the PARAMETERS page

3 Likes
#1562

tha’s bummer :frowning:
anyway any workaround could be useful, thanks for checking out!