I don't think BD3D2MK3D could be the culprit, It creates only a AVS script with (basically) this:
Code:
LoadPlugin("D:\Tcl\work\BD3D2MK3D\toolset\FRIMSource.dll")
#LoadPlugin("D:\Tcl\work\BD3D2MK3D\toolset\DGMVCDecode.dll")
# Load the two video streams (192000 frames per stream)
interleaved = FRIMSource("mvc", "00001.track_4113.264", "00001.track_4114.mvc", num_frames = 192000, cache = 2, platform = "")
#interleaved = DGMVCSource("00001.track_4113.264", "00001.track_4114.mvc", view = 0, frames = 192000, mode = "auto") # Old syntax for mode: hw = 0
# Current base view: left eye.
# The views are in the common order: AVC stream = left view, MVC stream = right view.
left = SelectEven(interleaved)
right = SelectOdd(interleaved)
# Build Side-by-Side stream
StackHorizontal(HorizontalReduceBy2(Left), HorizontalReduceBy2(Right))
In this example, the platform mode is left to automatic. The plugin should use the hardware decoder if it is available. You can also force sw or hw mode from the GUI, but it's normally not necessary.
That script is then encoded in h264 or h265 with a shell script containing a command similar to this:
Code:
"D:\Tcl\work\BD3D2MK3D\toolset\avs2yuv.exe" ^
"__ENCODE_3D_MOVIE.avs" -frames 192240 -o - ^
| "D:\Tcl\work\BD3D2MK3D\toolset\x264_8bit_x64.exe" ^
--crf 22 --preset slow --level 4.1 --vbv-bufsize 78125 --vbv-maxrate 62500 ^
--sar 1:1 --range tv --colormatrix bt709 ^
--frame-packing 3 --qpfile chapters_3D.qpfile --frames 192240 --fps 24000/1001 ^
--output "00001_3D.264" --demuxer y4m --stdin y4m -
That .CMD script is launched directly by the user and runs therefore in a command prompt window, totally independent to BD3D2MK3D.