The VideoLAN Forums

I have created a number of m3u playlists for use with vlc on my TVision HUB which runs Google TV. I have just encountered a problem with one of them. For some reason when I open this playlist only the first track is loaded for playback. I don't see a way to attach a file, so here is the playlist:
Why is only the first track being loaded for playback?

Dave

It looks like your first media has a different path. Are you sure the other media's paths are valid?

It looks like your first media has a different path. Are you sure the other media's paths are valid?

Yes. I prepared the m3u using the find command as:

find /storage/FA29-7738/Music/Beethoven/ -name "*.mp3" -o -name "*.ogg" >Beethoven.m3u

I ran this using adb shell on the TVision HUB and the files are all on a USB attached flash drive.

This is one of several similar m3u files I created for different artists and the only one that behaves like this.

I assume something strange is going on, but I have no idea how to debug this given the android google TV environment.

Dave

For example, I opened an adb shell connection to the device and then confirmed the second file in the list is accurate:
So I have no idea why vlc on the device isn't loading the entire playlist.

Dave

The underline is in the directory name? Is VLC choking on it? The one that plays has underlines in the filename.

The underline is in the directory name? Is VLC choking on it? The one that plays has underlines in the filename.

I have other m3u files which play with underscores in the path name, so that isn't it.

Is there a way to get vlc on android to log things? I have adb running as you see, so perhaps it can be done.

Dave

Yes, under More > Settings > Advanced > Debug logs. If you tap on "Start logging" (or if VLC crashes), logs are stored with the timestamp as the filename in Android/data/org.videolan.vlc.debug

Yes, logs would help.

Yes, logs would help.

I found the setting to enable the logs and logged what happened. I stopped the logging, but I find no permission to the indicated log file location. Looking at the options on the debug screen I see "copy to clipboard" and "dump logcat log", so I selected the "dump logcat log" option. I found a file in logs/error with the current timestamp, so I have copied it to my laptop.

I hope it contains what you want to see. If not, how can I get what you need? I could use the "copy to clipboard" option, but how to get that into a file?

I also see no option here to attach a file. How do I get this to you?

Dave

PS: found a way to save the clipboard and now have that available as well.

I was going to post the log I clipboard copied in a code segment, but encountered a problem. It is too long for me to do so. I really need to be able to attach a file here or provide it in some other fashion. How can I make this available?

Dave

Here is the first 30 lines of the log copied to the clipboard:
More to follow.

Dave

Here is the next 30 lines:
More to follow.

Dave

Here is the remainder of the log copied to the clipboard:
I hope this provides some insight into the problem. I don't have the background to make any sense out of it.

Dave

For those who think there might be a problem with the m3u file I just thought of a way to validate it:
So you can see each and every file in the list exists. Any further tests I can do to help diagnose the problem?

Dave

There is nothing useful in the logs. Could you please share the whole log file with the sharing service you prefer (Google Drive, Dropbox, pastebin...)?

There is nothing useful in the logs. Could you please share the whole log file with the sharing service you prefer (Google Drive, Dropbox, pastebin...)?

By "the whole log file" do you mean the file I downloaded after hitting the "Dump Logcat Log" button? If not, how do I obtain what you need?

Dave

Here is a link to the logcat dump. Let me know if you need more.

https://www.dropbox.com/s/gt24dfmndrx8z ... ar.gz?dl=0

Dave

Have you been able to access the logcat dump? Is there anything there helping diagnose the problem? If this gives no further information on the problem how do I capture information for you?

Dave

Sorry I missed your logs. There is no playback logs in it. You should share the logs generated by the application. Reproduce the issue and then go to: Settings > Advanced > Debug logs.
To retrieve the logs on Android TV, you should follow this: https://forum.videolan.org/viewtopic.ph ... ck#p509973
Then share the logs with the sharing service you prefer (Google Drive, Dropbox, pastebin...).

Sorry I missed your logs. There is no playback logs in it. You should share the logs generated by the application. Reproduce the issue and then go to: Settings > Advanced > Debug logs.
To retrieve the logs on Android TV, you should follow this: https://forum.videolan.org/viewtopic.ph ... ck#p509973
Then share the logs with the sharing service you prefer (Google Drive, Dropbox, pastebin...).

I'm not sure my options match what you are expecting. When I go to settings->Advanced->Debug logs my options are:

START LOGGING STOP LOGGING

COPY TO CLIPBOARD DUMP LOGCAT LOG

CLEAR LOG

On initial entry START LOGGING is highlighted and others are not. Is this what you anticipate?

Dave

1. Start logging
2. reproduce the issue (wait after the first track)
3. Dump logcat
4. Share the generated file

1. Start logging
2. reproduce the issue (wait after the first track)
3. Dump logcat
4. Share the generated file

Followed steps 1-3, but don't see the generated file anywhere using the Wireless File Manager. Where specifically should it be. It is definitely NOT in the root as shown in the linked thread nor in the data folder that was shown at the start.

Dave

It will be on the device on which VLC is installed, at—
/Android/data/org.videolan.vlc.debug/files

It will be on the device on which VLC is installed, at—
/Android/data/org.videolan.vlc.debug/files

Unfortunately that does not appear to be the case here. Here is what I get with adb:
First there is no permission to list the data directory, then there appears to be no directory to access the file in. If I can provide more information either via adb or from vlc please let me know.

Dave

No, it should be at the root of your internal memory. Something like /storage/emulated/0/vlc_logcat_[XXX].log