Author
3D1on
A DirectStreamCopy Presentation
Howard Stern Show Opera
From satelite to... on-line streaming?
WTF!
HOWARD STERN IS BULLSHIT
What you have here is greatly the work of Dan The Song Parody Man. The rest of the show is basically highly egotistical in nature with interviews, performances, and spectacles.
The Opera:
106663863bytes
137 object files (reduced from 169 after sorting)
playlist length: 01:47:27 (high accuracy, low precision)
working average length per cut: 105.2seconds
number of subdirectories: 7
maximum number of cuts per directory: 78
largest sample: 305seconds, 6960264bytes
smallest sample: 2133millseconds, 36389bytes
samplerate range: 8kHz-24kHz
Processing
0) accumulated content
1) stored content
2) cut
3) tag cuts for contents *
4) compress cuts
5) backup of cuts
6) edit cuts (search (using tags! *), mark ends, delete)
7) adjust each cut for rms **
8) compress and backup finals
9) assemble and compile into single object files
overall time frame: 25days
trim time frame: 0704 22:50 to 0705
rough memory load: 1.3gigabytes ***
* this area of (keeping track of what makes up individual cuts) is increasingly an area of use under development for me in my work now - so much so it is almost a job all on its own worthy of its own, unique artistry!
** i decided to leave out this step (basically it just puts each clip at the same volume for the listener, but it requires processing each cut manually and in this case is making mostly minor changes that i would just as sooner leave alone anyways so as to provide clarity to the listener that this is content i have accumulated from encodings on the internet - i did not encode any of this content!) - please note, the files have been thusly editted, only globally instead of each cut (the significance of which might be a lengthy explanation)
*** obviously, this far exceeds what is needed and is mostly comprised of duplication
Note: the trick here, really, was 2) - these are very large files that can require 4gigabytes of memory for any editing. Swapping to harddisk all of this information could take days. The easiest way out is to utilize the full-duplex capabilities availble in most sound cards today. Next, one program plays the file.
This becomes problematic, thus the numerous points of processing. Basically, without visualizing the audio as a 'wave' (like on an EKG), one needs an audio player with good controls (i.e. single stroke keyboard shortcuts). One concern here is that kind of activity routinely freezes computers.
Visualization of the audio itself inside of an editor is the best way. But that takes a lot of memory.
My work was made easier by taking the 5 hour audio files and using a simple object file utility, called a splitter. The only, very minor, complication that arises here (aside from the fact that it is a bit of an end-run around the operating system and its "extensions" guides) is when you have a clip you what that has been spliced right down the middle. Digitally, this is no problem. So file-splitting was key to this fun as heck cut.
One other point. I am moving from a software-only approach to editting and into one that takes more advantage of capabilities inherent in the technology. It comes down to point 9).
What comes down to is that I normally will take all of my cuts and, one by one, copy and insert them into one, single audio file. This file I can store as I go, which has always been helpful in dealing with computer crashes, among a host of other benefits - such as using point 7) when I see fit or just taking some licence in general with the audio clip before or during insertion into the main audio file.
How is this changing? More and more, I take the easy road! I simply take my clips (which is not always challenging, at least numerically - the disordered state data can take is usually the greater challenge), stick it all into an ordered playlist, and record from the playlist player into the audio editor. Simple!
This is more what I am used to from my years with analogue. All you need, as any engineer will tell you: good metres! You need to be able to SEE when you are peaking. The fun part (and I do think this can be fun - after all, the final product 'does all the work for you...' forever!) is that it forces you to be very intuitive with the _content_ of what you are doing. Gasp! Making adjustments on the fly is truly the closest an audio geek can get to transforming these wastoid machines into veritable musical instruments!!!
2 Howard Stern Opera - 098-169 144megabytes (native)
1 Howard Stern Opera - 050-097 145megabytes
0 Howard Stern Opera - 000-049 147megabytes
p.s. I barely detected one error during assembly. So there is a remote chance that a few seconds here and there should not have been included.
p.p.s. These notes are incomplete.