Howdy all,
I did give up for a while. The discussion is here:
https://github.com/pure-data/pure-data/pull/897 <https://github.com/pure-data/pure-data/pull/897>
I still have the relevant code but there was simply too much to do back then and I had to pull back and put it on the back burner. It's still something I think should be working in Pd, but maybe restricted to *read* only as a start instead of me trying to implement full write access.
My first focus is to get the sound file updates into a Pd release as we need CAF and AIFC support for a major project at work: https://github.com/pure-data/pure-data/pull/855 <https://github.com/pure-data/pure-data/pull/855>
Once that is in, say Pd 0.52, then I can refactor the previous meta read code, otherwise there is no-one stopping someone from writing an external using something like libsndfile to poop out metadata....
> On Nov 9, 2020, at 1:28 PM, pd-list-request(a)lists.iem.at wrote:
>
> Date: Mon, 9 Nov 2020 13:15:15 +0100
> From: "Ingo" <ingo(a)miamiwave.com <mailto:ingo@miamiwave.com>>
> To: "'Alexandre Torres Porres'" <porres(a)gmail.com <mailto:porres@gmail.com>>
> Cc: "'Pd-List'" <pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at>>
> Subject: Re: [PD] Sample loop - start and end point (WAV files)
> Message-ID: <000001d6b691$fbb7acc0$f3270640$(a)miamiwave.com <mailto:000001d6b691$fbb7acc0$f3270640$@miamiwave.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Dan Wilcox was working in the ability of [soundfiler] to read the loop point within Pd.
>
> In Pd 0.51.1 there was still no change concerning sample loop points - unless it's not documented in the help file.
>
>
>
> Reading and writing loop points outside of Pd is no problem. I've been doing this for more that 30 years.
>
>
>
> However, I need to be able to automatically read loop points within Pd when unknown samples are being loaded.
>
> So far I had to get the loop points in other softwares and write lists for Pd to be able to handle them.
>
> This is rather tedious and also prone for errors. One little typo and you get clicks!
>
>
>
> Especially this won't work for simply loading new sample into an existing Pd patch by other users.
>
>
>
> I hope Dan didn't give up on ths . . .
>
>
>
> Ingo
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Hi everybody,
I know it had been a problem in the past to read out the loop information of
wav samples.
I have not followed any further development since years.
Is there anything (like an external) that can read the loop points of .wav
samples by now?
If not has anybody been successful reading the header information with
something like [mrpeach/binfile]?
I know that loop points can be stored somwhere or somehow in the header.
Unfortunately I cannot see from the Microsoft WAVE soundfile format where
the loop points would be or find any information on it.
http://soundfile.sapp.org/doc/WaveFormat/
Any ideas?
Am I looking at the wrong file header type?
Up until now I had been creating loops by copying the loop start and end
point manually from the readings of SoundForge.
However, I'm going to need a method soon that can read the loop points
directly from the samples.
Thanks!
Ingo
Hi,
it seems that opening /tmp/foo.wav and starting to write into it on
Windows10 from Pd 0.51.2 and DSP turned on will halt Pd after a few
seconds.
Is this known?
cheers, Peter
as of today, i have launched a new version of the backend for the deken
externals finder.
https://deken.puredata.info/
highlights:
- you can now search for externals (and objects) in your favourite
browser. https://deken.puredata.info/
- as a bonus you can also see which objects a library contains
(provided this information was uploaded)
- the delay between uploading a package and making it available in the
search should be "almost immediate" (as in: a couple of minutes) rather
than up to 24 hours. this is true for both the web-frontend and the
"Find externals" menu in Pd.
as always, i hope i didn't break anything (esp. with older versions of
the deken-plugin).
if i did, please don't hesitate to complain.
gfdsmt
IOhannes
Newer macOS versions can't run 32 bit code and so the compiler, as far as I know, won't build 32 bit versions. If you are running macOS 10.15, which I believe you are, you cannot build for 32 bit anymore.
As a result, pd-lib-builder was updated to only build for the default system, in your case 64 bit, and requires an additional flag or argument to do fat builds:
https://github.com/pure-data/pd-lib-builder/issues/50 <https://github.com/pure-data/pd-lib-builder/issues/50>
In any case, you may have to move to a dedicated build machine which stays on an older version of macOS, say 10.14, if you personal machine is to run the latest version.
> On Oct 18, 2020, at 12:00 PM, pd-list-request(a)lists.iem.at wrote:
>
> Message: 1
> Date: Sat, 17 Oct 2020 21:21:19 -0300
> From: Alexandre Torres Porres <porres(a)gmail.com <mailto:porres@gmail.com>>
> To: Pd-List <pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at>>
> Subject: [PD] compiling extenrals for mac 32 bits
> Message-ID:
> <CAEAsFmi=3p7NLYza7v_QVb7UNj52_3Zbf-U7T-PSMWsaQkoNyw(a)mail.gmail.com <mailto:CAEAsFmi=3p7NLYza7v_QVb7UNj52_3Zbf-U7T-PSMWsaQkoNyw@mail.gmail.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Hi, I see my libraries are only available for mac 64 bits. I have the
> impression it used to be also available for mac 32 bits when I compiled
> them long ago, by the way. And what I mean by this is that the same
> binaries could run on both.
>
> Well, I'm using Pd lib builder and I wonder if any of you can help me on
> what I should do. I don't mind doing two separate compilations, one for
> each.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
"whether deken find objects, solely depends on whether the uploader
decided to upload an objects-list file (*.dek.txt)."
I think that answers my question :)
Cheers,
Mario
Could be system permissions for reading the microphone. Try going to the Security panel and enable Microphone access for Pd.
Normally, it should show the request dialog automatically, but sometimes it doesn't, maybe due to running different versions of Pd on the same system? I'm not sure off the top of my head.
> On Nov 1, 2020, at 12:00 PM, pd-list-request(a)lists.iem.at wrote:
>
> Date: Sat, 31 Oct 2020 16:36:13 -0400
> From: Ricky Graham <rickygrahammusic(a)gmail.com <mailto:rickygrahammusic@gmail.com>>
> To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at>
> Subject: [PD] error opening audio: Internal PortAudio error
> Message-ID: <488FA85A-79FB-4577-881A-852EB7C61045(a)gmail.com <mailto:488FA85A-79FB-4577-881A-852EB7C61045@gmail.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> When I switch on DSP using Pd-0.51 (stable build) on macOS Catalina 10.15.7, I get the following error:
> error opening audio: Internal PortAudio error
>
> Any ideas how to resolve this issue?
>
> Best,
>
> Ricky
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>