Official Kodi Wiki - User contributions [en]

Archive:Upgrade Python interpreter on Linux

2017-04-04T13:57:26Z

Niklas Holm: /* Launch Kodi */ fix typo

{{mininav|[[Development]]|[[Add-on development]]|[[Python development]]}}

{{Notice|This is for Linux only. Other platforms uses a built-in Python interpreter shipped with Kodi.}}

If you have TLS-handshake errors with some plugin(s) in Kodi under Linux, this page is for you. The problem is caused by an outdated system-wide Python 2 interpreter installed on your system. Some users may instinctively attempt to upgrade the system-wide Python interpreter, from source, from a PPA, using a third-party package manager or whatever. '''''Do not do that!''''' Python is an integral part of many distributions, including Ubuntu, and messing with the vendor-supplied interpreter may cause all kinds of problems. This method uses Miniconda and a modified environment to launch Kodi with it's very own, updated Python interpreter.

== Procedure ==
{{Note|This procedure is tested on Ubuntu 14.04 LTS}}

=== Prerequisites ===
* Miniconda. To download and install follow the instructions [https://conda.io/docs/install/quick.html#linux-miniconda-install here].
* BlueZ development files to compile PyBluez. Install with
<syntaxhighlight lang="bash" enclose="div">
$ sudo apt-get install libbluetooth-dev
</syntaxhighlight>

=== Create the environment ===
<syntaxhighlight lang="bash" enclose="div">
$ conda create --name kodi python=2.7
$ source activate kodi
(kodi) $ conda install simplejson pillow
(kodi) $ pip install PyBluez PIL-compat
(kodi) $ source deactivate
</syntaxhighlight>

=== Launch Kodi ===
<syntaxhighlight lang="bash" enclose="div">
$ env PATH="/<path>/<to>/<miniconda>/envs/kodi/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" LD_LIBRARY_PATH="/<path>/<to>/<miniconda>/envs/kodi/lib" kodi
</syntaxhighlight>

(obviously replace "/<path>/<to>/<miniconda>" with wherever you installed miniconda)

==== Modify the .desktop-file (optional) ====
You can also put the above command inside your .desktop-file to enable launching directly from your desktop environment.

<syntaxhighlight lang="bash" enclose="div">
$ mkdir -p ~/.local/share/applications
$ x="/<path>/<to>/<miniconda>/envs/kodi"
$ sed 's|Exec=kodi|Exec=env PATH="'"${x}"'/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" LD_LIBRARY_PATH="'"${x}"'/lib" kodi|g' /usr/share/applications/kodi.desktop > ~/.local/share/applications/kodi.desktop
</syntaxhighlight>

== See also ==
{{forum link2|[[forum:307169#pid2534910|Original forum post]]}}

{{Like}}

[[Category:Python]]
[[Category:How-to]]

Archive:Upgrade Python interpreter on Linux

2017-04-04T13:35:24Z

Niklas Holm: Created page with "{{mininav|Development|Add-on development|Python development}} {{Notice|This is for Linux only. Other platforms uses a built-in Python interpreter shipped with Kod..."

{{mininav|[[Development]]|[[Add-on development]]|[[Python development]]}}

{{Notice|This is for Linux only. Other platforms uses a built-in Python interpreter shipped with Kodi.}}

If you have TLS-handshake errors with some plugin(s) in Kodi under Linux, this page is for you. The problem is caused by an outdated system-wide Python 2 interpreter installed on your system. Some users may instinctively attempt to upgrade the system-wide Python interpreter, from source, from a PPA, using a third-party package manager or whatever. '''''Do not do that!''''' Python is an integral part of many distributions, including Ubuntu, and messing with the vendor-supplied interpreter may cause all kinds of problems. This method uses Miniconda and a modified environment to launch Kodi with it's very own, updated Python interpreter.

== Procedure ==
{{Note|This procedure is tested on Ubuntu 14.04 LTS}}

=== Prerequisites ===
* Miniconda. To download and install follow the instructions [https://conda.io/docs/install/quick.html#linux-miniconda-install here].
* BlueZ development files to compile PyBluez. Install with
<syntaxhighlight lang="bash" enclose="div">
$ sudo apt-get install libbluetooth-dev
</syntaxhighlight>

=== Create the environment ===
<syntaxhighlight lang="bash" enclose="div">
$ conda create --name kodi python=2.7
$ source activate kodi
(kodi) $ conda install simplejson pillow
(kodi) $ pip install PyBluez PIL-compat
(kodi) $ source deactivate
</syntaxhighlight>

=== Launch Kodi ===
<syntaxhighlight lang="bash" enclose="div">
$ env PATH="/<path>/<to>/<miniconda>/envs/kodi/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" LD_LIBRARY_PATH="/<path>/<to>/<miniconda>/envs/kodi/lib" kodi
</syntaxhighlight>

(obliviously replace "/<path>/<to>/<miniconda>" with wherever you installed miniconda)

==== Modify the .desktop-file (optional) ====
You can also put the above command inside your .desktop-file to enable launching directly from your desktop environment.

<syntaxhighlight lang="bash" enclose="div">
$ mkdir -p ~/.local/share/applications
$ x="/<path>/<to>/<miniconda>/envs/kodi"
$ sed 's|Exec=kodi|Exec=env PATH="'"${x}"'/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" LD_LIBRARY_PATH="'"${x}"'/lib" kodi|g' /usr/share/applications/kodi.desktop > ~/.local/share/applications/kodi.desktop
</syntaxhighlight>

== See also ==
{{forum link2|[[forum:307169#pid2534910|Original forum post]]}}

{{Like}}

[[Category:Python]]
[[Category:How-to]]

PulseAudio

2016-06-08T14:32:10Z

Niklas Holm: /* FAQ */ use pasuspender

{{mininav|[[Audio]]|[[Linux audio]]}}
<section begin="intro" />This page goes into detail on using PulseAudio on Linux systems. PulseAudio is used when Kodi is installed in a desktop-environment rather than a dedicated/direct boot setup. PulseAudio allows normal video & audio playback in XBMC while at the same time allowing the user to get audio in their browser or other applications. It also allows Kodi playback of video or audio to be paused in order to run a game, Skype or similar. Kodi is set to only use PulseAudio if you have installed it and running.<section end="intro" />

== History ==
In the past users have experienced problems with audio not working within Kodi, because they were running a full-blown Ubuntu desktop environment with PulseAudio installed. This happened because PulseAudio blocked the device Kodi required, and audio playback only worked reliably when using the virtual Pulse device.

Our workaround for those users has been to uninstall PulseAudio which completely broke desktop audio.

For XBMC 13 'Gotham' and later (named Kodi since 14 'Helix') we wanted this situation to change, so thanks to the new '''PulseAudio Sink''' users now can run a normal Ubuntu desktop.

== PulseAudio Output Configuration ==
PulseAudio will be automatically detected and selected in Kodi when it is running.

PulseAudio can be run in one of two modes these are:

<big>'''Passthrough Mode'''</big>
Used if you want to passthrough (bitstream) AC3, DTS, and EAC3 to an AVR or other device. In order to allow passthrough to work with PulseAudio then it '''MUST''' be set to use a 2.0 channel configuration, despite the 2.0 setting this will still allow 5.1 audio from AC3, DTS, and EAC3.

{{Note| PulseAudio does not currently allow TrueHD or DTS-MA passthrough, this is a PulseAudio limitation and not a limitation of the Kodi implementation.}}

<big>'''Multichannel Mode'''</big>

Used if you want Multichannel PCM out, in this mode you can configure PulseAudio for up to 7.1 channels. In this mode Kodi must decode all audio formats to PCM for passing onto the PulseAudio, this can have the advantage of improve audio/video sync.

{{Note| Audio decoded to PCM and sent through PulseAudio the audio will not likely be "bit perfect". Where a video has TrueHD 7.1 audio, this can be decoded by Kodi to PCM 7.1, however DTS-HD 7.1 audio can't be decoded by Kodi, only the embedded DTS Core 5.1 can be decoded to PCM 5.1 audio. Als Pulseaudio will always open the number of channels you have configured. You can stop it doing upmixing (see Known issues), but it will still open all configured channels which makes Dolby Pro Logic II of your AVR not usable.}}

 

== Setting up pavucontrol ==

=== Passthrough Mode ===
{{bluev|'''IMPORTANT:'''|Passthrough is always exclusive mode. If you have another application hogging the device, e.g. google chrome or skype or something else, Passthrough won't work.}}
{{greenv|'''REMEMBER:'''| To use passthrough you need to be using '''2.0''' channel configuration via '''pavucontrol''' (e.g. Digital Stereo (HDMI)}}

In order to activate Passthrough Codecs, just setup pavucontrol, as in the following:

<gallery widths=500px heights=313px>
File:Passthrough2.png|<big>'''Step 1:'''</big> ''pavucontrol'' '''Output Settings.'''
File:Passthrough1.png|<big>'''Step 2:'''</big> ''pavucontrol'' '''Configuration.'''
</gallery>

If you like to do this from the command line, issue:
'''pactl set-sink-formats 0 "pcm; ac3-iec61937; dts-iec61937; eac3-iec61937"'''

Where '''0''' is the sink you want to alter.
You can print all sinks, by using:
'''pactl list sinks'''
You can leave out the codecs your AVR does not support, always keep pcm.

{{bluev|'''IMPORTANT:'''| If you have for example 5.1 flacs or other multichannel files, you can play them as AC3 streams, check the AC3 Transcoding setting.}}

=== Multichannel Mode ===
{{greenv|'''REMEMBER:'''| When configuring pulse to use '''Multichannel configuration''' passthrough will be disabled}}
To configure instead Multi channel mode, do the following settings.

<gallery widths=500px heights=313px>
File:Lpcm2.png|<big>'''Step 1:'''</big> ''To alternatively configure Multi channel, check this:''.
File:Lpcm1.png|<big>'''Step 2:'''</big> The ''Add-on manager'', displaying four/five options (explained below).
</gallery>

=== Example setup in Kodi ===
{{orangev|'''GOOD TO KNOW:'''| Limit sample rate can be set to Fixed - between 48kHz ~ 192kHz or as Optimized and even Best match.}}

<gallery widths=500px heights=313px>
File:Xbmclpcm.png |<big>'''Step 1:'''</big> ''to be edited'' '''Output Settings.'''
File:Xbmcpaa1.png |<big>'''Step 2:'''</big> ''to be edited'' '''Configuration.'''
</gallery>

<gallery widths=500px heights=313px>
File:Xbmcpass2.png |<big>'''Step 1:'''</big> ''to be edited'' '''Output Settings.'''
File:Xbmcpass1.png |<big>'''Step 2:'''</big> ''to be edited'' '''Configuration.'''
</gallery>
{{-}}

=== Setup Guide ===
{{orangev|DEVICE ENUMERATION:| Kodi Enumerates Pulseaudio devices as SPDIF when you have '''Passthrough''' set. Otherwise its '''PCM Device'''. If '''Passthrough''' was not configured with pavucontrol - no '''Passthrough''' setting within Kodi will be available.}}
{{bluev|GOOD TO KNOW:|SPDIF has 2 pcm channels but can do virtual 5.1 formats like dts, ac3, eac3.}}
{{greenv|'''NOTICE'''|The following is meant to act as a guide to get you started, thus you may want to adjust things to suit your own particular set of equipment.}}
{| class="prettytable" style="text-align: center; color: black;"
!
! PC Speakers 2.0
! PC Speakers 5.1
! TV SPDIF 2.0
! TV SPDIF AC3 ('''1''')
! AVR SPDIF AC3/DTS ('''2''')
! AVR HDMI PCM ('''3''')
! AVR HDMI No HD Audio ('''4''')
! AVR HDMI Decode HD Audio ('''5''')
|-
! colspan="9"|'''PusleAudio Mode'''
|-
|
|Multichannel
|Multichannel
|Multichannel
|Passthrough
|Passthrough
|Multichannel
|Passthrough
|Multichannel
|-
! colspan="9"|'''Pavucontrol - Output Devices'''
|-
|align="left"|'''Port'''
|Speakers
|Speakers
|Digital Output (S/PDIF)
|Digital Output (S/PDIF)
|Digital Output (S/PDIF)
|HDMI/Displayport
|HDMI/Displayport
|HDMI/Displayport
|-
|align="left"|'''AC3'''
|N/A
|N/A
|Disabled
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''EAC3'''
|N/A
|N/A
|Disabled
|Disabled
|Disabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''DTS'''
|N/A
|N/A
|Disabled
|Disabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
! colspan="9"|'''Pavucontrol - Configuration'''
|-
|align="left"|'''Profile'''
|Analog Stereo Output
|Analog Surround 5.1 Output
|Digital Stereo (IEC958) Output
|Digital Stereo (IEC958) Output
|Digital Stereo (IEC958) Output
|Digital Surround 5.1 (HDMI) Output
|Digital Stereo (HDMI) Output
|Digital Surround 7.1 (HDMI) Output
|-
!Colspan="9"|Kodi Settings
|-
|align="left"|'''Audio Output Device'''
|Speakers
|Speakers
|SPDIF
|SPDIF
|SPDIF
|HDMI
|HDMI
|HDMI
|-
|align="left"|'''Number of channels'''
|2.0
|5.1
|N/A
|N/A
|N/A
|5.1
|2.0
|7.1
|-
|align="left"|'''Enabled passthrough'''
|Disabled
|Disabled
|Disabled
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''Passthrough output device'''
|N/A
|N/A
|N/A
|SPDIF
|SPDIF
|N/A
|HDMI
|N/A
|-
|align="left"|'''Dolby Digital (AC3) capable receiver'''
|N/A
|N/A
|N/A
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''Enabled Dolby Digital transcoding'''
|N/A
|N/A
|N/A
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''DTS capable receiver'''
|N/A
|N/A
|N/A
|Disabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''TrueHD capable receiver'''
|N/A
|N/A
|N/A
|Disabled
|Disabled
|Disabled
|Disabled
|Disabled
|-
|align="left"|'''DTS-HD capable receiver'''
|N/A
|N/A
|N/A
|Disabled
|Disabled
|Disabled
|Disabled
|Dsiabled
|}

'''(1)''' Where TV can decode 5.1 AC3.

'''(2)''' Where AVR only has SPDIF which will support 5.1 AC3 & DTS.

'''(3)''' Where AVR can do 5.1 PCM.

'''(4)''' Where AVR has HDMI inputs but can't decode TrueHD or DTS-HD but does support 5.1 Ac3 or DTS.

'''(5)''' Where AVR has full decode capabilities including 7.1 PCM.

{{orangev|'''IMPORTANT:'''| You can only have '''AC3''', '''DTS''', '''EAC3''' passthrough '''if your Receiver supports it'''. Most '''TV's''' only support '''AC3'''. If you have a '''HDMI''' connection to your TV and '''from this TV''' a '''SPDIF/Optical''' connection to an '''AVR''', passthrough might not work at all.}}

== Combined Output aka dual audio==
If you want to output to all your attached devices in parallel, e.g. HDMI out, analog out and USB sound card, it is enough to do as below:

'''Step 1:''' Edit <code>/etc/pulse/default.pa</code>

<pre>load-module module-combine-sink sink_name=combined</pre>
'''Step 2: '''Restart pulseaudio.
<pre>killall pulseaudio</pre>

Kodi will then pickup the device, it is named '''combined'''.

{{orangev|'''Downside:'''| The dual audio sink will only output decoded audio, you cannot use it to have one slave doing AC3/DTS and the other PCM. If you use the combined sink for normal music you will realize that direct passthrough output for your movies won't be working anymore, too. This is a pulseaudio bug, cause the combine sink is not deconstructed fast enough internally while the passthrough opening is always exclusive. It will work however if your passthrough device is not part of the device combination. }}

== Audiophile Pulse User ==
Pulseaudio resamples everything that does not match the underlaying sink, so if you are an audiophile user, you perhaps want to hear your 96 / 192 khz and 24 bit recordings as exact as possible. Therefore you need to tell pulseaudio to use a better resampler in general and second change the default sample rate to 96 or 192 khz. Pulseaudio does not resample audio, that is already in the correct samplerate. Furthermore you need to take care, that your sink has a wide enough output format.

To do this configuration systemwide (96 khz in that example), change /etc/pulse/daemon.conf to include (please replace already existing lines and also remove the commenting):

<pre>
default-sample-format = s32le
default-sample-rate = 96000
resample-method = speex-float-5
</pre>

Some remark: This will actively make '''passthrough non working''', as we need s16le format for adding ac3 / dts / etc. float to the sink.

The last setting will increase the resample quality from pulse and therefore the CPU load quite a lot. Again: Resampling is only done, when the sink output does not match the data you throw onto it. But as most normal mp3s are in 44.1 khz, you need to take great care when upsampling them. The overwriting of the resample-method is for this use case.

{{orangev|'''Alternatively:'''| If you don't want any resampling outside Kodi, e.g. no resampling done extra by pulse, you need to configure the sink as told above and set Audio Engine to '''Fixed''' with the number of channels you configured pulseaudio via pavucontrol and samplerate of '''96 khz''' with resample quality high. In that combination Kodi will take care that files are resampled (e.g. 44.1 khz or 48 khz media) in the best possible quality. Already 96 khz files are not touched at all. }}

== FAQ ==

{| width="100%"
{{FAQ|1=When_would_I_want_Pulseaudio
| BGcolor=whitesmoke
| Question=When would I want PulseAudio?
| Answer=
You should use '''PulseAudio''' when:

* You use your Kodi computer mainly as your Desktop when you don't run XBMC.
* You want other applications audio like Skype, youtube, browser mail notification in parallel with Kodi.
* You use Kodi in windowed mode as Desktop player
* You use Pulseaudio as a network sink to stream Audio to other devices in your living room.
* Passthrough is nice to have for you, but to be honest - you don't really need it.
* Whenever you plugin your Bluetooth headset, Kodi audio will continue over this new device (when Default 'PULSE' device is chosen)
}}

{{FAQ|1=When_would_I_want_ALSA
| BGcolor=
| Question=When would I want ALSA?
| Answer=
You should use '''ALSA''' when:

* You use Kodi as your standalone media center.
* You are highly interested in bitperfect exclusive audio output.
* DTS-HD, TrueHD is something you use daily and is of high importance.
* You don't need other applications that would access audio in parallel.
}}

{{FAQ|1=Why_cant_I_have_both?
| BGcolor=whitesmoke
| Question=Why can't I have both?
| Answer=
* '''PulseAudio''' might hog your Audio device and you cannot open the '''ALSA''' device exclusively, therefore we decided for one or the other.
* Whenever '''PulseAudio''' is running your '''ALSA''' device that Kodi chooses, might be busy or even might vanish while you are using Kodi, when system sounds are playing and pulseaudio is trying to access the device again. Out of this reason we also won't implement a selection box to decide between '''ALSA''' and '''PULSE''', because it will actively harm users. Advanced Users can go with the workaround listed beneath.
}}

{{FAQ|1=Forcing_alsa
| BGcolor=
| Question=Can I force ALSA even with PulseAudio installed?
| Answer=
{{note|Doing so may cause problems!}}

Yes, you can - start Kodi from terminal with:
<pre>pasuspender -- env AE_SINK=ALSA kodi</pre>

'''pasuspender''' is a tool that can be used to tell a local PulseAudio sound server to temporarily suspend access to the audio devices, to allow other applications access them directly. pasuspender will suspend access to the audio devices, fork a child process, and when the child process terminates, resume access again.

You can also put the previous command in a custom .desktop-file.

Be warned as this will interfere with your Desktop sounds!
}}
|}
=== Known issues ===
When your audio is much too fast or crackles a lot or passthrough only produces noise, you might have a broken driver in use. If this is the case, try to add ''tsched=0'' to the udev loading section in /etc/pulse/default.pa to read like:

''load-module module-udev-detect tsched=0''

When Pulseaudio is configured to be multi-channel output, e.g. 5.1 profile from within pavucontrol, 2.0 streams are automatically upmixed, no matter what setting you have chosen in Kodi. This is default pulseaudio server behaviour. You can workaround that by disabling ''enable-remixing'' in /etc/pulse/daemon.conf

''enable-remixing = no''

Beware: This will also forbid PA to remix e.g. FL,FR, LFE, FC, BL, BR into FL, FR, LFE, FC, SL, SR - which means you might loose your rears if your speaker layout is non standard.

Audio devices are disappearing with pulseaudio 8.0 (Ubuntu 16.04) especially while running kodi and while using ''Adjust Refreshrate to match video''. This is an issue with the module-switch-on-port-available module and will be fixed with pulseaudio 9.0, the fix sadly won't probably make it into Ubuntu 16.04. As a workaround please disable that feature by editing /etc/pulse/default.pa and commenting or removing ''load-module module-switch-on-port-available'' and reboot the system.

== HOW-TO ==

====[[PulseAudio/HOW-TO: Disable PulseAudio and use ALSA (without removing PulseAudio) for Ubuntu|HOW-TO: Disable PulseAudio and use ALSA (without removing PulseAudio) for Ubuntu]]====

== References ==
{{forum link2|[[forum:183436|Linux - Pulseaudio Sink]] Discussion and further information.}} 

[[Category:How-to]]
[[Category:Audio]]

User:Niklas Holm/sandbox1

2015-11-30T14:27:53Z

Niklas Holm: work in progress

{{greenv|Information:|This page contains explanation about EDID generation and usage in xorg.conf}}
{{bluev|Advanced:|The information contained in this page is considered advanced.}}
{{redv|Warning:|The informations contained in this page can cause issues with your X if any errors or incorrect information is entered.}}

{{xorgnav}}

==Outline==
If your machine has a black screen only when you boot it up before the TV or AVR, follow this guide.

On some combinations of equipments ('''AVR/TV/XBMC'''), in rarer cases you may find that the order you power on your equipment matters. This is obviously inconvenient but can be easily fixed.

The root cause of this issue is the '''EDID''' (Extended display identification data) handshake. Xorg may not correctly handshake with '''AV''' equipment after boot. Typically this results in a black screen and a full system shut down and restart to rectify.

In this guide we will show you how to trick Xorg into thinking your AV equipment is connected and powered on at all times. This locks on your install to one monitor/AVR (port specific) and should stop all handshake issues.

This example is for a Nvidia GPU, other GPUs will have a similar approach but are not covered here.

==Introduction==
There are several methods for acquiring EDID information from Xorg.0.log, but in this page we use output from XRandR piped through grep and xxd which has the advantage of not having to restart the X server.

You'll need:

* Shell access.
* Sudo privileges
* parse-edid
* nvidia-xconfig

You should be running as normal user while following this guide, i.e. not as '''root'''
Any further references to "root" are meant to be interpreted as base directory not the user.

{{note|'''[http://manpages.ubuntu.com/manpages/trusty/man1/get-edid.1.html parse-edid]''' can be installed on Ubuntu with "sudo apt-get install read-edid"}}
{{note|'''[http://manpages.ubuntu.com/manpages/precise/man1/alt-nvidia-96-xconfig.1.html nvidia-xconfig]''' is already installed on Ubuntu and variants if you have the '''nvidia-current drivers installed''' via the Ubuntu packaging or X-swat PPA. This guide is not intended to instruct users on full use of this tool.}}

==Generating & using edid.bin==
Make sure your install is in a working state, powered on in the correct order so that you can see the GUI.

{{how-to
|Step1=
Open a terminal session to your machine and backup any existing xorg.conf (either via [[SSH]] or locally).

<syntaxhighlight lang="bash" enclose="div">sudo cp -pi /etc/X11/xorg.conf /etc/X11/xorg.conf.bak</syntaxhighlight>

|Step2=
You can use a current xorg.conf and should always have a backup of existing, however if you want to start with an fresh xorg.conf proceed with following step.
<syntaxhighlight lang="bash" enclose="div">
sudo nvidia-xconfig -s --no-logo --force-generate --output-xconfig=/etc/X11/xorg.conf
</syntaxhighlight>

|Step3=
Now we work out the display device name of your attached monitor

type:
<syntaxhighlight lang="bash" enclose="div">
grep "ConnectedMonitor" /var/log/Xorg.0.log |cut -f2 -d\"
</syntaxhighlight>

you should see message like the following:
<pre>
ConnectedMonitor
DFP-0
DFP-0
...
</pre>
Take a note of the DFP number, in this example "DFP-0". Your number may vary.
}}

== Extracting EDID binary ==
We use XRandR, grep and xxd to extract the EDID information and generate a binary

{{how-to
|Step1=
<syntaxhighlight lang="bash" enclose="div">
sudo sh -c 'xrandr -display :0.0 --verbose -q | grep -Pzo '"'"'(?<=EDID:)(\s+[0-9a-f]{32})+'"'"' | xxd -r -p > /etc/X11/edid.bin'
sudo chmod 444 /etc/X11/edid.bin
</syntaxhighlight>

|Step2=
Check that the integrity of binary by using parse-edid
<syntaxhighlight lang="bash" enclose="div">
cat /etc/X11/edid.bin | parse-edid | grep -i "checksum"
</syntaxhighlight>
On success you should see a message like the following:
<pre>
Checksum Correct
</pre>
If you don't see this message, or any other message in addition to the above, such as
<pre>I only know about extension blocks of type 02h ...</pre>
or
<pre>Extension block checksum failed</pre>
please examine the output from
<syntaxhighlight lang="bash" enclose="div">
xrandr -display :0.0 --verbose -q
</syntaxhighlight>
manually to try to locate the issue.
}}

== Configure xorg to read from EDID ==
Now edit the xorg.conf you created again

{{how-to
|Step1=
<syntaxhighlight lang="bash" enclose="div">sudo nvidia-xconfig --connected-monitor="DFP-0" --custom-edid="DFP-0:/etc/X11/edid.bin" --use-edid --xconfig=/etc/X11/xorg.conf</syntaxhighlight>

{{redv|Important:|It is VITAL you change the '''DFP-<big>#</big>''' number to match the one we found earlier.}}

If you open your xorg.conf with an text editor/reader, your screen section will look something like the '''example''' below.

<syntaxhighlight lang="xml" enclose="div">
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "NoLogo" "True"
Option "UseEdid" "True"
Option "CustomEDID" "DFP-0:/etc/X11/edid.bin"
Option "ConnectedMonitor" "DFP-0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
</syntaxhighlight>
}}

Since we have created a new xorg.conf file in a location the OS knows to use as default, no further changes need made to make this permanent. If at a later date you need to undo this work simple rename the config file and reboot to revert to default.

If all has went to plan when you reboot everything will just work and the order of powering equipment up will not matter anymore.

{{note|If your equipment is coupled to a receiver that has broader HDMI capabilities than your TV, you should edit your xorg.conf so that the '''section "Screen"''' looks like this:}} 

<syntaxhighlight lang="xml" enclose="div">
Section "Screen"
Identifier "screen"
Device "nvidia"
DefaultDepth 24
Option "ColorRange" "Full"
Option "ColorSpace" "RGB"
SubSection "Display"
Depth 24
EndSubSection
EndSection
</syntaxhighlight>

== EDID Library ==

The edid library is intended to be a collection of user generated edid.bin for equipment such as TV's or AVR's in case users want to test or modify or share with others existing edid's.
This section is a WIP and will need to be improved on by users.

Use the '''Legend''' below as a guide to fill in new entries onto the '''edid.bin''' table.

{| class="prettytable" style="text-align: center"
! colspan="5" | '''Legend'''
|-
| {{yes}}
| {{no}}
| {{NA}}
| {{?}}
| Other
|-
| <nowiki>{{yes}}</nowiki>
| <nowiki>{{no}}</nowiki>
| <nowiki>{{NA}}</nowiki>
| <nowiki>{{?}}</nowiki>
| Other
|}

{{redv|Warning:|Make sure you have a backup of your current installation before using any '''edid.bin''' below. Verify download integrity via MD5 checksum.}}

Below is an area that the general community can share their '''edid.bin''' and relevant information with other users.
 '''<big>Feel free to update and share your experience below.</big>''' 

{| class="prettytable" style="text-align: center"
! style="background: #DBDBDB; width: 100px" | '''TV Brand'''
! style="background: #DBDBDB; width: 100px" | '''AVR Brand'''
! style="background: #DBDBDB; width: 100px" | '''Model'''
! style="background: #DBDBDB; width: 150px" | '''GPU Brand/Model'''
! style="background: #DBDBDB; width: 100px" | '''Working'''
! style="background: #DBDBDB; width: 200px" | '''Download link'''
! style="background: #DBDBDB; width: 150px" colspan="2" | '''Download contents'''
|-
| Samsung
| {{NA}}
| Series 5
| Nvidia ION
| {{yes}}
| [https://dl.dropboxusercontent.com/u/4325533/edid.zip Download edid.zip]
| edid.bin || edid.md5
|-
| {{?}}
| {{?}}
| {{?}}
| {{?}}
| {{?}}
| [http://placeholder-download.com Download edid.bin]
| {{?}} || {{?}}
|}

{{note|Recommended you would create a md5 checksum of the edid.bin and compress both so it can be checked for integrity on download.}}

== Credits ==
The edid instructions are adapted from the Openelec wiki, credit to original authors<ref>[http://wiki.openelec.tv/index.php?title=Config_EDID_nvidia Config EDID NVidia]</ref>

== References ==
<references/>