Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > (HD) DVD, Blu-ray & (S)VCD > (HD) DVD & Blu-ray authoring

Reply
 
Thread Tools Search this Thread Display Modes
Old 17th November 2013, 20:50   #181  |  Link
frencher
French Love
 
Join Date: Oct 2008
Location: France
Posts: 456
Quote:
Originally Posted by trevorjharris View Post
Cannot get it to work with the latest version of avisynth.

"Cannot get YUV420 frame from input avi-file input.avs"

yuv raw files work fine
Quote:
FIXED
Avisynth 2.5.8 stable version have some problem with YUV.
Now fixed with AviSynth 13-09-18 2.6.0 Alpha 5 works perfectly.
Try this
__________________
2013-11-29 MVC Player Free v0.0.2.6 BD & 3D BD's Player, Demuxer v0.0.0.8b, Recoder. Tutorial
Demo for MVC Player Free: Trailer 3D

3DBD's Free - v0.0.0.0005.exe Old

Programing free for all.
frencher is offline   Reply With Quote
Old 18th November 2013, 19:25   #182  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
videofan3d, this is my second time and I noticed VBR algorithm undersize files as much as 40 % and I am using pacific rim as a example. While I expected file size to be 18GB+, it was around 10 GB or so for both stream. I have provided command line and specify bitrate in Kbit/s

Quote:
FRIMDecode mvc -i 00098.track_4113.264 -i 00098.track_4114.mvc -o \\.\pipe\test.yuv | FRIMEncode.exe mvc -i \\.\pipe\test_L.yuv -i \\.\pipe\test_R.yuv -viewoutput -o Pacific_Rim_AVC.264 -o Pacific_Rim_MVC.264 -w 1920 -h 1080 -f 23.976 -u 1 -cpbsize 3570 -l 6 -vbr 19540 60000 -profile high -level 4.1 -gop 24 4 0 S -maxdpb 4
[update1]

I decided redo and change bitrate to 28000, after about 55% done (calculate from number of frames done, from total frames) total size is 7.10 GB for both stream.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 18th November 2013 at 19:31.
HWK is offline   Reply With Quote
Old 18th November 2013, 19:34   #183  |  Link
Cedvano
Registered User
 
Join Date: Jul 2009
Posts: 244
Quote:
Originally Posted by HWK View Post
videofan3d, this is my second time and I noticed VBR algorithm undersize files as much as 40 % and I am using pacific rim as a example. While I expected file size to be 18GB+, it was around 10 GB or so for both stream. I have provided command line and specify bitrate in Kbit/s



[update1]

I decided redo and change bitrate to 28000, after about 55% done (calculate from number of frames done, from total frames) total size is 7.10 GB for both stream.
Me, I have see increase size with version 1.15.

Can I have your calcul for Bitrate ?
Cedvano is offline   Reply With Quote
Old 18th November 2013, 20:05   #184  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by Cedvano View Post
Me, I have see increase size with version 1.15.

Can I have your calcul for Bitrate ?
I think I have figured out my problem, It has to do with Kilobytes and kilobits. When calculating for disc use Kilobytes, which I didn't. Where encoder wants them in Kbit/s dumb error.

Spoke to soon, error is still there, but I think I have manged to get bottom of this and that is encoder help fine need some work, instead kilobits unit it expect bit-rate to be in Kilobytes. When I enter 60000 KBps (kilobytes per second) media info report correctly about max bitrate for combine avc and mvc to be 60 MBps (megabytes per second) which can be confirmed by reading values from original and another mvc encoder.

Quote:
FRIM Encoder version 1.15 (build: Nov 12 2013)
- based on Intel(R) Media SDK (version: 4.0.760.60435)

Usage:

FRIMEncode mpeg2|h264|mvc|jpeg [options]
-i InputFile -o OutputBS

options:

-avi - input file is in AVI format,
if not specified then YUV is expected
-sbs|tab numViews - input file is in side-by-side or top-above-below
format, valid only for multiview
-w width - source picture width (one view), mandatory for YUV
-h height - source picture height (one view), mandatory for YUV
-f frameRate - video frame rate (frames per second)

