Untracked objects , what does it mean?


#1

since a few days, I get this message after startup then Sync:

Axoloti version : 1.0.12-0-g80370d2 build time : 02/02/2017 20:39:14 CET
Link to firmware CRC E95BAC96
Status: factory (1.0.12,anon) : OK ( 1.0.12,clean )
Status : home : OK
Status: community (1.0.12,anon) : OK ( 1.0.12,dirty )
Changes for: community (1.0.12,anon)
untracked: objects/phi/lfo/slowphasor.axo
untracked: objects/phi/prob/%bang inc.axo
untracked: patches/phi/21.axp
untracked: objects/phi/lfo/slowsquare.axo
untracked: objects/phi/sel/sel dial 16 h p.axo
untracked: objects/phi/prob/%bang in.axo
untracked: patches/phi/Launchcontrolsequencer2.axp
untracked: patches/phi/binauralbeats.axp
untracked: patches/phi/binauralbeatsextraction.axp
untracked: patches/phi/ProbquencerSeed.axp
untracked: patches/phi/shuphil1.axp
USB device found
connected
Authentic Axoloti Core
search path : C:\Users\Philoop\Documents\axoloti\axoloti-factory\objects
Firmware version: 1.0.0.1, crc=0xE95BAC96, entrypoint=0x20011000
search path : C:\Users\Philoop\Documents\axoloti\objects
search path : C:\Users\Philoop\Documents\axoloti\axoloti-contrib\objects
Sync Successful : factory (1.0.12,anon)
Modifications detected : community (1.0.12,anon)
unauthorised changes, resetting : community (1.0.12,anon)
Sync Successful : community (1.0.12,anon)
finished loading objects
search path : C:\Users\Philoop\Documents\axoloti\axoloti-factory\objects
search path : C:\Users\Philoop\Documents\axoloti\objects
search path : C:\Users\Philoop\Documents\axoloti\axoloti-contrib\objects
finished loading objects
Using controller object: controllers/cycle buttons

How can i solve it?


#2

means objects are not in library.

unauthorised changes, resetting : community (1.0.12,anon)
this means you are not in your correct prefix


#3

so my file(s) are in someone elses folder? hmm ..how to find out where?


#4

I was not logged in to Github. !!! lol
But how did this happen ? why does the patcher Reset my Github Account ?


#5

it doesnt... unless you
a) delete the prefs file
b) do a reset libraries


#6

wich i didnt do .....


#7

no idea then, never happened here without me explicitly doing this.