View Full Version : BD3D2MK3D v1.17: Convert 3D BDs or MKV to 3D SBS, T&B or Frame-sequential MKV
frank
25th February 2015, 10:54
Hm, I wanted to add a fixed depth and that was not processed by BD3D2MK3D. Then I used the Tools and converted the sup directly with depth 20.
I will repeat the test. But that damned ISO needs 50GB...
Maybe I need some time.
r0lZ
25th February 2015, 11:24
The fixed depth is added during the final phase of the conversion (when the PNGs with the stereoscopic bitmaps are written to disc). The fixed depth is not taken into account when BD3D2MK3D writes the <depth> tags in the temp 2D XML file. (That allows you to convert the temp XML file again with another fixed depth if you think that the resulting final depths are not good, without affecting the original depths extracted from the 3D-planes and already written in the XML.)
It is never necessary to redo the whole process if you need to fine tune the 3D subtitles. You can convert them again with the Tools menu, and overwrite the original 3D subtitle file. Then use the _MUX_3D.cmd to remux the final MKV with the modified subtitles. (Of course, in case of hardcoded subtitles, you'll have to restart _ENCODE.cmd, and that's much longer.)
frank
26th February 2015, 19:58
The help link at Additional options doesn't work.
Please correct to
http://en.wikibooks.org/wiki/MeGUI/x264_Settings
r0lZ
26th February 2015, 20:10
Hum, indeed the site seems down. But the last time, it has been down only during a couple of hours. If tomorrow it is still down, I'll use your link. And I'll release a new version of BD3D2MK3D, for that reason and others. Thanks anyway!
frank
26th February 2015, 20:17
Oh, the site is 4 years old. Some important options missing. :rolleyes:
|1313|
26th February 2015, 20:51
Isit possible to make 720p rips using BD3D2MK3D i have searched and not found anything about it i checked the files and cant find any setting to change. Its not important just want to know. :)
Thanx for an awesome software.
r0lZ
26th February 2015, 22:43
Oh, the site is 4 years old. Some important options missing. :rolleyes:Hum, I need another link than. The old wiki seems definitively dead. Anyone knows a good site with up to date explanations if the x264 options?
r0lZ
26th February 2015, 22:49
Isit possible to make 720p rips using BD3D2MK3D i have searched and not found anything about it i checked the files and cant find any setting to change. Its not important just want to know. :)
Thanx for an awesome software.
Hi |1313|, Welcome to the Doom9 forums!
Currently, encoding in 720p is not possible. It's difficult to do, especially because the 3D subtitles are difficult to resize in 720p while keeping the correct 3D depth. Furthermore, don't forget that the width or height of the SBS or T&B image is divided by 2 (unless you encode in full-SBS or full-T&B), and I believe that half-720p may be too small for a good result. But the resize to 720p is in my TODO list for ages. Maybe I'll do it one day. It's not my priority though.
|1313|
26th February 2015, 22:54
Thanx for the answer :) But if you dont need the subs?
And thanx again for a wonderful software :)
r0lZ
26th February 2015, 23:00
I can't add an option that works only in some circumstances.
|1313|
26th February 2015, 23:37
I understand that but is their any file i can edit? I mostly rip movies using swedish language cause thats where iam from :) without subs :)
r0lZ
27th February 2015, 01:17
Well, you can simply edit _ENCODE_3D_MOVIE.avs.
For Half-SBS, you should remove (or comment out) the line with:
StackHorizontal(HorizontalReduceBy2(Left), HorizontalReduceBy2(Right))
and replace it with:
StackHorizontal(left, right).LanczosResize(1280, 720)
The line to replace in Half-T&B mode is something like:
StackVertical(VerticalReduceBy2(Left), VerticalReduceBy2(Right))
and you should replace it with:
StackVertical(left, right).LanczosResize(1280, 720)
In Full-SBS or Full-T&B, the original lines are respectively StackHorizontal(left, right) and StackVertical(left, right), and you should replace them with StackHorizontal(left, right).LanczosResize(2560, 720) or StackVertical(left, right).LanczosResize(1280, 1440)
Note that I have used the Lanczos resize filter in my examples. You can use another filter if you wish. The basic syntax is always identical: XXXResize(width, height). The available filters are listed here (http://avisynth.nl/index.php/Resize). Lanczos gives good results but is relatively slow.
I don't think there are other files to modify (except the subtitles, but you don't need them), but I may be wrong.
Good luck!
|1313|
27th February 2015, 01:21
Thanx alot :)
EDIT. Works perfectly. EDIT.
Iggyrules
27th February 2015, 02:34
Hello all, I'm needing help...
I'm having a similar issue as CaBleman had regarding BD3D.iso to 3D.mkv with hard coded 3D subtitles...I've disabled the Hardware Accelerator, but I still have black frames issues. The sound is perfect throughout. Her's some examples - Avatar has all black frames from the start through to the end, but the sound and all the forced subs (hard coded) are perfect. Transformers I get about 90 minutes, then black frames for the remainder of the movie, sound and subs (hard coded) are perfect. Teenage Mutant Ninja Turtles is the same, about half the movie. I can provide all files.
'lo there,
I've been using BD3D2MK3D on a WIN 7 machine for a while and was quite happy with 0.42
I installed Avisynth 2.58 on a Windows 8.1 with all recent updates (also the .NET ones) and tried BD3D2MK3D 0.51 with different 3D BD ISOs. THe result is awlways the same.
After demuxing, all files seem to be there, in sizes which make sense.
But the encoding step would produce MKVs which have a black/blank video part in the end.
I tried a couple of things, examined the command lines, ran the commands manually - there are no specific error message, if any at all...
Non 3D chain with BluRip works fine BTW.
Any idea or guidance where to inspect further?
thx & bye,
CaBleman
Thank you,
Iggyrules
Iggyrules
27th February 2015, 05:18
FYI - I've thoroughly read through numerous forums, topics and posts (especially this topic) looking for ANY clue to correct my issue. I've tried dozens of setting options and hours of failures. The best results so far are when using crf with BD compatible selected. Everything appears to be working as designed. It's possibly in the encoding process or in the .mkv file writing process after the encoding. Regardless of the movie title the original BD3D.iso(s) are all around 40 GBs, but the final Half SBS 3D.mkv is only a few GBs.. Total .mkv writing time is only about 1 minute...
I know you'll require the file logs, but I don't want to add all of them until you request them.
Thank you for taking the time to read my post.
Iggyrules
r0lZ
27th February 2015, 11:16
Thanks for your bug report, and welcome to the Doom9 forums.
First of all, have you read the solution found by CaBleman here (http://forum.doom9.org/showthread.php?p=1697452#post1697452)? As he has explained, the culprit was the hardware acceleration. If you use DGMVCSource, you can simply edit the _ENCODE_3D_MOVIE.avs file, and change the "hw = 0" parameter at the end of the DGMVCSource command with hw = 1. (You can immediately relaunch the encoding, without having to redo the whole demuxing process.)
Note also that soon after that post by CaBleman, I have released v0.52, and, the same day, v0.53, with a new option in the Settings -> MVC Decoder menu. It is now possible to specify "auto" (the default that doesn't work for you), "disabled" (the setting that you should try) and "enabled" (that will almost certainly produce the same bug).
Also, you posted your bug report exactly at the right moment. I had the intention to release a new version of BD3D2MK3D today. Although I'm not sure, it is possible that it fixes that bug, because DGMVCDecode.dll has been recompiled with the latest Intel INDE toolkit. The software decoder in libmfxsw32.dll has also been fixed by Intel. I know already that the new versions of that 2 DLLs fixes all decoding problems encountered so far with the software decoder (and notably the famous glitches in Pacific Rim at 1:06:14 and in Flying Swords of Dragon Gate at 1:23:35). I don't have the required Intel hardware to test the hardware acceleration, but Frank has tested it on several machines, and it works apparently well on all machines with the up-to-date Intel drivers. (It might still be necessary to force the software decoding if your CPU doesn't have the right driver, or if Indel has not updated the driver for your model).
I will release that new version very soon, but I still have to fix a little bug. Please come back in a couple of hours, and try the new version. In the meantime, please verify if you have the latest Intel drivers for your CPU. When you will have encoded a 3DBD with the new version, please report here if the updated decoders work for your CPU, with and without hardware acceleration. BTW, what CPU do you have?
r0lZ
27th February 2015, 12:50
Here is the update. It's an important update, because it fixes (or should fix) all decoding problems related to the Intel MVC Decoder (used indirectly by DGMVCSource and FRIMSource). As you know if you have followed the development of BD3D2MK3D, there was a decoding bug in Pacific Rim around 1:06:14 (as you can see in the old thread here (http://forum.doom9.org/showthread.php?p=1667236#post1667236)). Recently, I have discovered a similar decoding bug in Flying Swords of Dragon Gate (at 1:23:35). It was therefore urgent to find a solution to that problem. The update of the MVC decoder made by Intel last year was completely bugged, so I have never updated the libmfxsw32.dll included with all previous versions of BD3D2MK3D. But after having noticed the new bug in Dragon Gate, Nico and I have contacted Donald Graft (ex Neuron2 here), and he has been kind enough to try to fix the problem. With the help of Intel and frank (who did several tests on his numerous PCs with hardware acceleration of the 3 beta versions released by Donald) we have now a solution that seems to work fine on (almost) all PCs. :)
Just be sure to use DGMVCSource (instead of FRIMSource, not updated yet). Verify what version you are using with Settings -> MVC Decoder.
However, if you have a recent Intel CPU that supports the hardware acceleration, you might need to update your Intel drivers to use the latest version without problem. Please be sure to do so before posting bug reports here. Also, Intel has dropped the support for some processors, and if there is no recent drivers available, you may have to turn the hardware acceleration off (with Settings -> MVC Decoder -> Hardware Acceleration -> Disabled).
I'm still not sure, but that update *should* also fix the problem of the black frames reported by CaBleman and Iggyrules above. That should be confirmed soon.
Please be sure to post here all problems you may encountered with the current version of the MVC decoders. Thanks in advance!
I want to thank the guys who have helped to finally have a solution to that numerous problems of the Intel decoders: Donald Graft who has kindly accepted to work again on his decoder despite the poor support from Intel, Frank who has spent much time in testing the fixed versions, Nico for his constant help, the developers of the Intel team who have finally released a version of their decoder that seems to work well, and everyone that has posted bug reports about Pacific Rim and helped to identify the problem.
This release of BD3D2MK3D has also a few other changes. They are less important little bug fixes. Note however the new option in the Settings menu: Full-SBS/T&B Aspect Ratio. Previously, when a movie was encoded in Full-SBS or Full-T&B, BD3D2MK3D used 16:9 as the aspect ratio to write in the MKV header, assuming that it's the "final" aspect ratio that has to be specified. That works fine with some hardware or software players, but after the request of someone to specify the aspect ratio of the SBS or T&B composite frame instead, I did some tests with as many players as possible, and I think now that it is better to store 32:9 for Full-SBS and 16:18 for Full-T&B. (Of course, Half-SBS and Half-T&B have still the 16:9 aspect ratio). Therefore, the full aspect ratio is now the default if you encode in Full mode. However, since there may be players that "prefer" the old 16:9 value, I have added the option to specify the desired aspect ratio in the Settings menu.
Note that the hidden option in the config file (introduced in the previous version) has been removed. If you encode in Full mode, please verify in the Settings menu if the current aspect ratio setting corresponds to your needs.
# v0.60 (February 27, 2015)
# - New versions of Neuron2's DGMVCSource.dll (v1.0.0.23) and Intel's libmfxsw32.dll (v6.14.11.28) included. No more decoding bugs in Pacific Rim and Dragon Gate!
# - Little bug in the Convert Subtitles to 3D Tool: The default output format was undefined when the "both" option is selected in tab 2.
# - Added an explanation about the double 3D-depth values used internally by BD3D2MK3D in the 3D-planes.log file and in the Convert Subtitles to 3D Tool.
# - Changed the link called by the help button for the x264 additional options in tab 5, because the old site is closed
# - Added Settings -> Full-SBS/T&B Aspect Ratio option to select the aspect ratio to write in the MKV header when encoding in Full mode.
# - Removed the "full_ar_in_full_mode" hidden option introduced in v0.59 because you can now select that option in the GUI.
As always, you can download the current version here: BD3D2MK3D.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z)
r0lZ
27th February 2015, 12:59
This post was the continuation (from the second post of this thread) of the Version History of BD3D2MK3D. Since the full history is now available here (http://download.videohelp.com/r0lZ/BD3D2AVS/history.txt), it has been removed.
Iggyrules
27th February 2015, 19:55
Thank you for welcoming me to the Doom9 forums, your suggestions and the BD3D2MK3D v0.60 release.
I already ran BD3D2MK3D with the Hardware Acceleration "disabled" (hw=1), and the log verified this setting, but it made no difference. I'm looking forward to running your new BD3D2MK3D v0.60 release later today. I'll post the results once I've finished, hopefully with 100% success.
I'm not sure if this is helpful information, but you can be the judge -
3D Blu-ray is fairly new to me, but I've been performing back-ups of my Blu-ray collection for 8 years. Hardware, OS and Software: VM set-up for AnyDVD HD, Clown BD, BD3D2MK3D...on Windows 7 (x32), 4GB RAM...through an iMac (MB418LL/A), 2.66GHz Intel Core 2 Duo/E7300 (EOL), 8GB RAM, OS X 10.8.5, Synology DS1010+ and DX510, Dune HD TV-303D, Samsung PN64D8000...
r0lZ
27th February 2015, 20:12
If I understand correctly, you run BD3D2MK3D in a VB emulating Windows 7 under your iMac. I wondor how it is still possible to use the Intel hardware acceleration in these circumstances.
Anyway, test v0.60. I hope it will solve your problem.
Iggyrules
27th February 2015, 20:25
You are correct, but you make it easier to understand.
I'm not sure about the hardware acceleration statement. Does that have anything to do with setting it to "disable" (hw=1)? The entire 40GB.iso to .mkv process (w/hardcoded subtitles) currently takes about 3-4 hours (without the output .mkv). Maybe I'll try running Windows 7 in "BOOTCAMP" (utilizes full hardware on a Mac)?
r0lZ
28th February 2015, 00:03
I have tried to say that I'm not sure that your hardware and software (VM under iMac) can be used with the hardware acceleration. To use it, you must install the Intel drivers, that work certainly on a very low level, and can probably not be installed under your emulated Windows. Most emulators do not have direct access to the hardware, and depend of generic drivers that may not support the hardware acceleration. If the MVC decoder tries to use the hardware in that circumstances, it may fail, or work fine, but don't expect miracles. I don't know how the VM works on your Mac, and I can't tell if the bootcamp mode can be beneficial to the Intel decoder, but of course you can try.
It is more bizarre to have bad results without the hardware acceleration. Anyway, try v0.60 with the new decoders in software mode. It should work. At least, I hope so!
The time taken by the encoding is usually slow anyway. The decoding of the AVC and MVC streams only is made by the Intel software lib or by the hardware if you have the right CPU. For that part, using the hardware (when it works!) is of course a big benefit, but the major part of the time spent during the encoding is taken by the x264's encoding process. That part cannot be accelerated. On my machine, without hardware acceleration, I use the preset "veryslow" and processing a whole movie takes normally between 8 and 12 hours, depending of the duration of the movie and the complexity of the images. Hardcoding the subtitles can also slow down considerably the whole process. (The speed does not depends of the size of the ISO, or only a very little bit.) So, IMO, 3-4 hours is very fast. Unless you use a fast preset, it's a very good result. You should not really expect better results without a dedicated PCs running Windows and with a very efficient CPU with hardware acceleration.
Iggyrules
28th February 2015, 02:47
Thanks for the reply.
I'm glad to hear you say 3-4 hours is good process time. I have kept the settings at "CRF", "medium", "film" and "BD Compatible" for every test so far. I downloaded v0.60 and Avatar 3D is currently encoding...so hopefully in the next few hours I'll have something to report.
Iggyrules
28th February 2015, 06:28
I just realized I downloaded v0.59! I checked for update, v0.60 was available to download, I select yes, it downloads, but it's v0.59 when I open it. What is wrong. I've tried COMEPLETELY deleted v0.59 first then downloading v0.60, but it's still v0,59... ????
r0lZ
28th February 2015, 10:38
Oooops! Sorry! I forgot to change the version number inside the exe. But don't worry. Except the version string, the exe you have downloaded is really v0.60 and your tests are relevant.
I have updated the archive with v0.60, this time with the correct version string "0.60". You can download it (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z) if you wish, but it's not really necessary.
Have you finished your first encoding? Is it correct? Have you used the hardware or software mode?
r0lZ
28th February 2015, 10:44
I have kept the settings at "CRF", "medium", "film" and "BD Compatible" for every test so far.
Note that the Film tuning sharpens the image, and that makes it harder to compress. For better compression results, it might be better to leave the tune option to "none". Of course, if you like the sharpened picture and disc size is not a problem for you, you can also leave it to "film".
If you can encode Avatar in 4 hours, your process in very fast! Avatar is a long and difficult movie to encode, especially if you hardcode the (forced) subtitles. On my system, it is one of the longest encode I did, around 15 hours (but with preset "veryslow" and level 4.1). I don't use BD Compatible.
Iggyrules
28th February 2015, 16:25
Still the SAME result…the first 22 seconds of video (3D) and sound (DTS Master) is perfect, then BLACK FRAMES (video) for the remainder of the movie, the audio from the first second until the final second is perfect, the hard coded forced subtitles (3D) are perfect. What should I try next?
Here's the encode log ---
Encoding _ENCODE_3D_MOVIE.avs
Movie: Avatar
Encoding started Fri 02/27/2015 20:24:59.42
Y:\BD3D2MK3D Output\Avatar\00800>"C:\BD3D2MK3D\toolset\x264.
exe" --crf 23 --preset medium --tune film --bluray-compat --profile high --l
evel 4.1 --open-gop --keyint 24 --slices 4 --colormatrix bt709 --colorprim bt7
09 --transfer bt709 --b-pyramid strict --vbv-bufsize 30000 --vbv-maxrate 40000
--aud --frame-packing 3 --qpfile chapters_3D.qpfile --output "00800.264" "_
ENCODE_3D_MOVIE.avs"
avs [info]: 1920x1080p 0:0 @ 24000/1001 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
x264 [info]: profile High, level 4.1
x264 [info]: frame I:10394 Avg QP: 6.04 size: 1236
x264 [info]: frame P:51814 Avg QP: 9.07 size: 263
x264 [info]: frame B:170400 Avg QP:12.68 size: 139
x264 [info]: consecutive B-frames: 2.2% 0.3% 0.4% 97.2%
x264 [info]: mb I I16..4: 99.7% 0.2% 0.1%
x264 [info]: mb P I16..4: 0.0% 0.0% 0.0% P16..4: 0.1% 0.0% 0.0% 0.0% 0
.0% skip:99.7%
x264 [info]: mb B I16..4: 0.0% 0.0% 0.0% B16..8: 0.1% 0.0% 0.0% direct:
0.0% skip:99.9% L0:36.2% L1:58.0% BI: 5.8%
x264 [info]: 8x8 transform intra:0.4% inter:81.7%
x264 [info]: coded y,uvDC,uvAC intra: 0.3% 0.4% 0.2% inter: 0.0% 0.0% 0.0%
x264 [info]: i16 v,h,dc,p: 94% 0% 6% 0%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 39% 9% 32% 4% 2% 4% 2% 5% 3%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 43% 13% 16% 5% 4% 6% 3% 6% 4%
x264 [info]: i8c dc,h,v,p: 100% 0% 0% 0%
x264 [info]: Weighted P-Frames: Y:0.2% UV:0.2%
x264 [info]: ref P L0: 84.0% 12.9% 3.1%
x264 [info]: ref B L0: 98.4% 1.6%
x264 [info]: ref B L1: 97.2% 2.8%
x264 [info]: kb/s:41.33
encoded 232608 frames, 22.97 fps, 41.33 kb/s
Return on error: error code 1, sample_decode.cpp 66
Encoding finished Fri 02/27/2015 23:14:01.26
Y:\BD3D2MK3D Output\Avatar\00800>"C:\BD3D2MK3D\toolset\mkvme
rge.exe" @_MUX_3D_OPTIONS.txt | "C:\BD3D2MK3D\toolset\tee.
exe" "00800.mkvmerge.log"
mkvmerge v7.6.0 ('Garden of Dreams') 32bit built on Feb 8 2015 12:51:39
'00800.264': Using the demultiplexer for the format 'AVC/h.264'.
'00800.track_4352.Eng.dts': Using the demultiplexer for the format 'DTS'.
'00800.264' track 0: Using the output module for the format 'AVC/h.264 (unframed
)'.
'00800.track_4352.Eng.dts' track 0: Using the output module for the format 'DTS'
.
The file 'Avatar 3D.mkv' has been opened for writing.
Progress: 100%
The cue entries (the index) are being written...
Muxing took 1 minute 18 seconds.
Press any key to continue . . .
Iggyrules
28th February 2015, 16:32
I'm not sure what the difference is between "hardware" and "software" modes, so I'm not sure which I've used. How can I tell which I'm using? Currently I double click the application (.exe file) and the GUI opens...
r0lZ
28th February 2015, 17:04
Hum, I've noticed "Return on error: error code 1, sample_decode.cpp 66". Obviously, it's during the decoding operation that the error occurs.
Are you sure that your BD or ISO is fully unprotected? BD3D2MK3D can't process encrypted BDs.
Also, try to decode in sw mode. Use the menu Settings -> MVC Decoder -> Hardware acceleration. Auto is the default and tries to detect the "best" decoding mode automatically according to your hardware. (It may not work correctly because you are running Windows in an emulator.) Use Disabled, that turns off the hardware acceleration. (You can also try Enabled, but I guess that the program will either crash or error out.)
You may also want to try FRIMSource instead of DGMVCSource, but I don't think that will make any difference.
If that solutions do not work, that means probably that you cannot use the Intel decoder under the Windows emulator, and unfortunately there is probably no solution. BD3D2MK3D has not been designed to be run in a Mac emulating Windows. Sorry.
The Settings menu "remembers" your settings, so you can see what has been the options used for your last encode simply by browsing the menu.
You can also have a look at the _ENCODE_3D_MOVIE.avs file. If the last parameter in the interleaved = DGMVCSource(...) command is "hw = 0", then you have run the decoder in automatic mode, and you can't tell what mode has really been used. If it is "hw = 1", then you have used software mode, and the MVC decoding *should* work. With "hw = 2", you have forced the hardware mode, and it's not a good idea!
Iggyrules
28th February 2015, 17:46
I've run the hardware accelerator in "disabled" (hw=1) every time, it is verified in the log, I'll set it to "automatic" (hw=0) and see how that works. I've saved those settings. I'll even decrypt the original again, but I don't think that's the problem. The strange part is I get some parts of the movie to actually to work, perfectly (Transformers & TMNT both play half the movie perfectly...)
r0lZ
28th February 2015, 19:40
Sorry, but I can't help more. Your configuration is very special, and I don't know what could be the cause of the problem.
Iggyrules
28th February 2015, 20:06
I understand. I'm glad you provided all the help you have (thank you!!!). Im going to try a few more things. If I can't resolve this using my Mac I'll try the same .iso on a dedicated windows 7 machine and hopefully that will resolve my problem...
Thank you again for all your help. I'll post my results if your or anyone else is interested. I appreciate your efforts regardless of my results. It's people like you that make my hobby that much more enjoyable.
Doom9 members, has anyone successfully created a BD3D.mkv with forced subtitles using VM Windows 7 from a Mac...?
Good luck to you all.
Iggyrules
r0lZ
1st March 2015, 00:28
Thanks for your kind words, and good luck. I'm curious to know if you can find a solution.
r0lZ
1st March 2015, 15:16
Already a new version.
After the request to rip to 720p by |1313| here (http://forum.doom9.org/showthread.php?p=1711370#post1711370), I have realized that it is not really difficult to add that option, and I did it. There is now a new option in tab 5 to resize to 720p (and another option to select the Avisynth resize filter for that operation). The subtitles are resized too. If you hardcode the subtitles on the video, they are hardcoded before the resize of the video, so the best quality possible should be maintained.
The other important change is the new version of FRIMSource, recompiled with the latest Intel SDK, and that should be fully compatible with the latest Intel MVC decoder and hardware drivers. (@Iggyrules: I doubt that it will solve your problem, but try it anyway!)
# v0.61 (March 1, 2015)
# - Added the possibility to resize the final video to 720p (in tab 5). The subtitles are also resized.
# - Added Settings -> Open Console at Startup.
# - The position of the console is now also saved in the config file (if it is open when the config is saved)
# - Fix: The Preview of the "Move Cinemascope Image Up" option did not work without a DirectShow codec able to open MPLS files. It's uses now the longest M2TS.
# - Minor cosmetic changes
# - Updated FRIMSource to the latest version (v2015-02-28, compatible with libmfxhw32.dll v6.14.11.28). Thanks Videofan3d!
Download: BD3D2MK3D.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z)
Iggyrules
1st March 2015, 16:26
Thanks r0lZ, I'll try the updated FRIMSource.
BTW: I received an error when the MVC decoder started with hardware acceleration forced (hw=2).
r0lZ
1st March 2015, 16:33
OK, the error is normal on your system, and it confirms that your previous tests have been made in sw mode. But it's bad news for you!
Iggyrules
1st March 2015, 16:36
At least I have more confirmations
Thank you for your work r0lZ! :thanks:
r0lZ
1st March 2015, 19:53
No problem! Thanks to you too! ;-)
igvk
1st March 2015, 20:05
I have the following disc image, that is recognized in BD3D2MK3D as shown in the attached image.
14658
Unfortunately, it seems that it converts only the first part from 00001.m2ts (about 4 minutes), not the whole 2 hours 41 minutes.
What can be done to diagnose the problem?
Here is the log contents:
Log file generated by BD3D2MK3D v0.61
Conversion of "F:\Video\Movies\BluRay\AVATAR_3D\BDMV\PLAYLIST\00800.mpls" to Side-by-Side.
Movie title: Avatar
*** Demuxing the streams...
Network Optix tsMuxeR. Version 2.6.9. www.networkoptix.com
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
H.264 muxing fps is not set. Get fps from stream. Value: 23.976
Decoding H264 stream (track 2): H.264/MVC Views: 2 Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
MVC muxing fps is not set. Get fps from stream. Value: 23.976
Decoding DTS-HD stream (track 3): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 5.1 (DTS Master Audio 24bit)
Processed 6445 video frames
Processed 6447 video frames
Flushing write buffer
Demux complete.
Demuxing time: 16 sec
*******************************************************************************
*** Retrieving audio delays from playlist 00800.mpls...
*******************************************************************************
*** Generating the avisynth script...
*** Saving "_ENCODE_3D_MOVIE.avs"...
*** Generating the batch files...
*** Saving "_ENCODE.cmd"
x264 command:
"C:\TOOLS\BD3D2MK3D\toolset\x264.exe" ^
--crf 23 --preset medium ^
--keyint 96 ^
--frame-packing 3 --qpfile chapters_3D.qpfile ^
--output "00800.264" "_ENCODE_3D_MOVIE.avs"
*** Saving "tags.xml"
*** Saving "_MUX_3D.cmd"
*** Saving "_MUX_3D_OPTIONS.txt"
*** Adding attachments...
*** Saving "_MUX_2D.cmd" and "_MUX_2D_OPTIONS.txt"
*** Saving "_POSTPROCESS.cmd"
*** Done. Avisynth script and batch files generated.
Job finished Sun Mar 01 21:56:02 AST 2015
*******************************************************************************
Done with errors!
* Warning: The AVC and MVC video streams do not have the same number of frames: 6445 and 6447. That means that the two streams are probably not synchronised properly, and that encoding this playlist to SBS or T&B may fail.
The script will be generated anyway.
Launch "_ENCODE.cmd" to encode the video (and optionally mux to MKV).
r0lZ
1st March 2015, 22:45
I can't see the image (not yet approved), but the error message in the log is easy to interpret: bad ISO. When there are different numbers of frames in the two video streams, that indicates usually that there are errors in the streams. Furthermore, if tsMuxeR demuxes only 6445 and 6447 frames, that means that the streams are seriously damaged. Sorry, but BD3D requires a good BD3D image as input. Re-rip the BD.
igvk
2nd March 2015, 05:00
Ok, but when I press "Preview M2TS", it shows only "00001.m2ts", which exactly corresponds to the part that is demuxed.
And this ISO can be played fully in PowerDVD.
r0lZ
2nd March 2015, 10:13
OK, I see the image now. I note that the title bar shows the full path to a folder (F:\Video\Movies\BluRay\Avatar...), indicating probably that you have not used a mounted ISO. When the disc image has been mounted, BD3D2MK3D should show something like this in the title bar: "Z:\ - 00800.mpls" (without the quotes).
Apparently, you are running Windows 8. Under Win8, you can mount the disc image (the ISO file) without an external program. It is normally sufficient to double-click it. Try it. That should work.
Of course, if you have ripped the files directly from the BD, you will have to start over, and rip the BD to an ISO instead of as files in a directory. Then mount the ISO. Or you can also process the original BD through AnyDVD HD directly with BD3D2MK3D.
It is ALWAYS a very bad idea to copy the files of a 3DBD (or of its ISO) directly to hard disc. The SSIF files have a complex structure that is totally destroyed when the files are extracted from the BD. Also, you end up with all 3D video files twice: once in the form of the SSIF file, and once as M2TS file, and therefore your copy consumes about two times the disc space of the ISO. The fact that you can play the M2TS files independently but not rip the SSIF files (referenced by the MPLS) is an evidence that something is broken. Delete the files you have copied to disc, and try again with the mounted ISO.
igvk
2nd March 2015, 19:43
Ok, my fault - I was not using ISO image, but files copies.
I am working with mounted ISO now, it looks correct.
Thanks!
frank
4th March 2015, 15:32
TATAAAA!!! :D
BD3D2MK3D v0.61 passed the Pacific Rim Test on new 5. generation Intel CPU I7-5500U (Broadwell) without errors!
New dgMVCdecode.dll and FRIMsource.dll worked fine in HW- and SW-mode. Thanks!
Edit: Latest Intel graphics drivers (2015) are required.
r0lZ
4th March 2015, 15:52
Thanks for the (noisy!) confirmation. :-)
|1313|
6th March 2015, 19:11
Will you add x265 later on or? :)
r0lZ
6th March 2015, 19:23
I don't know. I suppose that that will be useful one day, but currently, h265 is too young and not really supported by most hardware players. Also, I have never used it, and I don't know if it will be easy to add it in BD3D2MK3D.
|1313|
6th March 2015, 19:36
Okey! Thanx for the answer.
frank
9th March 2015, 10:56
Intel has actually updated the drivers for 2nd gen cpu, Sandy Bridge in February!
Now BD3D2MK3D workes properly on Dell XPS (Intel 7, 2nd gen, igfx3000, Sandy Bridge). No more glitches with hardware or software decoding.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.