Add update.

[homepage.git] / blog / data / 2018-07-12-kodi-linux-desktop-vlc.txt

diff --git a/blog/data/2018-07-12-kodi-linux-desktop-vlc.txt b/blog/data/2018-07-12-kodi-linux-desktop-vlc.txt
index a36df04104b067329632907d7d14e0179e701fcf..2de00dbdc281ce1157bd69dbf83f2ad86537c0a6 100644 (file)
--- a/blog/data/2018-07-12-kodi-linux-desktop-vlc.txt
+++ b/blog/data/2018-07-12-kodi-linux-desktop-vlc.txt
@@ -7,7 +7,7 @@ my projector connected to Kodi.  I sadly had to admit that I had no
 idea, as it was a task I never had tried.  Since then, I have been
 looking for a way to do so, preferable without much extra software to
 install on either side.  Today I found a way that seem to kind of
-work.  Not great, but it si a start.</p>
+work.  Not great, but it is a start.</p>
 
 <p>I had a look at several approaches, for example
 <a href="https://github.com/mfoetsch/dlna_live_streaming">using uPnP
@@ -37,7 +37,7 @@ this working on the desktop/streaming end.</p>
 
 <blockquote><pre>
 vlc screen:// --sout \
-'#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{dst=projector.local,port=1234,sdp=rtsp://192.168.11.4:8080/test.sdp}'
+  '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{dst=projector.local,port=1234,sdp=rtsp://192.168.11.4:8080/test.sdp}'
 </pre></blockquote>
 
 <p>I ssh-ed into my Kodi box and created a file like this with the
@@ -45,14 +45,14 @@ same IP address:</p>
 
 <blockquote><pre>
 echo rtsp://192.168.11.4:8080/test.sdp \
-> /storage/videos/screenstream.m3u
+  > /storage/videos/screenstream.m3u
 </pre></blockquote>
 
 <p>Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
 to update screenstream.m4u on the Kodi machine and adjust the vlc
-repice.  To get started, locate the file in Kodi and select the m3u
+recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)</p>
 
@@ -61,6 +61,36 @@ the audio quality is really bad.  No idea if the problem is package
 loss or bad parameters for the transcode.  I do not know VLC nor Kodi
 enough to tell.</p>
 
+<p><strong>Update 2018-07-12</strong>: Johannes Schauer send me a few
+succestions and reminded me about an important step.  The "screen:"
+input source is only available once the vlc-plugin-access-extra
+package is installed on Debian.  Without it, you will see this error
+message: "VLC is unable to open the MRL 'screen://'.  Check the log
+for details."  He further found that it is possible to drop some parts
+of the VLC command line to reduce the amount of hardcoded information.
+It is also useful to consider using cvlc to avoid having the VLC
+window in the desktop view.  In sum, this give us this command line on
+the source end
+
+<blockquote><pre>
+cvlc screen:// --sout \
+  '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}'
+</pre></blockquote>
+n
+<p>and this on the Kodi end<p>
+
+<blockquote><pre>
+echo rtsp://192.168.11.4:8080/ \
+  > /storage/videos/screenstream.m3u
+</pre></blockquote>
+
+<p>Still bad image quality, though.  But I did discover that streaming
+a DVD using dvdsimple:///dev/dvd as the source had excellent video and
+audio quality, so I guess the issue is in the input or transcoding
+parts, not the rtsp part.  I've tried to change the vb and ab
+parameters to use more bandwidth, but it did not make a
+difference.</p>
+
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>