Messages

Thanks !

Thank you Danne. WHen you say Non crop mode you mean 1736*976 ?

Tricky question to answer. The mv1080 mode is missing on the EOSM but Danne has a crop_rec module that will put it in mv1080 mode. He also has builds with the experimental sd_uhs module which allows longer recording times at higher resolutions. I've recorded continuous 2520x1080 at 24fps with audio using his builds. Note that all APS-C cameras in mv1080 mode will only record a maximum of about 1736x976. You probably already know this but it is worth repeating for newer users that might be reading this.

Thank you Dfort, it's always good to refresh our mind and the progress of the thread. I just bought an EOS-M and want to experiment. That's why I'm asking about the current possibilites. So, if I understand correctly, there is a build with Sd_uhs hack + MV1080 (1736*976) and 2520*1080 or this are all separate builds ? 1736*976 is lineskip 3X3 ?

@12georgiadis
You're right that the options I mentioned only work for color aliasing, it doesn't work for annoying moire patterns.
Shooting 1x3 should fix this in 99%(I guess, because even camera's that don't do binning and lineskipping can suffer from moire patterns, since the pixels on the CMOS are pretty straight aligned in rows and columns)
The problem for now is that shooting in 1x3 takes up 3x the amount of resolution and thus 3x the amount of data to be recorded.

Ok, good to know...

Thank you for the example Levas. I can see the improvement for defringing but my concern is also aliasing and I can't get rid off in my try. On the other hand, this 1X3 binning mode seem to be the solution, especially if it's done before going in post, isn't it ?

Thank you Levas ! Yes LMMSE available on RawTherapee. I tried with a dual iso footage from 5DmkIII but it wasn't working well.

Luckily I know my ways to get rid of color moire, so still going strong on 3x3 

And what is your method ? =)

Only problem is the H.264 proxy. I haven't had much luck with it on the EOSM. I believe that the LiveView brightness when switching to various bit depths and lossless compression has been fixed--at least I don't see the problem on the latest versions.

Thank you for the update Dfort. Do we have continuous rec in 1080p 24fps 14bit lossless +12 bits lossless with eosm  or only with 8...11bits ?


Envoyé de mon iPhone en utilisant Tapatalk

Insane work for 96fps and remove aliasing 1x3, even for dual iso !!
This is fantastic and if the bitrate remains the same, it means that all camera could benefit of these function !
No need for expansive vaf anymore !



Envoyé de mon iPhone en utilisant Tapatalk

Hi All,

Is it possible to get 24 fps, 1080p raw 8...11 bit lossless & h264 proxy on EOS-M by using SD hack ? When we use 8...11, is it darker than usual on liveview or normal ?
Thanks

@Reddeercity, you helped us a lot with your research. Please don't give up. You've done an amazing work for D4 improvement.

Maybe we can change the name of the thread if we have to include CF cards investigation. And thank you all for the ressearch effort. And @reddercity, you are very helpful and you've participated a lot to the progress of D4 Raw. Let's try talking here about SD / CF investigation. If it's the chaos, I hope that someone from the forum moderation would split again the topic if it's necessary.

[/url]



Hello Danne, I'm cleaning 10 hours of h264 proxy from 5DMKIII, and switch is running. But it shows me this parse error message (see the picture) 

What does it mean ?

log :
https://pastebin.com/sYV9guek

Edit : I batch renamed h264 files to correspond to the MLV's name.  It's still showing errors...
Edit2 : just 5 shots worked and now they are named like this : FY5A0516_1_2017-08-30_0001_C0000
It's good if we generate DNG files via MLVFS. But if we relink with the new XML option from MLV, we could keep only the original name. I don't understand what's wrong with my files.

One thing I haven't tried yet was to "force hdmi to low rez."
There a option to force hdmi to 720x480 the same size as liveview , I'll try tomorrow .

For one project, I needed a monitor HDMI + raw rec on 7D and had a black screen. Force to VGA low rez solved the problem for liveview

@12georgiadis
Thanks a lot for your info. You can use my email from https://www.fastcinemadng.com/contacts/contacts.html
or you can send PM to me.

check on MLV app threads. Features have been implemented with FCPXML. Still some tests to do from Resolve => Pr CC / Avid MC to convert fcpxml to xml/aaf.

No. I have sometimes some colored artifacts in trees - these are a bit less with IGV... but therefor on clean surfaces you'll find a kind of structures.

ok, good to know

@danne, @masc : you guys rock !

@masc, @danne, is there a function that cut black frame on h264 + reset tc to zero to sync it with MLV ?

