<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[readsf~ and sample rates]]></title><description><![CDATA[<p>Hello!</p>
<p>I am working with a handful of samples, all of which are wav-files, single-channel, 16-Bit, 11025 Hertz, to be precise.<br />
Running PD at 44100 Hertz, the samples are played back up-sampled, naturally.</p>
<p>I understand the reasons behind this, but how do I remedy this in PD, so I can play back the samples at original pitch?<br />
How do I change the rate at which a sample is played back, without changing PDs sample rate?</p>
<p>I've spent a lot of time with block~ now, it should be the right tool for this I thought.<br />
But unfortunately, I really don't understand how to handle the block~ object, and all reading just adds to the confusion.<br />
No matter what I do, everything just turns silent as soon as I interact in any way with block~.<br />
until I delete it again.</p>
<p>All help appreciated, Thanks a lot.</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/10894/readsf-and-sample-rates</link><generator>RSS for Node</generator><lastBuildDate>Tue, 06 Oct 2026 06:32:04 GMT</lastBuildDate><atom:link href="http://forum.pdpatchrepo.info/topic/10894.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 18 Jul 2017 14:18:21 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to readsf~ and sample rates on Tue, 18 Jul 2017 14:18:21 GMT]]></title><description><![CDATA[<p>Hello!</p>
<p>I am working with a handful of samples, all of which are wav-files, single-channel, 16-Bit, 11025 Hertz, to be precise.<br />
Running PD at 44100 Hertz, the samples are played back up-sampled, naturally.</p>
<p>I understand the reasons behind this, but how do I remedy this in PD, so I can play back the samples at original pitch?<br />
How do I change the rate at which a sample is played back, without changing PDs sample rate?</p>
<p>I've spent a lot of time with block~ now, it should be the right tool for this I thought.<br />
But unfortunately, I really don't understand how to handle the block~ object, and all reading just adds to the confusion.<br />
No matter what I do, everything just turns silent as soon as I interact in any way with block~.<br />
until I delete it again.</p>
<p>All help appreciated, Thanks a lot.</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/10894/readsf-and-sample-rates</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/10894/readsf-and-sample-rates</guid><dc:creator><![CDATA[Ein Wald]]></dc:creator><pubDate>Tue, 18 Jul 2017 14:18:21 GMT</pubDate></item><item><title><![CDATA[Reply to readsf~ and sample rates on Tue, 18 Jul 2017 16:59:03 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-a" href="http://forum.pdpatchrepo.info/user/ein-wald">@Ein-Wald</a></p>
<p><a href="/uploads/files/1500393678122-resample.zip">resample.zip</a><br />
Right-click the block object for more help......<br />
You can only &quot;do&quot; multiples of 2 if you use [inlet~] or [outlet~] in the patch.... so for 11025Hz you will have to have your soundcard set to 44100Hz ..... 4X.....</p>
<p>Works well in extended, but seems to want to often crash 0.47.1 vanilla...... maybe block sizes?..... vanilla seems more stable with a lower block size..... so<br />
[block~ 2048 1 0.25] for your application.<br />
But in extended, the quality is poor, so stick with [block~ 4096 1 0.25]</p>
<p>You can do weird multiples of the block size, but as you cannot then communicate with the mother patch containing a [dac~] I cannot see how it could be used (for you... for this application).<br />
David.</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/10894/readsf-and-sample-rates/2</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/10894/readsf-and-sample-rates/2</guid><dc:creator><![CDATA[whale-av]]></dc:creator><pubDate>Tue, 18 Jul 2017 16:59:03 GMT</pubDate></item></channel></rss>