Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - megapolis

#51
Post-processing Workflow / Re: fastcinemadng
August 15, 2018, 03:56:06 PM
@12georgiadis
QuoteWhat could be improved with fast cinema DNG ?
1) generate ProRes Proxy via FFmpeg with a script that timestamp the same TC on proxy than on the MLV. Most cameras cannot generate proxy mlv in the same time (all except 5DmkIII) + script for 5DmkIII that correct black off frame from proxy & timestamp same tc on proxy than MLV
2) a system to generate on the fly CDNG with GPU rendering to speed workflow with resolve ? Or if not possible, generate CDNG that maintains the same TC and synch them to the proxy file (H264 or prores proxy)

I think that it could be done, but we need more sofisticated specification for the full task. Could you please prepare it in more detail from the very beginning till the end? We will probably be able to generate proxy .mp4, .wav and full-frame .dng series at the same time.
Here are some questions:
1. If we choose new start and stop positions for CDNG series, which time code we need to write to CDNG file at start position? Is it zero or not? The same question for CDNG file at stop position – which time code should be there?
2. If we choose correct start and stop positions at CDNG series, what we have to do with audio file? Should it be truncated according to start and stop coordinates?
3. I don't think that we need to do anything with black frame series because we will choose start and stop positions manually. Is it correct?
#52
Post-processing Workflow / Re: fastcinemadng
August 15, 2018, 01:37:56 PM
@theBilalFakhouri

QuoteI was using a build from about three months without problems in playback but the latest one I can't playback the file until I press the mute sound button and when sound is on the playback stuck, can you confirm that in Windows ? (I am on Windows 8.1).

QuoteIt would be nice if we can export .wav audio file beside Motion JPEG .avi format for MLV so we can have audio playback too after exporting to Motion JPEG.

In the latest release you can see bug fixes both for audio sync and for .wav audio at MJPEG:
https://www.fastcinemadng.com/download/download.html
#53
Post-processing Workflow / Re: fastcinemadng
August 03, 2018, 08:34:52 AM
QuoteAs said above, no ProRes 12 bits. Only Avfoundation.
As I know, ProRes is DCT-based compression algorithm, which is, to a certain extent, almost the same (not exactly the same) as JPEG. We have implemented 12-bit JPEG on GPU and it's super fast:
https://www.fastcompression.com/products/jpeg/12-bit-jpeg-codec.htm
Please note that libjpeg library also has 12-bit JPEG option and its performance is sufficient to get decoding in realtime on modest CPUs.
By the way, Blackmagic CDNG RAW 3:1 is also utilizing that compression algorithm.
Could it be a solution?

Quotej2k is interesting because if it's wrapped in MXF, it can be used for editing on all NLE.
I think that j2k is too heavy to be comparable with ProRes, j2k is too slow, though it could have better quality. To get smooth playback for j2k at full resolution, you need very good PC, no chances for laptop. I agree that j2k at MXF can be used at any NLE, but how many users really do that? In that workflow we will need multi-GPU PC. We are going to add such a feature, hopefully this year, but two GPUs will be a must. Our j2k codec on GPU is ready.

QuoteCdng is good and all the options you offer are excellent, but this format is sadly not very well handled by fcp X / Premiere / Avid.
Our software can smoothly process and play CDNG/RAW series at full resolution for 4K and higher. Can you do that with FCPX/Premiere/Avid smoothly not at ½ or ¼ mode together with high quality debayering? At the moment, external FFmpeg is the only option to use our software with any NLE. Interoperability with FFmpeg is working well.

QuoteThen, where we can use it except with Davinci Resolve?
At the moment that software is mostly utilized by our customers which are ok with export of JPEG series. In that case everything is done on GPU and this is very fast. It's called ingestion task for realtime multiple camera systems and that approach is also used in 3D and VR applications. Please have a look how it's working:
http://ir-ltd.net/introducing-the-aeon-motion-scanning-system/

I agree, that export to ProRes or DNx would be necessary for our software, but right now this is not possible. It's a shame. But you can use it with any NLE via FFmpeg.
We also have very positive feedback concerning our MG debayer algorithm and this is the reason why many our users do preprocessing at Fast CinemaDNG Processor software.

QuoteI think ProRes + J2k GPU encoding + GoPro cineform GPU is very futur proof editing codec as it can be used in cross platform.
It looks interesting, but we are not sure that this is standard approach. Implementation of such an algorithm on GPU will take at least a year (we are a small company), so before starting such a development, we need to understand why it's worth doing. Unfortunately it's not clear for us.
#54
Post-processing Workflow / Re: fastcinemadng
July 31, 2018, 06:23:43 PM
QuoteI wanted to know if there is a possibility to implement a batch for cinema offline workflow Id. Export ProRes 4444 12 bits (av foundation) + ProRes proxy that shares the same tc + reelname + name on metadatas. The idea is that we can edit with proxy for offline editing. Then conform with ProRes 4444.
Right now it's not possible at our software. You can do that in two steps:
1. Export from Raw to ProRes 4444 12 bits via FFmpeg
2. Export from Raw to ProRes proxy via FFmpeg
We are going to add scripting to the software in the future to be more flexible and I think that such a task could be solved then.

