[unknown] aha! I had a feeling it was something naive like that. I'm still having some trouble, and I'm sure it's just that I'm not comprehending something simple at this point.
I would like to have the externals stored in such a way that I can enter [cyclone/scale 0 120 0 65535], which helps me to keep track of my use of externals, and will make development faster. I know I had this set up before, but I changed the way externals were saved. I would like to have a folder of cyclone externals called cyclone. I've tried using the "create new folder" button, which creates " - cyclone" in Directories. I then highlighted it and tried uploading a new file to place a cyclone external within that folder, but the file is uploaded to resources.
The other way I've tried is to upload the zip "cyclone-0.3rc1.zip" into pd-externals. Then I run this script:
mkdir -p /root/Bela/projects/pd-externals
cd /root/Bela/projects/pd-externals && unzip /root/Bela/projects/pd-externals/cyclone-0.3rc1.zip && rm /root/Bela/projects/pd-externals/cyclone-0.3rc1.zip
This then creates a series of messages in the console saying it's expanding all of the objects. After it's finished with this, the cyclone zip file disappears. There is no cyclone folder in the pd-externals project when this is finished.
I really just want to do things in the most organized and "correct" way🙂 Is the answer that I should just do what I did (running the mkdir script), understanding that the externals are now in some hidden place in the bela board, and then just stop using the cyclone/ prefix with the externals? Or should I do this in some other way.
My apologies for being a bit dense with this. I have been having great success with Salt, in spite of these hitches. I've made vanilla versions of my favorite cyclone and else externals, and have a pretty wonderful contrapuntal logic encorporating the manta controller and mantamate module and making lots of polyphonic controller of the oscillators in my case. I'm excited to figure out this externals problem🙂