Yes, your posts are going only to the group, not my E-mail inbox. Thank you.
The URL we're really interested in appears in your Hit Details as topUrl, the one at
fitnessfaqs.com. That's the page where the content is hosted & that's the one anybody
trying to diagnose your problem would be interested in. Except when I went there, it
didn't show me the page. Instead, it prompted me for a login. Oh well. I can't help
now.
The URL you did post is of the video track. (There's another URL in there for the audio
track.) It is full of the typical sort of gibberish strings that identify this as being
(a) unique to your visit to the page, (b) on a timeout. Apparently, mjs visited the URL
soon enough after you posted that the URL was still valid. I tried the master.m3u8 trick
& got the error 410 Gone. That says that the URL timed out between the time mjs looked
at it & the time I tried to look at it.
It appears that fitnessfaqs hosts their content in the cloud on
akamaized.net. Akamai is
one of the major cloud service providers, along with Amazon Web Services, Google,
Cloudfront, & a number of other providers. It may be jumping to a conclusion based on
insufficient evidence to say this is an embedded Vimeo video. Vimeo content is also
usually hosted on Akamai, as our experience in many other cases on here has shown. But
given what we have here, I think it's a leap too far to say for certain this is an
embedded Vimeo video. Vimeo is not the only client hosting their content on Akamai.
However, the appearance in the Hit Details of such things as audioMpd, dash-adp, DASH
streaming, & videoMpd leads me to believe that this case is very much susceptible to the
solutions offered in the "too fast" discussion mjs mentioned. Despite the thread having
"too fast" in its title, the discussion applies to many situations in addition to the too
fast case. Here's another vote for you to read that thread & see if you can apply what
we've said there. I think the chances are extremely good that you could get this content
using our ideas we've laid out there. That is reinforced by mjs's result from ffprobe.
It's too bad you're not using Firefox. I would recommend you get on VDH 8.1.0.0a5 beta.
But Michel doesn't create VDH betas for Chrome. Despite that, you might try the latest
CoApp 2.0.5. Go here:
https://github.com/aclap-dev/vdhcoapp/releases
Get the Mac ARM64 CoApp. I have 0 experience with Mac so I'm not sure whether you should
get the dmg or the pkg. Seems to me there's been some talk in here that one is
preferable to the other. You could search this forum to find discussions on the topic
from people who actually know Mac.
But I'm only about 50% optimistic that the new CoApp would do anything for you. I hit a
case just a couple of days ago (it's in a thread on here) of a Vimeo video that was not
downloaded correctly even by the 8.1.0.0a5/2.0.5 combination. So I wouldn't hold out too
much hope that upgrading your CoApp would do anything for you. Still, you can't know for
certain unless you try. It's easy enough to go back to the old CoApp. Just don't remove
1.6.3. Pay attention to the directory into which 2.0.5 installs itself. If 2.0.5
doesn't work, just delete that directory. Or keep it & see if other content from other
sites downloads fine. Your choice. I'm assuming that the conventions for the CoApp on
Mac are similar to those on Windows. Here, the CoApp is in its own subdirectory within
the the standard Windows installation directories, both for 1.6.3 & 2.0.5. So it is
self-contained & easy to remove. VDH recognizes the presence of the CoApp & uses
whatever it finds with the highest release number. I still have my 1.6.3 directory on my
system but I also have 2.0.5. VDH finds 2.0.5 & stops looking, so it's oblivious to the
fact that 1.6.3 is still here.