Hello,
I've seen many examples using one or the other
I guess it's preferable to use delwrite/delread for delay lines, but I wanted to know why
ps : also if someone knows how to get cpuload in puredata ?
thanks
delread/delwrite vs tabread/tabwrite
Hello,
I've seen many examples using one or the other
I guess it's preferable to use delwrite/delread for delay lines, but I wanted to know why
ps : also if someone knows how to get cpuload in puredata ?
thanks
@phil123456 Cpu is Easy in extended...... [dsp] contains extensions with access to kernel data.
In Vanilla I think you will need the iemlib library.
[delwrite] requires no table, but if the table is hidden then tabwrite is fast.
But delread gives very easy access to a tap into the ram at a specific delay point, whereas with [delread] the table has to be written first. There is a max/msp object that was imported to Pd, that made a "moving" circular table..... [ipoke~]........ http://puredata.info/Members/ipoke/ipoke_v.3_test1.zip/view
That you might find useful.....!
David.
@phil123456 in vanilla you can use the menu Media > Load meter to see the cpu load.
following @whale-av suggestion, in the last post here there is a delay patch using ipoke~ https://forum.pdpatchrepo.info/topic/10972/distorted-sound-trying-to-simulate-a-bucket-brigade-delay/3
@weightless Ha! I didn't realize [cputime] had made it into vanilla.
I really am still a brown paper envelope noob!
David.
ok, so they both do the same but delread offers some more flexibility
thx
I'll check these cputime and ipoke
thanks guys
@weightless easiest/best answeer to me
Oops! Looks like something went wrong!