Wed, Jul 11
Mon, Jul 9
Sun, Jul 8
I tested this on Linux with various file formats and libopenimageio 1.8.12 .
Image proxies can be useful tho, what about transparent images/sequences? It would be nice if these were proxied in a way to preserve that transparency.
No, we want only AVIs for proxies.
For consistency sake, I would generate AVI even for image, just 1 frame long video maybe for speed reasons.
Also if it was up to me, I would like to make it possible, so every image generating sequence could have proxy.
From my use of video proxies (in VSE and MCE) if a video is an image sequence
there is no frame rate or time code so it's rendered as an image sequence.
But for a video there is a frame rate so it's kept as a video.
I have looked at the code, where the problem lies - the main problem is that we want to generate MJPEG video for proxies instead of a bunch of jpeg images. Making filename would be quite silly reason for dropping functional feature...
@ International Space Station
Sat, Jul 7
I am also interested in a resolution to this bug.
Fri, Jul 6
I was proposing change(D3484) for VSE proxy system.
Fri, Jun 29
Is it possible to get this looked over before 2.8 bata?
Thu, Jun 28
I switched to TIF file format to continue my work. TIFs color channels can be read by single.
I hope this is the right place to place my problem. If not please open a new task.
Wed, Jun 20
I'm afraid we'll have to archive this report then.
Feel free though to reopen this if you've found a way to reproduce [or enjoy if this never happens again:)]
Jun 14 2018
ffmpeg setup in blender seems OK, pCodec is set to jpeg2000 correctly.
anim->pCodecCtx->pix_fmt is AV_PIX_FMT_RGB48LE
anim->pCodecCtx->bits_per_raw_sample is 16
anim->pCodecCtx->bits_per_coded_sample is 8
Jun 10 2018
Jun 1 2018
This is quite odd, I'm back on the computer which initially presented the issue. However i'm no longer able to reproduce the issue, even after following my own steps to reproduce the issue word for word. As a result, I'm unable to do the troubleshooting steps you have provided. And there is no way for me to provide a phone recording, since there is nothing to record.
May 31 2018
Thats odd, I tried reproducing on a different device (My laptop) and failed to produce the same error. While the issue would show itself without fail on the initial device (my school's desktop) when i followed those instructions.
May 30 2018
Apr 11 2018
Just a first note: can confirm this.
Apr 10 2018
Apr 7 2018
Mar 23 2018
@Campbell Barton (campbellbarton) Polite nudge.
Just would like this looked over before 2.79b release...
Mar 18 2018
Mar 14 2018
More than a week passed without a reply.
Mar 7 2018
Mar 3 2018
Feb 19 2018
Jan 15 2018
Not sure about the folderstructure (I dont see that here)
But I can confirm a crash
Dec 7 2017
The patch is now committed to master, and in fact solved the issue for Sebastian. The image is still flipped, but all tools here shows it like that. The header also suggests this is a correct orientation... Needs more investigation, but is unrelated to this patch.
@Sergey Sharybin (sergey) Thanks! I tried the patch, but it did not work. Neither the MCE nor the IE can open the image. If I try, it gives me an error: IMB_ibImageFromMemory: unknown fileformat (/home/sebastian/1-38_A002.0000811.dpx)
I'll open a report.
@Sebastian Koenig (sebastian_k) , please try this patch P572. The image is indeed flipped upside-down, but it's same as OIIO opens it as well. In any case, please open a report with a file attached, so we can reference it from commit message.
Dec 6 2017
What a pleasant coincidence! I just had the problem a few days ago that I could not load a DPX file into Blender which I got from some other application. I used EXR instead as workaround. But I tried the patch and that actually works (even though the frame itself is flipped)! Here's a frame from the sequence that did not work:
We do need to have files to justify whether this change really fixes anything or not. I am fully unhappy even considering applying such a non-trivial patch without knowing what is broken. It also makes it more difficult to do regression tests if we don't know what is broken.
Nov 30 2017
Good find! Confirmed.
Here's a fix that seems to work:
Nov 29 2017
True. I'd also consider this a bug. Not a dramatic one of course, but it is indeed an inconsistency...
Nov 23 2017
See also "precision limitations on integer values" here:
Half floats can store maximum 65536, but definitely not all integers in between. I think we should always store ID passes with full float precision, regardless if the half float option is used.