AutOKtv, specifications

From AutOKwiki

(written by toqer) In autOKtv, a primer I discussed the various aspects of getting media to the web. The entire key is network title updating, but no software other than shoutcast supports this. Shoutcast is great for live video, and the entire system would still support it. The goal of autOKtv would be to give a better option for recording video destined for other formats.

There are a lot of hardware devices that can do compression on the fly. The original DV video camera at the boo did DV compression. The video blaster box can compress to high bitrate mp4 video.This way I could just use a firewire splitter and 2 machines to continue broadcasting live with a high end machine while another low end machine writes out the high quality files.

This is what the autOKtv system would consist of...

1. a webserver that listens for shoutcast style updates
2. keypress emulation Scripting System

Take a look at the various video recording tools out there. Most of them have the same menu items.

File Edit Capture Help

Now I press some keys alt-f a

What did I just do? Most of the time that keypress would activate file>save as. It could have been followed up with the newly updated title.We could create different keypresses presets for different applications. It would be pretty limitless. Everything from adobe premiere to MPC to virtualdub to whatever the heck the user wants to use for recording. Everything could be supported.

What's needed is a simple webserver, maybe something cut out of autOKdj or based on original jnetlib that would sit there and launch keypresses whenever there is a title update recording machine.

We can harness the ways these different programs record as well as setup other machines on the network to perform tasks besides live recording. The user will require some knowledge of windows networking and their application.

http://someserver:port/admin.cgi?mode=keypress&title=titlegoeshere&preset=keypresspresetname<

mode=keypress
new addition to the server, launches keypresses)

title=titlegoeshere same as a shoutcast title, it can be used in the keypress preset name as $sc_title

preset=keypresspresetname This tells the server which keypress preset file to use.

Preset file format

Plain text format, plain english format. The file will consist of a header which describes what window the keypresses should be going to, and which program to launch if the window isn't found

Window=HWND_window_title program=path_to_some_program

The header would be followed by the actual keypresses. Each keypress is seperated by commas. for example, if I wanted to save a file as "toqer.txt"

alt-f,a,t,o,q,e,r,.,t,x,t

Uhhm, lookin at that makes me glad my name doesn't start with a g :/ continueing on though..

The preset interpeter would have to look for "alt-" combinations, ctrl combinations, and special keys like f1-f2-f3 and so on...

autOKdj Mods

Since we're managing a bunch of servers, why not make it some snazzy ml view? Have a big page with plenty of real estate to enter in server details. Each server could be setup for a certain task.

comments suggestions welcome :)