Richard Damon <Richard(a)Damon-Family.org> wrote:
> From your description, your fundamental problem is you are trying to
> automatically "control" things that weren't designed to be automatically
> controlled in the way you are attempting.
<snip>
> What you seem to be missing is that you could get the podcasts from a
> browser, and all a browser is is a program. It isn't that much work to
> write a rudimentary browser in python, especially if you don't actually
> need to display the results to a user, but are only trying to automate a
> particular task.
Even easier, the few NPR podcasts I just checked now have RSS
feeds of their episodes (as expected). It seems it would be much
easier to just download the latest episode based on the XML file,
normalize, send it to play, done.
Why is it so crucial that it be done "in real time", which it
really isn't, unless you are listening to the live NPR feed. In the
case of podcasts, *why* would you possible play them via streaming
instead of downloading the publicly accessible file to manipulate
however you chose?
> SteveGS wrote:
>> The code is to: Listen to the audio level for about 10 seconds or
>> so and raise or lower the level in small increments.
Based on what? Do you want a 10 second buffer to continually be
analyzed in real time? From the output of a speaker, no less?
And which level? Peak? Average over...10 seconds? Are you
keeping track of the previous values to make it match? Where is that
stored?
>> It has nothing to do with understanding how to grab podcasts. The
>> system is working very well for that.
OK...then perhaps I/we am/are confused on the limitations of the
program. What does it "grab", *exactly*?
Phil
--
AH#61 Wolf#14 BS#89 bus#1 CCB#1 SENS KOTC#4
philb(a)philb.ca http://philb.ca
