Transcoding Go Pro format to Samsung TV

[BTVCON]

Dear Mezzmo,

I am having problems playing go Pro footage on my Samsung TV (ES8000 with Evo Kit). I very rarely have any problems playing anything on this TV from Mezzmo but for some reason the Go Pro format is no recognized by the TV.

I have trans-coded to Matroska H264 AC3 as per the recommended settings but still no joy. As a note the transcoding does not take long as it runs at over 1500 fps.

Have you had any previous issues with Go Pro formats on Samsung TV's.

Below is the Go-Pro format that I am having issue with.

954

Any help would be much appreciated.

PS Keep up the good work.

Regards

Brett

[Paul]

Hi Brett,

Right-click on one of your Go Pro videos in Mezzmo and click 'Get FFmpeg Information'. Post that information here or email it to us at support [at] conceiva [dot] com. Also, let us know what device profile that is assigned to your TV in the Media Devices dialog in Mezzmo.

[BTVCON]

ffmpeg version N-78742-gf477849 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 4.9.2 (GCC)
configuration: --enable-memalign-hack --arch=x86_64 --target-os=mingw32 --cross-prefix=x86_64-w64-mingw32- --enable-static --disable-shared --enable-zlib --disable-postproc --prefix=/home/peter/ffmpeg/build/gpl64 --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread -lstdc++' --enable-runtime-cpudetect --extra-cflags=-I/home/peter/cc32/include --extra-ldflags=-L/home/peter/cc64/lib --pkg-config=pkg-config --pkg-config-flags=--static --disable-w32threads --enable-libvpx --enable-libvorbis --enable-libtheora --enable-libx265 --enable-libmfx --enable-gnutls --extra-libs='-lz -lnettle -lhogweed -lgmp -lidn -lws2_32 -lcrypt32'
libavutil 55. 19.100 / 55. 19.100
libavcodec 57. 25.101 / 57. 25.101
libavformat 57. 26.100 / 57. 26.100
libavdevice 57. 0.101 / 57. 0.101
libavfilter 6. 36.100 / 6. 36.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.101 / 2. 0.101
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\Brettie\Pictures\GoPro\2016-07-25\HERO4Black\GOPR1239.MP4':
Metadata:
major_brand : mp41
minor_version : 538120216
compatible_brands: mp41
creation_time : 2016-07-25 14:06:35
Duration: 00:09:04.36, start: 0.000000, bitrate: 30124 kb/s
Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 29970 kb/s, 59.94 fps, 59.94 tbr, 60k tbn, 119.88 tbc (default)
Metadata:
creation_time : 2016-07-25 14:06:35
handler_name : GoPro AVC
encoder : GoPro AVC encoder
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default)
Metadata:
creation_time : 2016-07-25 14:06:35
handler_name : GoPro AAC
Stream #0:2(eng): Data: none (tmcd / 0x64636D74) (default)
Metadata:
creation_time : 2016-07-25 14:06:35
handler_name : GoPro TCD
timecode : 14:05:54:39
Stream #0:3(eng): Data: none (fdsc / 0x63736466), 13 kb/s (default)
Metadata:
creation_time : 2016-07-25 14:06:35
handler_name : GoPro SOS
At least one output file must be specified

<MEZZMO>: Child process ended with code: 109, ExitCode=1


---> DB Level Info: 42, 100
---> Frame rate: 59.94
---> Aspect ratio: 16:9 PAR=1:1
---> Duration: 00:09:04


Above is the FFmpeg info.

I am currently using the Samsung E (Evolution Kit) Profile.

Hope this helps

Thanks

Brett

[Paul]

Thanks for the information. It looks like the high video bitrate will be the problem. Please email us at support [at] conceiva [dot] com and we'll provide an update device profile to try.