QuoteOr then what alternative codec to ProRes 4444 with C-log do you recommend ?
We can't give you such a recommendation. We think that ProRes is good.

QuoteI heard that jpeg2000 is lighter than APR444 but is it editable in Premiere Pro CC / FCP X / Resolve / Avid MC ?
We have experience with JPEG2000 and recently we've actually released GPU-based JPEG2000 codec. You can get more info here:
https://www.fastcompression.com/products/jpeg2000/gpu-jpeg2000.htm
This is very complicated algorithm and our JPEG codec on GPU is about 15-20 times faster. You can see our J2K benchmarks at the site. I think that J2K will make sense only in the case if there is a second GPU at your PC, exactly for J2K handling in realtim. So, J2K is not a light solution. It's quite heavy, but with high quality, and it supports 14 and 16 bits as well. Though, for small resolutions it could be ok even on a single GPU. Soon we are going to release MXF player on GPU, but this is different task.

QuoteCould it be contained in a .mov ? Can we put a log-c on it ?
Export to MOV is usually done via FFmpeg, so this is not a problem. As far as concerns Log-C, we still need to add a feature to import output curves from external files. Right now our software can't do that.

QuoteCan we have an offline workflow like working with APR Proxy and conform to jpeg2000 (sharing the same TC and name metadatas)?
We haven't done that yet. You can try it with our software via external FFmpeg, which can encode to J2K.

Quoteis it seen as one file and not multiple stills?
In general, if you save J2K frames in MXF file, then in will be just one file. You can also save J2K as multiple stills.

QuoteIs it faster to process from mlv than APR 4444 ?
We haven't done that comparison yet.

QuoteWhat about Cineform ? Is it compatible with CUDA ?
I think that Cineform could be implemented on GPU, but I haven't heard about such an attempts. In general, that algorithm could be done in parallel, but at the moment it exists only at CPU implementations, as I know.

QuoteBy the way, what demosaicing algorithm do you recommend to remove aliasing when you have a camera without vaf-filter (like eos-m)?
I don't know good solution for that task. Chroma denoising could help, but not too much. I think that current progress in debayering is slow and I think that we could expect good results only from machine learning side. Neural networks (CNN) show very good results, but they are still very slow. As I know, max debayering performance currently is around 1 Mpix/s on GPU at CNN.
#55
Here you can download free software for HQLI, DFPD and MG demosaicing algorithms:
https://www.fastcompression.com/download/download.htm
You can test DFPD debayer to evaluate image quality.
Please note that you will need NVIDIA GPU 6xx or later.
#56
Post-processing Workflow / Re: fastcinemadng
July 27, 2018, 07:55:00 PM
Thanks for your info and for mlv. This is a bug. I will let you know when we fix it.
#57
Post-processing Workflow / Re: fastcinemadng
July 26, 2018, 06:53:06 AM
Three months ago, as I remember, we didn't have full audio support yet. Since then we've added audio player and it could be a problem at playback if audio file size doesn't correspond to a number of frames in mlv or dng series. If you press mute, you switch off audio player, so audio can't affect the playback. Could you please send me a link to your mlv for testing to discover possible bug in audio player? You can do that here or via PM.

As far as concerns project loading time, it takes so long because before loading we need to reallocate GPU memory and recreate all GPU-based modules for image processing. These are not fast procedures. We know how to make it better, but the task is quite complicated and we hope to accomplish it by the end of the year.

MLV/DNG projects can be loaded fast if they have the same frame resolution and bit depth. In that case we don't need to reallocate GPU memory and we can reuse it. Please don't close current project before opening the next one. If all your mlv/dng are from the same camera, you will get fast loading for all projects starting from the second one at such approach.

If you have loaded one project and the next project has the same bit depth, but less or the same width and height, in that case the second project will be loaded fast as well. If your projects have different bit depths, in that case we always have to recreate image processing pipeline and it takes time.

Good SSD helps to read mlv/dng fast, this is very important to ensure smooth playback. This is especially important when you are loading uncompressed mlv/dng. Please note that our software is offering both mlv2dng export and dng recompression (dng2dng transform), so you will be able to get your dngs with lossless or lossy compression. You can also cut your dngs at the same time if you need.
#58
Post-processing Workflow / Re: fastcinemadng
July 25, 2018, 12:38:56 PM
Thanks for sending your screenshots and mlv files.
Now High DPI mode is working. Your spanned mlv files also could be loaded and processed.
The latest release is here: www.fastcinemadng.com/download/download.html
#59
Post-processing Workflow / Re: fastcinemadng
July 23, 2018, 10:01:12 PM
QuoteMost of the GUI scales a lot better on my 3840x2160 sceen, but the picture is very small now.
Have you tried to zoom the picture? Could I have a look at screenshot?

