MVCenc v3.0.0 - MVC 3D Encoder (Intel Quick Sync)

[dorati]

Works great. Thank yor for this Tool !

[pistacho]

Version 2.2.3 (11/07/2014)

• Fixed all Pacific Rim 3D decoding issues (SW mode and HW mode).
• Full compatible with latest Intel HD Graphics driver's series.
• Slightly reduced CPU usage and memory usage.

[dorati]

I have some problems.

I demux the original file with eac3to and then i use this tool.

On My i7-3517 Ivy Bridge, the mfc-video is ok.
On Haswell i get a lot of artifacts. What i make wrong ?

This commandline i use:


C:\Program Files (x86)\BDtoAVCHD>mvcenc "u:\eac3to\video.avc" "u:\eac3to\video.mvc" 999999 c:\eac3to\convert.h264 32699 1
MVCenc v2.2.3. This tool is part of BDtoAVCHD software. Coded by Joel Gali.

Intel Media SDK Decoder Info: API LEVEL 1.11 - HW

Source Information:

- Resolution: 1920x1080
- Frame Rate: 24000/1001 (23.976 fps)

Intel Media SDK Encoder Info: API LEVEL 1.11 - HW

Target Information:

- Resolution: 1920x1080
- Frame Rate: 24000/1001 (23.976 fps)
- Codec: AVC, Level: 4.1, Profile: AVC Stereo High
- Num Slice: 6
- Num Ref: 4
- GOP: 24-4-0 Open
- Buffer Size: 30000 Kbits
- Max Bitrate: 60000 Kbps
- Bitrate: 32699 Kbps
- Tar. Usage: 1

MVCenc [12.2%] 122384/999999 frames, 29.64 fps, 377.45 Kb/s, eta 8:13:27

[dorati]

Update..
On Stereoscopic Player, all look fine. The Problem i have only with my SamsungTV and m2ts.

Somebody the same problem ?

[pistacho]

Originally Posted by dorati

Update..
On Stereoscopic Player, all look fine. The Problem i have only with my SamsungTV and m2ts.

Somebody the same problem ?

What method do you use to create the m2ts?

Maybe if you create the ISO structure using BDtoAVCHD and then use the SSIF file works OK with Samsung TV...

[dorati]

I make some tests:

I use tsmuxer 2.6.12 to create m2ts.

I found, when select "Always rebuild SEI and VUI data"; the picture seems ok.
Is this setting ok? I read, when use this option, the file normaly is not 100% ok.

[pistacho]

I don't know. The only scenario tested by me is generating ISO structure to play thought standalone Blu-Ray player or compatible SW (Stereoscopic Player, TMT6, etc.) and in this case is NOT used "rebuild SEI and VUI data" option.

But probably muxer requirements are different for Samsung TV. Anyway it seems clear that this is a muxing issue (unrelated to the encoder itself).

Though not understand how the TV can correctly play 3D content with only .m2ts as there is important information in other files of the ISO structure (such as the assignation of left/right views to AVC/MVC streams).

[pistacho]

Version 2.2.4 (11/20/2014)

 - Upgraded to Visual Studio 2013 (no functional changes).

[Tounet]

Hello there

Thx for you're great tool. Very useful for re-encoding 3D blurays.
There is some problems with some bluray 3D muxed in m2ts on Samsung TVs. I guess that's a bitrate problem. (officially, in the samsung doc, max bitrate is 30Mb/s) This require more testing.

With this tool, we can simply re-encode the bluray with lower bitrate, and that's works well.
I suggest some more functionnality for BDtoAVCHD, i 'll post in the good thread.

[pistacho]

Originally Posted by Tounet

I guess that's a bitrate problem. (officially, in the samsung doc, max bitrate is 30Mb/s) This require more testing.

This is interesting: bitrate really could be the cause of some problems reported:

Originally Posted by dorati

Target Information:

- Resolution: 1920x1080
- Frame Rate: 24000/1001 (23.976 fps)
- Codec: AVC, Level: 4.1, Profile: AVC Stereo High
- Num Slice: 6
- Num Ref: 4
- GOP: 24-4-0 Open
- Buffer Size: 30000 Kbits
- Max Bitrate: 60000 Kbps
- Bitrate: 32699 Kbps
- Tar. Usage: 1

Then I put a sample command lines that can be used for testing:

max_bitrate = 30000
buffer_size = 30000
bitrate = 25000

encode:

"C:\Program Files (x86)\BDtoAVCHD\MVCenc.exe" "T:\TEMP\source.avc.h264" "T:\TEMP\source.mvc.h264" 187608 "T:\TEMP\encode.h264" 25000 4 30000 30000

187608 is the frame count of source, change accordingly or put a smaller number (10000) for short test.

remux:

1. Create a text file called "tsmuxer.meta":

MUXOPT --no-pcr-on-video-pid --new-audio-pes --vbr --vbv-len=500
V_MPEG4/ISO/MVC, "T:\TEMP\encode.h264", subTrack=1
V_MPEG4/ISO/AVC, "T:\TEMP\encode.h264", subTrack=2

