cannot play transcoded 2d-to-3d VR files with non-english filename

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
yuchih
Posts: 6
Joined: Sat Feb 04, 2023 9:09 pm

cannot play transcoded 2d-to-3d VR files with non-english filename

Post by yuchih »

Hi,
2d-to-3d VR is a great feature in the new UMS.
I tried to play the file with only english file name successfully.
But it seems if the filename contains chinese words, then it will fail to play.
I tried to play it with the vlc player (renderer), it will popup this error message:
Your input can't be opened:
VLC is unable to open the MRL 'http://192.168.0.34:5001/get/51/BigBuck ... ded_to.mpg'. Check the log for details.
Rename the file could solve the issue, but it is better to support filename include non-english characters.
I've attached the debug logs.
Hope this issue could be fixed, thanks.
Attachments
ums_dbg_2023-02-04-17-40.zip
(252.87 KiB) Downloaded 492 times
yuchih
Posts: 6
Joined: Sat Feb 04, 2023 9:09 pm

cannot play transcoded 2d-to-3d VR files mroe than 1 min (with newer version)

Post by yuchih »

After I upgrade UMS to 13.1.0 or 13.2.0, the "transcoded 2d-to-3d VR video" could be started smoothly, but always stop before and around 1 min (1:00), then I cannot seek/play the video anymore.
It is fine to play the video on UMS-13.0.1.
Please check the attachments.
I think this is a critical issue. Hope this could be fixed. Thanks. ;)
Attachments
ums_dbg_2023-02-04-19-22.zip
(237.15 KiB) Downloaded 486 times
User avatar
mik_s
Moderator
Posts: 1158
Joined: Wed Aug 23, 2017 11:03 pm
Location: UK

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by mik_s »

I have emerged these 2 posts as I think they may be the same thing.

As far as I can tell non-English characters in filenames should not cause any problems with playback and I don't see any errors relating to that.

These errors seem to be related to a recent bug that emerged. more info here. This may be the cause if those problems just started happening the past few days.

Code: Select all

DEBUG 2023-02-04 19:20:12.079 [main] net.pms.util.APIUtils Error with HttpURLConnection: {}
java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
	at java.base/sun.nio.ch.NioSocketImpl.read(Unknown Source)
	at java.base/sun.nio.ch.NioSocketImpl$1.read(Unknown Source)
	at java.base/java.net.Socket$SocketInputStream.read(Unknown Source)
	at java.base/sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
	at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
	at java.base/sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(Unknown Source)
	at java.base/sun.security.ssl.SSLSocketImpl.readApplicationRecord(Unknown Source)
	at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(Unknown Source)
	at java.base/java.io.BufferedInputStream.fill(Unknown Source)
	at java.base/java.io.BufferedInputStream.read1(Unknown Source)
	at java.base/java.io.BufferedInputStream.read(Unknown Source)
	at java.base/sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
	at java.base/sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
	at java.base/java.net.HttpURLConnection.getResponseCode(Unknown Source)
	at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
	at net.pms.util.APIUtils.getJson(APIUtils.java:971)
	at net.pms.util.APIUtils.setApiImageBaseURL(APIUtils.java:228)
	at net.pms.PMS.init(PMS.java:631)
	at net.pms.PMS.createInstance(PMS.java:867)
	at net.pms.PMS.main(PMS.java:1021)
TRACE 2023-02-04 19:20:12.079 [main] net.pms.util.APIUtils Did not get imageBaseURL, will attempt to use the database version
TRACE 2023-02-04 19:20:12.080 [main] net.pms.util.APIUtils imageBaseURL could not be fetched from the API or the local database
The other issues I can see is the connection to the renderer being reset by peer in both instances.

Code: Select all

