Some files converted to non-compatible format #29
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry.go#29
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In certain cases, not sure if this is related to resolution or video quality, the yt downloader uses a VP80 Codec (https://www.screencast.com/t/YpjByam5) and not the typical web optimized h264. I remember we ran into something similar a while ago with John Cleese videos.
Here's an example: lbry://the-metagame-batman-arkham-asylum-20
Not sure what we can do in this case, but maybe we can force h264 or convert via ffpmeg.
Another: lbry://the-holloway-series-in-poetry-matthew#ced531f814390eea0e763c34327f7f4b9ada0d3f
Another recent one: lbry://what-is-an-etf#3ab1078328232fe17700815ae35e582ee8c185cd
Another: lbry://left-boy-get-it-right-sped-up#110aad98da20d92fc9f07e99dc7229cb4f979272
@nikooo777 and I looked into this, and he has a way of removing VP8 codecs as an output method. Please close once it's been implemented.
I implemented this in a slightly different way than we discussed yesterday but it works the same.
Closing this as it's live!
Reopening this as I think it caused issues on ALL videos synced since it was implemented. @nikooo777 can you confirm? How do we remedy this?
I checked out a random new channel that was synced: lbry://@Prophetz and it's running into the metadata issue - VP8 codec with a low resolution.
@ all-hands: Tom and I figured out what happened and we're working on a fix.
we fixed the codec issue and now we're dealing with the wrongly synced content.