• jameslo

    @ddw_music I think I built something similar to what you're describing for @cfry, see https://forum.pdpatchrepo.info/topic/13518/readsf-varispeed. The second version with the shorter buffer wraps the playback point correctly. The idea is to use [switch~]'s bang feature to run [readsf~] faster than realtime and to read your sound file into a buffer that's a multiple of the block size so that you don't have the control rate synchronization problem you alluded to. But yes, it's tricky to get right.

    posted in technical issues read more
  • jameslo

    @mkdewolf I'm wondering if you're aware of Pd's help system? For instance, you could create a [text] object, right click it, and choose help to get all the info you need about [text]. There are also tutorials on how to do things in Pd. Click Help->Browser...->PureData->3.audio.examples/ for ones related to audio. In particular, A02.amplitude.pd describes how to control volume. If you fill us in more on how you are generating notes we might be able to suggest tutorials on how to control their duration.

    posted in patch~ read more
  • jameslo

    @yannseznec I think you are describing ipoke~. @whale-av can give you the whole run down, but my understanding is that it was a 32 bit external that was never compiled for 64 bit Pd, so it still runs but you have to run it under an old version of Pd. I wrote a portable but clunky one in Pd itself just to pass the time (and I think I didn't quite finish it)--search this forum for vipoke if you're interested--and I'd be happy to finish it if it was useful to you. Not sure if what I've described is still the current state of affairs though, would be worth digging further.

    posted in technical issues read more
  • jameslo

    You will also notice that if N is the power-of-2 table size, the (N/2th) coefficient of sinesum is mostly noise, whereas the ((N/2)+1)th coefficient of cosinesum is Nyquist.

    posted in technical issues read more
  • jameslo

    @whale-av OMG I was so fixated on the part I quoted that I didn't see that you had already offered that theory. COMPLETE BLINDNESS

    posted in technical issues read more
  • jameslo

    Oh wait, I can reproduce that behavior if I click a second time before the first click has completed. Maybe that's what's wrong? To address the issue I think you need to add a zero to the beginning of that vline~ message, i.e. [0, 1 500 0, 0 500 500(. That makes sure the first ramp always starts from 0.

    posted in technical issues read more
  • jameslo

    @whale-av said:

    But I will defer to somebody that actually knows.

    Not implying that that someone is me, but I'm wondering if the OP might get the behavior they expect if they used [line~] instead? I think [vline~] has fancy features I don't know about and have never needed (but don't quote me).

    posted in technical issues read more
  • jameslo

    @whale-av That totally worked, thanks. I must be going blind because I didn't see that flag in the help until you sent me looking for it.

    posted in technical issues read more
  • jameslo

    @ddw_music Ah, OK, I see that @oid is probably referring to the right outlet of [text get]. Things are still a little strange when newlines are treated as whitespace though.
    Screenshot 2024-02-14 102145.png

    posted in technical issues read more
  • jameslo

    @oid said:

    [text] can also deal with csv files that have comma separated fields, right outlet tells you if the line ends with a comma or a semicolon, just takes some simple logic, the helpfile for [text] should provide the answers.

    Can you write a little more on how to make this work? For instance, when I use this csv file test.csv
    Screenshot 2024-02-14 092926.png

    [text] loads the commas and treats the new lines as whitespace
    Screenshot 2024-02-14 092832.png
    plus I don't get any notification on the right outlet. What am I missing?

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!