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.

Messages - megapolis

Pages: [1] 2 3 4
Post-processing Workflow / Re: fastcinemadng
« on: June 09, 2022, 09:06:16 AM »
Unfortunately MacOS support is not possible.
Our SDK for GPU-based image processing is available for Windows, Linux and ARM (Jetson).

Post-processing Workflow / Re: fastcinemadng
« on: May 27, 2022, 03:42:49 PM »
In the latest release (which could be downloaded from the site) you can find experimental version of defringe feature to suppress the consequences of chromatic aberrations. The feature still has some minor artifacts on the image borders, but it's working and pretty fast.

Post-processing Workflow / Re: fastcinemadng
« on: May 24, 2022, 12:01:52 PM »
It's a pity that it doesn't work for me even after reinstalling. I tried logging the installation of your program in order to then delete its remnants manually, including registry entries, but even that didn't help. After rebooting and reinstalling, the demo mode still remains, but the most important thing is that my presets remain in the export settings via ffmpeg, which means that the program files still remain in the system and do not allow the program to perform a clean installation and not work in demo mode. This is my guess. Perhaps other users will also encounter this. I really hope you fix it :) This will be the best thing that has happened to me since I met magic lantern.

Thanks for your info. Application settings are not stored in the registry now.
They are at C:\Users\<UserName>\AppData\Roaming\Fastvideo LLC.ini
Licence file is stored at C:\ProgramData\Fastvideo
1. Please check the software version. The latest version should be, build 1124.
2. Please check license file *.dat in the folder C:\ProgramData\Fastvideo. If you see such a file, please rename or remove it and run the software once more.

We don't remove licensing info after reinstalling, this is a feature, not a bug.
If the above info won't help, please send us your questions and screenshots either here or via PM.

Post-processing Workflow / Re: fastcinemadng
« on: May 23, 2022, 07:38:12 PM »
I thought it would help you to identify possible problems ...
Thanks, we will check that.

Tell me, is there a possibility to export personal video files without a watermark or did I misunderstand you about this?
Yes, it should work.

Post-processing Workflow / Re: fastcinemadng
« on: May 23, 2022, 06:48:00 PM »
For free version you don't need to enter the hardware id.
We need that hardware id to issue the license, but for free version you don't need it.

Post-processing Workflow / Re: fastcinemadng
« on: May 22, 2022, 05:28:41 PM »
What does "is free for non-commercial use" mean?
"Is free for non-commercial use" means that your can use it for free for your non-commercial projects. For commercial projects you will need to acquire the license.

Will the label "Demo version" disappear when exporting?
Please download the latest version and run it, the software should work without "Demo version" label.

Post-processing Workflow / Re: fastcinemadng
« on: May 05, 2022, 05:55:52 PM »
I hope you get it working.  The painfully slow processing times and flickering issues make it nearly useless currently.

This is difficult to forsee when it could be done. Dual ISO mode exists not only at Canon image sensors, this is also the case with Gpixel and CMOSIS. We have been developing GPU-based image processing software for such cameras, but none of the customers needed dual ISO mode up to now. So it's not yet ready.
Currently there is more sofisticated approach to enhance dynamic range. This is a Dual ADC mode at SONY Pregius image sensors of the 4th generation. Such a mode also exists at Gpixel image sensors as well. We've just implemented that solution on GPU and you can see more info at my article in the blog:

Post-processing Workflow / Re: fastcinemadng
« on: May 04, 2022, 11:38:46 AM »
For testing purposes we've done dual ISO, but it's on CPU and such an implementation would affect real time performance which is the key feature. We haven't added dual ISO to the software because we don't have that module on GPU yet.

Post-processing Workflow / Re: fastcinemadng
« on: April 27, 2022, 02:20:30 PM »
1- There no soft highlight roll off, the absolute highlights looks crushed. Am I missing something here?
Would it be ok if it's like soft clip in Resolve?

2- Focus pixel fix affect the whole image, fastcinemadng doesn't use focus pixel maps. this might degrade image quality a little.
Yes, this is how we've done that. We will check how it could be done on GPU with pixel maps.

P.S. Have you tried to convert MLV to DNG series with our software? You can also recompress existing DNG series as well.

Post-processing Workflow / Re: fastcinemadng
« on: April 26, 2022, 04:24:31 PM »
You are welcome.
Please note that this is not just MLV viewer, this is a raw to rgb (raw to jpg) converter, which is very fast on GPU. You can also convert your MLV files to lots of video formats with external FFmpeg as well.
As far as concerns MLV preview, you can run it at full screen by pressing Tab and you can also upscale video output - these are quite useful features.

