• pman

    Thank you for your help David. I tried setting delay to 80 and 100 with no luck.
    I did run 'realtimeconfigquickscan.pl and am attaching the results. I'm also attaching a copy of my '/etc/security/limits.conf' file. It is worrysome that I cannot set a realtime priority even though I have that parameter set in limits.conf.
    Thanks again for your help!

    Screenshot 2020-06-07 at 1.02.08 PM.png

    output from realtimeconfigquickscan:
    Screenshot 2020-06-07 at 1.03.59 PM.png

    posted in technical issues read more
  • pman

    Hello folks,

    I have been struggling for the last several days trying to get any version of Puredata to work correctly on Chromebook Crostini. It almost works. It runs and I get sound but it is extremely scratchy and broken up.

    Firstly, I know that audio can work because csound 6.12 works well with perfect sound. No hiccups at all.

    I am running 83.xxxxx.77 official version of chromeos on an acer 14" Chromebook. I have tried many things to try to get some version of Puredata to work. I have used apt-get to install pd-version 0.49.x. I have downloaded and built from source pd versions 0.50.2 and 0.51 (brand-new). Every version runs and makes a similar complaint both on the command line and in the running program (see below):

    "priority X scheduling failed; running at normal priority" - where X is 94, 92, 8 or 6.

    I have tried multiple command line switches and setup parameters all with the same results. Additionally, as you can see from the screencapture below, once DSP is turned on the helpful 'Audio I/O error' message is displayed. I have researched and tried many things including adding the audio group and my name to '/etc/security/limits.conf' with the same result. Also, I have run pd without realtime scheduling: 'pd -nrt' with the same scratchy sound results.
    I would be extremely grateful to anyone who could help me solve this problem or point me in the right direction. Perhaps I am missing something simple and/or obvious. Thank you in Advance!

    Screenshot 2020-06-06 at 1.53.00 PM.png

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!