• jameslo

    @nicnut OK, but if you punch in and out in the middle of the original loop, you still want the original loop to play out in full with your new overdub in the middle and at the speed it was playing at when you punched out, right?

    posted in technical issues read more
  • jameslo

    @nicnut I haven't been following this discussion very carefully but I could have sworn that @whale-av suggested ipoke~ and you determined it wasn't necessary. From your last problem description, it sounds like ipoke~ is exactly what you need. If you are looping a fixed-length buffer at some speed other than -1 or 1, then the time to play each loop iteration will be different than the time it took to record it. But if that's the case then you are no longer recording at the normal sample rate. ipoke~ let's you record into a buffer at a variable rate by either interpolating the samples when the record speed is fast, or averaging the samples when the record speed is slow. It's like tabwrite4~ except with linear interpolation. Does this sound like what you need?

    Edit: hmm, ipoke~ is a general solution but I think there might be a way to do this with 2 buffers, Suppose you are overdubbing a previous loop recording that you are playing at 1/2 speed. What should happen if you punch in sometime in the middle and punch out before the end? What should happen if you punch in towards the end and the playback loop wraps around to the beginning?

    posted in technical issues read more
  • jameslo

    @gentleclockdivider [osc~] outputs -1 .. 1, then you add 1 to shift it to 0 .. 2, then you multiply by 38 to get 0 .. 76. But your table only has 50 points of data, so I assume [tabread4~ is just using the highest value in the table for indexes 50 .. 76. So what you're graphing at the top looks correct to me, except maybe for that little discontinuity labeled "right" which I don't understand, not knowing plugdata. Try reducing that number in the red box to 25 or less.

    posted in technical issues read more
  • jameslo

    @lyric Another way would be to use [array random] with a suitably initialized 3 element array.

    posted in patch~ read more
  • jameslo

    @bang said:

    I am not a bitshifter guy yet.

    I applaud your positive attitude and am looking forward to when you become a card-carrying bitshifter. :)

    Does this give you any insight?
    bitshifter.pd
    Screenshot 2022-11-07 203933.png
    The numbers in the bitwise AND operations are called "bit masks", and the operations below just shift the masked bits into their proper place. You have to enter your numbers right to left to make the addition work. Finally, you have to sit down with a pad, pen, and decimal to binary converter to convince yourself that it's working.

    posted in technical issues read more
  • jameslo

    Yep, I can see it says "online" all over the site, but I don't see a link to register.

    posted in news read more
  • jameslo

    @ddw_music That's it!!! I was ignoring my panner, which when panned to the middle is down 3dB on both L & R. And for that last test with my lazy man's loopback, I just wrote something from scratch and omitted the panner. Crap, I wish I could delete this whole thread so as not to mislead anyone else. -1..1 is the full range, period. Sorry to waste everyone's time :(

    posted in technical issues read more
  • jameslo

    I sometimes use my mixer as a lazy loopback device: I output to it via S/PDIF and then take input via USB. If I send signals that step outside of -1..1 I get clipping! So so far I only see that 3dB of headroom on the analog outputs.

    posted in technical issues read more
  • jameslo

    @seb-harmonik.ar I just tested the line out of my 2012 MacBook Pro 10.14.6 and it goes up to 1.4 without clipping too! Puny signal though.

    posted in technical issues read more
  • jameslo

    @whale-av I'd be curious if anyone sees analog output clipping at +/- 1.1 and if anyone doesn't see clipping at +/- 2. That 1.4142 thing seems too...um...spooky. Happy Halloween.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!