ImageSource Avisynth problem

[arthurm]

Hey there,

So, a few months ago I posted a question about converting 3D DCP's to 3D ISO's (MVC). I got a lot of help from Cornucopia (Thanx!) but eventually found a total different way to do it. I use a tool called myDCPconvert. This tool basiclly did this:
- It encoded all the .j2c frames to PNG images (000000L, 000000R, 000001L, 000001R, 000002L, 000002R...) using the tool asdcp.
- Then it used a "Vapoursynth Python Script" (.vpy) to create a SBS video for FRIM to encode.
- Then the tool used FRIM to encode the MVC and AVC stream using the standard Avisynth input line but instead of a .avs file the input was a .vpy file.
- Then it used TsMuxer for the ISO, but that's not important, considering this is only about the AVC/MVC stream.

Now, I have a new computer but, like I also experienced with some other computers, FRIM gives an error when it gets the VPY file as input. So, I decided to re-view the information that Cornucopia gave me. I had to edit it a bit to fit with my image sequence, but unfortunately, I can't get my Avisynth script to work. I will the next files in a .RAR file:
-frames from asdcp
-.avs script
-.vpy script
-FRIM/Avisynth error BMP
-frim code

Some usefull info on the video itself: the video only has to be from frame 312 to 3793, but I already added that in the .avs script so that should be OK.

[jagabo]

You have the start and end numbers wrong. And you need to use a proper filename spec. This will work with the png files in the same folder as the avs script:

LView=ImageSource("%06dL.png", 855, 860, fps=24, pixel_type="RGB24")
RView=ImageSource("%06dR.png", 855, 860, fps=24, pixel_type="RGB24")

And your original script loaded the "L" images into both LView and RView.

[arthurm]

Yeah sorry, my fault, but the images I uploaded were just 5 rondom picked. Otherwise I had to upload 48,1 GB of images .
I fixed the L/R letter, but it still gives the same error.
Also, when I use the scipt in the same folder with your code, it still gives the "DevIL library" error.

[jagabo]

Also, when I use the scipt in the same folder with your code, it still gives the "DevIL library" error.

Not for me:



I'm using AviSynth 2.6 but I doubt that matters.

[arthurm]

weird! I'm also using avisynth 2.6.0 but virtual dub can't open it and gives the same error. Is there maybe something wrong with a DevIL plugin (it says I have version 166)?

[Cornucopia]

I had a similar problem recently and had to totally uninstall & reinstall both AVISynth, Vdub, and all the plugins. Never found out for sure exactly where the problem was coming from, but it (the problem) went away.

Scott

[jagabo]

weird! I'm also using avisynth 2.6.0 but virtual dub can't open it and gives the same error. Is there maybe something wrong with a DevIL plugin (it says I have version 166)?

Did you copy from my post and paste into your script? Do you realize your original script didn't even specify .PNG?

[arthurm]

Thanx! I finally got it working in virtual dub! (I had to add PNG indeed ). but now I can't get the file to work in FRIM. The error it gives: cannot get YUV420 frame from input avi-file D:/INPUT.avs

the avs code I now use (works in virtual dub):

LView=ImageSource("%06dL.png", 855, 860, fps=24, pixel_type="RGB24")
RView=ImageSource("%06dR.png", 855, 860, fps=24, pixel_type="RGB24")
LView1080=Spline36Resize(LView, 1920, 1080)
RView1080=Spline36Resize(RView, 1920, 1080)
CombinedView1080=StackHorizontal (LView, RView)
MVCReadyView=ConvertToYV12(CombinedView1080)
return (MVCReadyView)

I think it has something to do with the pixel_type="RGB24" and the pictures themselves, but don't think that replacing it with RGB48 is a good solution. The pictures are 48 bits.

[jagabo]

I don't know anything about FIRM but YV12 is YUV420. And you script is converting to YV12. Open the script with VirtualDub and select File -> File Information. Verify that the script putting out YV12.

[Cornucopia]

3D Blu-ray works just like Blu-ray: 4:2:0 YUV. Maybe FRIM internally converts, but if it doesn't you WOULD need to convert first.

Scott

[arthurm]

@jagabo, VirtulDub does indeed give me that information. I've also tried it without ConvertToYV12. Virtual dub does work then but FRIM still doesn't.

@cornucopia, I am converting the full video now, but I did a test using those 5 frames I sent you, and FRIM says it can't open the AVI file.

[arthurm]

OK, it looks like this video is doomed to work. Also the AVI file (41,9GB) doesn't work with FRIM. I've attached the AVI from the frames I sent before. The error FRIM gives:

C:\Users\Arthur\Documents\FRIM_x64_version_1.23\x6 4>FRIMEncode -avi -sbs 2 -i D:
\TEMP\avisynth.avi -viewoutput -o::mvc D:\TEMP\avisynth.avc D:\TEMP\avisynth.mvc
-vbr 28000 40000 -u 1

