-
Notifications
You must be signed in to change notification settings - Fork 19
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
PixelFormat invalid #8
Comments
Thanks for the kind feedback and for making me aware of that issue. I didn't test too deeply on windows, so this slipped through the net. |
I don't know if RGB32 is the "default" for windows, I see many other codes using AV_PIX_FMT_RGB24 instead AV_PIX_FMT_RGB32, so I'm still searching.
I tried that, juce::Image has a getPixelFormat(), but the usefull values are just RGB and ARGB. Is not possible discover if the juce image is BGR0. |
Hi again Daniel, I'm experiment with lib264 encoder, using just swscale (not avcodec) and this is working in Windows 10. I discovered my native format is AV_PIX_FMT_BGR24. I hope you have some insight.
|
Hi Daniel, your work with Juce and FFmpeg are amazing.
I'm testing your video engine and the VideoPlayer example play the audio (from a mp4 video) but the video frames are black (no video).
I changed the scaler output pixel format from AV_PIX_FMT_BGR0 to AV_PIX_FMT_RGB32 and the video is playing perfectly:
https://github.com/ffAudio/foleys_video_engine/blob/master/ReadWrite/FFmpeg/foleys_FFmpegReader.cpp#L87
I changed
to
I see AV_PIX_FMT_BGR0 is CUDA accelerated, right?
I'm testing in Windows 10, compiling in MSVC 2017 and running in a laptop with a builtin nvidia graphic card. I suppose CUDA is not working in my side.
I'm compiling with FFmpeg 4.2.2.
You think is possible adjust the scaler output pixel format to match user machine?
Thanks for your time, I really enjoy your work as a developer.
The text was updated successfully, but these errors were encountered: