Hi Ben
On Mon, Feb 03, 2025 at 04:02:15PM +, Ben Lu via ffmpeg-devel wrote:
> Sure, looks like gmail is complying with a plaintext email RFC. Let me try
> attaching to eml with:
> `git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix
> .eml --to ffmpeg-devel@ffmpeg.org -1
Sure, looks like gmail is complying with a plaintext email RFC. Let me try
attaching to eml with:
`git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix
.eml --to ffmpeg-devel@ffmpeg.org -1 0f497eb391b`
On Mon, Feb 3, 2025 at 3:22 PM James Almer wrote:
> On 2/3/2025 10:58 AM,
On 2/3/2025 10:58 AM, Ben Lu via ffmpeg-devel wrote:
Sorry about that, it looks correct in gmail and sending to myself also
looks fine, not sure where the line width corruption is happening. Our org
doesn't allow programmatic email.
Looks like lines with a single blank space are being replaced
Sorry about that, it looks correct in gmail and sending to myself also
looks fine, not sure where the line width corruption is happening. Our org
doesn't allow programmatic email.
Is it possible to use this gist?
https://gist.github.com/ayroblu/1d7bbfdf82aa9a127abefa4c5d518cdb
Also trying again:
Hi
On Sat, Feb 01, 2025 at 12:18:08AM +, Ben Lu via ffmpeg-devel wrote:
> When using pad with eval=frame with variable frame sizes, we get
> significant artifacting. This is due to incorrect frame sizes, resulting in
> invalid frames. Made changes to use the output width and height for frame
>
When using pad with eval=frame with variable frame sizes, we get
significant artifacting. This is due to incorrect frame sizes, resulting in
invalid frames. Made changes to use the output width and height for frame
sizes when using eval=frame, with if statement guards to make sure the
normal usage
