Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

audio and video files do not play #1162

Open
hannahfrost opened this issue May 27, 2017 · 13 comments
Open

audio and video files do not play #1162

hannahfrost opened this issue May 27, 2017 · 13 comments
Labels
Milestone

Comments

@hannahfrost
Copy link

Created a work for an MP3 audio file and another work for an MOV video file.

On each work's show page, the file is listed and it is clear that has been successfully uploaded. The default media player appears, but clicking on play results in no response.

For a fleeting moment, the download arrow was displayed for the audio file. When I clicked on it, the browser responded with an error: "Failed - no file found"

Links to sample files:
video
https://salad.demo.hydrainabox.org/concern/generic_works/b8eb3733-008e-40c4-80ae-72995c75a98a?locale=en

audio
https://salad.demo.hydrainabox.org/concern/generic_works/c8cc206c-11b0-44fc-b1a1-1ffa332e02df?locale=en

@jcoyne
Copy link
Member

jcoyne commented May 31, 2017

@hannahfrost It was my impression that we purposely excluded audio and video from the beta. As far as I can tell, we haven't installed ffmpeg on the worker machines, which would be prerequisite for this.

@hannahfrost
Copy link
Author

@jcoyne That was never my intention. I wish I had caught this issue earlier.

@mjgiarlo
Copy link
Member

@jcoyne Could you estimate the level of effort for this ticket? (Do we need DevOps folks to chime in on this too?)

@jcoyne
Copy link
Member

jcoyne commented Jun 1, 2017

@mjgiarlo this is completely a dev ops concern if we want to use ffmpeg (like local hydra). If we want to use elastic encode, it might be a week of work.

@mjgiarlo
Copy link
Member

mjgiarlo commented Jun 1, 2017

@bbranan @eefahy @cbeer @dbernstein How much would it take to add ffmpeg to our AWS deployment? Alternatively, would folks prefer to use Elastic Transcoder? (FWIW, the hydra-derivatives gem now includes support for the latter but I don't yet have a sense of how costly it'd be to make Hyrax's transcoding work with it.)

@bbranan
Copy link
Contributor

bbranan commented Jun 3, 2017

I'd prefer to see us use Elastic Transcoder here if possible. We have enough issues already with capacity planning on the workers with FITS and ImageMagick, I'm not inclined to add ffmpeg to the mix. That said, is there any reason to not simply allow these files to be downloadable (like other generic files) in the meantime?

@cjcolvar
Copy link
Member

cjcolvar commented Jun 3, 2017

I'd be willing to help on an effort to support Elastic Transcoder in hyrax. Avalon has this work planned but I have been bogged down in local migration to Avalon 6.x and will be for the next week or two.

@mjgiarlo
Copy link
Member

mjgiarlo commented Jun 5, 2017

Great, @cjcolvar. Glad to hear this!

@mjgiarlo
Copy link
Member

mjgiarlo commented Jun 5, 2017

@bbranan 💬

That said, is there any reason to not simply allow these files to be downloadable (like other generic files) in the meantime?

They should already be downloadable. If not, that's a 🐛!

@hannahfrost
Copy link
Author

@mjgiarlo @bbranan These files are downloadable from the Action dropdown menu under the file list for each work.

@mjgiarlo mjgiarlo modified the milestone: November 2017 Jun 5, 2017
@mjgiarlo
Copy link
Member

@cjcolvar Are you still interested in taking this on?

@cjcolvar
Copy link
Member

@mjgiarlo Interested yes, but I'm still stuck in production land for another week at least.

@mjgiarlo
Copy link
Member

@cjcolvar OK, no problem. Good luck in production land!

jcoyne added a commit that referenced this issue Jun 29, 2017
Because we aren't installing ffmpeg on AWS/Docker.

Fixes #1141
Ref #1162

We should revert this when we install ffmpeg
sephirothkod pushed a commit to UVicLibrary/Vault that referenced this issue Jul 13, 2017
Because we aren't installing ffmpeg on AWS/Docker.

Fixes samvera#1141
Ref samvera#1162

We should revert this when we install ffmpeg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants