That error message is not issued directly by BD3D2MK3D. It's probably a third party exe that causes the problem.
Where and when do you see the error message? Do you know what exe is the culprit? Perhaps if I know what exe refuses the path I will be able to do something (although I don't think so).
Anyway, I recommend to encode locally. MkvMerge in particular is very slow when it muxes a file on a network share, and I suppose that everything will be much slower. But if you really want to do it, you can map the network drive, as you have discovered yourself.
BTW, if you want to just move the final file to your NAS, you can also edit __POSTPROCESS_3D.cmd to add a DOS command that will move the final MKV to your preferred location. Or, if you prefer, you can also edit the __MUX_3D_OPTIONS.txt and add the destination path in the --output argument.
If you do it, note that all backslash characters must be doubled, or replaced with normal slash, like this:
--output
\\\\myNAS\\DestinationFolder\\file.mkv
or:
--output
//myNAS/DestinationFolder/file.mkv
(I have never tried the second method, but it should work.)
|