View Full Version : DVX: Most important new feature
stax76
11th June 2003, 16:16
same as the AviSynth topic, which feature do you
think would be most important?
ChristianHJW
12th June 2003, 15:22
Lo Dolemite,
i was teaching my bros on your tool, and he made 4 rips meanwhile into .mkv format, and i liked the quality a lot, plus filesize was extremely precise ;) ...
My wish :
Adding a function to encode without resizing in AVISynth, just cropping but following a mod 4 or mod 8 rule ( a few lines cropping into the picture, who cares ), and then automatically set the AR in the MKV file ( according to the DVD AR ) by using mkvmerger.exe to remux the mkv with the --aspect-ratio flag ;) ....
stax76
13th June 2003, 02:11
plus filesize was extremely precise
it still uses the ogm overhead code ;)
Adding a function to encode without resizing in AVISynth, just cropping but following a mod 4 or mod 8 rule ( a few lines cropping into the picture, who cares ), and then automatically set the AR in the MKV file
I made a few changes and wrote a plugin to execute
mkvmerge. You can compile the plugin as followed:
Extras -> Plugin Editor
File -> Open -> open the file MatroskaARFlag.vb
Language -> VB
File -> Compile
After you restart DVX you can read a short manual
in the settings dialog in the plugin tab and in the
program paths tab you can specify the mkvmerge path
I don't have cygwin and couldn't test it but you
can find the commandline in the logfile if it don't
work
dowload it here
http://home.tiscalinet.de/pva2divx/dvx_test.rar
Kent Wang
11th July 2003, 20:16
Whoa, first time I've seen this thing. Looks cool. This is supposed to replace Gordian Knot for Xvid use, right? Who here uses DVX instead of Gordian Knot? Hope I'm not hijacking the thread.
I waited a while to post here, because I don't want to come off as overally critizing and not being thankful. :)
I voted for other.
1. Bugs fix(too bad you can't reproduce the bugs that some users including myself reported), especailly it random crashes.
2. Better compression test values with b-frame and xvid. Right now the compression range is +-15% difference(on some film) while doing a 5% compression test, jonny's tool seems to give the more accurate results, maybe he can provide some hints.
3. Better support for automation. Something like Robot4Rip.
- Auto force film with a threshold of 95%(user define).
- Auto rip subtitle then winrare then deleted the subtitle file.
Thanks for your great tool.
Friendly competition is always good. :)
jernst
12th July 2003, 22:05
- Auto rip subtitle then winrare then deleted the subtitle file.
Subtitle ripper plugin for DVX just do that; did you try it ?
This is supposed to replace Gordian Knot for Xvid use, right? Who here uses DVX instead of Gordian Knot?
DVX doesn't do only XviD encodes but also DivX and others (like VP3). Since I started to use DVX (because Gordian Knot wasn't being actively developped at that time anymore) I stopped to use Gordian Knot and never regreted it; but this is only a matter of personal taste.
--------------
Back to this thread:
I wish that problems that some people encounter will be fixed by Dolemite soon (if you have some, please post on DVX board) and that we can provide a better help with well made guides (we have to finish what we started with the help file).
Originally posted by jernst
Subtitle ripper plugin for DVX just do that; did you try it ?
Didn't work last time I tried it. The usual path problem that has being repeatly reported in the DVX board.
stax76
13th July 2003, 19:22
This is supposed to replace Gordian Knot for Xvid use, right?
I was hoping it would but unfortunately it didn't (GK source was released, people refuse to install .NET etc.)
Who here uses DVX instead of Gordian Knot?
according to the post counts of GK and DVX not many
too bad you can't reproduce the bugs that some users including myself reported
if you post (maybe more precise) your bug report again, I'll try again. Some bugs are not easy to fix, occur only on very few systems etc. DVX works stable here
Better compression test values with b-frame and xvid
unfortunately I don't understand what's all this about, even after reading all the topics. I don't understand why to make a difference between codecs and codec settings. The DVX comptest is a matter of 3 lines code, using file size, frame count and the resolution, works pretty well for me using XviD at 75%
@all
most votes are on AviSynth filters, maybe somebody can help us working on the filter descriptions, DVX incl. a editor (Extras -> AviSynth filter editor) to edit and add filters. Usually I use quite simple (5 lines) scripts so I'm not very motivated for this task
JohnMK
14th July 2003, 00:08
I use DVX . . . if that means anything. :)
Originally posted by Dolemite
if you post (maybe more precise) your bug report again, I'll try again. Some bugs are not easy to fix, occur only on very few systems etc. DVX works stable here
unfortunately I don't understand what's all this about, even after reading all the topics. I don't understand why to make a difference between codecs and codec settings. The DVX comptest is a matter of 3 lines code, using file size, frame count and the resolution, works pretty well for me using XviD at 75%
Thanks for your willingness to go at the bugs again. Unfortunatly I dont have much time as I had couple monthes ago, and I don't encode much any more. When I find time, I will write a very detailed bug report. Myabe the bugs will go away with future release. :)
For compression test, the final compression is off when doing 5% compression test with xvid + b frame using DVX. For example(numbers are made up), dvx report a compression of 60%, Johnny's enc report a compression rate of 72%, latest GK will also report a compression rate of 71%, when the final 2pass encoding is done, the compression rate compare to 1st pass is around 75%. That is what I mean by off.
I dont know what len0x did, but this is in the GK 0.28.5 change log:
- when using XviD + b-frames new extended comp test is performed (as in Jonny's Enc)
I am sorry that I dont have the time like I used to. That is one of the reasons I didn't reply this post right away. It seems pretty bad to say the program doesn't work and then dont have the time to fully test the fixed version with a detailed bug report. But I think it is better to let you know than provide no feedback.
@Doom9, a while ago you said the reason there isn't a guide for DVX is because it is buggy when you used it. If DVX is stable now, would you mind try it again?
stax76
14th July 2003, 13:17
For compression test, the final compression is off when doing 5% compression test with xvid + b frame using DVX. For example(numbers are made up), dvx report a compression of 60%, Johnny's enc report a compression rate of 72%, latest GK will also report a compression rate of 71%, when the final 2pass encoding is done, the compression rate compare to 1st pass is around 75%. That is what I mean by off.
on my test it was only 2% difference (higher) using XviD with 1 B-Frame for standalone player compatibility. Changing a codec setting will result in a different file size which will result in a different compressibility value is more logical to me than taking care of special codec settings. It's recommend to do a visual test (Action -> Test encode) anyway since every movie is different
jonny
14th July 2003, 16:48
If this can help, i've written a little proggy that parse the log file generated by VDub or AVS2AVI and return the average frame size (discarding the correct frames).
You can ask @ Bilu or TaZ4hvn, both use this (i'm quite lazy on summer time :D)
Cheers
jonny
bilu
14th July 2003, 18:21
Download R4R_ENC 2.0b from the last post of the thread at my sig.
There's a file called sp.exe
Usage: sp MOVIE.LOG normal|extended
Use extended if you encoded with b-frames.
It returns the average frame size.
Best regards,
Bilu
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.