I am adding .cine capability to pims (Python Image Sequence) by @tcaswell
https://github.com/soft-matter/pims
using python-cine. This will give it more features and a uniform interface to other types of camera files.

However, the GPL3 is inconsistent with the license for PIMS and so the python-cine code and PIMS cannot currently co-exist in a distributable package.

Would it be possible to dual-license the code?

Hi there,
it would be great if also the tagged information blocks would be read out from the cine file, in particular the Time only block, which gives the timestamp of each image and the Exposure only block, which gives the real exposure time of each frame (it may vary for different frames). See page 30 of the cine file format manual (version 2011).
I could not find a way to load that information in the current pycine module.

Is it possible to release a new version for PiPy with the recent changes, so that all can profit from the improvements?

.chd header files are created when Phantom software saves the images in a file format other than .cine (.cine docs). It would be good if pycine could read these files too. Apologies if this functionality is already available in the package and i have missed it.

.chd files have exactly the same format as the .cine header, so can be read using a function that is near identical to pycine.file.read_header -- just without the last couple of lines that add the "pImage" key to the header dict.

The proposed function would look something like this:

def read_chd_header(chd_file):
    with open(chd_file, "rb") as f:
        header = {
            "cinefileheader": cine.CINEFILEHEADER(),
            "bitmapinfoheader": cine.BITMAPINFOHEADER(),
            "setup": cine.SETUP(),
        }
        f.readinto(header["cinefileheader"])
        f.readinto(header["bitmapinfoheader"])
        f.readinto(header["setup"])

    return header

What do you think?

My .cine video returns setup.CFA = 0 so the function does not work.

I was interested in having a viewer than can go through the cine with some kind slider in a GUI.
I wrote it in my fork using PyQt and pyqtgraph.
adrianroth10/pycine/blob/master/pycine/viewer.py

To make it working I also changed the structure of the frame_reader in raw.py from a yield iterator to a class.

It seems to be working for one of my cine file. What do you think?

This is already almost finished. Just creating an issue so people waiting for it can get notified.

Dear all,
I use a Phantom highspeed camera which saves the data in cine-files. Therefore I use pycine to open the files and work with them. Overall it works quite nice.
But I found a discepancy between images I export directly from the Phantom software compared to the imported frames via pycine. It is not only a difference in global intensity values as expected for 8, 12 or 16 bit. It is also a different dynamic! Here you see a plot for two different exports from the Software (CV) with different bit depths and from pycine (Python). It is normalized to [0,1] to see the different dynamics.

I used the following code for saving the frames as tif files:
raw_images, setup, bpp = pycine.raw.read_frames(pin, start_frame=1) for i, raw_image in enumerate(raw_images): imsave(os.path.join(pout, 'frame_py_{}.tif'.format(str(i).zfill(4))), raw_image)

Can someone tell my, why I get different dynamics and how I can solve this issue?

Kind regards
Stefan

OCC does "ei2.5" and on-cam save translates that to "ei2_5". PCU does "ei2-5".
Unfortunately all of these have issues in resolve.

The code is already written and being used in production for a long time. It's currently written in cython but could also be ported to plain python if needed.

@ehki
https://github.com/OTTOMATIC-IO/pycine/blob/master/pycine/raw.py#L45 and https://github.com/OTTOMATIC-IO/pycine/blob/master/pycine/raw.py#L67 and https://github.com/OTTOMATIC-IO/pycine/blob/master/pycine/raw.py#L110

I think we can port the algorithm from the example C code provided by Vision Research.