That’s all to have HandBrakeCLI compiled.

The GUI version still requires some work. I will update the post then.

create index a1 on tfm (insert_date);

And the page load time decreased magically from 2.3s to 22ms . This is a reminder to power of myql indexes in tfm linux or any other linux of your choice.

What tools will you need ? Well that depends on two main things: quality of the broadcast and number of people that will watch the live event. Let’s start with a high quality and lots of people that will watch the event. For this you will need:

A very good video and audio signal for the encoder . From my experience there are several ways to do it:

• a professional camera with firewire works best or even better if you can rent a video mixer and use multiple cameras.
• If you have SDI signal you can use Osprey HD capture cards

An encoder PC ( or laptop ) with firewire interface.

• You will need a fast processor and a fast hardisk in it if you want to record the event for later use.
• Install Adobe Flash Live Encoder (Adobe FMLE) . At the time i write this article the latest version is 3.2.
• Adobe FMLE comes in 2 flavors: Windows version and Mac OSX version

A CDN ( Akamai , Edgecast, Level 3 Communications, etc ) or if you intend to broadcast yourself and intend do to this for profit you can build you own CDN ( this will be covered in another article )

If you buy services from a CDN you will have to pay on how much bandwidth your viewers will consume. And that can be expensive

If you have built your own CDN  you can achieve 20.000 simultaneous viewers with 1 core and 5 edge servers.

Setting up Adobe FMLE

Adobe FMLE settings part1

Important video parameters are: Format to be H264 , framerate is also important ( i choose 15 or 25 ) , input video size should ALWAYS be greater or at least equal to the output video size.

For audio encoding . This is a little bit tricky . Adobe FMLE does not support AAC encoding by itself . You will need a special plugin for that.

And if you will target Iphone / Ipad and other mobile devices you will also need this settings:

Adobe FMLE settings part 2

• New Microsoft Kinect driver
• updated graphics drivers
• cleancache support
• optimizations for Intel and AMD processors

But mainly this new numbering will force companies to keep their products close to the latest kernels. Right now there are many companies that trumpet they support 2.6 kernel and in fact they are supporting the old 2.6.26 or worse version.

Also this move celebrates Linux entering in it’s third decade of life.

Well . I can say that i’m slightly older than linux . But not with much.


root@tfm33: /Space/server/_wks/trunk# svn commit
svn: Commit failed (details follow):
svn: Aborting commit: '/Space/server/_wks/trunk/libmp3lame' remains in conflict


An no matter what i tried it stayed in conflict. doing some google-ing i found out that the fix is quite simple:


svn resolved /Space/server/_wks/trunk/libmp3lame


1) Documentation (lack of) – The documentation itself should be inside the kernel itself.

2) Need for new blood . Some of the original developers are getting old.

3) Keeping Independent thinkers is very important.

4) Fixing scheduler is around the corner. RTT will be merged into kernel.

5) Android is forking a part of kernel. There will be tries to merge codes between Google and Linux Kernel.

6) A person ( or persons ) are needed to reduce the kernel bloat ( kernel foot print )

Best way to do this is like this:

• Download OA firmware, ILO firmware and rombios ISO image .
• From the web interface update ILO firmware.
• Create an ILO user and enable ssh .
• Activate ILO advanced license
• Open a terminal and ssh to ilo
• issue the following command from ilo command line:

vm cdrom insert http://192.168.1.1/ROMPAQINTEL.iso

vm cdrom connect
power on

• From web browser open an ilo remote console to server and power it off.
• After the server gracefully powers off issue a “power on” command from ILO
• Switch to remote console and complete the update
• After update is complete issue the following commands from ILO

power off
vm cdrom eject
power on

Enjoy updating.

3) A quick search on the net on how to set this phone up ( in the box I found no documentation so i guess google il my friend tonight ) revealed that i need to set up a tftp server to serve a software for the phone.  But to get the software i will need a Cisco account.

Great ( NOT ) … In order to download from Cisco you will need: “Have a valid Technical Support Services Agreement”

Now i have to wait a bit until my friend who has the account will download it for me. Time to get something to eat. This is going to be a loooooooong night.

Got the file. One big zip unpacked in tftp directory. Created a file named: XMLDefault.cnf.xml

4) got the files. DHCP server updated …

class "cisco7945"
{
match if substring (option vendor-class-identifier,0,32) = "Cisco Systems, Inc. IP Phone CP-";    #<----Matches first 32 characters
option tftp-server-name "172.17.0.1";
}

5) Press # while plugin the power and then “123456789*0#” to enter the upgrade sequence.

6) At this point the phone will request from tftp a file named : term45.default.loads

7) The phone is quite bricked. Requesting something via UPNP and there you go … another brick in the wall.

After 1 day of intense internet  searching  i found out that SIP45.8-5-2S was the the one firmware to go with. Worked like a charm.The firmware loaded as expected so the phone is now SIP.

9) Time to make it talk to yate. This is much more difficult than i expected. I have a small yate instalation here and usually i’m connecting to it with Xten clients .I added a number and a password for cisco phone ( from freesentral ) but at this point i’m stuck at registering. It doesn’t wat to register to yate.

I guess it will be at least another day of searching.

In  /etc/sysconfig/network-devices directory  create a directory named ifconfig.bond0 with the following content:

ONBOOT=yes
ONHOPLUG=yes
SERVICE=ipv4-bonding
IP=192.168.1.1
PREFIX=24
BROADCAST=192.168.1.255
CHECK_LINK=no
BONDING_SLAVES="eth1 eth2"
BONDING_MODE=4
BONDING_MII_DELAY=100