Profile for Samsung Smart TV UE55D6500

Discuss encoding for devices and presets.
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
macgyver2004
Posts: 9
Joined: Wed Oct 16, 2013 7:38 am

Profile for Samsung Smart TV UE55D6500

Post by macgyver2004 »

I have a problem with making a good profile to keep my movies for playing on a Samsung Smart TV UE55D6500.
I would like to make smallest files posible but with good quality. Time for encoding is not important.
My commandline looks like this:

Code: Select all

HandBrakeCLI -v3 -i %1 -o %2 -f mp4 -m -4 -e x264 --x264-preset veryslow --x264-tune film --q 20 -a 1 -E faac -B 320 --mixdown stereo -R 48 --denoise weak -s 1 --subtitle-burn 1
But the encoded files cant be opened. The video codec is not supported.
The format that is playable on my tv is:

Code: Select all

HandBrakeCLI -v -i %1 -o %2 -f mp4 -m -4 -e x264 --x264-preset ultrafast --x264-tune film --vb 8000 --two-pass -a 1 -E faac -B 320 --mixdown stereo -R 44 --denoise weak -s 1 --subtitle-burn 1
but the files are very big. I had many tries before I made this preset.

Could you help me with my problem?

In the meantime I'm trying to find best profile.
I've created a script that will encode short films with custom options:
- quantizer 15,20,25,30 or bitrate 1000,2000,3000,4000
- --x264-preset: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow
- framerate 23.976/25/29.97
- --x264-tune: film, animation
- diferent --h264-level
and I will try them all on my TV.

But this will take a lot of time.
I would be very grateful if someone could help me with choosing correct options for my TV.

Woodstock
Veteran User
Posts: 3672
Joined: Tue Aug 27, 2013 6:39 am

Re: Profile for Samsung Smart TV UE55D6500

Post by Woodstock »

Question for you - what do you use for the file extension?

I have found that older Samsung TVs vary in their support for things based upon file extension. A file that was unplayable as a .m4v would work by renaming it to end in .mpg, and MKV files would only play across the network if they had the file extension .AVI.

macgyver2004
Posts: 9
Joined: Wed Oct 16, 2013 7:38 am

Re: Profile for Samsung Smart TV UE55D6500

Post by macgyver2004 »

I am using mp4 file extension and "-f mp4" in the commandline.
It works in the ultrafast profile but in veryslow it says that codec is not supported.

moneymatt4life
Veteran User
Posts: 436
Joined: Fri Mar 09, 2012 5:26 am

Re: Profile for Samsung Smart TV UE55D6500

Post by moneymatt4life »

the tv manual says it only supports up to H.264 level 4.1, so you need to specify

Code: Select all

--encoder-level="4.1"
for 1080p... although i prefer 4.0 to lower them vbv limits... but that's just me...
so that means if you want 60FPS video, you'll have to downscale to 720p at the most...
and if you want AC3/DTS Core audio, you need to use mkv. since it doesn't support those audio formats for mp4 for some reason...

i hope you've updated handbrake to at least 0.10.0 too...

macgyver2004
Posts: 9
Joined: Wed Oct 16, 2013 7:38 am

Re: Profile for Samsung Smart TV UE55D6500

Post by macgyver2004 »

It seems it's working:

Code: Select all

\HandBrakeCLI -v3 -i %1 -o %2 -f av_mp4 -m -4 -e x264 --x264-preset veryslow --x264-tune film -q 20 --encoder-level=4.1 -a 1 -E av_aac -B 192 --mixdown stereo -R 48 --denoise weak
I have made corrections in the code to match new commandline options.

Is there a way to make files even smaller without the loss of quality?
Even at the cost of encoding speed?

I want to make an library of all my pictures and movies,
I'm encoding them from my camera.

moneymatt4life
Veteran User
Posts: 436
Joined: Fri Mar 09, 2012 5:26 am

Re: Profile for Samsung Smart TV UE55D6500

Post by moneymatt4life »

you could try CRF at 22, if we're talking about 1080p stuff that is... quality is still quite decent(to me at least), especially if using better x264 presets... level 4.0 lowers the vbv values so the max allowed bitrate will be lower, filesize savings will be marginal at best(i would think)...

i also suggest using fdk_aac ... av_aac is gross...

Post Reply