DEBUG 2023-02-04 17:39:48.816 [jupnp-netty-worker-20] org.jupnp.transport.spi.StreamServer Connection error: {}
java.io.IOException: Connection reset by peer
	at java.base/sun.nio.ch.SocketDispatcher.write0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.write(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.write(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.write(Unknown Source)
	at java.base/sun.nio.ch.SocketChannelImpl.write(Unknown Source)
	at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:201)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:146)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:99)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)
	at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
	at org.jboss.netty.channel.Channels.write(Channels.java:725)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.flush(ChunkedWriteHandler.java:274)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:121)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
	at org.jboss.netty.channel.Channels.write(Channels.java:704)
	at org.jboss.netty.channel.Channels.write(Channels.java:671)
	at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:347)
	at net.pms.network.mediaserver.nettyserver.RequestV2.answer(RequestV2.java:799)
	at net.pms.network.mediaserver.nettyserver.RequestHandlerV2.writeResponse(RequestHandlerV2.java:431)
	at net.pms.network.mediaserver.nettyserver.RequestHandlerV2.messageReceived(RequestHandlerV2.java:276)
	at net.pms.network.mediaserver.jupnp.transport.impl.NettyStreamServer$RequestUpstreamHandler.messageReceived(NettyStreamServer.java:192)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.codec.http.HttpChunkAggregator.messageReceived(HttpChunkAggregator.java:145)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
	at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
I know nothing about the VR conversion so can't tell if the problem lies in there. Maybe something here will be of some help.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
yuchih
Posts: 6
Joined: Sat Feb 04, 2023 9:09 pm

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by yuchih »

Sorry for the late reply. I don't think they are the same issue.
For the "cannot play transcoded 2d-to-3d VR files mroe than 1 min" issue:
It is fine in 13.0.1, but just don't work on the newer version. Probably, some new stuff breaks the video playing.
We could track this issue in this thread: viewtopic.php?t=15574

For the "non-english filename" issue, it doesn't work since 13.0.1.
I saw these errors:

Code: Select all