ERROR: Cannot get YUV420 frame from input avi-file D:\TEMP\avisynth.avi
Frame was written in default format to file D:\TEMP\avisynth.avi.error.bm
p

ERROR: File reader initialization failed.

ERROR: Cannot start encoding process.

Is there maybe something wrong with the [pixel_type="RGB24"] or [MVCReadyView=ConvertToYV12(CombinedView1080)] in the AVS script?

[poisondeathray]

-i D:\TEMP\avisynth.avi

what is avisynth.avi ? shouldn't it be an .avs ?

Or did you encode to an avi for input ?

[arthurm]

That's the AVI version of my AVS file. I just use avisynth for all filenames to make the extensions because the file extension is more important. but both avisynth.avs and avisynth.avi do not work.

[poisondeathray]

what does mediainfoxp (view=>text) say about the avi version ? Copy & paste the text view here

I haven't used frim, but it looks like an x64 version. Is your avisynth x64 ? otherwise you need some way to bridge x86 <=> x64 otherwise. A physical AVI shouldn't have that problem

[arthurm]

FRIM: 64x
Avisynth: 86x

So I will thy it again with avisynth64

Mediainfo for the AVI:

General
Complete name : D:\TEMP\avisynth.avi
Format : AVI
Format/Info : Audio Video Interleave
Format profile : OpenDML
File size : 42.0 GiB
Duration : 2mn 25s
Overall bit rate : 2 486 Mbps
Writing library : VirtualDub build 35491/release

Video
ID : 0
Format : RGB
Codec ID : 0x00000000
Codec ID/Info : Basic Windows bitmap format. 1, 4 and 8 bpp versions are palettised. 16, 24 and 32bpp contain raw RGB samples
Duration : 2mn 25s
Bit rate : 2 486 Mbps
Width : 3 996 pixels
Height : 1 080 pixels
Display aspect ratio : 3.700
Frame rate : 24.000 fps
Bit depth : 8 bits
Bits/(Pixel*Frame) : 24.000
Stream size : 42.0 GiB (100%)

[poisondeathray]

avisynth2.avi is RGB, and so is avisynth.avi

How did you convert it ? If vdub, did you use forget to use video=>fast recompress ? That would explain why it is RGB, not YV12

[poisondeathray]

The AVI route should work for sure, if you converted it correctly

People tend to avoid avisynth x64, because it's less stable, fewer filters available for it

The other options, since it looks like frim accepts stdin, are to pipe avs input in with something like avs2yuv or ffmpeg

[jagabo]

Yes, you converted the YV12 output of AviSynth to RGB when you saved the AVI file. That's the default behavior of VirtualDub in Video -> Full Processing mode.

[arthurm]

I had it on full processing mode. But now I tried it in 'direct stream copy'. I've tested the 5 preview frames. mediainfo:

General
Complete name : D:\TEMP\avisynth.avi
Format : AVI
Format/Info : Audio Video Interleave
File size : 37.0 MiB
Duration : 250ms
Overall bit rate : 1 243 Mbps
Writing library : VirtualDub build 35491/release

Video
ID : 0
Format : YUV
Codec ID : YV12
Codec ID/Info : ATI YVU12 4:2:0 Planar
Duration : 250ms
Bit rate : 1 243 Mbps
Width : 3 996 pixels
Height : 1 080 pixels
Display aspect ratio : 3.700
Frame rate : 24.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Compression mode : Lossless
Bits/(Pixel*Frame) : 12.000
Stream size : 37.0 MiB (100%)

unfortunately FRIM still gives this error:

C:\Users\Arthur\Documents\FRIM_x64_version_1.23\x6 4>FRIMEncode -avi -sbs 2 -i D:
\TEMP\avisynth.avi -viewoutput -o::mvc D:\TEMP\avisynth.avc D:\TEMP\avisynth.mvc
-vbr 28000 40000 -u 1

ERROR: Cannot get YUV420 frame from input avi-file D:\TEMP\avisynth.avi

ERROR: File reader initialization failed.

ERROR: Cannot start encoding process.

So I think it is better to either re-instal Avisynth in a 64x version or use FRIM 86x. Which of these two is best, and IF I need to re-instal Avisynth, what do I need to do? there are no official 64x releases.

[jagabo]

Even though the YV12 video is uncompressed you still need a VFW YV12 "decoder" to handle it. You can use ffdshow for that. Or just use a compression codec like UT Video Codec or Lagarith that supports YV12 (be sure to specify YV12 in the codec properties). That will give you smaller intermediate files too.

[poisondeathray]

I haven't used FRIM, so I cannot answer what is "best". I can only advise that avisynth x64 isn't ideal due to stability issues and fewer filters available. I would avoid that if possible

There are different kinds of "planar" 4:2:0 YUV files. First, can you test this one, it is fourcc "IYUV" which is usually more compatible with windows software than avisynth's "YV12". (unzip it first, of course, and change your commandline to reflect the filename)

