• Load074

    What a useful bit of knowledge. So glad you figured that out; thanks again.

    posted in technical issues read more
  • Load074

    Unglaublich - exactly what I needed! Thank you.

    Say - how did you know this? Is it documented somewhere? Because I couldn't find it.

    posted in technical issues read more
  • Load074

    I'm new to the [clone] game. Is there a way to poll the [clone] object to see which instance number it's currently on?

    Let's say I've got 16 cloned synths. I'm semi-randomly changing certain parameters, of one synth at a time, but it doesn't really matter which one. I've been doing this with [next( and [this(. But I'm curious to see WHICH instance I've changed, say, "rate" on, and which one had "onset" increased.

    Does this make sense? Well, my particular use-case isn't that relevant; I'm just wondering about asking [clone] which synth-instance its counter, as triggered by [next(, is on.

    posted in technical issues read more
  • Load074

    of COURSE! The good ol' [set $1(. How quickly we forget.
    I guess there's no way of putting that in the [hslider] properties, which is actually where I was receiving my "fromPhasor" (instead of using wires). But that's better really; I always forget that I used the "properties" for send/receive after a few weeks, and have a horrible time troubleshooting my work.
    Thanks!

    posted in technical issues read more
  • Load074

    I set this up so that a [phasor~] is reading through a table, an [hslider] underneath the table provides a visual of where in the table we are, AND you can adjust the [hslider] to re-position the playback.

    This works perfectly, but it seems a little... inelegant. I don't like the fact that I'm resetting the phase of [phasor~] with every [metro] bang. It's like I'm doing double work... the phase reset is only useful when I move the [hslider] by hand.

    Anyone have any opinions on this? Like I said, it works fine, it just seems like there must be a prettier way to do it.inelegant_screenshot.png

    posted in technical issues read more
  • Load074

    I've had issues with PD and its sound server on Linux - sometimes I'll need to kill PD with some other method (like XKILL... that's alt-F2, then type "xkill" + enter, then click the skull-and-crossbones on your PD window).
    I am not at my computer, and I can't recall exactly what causes my PD to stay open (but non-functioning)... but I have, sometimes, had similar issues (though not consistently!). Anyway, temporarily, at least some other kill function can keep you from needing to reboot the whole system.

    posted in technical issues read more
  • Load074

    That's a very good point... but yes, I sometimes do route PD to other software. I'm also trying to get my setup so that I can painlessly switch between programs, and/or interconnect them, without a lot of mess.

    And - maybe it's just me, but I have been ALWAYS using Jack for a few years now... it's sort of the default setup for KXStudio and AVLinux, which is what I've been running. So it's the workflow I'm used to.

    Someone at linuxmusicians pointed out that a 192 buffer size satisfies both 64 and 48... Math! Genius!

    posted in technical issues read more
  • Load074

    This query is probably too specific to be relevant to very many people...

    But I've been trying to get the best audio performance out of my computer. I am running Debian (Linux), using Jack, and an external soundcard (Focusrite Scarlett 18i20). By using this nifty program called "xruncounter" I was able to determine that my setup prefers a frames-per-period size as a multiple of the sample rate (48k, so 92 or 144), instead of the usual powers-of-two. However, PD absolutely hates that! Basic sine waves are very distorted (sounding like a sample rate mismatch). SuperCollider is much the same.

    I don't know if there's a part of PD that I can adjust to compensate for this. I thought maybe making the Buffer Size also 48 or 92 might fix that issue... but, as we all know, PD only allows Buffer Sizes selected from the drop-down menu, all powers of 2.

    Any thoughts? I'm just curious, in general, if anyone has anything to say. It's interesting that PD and SuperCollider don't work right with these settings, but other audio software seems to (though I haven't done extensive testing).

    And, if you're using Jack and Linux and are curious about this, here's where I started:
    https://linuxmusicians.com/viewtopic.php?f=27&t=19268
    https://linuxmusicians.com/viewtopic.php?f=27&t=17033
    and my thread:
    https://linuxmusicians.com/viewtopic.php?f=27&t=19907

    posted in technical issues read more
  • Load074

    If Curtis Roads is floating your boat, I'm going back to what I almost suggested initially but thought was too "raw." I really like some (Florian) Hecker. More like computer "noise" than concrete (though he DOES like to use Xenakis' Gendy program). I'd suggest checking out his PV Treks and/or Recordings for Rephlex.... also, Sun Pandamonium is a "classic" but those first two give more giggly smiles per second.

    posted in Off topic read more
  • Load074

    That's quite a shame. Makes me nervous... though I must say, I haven't experienced it (yet). I just tried both Nanokontrol and Nanoknontrol2 on my AVLinux (Debian) system with PD 0.49.0, and nothing untoward happened. Jigglin' those li'l sliders fast as my fingers could allow, all 8 at a time sometimes.
    This is just with the "Test Audio and MIDI" patch open, right?

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!