DEBUG 2023-02-04 17:39:45.804 [Thread-34] net.pms.platform.windows.WindowsNamedPipe Waiting for Windows names pipe connection "\\.\pipe\ffmpegvideo_136_1675503585803"
DEBUG 2023-02-04 17:39:46.104 [ffmpeg.exe-8] net.pms.io.ProcessWrapperImpl Starting "C:\Program Files (x86)\Universal Media Server\bin\ffmpeg.exe" -y -loglevel info -i C:\Users\User\AppData\Local\Temp\UMS\UMS-AV~2.AVS -bufsize 7000k -maxrate 89000k -g 5 -q:v 1 -qmin 2 -qmax 3 -ab 448k -ar 48000 -c:a ac3 -c:v mpeg2video -f vob \\.\pipe\ffmpegvideo_136_1675503585803
DEBUG 2023-02-04 17:39:46.106 [ffmpeg.exe-8] net.pms.io.ProcessWrapperImpl Reading pipe: \\.\pipe\ffmpegvideo_136_1675503585803
TRACE 2023-02-04 17:39:46.120 [ffmpeg.exe-8] net.pms.io.BufferedOutputFileImpl Successfully initialized buffer to 52,428,800 bytes.
DEBUG 2023-02-04 17:39:46.120 [ffmpeg.exe-8] net.pms.io.BufferedOutputFileImpl Attaching thread: ffmpeg.exe-8
TRACE 2023-02-04 17:39:46.120 [ffmpeg.exe-8-Timer] net.pms.io.BufferedOutputFileImpl buffered: 0 bytes / inputs: 0
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger ffmpeg version 2022-12-25-git-eeb280f351-essentials_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers
TRACE 2023-02-04 17:39:46.121 [ffmpeg.exe-8-Timer] net.pms.network.webguiserver.ServerSentEvents ServerSentEvents send message: {"id":1,"name":"VLC for desktop","address":"192.168.0.34","icon":"VLC.png","iconOverlays":"","playing":" ","time":" ","progressPercent":0,"isActive":true,"controls":0,"state":{"playback":0,"mute":false,"volume":0,"position":"","duration":"","buffer":0,"name":" "},"action":"renderer_update"}
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   built with gcc 12.1.0 (Rev2, Built by MSYS2 project)
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libvpl --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libavutil      57. 43.100 / 57. 43.100
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libavcodec     59. 55.103 / 59. 55.103
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libavformat    59. 34.102 / 59. 34.102
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libavdevice    59.  8.101 / 59.  8.101
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libavfilter     8. 53.100 /  8. 53.100
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libswscale      6.  8.112 /  6.  8.112
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libswresample   4.  9.100 /  4.  9.100
DEBUG 2023-02-04 17:39:46.127 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger   libpostproc    56.  7.100 / 56.  7.100
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger [avisynth @ 0000023ff255bb00] DirectShowSource: Could not open as video or audio.
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger Video returned:  "DirectShowSource: couldn't open file D:\UMS_SHARE\BigBuckBunny_大雄兔.mp4:
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger ����ΦW�٧䤣��C"
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger Audio returned:  "DirectShowSource: couldn't open file D:\UMS_SHARE\BigBuckBunny_大雄兔.mp4:
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger ����ΦW�٧䤣��C"
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger 
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger (C:\Users\User\AppData\Local\Temp\UMS\UMS-AV~2.AVS, line 5)
DEBUG 2023-02-04 17:39:46.140 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger C:\Users\User\AppData\Local\Temp\UMS\UMS-AV~2.AVS: Unknown error occurred
TRACE 2023-02-04 17:39:46.306 [jupnp-netty-worker-19] net.pms.dlna.DLNAResource Sleeping for 2500 milliseconds
TRACE 2023-02-04 17:39:47.144 [ffmpeg.exe-8] net.pms.io.BufferedOutputFileImpl EOF
INFO  2023-02-04 17:39:47.144 [ffmpeg.exe-8] net.pms.io.ProcessWrapperImpl Process C:\Program Files (x86)\Universal Media Server\bin\ffmpeg.exe has a return code of 1! Maybe an error occurred... check the log file
TRACE 2023-02-04 17:39:48.121 [ffmpeg.exe-8-Timer] net.pms.io.BufferedOutputFileImpl buffered: 0 bytes / inputs: 0
TRACE 2023-02-04 17:39:48.121 [ffmpeg.exe-8-Timer] net.pms.network.webguiserver.ServerSentEvents ServerSentEvents send message: {"id":1,"name":"VLC for desktop","address":"192.168.0.34","icon":"VLC.png","iconOverlays":"","playing":" ","time":" ","progressPercent":0,"isActive":true,"controls":0,"state":{"playback":0,"mute":false,"volume":0,"position":"","duration":"","buffer":0,"name":" "},"action":"renderer_update"}

Probably, ffmpeg.exe doesn't accept non-english filename?
User avatar
mik_s
Moderator
Posts: 1158
Joined: Wed Aug 23, 2017 11:03 pm
Location: UK

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by mik_s »

Could you try the latest version (13.2.0) as that fixed the problem I saw in you last logs that may have been part of the problem, and post new logs.

You could also try playing that file on another renderer or using the web player to see if those have trouble with the filenames.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
yuchih
Posts: 6
Joined: Sat Feb 04, 2023 9:09 pm

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by yuchih »

For the "non-english filename" issue, I tried 13.2.0 and the early access 13.2.1. This issue still existing.
This error may be pointing to the root cause:

Code: Select all

DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger Video returned:  "DirectShowSource: couldn't open file D:\UMS_SHARE\BigBuckBunny_大雄兔.mp4:
DEBUG 2023-02-04 17:39:46.139 [ffmpeg.exe-8-2] net.pms.io.OutputTextLogger ����ΦW�٧䤣��C"
2023-03-05 135441-use-ffms2.png
2023-03-05 135441-use-ffms2.png (86.68 KiB) Viewed 5665 times
After I checked the "use ffms2 instead of DirectShowSource", the file with non-english filename is able to play.
User avatar
mik_s
Moderator
Posts: 1158
Joined: Wed Aug 23, 2017 11:03 pm
Location: UK

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by mik_s »

