[BUG] tracks in .m3u8 playlists cannot play

[stephen147]

When in a .m3u8 playlist and clicking a track, it doesn't play.

System info:

• OS: Windows 10 Pro (Build 19045)
• Related software:
• Github release: Latest version.

[regorxxx]

I don't think that's related at all to my plugin... since once the playlist is loaded, playback is a foobar thing.

Provide more info please.

[stephen147]

Sorry, it's hard to give more info. What happens if you create a normal playlist and try playing a track?

[regorxxx]

What happens if you create a normal playlist and try playing a track?

Works perfectly fine.

Check your console log.

Also, why do you say M3U8 don't play? Do other playlists play fine?

As said, provide more info. A video or gif, etc.

[stephen147]

Nothing is appearing in the console when I click on a track.

That playlist shows 5067 tracks but when I click on it, it now shows nothing. I tried to reload the playlist and it gives me this:

Followed by this:

Along with this:

Error: Spider Monkey Panel v1.6.1-mod ({BEE593A9-3CE1-42A4-8EA0-AB09F34D20D2}: Playlist Tools: Buttons Bar v1.1.0 by regorxxx)
Script aborted by user

File: helpers_xxx_cache_volatile.js
Line: 43, Column: 22
Stack trace:
  clear@helpers_xxx_cache_volatile.js:43:22
  _recycleFile@helpers_xxx_file.js:224:31
  _list/this.updatePlaylist@playlist_manager_list.js:3400:18

[regorxxx]

You have to click continue, not stop. Obviously it crashes, if you stop it.

As I said, post a video. And playback is not related at all to my script anyway.

[stephen147]

It was related. This fixed it. Setting this to none worked.

[regorxxx]

That's not a problem of my script, as I said, my script is not related to playback. It's a foobar/SMP bug, which blocks the double click action.
TheQwertiest/foo_spider_monkey_panel#198

You can play the tracks, just click play, don't use double click.

[stephen147]

Funny as I did try pressing play and that didn't work either.

[regorxxx]

It may depend on OS or version. Who knows. It's a SMP bug.

Last version has a workaround for it, it is NOT a bugfix, since I can not fix it. But problem should not happen anymore.