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

    I don't know about the UI question (and I agree!), but regarding externals: have you been using the form [library_name/external]... like:

    [ekext/cup]
    or
    [cyclone/bondo]

    I haven't had any problems with deken & this method... deken installs to the place PD wants them automatically. I'm on Linux, so maybe it's different on Windows.

    posted in technical issues read more
  • Load074

    My guess would still be sample rate. If your original was at 48k, most players that I know of would automatically adjust and play at the appropriate sample rate. But PD would still be playing according to its settings, ie, 44.1 in your case. So a little slow and out of tune makes sense to me.

    You could check the sample rate, or just save a copy at 44.1 in Audacity or some such to see if that is the case.

    posted in technical issues read more
  • Load074

    @MasettoSlothrop If it's low-quality bangin' for scant bucks you're after, I've had surprisingly good luck with this StarTech 7.1 USB gadget.

    https://www.startech.com/Cards-Adapters/Sound/USB-Audio/USB-7-Channel-Audio-Adapter-with-SPDIF~ICUSBAUDIO7D

    I'm not necessarily RECOMMENDING it - it's only four stereo minis, and I don't know about its input capabilities (as that's never something I'm doing), but for under $40 USD for eight channels, it's been a good purchase for me. I've been perfectly happy plugging my thrift-store mismatched computer speakers in and surrounding myself with clicks and squeals. Supercollider, Pure Data, and Reaper all worked pretty painlessly on Linux, OSX, and (if i remember correctly) Windows 10.

    posted in I/O hardware diyread more
  • Load074

    YES! Thank you!

    posted in technical issues read more
  • Load074

    I am trying to Vanilla-ize my PD-Extended patches, and for the most part, it's going great. But I miss "knob," and I can't find a suitable replacement.

    I've tried moonlib/mknob but something is unhappy... perhaps related to the PD-X warning about moonlib on 64 bit systems? Anyway, I can't adjust its properties with everything barfing.

    I can't find flatspace in Synaptic, in order to try flatspace/knob. I just installed deken (finally) but nothing comes up for Knob or Flatspace.

    Does anyone have any suggestions? Basically, I want a nice visual correlation to the knob on my Korg Nanokontrol, for my less PD-savvy (so pretty damned unsavvy) musical collaborators. Guess I could use a really squat HSlider... but I like Knob.

    By the way, I'm running KXStudio/Ubuntu 64bit. And I wasn't able to get PD-L2Ork working either (now I've forgotten why - some unmet dependency).

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!