Having problems with message search?
The container was able to hold/reference as many media files as you wanted.
There was no limit. It basically created a self-contained "web" since it could use html, images, audio, video, text files and even other .box files inside of itself (packages within packages) which you could hyperlink to and create more complex environments. Of course the .box file size would increase with each additional item added to it.
Throttlebox had good success back then, basically sigining deals with record labels to create custom box files for madonna and other artists. I was a driving force to get the technology into a cross-compatible state and some work began on a Java version. But not quickly enough and Throttlebox became irrelevent in the after-effects of Napsterization.
Obviously, the underlying idea of having these media wraps has always been important and I personally have had great interest in the topic for a long time. I lost interest for a while when my focus turned onto Open Media and just making web apps work better instead... or settling for Flash usage. But as this discussion makes clear, media wrapping is still very relevant... not for DRM but for logical organizationa nd presentation of works.
sull
On 11/27/06, Lucas Gonze <lucas.gonze@...> wrote:
On 11/26/06, sull <sulleleven@...> wrote:
> Back in 2000ish, i worked with a technology called Throttlebox which was a media wrapper (executable) that played .box files which contained various media formats and presentation data. A player was required to run these .box files.
Hey sull -- did these container files contain more than one format of
the same underlying song?
-L
--
Sull
http://vlogdir.com (a project)
http://SpreadTheMedia.org (my blog)
http://interdigitate.com (otherly)
Offline 
Send Email
