if i ctrl+c 3 times it will kill it which removes it from task manager as well.
done - gmail sent a link to drive since it was larger than 25 megs compressed. Let me know if you are able to access.
I got the dump file, thanks.
Can you try running the command again, after changing to -loglevel info and change -t 0.1 to -t 1. See if it still hangs or works this time.
Also if you feel comfortable installing TightVNC server to give me temporary remote access, that would be helpful.
PS C:\Windows\System32\WindowsPowerShell\v1.0> C:\ProgramData\ChannelsDVR\latest\ffmpeg.exe -hide_banner -nostats -logle
vel info -f lavfi -t 1 -i color=black:640x480 -c:v h264_mf -profile:v high -level 42 -b:v 400k -maxrate:v 600k -f null -
y nul
Input #0, lavfi, from ‘color=black:640x480’:
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 640x480 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc
Stream mapping:
Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (h264_mf))
Press [q] to stop, [?] for help
[h264_mf @ 0000000001da7920] MFT name: ‘Intel« Quick Sync Video H.264 Encoder MFT’
Output #0, null, to ‘nul’:
Metadata:
encoder : Lavf57.71.100
Stream #0:0: Video: h264 (h264_mf), nv12, 640x480 [SAR 1:1 DAR 4:3], q=2-31, 400 kb/s, 25 fps, 25 tbn, 25 tbc
Metadata:
encoder : Lavc57.89.100 h264_mf
[h264_mf @ 0000000001da7920] stream format change
Did it still hang?
Yes - emailing VNC to your support email if you want to look
These guys are amazing. Thanks for the fix!
Thanks has been fixed in the latest DVR build.
I’m not sure if Windows 8.1 has some problem with hardware transcoding, or the issue was specific to @mpfountz’s computer. If someone else has the DVR running on Windows 8.1, let me know if the latest version lets you use hardware transcoding or now.