You are Here:
Install Updates Gimp Error - see Security & Bug Fixes Section Sticky



Tutorial: How to play HD videos on a single-core Intel Atom netbook.

Author (Read 1148 times)

0 Members and 2 Guests are viewing this topic.

 

m654321

  • Gold Level Poster
  • *******
  • 871
    Posts
  • Country: gb
  • Reputation: 83
  • Linux Lite Member, 'Advocate' & Donator

  • Linux Lite: 3.8 64bit

  • CPU: Intel Core T7100@1.8GHz (2cores) on a Dell Latitude D630

  • MEMORY: 4Gb

  • VIDEO CARD: Intel GM965/GL960 Integrated Graphics Controller
Do you have old or low-powered hardware that seems unable to play HD-quality videos ?
If the answer is yes, then donít worry. Help is at hand with a video file manipulation application called handbrake. This tutorial is for those who, like me until recently, had never heard of or used this application.

I discovered handbrake while trying to figure out how to play HD-videos (1080p/50fps) on a single-core Intel Atom netbook (see signature), which I use mainly as a portable media player. Due to the low processing power of this machine, playing HD videos resulted in either stuttering (choppy video motion) and/or a lack of audio/video synchronisation (audio running ahead of video).  To make this video play on an Atom netbook, or other old or low-powered hardware, youíll need to set the bitrate and reduce the frames per second (fps):

First, download and install handbrake from the repository that comes with the LL package. When youíve done this, open it from Menu (type handbrake in Menu search box).

Then, from within handbrake, load the file you want to modify, using the Source or File/Source buttons in its toolbar. Make sure youíve indicated the desired Destination for the modified file, though by default it appears to choose the Videos directory. Next, look for the toolbar running from left to right (located half-way down the handbrake window) with the following options:


Summary/Picture/Video/AudioDefaults/AudioList/SubtitleDefaults/SubtitleList/Chapters/Tags

Click on the option Video, then:
- select option Bitrate (kbps),set this to 2500
- select option Constant Framerate, set this to 25 (PAL Film/Video)
- click on Fast Decode (not sure if this makes any difference)
- finally click Start Button to start file processing.

When youíve finished, collect your modified video file from the Video directory and open with your media player - the playback experience should be improved. If not, you could try a lower bitrate, e.g. 1500 kbps. Processing time will depend on the type of file modification you want, e.g. a lower bitrate setting of 1500, it will take longer.  With a bitrate/fps setting of 2500/25, a video with a 30 minute playback time took me around 45 minutes to process on a Dell Latitude D630. Handbrake will do all sorts of other video file modifications - Iíve only described one specific case here.

NB. Modifying video files is very CPU-intensive. Therefore, itís highly recommended that you donít carry this out on a low-powered machine (it may either fail or take forever) - I recommend using at least a Core-2-Duo computer - the more cores the better !


PS. around 23-24 fps is apparently the threshold framerate, at which the brain is fooled into seeing continuous motion.

Hoping this tutorial will be of use to someone.
Last Edit: November 21, 2019, 11:09:06 PM by m654321
64bit OS (32-bit on Samsung netbook) installed in Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ Arm710@1.2GHz - LibreElec, used for upgrading our Samsung TV (excellent for the task)  
2012 - Lenovo G580 2689 (2cores; 4threads] ~ i3-3110M@2.4GHz - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom N455@1.66GHz - LL 3.8 32-bit (LL3.8 64-bit & LL4 are too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel T3200@2.0GHz - LL4.4/Win8.1 dual-boot (LL working beautifully)
2007 - Dell Latitude D630 (2cores) ~ Intel T7100@1.8GHz - LL3.8/Win8.1 dual-boot (LL really zippy!) - my daily driver  :-)
 


 


Install Updates Gimp Error - see Security & Bug Fixes Section Sticky