I'm looking for a solution to have the values of input and output audio
latency inside Pd. The same many DAW's show in audio preferences.
The use case is I'm writing a patch using [abl_link~], that ensure music
event synchronization whenever I set an offset parameter with the output
audio latency.
I found these:
https://stackoverflow.com/questions/37729442/how-do-you-find-the-audio-late…
which can be a start point.. or not.... once there is not jack.
Thanks for any advance!
--
Esteban Viveros
www.estebanviveros.com
Before anyone looks further into the *details* ie. compiler flags, the configure overview output gives us a clue:
> configure:
>
> pd 0.51.3 is now configured
>
> Platform: Unknown
Clearly, configure failed and it never set the platform. The platform-specific / host checks failed and it probably half-defaults to building for Linux which is why it's trying to build the OSS audio backend.
Now, looking at the beginning of the same configure log, we see:
> checking build system type... x86_64-pc-msys
> checking host system type... x86_64-pc-msys
> configure: iPhone SDK only available for arm-apple-darwin hosts, skipping tests
> configure: Android SDK only available for arm-linux hosts, skipping tests
Hmm. The canonical host it's seeing is "x86_64-pc-msys" which is not one we actually support directly. What we support for building on windows with autootols is "mingw" see
https://github.com/pure-data/pure-data/blob/master/configure.ac#L108 <https://github.com/pure-data/pure-data/blob/master/configure.ac#L108>
So I think this a configuration issue with your setup as you are somehow not building with mingw as we have listed in the INSTALL.txt. One reason for this may be using the wrong shell, ie. MSYS2 instead of the explicit MinGW64 shell. It's been a few years since I've worked directly with MinGW & Pd, so the naming may have changed... which is also why we wrote the steps in INSTALL.txt. :)
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Hi -
I imagine that this is somehow my mistake, but I am having persistent
problems with building PD 0.51.x from git under the latest MSys2/Mingw64 gcc
$ gcc --version
gcc (GCC) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
$ gcc -dumpmachine
x86_64-pc-msys
The issues seem to center around various WIN32 compatibility hacks. If I
use the usual
$ ./autogen.sh
$ ./configure
$ make clean
$ make all
the build fails while linking pd.exe
/usr/lib/gcc/x86_64-pc-msys/10.2.0/../../../../x86_64-pc-msys/bin/ld:
pd-s_audio_oss.o: in function `oss_open_audio':
/c/Users/User/git/pure-data/src/s_audio_oss.c:305: undefined reference
to `sys_setalarm'
/c/Users/User/git/pure-data/src/s_audio_oss.c:305:(.text+0xee3):
relocation truncated to fit: R_X86_64_PC32 against undefined symbol
`sys_setalarm'
/usr/lib/gcc/x86_64-pc-msys/10.2.0/../../../../x86_64-pc-msys/bin/ld:
/c/Users/User/git/pure-data/src/s_audio_oss.c:394: undefined reference to
`sys_setalarm'
&cet
interestingly, that build also generates a warning message while compiling
s_inter.c (which defines sys_setalarm() under the right set of compiler
flags) indicating that _WIN32 is not defined.
s_inter.c: In function ‘sys_init_deken’:
s_inter.c:998:4: warning: #warning unknown OS [-Wcpp]
998 | # warning unknown OS
So if I instead build with CFLAGS=-D_WIN32, I get a different set of errors
while building s_inter.c
/usr/include/w32api/psdk_inc/_fd_types.h:100:2: warning: #warning
"fd_set and associated macros have been defined in sys/types. This can
cause runtime problems with W32 sockets" [-Wcpp]
/usr/include/w32api/winsock2.h:1025:34: error: conflicting types for
‘select’
s_inter.c:217:52: warning: passing argument 5 of ‘select’ from
incompatible pointer type [-Wincompatible-pointer-types]
/usr/include/w32api/winsock2.h:1025:116: note: expected ‘PTIMEVAL’ {aka
‘struct __ms_timeval * const’} but argument is of type ‘struct timeval *’
s_inter.c:490:17: warning: implicit declaration of function ‘write’;
did you mean ‘fwrite’? [-Wimplicit-function-declaration]
s_inter.c:1305:20: warning: implicit declaration of function ‘_spawnl’;
did you mean ‘spawnl’? [-Wimplicit-function-declaration]
s_inter.c:1305:28: error: ‘P_NOWAIT’ undeclared (first use in this
function)
s_inter.c:1493:10: warning: implicit declaration of function ‘_exit’
[-Wimplicit-function-declaration]
s_inter.c:1493:10: warning: incompatible implicit declaration of
built-in function ‘_exit’
Could someone please enlighten me? Or point me to relevant documentation?
ig gcc 10.2.0 known to be problematic?
TIA
--
GPG Public key at http://cyber-rush.org/drr/gpg-public-key.txt
Hi, when compiling ELSE for camomille in windows, me and Esteban are
getting some errors. Offending pieces of code are when trying to do things
like
t_atom at[ac];
and
t_float temp[n];
from stackflow
<https://stackoverflow.com/questions/9881777/why-do-i-get-cannot-allocate-an…>
we see "*You cannot allocate an array of unknown size with automatic
storage duration in C++. If you want a variable sized array then you need
to dynamically allocate it (or, better yet; just use a vector).*"
Thing is we don't know how to proceed here and are looking for hints, maybe
showing how other objects in Pd deal with this.
BTW, there's an issue <https://github.com/porres/pd-else/issues/881> on
ELSE's repository.
Thanks
Alex
Howdy all,
Apple is now selling new macs with their own "M1" arm CPU. We will probably get a Mac Mini at work for building & testing the architecture. I also need a new machine and am considering getting a laptop with an M1.
In either case, I anticipate being able to make a macOS arm64 build of Pd for testing. With the build system we now have, I don't foresee any major issues... hopefully. I think updating pd-lib-builder should be similarly straightforward.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
> On Nov 3, 2020, at 6:04 PM, pd-dev-request(a)lists.iem.at wrote:
>
> Message: 2
> Date: Tue, 03 Nov 2020 18:03:59 +0100
> From: IOhannes m zmölnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>>
> To: pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>
> Subject: Re: [PD-dev] [PD] [PD-announce] Pd 0.513 test5 released
> Message-ID: <33E1D9D9-D44A-46DE-B598-B6DD3B49E6C4(a)iem.at <mailto:33E1D9D9-D44A-46DE-B598-B6DD3B49E6C4@iem.at>>
> Content-Type: text/plain; charset=utf-8
>
> Am 3. November 2020 15:37:38 MEZ schrieb Dan Wilcox <danomatika(a)gmail.com <mailto:danomatika@gmail.com>>:
>> Main point is that the 64 bit build needs the 64 bit Tk.
>
> sorry for being dumb, but: why?
Why not?
> I agree that its probably preferred to have matching architectures between Pd-core and Pd-GUI, but is it a requirement?
I would say yes.
> afaict the problem lucarda is describing comes mostly from the fact that wish.exe and pdfontloader.dll have different archs. (or is this what you were saying).
Yes, that's what I was saying. If previous versions of the windows 64 bit build worked fine with a 64 bit pdfontloader, then it's because Pd game with a 64 bit tk, so it follows that is what's needed in this case.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Main point is that the 64 bit build needs the 64 bit Tk.
> On Nov 3, 2020, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote:
>
> Message: 1
> Date: Tue, 3 Nov 2020 04:43:42 -0300
> From: Lucas Cordiviola <lucarda27(a)hotmail.com <mailto:lucarda27@hotmail.com>>
> To: Miller Puckette <msp(a)ucsd.edu <mailto:msp@ucsd.edu>>
> Cc: pd-dev <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>>
> Subject: Re: [PD-dev] [PD] [PD-announce] Pd 0.513 test5 released
> Message-ID:
> <MWHPR22MB0864B7EAE3380C7412622C01A6110(a)MWHPR22MB0864.namprd22.prod.outlook.com <mailto:MWHPR22MB0864B7EAE3380C7412622C01A6110@MWHPR22MB0864.namprd22.prod.outlook.com>>
>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi Miller,
>
> On Windows 64bit builds starting from Pd 0.51.3-test2 you have switched
> tcl/tk-8.6.8(64bit) to 8.6.10(32bit).
>
> Was it intentional to change the arch?
>
> Pdfontloader.dll (64bit) has stopped loading and Pd falls-back to
> courier font.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Hi Miller,
On Windows 64bit builds starting from Pd 0.51.3-test2 you have switched
tcl/tk-8.6.8(64bit) to 8.6.10(32bit).
Was it intentional to change the arch?
Pdfontloader.dll (64bit) has stopped loading and Pd falls-back to
courier font.
--
Mensaje telepatico asistido por maquinas.
On 11/3/2020 12:54 AM, Miller Puckette via Pd-announce wrote:
> Ok... test 5 now. Improved Mac 10.15 permission stuff and some more bug fixes.
>
> http://msp.ucsd.edu/software.htm
> https://github.com/pure-data/pure-data
>
> cheers
> Miller
>
>
>
> _______________________________________________
> Pd-announce mailing list
> Pd-announce(a)lists.iem.at
> https://lists.puredata.info/listinfo/pd-announce
> _______________________________________________
> Pd-list(a)lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list