QuoteDon't seem to import more than the first mlv file. DNG's from M00, M01 etc. don't appear (only 102 dng's from MLV + M00...M21).
Could you please send me your set of spanned files for testing? We tested such files and there were no problems with them.
#60
Post-processing Workflow / Re: fastcinemadng
July 23, 2018, 05:50:03 PM
The bug is fixed and the latest version for Windows could be downloaded here:
www.fastcinemadng.com/download/download.html
Your MLV/DNG files could reside either on SSD or on network disk, the software should work. We have a user who is processing 5K CinemaDNG images on M.2 network disk via 10GigE and even at that case he can achieve realtime processing with our software.
In the latest release we've also added support of Kinefinity digital cinema cameras.
#61
Post-processing Workflow / Re: fastcinemadng
July 21, 2018, 08:24:21 PM
Thanks for your info. I've checked that and I can see that you are right - in the latest release, which we've uploaded yesterday, there is a problem at DNG export with Lossless JPEG compression. All other options for DNG export (uncompressed DNG, BMD 3:1, BMD 4:1 and BMD 5:1) are working well and you can use them. I think, we will be able to fix that on Monday. I will let you know.

For DNG export you need to set Output format to be DNG and in "DNG export" tab choose compression algorithm. Then press red button at Player panel and you will get exported DNGs at /Output folder.
#62
Post-processing Workflow / Re: fastcinemadng
July 11, 2018, 05:07:14 PM
I'm sorry for the delay. We have too many urgent things to do at the moment. Currently we are working on grayscale DNG support. We are also going to release pgm2dng opensource project at github soon. I hope that Linux version of Fast CinemaDNG Processor for Ubuntu 16.04 should be ready within 2-3 weeks. I will post that info here as soon as it's ready.
#63
Thanks for your images.
I've compared Amaze and RCD algorithms at RT and haven't found any noticeable difference. As I understand, at your pictures you could probably have different color spaces or different preprocessing before demosaicing, these differences could barely come from demosaicing algorithms. Please correct me if I am wrong.
#64
Quote from: 70MM13 on July 11, 2018, 02:54:34 AM
Rawtherapee has some excellent demosaicing algorithms that are far superior to amaze for very critical details.
Could you please supply more detail concerning that matter? Which demosaicing algorithms do you mean? Could you please show some examples for raw and processed images? Thanks a lot.
#65
Post-processing Workflow / Re: fastcinemadng
June 20, 2018, 09:45:26 AM
Some new features were added:
1. AVX speedup for focus dots removal
2. Export to EXR format
3. One can save current frame to any 24-bit image format which is supported in QT
#67
The tab "Output and extensions" is gray if you haven't closed the project.
Full manual is expected in a week.
#68
To enable any set of image processing modules in Fast CinemaDNG Processor, you need to close current project and go to dialog Options (right tab) - there you can check all available image processing modules. We've done that because sometimes user doesn't have enough GPU memory to utilize all available options.
#69
Fast CinemaDNG Processor could be utilized to convert raw data from CinemaDNG or MLV to ProRes. This is very fast pipeline because it's done on NVIDIA GPU. After that transform one could utilize Adobe Premiere Pro or AE, Davinci Resolve and any other software for editing.

The latest version for Windows could be downloaded here:
www.fastcinemadng.com/download/download.html
Linux version is expected soon.

For resolutions less than 1920x1080 that software will be free, you can check licensing info at the site. Yes, at the moment this is evaluation version, final release is expected within 3-4 months. Anyway, one can use that software as CinemaDNG or MLV player for fast preview of raw footages – this is also will be free.
#70
Post-processing Workflow / Re: fastcinemadng
May 21, 2018, 07:45:22 PM
QuoteIs Nvidia 980m supported? Older versions worked with it, not sure if you changed anything
Yes, it should work. Previous version of the software was based on CUDA-8.0 which was compatible with 5xx series of NVIDIA GPU. Now we've moved to CUDA-9.1 and that's why minimum requirement is 6xx NVIDIA GPU.
980m is laptop gpu and quite powerful. This is Maxwell architecture which is fine.
#71
Post-processing Workflow / Re: fastcinemadng
May 21, 2018, 02:12:49 PM
Quoteit doenst work  on my laptop with 2gb nvidia graphic
Which GPU model do you have? Minimum requirement is GPU of 6xx series (Kepler architecture). Have you installed the latest NVIDIA driver? 2 GB should be ok for images up to Full HD.
#72
Now DNG to JPG converter is a part of Fast CinemaDNG Processor software which is working on NVIDIA GPU. These are main options for MLV converter:
http://www.fastcinemadng.com/info/mlv/mlv-converter.html

