• gmoon

    One way to tell it's a camera issue is the (imperfect) specular reflection on your wooden table -- the LED light reaching the camera from that reflection has the "correct" intensity and plenty of color saturation.

    Simple auto-exposure for cameras works by averaging all the tones and adjusting exposure to achieve a "medium gray" overall. If your camera is auto-exposure only, that's a problem -- you need a dark background, but the camera will always lighten the scene (try to average it out to gray).

    Does the GoPro work? Those should have manual exposure settings in the camera.

    Otherwise, try what whale-av mentioned (and [color 0.25 0.25 0.25] and [pix-threshold] with high values), but those solutions are destructive, data-wise.

    posted in technical issues read more
  • gmoon

    It's an intensity thing, rather than a GEM issue -- either the LEDs are too bright, or the automatic exposure in the webcam is compensating for the overall darker background.

    Of course you want the video dark, relative to the LEDs. Ideally, you'd have a video camera with manual settings.

    posted in technical issues read more
  • gmoon

    @ddw_music said:

    (As a silly aside: Speaking as an American, the acronym of graph-on-parent has proven lately to be rather unfortunate, though in Pd's early years, nobody would have predicted it could get so far out of hand.)

    I probably shouldn't go there, but I have a similar reaction...

    posted in technical issues read more
  • gmoon

    @lysergik
    I've done some stuff with Pd/oversampling, although not related to multichannel synths (mono audio streams).

    I don't think you're wrong describing the CPU hit -- and that's not really a knock on Pd. It's the nature of all that extra data.

    However, definitely try a lower sampling rate; 4X or 8X, and see how that impacts your machine. The J07.oversampling.pd patch ref'd in the manual also illustrates the butterworth.pd coefficients patch, and dropping the low-pass cutoff freq will reduce antialiasing.

    Any low-pass filter will help (even lop~), though some will impact your sound more than others. I found biquad~ to be quite useful with incoming audio signals. Sample-resolution tools like fexpr~ will hit the CPU in a major way, but the expr~ obj not so much (it's unfortunately not as useful for filtering). I tend to be limited to vanilla Pd; you may not be.

    Working with synth-generated signals within the upsampled block at least reduces some of the overhead, verses upsampled/downsampled streams. It also lends to some sculpting of the sounds without oversampling (the second half of your manual link).

    There's much to be said for really targeted and tailored EQ. I like to think much of the 'magic' of commercial software is carefully working around limitations.

    I'm unclear on how (or whether) Pd distributes any processes. It might be interesting to try the pd~ obj, and explore "Embedding Pd in Pd" as outlined in Puckette's article on multiprocessors & Pd.

    posted in technical issues read more
  • gmoon

    @cuinjune Thanks - bookmarked!

    (Ofelia is really pretty amazing, btw.)

    posted in technical issues read more
  • gmoon

    @alexandros
    If I recall, that install failed until I placed all the OpenFrameWorks source in the ~/OF/ directory. I.e., it wouldn't compile correctly in a subdirectory, only the base of my home dir. That wasn't clear to me from the install docs. And Ofelia source into the ~/OF/addons/ dir.

    Deken fails w/Ofelia in my Ubuntu install due to (I believe -- I don't want to try again and overwrite the existing version) a checksum error. Deken does find the external, they just won't install.

    posted in technical issues read more
  • gmoon

    You can compile the latest source version, and run Pd locally, in your home dir. Note that it doesn't come without some issues, mostly with paths and externals. But vanilla usually works fine.

    I'm also (generally) using the 0.50.2 in Ubuntu 20.04.1 repositories, but that's due to the lengthy process of compiling Ofelia to work with that version (yeah, "breaking something" in Linux is a thing). Deken didn't work for that external.

    posted in technical issues read more
  • gmoon

    @Pierre-Guillot
    Oops, sorry, when I saw "enhancement" and "removed from to do in 1.0.7" I thought it was done. My bad.

    posted in news read more
  • gmoon

    @Pierre-Guillot Thanks Pierre -- all my plugins build and work well with this beta release. Glad you kept the JUCE dialogs for openpanel and savepanel.

    Is there any documentation for the new image properties capabilities mentioned in issue #122 (size, anchor, level, etc)?

    posted in news read more
  • gmoon

    What you're describing (a fixed order of FX) should be easy to do with a crossfade.

    Somewhat more complicated if you wish to change the order...

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!