Quote:
Hope this helps. If not, please post what your doing step-by-step. |
I have done all in the screens of kwag but he doesn't describe the output option. How I have to set it?
|
Quote:
|
I'll give it a try.
|
YES, thx, It runs, now! :D
|
Quote:
About that sawtooth/zigzag Q you are having problems with. I was always under the impression that you want to have the Q be as close to the sources bitrate path as possible 8O I must be pretty domb then. Because at the moment, I can't seem to stop my Q from being straight (flat-line) looking. I mean, it's not curved or zigzag (like I assumed its suppose to be) 8O. I'll post a pic shortly of what I'm on about K ? As to the emotion.mpg clip. It's a pretty high-quality source file. 1920 x 1088 resolution. Its pretty blocky in various areas, no thanks to the limited bandwitdh for such a large resolution. But, you won't notice it when you encode it anyways :wink: It's all gone!! Must be an dvd2avi glitch when you preview the emotion.mpg clip. By the way, this clip is Film based. That is, it's Telecined. I used my IVTC method on this, and it came out great. So, don't worry about Interlace. Just use your best IVTC method to week it out and get a great looking encode from this short, test clip, though 38mb in size. I can't remember how long it took, but I think it took like 1hour to D/L on my 56k dial-up.. not to get that mixed w/ Dialhot :P But, I do have a quation on this clip though. Was it Fullscreen, or was it a widescreen. I really couldn't tell because it's my first time dealing w/ such a large resolution source file. However, I think I prefered my tipicle TMPG encode quality better than my ffvfw encode. I'm still in the greay area w/ encoding w/ ffvfw 8O. I think that kwag's ffvfw encode came out much better than my ffvfw attempts. But, I suspect that it may be a "version" difference. My version I'm using is Sept 27 2003 13:29:54 and I did notice some items not present when comparing kwag's screen shot over on the sticky, page 1. -vhelp |
Quote:
Some of you may remember that I had that problem also, though I always found the codec was providing better quality than tmpg. Ok, now that most of you dropped the codec and since I was in trouble with something else and I had to reinstall XP (I was promissing this for months...) :arrow: Guess what :!: Now I have a PERFECT Q line and I will do some testing just to check if the bitrate peaks above 9800Kb. Cheers |
Quote:
|
Quote:
As I said I'll run my own bitrate peaks tests to see if it's ok to use it for KDVD because if it's higher than 9800kb... Just to share with you that I should have other problems that were preventing me to experience what other posted here such as Kwag or Inc. Cheers |
ok. Let me see if I get this straight..
A wavy Q line is bad, but a flat-line Q is GOOD ?? If flat-line "is GOOD", then just where should this line be ?? * below bitrate values ?? * above bitrate values ?? * dead center of bitrate values ?? Assuming your given encode went like this, with following bitrates: * 900 - - 7800, and Average bitrate @ 3200 (our dead center) For what it's worth, my Q's are always flat-line, using DVD rip as my source! And, I always thought that this type of Q was bad, and that the Q should always be wavy and matching that of the bitrate wave.. as if riding the wave :wink: 8O I don't know if I understand correctly this "Q" thing, but a little help would be appreciated :P Thanks, -vhelp |
Quote:
The problem here is that everyone is trying to use ffvfw and give results to all. BUT... I'm damn sure that there is "something'" external to the codec that modify deeply the results. And as long as we don't find it, there is no way to compare test done by everyone ! When some have flat curve and others don't, you are comparing citrus and orange. For sure they won't have the same taste :-) |
I agree with you phil! Did some tests on 2 pc's With exactly the same codec configuration both on WinXP. Same ffvfw builds, same source (even from the same network drive en exactly the same ffvfw config. With this the sample on pc1 was 21.628KB, on pc 2 18.544KB! Avg. Bitrate of the pc1 file is about 200 higher than pc2 file.... with same q value.
When I encode the sample again and again on the same pc, the size and bitrate stay (approximatly) the same. I really think there is an external factor influencing this codec, also becease if I encode this sample with tmpgenc on both pc's, the filesize is (approximatly) the same. Tinus |
Quote:
Still no news about Milan ? |
Quote:
That's why I started this thread about the FFMPEG development status, I think we should still focus our attention here: FFMPEG status on MPEG-2 encoding http://www.kvcd.net/forum/viewtopic.php?t=8835 Bilu |
Quote:
I agree with that, but FFMPEG has some serious issues on the stream, which render the muxing useless. That apparently has been fixed in ffvfw, because I can mux every ffmpeg produced stream, without any underruns or overrruns. Not so with ffmpeg :roll: -kwag |
Well, you got me interested on how much FFMPEG bugs are already corrected in FFVFW... :wink:
A good place to look: http://cvs.sourceforge.net/viewcvs.py/ffdshow/ffvfw/ Bilu |
Quote:
Where are the sources for ffvfw that we got here: http://www.ligh.de/software/mirrors.phtml :?: :?: :?: -kwag |
Hey Kwag,
I could be mistaken but i think it was Dano that told us that the latest builds available were produced by a guy by the nick of Athos. Rings a bell :?: Maybe he moved on with Milan's work since he hasn't been around for months. But then maybe i am only mistaken. Cheers |
|
how i can save a m2v, m1v?
I ¡m trying the ffvfw in virtualdubmod 1.4.5.1 and Virtualdub-mpeg2, i opne the avs /avi file but the final file it's an avi!!!
How i can save with vdub-mod-mpeg2 in m2v or m1v? Thanks |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.