Hey!
Some days ago I updated my Axoloti to the build from Github, which has been great in many ways. But today I tried opening an older larger patch, which used to work. But now I get this error every time I make the patch live. Dont now if it related to the update, but that is the ony ting I have changed. Anyway:
Error message:
/axoloti-master/build/xpatch.cpp:2487:6: error: 'net5' was not declared in this scope
I get a few of them, for net5, net6, net7, net10 and net30.
Any ideas?
hmm, well the 'net' numbers are the wire connections, and I'm not sure why they would disappear.
if you are using object search paths (which of course your not 
) then it could you have changed your path since you last used it?
or object has changed such that an inlet/outlet has been removed.
don't think this is likely on factory objects, but perhaps if you have changed your sub patches?
would need to see the patch to be sure whats going on .
what you could try is saving the patch (as new patch so you don't loose original), its possible when you do this it will be missing some wires. (actually already missing in the UI)
Thanks man 
WIll try saving out later. If this doesnt work I will send you a copy of the patch... It is the same patch as you have seen before
All subpatches are saved in same folder as main patch ans is called up with ./xxxx.axs.
I got a new used Macbook today and I have been able to open the patch on that. Nice
Seems like all the trouble I have had with Axoloti, like noise from powersupply on Axoloti output, Cpu spikes, etc is sorted out. At least havent encountered any of them yet
Recently received and built the Music Thing and tried compiling the three examples on Github. The first and third examples built loaded and worked okay, but the second failed to build due to the following errors (extracted from the page of text generated at compile time:
Object name delay/read_slow_S not found
Error: object “digital_8” attribute “mode”, value “hi-z” unmatched
‘net54’ was not declared in this scope.
Any idea why this example didn’t compile but the others do?
Thanks.
Looks like an object that's not available, it's not a factory object , so perhaps it was also on github with this patch?