dockerwest / compose-pimcore

Docker compose environment for Pimcore
MIT License
13 stars 8 forks source link

mp4-video 'unsupported file type' #17

Open ppi-buck opened 6 years ago

ppi-buck commented 6 years ago

Hey again,

I'm trying to work with videos in my project. After changing the max file size via including a custom.ini file in the docker-compose.yml I can upload videos to the admin interface of pimcore. All good so far!

The problem now is that it doesn't render any previews nor thumbnails in the frontend nor the video itself (in backend view or frontend). See attachments at bottom.

When I try to get a thumbnail of the video it returns /phpapp/web/pimcore/static6/img/filetype-not-supported.svg (the path falsely includes /phpapp/web/ but I don't think this is an issue with your project but rather with pimcore itself). Same issue in Admin view when inspection console logs.

This makes me believe that maybe FFMPEG doesn't support the video-type?! It is a .mp4 though and the docs say FFMPEG does support it. The installed ffmpeg version is 3.2.10 from what I found.

Do you have any idea why that issue occurs? Can you reproduce this behaviour?

Thank you so much


My system:

The videos I tested, all with the same result:

Attachments: image image image

This is the frontend where I'm trying to get a thumbnail first and then use the video output which never finishes loading but tries to get the above mentioned image image

ppi-buck commented 6 years ago

PS: I just tried with .mpeg - same issue...

BlackIkeEagle commented 6 years ago

If there are ffmpeg errors there should be a log with the issues encoutered generated by pimcore

ppi-buck commented 6 years ago

Oh thank you so much! Somehow I never think about logs as they rarely used to help me. But in this case they absolutely did.

FFMPEG doesn't seem to handle filenames that contain spaces. It's giving me /phpapp/web/var/assets/Islands: No such file or directory where the file name is actually Islands - 2119.mp4.

Seems like pimcore doesn't use quotes around the file name... Maybe an worth an issue over there?

BlackIkeEagle commented 6 years ago

Wow that would be a nasty mistake. Definatly worth reporting to pimcore

ppi-buck commented 6 years ago

Hmm I can not reproduce this in the basic-demo. Seems like it's only in my local installations that use your compose-environment ... maybe something here then

Any more ideas how I can track it down and maybe help?

ppi-buck commented 6 years ago

PS: I found this https://github.com/pimcore/pimcore/issues/2971 - might be related or the issue here. Than it's not your compose-environment but nginx and pimcore.