I know little about the transcoding side of things so I don't fully know what is happening, but from what I can tell it is using a tool that is part of AviSynth called DirectShowSource and it cannot understand that filename for some reason. I don't know if the problem is in that program or to do with how UMS sends the command to it.
FFMS2 might not have this problem so is why that works.

As I understand it this uses an AVS script to run the 3D conversion which is sent to FFmpeg. There may be a problem in the creation of this script.

Code: Select all

Starting "C:\Program Files (x86)\Universal Media Server\bin\ffmpeg.exe" -y -loglevel info -i C:\Users\User\AppData\Local\Temp\UMS\UMS-AV~2.AVS -bufsize 7000k -maxrate 89000k -g 5 -q:v 1 -qmin 2 -qmax 3 -ab 448k -ar 48000 -c:a ac3 -c:v mpeg2video -f vob \\.\pipe\ffmpegvideo_136_1675503585803

Code: Select all

C:\Users\User\AppData\Local\Temp\UMS\UMS-AV~2.AVS: Unknown error occurred
Could you see if you can find this script and post it here? You should try playing that file again so that a new AVS script is generated as being a temporary file it may have already been deleted. Could you do this with using DirectShowSource and FFMS2 so I can compare them?
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
vruser
Posts: 10
Joined: Fri Oct 07, 2022 5:57 pm

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by vruser »

Hi, I didn't see this thread until now. DirectShowSource uses native codecs, typically supplied by the K-Kite codec pack, if my install guidance was followed. These can leverage GPU hardware. I introduced FFMS2, which is based on FFMpeg, as it does not need native codecs to read many file types so it is more general and in many cases, depending on the version, may do the conversion entirely in software. These two AviSynth "Sources" will have radically different implementations, different capabilities interns of file naming conventions that they can read, file types that they can open and performance will differ. I moved away from FFMS2 when I discovered the K-Lite Codec pack as I was looking for the performance necessary to support 2D to 3D conversion and native codecs have better performance. If FFMS2 works and is fast enough for the files you want to view, then use it. If you have performance issues try using the default DirectShowSource. I hope this helps. There are many variables and system configurations out there. I don't get enough (hardly any) feedback on what is working and what isn't. I did a lot of testing, but obviously limited to my own hardware.
yuchih
Posts: 6
Joined: Sat Feb 04, 2023 9:09 pm

Re: cannot play transcoded 2d-to-3d VR files with non-english filename

Post by yuchih »

@mik_s, sure, I've attached the scripts. It seems the only difference is this line:

Code: Select all

//FFMS2
FFMS2("D:\UMS_SHARE\BigBuckBunny_大雄兔.mp4", fpsnum=24, fpsden=1, cachefile="C:\Users\User\AppData\Local\Temp\UMS\ums-avs-BigBuckBunny_大雄兔.mp4.ffindex", atrack=-1, seekmode=2)
//DirectShowSource
DirectShowSource("D:\UMS_SHARE\BigBuckBunny_大雄兔.mp4", fps=24, convertfps=true).AssumeFPS(24,1)
Please check the files. Thanks.

@vruser, thanks for your explanation.
Then I will switch to use DirectShowSource to play the english-filename videos.
To play the non-english-filename video, FFMS2 seems slower but workable on my PC(cpu: intel 13600k, gpu: nvidia 3060-ti, RAM: 32GB).
Could you check another issue I posted here: viewtopic.php?t=15574&start=10
I only can watch 2d-to-3d video (with english-filename) smoothly on the version 13.0.1 now. :(
Attachments
ums-avs.zip
(1.48 KiB) Downloaded 477 times
Post Reply