VLC has some problems..

[ozgur55]

1- i have a .mkv video with VP9 codec that i downloaded from utube and when you randomly and fastly click on the seekbar you will see this problem, İt shows a full glitch display.. Will VLC fix this issue in the near future?
Here's the screenshot..
(https://ufile.io/qui6ddms)

2- This is another issue, an .mp4 video file with HEVC codec, VLC can't play it correctly, when i play it, i only see this..
here's the screenshot..
(https://ufile.io/ab9q3ml7)

[Lotesdelere]

https://forum.videolan.org/viewtopic.php?f=14&t=157228

It should be fixed in VLC 3.0.15 nightly build:
https://nightlies.videolan.org

You can also try with Direct3D9 video output.

[ozgur55]

https://forum.videolan.org/viewtopic.php?f=14&t=157228

It should be fixed in VLC 3.0.15 nightly build:
https://nightlies.videolan.org

You can also try with Direct3D9 video output.

thanks for the reply, but My first issue with VLC is not about lag on the seekbar, it's all about with the VP9 codec, This problem has been around for ages. VLC can't play it correctly, you can see for yourself, just download an .MKV format video with VP9 codec from utube using a video downloader and then click different places on the seekbar, VLC eventually will show you a garbage glitch display like i mentioned above in the first screenshot.

and I've just installed nightly build 4.0 and VLC still has the second problem, it can't play my 2k HEVC video correctly, the video freezing with VLC, but i got smooth crystal clear playback with Potplayer, and potplayer has no issue with VP9 codec, that's why i'm using it atm, VLC is not good tbh.. i hope they fix these ''glitch'' issues.. and they need to improve its video playback.

[Hitchhiker]

We'll try to help you if we can, but you have to do all the hard work yourself.

So provide a couple of links to .mkv files which have been encoded with the VP9 codec which you say won't play properly in vlc and we'll take a look at it.

[Lotesdelere]

I wasn't able to download your screenshots because of the crappy site using too many ads which were blocked. Please use another site like https://postimages.org or https://imgur.com .

That said, I also have problems playing some VP9 files, but no problem with some other ones. So yes, we do need samples files and a log.
Please open Tools -> Messages (set Verbosity to 2) before you start the playback, and then paste the full resulting log here or on Pastebin.com if it's too long.

Also upload a short sample of your original problematic file to Zippyshare.com or to WeTransfer.com and then post the link to the file here.
https://www.zippyshare.com
https://wetransfer.com

If needed cut it with DGsplit and read here about how to do it:
https://forum.videolan.org/viewtopic.ph ... 35#p193335
100 MB max should be enough.

[ozgur55]

I wasn't able to download your screenshots because of the crappy site using too many ads which were blocked. Please use another site like https://postimages.org or https://imgur.com .

That said, I also have problems playing some VP9 files, but no problem with some other ones. So yes, we do need samples files and a log.
Please open Tools -> Messages (set Verbosity to 2) before you start the playback, and then paste the full resulting log here or on Pastebin.com if it's too long.

Also upload a short sample of your original problematic file to Zippyshare.com or to WeTransfer.com and then post the link to the file here.
https://www.zippyshare.com
https://wetransfer.com

If needed cut it with DGsplit and read here about how to do it:
https://forum.videolan.org/viewtopic.ph ... 35#p193335
100 MB max should be enough.

https://imgur.com/a/JOWQdTM The first one with VP9 codec and the second screenshot from an .mp4 video (2560x1440, HEVC, 60 fps)

and here's the video sample(https://ufile.io/ibcvlhhi) i just downloaded from utube and tested it, it has the same glitch problem.

[Lotesdelere]

I asked you to use either Zippyshare.com or Wetransfer.com, I don't want to use ufile.io.
And we also need a log file, please read carefully my post again.

[ozgur55]

I asked you to use either Zippyshare.com or Wetransfer.com, I don't want to use ufile.io.
And we also need a log file, please read carefully my post again.

zipshare--->>>> https://www95.zippyshare.com/v/DHOwYqeV/file.html


the log is too long, i can't paste it here and pastebin.com doesn't work atm, how do i send it to u?

[Lotesdelere]

I can't reproduce the problem with your sample but I can do it with some other VP9 sample files.
Upload your log to Zippyshare.com or Wetransfer.com.

[ozgur55]

I've uploaded my two problem's log file,
I see glitch display( with the VP9 one) mostly when i click on the seekbar fastly, the second issue is worst than VP9 one.

https://www66.zippyshare.com/v/DjM6JlN5/file.html
https://www66.zippyshare.com/v/0hPB3Ujr/file.html

[ozgur55]

I can't reproduce the problem with your sample but I can do it with some other VP9 sample files.
Upload your log to Zippyshare.com or Wetransfer.com.

and I've just discovered another problem, when i play my another video i only see very beginning of it and it freezes, VLC can't play it..
here's the log---->> https://www115.zippyshare.com/v/tKa9CRmz/file.html

[Lotesdelere]

Ok, so you're using an AMD Radeon R5 Graphics 1002 9874 with the WDDM driver 23.20.808.1536.
There are some things which are common to all of your logs:

Code: Select all

direct3d11 debug: Output max luminance: 270.0, colorspace RGB Rec.709 gamma:22 range:FULL, bits per pixel 6

Bits per pixel 6 looks unusual to me, should be 8 or 10.

For some reason, it can't use D3D11 and always switch to D3D9:
First and second log:

Code: Select all

direct3d11 debug: Direct3D11 device adapter successfully initialized direct3d11 debug: Direct3D11 Open Succeeded main debug: using vout display module "direct3d11" main debug: A filter to adapt decoder DXA9 to display YUVA is needed main debug: looking for video converter module matching "any": 24 candidates chain debug: Trying to use chroma I420 as middle man main debug: looking for video converter module matching "any": 24 candidates d3d9_filters debug: Using Direct3D9 Extended API! main debug: using video converter module "d3d9_filters" main debug: Filter 'd3d9_filters' (0000020e44997520) appended to chain

Third log:

Code: Select all

main debug: A filter to adapt decoder DXA0 to display YUVA is needed main debug: looking for video converter module matching "any": 24 candidates chain debug: Trying to use chroma I420 as middle man main debug: looking for video converter module matching "any": 24 candidates chain debug: Trying to use chroma I422 as middle man main debug: looking for video converter module matching "any": 24 candidates chain error: Too high level of recursion (3) main debug: no video converter modules matched main error: Failed to create video converter chain debug: Trying to use chroma I0AL as middle man main debug: looking for video converter module matching "any": 24 candidates d3d9_filters debug: Using Direct3D9 Extended API! main debug: using video converter module "d3d9_filters" main debug: Filter 'd3d9_filters' (000001a484901cb0) appended to chain

Problem in your first log (VP9):

Code: Select all

main error: Timestamp conversion failed for 38529001: no reference clock main error: Could not convert timestamp 0 for FFmpeg

Problem in your second log (HEVC):

Code: Select all

d3d11va warning: Unsupported profile 1 for HEVC Main profile

Problem in your third log (HEVC):

Code: Select all

d3d11va warning: Unsupported profile 2 for HEVC Main profile

You should create a new ticket on the VLC Trac with your above reports, the links to your sample files and the link to this thread:
https://code.videolan.org/videolan/vlc/-/issues

[ozgur55]

Ok, so you're using an AMD Radeon R5 Graphics 1002 9874 with the WDDM driver 23.20.808.1536.
There are some things which are common to all of your logs:

Code: Select all

direct3d11 debug: Output max luminance: 270.0, colorspace RGB Rec.709 gamma:22 range:FULL, bits per pixel 6

Bits per pixel 6 looks unusual to me, should be 8 or 10.

For some reason, it can't use D3D11 and always switch to D3D9:
First and second log:

Code: Select all

direct3d11 debug: Direct3D11 device adapter successfully initialized direct3d11 debug: Direct3D11 Open Succeeded main debug: using vout display module "direct3d11" main debug: A filter to adapt decoder DXA9 to display YUVA is needed main debug: looking for video converter module matching "any": 24 candidates chain debug: Trying to use chroma I420 as middle man main debug: looking for video converter module matching "any": 24 candidates d3d9_filters debug: Using Direct3D9 Extended API! main debug: using video converter module "d3d9_filters" main debug: Filter 'd3d9_filters' (0000020e44997520) appended to chain

Third log:

Code: Select all

main debug: A filter to adapt decoder DXA0 to display YUVA is needed main debug: looking for video converter module matching "any": 24 candidates chain debug: Trying to use chroma I420 as middle man main debug: looking for video converter module matching "any": 24 candidates chain debug: Trying to use chroma I422 as middle man main debug: looking for video converter module matching "any": 24 candidates chain error: Too high level of recursion (3) main debug: no video converter modules matched main error: Failed to create video converter chain debug: Trying to use chroma I0AL as middle man main debug: looking for video converter module matching "any": 24 candidates d3d9_filters debug: Using Direct3D9 Extended API! main debug: using video converter module "d3d9_filters" main debug: Filter 'd3d9_filters' (000001a484901cb0) appended to chain

Problem in your first log (VP9):

Code: Select all

main error: Timestamp conversion failed for 38529001: no reference clock main error: Could not convert timestamp 0 for FFmpeg

Problem in your second log (HEVC):

Code: Select all

d3d11va warning: Unsupported profile 1 for HEVC Main profile

Problem in your third log (HEVC):

Code: Select all

d3d11va warning: Unsupported profile 2 for HEVC Main profile

You should create a new ticket on the VLC Trac with your above reports, the links to your sample files and the link to this thread:
https://code.videolan.org/videolan/vlc/-/issues

so i need to go to this (https://code.videolan.org/videolan/vlc/-/issues) site and create a new ticket.. okey thank you.
Do i need to create another account for that site?

[Lotesdelere]

Do i need to create another account for that site?

Yes, you do.

[ozgur55]

Do i need to create another account for that site?

Yes, you do.

@Lotesdelere Could you pls tell me how do i post my issue on the link that you gave me? i dont know how to post my question, i have created an account there but after i sign in, i see this ''enable two step verfication'' page and everytime i click on something it shows me the same page, Do i have to enable two step verification to get rid of this page? english is not my native language so i dont know how to skip this page, i dont get what that page wants me to do exactly? Could you pls help? and tell me how do i post my issue on that forum? thanks!
https://www69.zippyshare.com/v/CF9bL34q/file.html

[Lotesdelere]

Yes, I know it's a bit confusing. I would like the devs to make a sticky post for explaining step by step how to use two-factor authentication, especially for the people who don't have a mobile phone or who don't want to rely on any Google service.

They said they are trying to find a better option, but nothing is happening yet:
https://forum.videolan.org/viewtopic.ph ... 28#p518628

[Rémi Denis-Courmont]

In my understanding, system administrators promised to add support for some major third party authentication services so that people would have choices not to use 2FA. That has already been done a while ago.

If you think that better documentation is needed here, you are free to write it and apply for making your post sticky. But realistically, whom do you hope to help? If somebody is unable to set up standard TOTP 2FA nor use a third party service, it's unlikely that they'll understand your English language help. And even if they do, they are probably not able enough to inform a bug report to an exploitable state.

[Lotesdelere]

So you say.
And now many people are not going to help the development by reporting problems with VLC, but it won't change the fact the problems are still there. So the devs will have to make the reports themselves.
A good idea after all.

[Rémi Denis-Courmont]

You're free to write that documentation, or to concede that it wouldn't be such a good investment of your time, and not write it. You can't have it both ways. Doing nothing but criticising the other volunteers is just conceding in a passive-aggressive manner.

What's for sure is that, either way, there will be people who won't bother to write exploitable bug reports, people who won't be able to write exploitable bug reports, and potentially exploitable bug reports that nobody wants to sponsor the bugfix work for.

[Lotesdelere]

Doing nothing but criticising the other volunteers is just conceding in a passive-aggressive manner.

"Would like" is not a critic but a request. It's just about making a sticky post. Why you feel it agressive is a mystery.
The VideoLAN organization wants people to use 2FA so it's up to the VideoLAN organization to explain how to use the tools they suggest to use.
Some people might not be tech savvy but they can find flaws and bugs. This thread is a good example, VLC is (was ?) well known to have troubles with some VP9 videos. You can choose to ignore this report because the user is not able to login to the VLC bug tracker but the issue still exists, whether it's been reported on the tracker or not.

[Rémi Denis-Courmont]

And what I see is that, yet again, you demand that volunteers do something that you won't do yourself. I wouldn't know, but it seems to me that this is not just critical, but actually hypocritical? Or is it not as quick and simple a task as you make it sound?

As the saying goes, there is no better service than one's own. As you are surely aware, most VLC devs are Linux or Mac geeks using their mobile phone for the TOTP (including myself). You're much better poised to actually write that sticky post that you demand.

[Lotesdelere]

I've asked several times VideoLAN not to use 2FA for reporting bugs because I knew it would be a blocker for many people. I've been told it will not be possible for various reasons.
So you're just wasting your time trying to make it personal. I fought against 2FA so the people in charge and who have made this decision have to assume all of the consequences of their choice.

Meanwhile, some bugs and problems are not being reported so they are not addressed because some users don't bother to deal with this. They just move to another player because for the average end user it seems VLC is having very little progress over the years, and you should keep an eye on another open source and cross platform player which supports gapless audio playback and reverse frame by frame, among other features, even though it doesn't have the streaming and conversion abilities of VLC. And yes, this time that is a critic.

[Rémi Denis-Courmont]

I've asked several times VideoLAN not to use 2FA for reporting bugs because I knew it would be a blocker for many people.

Well, I am a voting delegate of VideoLAN, and I can't say that I remember you raising that objection against the switch to Gitlab to inform the voters.

I've been told it will not be possible for various reasons.

As far as I know, there are no ways to disable 2FA for bug reporting without also disabling 2FA for source code management. Disabling 2FA there would put everybody at risk that a trojan gets inserted in the VLC code base, so there is that...

So you're just wasting your time trying to make it personal.

And you are wasting your time complaining about documentation not materialising.

I fought against 2FA so the people in charge and who have made this decision have to assume all of the consequences of their choice.

The delegates voted to switch to Gitlab and I am pretty sure that they would vote the same way if the vote was recalled. Not that there are any credible means of switching back to Trac anyway.

Several people (including myself) have complained about the lack of documentation from admins in the migration to Gitlab on a general level, as compared to previous tool migrations. But 2FA is not that difficult to set up.

Now, if you want documentation you write it. Otherwise, you're just being hypocritical.There will be no documentation and you will be as much part of the problem rather than the solution as everybody else.

Meanwhile, some bugs and problems are not being reported so they are not addressed because some users don't bother to deal with this.

How exactly will writing documentation (or for that matter, disabling 2FA) help here? Again, if the user has such poor command of English, or of computing that they cannot set 2FA up, their bug report is all but guaranteed to be completely unusable/inexploitable.

[Lotesdelere]

So to sum it up, if someone cannot use 2FA for whatever reason (not rich enough to afford a mobile phone, not willing to share his phone number with private companies, not enough English language knowledge, not enough computer experience, etc) then it's not worth listening / reading to what he says and reports.
Is that the official VideoLAN organization position ?

[Hitchhiker]

If somebody is unable to set up standard TOTP 2FA nor use a third party service, it's unlikely that they'll understand your English language help. And even if they do, they are probably not able enough to inform a bug report to an exploitable state.

I don't wish to appear to be sarcastic, but I think most users know how to post a link to a log file they've created on Pastebin so your above mentioned comment is hardly valid in that respect.

Setting up 2FA on the other hand is unnecessarily complicated even with the help of the official documentation.

Also, 2FA can be bypassed which may put the user's phone number at risk.

Relying on third party authorization services is usually going to mean using one of the major services like Google or Microsoft or similar in order to be certain the third party service itself hasn't been compromised.

I understand that you as a developer use TOTP constantly and in that respect 2FA is essential, but the number of times ordinary users are going to post a bug on Videolan/Github can probably be counted on the fingers of one hand. Therefore being rigid as to what you're prepared to accept is going to lead to fewer and fewer bug reports to the ultimate detriment of vlc.