Post-processing Workflow / Re: fastcinemadng
« on: April 26, 2022, 02:12:52 PM »
Linux version is ready, but it's not yet updated to the latest SDK on CUDA. We will do that soon.
Unfortunately Mac OS is not compatible with CUDA, so we can't release the software for Mac.

Post-processing Workflow / Re: fastcinemadng
« on: April 26, 2022, 01:19:20 PM »
Starting from the current release, Fast CinemaDNG Processor software is free for non-commercial use.
The latest version of Fast CinemaDNG Processor software could be downloaded from

Post-processing Workflow / Re: fastcinemadng
« on: March 18, 2021, 12:30:24 PM »
The latest version of Fast CinemaDNG Processor software could be downloaded at

If you want speed, just go with fastcinemadng.

This won't fix the AF points or help me with other MLV-specific raw fixes though. It's not really a full solution. The only app with the proper raw controls is MLV app. That's where Cuda needs to be added (along other optimizations, let's not put all the blame to the lack of GPU support).

This is not correct. In the Fast CinemaDNG Processor software there is a module to suppress AF points. You just need to close current project and go to Option dialog, choose MLV tab and mark "Fix focus dots". If it doesn't work, please send us your MLV file for evaluation.

Post-processing Workflow / Re: fastcinemadng
« on: May 04, 2020, 08:30:27 PM »
We’ve released Linux version (Ubuntu 18.04, 19.10, 20.04) of Fast CinemaDNG Processor software which is working on NVIDIA GPU. It includes all features which we already have in Windows version, including the following:
1. Smooth RAW Video Player for MLV, DNG, BRAW
2. RAW transforms: MLV to DNG, BRAW to DNG, DNG to DNG
4. Output to authentic Apple ProRes 422 LT, 422, 422 HQ, 4444, 4444 XQ
5. Bad pixels removal, dark frame subtraction, FFC, wavelet-based denoiser
6. Support of DCP and LCP profiles, 1D and 3D LUTs
7. Improved performance for NVIDIA Turing GPUs (RTX series)
8. Interoperability with external FFmpeg

Linux version of Fast CinemaDNG Processor could be downloaded here:

How to install Linux version:
sudo apt install ./fastcinemadng-1.0.10-4_amd64_Ubuntu_18.04.deb

Post-processing Workflow / Re: fastcinemadng
« on: March 17, 2020, 08:00:57 AM »
New features at Fast CinemaDNG Processor software:
1. Improved BRAW processing for BMPCC 4K and 6K
2. Support for Canon CR2 and CR3, Nikon NEF formats

The latest version of Fast CinemaDNG Processor could be downloaded here:

Post-processing Workflow / Re: fastcinemadng
« on: December 06, 2019, 06:51:09 AM »
We’ve released open source project PGM2DNG to transform raw images from PGM format to DNG. You can get more info and source codes at
We need to convert PGM to DNG to be able to process them with our Fast CinemaDNG Processor software. Usually this is the case with machine vision and industrial cameras.

Post-processing Workflow / Re: fastcinemadng
« on: October 16, 2019, 11:54:31 AM »
I can’t really call BRAW to be an open standard. Unfortunately we can’t find BRAW format specification either, we can see just Blackmagic SDK manual, that’s all. The manual doesn’t include that spec, this is the problem.
Sure, you can do a lot with Blackmagic SDK, but you are supposed to work with processed images because Blackmagic has already done decoding and raw processing. This is the idea they are trying to push.
As far as concerns “partially debayered” data, it also sounds strange, because hardware capabilities of BMD cameras just can’t be compared to modern CPU or GPU, so this could hardly be partial debayering. It looks like an approach for specific data representation which is more suitable for fast lossy compression in camera hardware.
If I remember it right, RED has patented in-camera compression with wavelets, so the situation with BMD doesn’t look the same.

Post-processing Workflow / Re: fastcinemadng
« on: October 15, 2019, 03:22:20 PM »
In the latest version of Fast CinemaDNG Processor software we’ve implemented native support of BRAW format from Blackmagic Design. Apart from BRAW Player, there is an option for BRAW export to CinemaDNG. It’s working quite well, but not perfect. To the best of our knowledge, this is the only solution for raw export from BRAW footages. Please download and test the software. Your feedback is welcome.

Post-processing Workflow / Re: fastcinemadng
« on: September 06, 2019, 10:46:45 AM »
We’ve added the following fixes and new features to the Fast CinemaDNG Processor software:

1. Dynamic bad pixel correction on GPU. There is no need to have a list of bad pixel coordinates, the software can find and interpolate bad pixels in realtime at RAW domain. On NVIDIA GeForce GTX 980 we need around 1 ms to remove bad pixels from 12-bit 12-MPix image. We used to have that feature on CPU and now we’ve implemented it on GPU. It’s working with 8-16 bit raw images (bayer and grayscale).
2. Apple licensed their ProRes encoder to us, so we’ve included Apple ProRes support on CPU. Now we can export processed frames to original Apple ProRes 422 LT, 422, 422 HQ, 4444, 4444 XQ. We can offer MLV to ProRes and DNG to ProRes transforms.
3. Motion JPEG output encoding on GPU now is working well with audio.
4. We can store JPEG and TIFF images to SSD in a separate thread after GPU processing, so total processing time is better now.

The latest version of Fast CinemaDNG Processor is here:

Post-processing Workflow / Re: fastcinemadng
« on: July 02, 2019, 09:15:48 PM »
Thanks for your info. At the moment H.264 or ProRes could be added via external FFmpeg only. It’s not really hard. You need to specify output format as FFmpeg and then set correct command line for FFmpeg. Not ideal, but looks acceptable.

Thanks, we will check audio output synchronization for Motion JPEG. It’s also done via FFmpeg.

Focus pixels we are correcting on CPU and you are right that it’s slow. We haven’t finalized the algorithm yet, so we don’t have GPU version.

Currently we are doing Bad Pixel Correction (BPC) on CPU as well. This is adaptive averaging over 5x5 window for RAW data. Within a couple of weeks GPU-based version should be ready. At the moment we are utilizing CPU version for testing.

I think that dynamic BPC is much better than pixel maps. There are different types of bad pixels (hot, dead, bright, etc) which could be seen in different situations. So it’s quite difficult to create precise map for all these cases. There is also image sensor degradation, so we have new bad pixels to come out. Our BPC is working as impulse noise filter and quite often it corrects 5,000-10,000 pixels per 10-20 Mpix image, which we think to be good. We expect that total time for BPC will be really small on GPU, though right now we do that on CPU and it’s slow.

MLV (DNG) playback with audio implies that for a particular audio packet we will process corresponding RAW frame without any delay. This is not always the case even on GPU and this is the reason why we see such jerks. We could probably do some prefetching to fix that issue. Audio doesn’t need a lot of processing and at the second run it should work smoothly.

Post-processing Workflow / Re: fastcinemadng
« on: June 18, 2019, 01:14:22 PM »
Dual ISO feature is very interesting, but I'm not sure that we will be able to implement it soon on GPU. Hopefully, we will release soon some other features like automatic bad pixels correction, defringe and some more.

We are doing quite a lot of other projects with GPU image processing, not only for MLV/DNG. You can see more info here:

Post-processing Workflow / Re: fastcinemadng
« on: May 24, 2019, 09:49:20 PM »
We’ve implemented a new version of dark frame subtraction and flat-field correction in Fast CinemaDNG Processor software. As usual, everything is done on GPU, so it’s quite fast.

We can apply flat-field correction (FFC) and dark frame subtraction by providing two corresponding linear RAW images in PGM or DNG format. To prepare these images from DNG files we can use dng_validate.exe utility from DNG SDK.
This is a command line to get FFC image: dng_validate -16 -2 FFC <path\to\dng>

This will extract 16-bit linear RAW data into FFC.tiff. The FFC and dark frame width and height must be exactly the same as width and height of the processed RAW file. Otherwise the correction will not work.
To supply FFC and dark frame files, click “...” buttons next to “Dark frame” or “FFC frame” field. To temporary disable correction, uncheck “Enable dark frame and flat field correction” check box.
To disable whole FFC and dark frame corrections, uncheck "Dark frame and flat field correction" check box in the application processing options.

The latest version of Fast CinemaDNG Processor is here:

Post-processing Workflow / Re: fastcinemadng
« on: March 30, 2019, 11:57:11 AM »
The latest version of Fast CinemaDNG Processor is here:
Now it's based on CUDA-10, so please update your NVIDIA driver before running the software.

It's not straightforward to port complicated solution from Windows to Linux. We need to port not only GUI, but also full GPU image processing SDK. We are working on that, sorry for the delay.
We do need NVIDIA GPU to offer high performance solution.
Soon we will release new SDK with less requirements for GPU memory, so any NVIDIA GPU will be fine.

Pages: [1] 2 3 4