-cbr|b bitRate - CBR mode (in Kbits/s)
-vbr bitRate maxRate - VBR mode (in Kbits/s)
-cqp QPI QPP QPB - CQP mode
QPx quantization parameters for I,P,B frames
QPx in range [0,51]
-labrc bitRate depth - LA BRC mode (in Kbits/s) for H.264 encoder
look ahead depth, in range [10,100] or 0(=auto),
number of frames to be analyzed before encoding
Supported only with -hw option on 4th Generation
on Intel Core processors
bit rate is valid for H.264, MPEG2 and MVC
-cpbsize size - cpb/vbv buffer size (in KB)
max 3750 for H.264 Blu-ray
max 1194 for MPEG2 Blu-ray

-tff|bff - input stream is interlaced, top|bottom field first,
if not specified then progressive is expected
-nv12 - input is in NV12 color format,
if not specified then YUV420 is expected
-u 1..7 - target usage: between 1(=quality) and 7(=speed),
default is 4(=balanced),
valid for H.264, MPEG2 and MVC
-q quality - quality parameter for JPEG,
in range [1,100], 100 is the best quality
-l numSlices - number of slices, default value 0

-profile profile - codec profile name
MPEG2: simple, main, high
H.264: baseline, main, high
-level level - codec level
MPEG2: low/LL, main/ML, high1440/H14, high/HL,
H.264: 1, 1b, 1.1, 1.2, 1.3,
2, 2.1, 2.2, 3, 3.1, 3.2,
4, 4.1, 4.2, 5, 5.1, 5.2
MVC: 4, 4.1, 4.2, 5, 5.1, 5.2

-gop gopLength gopDist idrInterval O|C|S
- GOP structure control
GOP length
(0=unspecified, 1=I-frame only, ...)
GOP distance between I- or P-frames
(0=unspecified, 1=no B-frames, ...)
IDR interval:
H.264: between I- and IDR-frames
(0=every I-frame is an IDR frame, ...)
MPEG2: sequence header interval
(0=once at beginning, 1=every I-frame, ...)
Opened, Closed, Strict ... GOP structure

-maxdpb numFrames - maximum number of frames buffered in a DPB
(Decoded Picture Buffer), default value 0(=unspecified)
-CAVLC|CABAC - use CAVLC or CABAC for encoding, default is CABAC
(for H.264 only)
-VuiNalHrd on|off - insert NAL HRD parameters into bitstream,
default value on (for H.264 only)
-VuiVclHrd on|off - insert VCL HRD parameters into bitstream,
default value on (for H.264 only)
-PicTimingSEI on|off - insert picture timing SEI with pic_struct syntax
element into bitstream,
default value on (for H.264 only)
-EndOfSequence on|off - insert End of Sequence NAL into bitstream,
default value on (for H.264 only)
-EndOfStream on|off - insert End of Stream NAL into bitstream,
default value off (for H.264 only)

-dstw width - destination picture width, invokes VPP resizing
-dsth height - destination picture height, invokes VPP resizing
-hw - use platform specific SDK implementation,
if not specified then software implementation is used
-d3d - work with d3d9 surfaces
-d3d11 - work with d3d11 surfaces

-viewoutput - instruct the MVC encoder to output each view
in separate bitstream buffer.
Depending on the number of '-o' options behaves as follows:

1: two views are encoded in single file
2: two views are encoded in separate files
3: behaves like two '-o' were used and then one '-o'
Example: FRIMEncode mvc
-i InputFile_L -i InputFile_R
-o OutputEncodedBase -o OutputEncodedDependent
-viewoutput -w width -h height
Quote:
23.3 GB
Here are my calculation result

Subtitle + DTS 7.1 Audio = 2.82GB
Subtitle + DTS 7.1 Audio + Muxinng Overhead = 4.68

23.3 - 4.68 = 18.62 GB Video


2H, 11M, 17S video bit-rate = 20304kbps after factoring in overhead.

