How to install Peek recorder on Ubuntu 17.04
To install Peek recorder on Ubuntu 17.04
Peek is a very basic screen recording tool which contains only a set of options that is used to create/record a section of screen and export the recorded video as a GIF file. It uses ffmpeg and imagemagick to create the GIF screencasts. It can be fixed or resized on any screen to record and also the user can change the format of the created recording. This tutorial covers the installation procedure of Peek recorder on Ubuntu 17.04.
Installation procedure
To proceed with the installation procedure, add the required repository by executing the following command.
root@linuxhelp11:~# add-apt-repository ppa:peek-developers/stable
Stable releases of the Peek animated GIF recorder
https://github.com/phw/peek
More info: https://launchpad.net/~peek-developers/+archive/ubuntu/stable
Press [ENTER] to continue or ctrl-c to cancel adding it
gpg: keybox ' /tmp/tmpyb0_cfrh/pubring.gpg' created
gpg: /tmp/tmpyb0_cfrh/trustdb.gpg: trustdb created
gpg: key 9578539176BAFBC6: public key " Launchpad PPA for Peek Developers" imported
gpg: Total number processed: 1
gpg: imported: 1
OK
The repositories are added to the system. Update your system by running the apt-get update command.
root@linuxhelp11:~# apt-get update
Hit:1 http://security.ubuntu.com/ubuntu zesty-security InRelease
Get:2 http://ppa.launchpad.net/peek-developers/stable/ubuntu zesty InRelease [15.9 kB]
Hit:3 http://us.archive.ubuntu.com/ubuntu zesty InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu zesty-updates InRelease
Get:5 http://ppa.launchpad.net/peek-developers/stable/ubuntu zesty/main i386 Packages [620 B]
Hit:6 http://us.archive.ubuntu.com/ubuntu zesty-backports InRelease
Get:7 http://ppa.launchpad.net/peek-developers/stable/ubuntu zesty/main amd64 Packages [620 B]
Get:8 http://ppa.launchpad.net/peek-developers/stable/ubuntu zesty/main Translation-en [428 B]
Fetched 17.6 kB in 1s (12.6 kB/s)
Reading package lists... Done
The system is updated with the required repositories. Next install the peek recorder by executing the following command.
root@linuxhelp11:~# apt-get install peek
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.10.0-19 linux-headers-4.10.0-19-generic
linux-image-4.10.0-19-generic linux-image-extra-4.10.0-19-generic
Use ' apt autoremove' to remove them.
The following additional packages will be installed:
ffmpeg gstreamer1.0-plugins-ugly gstreamer1.0-plugins-ugly-amr
.
.
.
Setting up libavformat57:amd64 (7:3.2.4-1build2) ...
Setting up libavfilter6:amd64 (7:3.2.4-1build2) ...
Setting up libavdevice57:amd64 (7:3.2.4-1build2) ...
Setting up ffmpeg (7:3.2.4-1build2) ...
Setting up peek (1.0.3-0~ppa552~ubuntu17.04.1) ...
Processing triggers for libc-bin (2.24-9ubuntu2.2) ...
The installation is complete. The Peek application is running successfully and now you can start to record the screen with minimal fuss.
To stop the recording, press the stop button on the menu bar. The video gets automatically saved.
The installation procedure of Peek recorder on Ubuntu 17.04 is done successfully.
The output directory does not exist (i.e. you entered an incorrect path).
You don't have permission to write to the output directory.
Your hard disk is full.
"Warning: Audio input is more than 5% too fast, video and audio will be out of sync."
The cause is a bug in PulseAudio. The issue has been fixed and the fix should arrive in some future version (probably 4.1). For now, you can work around the bug by modifying the file /etc/pulse/daemon.conf and adding/modifying these lines:
"default-sample-rate = 44100
alternate-sample-rate = 44100"
After doing this, you should restart PulseAudio (or just reboot). These values will force PulseAudio to use the same sample rate at all times rather than switching between 44100 Hz and 48000 Hz (which will trigger the bug).
Some users have reported that sound recorded through PulseAudio is still buggy even after applying this workaround, so it appears that there is more than one bug in PulseAudio that can cause this issue. I haven't been able to reproduce this myself though. If you are unable to fix the problems with PulseAudio, consider using JACK instead.