So, if you increase the frame size, without increasing the data rate to a reasonable amount, the CODEC will have no choice but to starve the frame of image data (quality suffers). Increasing the frame size means less bytes per second per square inch of video frame which translates to lower image quality. Decreasing the frame rate will give you more bytes per second to fill in detail in the image but at the cost of motion.
Don't if you aren't using a streaming server and you misused that term when you said you wanted it for web streaming then don't enable streaming, it does nothing but make the file larger.Įxperiment. Set the data rate to anywhere from 320 to 420Įnable Streaming if you are using a streaming server. I can't match your description with what I see when I do a compression using MPEG-4 from FCP. You'll need QuickTime 7 to get the H.264 CODEC. You'll want to make sure your MPEG-4 files are using the H.264 CODEC so you can get the frame size you want in a more reasonab e data rate such as 320. Most video for DSL is set at no more than 320k bits per second. Only people with 1MB DSL and better web connections could stream that kind of data rate. If you make it 30MB, then the video will be 125k bytes per second or 1 megabit per second. FCP comes with the Compressor package which is dedicated to doing compression.ĭo some math on what you are asking.
Strangely, these both work ("Extract Visual Track ID _ to an AVI file" command line):Ĭ:\>"C:\Program Files\YAMB\MP4Box.exe" -single 2 "G:\pub\yamb_tst.There are many many postings on this topic with step by steps on adjusting the parameters used during compression. Notice that they are the same mp4box command. G:\pub>"C:\Program Files\YAMB\MP4Box.exe" -single 2 "G:\pub\yamb_tst.mp4"Ĭ:\>"C:\Program Files\YAMB\MP4Box.exe" -single 2 "G:\pub\yamb_tst.mp4" This fails ("Extract track ID _" command line): Drive C: is local and drive G: is shared. I think this is due to the following behavior of mp4box so it is not a bug in Yamb. This is strange because the "Extract Visual Track ID _ to an AVI file" works on either a shared/mapped drive or a local drive. If the input file is on a shared/mapped drive on my server, the "Extract track ID _" function of Yamb does not work. Here's a revision to my previous reported behavior, that I now believe is unrelated to the source video: I'll also try a test without bframes and also some DVD source. Bond, would you like to file a (much more expert) bug report :) I don't know if the project is still under development but I'll file a bug report anyway as it should be making correct. OpenShiiva is clearly designed for DVD source, but I assume it would have the same problems with DVD source too.
OPENSHIIVA MAC
Thanks everyone! The source was originally 1080i ATSC.īond, I encoded it with OpenShiiva as I'm checking out some Mac encoding aps. Then, with mkvextract you should be able to extract each tracks. So, does anyone can confirm that mp4box is not compatible with hd stuff as input ? I don't have much hd files here apart the Calinb sample.įor the moment, if you want to extract video and audio tracks, you can try to mux your file into a matroska file (via mmg).
OPENSHIIVA MP4
Otherwise, I suspect the HD resolution.I tried to remux your sample directly in mp4 and mp4box doesn't seem to like the video track (I've a bad parameter error as return). We can see that video & audio track are synchronized with the track 3. MPEG-4 Config: SceneDescription Stream - ObjectTypeIndication 0x02 Media Info: Language "und" - Type "sdsm" - Sub Type "mp4s" - 1 samples MPEG-4 Config: ObjectDescriptor Stream - ObjectTypeIndication 0x01 Media Info: Language "und" - Type "odsm" - Sub Type "mp4s" - 1 samples MPEG-4 Audio AAC LC - 2 Channel(s) - SampleRate 48000 MPEG-4 Config: Audio Stream - ObjectTypeIndication 0x40 Media Info: Language "und" - Type "soun" - Sub Type "mp4a" - 888 samples Pixel Aspect Ratio 1:1 - Indicated track size 1280 x 720 MPEG-4 Visual Size 1280 x 720 - Simple Profile Level 3 MPEG-4 Config: Visual Stream - ObjectTypeIndication 0x20 Media Info: Language "und" - Type "vide" - Sub Type "mp4v" - 567 samples Visual PL: Simple Profile Level 3 (0x03)Īudio PL: High Quality Audio Profile Level 2 (0x0f) Scene PL 0xff - Graphics PL 0xff - OD PL 0xff I usually do a constant quality QP7 rip with no scaling at between 25-30 fps on my Dual 2GHz G5, which calculates to being real time (add 20 minutes for 0Sex to do its job). The 3ivX codec is almost as good and twice as fast at similar settings. ) I tested directly by command line and we have the same result. OpenShiiva defaults to the XviD codec which produces great quality at the cost of slow encoding.
I post here some notes to inform other people and to have more informations.įirst, this is not a bug in Yamb. Aaaa.your sample is very interesting Calinb (you like Green Day, isn't it ?).
0 kommentar(er)
