Hello,

Thanks for your reply, I will answer them in parts.

Douglas.Arellanes@mdlf.org wrote:
> - When the voice tracks are recorded, I'm assuming they'll go to the
> client's /tmp directory, or will they reside in RAM until the file is
> uploaded?
Maybe someone already noticed I'm exploring the possibilities to make
Firefox natively work with sound.
https://bugzilla.mozilla.org/show_bug.cgi?id=305567

Until then it will depend on the used audiolibrary, to play save storing
directly to disk sound the best way around. This is one of the major
problems with the current system it cannot be selected and literally a
COMPLETE show is lost when something goes wrong.

I think it should be selectable an audioterminal has normally enough
memory to compress and send, but the diskspace is on the otherside of
the networkline thus makes it 'relatively' slow on a GigE interface

> - Will all voice tracks be uploaded at once in a group, or will they go
> up individually?
Background scheduling for DSL/Cable users was talked about, but this
should be selectable too. Like the download function. For example you
could start right away ones you download the first samples. And don't
need to wait for songs last in your playlist.

> - It sounds like you're not only going to need the client app, but
> something that interfaces with the playlist editing functions in the
> scheduler. Maybe a more elaborate version of the 'reorder playlist'
> feature in the HTML UI? Regardless, the files will still have to be
> uploaded into the StorageServer, right?
This is correct. Although placing (voice-)track between tracks should
not be too hard in a DOM way. What worries me is the fade level and time
(and howto put such thing in a playlist).

> - Based on my experience - and even watching Robert Klajn work on a set
> of jingles we're including on the LiveSupport install/live CD - it seems
> like a lot of effects are applied to announcers' voices. Wouldn't it be
> easier to use something like Audacity, which allows for a wide number of
> effects to be applied to a sound file, for the recording and manipulation?
Wow This is an ongoing discussion at our radio station, currently
there is a hardware Behringer voiceprocessor and a no-name effectbox
between the mic and mixer. Though it is prefered to not alter the voice
too much because *all* voice is (live-)processed again before it is
broadcast.

But imagine this, our unpayed personal need to record about 5 hours of
program for a week. Do you really think it works fast to record stuff in
Audacity? I did it before and I can honestly say, it doesn't, because
recording is easy but managing the MP3/Ogg files out of it doesn't.


> - How will talent know the duration each spoken segment has to be?
Can be unlimited, the current system even paste the end of the intro
seamlessly to the end of the voice track.
_______________________________________________________
| outro | | intro |
music | s. voice | voice | e. voice | music
_______________|__________|_______|__________|_________

So basically it makes a bad DJ a good one

This image makes me think, about compression of the 'voice' part But
I will elaborate on that later.

> - How should metadata be handled for each spoken segment, assuming
> they're going to be individual entries in the StorageServer? The two
> obvious options seem flawed: Either the individual spoken segments
> require individual metadata, which is a pain, or the group of spoken
> segments is treated as its own object, which is very inadequate for
> later retrieval/use
The current software manage it by time and because their data is so
*@#$^&&# stupid stored, it cannot be used to repeat programs. I think
the best thing would be save the following metadata:

Track1 / Voice Artist / Track2

And when explicit content is used a small tag.



I hope I made it a bit clear,


Stefan

------------------------------------------
Posted to Phorum via PhorumMail