No sound or sound dropping after a few minutes #6
-
|
Apparently, some users do not have sound in some cases. |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 3 replies
-
|
Also issues with sound being stopping after a few minutes. |
Beta Was this translation helpful? Give feedback.
-
|
Previously discussed here: aclap-dev/vdhcoapp#197 |
Beta Was this translation helpful? Give feedback.
-
|
Part of the issue has been identified. The upcoming v8.2 should improve the situation. |
Beta Was this translation helpful? Give feedback.
-
|
v8.2 announced here: #13 Those should fix the sound issues. |
Beta Was this translation helpful? Give feedback.
-
|
Refer to this discussion: https://groups.google.com/g/video-downloadhelper-q-and-a/c/30eftZvT0SA In there you will find the URL of a German language ASMR video on YouTube. The primary complaint there is that the 4K webm gets a strange error. Yes, that error is still occurring. There has been nothing released yet that addresses that issue. However, that ASMR video exhibited another anomalous behavior with the 1920x1080 mp4 variant. The video was downloading fine but the audio was cutting off before the end of the video. With this new beta CoApp, that problem is corrected. Another YouTube video exhibiting the same short audio problem was this one: https://www.youtube.com/watch?v=JCbHKQCkRpU This one has no 4K variants to cloud the issue. The 1920x1080 mp4 variant now downloads with a complete video track, which it has done all along, but it also now downloads a complete audio track, which is a correction of a previous fault. So this CoApp beta is looking very good. I must point out one bit of weirdness. I'm getting this: C:\DownloadHelper CoApp>dir Directory of C:\DownloadHelper CoApp 01/30/2024 08:15 C:\DownloadHelper CoApp>vdhcoapp.exe --version C:\DownloadHelper CoApp>vdhcoapp.exe --info It just says it's CoApp 2.0.14. I would have hoped that it would have been 2.0.14 beta or 2.0.14a1 beta or even 2.0.15. Something, anything to distinguish it from the 2.0.14 that we already had. If there is something here that uniquely identifies this CoApp as the new beta, I don't see it. When there's a beta of the VDH browser extension, that is reflected in its version number. We should have the same sort of thing with the CoApp beta. |
Beta Was this translation helpful? Give feedback.
-
|
There should be a link somewhere on this page: https://github.com/aclap-dev/vdhcoapp It should link to a page where the CoApp betas are listed, sort of like the page on the VDH web site that lists all the beta versions of the VDH browser extension for Firefox. There's a link on that page for all the regular CoApp releases but there should be a link right below that for the CoApp betas. |
Beta Was this translation helpful? Give feedback.
-
|
For the most recent (as in, beta version), use this link: https://github.com/aclap-dev/video-downloadhelper/wiki/CoApp-Installation |
Beta Was this translation helpful? Give feedback.
-
|
That's not at all obvious that it's the CoApp beta. The word beta appears nowhere on that page. The CoApp beta should be somewhere under https://github.com/aclap-dev/vdhcoapp. There's a link on the right side of that page that says Releases. If you click that, it takes you to the repository of regular CoApps. You need to put another link right below that one that takes you to a repository of CoApp betas. It is not logical to keep a repository of code under a Wiki, & it is not logical to keep a repository of CoApps under the VDH extension area. We have an area here on GitHub for the CoApp. That's where these betas need to live. This may be fine for now but it really needs to be normalized. Speaking of the word beta, the word beta appears nowhere in the stuff you get from --info & --version. This can lead to confusion. |
Beta Was this translation helpful? Give feedback.
-
It doesn't need to be.
No. Like it says there, that place is for developers. And Beta means nothing to developers (rolling releases).
No reasons either.
There's no rules that says we can't.
VDH extension area?
Like I say in the CoApp repo, that's for developers only.
No.
You're making a ton of assumptions here :) I'm doing rolling releases. |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm...... The CoApp area is only for developers. Well then I'm just confused that a user-accessible repository of CoApp versions is in a developers-only area. If a version is a beta, you need to use the word beta somewhere near there to label it as a beta. It doesn't look like a beta. It looks the same as the regular version. Same concept for how you named the beta. The file needs a distinct name, same as the VDH browser extension betas all get unique names that are distinct from the regular releases. At the moment, this CoApp beta is called 2.0.14 & that's the same as the regular release. Also, the --info & --version output doesn't say anything about a beta. Is it or isn't it a beta? I haven't checked but is this beta now residing on this page? https://github.com/aclap-dev/vdhcoapp/releases. It doesn't look like it to me. That page says 2.0.14 was released 5 days ago but this 2.0.14 beta is something we learned about from you upthread here just yesterday. By giving the beta the exact same identification as the regular release, you have thoroughly confused me. Maybe I'm alone in my confusion & everything is perfectly obvious to everybody else. When I say VDH extension area I mean https://github.com/aclap-dev/video-downloadhelper. Like https://github.com/aclap-dev/vdhcoapp is the CoApp area. On this page https://github.com/aclap-dev both the VDH area & the CoApp area are labelled Public. It was never apparent to me that the CoApp area was meant for developers only. As for the rules of what should go in a Wiki, my understanding of a Wiki is that it's for documentation. Logic would tell me to expect code to be somewhere other than mixed in with documentation. I know we can improvise whatever we please here. But it just confuses me even more to have code mixed into a documentation area. It just doesn't make sense to me. |
Beta Was this translation helpful? Give feedback.
-
Because it's an Open Source project.
See it like this: the coapp has no channels (stable / beta / dev). It's a rolling release. The coapp beta link is the coapp version required for vdh beta.
Well now you know :)
I don't know why you're talking about code. There's no code in the wiki. |
Beta Was this translation helpful? Give feedback.
-
|
Right. I meant executable code, not source code. Also, when I said file name, I meant the name of the file I downloaded to get the beta of the CoApp. Of course the CoApp has to be named vdhcoapp.exe. But if I hadn't been paying attention, I would have accidentally replaced the installer file for the regular CoApp 2.0.14 with the one for the beta because the files have the same name. I like to keep at least the current version of software plus one older one in case I need to go back to the older version. |
Beta Was this translation helpful? Give feedback.
-
|
These are just links to the latest relevant coapp. And they are named I understand you want to archive the different versions of the addon and the coapp for your personal use, but for the sake of simplicity I'd rather keep the filename version less. Otherwise it requires a mechanic to rename the files and website and that's work I'm trying to avoid for now. |
Beta Was this translation helpful? Give feedback.
v8.2 announced here: #13
With coapp here: https://www.downloadhelper.net/install-coapp-beta
Those should fix the sound issues.