The VideoLAN Forums

Searched VLC forums and bug trac...apparently I'm the first entry on SMTube.

SMTube.org browses YouTube and plays videos in a back-end of user's choice. I use VLC. VLC works great except for its playlist.

SMTube sends a URL to VLC. VLC turns it into a human-sensible name in the VLC playlist. VLC always plays the correct video, but fails to show a correct name except on the first. The second and subsequent ones play fine, but VLC repeats the ID info from the first on all the rest.

So I can play 4 videos, all different, even with different time durations shown in VLC, yet ID title info is identical on each playlist line.

I've fiddled with VLC and SMTube playlist settings. I do not find answers. Is anyone using SMTube who might confirm, or would VLC devs try SMTube? Looks like an array in VLC uses var but needs var[i++].

Thanks for 2.1.0, fantastic release. Really like drag-n-drop.

INFO
Arch Linux i686, up to date (dash suffix = Arch build):
SMTube 1.8-1
VLC 2.1.0-2
PulseAudio 4.0-2
GStreamer 1.0.10-1

This is hard to guess without logs.

Is anyone using SMTube who might confirm, or would VLC devs try SMTube?

...was the question thanks.

Smtube pipes youtube to vlc using '--meta-title=...', as can be seen if you look in smtubes' source code (/src/players.cpp). As an experiment I renamed a couple of video files to "test_movie_1.flv" and "test_movie_2.mp4". I then opened a terminal and opened vlc with 'vlc --meta-title="test_title_1" test_movie_1.flv' and vlc opened with the title "test_title_1" (as expected). I then opened another terminal (with previous instance of vlc still running) and entered 'vlc --meta-title="test_title_2" test_movie_2.mp4'. The second video replaced the first video, but the first title remained ( "test_title_1").
Note that I tried the above with the playlist option 'allow only one running instance' set to true. If I unset that option and then tried the above, the videos would (as expected) open in two seperate windows but this time with the correct titles. Hope this helps. Kind regards.

I think I fixed some issue on 2.1.2 related to this.

Hi, I've just tested (the above) with commit 9f7bfd93e3a749a2912adda6380370310cd4dffa on Tue, 28 Jan 2014 and the problem appears to remain. Kind regards.