JM and JSVM software are the reference softwares used to understand
and emulate H.264 and its scalable version while HEVC and SHM software
are the reference softwares used to understand and emulate H.265 and its
scalable version. These reference softwares( JM, JSVM, HEVC, SHM ) are
managed using a version control software such as subversion (SVN) and
Concurrent Version Systems (CVS). These applications help in controlling
and distributions of the reference softwares.The HEVC and its scalable
version reference software can be downloaded
from
from
https://hevc.hhi.fraunhofer.de/
https://hevc.hhi.fraunhofer.de/svn/svn_HEVCSoftware/
In
Linux,the packages “subversion”and “cvs ”have to be installed via
command line or any other package manager(e.g. synaptic package
manager). After installation ,in the terminal , simply type the command
in the terminal window:- Windows
https://hevc.hhi.fraunhofer.de/svn/svn_HEVCSoftware/
- Linux
svn checkout https://hevc.hhi.fraunhofer.de/svn/svn_HEVCSoftware/
Unfortunately YUVplayer/YUV toolkit is not developed for linux however we can use the VLC player to read these YUV files. To read and play the yuv files in linux using vlc player use the command.
vlc --demux rawvideo --rawvid-fps FrameRate --rawvid-width FrameWidth --rawvid-height FrameHeight --rawvid-chroma I420 YUV_File
- build (which has the project files )
- cfg (configuration files)
- compact
- doc (documentation)
- HM.xcodeproj
- lib (libraries)
- source (source files)
the files have been compiled another folder “bin”will appear which will contain the binaries i.e. the executable files. Depending on the system configurations (i.e processor, RAM ,HDD size etc..) the time required to complete the execution may vary. It is recommended to use a system with good configurations.
- Windows
In
windows,the visual studio express(preferred 64 bit)software is used for
compilation of the project.The Project files are present in the build
folder with a .sln extension. While opening the visual studio project, a
set of projects will be displayed on the solution explorer.First the
solution of these projects must be built.
To build the solution of these projects simply click F7 or right click and select build solution and the executional files will be created. Now to select a particular project e.g. the encoder project “TAppEncoderStatic” first right click on the project and select ‘Set as Startup Project’. Next right click on the project and select properties go to configuration properties and select the
debugging tab.The Command arguments are already added however if not simply check the software manual in section 3.
To build the solution of these projects simply click F7 or right click and select build solution and the executional files will be created. Now to select a particular project e.g. the encoder project “TAppEncoderStatic” first right click on the project and select ‘Set as Startup Project’. Next right click on the project and select properties go to configuration properties and select the
debugging tab.The Command arguments are already added however if not simply check the software manual in section 3.
Using the encoder it will show that has to be written. Command Prompt
can also be used by going to the directory and using the command
TAppEncoder.exe [-c config file] [--parameter value]
E.g. TAppEncoder.exe -c BasketBallDrill.cfg -c encoder_lowdelay_main.cfg
Using this command the following outputs should appear if not then an error has occurred.
- Linux
./TAppEncoder [-c config file] [--parameter value]
E.g. ./TAppEncoder -c BasketBallDrill.cfg -c encoder_lowdelay_main.cfg
No comments:
Post a Comment