• 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
  • Load074

    Are you sure you have PD connected to a MIDI device (or softsynth)? That's not automatic, at least not on my system. In the video you mention, PD is not creating audio. He's using PD to control another program - that other program is actually making the sound.

    posted in this forum read more
  • Load074

    @geraldbiggs I'm not sure what the potential complications you're referring to are, but I will say that I've been using KXStudio as my primary/nearly-only environment for about two years now, and I love it. I used the ISO they provided (instead of adding repos to another flavor), which is currently Ubuntu 14.04 with KDE. Really, it's just Ubuntu with KDE... but lots of nicer, fancier audio stuff worked almost immediately (I say "almost" because this was a couple of years ago, but I don't remember any problems).
    So I guess I'm wondering why you'd want a dual-boot with Ubuntu & KXStudio (if that's what you're saying), because KXStudio runs as well as any non-audio-based Linux I've used.
    And PD & SC (and Reaper, under Wine, though there's also a native now) are what I usually use, too.

    posted in technical issues read more
  • Load074

    Thanks @weightless. I was thinking it'd be something like that when I mentioned "predictive math," but I didn't realize it would be quite so 1-to-1. I'll try it out.

    posted in technical issues read more
  • Load074

    Is there a quick way to see where tabosc4~ is in its cycle? I want to have a display with a [hsl] moving as tabosc~ goes slowly (and at varying speeds) across a waveform.
    I don't want to simply do some predictive math, because the oscillation speed is changing too much. I'm sure they'd get out of sync.
    I realize that if I'd been using tabread4~ I'd have been supplying that info... but I'm not going back to change my patch now.
    I think the answer is "no." There's only one output, so I don't see how I could get it.
    Thanks gang!

    posted in technical issues read more
  • Load074

    I will help you!

    In your two sub-patches, pd1 and pd2, you are using the same variable names (phase and cutoff). If you re-name them in one (or both) of the sub-patches, ie, phase1 / cutoff1 & phase2 / cutoff2, it will work.

    When you are running PD, every workspace/window can send and receive values.

    So you have to be careful with your names... even if they're two totally different patches, if both use a variable named "boomboom," you'll have them talking to each other.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!