20304Kbps
I also tried higher and lower values for bit-rate, but for me it is doing undersize. For example I use 28000 on higher side along with 60000 max, where after 55% it is only 7.10GB for both stream and with default bit-rate of 19540 expected target size is 18.62GB combined.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 18th November 2013 at 20:45.
HWK is offline   Reply With Quote
Old 18th November 2013, 20:37   #185  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
@HWK
in my maths:
18.62GB = 19'067MB = 19'524'485kB = 156'195'881kbit
video duration = 7'877 sec
156'195'881kbit/7'877sec = 19'829kbit/s
Sharc is offline   Reply With Quote
Old 18th November 2013, 20:43   #186  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by Sharc View Post
@HWK
in my maths:
18.62GB = 19'067MB = 19'524'485kB = 156'195'881kbit
video duration = 7'877 sec
156'195'881kbit/7'877sec = 19'829kbit/s
You are right, I just checked encoder values indeed correct (19540, leave some room for error) But text file where I put all the information some how manage to get higher number.

Still resize is an issue for me, I am still trying to figure out why.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 18th November 2013 at 20:47.
HWK is offline   Reply With Quote
Old 18th November 2013, 20:48   #187  |  Link
Cedvano
Registered User
 
Join Date: Jul 2009
Posts: 244
It's strange, I don't have this problem. I use Bitrate Calculator GPL and All my video are correct. (with max bitrate 48000)
Cedvano is offline   Reply With Quote
Old 18th November 2013, 20:54   #188  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Quote:
Originally Posted by HWK View Post
Still resize is an issue for me, I am still trying to figure out why.
I don't know the details of the Intel encoder, but perhaps encoder saturation comes into play at these high bitrates?
I have not seen undersize for my (usually much lower) bitrates.
Sharc is offline   Reply With Quote
Old 18th November 2013, 21:11   #189  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by Sharc View Post
I don't know the details of the Intel encoder, but perhaps encoder saturation comes into play at these high bitrates?
I have not seen undersize for my (usually much lower) bitrates.
I am thinking you are right, I also have mainconcept MVC encoder and every time I encode with it, target size is reached. Also I set bitrate 30928Kbps, but during preview I notice it is averaging around 15 Mbps or so with change in bitrate much more drastic than other encoders and maybe this might explain what is happening.

After all it's doing in VBR so may be that is expected from encoder
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 18th November 2013 at 21:13.
HWK is offline   Reply With Quote
Old 18th November 2013, 22:30   #190  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by Cedvano View Post
It's strange, I don't have this problem. I use Bitrate Calculator GPL and All my video are correct. (with max bitrate 48000)
I use Bitrate Calculator GPL as well and for some reason things are different, well I guess change is good thing
Also you do know you can go up to 60000 max rate combined, I use all the time and encoder is smart enough to split bitrate correctly. For example base view bitrate never go above 40Mbps, peaks not included.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 18th November 2013 at 22:37.
HWK is offline   Reply With Quote
Old 18th November 2013, 23:44   #191  |  Link
trevorjharris
Registered User
 
Join Date: Jan 2007
Posts: 43
Has anyone got this to work with asv. I tried AviSynth 13-09-18 2.6.0 Alpha 5 and it failed with

"Cannot get YUV420 frame from input avi-file input.avs"
trevorjharris is offline   Reply With Quote
Old 19th November 2013, 02:16   #192  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by trevorjharris View Post
Has anyone got this to work with asv. I tried AviSynth 13-09-18 2.6.0 Alpha 5 and it failed with

"Cannot get YUV420 frame from input avi-file input.avs"
It failed for me as well, I also tried with avisynth with 2.6.0 Alpha 5. I just use pipe and for me it works very well.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 19th November 2013 at 02:56.
HWK is offline   Reply With Quote
Old 19th November 2013, 03:25   #193  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by Sharc View Post
I don't know the details of the Intel encoder, but perhaps encoder saturation comes into play at these high bitrates?
I have not seen undersize for my (usually much lower) bitrates.
I re-ran test and I can confirm some kind of saturation is happening in my case. I expect final output to be around 29GB or higher. However when encoder finished it was just above 16GB for both files.

I encoded with bitrate 30298Kbps, with max at 60000Kbps. However bitrate scanner tell different story altogether.

Source: Pacific Rim

Currently, I am re-doing the test with average bitrate and max bitrate at same value and it is set to 60000Kbps. It would be interested to see what happens with output.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 19th November 2013 at 03:28.
HWK is offline   Reply With Quote
Old 19th November 2013, 06:36   #194  |  Link
Cedvano
Registered User
 
