1

I'm using ffmpeg for transcoding of my videos on a HP Blade dedicated server with these details:

OS: Windows Server 2012 R2 64Bit
CPU: Intel XEON X5650
RAM: 16GB
Hard disk: A sas normal disk

This command is a sample for creating qualities which has 4K as top level and I use this command for creating lower qualities from that as parallel at the same time.

ffmpeg -i input.mp4 -filter_complex 
[0:v]split=4[s0][s1][s2][s3];
[s0]scale=uhd2160[v0];
[s1]scale=hd1080[v1];
[s2]scale=hd720[v2];
[s3]scale=hd480[v3];
[s4]scale=nhd[v4];
[s5]scale=cga[v5]
-map [v0] -map [v1] -map [v2] -map [v3] -map [v4] -map [v5] -map 0:a 
-c:v libx264 -c:a aac -f tee -g 48 -threads 0 
"[select='v\:0,a':f=hls:hls_list_size=0:hls_time=6]../video/2160p/out.m3u8| 
 [select='v\:1,a':f=hls:hls_list_size=0:hls_time=6]../video/1080p/out.m3u8| 
 [select='v\:2,a':f=hls:hls_list_size=0:hls_time=6]../video/720p/out.m3u8| 
 [select='v\:3,a':f=hls:hls_list_size=0]../video/480p/out.m3u8| 
 [select='v\:3,a':f=hls:hls_list_size=0:hls_time=6]video/360p/out.m3u8| 
 [select='v\:3,a':f=hls:hls_list_size=0:hls_time=6]video/200p/out.m3u8"

Some times in transcoding time windows goes to reconnecting and count up to 20 and then goes to black screen. I cannot find anythings in windows logs. And finally I restart server from button of that server. What's hapenning? How can I find a clue, about this issue? Any one know anything about this issue?

  • Is it a single command? If yes then add backslash after every line and use it from a batch file. – Biswapriyo Feb 9 at 8:19
  • Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you have created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem. – fixer1234 Feb 9 at 8:57
  • Do you have enough free disk space on the system disk? – harrymc Feb 9 at 10:03
  • @harrymc Yes I have – parsa Feb 9 at 10:32
  • Ideas: Look in the Event Viewer for information of what happened. Use BlueScreenView to see if you had Windows crashes and to analyze them. – harrymc Feb 9 at 10:41
0

Tools to analyze such a problem:

  • Look in the Event Viewer for information of what happened.
  • Use BlueScreenView to see if you had Windows crashes and for help in analyzing them.
  • After about 1 week, the server crashed again – parsa Feb 18 at 5:35
  • These are analysis tools. But what have you found? What does BlueScreenView show? Add screenshots if you want us to have a look. Or use another conversion utility. – harrymc Feb 18 at 7:39
  • It showed that log of last crashed that related to hal.dll. I Update hal.dll, but cashing occured again, After last crash, in BlueScreenView there are not any new crash log. But it occured again – parsa Feb 19 at 15:34
  • You can't update hal.dll - it's an essential Windows component that only Windows can update. What was done? – harrymc Feb 19 at 16:06
  • In some servers,hal.dll was update, and in some of servers os couldn't run – parsa Feb 20 at 6:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.