-
Notifications
You must be signed in to change notification settings - Fork 278
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
WIP: fix crashes with video widths not multiple of 4 #577
base: develop
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -759,11 +759,11 @@ void Frame::AddColor(int new_width, int new_height, std::string new_color) | |||||||||||||
} | ||||||||||||||
|
||||||||||||||
// Add (or replace) pixel data to the frame | ||||||||||||||
void Frame::AddImage(int new_width, int new_height, int bytes_per_pixel, QImage::Format type, const unsigned char *pixels_) | ||||||||||||||
void Frame::AddImage(int new_width, int new_height, int bytes_per_pixel, int bytes_per_line, QImage::Format type, const unsigned char *pixels_) | ||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The old signature could then just be turned into: void Frame::AddImage(
int width, int height, int bytes_per_pixel,
QImage::Format type, const unsigned char* pixels_)
{
AddImage(width, height, bytes_per_pixel, type,
pixels_, (width * bytes_per_pixel));
} |
||||||||||||||
{ | ||||||||||||||
// Create new buffer | ||||||||||||||
const GenericScopedLock<juce::CriticalSection> lock(addingImageSection); | ||||||||||||||
int buffer_size = new_width * new_height * bytes_per_pixel; | ||||||||||||||
int buffer_size = bytes_per_line * new_height; | ||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alternatively, if you are gonna change the signature of (Plus it's totally implied by |
||||||||||||||
qbuffer = new unsigned char[buffer_size](); | ||||||||||||||
|
||||||||||||||
// Copy buffer data | ||||||||||||||
|
@@ -772,7 +772,7 @@ void Frame::AddImage(int new_width, int new_height, int bytes_per_pixel, QImage: | |||||||||||||
// Create new image object, and fill with pixel data | ||||||||||||||
#pragma omp critical (AddImage) | ||||||||||||||
{ | ||||||||||||||
image = std::shared_ptr<QImage>(new QImage(qbuffer, new_width, new_height, new_width * bytes_per_pixel, type, (QImageCleanupFunction) &openshot::Frame::cleanUpBuffer, (void*) qbuffer)); | ||||||||||||||
image = std::shared_ptr<QImage>(new QImage(qbuffer, new_width, new_height, bytes_per_line, type, (QImageCleanupFunction) &openshot::Frame::cleanUpBuffer, (void*) qbuffer)); | ||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If libopenshot/src/effects/Shift.cpp Lines 79 to 84 in 414a2cd
And potentially dozens more just like it, hiding scattered around the code. We are unfortunately not rigorous about using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Very good catch. Now, using QImage but NOT using bytesPerLine(), in my opinion, is very poor code hygiene and we should fix all of these cases, since we should not assume only certain types of QImages get here. However, fixing all of those effects to use bytesPerLine() properly is costly. Here's another option: we could leave the input to AddFrame with this bytes_per_line, but we could copy row-by-row into the QImage without any extra padding, so the QImages remain "packed" and all those effects will work unchanged. This would be slightly lower performance (hundreds of row-by-row copies instead of one bit batch copy), but that may not be meaningful, and it wouldn't change assumptions out from underneath all our users of QImage. As I said above, I'm open to any/all of these thoughts. Let me know what you think and I'll revise the pull request based on what we decide! |
||||||||||||||
|
||||||||||||||
// Always convert to RGBA8888 (if different) | ||||||||||||||
if (image->format() != QImage::Format_RGBA8888) | ||||||||||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps it'd be better to add this as an additional overload, rather than redefining the existing
Frame::AddImage()
semantics? There may be external API consumers who rely on the previous signature.To make overload resolution slightly less harrowing, there's some argument for tacking
bytes_per_line
on at the very end. Arguably it's a detail specific to the buffer, not a parameter describing the image (like all of the other parameters surrounding it), so it should (optionally) follow the buffer it describes — and only in the cases where it's necessary to specify it. (IOW, only whenbytes_per_line != width * bytes_per_pixel
.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A lot of good questions there, and I'm open to any solution. Here's my thoughts:
I don't consider the Frame class part of the externally exposed API of libopenshot, so since there are no other uses of this function, I felt safe changing it. If we consider the Frame class as something external callers can use, then I agree it should be a separate overload.
I see your point about bytes_per_line at the end; it doesn't matter to me, and I see the argument that it's a "property" of buffer.