Join Date: Jul 2009
Posts: 244
I've test with BRAVE and I would like 18GB and I have 16,2 GB.
Cedvano is offline   Reply With Quote
Old 19th November 2013, 06:47   #195  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by Cedvano View Post
I've test with BRAVE and I would like 18GB and I have 16,2 GB.
Thanks, for the result. Good to know I am not the only one. My guess VBR need some work and in my case difference is huge though.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.
HWK is offline   Reply With Quote
Old 19th November 2013, 14:08   #196  |  Link
videofan3d
Registered User
 
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
Bitrate

Regarding bitrate:

parameters for -vbr and -cbr are passed to Intel Media libmfxsw32.dll library, which controls the whole encoding.

Intel documentation specifies that it is in Kbit/s, defined as unsigned 16-bit number, where 1 kbit means 1000 bits.

Regarding "underbitrating" for VBR: I can imagine why it happens.
Intel Media is single pass encoder. When you specify -vbr 16000 24000, it means that maximum bitrate is 24000 Kbit/s which can be easily controlled. But average 16000 Kbits/s is a bit complicated issue for encoder, because single pass encoder cannot predict complexity of the videoscene, it can only evaluate current frame or maybe current GOP. So to achieve overall VBR on given value 16000 Kbits/s is only best guess for it. Therefore encoder uses rather lower bitrate whenever possible in order to prevent potential excess in future more complex scenes. As result it may happen that overall average bitrate is lower than specified.

Last edited by videofan3d; 19th November 2013 at 14:27.
videofan3d is offline   Reply With Quote
Old 19th November 2013, 18:01   #197  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by videofan3d View Post
Regarding bitrate:

parameters for -vbr and -cbr are passed to Intel Media libmfxsw32.dll library, which controls the whole encoding.

Intel documentation specifies that it is in Kbit/s, defined as unsigned 16-bit number, where 1 kbit means 1000 bits.

Regarding "underbitrating" for VBR: I can imagine why it happens.
Intel Media is single pass encoder. When you specify -vbr 16000 24000, it means that maximum bitrate is 24000 Kbit/s which can be easily controlled. But average 16000 Kbits/s is a bit complicated issue for encoder, because single pass encoder cannot predict complexity of the videoscene, it can only evaluate current frame or maybe current GOP. So to achieve overall VBR on given value 16000 Kbits/s is only best guess for it. Therefore encoder uses rather lower bitrate whenever possible in order potential excess in future more complex scenes. As result it may happen that overall average bitrate is lower than specified.
I understand your point of view, but I use different mvc encoder and use one pass on that as well and it is able to meet target size. I can't complain it is certainly better to have two mvc encoder than one.

[update1]
I just finished encoding on 60000 bitrate and so far my findings are file size is half of projected. For example I expected to be around 56GB, but final turn out to be around 27 GB.

Solution for me double the bitrate for example if I want 1000, write 2000 in encoder file and my final output would be of 1000 Kbps. In the meantime I would also try few more disc as well and see if it is some kind of pattern which I can repeat.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.

Last edited by HWK; 19th November 2013 at 22:59.
HWK is offline   Reply With Quote
Old 20th November 2013, 00:31   #198  |  Link
swallace
Registered User
 
Join Date: Nov 2013
Posts: 1
@HWK

Just out of curiosity: does changing the GOP length, or leaving it at default, have any effect on the output bitrate?
swallace is offline   Reply With Quote
Old 20th November 2013, 00:54   #199  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Input resolution -sbs or -tab

@videofan3d
In your documentation for the Encoder (which is very helpful and clear, thanks!) you write:
Please note, side‐by‐side Full HD 3D avi‐input has to have size 3840(!)x1080, however output
MVC‐encoded elementary streams will have standard size 1920x1080.

I just like to comment that input resolution of 2560x720 (-sbs 2) or 1280x1440 (tab 2) are accepted as well. MVC encoded elementary streams will then be 1280x720.
Sharc is offline   Reply With Quote
Old 20th November 2013, 01:03   #200  |  Link
HWK
Registered User
 
HWK's Avatar
 
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
Quote:
Originally Posted by swallace View Post
@HWK

Just out of curiosity: does changing the GOP length, or leaving it at default, have any effect on the output bitrate?
Yes, it does. If it is open gop it will increase compression efficiency and less bitrate is need to achieve same quality.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.
HWK is offline   Reply With Quote
Reply

Tags
encoders, mvc

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 19:07.


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