Compiling instructions can be found here: https://github.com/ilia3101/MLV-App
You are on Windows? You just need a Qt5.6 or newer installation with MinGW, then download sources from github and follow the instructions. If you are on OSX, try Dannes compiler app, which leads you through...

Mostly AMaZE is the best demosaic algorithm. For some clips IGV or LMMSE may look a little better, specially if AMaZE brings some false color artifacts.

MLVApp still runs 100% on CPU, that is why it runs on nearly every computer from the last 10 years or older, no matter which OS (Win/Linux/OSX), what CPU or what GPU (if there is any at all). Since the last version we support much better multithreading, what made rendering up to double speed to before.

Thank you masc for all informations !
I'm on Mac so will try danne's app compiler !
Ok for amaze but do you think lmmse or igv can help to reduce aliasing ?
Ok for cpu, i understand and totally agree with this choice to keep things universal. And superb for multi threading !


Envoyé de mon iPhone en utilisant Tapatalk

Just use mlv app compiler in the first post...

Ok danne, I'm gonna try it ! Super cool that you made it more easier


Envoyé de mon iPhone en utilisant Tapatalk

@12georgiadis: you can compile it? It is just commited to the repos. Cool, would be nice to know if it works fine with 5D3 proxys!
Hehe, yes, I went crazy with my own little projects: ~500 MLVs and only 50-100 of them were used in a project and have to be corrected/graded. Selecting these files manually was very time consuming and borring.

No, don't know how to compile... but if you have a tuto link, I can try. Same here 30 hour of footage and 1 hour at the end, I didn't want to find all clips manually =D By the way, I saw some new debayering algorithms. What is the best between IGV, LMMSE and Amaze ? Does MLV app works on CPU usage ? Or some the playback is GPU ?
Thanks!

@12georgiadis
Yes I read that, but it was implemented before... nice to hear it mostly works. I can't tell you what version of fcpxml is compatible - I have no spec and reverse engineered. I think your problem is, that Resolve renames the clips. Somewhere in the settings you can setup the clip names to real names. Maybe check this and it should work again. All MLVApps assistant needs is a coorect clip name. In the fcpxml I just search for e.g.

Code Select Expand

<clip name="M04-1441"so I know I have to search for M04_1441.MLV in the folder you set in the assistant. If Resolve builds clip names of e.g. M04-1441_0000001-0000054 my assistant is lost atm.

Edit: I see, Resolve is exactly doing what I expected plus I found another small bug. Will do a fix for all that...
Edit2: Done. All versions of fcpxml from Resolve opened fine now.

Thanks Masc, I didn't know it was already implemented, I'm even more happy that someone else found this idea helpful !
OK, I'm going to test your new version.
I'll also test with a 5DmkIII h264 proxy + mlv recording footage.
What is cool is that resolve can maybe convert xml v5 from premiere pro cc / fcp7 & AAF from avid to Fcpxml, so you wouldn't have to implement these type of files. We have to test it too but if it works it can help for all kind of NLE !

@masc : incredible update ! you seem to have read my #114 post on fast cinemadng forum about the MLV conformation. I'm currently testing it with proxys from MLV app. For now, MLVs are detected and well imported from an FCPXML with ProRes proxy edit in MLV app !
Later, I'll try to export these Mlv into APR444 and conform on Resolve with the same Fcpxml, to see if it replaces ProRes proxy with 444 and keep the edit correctly

edit : working with mlv from eosm
1) exported proxy from mlv app
2)imported in fcpx
3) exported fcpxml
4)importe in mlv app and use fpcxml assistant, pointing to mlv = OK
5) exported pre-corrected MLV to ProRes 444 = ok
6) import fcpxml resolve = ok to point to prores 444 keeping the editing

fail : form this timeline, export to fcpxml and reimport to mlv app = not working

what version s of fcpxml are compatible in mlv app ?

Thanks,

one example of my previous film

@12georgiadis
That solution is not yet ready, so it's not worth speaking about advantages. We are working on the software which will work as a server, without GUI, to process big quantities of frames on one or several GPUs. As soon as we could have many different workflows, we need to develop scripting to be able to cope with different tasks. This is concerned not only with mlv/dng, but also with much more solutions for massive image processing.
We already can process mlv/dng over network, so there is no need to copy raw data to your local PC if your network is fast enough.

Thanks for your suggestion. We will need your examples, and it would be better to start from standard, non-exotic workflow.

Ok for server solution.
For workflows give me a contact e-mail and I send you some pdfs.




Envoyé de mon iPhone en utilisant Tapatalk