View Full Version : open source H.264 or MPEG4 encoder ?
sherif_hanno
18th February 2007, 01:22
Hi all
I'm totally new to video world & extremely need help
I'm making a small video streaming project
I have the mainconceptV2 encoder which is by the way gr8
but I need an open source encoder
or a program that I can control it from the command line
any tip will be helpful
Thx in advance :cool:
Theliel
18th February 2007, 01:35
x264 is the best open source h264 encoder and probably it'll be the best encoder for all.
http://www.x264.nl/
sherif_hanno
18th February 2007, 21:41
x264 is the best open source h264 encoder and probably it'll be the best encoder for all.
http://www.x264.nl/
:thanks: alot...it was really helpful
but I'm little more greedy
another question
is there open source code written in JAVA ?
bob0r
18th February 2007, 21:58
x264 is the best open source h264 encoder and probably it'll be the best encoder for all.
http://www.x264.nl/
Why www. ?
Arg... i have to forward www. to some work unsafe website i think :angry:
Theliel
18th February 2007, 22:16
i dont belive this, sorry :(. always you could translate entire source code to java :S
sillKotscha
18th February 2007, 22:22
Why www. ?
because even without it you're still a part of the world wide web ;)
live with the fact - it will always be the www ...
DeathTheSheep
19th February 2007, 01:53
Argh, very true; sometimes domains registered under straight http://something.yea/ have problems when working with www and vise versa. It's CRAZY!
ChronoCross
19th February 2007, 23:11
i dont belive this, sorry :(. always you could translate entire source code to java :S
hahaha. you'd only take a 5000000000% speed loss.
not to mention there is no guarantee that all of it could be properly done in java.
foxyshadis
20th February 2007, 01:35
Not that slow, but if you take the speed of x264 with --no-asm, and half that, you're probably in the ballpark. Which on i386 is going to be a huge drop.
It could definitely be done just by a very long, very tedious code conversion - the trickiest parts are the function pointers, and they're almost exclusively used for asm optimization, so they can be ignored. Starting from the JM probably wouldn't be any easier and definitely wouldn't be as high quality (without taking another 10x speed hit on esa me). The various allocations, pointer/arrays, etc could be redone with java-native syntax.
ChronoCross
20th February 2007, 01:56
yeah that's the main problem. plus you'd want to design the code to be java class specific and use the correct heirarchy if you want it to be done right. Not worth it even for educational purposes.
Sirber
20th February 2007, 13:33
They can do anything for educational purposes... mostly if it has no uses. ;)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.