i missed this somehow. It is fixed now in the github repo and will be included in the next deken upload.

@jyg said:

just out of curiosity : why did you move to "deprecated" some objects (for example : pp.rev~) ?

because I am not planning to develop them any further (i don't use them anymore) and there are better alternatives, such as pp.phiverb~. I'm keeping them for anyone who wants to use them, Just copy from the deprecated folder.

There is a lot of stuff I'd like to change in this library, particularly the names of some of the objects. "pp.phiverb~" "pp.butterkreuz3~" etc., just horrible! plain stupid. I don't know who came up with this. So whenever i make a fundamental change in the future, i will keep a copy of the old stuff in the deprecated folder. However, the worst is the name of the library itself; "Audiolab" ... I hate it!
Too late to change that now i suppose

use [set 64 1 $1(
no need to switch dsp off

@jyg said:

Did you re-upload the latest audiolab 0.71.1 ?

yes, i re-uploaded, thanks to this comment from IOhannes in the list:

what i can say is, that the "audiolab" package includes both a "LICENSE"
file and a "License/" directory.
this is not a problem on case-sensitive filesystems (like ext2/3/4 on
linux), but it cannot work on case-insensitive filesystems (like FAT32,
NTFS or HFS+).

I was not aware of this and it was on my end to fix it, so thank you for bringing it up in the list!

Edit: the version number is the same, 0.71.1 because nothing has changed in the files except that LICENCE is now called LICENSE.txt.
If anyone else had issues with the install from deken, please try again.

Thanks again for helping to clear this up!

@jyg installing from plugdata works fine for me.

@jyg hm so i just checked if i missed something and if it is actually common practice to share files on deken with group and global write permissions. But that doesn't seem to be the case, here is a part of zipinfo output of else-v1.0-0_rc14 for example:

Is installing else causing trouble for you?
Could it be that you are having this problems because you are logged in as admin, not as user or you are trying to unpack these files to a protected folder or something like this?

If it helps i can re-upload the files with extra write permissions.

@jyg there were no issues with packaging and uploading it to the deken repos, and unfortunately that's all i can do from my end. If you can narrow down the problem, you might consider submitting a bug report on the deken github.

@jyg i just uploaded a new version 0.71.1 to the deken repo. Can you test if this works for you?

@jyg someone reported a similar issue with the deken installation on a Windows OS on github. I can not reproduce this on Linux and i don't know what could be causing it, so my suspicion was that it is somehow related to Windows security permissions. Are you using Windows? Does this happen with other libraries as well? Unfortunately, there is not much i can do about it, but i'll test as soon as i have access to a Windows machine.
For now, if you want to stay up to date you can download from github and set the path manually in pd settings.

Edit: just saw that you created another issue about this on github. I'll close it because it is not related to the development of this library, but we can continue the conversation here.

@jamcultur thanks! You can save any of these objects with a message [save 1( to the rightmost inlet. Then use [recall 1( to retrieve your parameter settings. You can save up to 21 presets this way. This is also documented in the help files and in Examples/01-basics.pd