Patch no longer compiles on 1.0.11


#1

hi!

unfortunately, i got problem with one of my patches that i used for several months already. everything was ok and patching was always without any issues. yesterday i re-installed axoloti patcher and axoloti runtime and did java update (mac os 10.11.6). i still can patch 'tybett' or other patches, for example. but when i try to patch (just press "live" button) my old patch it writes this (below). i'm a bit confused, because yesterday i did some corrections to this patch and everything was ok before re-installation. well, it was bad idea.. anyway what can i do now to solve this?

! /Users/musicworm/Documents/axoloti/build/xpatch.h.gch
/Users/musicworm/Documents/axoloti/build/xpatch.cpp: In member function 'void rootc::instanceobj__2::instancewindow::dsp(const int32_t*, int32_t (&)[16], int)':
/Users/musicworm/Documents/axoloti/build/xpatch.cpp:430:1: error: expected ';' before '}' token
}
^
/Users/musicworm/Documents/axoloti/build/xpatch.cpp: In member function 'void rootc::instanceobj__1::instancewindow::dsp(const int32_t*, int32_t (&)[16], int)':
/Users/musicworm/Documents/axoloti/build/xpatch.cpp:1404:1: error: expected ';' before '}' token
}
^
make: *** [/Users/musicworm/Documents/axoloti/build/xpatch.bin] Error 1
shell task failed, exit value: 2
Compiling patch failed ( /Users/musicworm/Documents/Records/axoloti/techno1.axp )


What's happening?!?!
#2

mod note: Ive moved to new post as not relevant to the original topic.

it looks like an issue with the window object your using but that's only based on the instance name, we would need to upload the patch to find the real cause.

please upload your patch here if you would like me to take a look
(make sure it does not use subpatches, rather embedded patches if relevant)


#3

thanks! i was not sure where i have to put this problem.

no problem, thanks for help.
here's part of this patch, still doesn't work, the same problem.
https://we.tl/WQsI880sQj


#4

works fine here...

go to your documents directory, axoloti, then delete the build directory in there.
(so ~/Documents/axoloti/build)


#5

i've tried this action before asking (found somewhere here that it could be ok) and did it again. anyway no luck, still the same thing.


#6

can you upload this file (after you have tried to go live and it failed)

what version were you using of axoloti before?
if its very old, can you confirm your are running the latest axoloti-runtime

another thing.
can you go to preferences, and do 'reset libraries'
and ensure they are sync'd correctly

(the code your are generating does not match the code im generating, so it 'feels' like the objects you are including are not correct... in particular the factory objects)


#7

oh, and if you have a 'controller script' enabled, please disable it, and re-test


#8

file: https://we.tl/TiPnjYyOsj

it was 1.0.11, but it could be runtime from 1.0.10 (i tried to make the same situation today, nothing).
i can confirm that patcher and runtime are 1.0.11 now.

i thought it's something with directories, but i re-installed again everything from the beginning.
i did 'reset libraries' and sync, problem still not solved.
'controller script' not enabled.
i hope i do every step correctly..


#9

just found that patch works without 'sptnk/osc/vosim FM' object..


#10

ah, thats the issue, Ive just done a sync on the library, and now get the error...
appears @Sputnki has introduced a bug in that object in the community library.


#11

yeah @Sputnki in your patch/object of window, you have missed a semi colon line 20 s-rate code.

@musicworm, you will need to wait for him to fix and release it.


#12

@thetechnobear, thanks a lot for help! sure, i'll wait for the fix soon.


#13

@musicworm @thetechnobear It seems i have completely destroyed that object in an attempt to make a new version of it. Luckily i had a backup copy lying around. Try doing a sync, it should be ok now

Thank you for the report!


#14

looking good here :slight_smile: :thumbsup:


#15

yeah, everything is ok! thanks, i'm happy now :slight_smile:
should i somehow save this object just in case?


#16

You could click on the arrow and convert it to patch/patcher, this way you're sure i won't cause any more trouble with my messings xD


#17

ok, thanks, i will do it!