[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[OpenDivX] General Development Discussion - All Projects -> OpenDivX Daily Forums Digest





Topic:		OpenDivx on Solaris
Author:		gruel
Posted:		 2001-03-28 05:04
------------------------------------------------------------------------
--------
My problem is solved... my mistake.
The results for one example frame (I-frame)
640x480, 1200 bps, no postprocessing

Plattforms:

AMD K6, 200 Mhz (no MMX compiled in); running Linux
Intel PII, 450 Mhz (no MMX compiled in); running Linux
Sun Ultra 10, 440 MHz UltraSPARC; running Solaris
SGI Origin, 180MHz MIPS R10000 CPU; running IRIX

Results: abs.  (rel.: fps at 1GHz)

K6 encoding:  1.35s    ( 3.7)
K6 decoding:  0.30s    (16.7)

PII encoding: 0.60s    ( 3.7)
PII decoding: 0.13s    (17.1)

SUN encoding: 0.45s    ( 5.1)
SUN decoding: 0.066s   (33.9)

IRIX enc.   : 0.45s    (12.3)
IRIX dec.   : 0.078s   (71.2)

chl 


Topic:		DVD movies
Author:		Henry
Posted:		 2001-03-27 23:16
------------------------------------------------------------------------
--------
I tried www.doom9.org. I read it but I cannot understand computer talk.
All I want to know is "how to burn DVD movies on to a CD. This what i
have, a DVD player, a 12x burner and a Easy cd creator software. What
else do i need and what is my starting point.Do I need to download a
software or a code.What is the first thing I need to do and what after
that.?


Topic:		DVD movies
Author:		Infinitegoof
Posted:		 2001-03-28 01:00
------------------------------------------------------------------------
--------
hey man, listen, you can't burn DVD's onto cd without changing the
format. You see a dvd works differently than a cd. I suggest you try
ripping your disc to divx format. Go to www.mydivx.com to learn all
about it - it ain't that hard, you'll just have to do a bit of reading
before doing it. B-Dogg


Topic:		OpenDivx on Solaris
Author:		eagle
Posted:		 2001-03-28 06:12
------------------------------------------------------------------------
--------
Nice one, gruel, we have SUN Solaris support   

I remember now, the UltraSparc multimedia instruction set is called
"VIS".  VIS is the Sun equivalent of MMX and Altivec.  It could
accelerate encode/decode even more.


Topic:		OpenDivx on Solaris
Author:		gruel
Posted:		 2001-03-28 06:26
------------------------------------------------------------------------
--------
Quote:
On 2001-03-28 06:12, eagle wrote:
Nice one, gruel, we have SUN Solaris support :D :D :D

Not to forget IRIX :-)

Quote:
I remember now, the UltraSparc multimedia instruction set is called
"VIS".  VIS is the Sun equivalent of MMX and Altivec.  It could
accelerate encode/decode even more.

You are right...
http://www.sun.com/sparc/vis/

or since nobody has to invent the wheel more than twice: 

http://www.sun.com/sparc/vis/mediaLib.html

Has anyone used this before (not that I would expect so...)


Topic:		OpenDivx on Solaris
Author:		gruel
Posted:		 2001-03-28 07:28
------------------------------------------------------------------------
--------
Quote:
I remember now, the UltraSparc multimedia instruction set is called
"VIS".  VIS is the Sun equivalent of MMX and Altivec.  It
could accelerate encode/decode even more.

Wow! I just replaced the fdct_enc routine by the correspondig
VIS-enhanced  SUNmedialib-routine and performance almost doubled. (0.28s
in encoding). I guess SUN could become the first plattform for
realtime-encoding.

There might of course be copyright problems with the library. Then
somebody has to get down to VIS-assembler... but not me ;-)


Topic:		OpenDivx on Solaris
Author:		eagle
Posted:		 2001-03-28 11:06
------------------------------------------------------------------------
--------
WOW, 0.28 seconds, is that for encoding a I-VOP (keyframe) or an average
over several frames including both I's and P's?  If it's only one
I-frame, then encore may not be doing all it's slow MC/ME work.

I can feel a ./decore/vis and ./encore/vis directory coming along !  Any
VIS gurus out there?!?!

When we finally get around to scrapping all the unecessary 16-bit images
in encore, then encore will be faster on all platforms (reduces memory
bandwidth needed).


