@fishcrystals the main alternative in this case would be to use polyblep I think.
I'm planning on making some objects to add polyblep residuals but I thought some vanilla polyblep logic already exists in some libraries, can't think of which right now. (I thought maybe https://github.com/MikeMorenoDSP/pd-mkmr/tree/master but can't see anything at 1st glance)

you could look at these papers for more info:
https://www.eurasip.org/Proceedings/Eusipco/Eusipco2015/papers/1570104119.pdf
https://dafx16.vutbr.cz/dafxpapers/18-DAFx-16_paper_33-PN.pdf

edit: actually cz synths had aliasing afaik..

@polle if you want to use linear interpolation you can make your own linear interpolator. I feel like there might be an external to do it but can't think of it.

@anvlkv for [out~] it is finding it, there's no issue (you're just seeing the loader trying binaries first in the logs). So maybe you want to suppress those logs somehow (I forget right now, there might be some verbose setting either while compiling or running..)

as for the other error, it probably has to do with how the search paths are set up (I'm not that familiar w/ libpd..). Anyways for an easy (but not best) fix I think it should work if you create the object like just [lb]

But to me it's odd for 'else' just to sit in your .app file directly.. I would at least put else in some subdirectory (like 'extra_obj'), and set your pd path to it instead, then in your pd patch create every object like [else/out~].

I thought the accepted place to put things like that was some subdirectory of Resources though..

true, don't try to use [expr] for everything.
The purpose of [expr] is to evaluate mainly mathematical expressions. yes it has an 'if' function but the main purpose is simple expressions.

so, put your loop/running sum outside of the [expr]s. you can use [until] to generate a loop

@brendanmac it's not really common practice afaik (usually just range -1 to 1), but it could make your product more usable/accessible.
If you want to do that I would at least use RMS, but perceptual loudness can get way more complex

@fishcrystals It worked with .PNG files for me

@atux midi note 60 will select the 61st image in the folder (usually sorted alphabetically)
so you either have to add more pictures or subtract 60 before [get $1(

edit: actually I wouldn't expect an out of range index to [list store] to trigger anything..

here's something to get you started.. you will need to get the 'else' library for the [else/pic] object
testpng.pd
if you put an "images" folder in the same folder as the patch and put .pngs in it the file names will be loaded into the [list store] when the patch opens. Then when you play midi notes they get stripped of their note-offs and used to look up the nth element in the list, which is used to load the image into [else/pic]
of course, you need to put 128 images in to cover the range of midi notes. otherwise you might want to use [clip] or some other math objects to get the notes into the range starting at 0.

if you want to see the values at any point in the data flow a good object to use is [print] which will show the input value in the console

Aside from the stuff in pd's included help, else also comes with a tutorial.

@jameslo well as soon as you change the [set( message to [block~] to have a 0.5 downsampling value then that's the case. (as you can see if you hook up a timer.. the downsampled 32-block patch with [bang~] will put out bangs at the same rate as the parent patch that has a 64 sample block.)
Actually in this situation another limitation is also due to [tabwrite~] not being able to do anything at fewer than 64-block size either afaict