Ok, I want to bring it up again, and hopefully after that we can burry it. I've been testing this baby too now, for several weeks. I also tested this setting in the "quantization type" setting...
Quote:
The stream produced by ffvfw with setting set to H.263 is the EXACT same as if you set it to MPEG2. That is what kwag insisted and that is what my tests confirm. Same size, same GOP structure, same Q-Curve, same bitrate allocation. Over and out. |
In BV it is 14 so realy 28.
I now try to figure out where it is VBV value seted in file. I compare two files with differend VBV under HexEdit but they are identical. It is mess of @!$@!&$%@$ like signs along with jahsdkjAHkjHASOIAS and some numbers and some ...... as usual in HexEdit :lol: so I migh overlooked this. I'm keep trying. EDIT: Hold youre horses. I think I foud entry. Few more test. I'll be bec in 5-10 min. |
Quote:
I was hoping that the vbv had been corrected by 40 but in fact it was by 44 since now you have 72 minus the 28 you had previously equals 44. I wonder if there is a way to tweak tmpg in the registry so that it patches the file to 224 instead of 44... I'll take a look at it now, though I'm not a regedit expert... Cheers |
:lol:
Oh my god... you're trying to change that VBV Buffer size of a file with a Hex-Editor? :lol: That is the funniest thing I've heard in a long time. I think the last time I used a Hex-Editor was to activate cheats in Doom II... :mrgreen: No offense, seriously buddy... :wink: |
Read my last edit :!:
|
@Hydeus,
You mean in the registry or using the hex editor 8O Be a sports and be back in 1m :lol: Cheers |
Quote:
Since in making of a KVCD/KDVD we have to break some standards anyway, at least let's find out how far we can go. Moreover we could picture more exactly where the problem with ffvfw resides or could be done in the futhure. For example untill yesterday I lived under the impression that everybody could play at least a VCD made with my settings and I would have been under that impression even now if rds wouldn't point out his problems playing such a file on his player and others. I just learned that Milan is back and I think it might be usefull for him such a poll. Besides, I'm not sure how much interest he has in mpeg2 encoding since a big deal of ffvfw is about mpeg4 encoding so I think that a suplimentary motivation for him would be good. marcellus |
Quote:
What do you achieve by finding the Hex Values that set the VBV value :?: It's not like it is at the same spot with every file you encode... |
Quote:
Ive changed now succesfulu VBV from VCD to SVCD 8) I'll post some instruction in few minutes. |
@Hydeus: I totally see your point but...
The way I see it, in order to see the differences between 2 files refering to the VBV buffer you'll always need : 1 File with the wrong VBV Buffer + 1 File with the right VBV Buffer The problem is, we can't produce a stream with the right VBV buffer with ffvfw right? So we can't know where the correction has to be done. I really do not believe that the information of the VBV buffer is at the same spot in generally all MPEG Files... Or is it? :roll: |
Quote:
Couldn't agree more with you, Marcellus. Do you want to tell us your latest settings? Hey Hydeus? What about your's? Anybody else wants in with us? While both you two post it your settings remember to tell us which build you're using so we can all tune up. What do you think :) |
Ok here we go :D
- Open file in hexeditor of any kind you like. - first line is our goal. its a bit tricki so read carefuly. Migh be some errors, I'm nevbe as you all know ;) it is build of 2 column , each of 8 pairs (hexadecimal) oure goal are two pairs in second column afret FF FF :arrow: For VBV 40 (20BV) type E0 A4 :arrow: For VBV 112 (56BV) type E1 C4 I don't preformed DVD VBV , so for now i dont know what value it will be , but i think it can be calculated. Test this while it is still not all. I'll be back in few minutes (of typing ; ) EDIT: Jelly we can produce files with proper VBV bufer, at least Kwag say it is possible. While I'm not expert on this I can only belive hes words. |
Quote:
That will give us a correct vbv under BV but a choppy playback because the stream is still vbv 14 in terms of body... Hope you can prove me wrong Hydeus. C ya |
Quote:
|
And thiss is where my problem lies. Same set of hexadecimal pairs repeats one more time in the stream. But now this is more complicated, while I dont know where to find them in some random/differend stream :cry: I'm still testing.
|
Maybe this is a dumb question, but why is there a vbv setting for muxing in avi2mpeg when this info is already present in the video stream?
|
I don't know the purpose of that, while video stream with VBV40 muxed as SVCD with 230 (another strange value ;) ), and demuxed still have VBV40.
|
Back to hexedit.
This is not one more time (I have 10s sample), I think this is period of GOP lenght. I need a specialist. I'm only newbie :lol: |
A VBV buffer size entry, is present on every "Sequence Header" of an MPEG-2 file.
This occuurs about every half second in the stream. So if anyone wants to patch a VBV buffer size, have fun :roll: References: Video Demystified. Page 573. Edit: I can see the writing on the wall: "kwag, can you write a VBVPatcher program" :lol: -kwag |
@rds_correia:
My settings I use since at least two weeks with good results are in this thread: http://www.kvcd.net/forum/viewtopic.php?t=9191&start=0 I hope that everybody could see the pictures, I had an issue on that side but I think I solved yesterday. But anyway I think that a new thread is necessary for this test. EDIT: I forgot to say that I use the latest version you can find at this address: http://www.ligh.de/software/mirrors.phtml @jellygoose I don't really understand the point in discouraging or making fun of somebody because he has an idea that could look dumb for the moment but in fact could be very useful at some point. This is a basic rule in brainstorming, everybody can say anything, no matter how stupid might look and nobody can criticize it. In the end we'll eventually see if it was a good idea or not. marcellus |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.