Topic:		Divx & ATI
Author:		malocite
Posted:		 2001-03-28 12:10
------------------------------------------------------------------------
--------
Ok, I have a problem,  and I have NO idea on how to fix it.  Everytime,
without fail when I compress using divx I have a problem where colours
go all nuts.  They go to purple, then weird green, then normal, then
back again.

Any idea on why?  It has done this when I capture using UYVY (the only
one I can use)  It has done this when I capture directly to Divx, or
when I capture Huffy then compress to divx.

Any ideas on WHY and how to fix this?

I have an ATI Radeon VIVO


Topic:		OpenDivx on Solaris
Author:		gruel
Posted:		 2001-03-28 17:57
------------------------------------------------------------------------
--------
Quote:
On 2001-03-28 15:58, eagle wrote:
Sorry, I didn't mean a forum, I meant a subdirectory in the source code
tree for your VIS optimised files.  What we're intending to do with all
the different optimisations is to keep generic (and hopefully readable)
C code in the <!-- BBCode Start --><I>encore</I><!-- BBCode End -->
directory.  The optimised versions of the same source files go in <!--
BBCode Start --><I>encore/intel_mmx</I><!-- BBCode End -->, <!-- BBCode
Start --><I>encore/altivec</I><!-- BBCode End -->, <!-- BBCode Start
--><I>encore/arm</I><!-- BBCode End -->, <!-- BBCode Start
--><I>encore/trimedia</I><!-- BBCode End -->, <!-- BBCode Start
--><I>encore/vis</I><!-- BBCode End -->, etc. etc.... 

Yaeh, sure... I just meant, that nobody was interested in such a forum,
so maybe there is just nobody interested in SUN-stuff. And in particular
no VIS-guru. 
Also my changes are not VIS, but a few simple calls to the VIS-optimized
SUN medialibrary which is commercial though free. 
About MMX: When I looked into the source, to see where the flag for
MMX-support is checked, I found e.g. the lines

#ifndef _MMX_ 
fcdt_enc(tmp);
#else
fcdt_mmx(tmp);
#endif

THAT's surely not a flexible way to include other platform-specific
versions. 


Topic:		OpenDivx on Solaris
Author:		gruel
Posted:		 2001-03-28 15:53
------------------------------------------------------------------------
--------
Quote:
On 2001-03-28 11:06, eagle wrote:
WOW, 0.28 seconds, is that for encoding a I-VOP (keyframe) or an average
over several frames including both I's and P's?  If it's only one
I-frame, then encore may not be doing all it's slow MC/ME work.

Just a single keyframe. The main work is the fdct. But the SUN
Videolibrary has support for Motion Estimation as well; I'll look into
that next. 

Quote:
I can feel a ./decore/vis and ./encore/vis directory coming along 8)!
Any VIS gurus out there?!?!

I don't think so. I asked for a general UNIX forum instead of just Linux
some time ago and didn't get a single reply... 
So maybe it's too early for that. 
But in any way the system of using/nonusing MMX should be changed to be
more flexible for other architectures. 


Topic:		OpenDivx on Solaris
Author:		eagle
Posted:		 2001-03-28 15:58
------------------------------------------------------------------------
--------
Sorry, I didn't mean a forum, I meant a subdirectory in the source code
tree for your VIS optimised files.  What we're intending to do with all
the different optimisations is to keep generic (and hopefully readable)
C code in the <!-- BBCode Start --><I>encore</I><!-- BBCode End -->
directory.  The optimised versions of the same source files go in <!--
BBCode Start --><I>encore/intel_mmx</I><!-- BBCode End -->, <!-- BBCode
Start --><I>encore/altivec</I><!-- BBCode End -->, <!-- BBCode Start
--><I>encore/arm</I><!-- BBCode End -->, <!-- BBCode Start
--><I>encore/trimedia</I><!-- BBCode End -->, <!-- BBCode Start
--><I>encore/vis</I><!-- BBCode End -->, etc. etc.... 


Topic:		OpenDivx on Solaris
Author:		eagle
Posted:		 2001-03-28 18:37
------------------------------------------------------------------------
--------
Agreed.  We can't have a whole list of #ifdef's for each architecture!
So we should try to standardise the function names and rely on the
makefile/project file to select the appropriate version.


_______________________________________________
OpenDivX mailing list
[email protected]
http://lists.projectmayo.com/mailman/listinfo/opendivx


Reply To Poster

Local References / HOW-TO / FAQs