2. command line:

"C:\Program Files (x86)\BDtoAVCHD\tsMuxeR\2.x\tsMuxeR.exe" "T:\TEMP\tsmuxer.meta" "T:\TEMP\encode.m2ts"

If dorati, Tounet or someone with a Samsung TV proves it and comment the result will be very useful

[sergio2]

I'm trying to back up a few 3D Blu-Ray disks by making .m2ts files from STREAM .ssib files with TSMuxer, in order to be read on my Samsung TV.
As it has been noticed on forum, some .m2ts files open and display native 3D on Samsung TV whereas others load indefinitly and never open.
The question was : is it a problem of bitrate ?
The thing is I'm a newbie and can't answer this question : I did a few tests and let you comment them.

Here's a first test with Jurassic Park 3D : .m2ts file made directly from .ssib file located into BD STREAM folder does not open on TV Samsung. So I used BDtoAVCHD to re-encode video : I chose BD25 and settings are in attachment Img1.jpg.
I mounted the .iso file obtained after BDtoAVCHD had finished running, then selected .ssib file from STREAM folder to run with TSMuxer and obtained the new re-encoded .m2ts file.
This new .m2ts file did open on Samsung TV with nice 3D displaying, but when I stopped the video or went fast forward then replayed, a bloody awful pixelation occured and was irreversible.
With the same BD, I tried your settings by using command lines (displayed in Img2.jpg and Img3.jpg) : Img2 refers to a target usage of 4, Img3 to a target usage of 1. I then muxed encode.h264 and sound files in TSMuxer to obtain two new .m2ts files. The result was the same as .m2ts obtained from BDtoAVCHD : nice 3D displaying, but pixelation when fast forward...................

Here's a second test with a second 3D Blu-ray Titanic : .m2ts file made directly from .ssib file located into BD STREAM folder does open on TV Samsung. But I had a try with BDtoAVCHD to re-encode video and check if there still was this strange pixelation phenomena : I chose BD25 and settings are in attachment Img4.jpg.
.m2ts obtained from .iso file with TSMuxer showed exactly the same issue than others .m2ts obtained from BDtoAVCHD : still this bloody pixelation !

So in conclusion :

1- First BD : bitrate < 30000 : need to be re-encoded with BDToAVCHD.

2- Second BD : bitrate > 30000 : don't need to be re-encoded.

Re-encoding with BDToACVHD gives a working .m2ts file, but pixelation occurs when playing video fast forward.
Could this observed pixelation be explained by the fact I've only got an i5 intel processor ?

A friend of mine has got a Thomson 3D TV : all .m2ts files obtained directly from BD STREAM folder .ssib files open without any problems on his TV : it looks as if it was a typical Samsung problem !

[dorati]

Bitrate is not the problem.
Then i was thinking, the problem was 3 reframes.

But Avatar has 3 reframes and >30Mbit.
Works perfect.... What can be the problem??

At the end, i mux the not working streams with scenarist - not working.
So, there must something with the stream, not the mux - i think.

But perhaps somebody as a idea.

[sergio2]

@Dorati
Did you observe pixelation on your Samsung TV after jumping fast forward then replaying files obtained from BDToAVCHD ?

[dorati]

this works so far for me.

[sergio2]

Which model of Samsung TV do you own ?

[sergio2]

In fact, pixelation comes from HW encoding !

When I disabled Media SDK (see attach file), SW encoding took 16 hours instead of 1 hour and a half with HW, but at least no pixelation occured after jumping fast forward .m2ts video file.

[pistacho]

Hi sergio2,

Some users have had problems with the combination (HW + 1-2 Target Usage levels).

Maybe with T.U level 4 you can use HW. It seems a limitation of some systems.

You also can try to update Intel Graphics drivers. Recent drivers comes with 1.11 API level (you're using API level 1.7).
Intel Media SDK files are updated by the driver.

https://downloadcenter.intel.com/

EDIT => Another thing: to generate the final .m2ts (when you already have ISO / ssif file) probably just have to rename/copy the .ssif file to .m2ts since both have the same structure.
No need to re-remux using tsMuxeR again.

[sergio2]

Hi,

Thank you for your answer.
I already tried HW encoding with T.U = 4. It didn't change anything.

I'm afraid of upgrading intel drivers on my ASUS notebook !
This computer was originaly built on Windows 7. I created a Windows 8.1 partition (it's on this partition I ran BDToAVCHD) so that I obtained a dual-boot 7/8.1. When I tried to upgrade Intel driver on Windows 8.1, my notebook displayed a black screen when booting and I don't want to see that again.........
I should try to run HW encoding with BDToAVCHD on Windows 7 partition.

[pistacho]

What model of processor is?

[sergio2]

Intel Core i5-3210M, 2.5 GH with two graphic cards :

INTEL(R) HD Graphics 4000 (driver 10.38.10.3308 from 09/2013)

NVIDIA GeoForce 630M (driver 9.18.13.3158 from 10/2013)