Hallo,
Roman Haefeli hat gesagt: // Roman Haefeli wrote:
as an alternative:
assuming the files were in 16 bit, wouldn't it make more sense to create
a ramdisk and store all wav-files there in order to read them with
[readsf~]? this way you would save half of the amount, because they are
Hans-Christoph Steiner wrote:
That would be a very nice object to have: [nosleep]. It probably
or probably [meth]?
are you envisioning an object to put the entire machine into
performance mode (probably tuneable), or just the harddisk or just the
performer?
fgamdr
IOhannes
+0200
From: Damian Stewart [EMAIL PROTECTED]
Subject: [PD] how to avoid (most/many/some) readsf~ dropouts
To: PD-List pd-list@iem.at
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
hey,
one thing i've noticed with readsf~ using it in my own live
Dr. Greg Wilder wrote:
Matt Barber wrote:
Hey Greg,
I wonder what would happen
if you split your 8-channel files and played them simultaneously as
4-channel soundfiles...
how long are the files? if they're not so long, and you've got a computer
with a lot of memory, you might be able to
Hallo,
Damian Stewart hat gesagt: // Damian Stewart wrote:
Dr. Greg Wilder wrote:
Matt Barber wrote:
Hey Greg,
I wonder what would happen
if you split your 8-channel files and played them simultaneously as
4-channel soundfiles...
how long are the files? if they're not so long,
On Tue, 2008-07-15 at 19:09 +0200, Frank Barknecht wrote:
Hallo,
Damian Stewart hat gesagt: // Damian Stewart wrote:
Dr. Greg Wilder wrote:
Matt Barber wrote:
Hey Greg,
I wonder what would happen
if you split your 8-channel files and played them simultaneously as
4-channel
Of course, the 8-channel environment is useful for its ambisonic and other
spatialization potential, and one solution that works well (for certain
musical situations) is to spatialize monophonic soundfiles in real time.
This is a great solution for reducing performance demand on the hard
Matt Barber wrote:
Of course, the 8-channel environment is useful for its ambisonic and other
spatialization potential, and one solution that works well (for certain
musical situations) is to spatialize monophonic soundfiles in real time.
This is a great solution for reducing performance
Matt Barber wrote:
Date: Sat, 12 Jul 2008 13:56:54 +0200
From: Damian Stewart [EMAIL PROTECTED]
Subject: [PD] how to avoid (most/many/some) readsf~ dropouts
To: PD-List pd-list@iem.at
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
hey,
one thing i've
Damian Stewart wrote:
Dr. Greg Wilder wrote:
I've attached the latest version of my basic playback (w/fade) patch
for suggestions/comments... Unfortunately, your ascii patch didn't
line up, would you mind posting an example patch that shows your method?
first thing i notice when i open
i just found that removing the [wavinfo] external from my patch also helped
reduce clicking.
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
Damian Stewart wrote:
Dr. Greg Wilder wrote:
I've attached the latest version of my basic playback (w/fade) patch
for suggestions/comments... Unfortunately, your ascii patch didn't
line up, would you mind posting an example patch that shows your method?
first thing i notice when i open it
Greg, you may like to experiment with tweaking the disk caches.
For linux see here:
http://www.linuxdevcenter.com/pub/a/linux/2000/06/29/hdparm.html
On Mon, 14 Jul 2008 17:11:02 -0400
Dr. Greg Wilder [EMAIL PROTECTED] wrote:
Damian Stewart wrote:
Dr. Greg Wilder wrote:
I've
Andy Farnell wrote:
Greg, you may like to experiment with tweaking the disk caches.
For linux see here:
http://www.linuxdevcenter.com/pub/a/linux/2000/06/29/hdparm.html
Thanks for the idea, Andy. It seems my stock Studio64 RT kernel is
treating my SATA as a SCSI device -- but sdparm
That would be a very nice object to have: [nosleep]. It probably
wouldn't be hard on GNU/Linux. Then you could embed in performance
patches.
.hc
On Jul 12, 2008, at 10:39 PM, hard off wrote:
julian! you're a legend!!! that was totally the problem. it
totally makes sense too,
13:56:54 +0200
From: Damian Stewart [EMAIL PROTECTED]
Subject: [PD] how to avoid (most/many/some) readsf~ dropouts
To: PD-List pd-list@iem.at
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
hey,
one thing i've noticed with readsf~ using it in my
Date: Sat, 12 Jul 2008 13:56:54 +0200
From: Damian Stewart [EMAIL PROTECTED]
Subject: [PD] how to avoid (most/many/some) readsf~ dropouts
To: PD-List pd-list@iem.at
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
hey,
one thing i've noticed
hey,
one thing i've noticed with readsf~ using it in my own live-performance
sets is that doing this
[symbol blahblahblah.aif]
|
[open $1, bang(
|
[readsf~]
sometimes causes dropouts. but if you go
[symbol blahblahblah.aif]
|
[t b a]
| \
| \
[del 50][open $1(
|
i was going to post about the readsf~ dropout problem today. good timing.
in my case though, i am sending the open message, and then manually banging
to start, usually at least 15-20 seconds after opening,
but i still get dropouts! not all the time, not in any pattern that i can
recognise, but
Is your hard drive going to sleep? I used to get this on osx when the
HD would sleep. Telling it not to rest fixed the issue. I now
routinely do this when performing live.
JP
On Jul 12, 2008, at 8:54 AM, hard off wrote:
i was going to post about the readsf~ dropout problem today. good
julian! you're a legend!!! that was totally the problem. it totally makes
sense too, because when i sent a couple of 'open' messages in a row, i
wouldn't get clicks, but if i left it for a while, it would drop out.
now i have zero dropouts. awesome.
21 matches
Mail list logo
