Open GoogleCodeExporter opened 8 years ago
This happens with the latest VLC remote and with VLC 2.0.4 (manually installed
all related packages for vlc 2.0.4 under Ubuntu 13.04)
Original comment by ase...@gmail.com
on 4 Jun 2013 at 7:51
From a network capture, the issue is visible: the :sout option is appended both
to the HTTP GET line as part of the input= parameter and the options=
parameter.
Example:
GET /requests/status.xml?command=in_play&input=file:///file.avi
:sout=#transcode{...}:rtp{...}}&option=:sout=#transcode{...}:rtp{...}}
This seems to be the result of the code in the method:
"public void play(String input, List<String> options)"
(line 254 in file "./src/org/peterbaldwin/vlcremote/net/MediaServer.java" in
revision edd1029288ca)
The first loop intends to provide compatibility for VLC version 1.1.10 and
earlier, appending the options to the file but this seems to be in conflict
with version 2.0.
As soon as I can make a build/test environment for Android, I'll try the
application without that loop (lines 257-259 of the same file).
Original comment by ase...@gmail.com
on 8 Jun 2013 at 8:49
Managed to get it built and installed on my Android devices.
Starting the stream is fixed through the code change I mention in comment #2,
but I had another problem - the video player launched by the VLC Remote wasn't
connecting to the stream.
Commenting out the loop worked, but had to also fix the link being passed on on
to the video player. I fixed this (quick fix; might have possible side effects
elsewhere) by commenting out lines 126-127 & 134-140 which generates an HTTP
url if the MIME type does not indicate an audio stream. This condition does not
seem particularly useful if using the stream command from the context menu
which uses RTSP no matter the MIME type of the content.
From first testing using a self-signed and manually installed version of the
application, it is fulfilling my needs.
Will consider next steps depending on owner/project member interest; I can
provide the self-signed APK if needed.
Original comment by ase...@gmail.com
on 9 Jun 2013 at 12:30
Original issue reported on code.google.com by
martin.k...@gmail.com
on 24 Jan 2013 at 3:18Attachments: