AVS › AVS Forum › Video Components › Home Theater Computers › High end HTPC / Nas / Surviallance build
New Posts  All Forums:Forum Nav:

High end HTPC / Nas / Surviallance build - Page 2

post #31 of 39
All depends on the transcoding being done. The benchmarks I've seen for a 200 MB AVCHD 1920x1080i media file to a 1280x720P MP4 are:

3770K + QuickSync: 9 sec
3770K @ 4.9: 36 sec
3770K: 47 sec

Transcoding an H.264 DTS 1080P trailer (150 MB) to MKV x.264 w/ 5.1 AC3 using HandBrake:
3770K @ 4.9: 30.66 fps
3770K: 24.71 fps

As you can see, the HandBrake encode is barely enough for realtime viewing of the transcode.
post #32 of 39
Quote:
Originally Posted by vladd View Post

All depends on the transcoding being done. The benchmarks I've seen for a 200 MB AVCHD 1920x1080i media file to a 1280x720P MP4 are:

3770K + QuickSync: 9 sec
3770K @ 4.9: 36 sec
3770K: 47 sec

Transcoding an H.264 DTS 1080P trailer (150 MB) to MKV x.264 w/ 5.1 AC3 using HandBrake:
3770K @ 4.9: 30.66 fps
3770K: 24.71 fps

As you can see, the HandBrake encode is barely enough for realtime viewing of the transcode.

The OP has posted that he wants to use Plex which is "ok" for a phone.
post #33 of 39
Quote:
Originally Posted by vladd View Post

All depends on the transcoding being done. The benchmarks I've seen for a 200 MB AVCHD 1920x1080i media file to a 1280x720P MP4 are:

3770K + QuickSync: 9 sec
3770K @ 4.9: 36 sec
3770K: 47 sec

Transcoding an H.264 DTS 1080P trailer (150 MB) to MKV x.264 w/ 5.1 AC3 using HandBrake:
3770K @ 4.9: 30.66 fps
3770K: 24.71 fps

As you can see, the HandBrake encode is barely enough for realtime viewing of the transcode.

I use a 3570K to transcode blu-rays full blu-rays (mkv format via makemkv) from my Plex Media Server, which only uses software transcoding. I can transcode three movies simultaneously without issue. CPU usage around 80-85%. I'm not sure why handbrake is so slow. I'm guessing it's only using one core.
post #34 of 39
Thanks. That's a better real world example. Unfortunately, I don't have an I7 to test so I could just go by the benchmarks I've seen. Handbrake uses multiple cores but the test was done with transcoding to x.264 which is very CPU intensive. MakeMKV may not actually be transcoding the video stream but simply remuxing the existing video into an MKV container.
post #35 of 39
Quote:
Originally Posted by vladd View Post

Thanks. That's a better real world example. Unfortunately, I don't have an I7 to test so I could just go by the benchmarks I've seen. Handbrake uses multiple cores but the test was done with transcoding to x.264 which is very CPU intensive. MakeMKV may not actually be transcoding the video stream but simply remuxing the existing video into an MKV container.

To clarify, all my my blu-rays are stored on the Plex Server as MKV files I made via makemkv (just remuxed). Plex Media Server then transcodes these MKV's to my phone, tablet, Roku, etc. using software transcoding.
post #36 of 39
Ah, ok. I misunderstood, yes.
post #37 of 39
Quote:
Originally Posted by vladd View Post

Thanks. That's a better real world example. Unfortunately, I don't have an I7 to test so I could just go by the benchmarks I've seen. Handbrake uses multiple cores but the test was done with transcoding to x.264 which is very CPU intensive. MakeMKV may not actually be transcoding the video stream but simply remuxing the existing video into an MKV container.

Most modern android phones support h264, which devices would need x264?
post #38 of 39
The H.264->x.264 encode was really just a stress test. x.264 might be used to transcode MPEG2 video for a device though.
post #39 of 39
It's just a test. Showing differences is its only design. It's not a real world study.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers
AVS › AVS Forum › Video Components › Home Theater Computers › High end HTPC / Nas / Surviallance build