1. MLV to TIFF/JPG
2. MLV to movie (to MP4 via external FFmpeg)
3. MLV crop, project trimming, transcoding to DNG/CinemaDNG
4. MLV crop, project trimming, transcoding to CinemaDNG RAW

To get the best performance for MLV to JPG/TIFF transform, it's a good idea to utilize fast SSD, because quite often total performance is limited by SSD write time.
#73
Post-processing Workflow / Re: fastcinemadng
May 21, 2018, 01:07:45 PM
Thanks a lot to @g3gg0 for the help with MLV format understanding and for making the file mlv_structures.h to be LGPL. We are also very thankful to @AWPStar, @IDA_ML and to other people from ML forum for useful comments.

We've finally implemented MLV support at Fast CinemaDNG Processor software and we can play and process MLV on GPU natively. Now it's possible to open MLV files from Windows Explorer via context menu, or one can set file association .MLV to open MLV with Fast CinemaDNG or drag-n-drop MLV file to the application window. The latest version for Windows could be downloaded here:
www.fastcinemadng.com/download/download.html

Please bear in mind that the software is working on Windows with NVIDIA GPU only (Kepler or better), it's not working without such GPU. The latest NVIDIA driver should be installed as well. Your feedback is welcome. If your MLV file can't be loaded or it's loaded with errors, please send us the link to your MLV file for testing.

The software supports 10/12/14/16-bit uncompressed MLV files or compressed with lossless jpeg. We also extract and play audio. MLV to video transform could be done via interoperability with external FFmpeg which should be installed by user. We've also implemented support for spanned MLV files and option to export CinemaDNG series out of MLV with lossless or lossy encoding.

The first project is loaded not very fast as soon as we need time to load application, to initialize CUDA, to check and to allocate GPU memory. If the next project has the same frame resolution or less, and the same bit depth, then it will be loaded immediately. If new project has bigger resolution or different bit depth, then we will have to reallocate GPU memory and recreate GPU pipeline for image processing, so MLV import will take more time.

More info you can find here:
http://www.fastcinemadng.com/info/mlv/mlv-processing.html

What you can do with Fast CinemaDNG Processor software
1. This is fast MLV Player with image processing on NVIDIA GPU
2. Realtime debayering, denoising, resizing, sharpening, geometric transforms, etc.
3. Support for DCP and LCP profiles
4. Color grading with 3D LUTs (cube format)
5. MLV export to TIFF/JPG or to video

This solution could be quite fast if you have good SSD, CPU and GPU. MLV preview should be smooth. To check the performance, please have a look at benchmarks widget to see timing for each stage of image processing. One can also perform a transform from MLV to JPG series to see how fast it could be.
#74
Post-processing Workflow / Re: fastcinemadng
April 05, 2018, 11:50:34 AM
We've implemented a new feature to import CinemaDNG raw footages to Adobe Premiere Pro. The subject is not straightforward, as soon as there are many possible choices for CinemaDNG encoding and formatting. For example, for the latest Blackmagic cameras one can't import CinemaDNG Raw files to Premiere Pro and it could be the case with other encoding options for CinemaDNG as well. An idea to save DNG series with better compression and correct formatting is also important for further editing in Premiere Pro. I hope that it could be relevant here as soon as ML users are working with Adobe Premiere as well.

We've implemented CinemaDNG transcoding to the format which is native to Adobe Premiere Pro CC.
This is converter pipeline at Fast CinemaDNG Processor:

  • CinemaDNG import, parsing, decoding
  • Export options: Uncompressed CinemaDNG, CinemaDNG with Lossless JPEG, CinemaDNG RAW 3:1, CinemaDNG RAW 4:1, CinemaDNG RAW 5:1
CinemaDNG workflow to prepare footage for Adobe Premiere Pro:

  • Run Fast CinemaDNG Processor
  • Load CinemaDNG footage via drag-n-drop or context menu
  • Choose project output format to be DNG
  • Choose encoding method: Uncompressed or Lossless JPEG
  • Press red button on Player
  • Wait for transcoding to be finished
  • After transcoding you can find at Output folder new footage with specified encoding
Uncompressed export option includes the following bit depths: 8-bit, 10-bit, 12-bit, 14-bit, 16-bit. For compatibility with Adobe Premiere Pro CC one have to utilize either Uncompressed or Lossless JPEG export options.
#75
Post-processing Workflow / Re: fastcinemadng
March 29, 2018, 10:39:19 PM
Sorry for late reply.
At the moment we haven't finished with UI management, so the only way to reset the interface is to delete the following branch in registry HKEY_CURRENT_USER\Software\Fastvideo\  and to reinstall the software.
MLV support is expected in April.