[arthurm]

Okay... @jagabo, I dodo have ffdshow intalled in k-Iite (I know it's it's a bit unprofessional ) but where can I read instructions on setting the VWF up?

[jagabo]

Start -> All Programs -> ffdshow x64 -> VFW Configuration -> Codecs (left pane) -> Raw Video (right pane) -> Enable (pulldown) -> YV12.

I don't know FRIM -- it might use DirectShow instead of VFW. If so to the same for Start -> All Programs -> ffdshow x64 -> Video Decoder Configuration.

Remember the 32 bit and 64 bit video systems are completely separate. You need to use 64 bit ffdshow for 64 bit programs, 32 bit ffdshow for 32 bit programs.

[poisondeathray]

If you can't get it working, just use the 32bit version - that's probably the version you had working on your older computer in the first place

"suitable for direct decoding/encoding and Avisynth (Intel Media SDK - INDE 2015 Update 1)"

http://forum.doom9.org/showthread.php?t=169651



"IYUV" should work in all programs, since the decoder is included in Windows since XP . It gets "magical" treatment, such as passthrough of YUV in programs such as NLEs . Other fourcc's like "YV12" typically don't get treated as "lossless" and get converted to RGB

[arthurm]

yes! I've finally managed to get FRIM encoding properly. I had:
FFDshow VFW 86x (even in K-lite)
FRIM 86x
AviSynth 86x
and it works now.

But...

I have FRIM encoding now, but the AVC and MVC files almost have the sameoutput size:
AVC: 70.710 kB
MVC: 70.380 kB

I assume the difference between the file size should be significantly bigger.

Here's what FRIM is showing me now:

INPUT\avisynth.avs -viewoutput -o::mvc D:\TEMP\NEW\avisynth.avc D:\TEMP\NEW\
avisynth.mvc -vbr 28000 40000 -u 1
FRIM Encoder version 1.25 (build: Mar 27 2015)
- based on Intel(R) Media SDK

Media SDK impl HARDWARE - D3D9 (C:\Program Files\Intel\Media SDK\libmfx
hw32.dll)
Media SDK version 1.8
Memory type System
Async depth 4

Input format YUV420

Output video AVC
Source picture:
Resolution 1920x1088
PAR 0:0
Structure Progressive
Crop X,Y,W,H 0,0,1920,1080
Destination picture:
Resolution 1920x1088
PAR 0:0
Structure Progressive
Crop X,Y,W,H 0,0,1920,1080
Frame rate 24.000
Bitrate control VBR
avg,maximum 28000,40000
GOP structure:
GOP length 24
I-/P-frame distance 4
IDR-frame interval 0
GOP type Opened
Num of slices 6
Target usage 1 (quality)

Processing started
Frame number: 1515

I've used new images that I created with FFMPEG this time, because of the problems of cropping the video in AviSynth;

ffmpeg -i "INPUT.mxf" -r 48 -s 1920x1080 -pix_fmt rgb24 D:\TEMP\NEW\REEL1\image_%05d.png

I then renamed them to 00000L, 00000R, 00001L, 00001R, 00002L, 00002R etc.

Then I used this AVS script for FRIM:

LView=ImageSource("D:\TEMP\NEW\REEL1\%05dL.png", 312, 3793, fps=24, pixel_type="RGB24")
RView=ImageSource("D:\TEMP\NEW\REEL2\%05dR.png", 312, 3793, fps=24, pixel_type="RGB24")
#LView1080=Spline36Resize(LView, 1920, 1080)
#RView1080=Spline36Resize(RView, 1920, 1080)
CombinedView1080=StackHorizontal (LView, RView)
MVCReadyView=ConvertToYV12(CombinedView1080)
return (MVCReadyView)

[arthurm]

Nevermind... There was something wrong with the video itself. Since I got it working now and it has been such a long problem for me ( to solve) I will make some kind of tutorial on it soon.

Thanx to Cornucopia, poisondeathray and jagabo for helping me with this.

[jagabo]

I have FRIM encoding now, but the AVC and MVC files almost have the sameoutput size:
AVC: 70.710 kB
MVC: 70.380 kB

I assume the difference between the file size should be significantly bigger.

file size = bitrate * running time

So use a lower bitrate if you want a smaller file.

[arthurm]

yes, but I the file sizes should be different. here is is the size from a 2.30 AVC/MVC video:
AVC: 377MB
MVC: 192MB

so as you can see the difference is bigger.

What AVC/MVC is: http://www.sonycreativesoftware.com/dostudio/understanding_3d_authoring_blu-ray_3d_mvc_encoding

I've also tried it with RGB48 PNG images, but it doesn't work, like I thought.

[jagabo]

yes, but I the file sizes should be different.

No. If the overall average bitrate is the same the file sizes should be the same. It's the very definition of bitrate. Aside from some small container overhead differences.