AnimeSuki.com Forum

AnimeSuki Forum (http://forums.animesuki.com/index.php)
-   Fansub Groups (http://forums.animesuki.com/forumdisplay.php?f=17)
-   -   h264 question (http://forums.animesuki.com/showthread.php?t=76367)

getfresh 2009-01-05 22:42
h264 question
 
What is the point or difference in naming a h264 file ".avi" or ".h264" in relation to the files you will be muxing to mkv? Just wondering.

neothe0ne 2009-01-05 22:46
..this is serious?

Obviously you don't put h264 inside the AVI container. It should just be a h264 "raw" you're muxing, or something in the MP4 container, I'd hope.

edogawaconan 2009-01-05 23:00
the way frames are stored is different, iirc

getfresh 2009-01-05 23:05
I'm talking about extension only here... does it matter if I change the extension of the track video to ".avi" when it is really ".h264"?

fireshark 2009-01-05 23:40
not anymore than you rename avi to, say, doc

cyberbeing 2009-01-06 03:04
.h264 is just an h.264 elementary stream without a container.
Renaming it to .avi does not put the .h264 inside the AVI container.

Does it matter? That all depends on if the mkv muxing app is idiot-proof or not, and is able to figure out what the file is, even when the file extension is inaccurate.

The real question is why would you even want to do this?

getfresh 2009-01-06 04:36
Quote:
Originally Posted by cyberbeing (Post 2145088)
The real question is why would you even want to do this?
No, the real question is the one I asked and had answered. The cynical question is the one you are leaning on. Anyways, I got my answer and fixed the issue I was having, end of topic. \o/

>.>

cyberbeing 2009-01-06 06:22
Quote:
Originally Posted by getfresh (Post 2145196)
No, the real question is the one I asked and had answered.
Whatever you say. :rolleyes:

Quote:
Originally Posted by getfresh (Post 2145196)
The cynical question is the one you are leaning on. Anyways, I got my answer and fixed the issue I was having, end of topic. \o/
I wasn't trying to be cynical, but your original question was rather ambiguous for why it was even being asked. As you just made clear, you were having an issue with something. The real question would have put this issue into the context of the question.

Anyway, since you solved your issue, enough said. :heh:

Emess 2009-01-07 09:03
Out of interest, was the issue you were having mmg telling you .264 files are not valid input? The GUI seems to like doing this.

E~

mad_cracker 2009-01-13 14:38
I know that this isn't the right thread to ask this but I don't want to open another one refering to x264 so here it goes. The thing is: I have a raw video in a mp4 container with FullHD resolution and when I try resizing it to 1024x576 the first pass goes insane and encodes a realy high number of fps. But after the second pass, that goes well, the quality of the video sucks and its full of blockin shit. I guess that the problem is in the first pass. I don't know what to do anymore. I've tried so many settings. Need help plz :)
Thanks in advance.

jfs 2009-01-13 15:17
Most likely, the video is VFR and is being treated as "120 fps" for whatever reason. The resulting VFRaC files are therefore marked as being "120 fps", and that makes the ratecontrol break. If you're feeding the video through Avisynth (I hope you are) just use AssumeFPS(24/1.001) or similar to get something sensible.

mad_cracker 2009-01-13 15:24
Quote:
Originally Posted by jfs (Post 2159123)
Most likely, the video is VFR and is being treated as "120 fps" for whatever reason. The resulting VFRaC files are therefore marked as being "120 fps", and that makes the ratecontrol break. If you're feeding the video through Avisynth (I hope you are) just use AssumeFPS(24/1.001) or similar to get something sensible.
When I say that "the first pass goes insane and encodes a realy high number of fps" I meant that the speed of the encode of the first pass is above 100 fps. Sorry for the misunderstanding.

This is way impossible with the bitrate at 2000.
http://madcracker.no.sapo.pt/InsaneProcessingRate.jpg

D404 2009-01-13 16:32
OH, some more info on how/what you aredoing would be helpful.

avs, x264 settings etc

mad_cracker 2009-01-13 20:15
Video info:

MPEG4 Video (H264) 1920x1080 23.98fps [Video]

AVS used:

Code:
DirectShowSource("D:\WorkPath\FMPTSR\FMPTSR01_track1.mp4")
BicubicResize(1024,576)
Tweak(bright=-15,cont=1.1,sat=1.2)
mergechroma(blur(1.3))
Asharp(1,3,1)
x264 settings(from megui: Unrestricted 2pass Anime_Toons HQ)

program --pass 2 --bitrate 2000 --stats ".stats" --ref 8 --mixed-refs --bframes 16 --b-pyramid --direct auto --deblock 1:1 --subme 7 --trellis 2 --psy-rd 0.6:0 --partitions all --8x8dct --me umh --threads auto --thread-input --aq-mode 0 --aud --progress --no-psnr --no-ssim --output "output" "input"

Programs used to encode:

meGUI

---------------------------------------------------------

If there's anything that can be useful to refer please tell me.

BTW I tried to encode it with no compression and then recompress it again with x264 and it worked perfectly. Don't know what happened diferent. Maybe something with the framerate.
Thanks.

checkers 2009-01-13 20:48
Quote:
DirectShowSource("D:\WorkPath\FMPTSR\FMPTSR01_trac k1.mp4")
BicubicResize(1024,576)
Tweak(bright=-15,cont=1.1,sat=1.2)
mergechroma(blur(1.3))
Asharp(1,3,1)
Suggestions for each line:
1. consider ffmpegsource, but that's not too important
2. Try using either spline36resize or lanczos4resize, which will help marginally.
3. This looks evil. If you have to do that much tweaking either the source is really fucked up and you should get another one, or you're Doing It Wrong
4. This is a weird megui-ism. Try dfttest(sigma=0.4) or so instead.
5. Try limitedsharpenfaster() instead of that (crappy) sharpener.

Add to the end of the avs: assumefps(23.976). Does that fix the problem?

Quote:
program --pass 2 --bitrate 2000 --stats ".stats" --ref 8 --mixed-refs --bframes 16 --b-pyramid --direct auto --deblock 1:1 --subme 7 --trellis 2 --psy-rd 0.6:0 --partitions all --8x8dct --me umh --threads auto --thread-input --aq-mode 0 --aud --progress --no-psnr --no-ssim --output "output" "input"
Make sure you have the latest version of sharktooth's profiles, I think that one is old.

mad_cracker 2009-01-13 21:28
It still encodes at above 150 fps. I've never seen something like this.

This raw must be realy fckdup.

Btw:

without the tweak:
http://madcracker.no.sapo.pt/t0.png

with Tweak
http://madcracker.no.sapo.pt/t1.png

checkers 2009-01-13 22:17
more contrast != better. Keep it how it was intended to be seen.

mad_cracker 2009-01-14 06:45
Not always :)
I was trying to use that plugin (dfttest(sigma=0.4)) that you have mensioned before and when I try to load libfftw3f-3.dll library it tells me that it isn't an avisynth 2.5 plugin. I'm using the latest stable version of avisynth and I've tried 2 diferent versions of the file and still doesn't work. Could you please advise? Thank you.

checkers 2009-01-14 08:56
read readme.htm

mad_cracker 2009-01-14 20:11
Course I've read it. But it just won't work. I'll try doing some research instead of filling this thread with non reliable info. Sorry for the bother and thanks for the help so far.

EDIT: Already workin. Thanks.


All times are GMT -5. The time now is 10:13.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.