LBRYCommunity/spee.ch

Fork 0

cannot view video on first resolve, ffmpeg exception on claim page #626

New issue

Open

opened 2018-10-10 22:59:52 +02:00 by tzarebczan · 8 comments

tzarebczan commented

2018-10-10 22:59:52 +02:00

(Migrated from github.com)

This happened to me a few times already when accessing newly resolved videos on spee.ch. @skhameneh believes it could be related to a race condition.

Unfortunately, we couldn't download your asset from LBRY. You can help us out by sharing the following error message in the LBRY discord.

Command failed: ffprobe -v error -of flat=s=_ -select_streams v:0 -show_entries stream=height,width /home/lbry/Downloads/blockwolf-cryptocandor-hashoshi-crypto-zombie-live-stream-cryptocurrency-chat-btc-eth-xrp.mp4 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x1ebcd80] moov atom not found /home/lbry/Downloads/blockwolf-cryptocandor-hashoshi-crypto-zombie-live-stream-cryptocurrency-chat-btc-eth-xrp.mp4: Invalid data found when processing input

This happened to me a few times already when accessing newly resolved videos on spee.ch. @skhameneh believes it could be related to a race condition. ``` Unfortunately, we couldn't download your asset from LBRY. You can help us out by sharing the following error message in the LBRY discord. Command failed: ffprobe -v error -of flat=s=_ -select_streams v:0 -show_entries stream=height,width /home/lbry/Downloads/blockwolf-cryptocandor-hashoshi-crypto-zombie-live-stream-cryptocurrency-chat-btc-eth-xrp.mp4 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x1ebcd80] moov atom not found /home/lbry/Downloads/blockwolf-cryptocandor-hashoshi-crypto-zombie-live-stream-cryptocurrency-chat-btc-eth-xrp.mp4: Invalid data found when processing input ```

tzarebczan commented

2018-10-29 23:33:32 +01:00

(Migrated from github.com)

This is happening very often and provides a bad UX when accessing videos.

tzarebczan commented

2018-12-07 22:41:33 +01:00

(Migrated from github.com)

Just ran into this still:
Unfortunately, we couldn't download your asset from LBRY. You can help us out by sharing the following error message in the LBRY discord.

Command failed: ffprobe -v error -of flat=s=_ -select_streams v:0 -show_entries stream=height,width /home/lbry/Downloads/how-to-max-star-level-on-any.mp4 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x8efd80] moov atom not found /home/lbry/Downloads/how-to-max-star-level-on-any.mp4: Invalid data found when processing input

Just ran into this still: Unfortunately, we couldn't download your asset from LBRY. You can help us out by sharing the following error message in the LBRY discord. Command failed: ffprobe -v error -of flat=s=_ -select_streams v:0 -show_entries stream=height,width /home/lbry/Downloads/how-to-max-star-level-on-any.mp4 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x8efd80] moov atom not found /home/lbry/Downloads/how-to-max-star-level-on-any.mp4: Invalid data found when processing input

jessopb commented

2018-12-07 22:52:28 +01:00

(Migrated from github.com)

Are we checking to see if filesize is > x before ffprobing the file? could
be trying to probe an empty file.

On Fri, Dec 7, 2018 at 4:41 PM Thomas Zarebczan notifications@github.com
wrote:

Reopened #626 https://github.com/lbryio/spee.ch/issues/626.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/spee.ch/issues/626#event-2013480171, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ai3FQtFVftcjX99-iKQR2X_bWvV1z8Ktks5u2uCOgaJpZM4XWUoR
.

Are we checking to see if filesize is > x before ffprobing the file? could be trying to probe an empty file. On Fri, Dec 7, 2018 at 4:41 PM Thomas Zarebczan <notifications@github.com> wrote: > Reopened #626 <https://github.com/lbryio/spee.ch/issues/626>. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/spee.ch/issues/626#event-2013480171>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/Ai3FQtFVftcjX99-iKQR2X_bWvV1z8Ktks5u2uCOgaJpZM4XWUoR> > . >

skhameneh commented

2018-12-10 03:21:26 +01:00

(Migrated from github.com)

wait-on has a window where it will continue to wait if the file keeps growing. I'll need to revisit this.

`wait-on` has a window where it will continue to wait if the file keeps growing. I'll need to revisit this.

tzarebczan commented

2019-02-15 21:38:32 +01:00

(Migrated from github.com)

This still happens on files that are accessed for the first time + moov atom is at the end of the file. Can we just skip ffmpeg processing in these cases, show the video, and update the sizes later?

jessopb commented

2019-02-18 09:21:06 +01:00

(Migrated from github.com)

The reason we're doing ffmpeg is to record dimensions to the db for oEmbeds. We can let it error out and either process the sizes on the fly, or check that they exist on the next embed call and upsert them then. I couldn't find any other case where dimensions are even used.

That said, it is nice to know when a video is going to sit blank for a long time.

kauffj commented

2019-02-18 16:37:17 +01:00

(Migrated from github.com)

@jessopb if the primary purpose of ffmpeg is to record dimensions to the db, this could be a background process rather than done as part of the request.

tzarebczan commented

2019-03-18 15:13:12 +01:00

(Migrated from github.com)

@jessopb this is also the error users see when content is unavailable.

This discussion has been locked. Commenting is limited to contributors.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/spee.ch#626

No description provided.

Rows
Columns