View Full Version : DivX Pro™ Plasma Codec [CoreBurn update]
DigitAl56K
25th November 2004, 01:25
We've just released a new update from the DivX Pro Plasma codec alpha program!
Check out DivX Labs for the CoreBurn download:
http://labs.divx.com/archives/000040.html
IgorC
25th November 2004, 04:42
aparently better than previos alpha version. Keep testing.
but the same problem with virtual dub 1.5.10. When i put on insane mode the window has closed. (1-st npass) other setings by default. 1pass better quality works good
And the files has the different sizes
2-d pass 4900 kb
3-d pass 5260 kb (other pair of files 2pass -2584kb , 3pass 2628 kb)
is it normal?
seems 3pass encoding works good (i have tested only on 780 kbit )
1pass better qual.
2pass insane
3pass insane
1pass -bvn1 780000 -vbv 9708400,6291456,4718592 -pq 7670 -b 3 -nf -quantization=2 -psychovisual=2
2-3pass -bvnn 780000 -vbv 9708400,6291456,4718592 -pq 8610 -nf -quantization=2 -psychovisual=2
Divx decoder hasnt any features to changes deringing, deblocking.
(so i use ffdshow)
in readme file it says
¨¨Post-processing is fixed: Full deblocking, no deringing, no film effect¨¨
nicco
25th November 2004, 14:17
Vdub (1.6.1 or VdubMod 1.5.10) crashes when GMC is enabled!!!:angry:
still a big problem in GUI: when loading the GUI for the 3rd pass settings, b-frames are automatically greyed out to Off (in the previous passes they were on single-b or multiple-b)
nicco
25th November 2004, 14:55
I can not make it work!!!
In Nth passes I get this error: "Video compression error: a codec-specific error ocurred (error code-400)"
of course gmc is off otherwise vdub crashes at the beginnin of the encoding process.
superdump
25th November 2004, 18:27
I experience precisely the same problem, I could not get the previous plasma release nor this one to encode anything at all with the latest CVS release of vdubmod from sourceforge, vdub 1.6.1 and avs2avi 1.39 (I think that's the correct version.) I cannot get it to encode a single thing. When I tried to encode via graphedit, I started it off and it popped up the XviD statistics graph... weird. (I do have XviD installed by the way.) If you need to know, tell me what and I'll try to get the information for you.
nicco
25th November 2004, 18:39
could not get the previous plasma release nor this one to encode anything at all
Tritium had a lot of problems (of course, it was an alpha) but it worked to me.
CoreBurn does not work at all!!
moreover to restore 5.2.1 I had to reinstall it becouse plasma did not uninstalled from codec list!
708145
25th November 2004, 22:05
Are there any estimates about when to expect stable betas or even RCs?
I'd really like to test the codec but currently I still shy away.
bis besser,
Tobias
DigitAl56K
25th November 2004, 23:59
If you open the encoder GUI, hit restore defaults, then immediately try encoding, does it work?
If not give us details about your source (resolution, format), if you're using full recompress, fast recompress, normal recompress, and some info on your system (CPU, OS, Service pack, RAM).
nicco
26th November 2004, 00:40
If you open the encoder GUI, hit restore defaults, then immediately try encoding, does it work?
NO!:scared:
My movie (it is exactly the same I used for tritium tests):
Avisynth:
AVISource("dv-avi,audio=false,pixel_type="yuy2")
trim(3350,4200)
tomsmocomp(0,3,1)
BicubicResize(512,368)
spatialsoften(2,2,4)
converttoyv12()
fast recompress
Winxp SP2
P4 2.8Ghz
512 RAM
superdump
26th November 2004, 03:15
OK, I found that loading the defaults does work and I added more and more options until it crashed. It first crashed when turning on QPel.
My source is 512x384, 25fps YV12. I'm using fast recompress. I'm running a P4 2.8 @ 3.5GHz (easily prime/memtest stable) with Windows XP SP2 and 1GB of RAM.
After further testing it only seems to be when QPel is enabled that it crashes.
DigitAl56K
26th November 2004, 07:56
Try full processing mode, there might be a colorspace issue.
EagleDivX
26th November 2004, 09:49
nicco: Try unchecking "do not prompt with errors and warnings" in the Advanced settings dialog. There's a chance you'll get an error message before the codec bombs out.
- John
nicco
26th November 2004, 10:52
Try full processing mode
Still not work
Try unchecking "do not prompt with errors and warnings"
I still get the same error:
Video compression error: a codec-specific error ocurred (error code-400)
This error occurrs AT THE ENDOF NTH PASSES, single-pass works (with defaults)
Could it be an installation problem?
CruNcher
26th November 2004, 13:59
I have exactly the same problem as nicco tritium worked coreburn doesn't anymore, tried with Vdub 1.5.10.1 and 1.6.1 also with standard settings no chance it displays the same error
Video compression error: a codec-specific error ocurred (error code-400)
looks like a problem with Nth pass
only Single Pass works and their is still the Qpel Crash problem loughable i mean what did you fixed some gui interface things, but not the major problems thats really ridiculous you even killed the normal 1pass/2pass function :P
ok i found the problem looks like you shouldn't delete the DivX folder that's created in C:\ :P
superdump
26th November 2004, 18:54
Originally posted by DigitAl56K
Try full processing mode, there might be a colorspace issue. OK, I tried full processing mode, same problem. I've tried converting the RGB32 and using full processing mode. QPel still causes it to crash. Any more ideas?
mgh
27th November 2004, 03:28
With my Win 98 SE
1. With tritium version had problems in encoding-what I could did not play either in DivX player or Media Player-but surprisingly played perfectly in latest Real Player
2. With the coreburn-no problem whatsoever single pass or 2 pass-sticking to hometheatre profile-and encodes play in DivX player and other players. Single pass encoding-insane quality, two pass-better quality followed by insane quality. Compared to slow setting of earlier versions-the compression is better. I like the visual quality better than older versions of DivX.
nicco
27th November 2004, 11:53
ok i found the problem looks like you shouldn't delete the DivX folder that's created in C:\ :P
is this the solution for (error code-400)?
Do you mean not to change the default divx temp folder in advanced settings?
it seems not work for me
CruNcher
28th November 2004, 10:14
yes it works for me on the encoding start but @ the end last frames i get the error again abd those frames are not in the final encode then, anyway those problems are not really interesting looking @ the picture stability it's still awefull (for 1 year paid research) and that count's not such usability bugs imo.
MacAddict
28th November 2004, 16:37
@CruNcher
Thats very disappointing to hear. Is the image still soft a great deal compared to XviD?
DigitAl56K
28th November 2004, 21:56
Ok guys, calm down :)
There's obviously still some kinks in the code preventing correct operation of the encoder on some boxes. Don't start judging the codec until you actually have something that works properly in your hands.
P.S. Did anyone try duct tape? It fixes almost anything.
superdump
1st December 2004, 11:35
Originally posted by DigitAl56K
Ok guys, calm down :)
There's obviously still some kinks in the code preventing correct operation of the encoder on some boxes. Don't start judging the codec until you actually have something that works properly in your hands.
P.S. Did anyone try duct tape? It fixes almost anything. I'm fresh out of duct tape I'm afraid. I'll try plasma again with the next release.
SeeMoreDigital
1st December 2004, 11:50
I have to agree with superdump. Why do your beta's have so many errors?
Apart from the GUI, how much will this proposed codec release differ from previous releases... because I really can't see any visual differences. Even when using the "insane" setting over 2 passes!
Cheers
obieobieobie
1st December 2004, 18:16
It's not a beta. It's an alpha. Alpha equals more bugs, right? :)
SeeMoreDigital
1st December 2004, 18:32
Originally posted by obieobieobie
It's not a beta. It's an alpha. Alpha equals more bugs, right? :) Good point!
If DivX wants to call it an "alpha" release, it's an "alpha" release.
Which begs the question. Which is supposed to contain less bugs "Alpha" or "Beta"?
Cheers
708145
1st December 2004, 18:37
alpha: very early version; usually features fixed
beta: almost all features stable; some are not
release candidate: all features are *expected* to be stable
bis besser,
Tobias
superdump
2nd December 2004, 01:12
Alphas are usually internal as well, but I guess DivX is so popular they need to test it on some of the masses anyway before going beta. Maybe. :)
LordRPI
2nd December 2004, 02:16
I think it's an excuse to actually let me test it. Although, we all pretty much use similar setups here, so I think that's why a lot of the stuff works on this end.
obieobieobie
2nd December 2004, 03:50
Originally posted by SeeMoreDigital
Good point!
If DivX wants to call it an "alpha" release, it's an "alpha" release.
Which begs the question. Which is supposed to contain less bugs "Alpha" or "Beta"?
Cheers
Logically, alpha is an eariler version than beta. Some like to talk about pre-alphas, pre-betas, release candidates, public betas and other cool terms, but the crux of the matter is that any version prior to the proper released version is a test version where there should be expected to be bugs.
Or something. :)
Sharktooth
2nd December 2004, 14:26
Well i think DXN has made a nice move this time, letting users test one of their next codecs before they have a "feature freezed" product.
Of course if they keep doing that they won't waste time re-releasing the "fixed" versions of their products (5.1 -> 5.11, 5.2 -> 5.21 ...)
Doom9
4th December 2004, 02:21
bleh.. still craps out immediately when I turn on qpel during the first pass.
DigitAl56K
4th December 2004, 06:16
We're working on that :)
CruNcher
4th December 2004, 11:46
More important is the Frame Stability please try to enhance this
dragongodz
4th December 2004, 12:20
no more important is getting the settings actually up in any program ohther than ones based on VDub. try it with something that brings up the standard windows codec slection(such as Tmpgenc's avi output) and watch the settings button disable. now THATS a major bug.
SeeMoreDigital
4th December 2004, 12:38
Originally posted by Sharktooth
Well i think DXN has made a nice move this time, letting users test one of their next codecs before they have a "feature freezed" product.
Of course if they keep doing that they won't waste time re-releasing the "fixed" versions of their products (5.1 -> 5.11, 5.2 -> 5.21 ...) Agreed...
I remember testing DXN's, Manihi, Kaukura, Kauehi codecs. And from what I remember each worked very well - in their own way!
Originally posted by CruNcher
More important is the Frame Stability please try to enhance thisAbsolutely!
This is where, WMV, Real and VP6 score well over Mpeg4, and DivX in particular. And if you're into encoding using 1:1 image pixel frame sizes (like me), the frames stability can be quite "off putting", especially if your attention is drawn to whats going on in the frames background.
Cheers
Sharktooth
4th December 2004, 14:21
Well, now that ahead has released Recode 2.2 it's time for DXN to move to AVC or they will be too late...
mgh
13th December 2004, 17:04
Am very happy with the speed and quality of encoding.
But pl. put back full post processing in your directshow decoder-at lower kbps there is heavy blockiness-using the 5.2.1 decoder the same vids play back well without blockiness.
Do not understand as deblocking is supposed to be enabled in the directshow decoder.
Sharktooth
27th December 2004, 13:34
Any updates?
Doom9
27th December 2004, 17:29
I love to keep people in suspense.. so keep checking my news in the next few days ;)
IgorC
27th December 2004, 22:48
when i put 3 jobs in virtual dub to do 3 pass Divx, before to do each pass i had to press enter. This message :rolleyes: ¨this is alpha version ......¨. There isn´t still any new beta. well
i hope new beta will realese untill 31 of diciembre, 23:59 :p
LordRPI
28th December 2004, 19:59
Digit was mentioning something about putting a time limit on the alpha/beta codecs due to the fact that people were still downloading the old 5.1 betas.
Keep on checking for the a new release though.
Doom9
29th December 2004, 02:01
you might want to check out the codec comparison to see what's coming your way DivX wise ;)
nicco
29th December 2004, 10:08
you might want to check out the codec comparison to see what's coming your way DivX wise
So, from 5.2 to plasma alpha to... "fusion 5.9"!! What's happening here? Is there something I missed on the way? Or it's just a new year mistery? :rolleyes:
LordRPI
29th December 2004, 17:25
Numbers don't mean much unless it's a Eurpean or Japanese car. Some of the guys over here are getting the American bug naming products like Americans, ie a cool name and a random number attatched to it.
Sharktooth
29th December 2004, 17:33
LOL :) that's so freaking funny:)
BTW, i stopped here to ask you why you still want to update your ASP codec when AVC is so "superior".
Once i read you were working on h.264 and the development was going pretty straight (divx 6?). I thought you should have been the first in the world with a commercial AVC codec but then no more news on that...
What's happened?
LordRPI
29th December 2004, 18:19
No really, this is something I can't comment on largely because I don't work in that department. I'm just a janitor.
LordRPI
30th December 2004, 02:04
BTW, I wasn't serious about being a janitor.
Sharktooth
30th December 2004, 16:10
doh!
IgorC
30th December 2004, 17:09
i saw a images of doom´9 comparing Xvid Divx 3ivx. Divx is so smooth, it seems like 5.9 is optimized for PSNR test and not for visual appereance. Xvid 1.1 is still better. there are a lot of post on divx.com that doom9´s is place of birthday of XVID. But I´m not a fan of Divx neither Xvid or 3vix , and i still beleive to my eyes. XVID is better , sorry guys.
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.