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

Remote URLs not working for jpeg files #829

Open
tslater opened this issue Oct 5, 2022 · 3 comments
Open

Remote URLs not working for jpeg files #829

tslater opened this issue Oct 5, 2022 · 3 comments

Comments

@tslater
Copy link

tslater commented Oct 5, 2022

I'd had great success using remote URLs for audio, png, etc. However, for jpegs, they never seem to work. They just get skipped over. The same files work if I download them locally. Here's an example command that fails:

melt \
https://upload.wikimedia.org/wikipedia/commons/3/3a/Cat03.jpg length=752 \
-filter luma cycle=75 duration=25 \
-consumer avformat:/tmp/cat.mp4 \
frame_rate_num=25 width=1920 height=1080 sample_aspect_num=1 sample_aspect_den=1

I'm on melt 7.8.0, MacOS 12.5 (I've also had the same issue on an Alpine Linux docker container)

I've been able to get it to work on ffmpeg:

ffmpeg -i https://upload.wikimedia.org/wikipedia/commons/3/3a/Cat03.jpg -vf "loop=-1:1:0,trim=duration=4.5" /tmp/test-ffmpeg.mp4
@tslater
Copy link
Author

tslater commented Oct 5, 2022

I found an interesting workaround: url params

melt \
"https://upload.wikimedia.org/wikipedia/commons/3/3a/Cat03.jpg?p=workaround" length=752 \
-filter luma cycle=75 duration=25 \
-consumer avformat:/tmp/cat.mp4 \
frame_rate_num=25 width=1920 height=1080 sample_aspect_num=1 sample_aspect_den=1

@ddennedy
Copy link
Member

ddennedy commented Oct 6, 2022

I reproduced this including the workaround, but I have not figured it out. All that is needed for the workaround is "?" at the end. I did find that if I force it to not be seekable in the code, then it works without the workaround. Unfortunately, the only way we can support protocol or device options is by using query string parameters - except in the case of HTTP because it may need the URL's query string.

@tslater
Copy link
Author

tslater commented Oct 6, 2022

The workaround works just fine for my purposes. Feel free to close the issue if you prefer. Hope that having a record of it at least, will let others know about the workaround!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants