Can people share their opinions on the simplest way to create a looping soundfile.
Thanks
pp
Check this http://www.pd-tutorial.com/english/patches/3-4-2-4-sampler-big.pd
On Tue, Jan 22, 2013 at 10:50 PM, Pagano, Patrick <pat@digitalworlds.ufl.edu
wrote:
Can people share their opinions on the simplest way to create a looping soundfile.****
Thanks****
pp****
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
That is a nice one, thanks. pp
From: Alexandros Drymonitis [mailto:adrcki@gmail.com] Sent: Tuesday, January 22, 2013 3:57 PM To: Pagano, Patrick Cc: pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
Check this http://www.pd-tutorial.com/english/patches/3-4-2-4-sampler-big.pd
On Tue, Jan 22, 2013 at 10:50 PM, Pagano, Patrick <pat@digitalworlds.ufl.edumailto:pat@digitalworlds.ufl.edu> wrote: Can people share their opinions on the simplest way to create a looping soundfile.
Thanks
pp
Pd-list@iem.atmailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Actually this one, though very nice can only hold files that are so large? It seems to snip off ends of longer soundfiles and the speed of the file if another file is loaded becomes confused. I am very interested in finding a non-external way to constantly loop sound files of ANY size.
So far Eric Lyon's Player~ seems to be a benchmark, I would love some more ideas though
TY
pp
From: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] On Behalf Of Pagano, Patrick Sent: Tuesday, January 22, 2013 4:03 PM To: Alexandros Drymonitis Cc: pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
That is a nice one, thanks. pp
From: Alexandros Drymonitis [mailto:adrcki@gmail.com] Sent: Tuesday, January 22, 2013 3:57 PM To: Pagano, Patrick Cc: pd-list@iem.atmailto:pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
Check this http://www.pd-tutorial.com/english/patches/3-4-2-4-sampler-big.pd
On Tue, Jan 22, 2013 at 10:50 PM, Pagano, Patrick <pat@digitalworlds.ufl.edumailto:pat@digitalworlds.ufl.edu> wrote: Can people share their opinions on the simplest way to create a looping soundfile.
Thanks
pp
Pd-list@iem.atmailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
De: "Patrick Pagano" pat@digitalworlds.ufl.edu
I am very interested in finding a non-external way to constantly loop sound files of ANY size.
using two [readsf~] is working so far so good for looping large soundfiles, with the offset option and a signal crossfading between them.
On Die, 2013-01-22 at 22:20 +0100, Patrice Colet wrote:
De: "Patrick Pagano" pat@digitalworlds.ufl.edu
I am very interested in finding a non-external way to constantly loop sound files of ANY size.
using two [readsf~] is working so far so good for looping large soundfiles, with the offset option and a signal crossfading between them.
Why using an offset? Why not letting each of them play the file to the end?
Roman
De: "Roman Haefeli" reduzent@gmail.com Envoyé: Mardi 22 Janvier 2013 23:24:09
On Die, 2013-01-22 at 22:20 +0100, Patrice Colet wrote:
De: "Patrick Pagano" pat@digitalworlds.ufl.edu
I am very interested in finding a non-external way to constantly loop sound files of ANY size.
using two [readsf~] is working so far so good for looping large soundfiles, with the offset option and a signal crossfading between them.
Why using an offset? Why not letting each of them play the file to the end?
Offset would be used for looping a part of the soundfile only, it's not simple indeed because we need to know the file length too, but's it's usefull for looping files writen in real time with [writesf~] for example, in this case the offset is used for reading the sound that comes after the end of the loop for mixing it with the begining of the loop, and then it can prevent to cut some sound's releases, or reverb.
Not Sure that one will not loop properly because of the need for an open message each time.
-----Original Message----- From: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] On Behalf Of Roman Haefeli Sent: Tuesday, January 22, 2013 4:04 PM To: pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
On Die, 2013-01-22 at 20:50 +0000, Pagano, Patrick wrote:
Can people share their opinions on the simplest way to create a looping soundfile.
[r playagain] | [open /path/to/your/file.wav, 1( | [readsf~ ] | [s playagain]
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Die, 2013-01-22 at 21:09 +0000, Pagano, Patrick wrote:
Not Sure that one will not loop properly because of the need for an open message each time.
You are indeed right. It is not the proper way to do it. Even the help-file of [readsf~] states it. However, in practice it usually works flawlessly (probably nowadays disks seem fast enough and there is enough memory for fs caches). Simply try it with the help of [readsf~ ].
Also the table based approach works, though I'd make two modifications to the previously posted patch. Use the '-maxsize ' flag for the message to [soundfiler] in order to allow bigger tables. Then, I'd get rid of [tabread4~], as it is not needed when you only want to play at original speed. Actually, I even wouldn't use [tabread~ ], because for very large tables, the index from [phasor~ ] or [line~ ] will not be precise enough to hit every sample after position 16'000'000 (limit of the 32bit floating point format). If you use [tabplay~], it is as simple my previous example with [readsf~ ]:
[r playagain] | [tabplay yourpreviouslyfilledtable] | [s playagain]
IIRC, [tabplay~] doesn't suffer from that precision problem described before.
Roman
-----Original Message----- From: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] On Behalf Of Roman Haefeli Sent: Tuesday, January 22, 2013 4:04 PM To: pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
On Die, 2013-01-22 at 20:50 +0000, Pagano, Patrick wrote:
Can people share their opinions on the simplest way to create a looping soundfile.
[r playagain] | [open /path/to/your/file.wav, 1( | [readsf~ ] | [s playagain]
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Maybe I'm not getting anything related about this topic... but what about using the end "bang" that many audio-file-playing-externals feature?
On Tue, Jan 22, 2013 at 10:48 PM, Roman Haefeli reduzent@gmail.com wrote:
On Die, 2013-01-22 at 21:09 +0000, Pagano, Patrick wrote:
Not Sure that one will not loop properly because of the need for an open
message each time.
You are indeed right. It is not the proper way to do it. Even the help-file of [readsf~] states it. However, in practice it usually works flawlessly (probably nowadays disks seem fast enough and there is enough memory for fs caches). Simply try it with the help of [readsf~ ].
Also the table based approach works, though I'd make two modifications to the previously posted patch. Use the '-maxsize ' flag for the message to [soundfiler] in order to allow bigger tables. Then, I'd get rid of [tabread4~], as it is not needed when you only want to play at original speed. Actually, I even wouldn't use [tabread~ ], because for very large tables, the index from [phasor~ ] or [line~ ] will not be precise enough to hit every sample after position 16'000'000 (limit of the 32bit floating point format). If you use [tabplay~], it is as simple my previous example with [readsf~ ]:
[r playagain] | [tabplay yourpreviouslyfilledtable] | [s playagain]
IIRC, [tabplay~] doesn't suffer from that precision problem described before.
Roman
-----Original Message----- From: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] On Behalf
Of Roman Haefeli
Sent: Tuesday, January 22, 2013 4:04 PM To: pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
On Die, 2013-01-22 at 20:50 +0000, Pagano, Patrick wrote:
Can people share their opinions on the simplest way to create a looping soundfile.
[r playagain] | [open /path/to/your/file.wav, 1( | [readsf~ ] | [s playagain]
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I would like it to be inside Pure Data without the use of externals. I am quite aware of the externals, but I am curious on how people have done it without an external
:)
From: Òscar Martínez Carmona [mailto:xamps23@gmail.com] Sent: Tuesday, January 22, 2013 5:11 PM To: Roman Haefeli Cc: Pagano, Patrick; pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
Maybe I'm not getting anything related about this topic... but what about using the end "bang" that many audio-file-playing-externals feature?
On Tue, Jan 22, 2013 at 10:48 PM, Roman Haefeli <reduzent@gmail.commailto:reduzent@gmail.com> wrote: On Die, 2013-01-22 at 21:09 +0000, Pagano, Patrick wrote:
Not Sure that one will not loop properly because of the need for an open message each time.
You are indeed right. It is not the proper way to do it. Even the help-file of [readsf~] states it. However, in practice it usually works flawlessly (probably nowadays disks seem fast enough and there is enough memory for fs caches). Simply try it with the help of [readsf~ ].
Also the table based approach works, though I'd make two modifications to the previously posted patch. Use the '-maxsize ' flag for the message to [soundfiler] in order to allow bigger tables. Then, I'd get rid of [tabread4~], as it is not needed when you only want to play at original speed. Actually, I even wouldn't use [tabread~ ], because for very large tables, the index from [phasor~ ] or [line~ ] will not be precise enough to hit every sample after position 16'000'000 (limit of the 32bit floating point format). If you use [tabplay~], it is as simple my previous example with [readsf~ ]:
[r playagain] | [tabplay yourpreviouslyfilledtable] | [s playagain]
IIRC, [tabplay~] doesn't suffer from that precision problem described before.
Roman
-----Original Message----- From: pd-list-bounces@iem.atmailto:pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.atmailto:pd-list-bounces@iem.at] On Behalf Of Roman Haefeli Sent: Tuesday, January 22, 2013 4:04 PM To: pd-list@iem.atmailto:pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
On Die, 2013-01-22 at 20:50 +0000, Pagano, Patrick wrote:
Can people share their opinions on the simplest way to create a looping soundfile.
[r playagain] | [open /path/to/your/file.wav, 1( | [readsf~ ] | [s playagain]
Roman
Pd-list@iem.atmailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.atmailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Òscar Martínez Carmona
What Òscar is suggesting also applies to [readsf~] and [tabplay~]. Both loop quite seamlessly when I've used them. the [open ( to [readsf~] doesn't seem to take any time. I haven't done the [readsf~] looping under heavy load tho.
.hc
On 01/22/2013 05:15 PM, Pagano, Patrick wrote:
I would like it to be inside Pure Data without the use of externals. I am quite aware of the externals, but I am curious on how people have done it without an external
:)
From: Òscar Martínez Carmona [mailto:xamps23@gmail.com] Sent: Tuesday, January 22, 2013 5:11 PM To: Roman Haefeli Cc: Pagano, Patrick; pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
Maybe I'm not getting anything related about this topic... but what about using the end "bang" that many audio-file-playing-externals feature?
On Tue, Jan 22, 2013 at 10:48 PM, Roman Haefeli <reduzent@gmail.commailto:reduzent@gmail.com> wrote: On Die, 2013-01-22 at 21:09 +0000, Pagano, Patrick wrote:
Not Sure that one will not loop properly because of the need for an open message each time.
You are indeed right. It is not the proper way to do it. Even the help-file of [readsf~] states it. However, in practice it usually works flawlessly (probably nowadays disks seem fast enough and there is enough memory for fs caches). Simply try it with the help of [readsf~ ].
Also the table based approach works, though I'd make two modifications to the previously posted patch. Use the '-maxsize ' flag for the message to [soundfiler] in order to allow bigger tables. Then, I'd get rid of [tabread4~], as it is not needed when you only want to play at original speed. Actually, I even wouldn't use [tabread~ ], because for very large tables, the index from [phasor~ ] or [line~ ] will not be precise enough to hit every sample after position 16'000'000 (limit of the 32bit floating point format). If you use [tabplay~], it is as simple my previous example with [readsf~ ]:
[r playagain] | [tabplay yourpreviouslyfilledtable] | [s playagain]
IIRC, [tabplay~] doesn't suffer from that precision problem described before.
Roman
-----Original Message----- From: pd-list-bounces@iem.atmailto:pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.atmailto:pd-list-bounces@iem.at] On Behalf Of Roman Haefeli Sent: Tuesday, January 22, 2013 4:04 PM To: pd-list@iem.atmailto:pd-list@iem.at Subject: Re: [PD] Simplest way for looping soudfiles
On Die, 2013-01-22 at 20:50 +0000, Pagano, Patrick wrote:
Can people share their opinions on the simplest way to create a looping soundfile.
[r playagain] | [open /path/to/your/file.wav, 1( | [readsf~ ] | [s playagain]
Roman
Pd-list@iem.atmailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.atmailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Òscar Martínez Carmona
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 01/23/2013 01:11 AM, Hans-Christoph Steiner wrote:
What Ãscar is suggesting also applies to [readsf~] and [tabplay~]. Both loop quite seamlessly when I've used them. the [open ( to [readsf~] doesn't seem to take any time. I haven't done the [readsf~] looping under heavy load tho.
yes, but roman's original suggestion was exactly to use [readsf~]. if you read on in this thread (after all, you were replying to exactly this email), you'll notice that [readsf~] might work or not, there is simply no guarantee that it does start playing in time; and this is documented and expected behaviour.
fmasdr IOhannes
Occams razor! Below is the simplest way, which provides no control but should play your soundfile at it's actual speed and loop for ever. Just write it into an array, then...
[r retrigger]
|
[tabplay~ sample]
| |
[dac~] [s retrigger]
From: pat@digitalworlds.ufl.edu To: pd-list@iem.at Date: Tue, 22 Jan 2013 20:50:09 +0000 Subject: [PD] Simplest way for looping soudfiles
Can people share their opinions on the simplest way to create a looping soundfile.
Thanks
pp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list