Not Sure Which Log Need To Be Reviewed.
@GoRichard said:
@cjmurphNot Sure Which Log Need To Be Reviewed.
The logs for Plex itself, not the service.
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Well Yes, I Downloaded The Logs But I Do Not Know Which One Needs To Be Reviewed. There Are A Total Of 147 Separate Log Files.
The Log For PlexService_1.1.5, Shows This :
4/6/2018 5:54:57 PM: Plex Media Server Started.
4/6/2018 5:54:57 PM: Plex Media Server has stopped!
4/6/2018 5:54:57 PM: Plex Update Service Stopped.
4/6/2018 5:54:57 PM: Waiting 90 seconds before re-starting the Plex process.
4/6/2018 5:56:27 PM: Plex executable found at C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
4/6/2018 5:56:27 PM: Successfully set the 'FirstRun' registry key to 0
4/6/2018 5:56:27 PM: Attempting to start Plex
4/6/2018 5:56:27 PM: Plex Media Server version is 1.12.2.4929. Can use startup argument.
4/6/2018 5:56:28 PM: Plex Media Server Started.
4/6/2018 5:56:28 PM: Plex Media Server has stopped!
4/6/2018 5:56:28 PM: Plex Update Service Stopped.
4/6/2018 5:56:28 PM: Waiting 90 seconds before re-starting the Plex process.
4/6/2018 5:57:58 PM: Plex executable found at C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
4/6/2018 5:57:58 PM: Successfully set the 'FirstRun' registry key to 0
4/6/2018 5:57:58 PM: Attempting to start Plex
4/6/2018 5:57:58 PM: Plex Media Server version is 1.12.2.4929. Can use startup argument.
4/6/2018 5:57:58 PM: Plex Media Server Started.
4/6/2018 5:57:59 PM: Plex Media Server has stopped!
4/6/2018 5:57:59 PM: Plex Update Service Stopped.
4/6/2018 5:57:59 PM: Waiting 90 seconds before re-starting the Plex process.Yep, as I said, the service logs are not going to help, you need the log for Plex itself to determine why it crashes.
The log will be called Plex media server log or something like that.
It’s not the service that’s crashing, it’s Plex. You need to look at the Plex server logs to work out why.
Hasta luego
On Sat, Apr 7, 2018, 2:18 AM cjmurph forums+d93994-s6025034@plex.tv wrote:
Plex Forums https://forums.plex.tv/
cjmurph commented on PMS as a serviceYep, as I said, the service logs are not going to help, you need the log
for Plex itself to determine why it crashes.The log will be called Plex media server log or something like that.
It’s not the service that’s crashing, it’s Plex. You need to look at the
Plex server logs to work out why.–
Reply to this email directly or follow the link below to check it out:
https://forums.plex.tv/discussion/comment/1648461#Comment_1648461Note: Your signature will be included when replying directly by email
unless you remove it first. Attachments will not be included when replying.Check it out:
https://forums.plex.tv/discussion/comment/1648461#Comment_1648461
@v3000 said:
Hasta luegoOn Sat, Apr 7, 2018, 2:18 AM cjmurph wrote:
Plex Forums https://forums.plex.tv/
cjmurph commented on PMS as a serviceYep, as I said, the service logs are not going to help, you need the log
for Plex itself to determine why it crashes.The log will be called Plex media server log or something like that.
It’s not the service that’s crashing, it’s Plex. You need to look at the
Plex server logs to work out why.–
Reply to this email directly or follow the link below to check it out:
https://forums.plex.tv/discussion/comment/1648461#Comment_1648461Note: Your signature will be included when replying directly by email
unless you remove it first. Attachments will not be included when replying.Check it out:
https://forums.plex.tv/discussion/comment/1648461#Comment_1648461
Not Sure What I’m Suppose To Do With This…
@GoRichard said:
Not Sure What I’m Suppose To Do With This…
With that other dude saying see ya later or with the info I gave you?
the log is called “Plex Media Server.log” as per the link I gave you it is found in the logs folder within your plex media server library folder. the default location of the library folder is within your user folder “%LOCALAPPDATA%\Plex Media Server\Logs”. Personally, I have moved mine, you may have done the same. It should also be in the logs you downloaded though the web interface.
open it in a text editor and find the timestamps that correlate to the times plex stops in the service logs. for example, from your logs above:
4/6/2018 5:56:28 PM: Plex Media Server has stopped!
There is something about your specific configuration of plex that is causing it to fail when run in session 0 (as a service). Lots of resources are not available when run as a service. The most common problem people have is with mapped drives. That does not seem to be your problem as it typically just makes your library unavailable but doesnt crash plex. You may have located your plex library/config folder on a mapped drive though. That would probably make it crash.
duplicate post
@cjmurph
Have you seen any issues with MS Windows 1803 SC build?
Issue:
Been running fine for months, but was forced to update to Windows 1803 like a lot of people, and now when a stream starts that needs to transcode, PMS immediately crashes. The service wrapper will restart it, but as soon as another transcode starts, it goes down. When I run PMS as a normal application (as the same accnt as the service), everything is fine, HW encode/decode is working great. Didn’t update any other software/hardware configuration other than the 1803 update and my video card drivers to the latest. I can scan libraries, and do almost anything else to include direct play/stream.
Here’s some info about my rig:
Environment:
OS: Windows 10 Enterprise 64-bit 1803 SCU
CPU: Intel® Core™ i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
GPU: Intel HD Graphics 530 (integrated graphics)
Display Memory: 16231 MB
Dedicated Memory: 128 MB
Shared Memory: 16103 MB
RAM: 32GB
Libraries: All on local USB HDD enclosure
PMS:
PMS: Version 1.13.0.5003 (PlexPass)
Running as local admin account
PMS Settings:
Transcoder quality: Automatic
Transcoder temp dir: Local system SSD
Transcoder default throttle buffer: 180
Background transcoding x264 preset: Medium
Use hardware acceleration when available: Enable
Maximum simultaneous video transcode: 6
T-shooting:
- Updated Intel drivers to latest
- Wiped out the codecs folder. (All codecs are regenerated upon transcode session start)
- Tried system account - same thing
- Haven’t tried with “A LOT” of players, but doesn’t seem to matter.
LOGS:
When running as a service it will crash right after the last line:
May 02, 2018 19:20:15.055 [9756] WARN - Couldn't determine bundle identifier for plug-in at: "C:\plex\Plex Media Server\Plug-ins\GoogleMusic.bundle"
May 02, 2018 19:20:16.605 [20732] WARN - Request for plug-in [com.plexapp.plugins.Cast] but it doesn't exist.
May 02, 2018 19:20:16.743 [4804] ERROR - [FFMPEG] - Failed to create Direct3D device
May 02, 2018 19:20:16.746 [4804] ERROR - [FFMPEG] - Cannot load nvEncodeAPI.dll
May 02, 2018 19:20:16.746 [4804] ERROR - [FFMPEG] - The minimum required Nvidia driver for nvenc is 378.66 or newer
May 02, 2018 19:20:16.746 [4804] WARN - avcodec_open2 returned -1313558101 for encoder 'h264_nvenc'
May 02, 2018 19:20:16.979 [4804] INFO - [FFMPEG] - MFT name: 'Intel® Quick Sync Video H.264 Encoder MFT'
The “plex crash uploader.log” also shows this:
May 02, 2018 19:20:17.170 [24512] INFO - Crash Uploader - Platform: windows-i386 (10.0 (Build 17134)) ServerUUID: 4b2718d1a78ac210f0049ee9c8fxxxxxxxxxxx UserId: seanxxxxxxxxxxail.com Version: 1.13.0.5003-8fcb5b6e5
May 02, 2018 19:20:20.800 [23412] INFO - Successfully reported 7c71b1fd-644a-4522-a08e-d82xxxxxxxxxxxx
When running as an application, the same log output will be generated as above but then continue with the below logs:
May 02, 2018 19:35:14.178 [20868] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 2827800 is out of range for mov/mp4 format
May 02, 2018 19:35:14.349 [24056] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 3670300 is out of range for mov/mp4 format
May 02, 2018 19:35:14.472 [13072] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 4341800 is out of range for mov/mp4 format
May 02, 2018 19:35:14.753 [20868] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 5501300 is out of range for mov/mp4 format
May 02, 2018 19:35:15.203 [24056] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 7774400 is out of range for mov/mp4 format
May 02, 2018 19:35:16.816 [16316] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 15986800 is out of range for mov/mp4 format
May 02, 2018 19:35:17.830 [9736] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 20979300 is out of range for mov/mp4 format
May 02, 2018 19:35:17.941 [9924] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 21521500 is out of range for mov/mp4 format
May 02, 2018 19:35:18.175 [13072] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 22393200 is out of range for mov/mp4 format
May 02, 2018 19:35:19.851 [22880] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 22580900 is out of range for mov/mp4 format
May 02, 2018 19:35:20.135 [18408] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 23865500 is out of range for mov/mp4 format
May 02, 2018 19:35:21.403 [22880] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 24411900 is out of range for mov/mp4 format
May 02, 2018 19:35:21.541 [13072] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 25025000 is out of range for mov/mp4 format
May 02, 2018 19:35:21.694 [18408] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 25725700 is out of range for mov/mp4 format
May 02, 2018 19:35:21.727 [22880] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 25855000 is out of range for mov/mp4 format
May 02, 2018 19:35:23.964 [18408] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 26255400 is out of range for mov/mp4 format
May 02, 2018 19:35:44.408 [20868] INFO - [FFMPEG] - Initialized an internal MFX session using hardware accelerated implementation
Any ideas?
@seanvree81 not sure why this is being raised in the service wrapper forum thread. it is a Plex Media Server crash as you indicated. Please ensue debug logging is enabled on the server. Disable auto restart in the wrapper. Restart the server to get fresh logs created. On getting the crash - restart the server and download the logs zip and attach to a Plex Media Server forum topic
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
@sa2000 I"m confused. That’s when it’s crashing…when I"m using it with the service wrapper. When it’s running as the standard stand-alone application, everything works fine.
I’ll get more detailed logs for you.
Thanks,
@seanvree81 said:
@sa2000 I"m confused. That’s when it’s crashing…when I"m using it with the service wrapper. When it’s running as the standard stand-alone application, everything works fine.I’ll get more detailed logs for you.
Thanks,
sorry I missed that aspect.
I am aware some hardware transcoding issues when run as a service because there is no desktop
either way will need debug logging in Plex Media Server log leading up to the crash and also ideally going back to when Plex Media Server was launched
And would need the full content of the crash uploader log files to locate the dump
@sa2000 no problem brother I know you’re a hard workin’ dude helping us out. appreciate it.
I agree with you, using a wrapper is not ideal…which I’ll refer to PLEX about. But thanks to the good man who made this piece of kit, it makes things easier.
But yes, you’re right there are issues with transcoding, but I’ve been running it like this for a LONG time with very little issues. NO doubt there is a codec/driver/etc issue here, just not sure if it’s intel, PLEX, windows, the wrapper or all of the above.
I performed the steps as you suggested - Enabled DEBUG, shut down PMS, disabled auto-restart on the wrapper, wiped the logs, and started again. This time she crashed almost instantly.
Here’s the logs:
https://drive.google.com/open?id=1hY0ysp2bNlFp44xnUewA2Ur_ZWJcHFAm
Again, thanks for your help.
@seanvree81 said:
@sa2000 no problem brother I know you’re a hard workin’ dude helping us out. appreciate it.I agree with you, using a wrapper is not ideal…which I’ll refer to PLEX about. But thanks to the good man who made this piece of kit, it makes things easier.
But yes, you’re right there are issues with transcoding, but I’ve been running it like this for a LONG time with very little issues. NO doubt there is a codec/driver/etc issue here, just not sure if it’s intel, PLEX, windows, the wrapper or all of the above.
I performed the steps as you suggested - Enabled DEBUG, shut down PMS, disabled auto-restart on the wrapper, wiped the logs, and started again. This time she crashed almost instantly.
Here’s the logs:
PMS_WIN_03_may_18.rar - Google Drive
Again, thanks for your help.
Could you shutdown the service and Plex Media Server and then launch outside the service and replicate the sequence playing from an iOS device through WAN the media file Jerry Maguire (1996)
and get me the debug logs to compare
We are crashing within an intel driver mfx_mft_h264ve_32.dll called from bundled Plex Media Server codec file avcodec-58.dll
@seanvree81 said:
@cjmurph
Have you seen any issues with MS Windows 1803 SC build?Issue:
Been running fine for months, but was forced to update to Windows 1803 like a lot of people, and now when a stream starts that needs to transcode, PMS immediately crashes. The service wrapper will restart it, but as soon as another transcode starts, it goes down. When I run PMS as a normal application (as the same accnt as the service), everything is fine, HW encode/decode is working great. Didn’t update any other software/hardware configuration other than the 1803 update and my video card drivers to the latest. I can scan libraries, and do almost anything else to include direct play/stream.Here’s some info about my rig:
Environment:
OS: Windows 10 Enterprise 64-bit 1803 SCU
CPU: Intel(R) Core™ i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
GPU: Intel HD Graphics 530 (integrated graphics)
Is the windows release an insider track release ?
And you can confirm that the crashes are not tied to a specific Plex Media Server version upgrade?
And any intel driver changes?
@sa2000 said:
Could you shutdown the service and Plex Media Server and then launch outside the service and replicate the sequence playing from an iOS device through WAN the media file
Jerry Maguire (1996)
and get me the debug logs to compareWe are crashing within an intel driver
mfx_mft_h264ve_32.dllcalled from bundled Plex Media Server codec fileavcodec-58.dll
Yeah, I can get you the comparison logs…will take me several hours as I’m an android guy. But I think I can get that comparison to you.
No, the server is on Windows Update Semi-Annual Channel.
The crashes NEVER occurred before the update to 1803. I can absolutely confirm this is not associated with a PMS update.
This started immediately after updating windows 1803. As far as the intel GPU driver update - I think it was updated with the Windows 1803 build, but I can’t really tell now that it’s already updated. I tried to roll back to the previous intel driver version for the GPU, but Windows just immediately installs the newer version.
@seanvree81 said:
@sa2000 said:
Could you shutdown the service and Plex Media Server and then launch outside the service and replicate the sequence playing from an iOS device through WAN the media file
Jerry Maguire (1996)
and get me the debug logs to compareWe are crashing within an intel driver
mfx_mft_h264ve_32.dllcalled from bundled Plex Media Server codec fileavcodec-58.dllYeah, I can get you the comparison logs…will take me several hours as I’m an android guy. But I think I can get that comparison to you.
No, the server is on Windows Update Semi-Annual Channel.
The crashes NEVER occurred before the update to 1803. I can absolutely confirm this is not associated with a PMS update.
This started immediately after updating windows 1803. As far as the intel GPU driver update - I think it was updated with the Windows 1803 build, but I can’t really tell now that it’s already updated. I tried to roll back to the previous intel driver version for the GPU, but Windows just immediately installs the newer version.
What we have for the crash is the stack frames
STACK_TEXT:
08f1d398 55a6fbda 051c2e80 08f1d3dc c9c2bb5e 0x0
08f1d498 55a97818 08f1d4b8 08f1d4b4 02442100 mfx_mft_h264ve_32+0xfbda
08f1d4d8 57fdb731 04e157a0 00000000 00000002 mfx_mft_h264ve_32+0x37818
08f1dc00 00000000 00000000 58066ea0 0000001b avcodec_58+0x18b731
All within the intel driver
and
0:051> .ecxr
Unable to load image C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfx_mft_h264ve_32.dll
*** ERROR: Module load completed but symbols could not be loaded for mfx_mft_h264ve_32.dll
eax=051d8360 ebx=08f1d4b4 ecx=00000000 edx=08f1d3dc esi=00000000 edi=04e157a0
eip=00000000 esp=08f1d39c ebp=08f1d498 iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
00000000 ?? ???
@sa2000 I’m not sure what all of that means. However, here are the logs from an Apple 6S on the WAN. Transcoded " E:\Movies\Jerry Maguire (1996)\Jerry Maguire (1996) Remux-1080p.mp4 " for approx 3 minutes without crash.
https://drive.google.com/file/d/1jhs2H9fZ9HuPlIdt3idHS54XpkC11-tf/view?usp=sharing
@seanvree81 said:
@sa2000 I’m not sure what all of that means. However, here are the logs from an Apple 6S on the WAN. Transcoded " E:\Movies\Jerry Maguire (1996)\Jerry Maguire (1996) Remux-1080p.mp4 " for approx 3 minutes without crash.
Thank you
I will look into it later - have to go out now
I didn’t read all the thread but I can tell you the crashes started with the latest PLEX release 1.13.0.5003. I started a thread on that to which I’ve received no response. I just got the 1803 update today and the crash of the PMS server for every stream is still present. Can’t use Plex for Live TV on my ROKU, my AppleTV or via the web interface.
Needs attention NOW. In the mean time, how can we roll back a version???
@seanvree81 said:
@cjmurph
Have you seen any issues with MS Windows 1803 SC build?Issue:
Been running fine for months, but was forced to update to Windows 1803 like a lot of people, and now when a stream starts that needs to transcode, PMS immediately crashes. The service wrapper will restart it, but as soon as another transcode starts, it goes down. When I run PMS as a normal application (as the same accnt as the service), everything is fine, HW encode/decode is working great. Didn’t update any other software/hardware configuration other than the 1803 update and my video card drivers to the latest. I can scan libraries, and do almost anything else to include direct play/stream.Here’s some info about my rig:
Environment:
OS: Windows 10 Enterprise 64-bit 1803 SCU
CPU: Intel(R) Core™ i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
GPU: Intel HD Graphics 530 (integrated graphics)
Display Memory: 16231 MB
Dedicated Memory: 128 MB
Shared Memory: 16103 MB
RAM: 32GB
Libraries: All on local USB HDD enclosurePMS:
PMS: Version 1.13.0.5003 (PlexPass)
Running as local admin accountPMS Settings:
Transcoder quality: Automatic
Transcoder temp dir: Local system SSD
Transcoder default throttle buffer: 180
Background transcoding x264 preset: Medium
Use hardware acceleration when available: Enable
Maximum simultaneous video transcode: 6T-shooting:
- Updated Intel drivers to latest
- Wiped out the codecs folder. (All codecs are regenerated upon transcode session start)
- Tried system account - same thing
- Haven’t tried with “A LOT” of players, but doesn’t seem to matter.
LOGS:
When running as a service it will crash right after the last line:
May 02, 2018 19:20:15.055 [9756] WARN - Couldn't determine bundle identifier for plug-in at: "C:\plex\Plex Media Server\Plug-ins\GoogleMusic.bundle" May 02, 2018 19:20:16.605 [20732] WARN - Request for plug-in [com.plexapp.plugins.Cast] but it doesn't exist. May 02, 2018 19:20:16.743 [4804] ERROR - [FFMPEG] - Failed to create Direct3D device May 02, 2018 19:20:16.746 [4804] ERROR - [FFMPEG] - Cannot load nvEncodeAPI.dll May 02, 2018 19:20:16.746 [4804] ERROR - [FFMPEG] - The minimum required Nvidia driver for nvenc is 378.66 or newer May 02, 2018 19:20:16.746 [4804] WARN - avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' May 02, 2018 19:20:16.979 [4804] INFO - [FFMPEG] - MFT name: 'Intel® Quick Sync Video H.264 Encoder MFT'The “plex crash uploader.log” also shows this:
May 02, 2018 19:20:17.170 [24512] INFO - Crash Uploader - Platform: windows-i386 (10.0 (Build 17134)) ServerUUID: 4b2718d1a78ac210f0049ee9c8fxxxxxxxxxxx UserId: seanxxxxxxxxxxail.com Version: 1.13.0.5003-8fcb5b6e5 May 02, 2018 19:20:20.800 [23412] INFO - Successfully reported 7c71b1fd-644a-4522-a08e-d82xxxxxxxxxxxxWhen running as an application, the same log output will be generated as above but then continue with the below logs:
May 02, 2018 19:35:14.178 [20868] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 2827800 is out of range for mov/mp4 format May 02, 2018 19:35:14.349 [24056] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 3670300 is out of range for mov/mp4 format May 02, 2018 19:35:14.472 [13072] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 4341800 is out of range for mov/mp4 format May 02, 2018 19:35:14.753 [20868] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 5501300 is out of range for mov/mp4 format May 02, 2018 19:35:15.203 [24056] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 7774400 is out of range for mov/mp4 format May 02, 2018 19:35:16.816 [16316] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 15986800 is out of range for mov/mp4 format May 02, 2018 19:35:17.830 [9736] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 20979300 is out of range for mov/mp4 format May 02, 2018 19:35:17.941 [9924] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 21521500 is out of range for mov/mp4 format May 02, 2018 19:35:18.175 [13072] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 22393200 is out of range for mov/mp4 format May 02, 2018 19:35:19.851 [22880] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 22580900 is out of range for mov/mp4 format May 02, 2018 19:35:20.135 [18408] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 23865500 is out of range for mov/mp4 format May 02, 2018 19:35:21.403 [22880] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 24411900 is out of range for mov/mp4 format May 02, 2018 19:35:21.541 [13072] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 25025000 is out of range for mov/mp4 format May 02, 2018 19:35:21.694 [18408] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 25725700 is out of range for mov/mp4 format May 02, 2018 19:35:21.727 [22880] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 25855000 is out of range for mov/mp4 format May 02, 2018 19:35:23.964 [18408] ERROR - [Transcoder] [mp4 @ 069bbb80] Application provided duration: -69 / timestamp: 26255400 is out of range for mov/mp4 format May 02, 2018 19:35:44.408 [20868] INFO - [FFMPEG] - Initialized an internal MFX session using hardware accelerated implementationAny ideas?
