From: gorecki3 <gorecki3@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VLSub not automatically loading subs
Date: Tue, 18 Jul 2023 14:40:53 +0200 [thread overview]
Message-ID: <20230718124053.Aec96jJuz1O1dJe2IllxMUeVr4QodRw3EX5iZDTPtC0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45045@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
New comment by gorecki3 on void-packages repository
https://github.com/void-linux/void-packages/issues/45045#issuecomment-1640138577
Comment:
Apologies for the confusion, I have just realized that I mistakenly identified the version number of my VLC. It appears that the version of VLC on my other Linux distribution was not up-to-date compared to the one on Void Linux. In my MX Linux installation, I have VLC version 3.0.16 and VLsub 0.11.1, and everything functions correctly there.
Hence, it is plausible that the lack of response from VLsub could be attributed to VLC version 3.0.18.
Considering this, it is possible that this observation undermines the validity of the user agent theory.
As you mentioned before, this will not have a significant impact in the long run anyways. However, I want to highlight that I was able to successfully install VLC through the flatpak version, and VLsub works flawlessly on Void Linux. This could be useful for those who still wish to have the ability to obtain subtitles automatically.
next prev parent reply other threads:[~2023-07-18 12:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 21:42 [ISSUE] " gorecki3
2023-07-15 3:18 ` gorecki3
2023-07-15 14:08 ` TeusLollo
2023-07-16 16:09 ` gorecki3
2023-07-16 16:10 ` gorecki3
2023-07-17 20:41 ` TeusLollo
2023-07-18 0:06 ` gorecki3
2023-07-18 1:26 ` TeusLollo
2023-07-18 1:28 ` TeusLollo
2023-07-18 12:40 ` gorecki3 [this message]
2023-07-18 12:42 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 13:10 ` TeusLollo
2023-07-18 13:10 ` TeusLollo
2023-07-18 21:37 ` gorecki3
2023-07-18 22:06 ` gorecki3
2023-07-18 23:30 ` TeusLollo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230718124053.Aec96jJuz1O1dJe2IllxMUeVr4QodRw3EX5iZDTPtC0@z \
--to=gorecki3@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).