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 - Phillight

#1
Well, I was being quite simplistic in my decision making process. I see green, interpret go, I see red, interpret no :)

But anyway, thanks to your encouragement, I have now decided and downloaded ML to the 70D. It seems to work so far. Great.

I'd still like to know if there is a setting that can be changed so that the 5DIII would also use AF in LV-mode.
#2
Hi, I've been out of the loop for quite some time.

So, here's what I'm looking for: Use a camera as a webcam/ record HDMI signal via a capture card onto the pc - no internal recording.

I have access to either a Canon 5D Mark III or a Canon 70D.

I've tested with Magic lantern on the 5DIII and got basically what I wanted, except it does not autofocus in liveview mode.
The 70D does focus in live view mode, but always shows the white focus rectangle, which cannot be in the recording obviously.

I didn't install ML to the 70D because it says failed on the download website.

Is there a way to make the 5DIII autofocus continuously in live view mode? Or a way to remove the overlay of the 70D completely?

Thanks for helping!
#3
The video's quite good, the audio is superb, it has just the right impact and strength to make your subject pop, much like in the well produced martial arts movies. I'm glad he did't hit your gear :)
#4
itsDPmikey, I would like to ask you if you are using DaVinci resolve to render your footage, because if you do I just might know what's causing that flickering. I once had a "beta-testing" (if you know what I mean) version of DaVinci Resolveinstalled , (mind I didn't write DaVinci Resolve lite) and that was the exact same flickering I got every time I rendered something, especially when DaVinci's NR was applied. And your footage does look like it was treated with a faire amount of NR in DaVinci. I might be wrong, but that flickering bar at the top is very characteristic.

Anyway, try the lite version if that is in fact the case.

#5
@chmee, that wouldn't be of no use if I did what you suggested, because there (very, very oddly) is no further use for troubleshooting the problem since it no longer exists. I haven't then known what was causing the issue, I don't know now and I probably shall never know. All I have observed since is that it never occurred again like Harry Potters scar just never hurt again. (sorry for the stupid methaphor.)

I upgrated to the latest version of your awesome converter and to the latest verision of ML, so if there was a bug in any of the previous versions, I'm pretty sure that it was fixed.

As for now, I don't see a point in downgrading both versions and trying again to find it. Do you? If so I can do it as soon as I have the time.

Have you heard of anybody else encountering that particular issue with the latest versions of MLV RAW and cdng converter?

#6
If you enter the submenu of RAW recording module, you'll find your answer to the problem under 'Preview'. If you use the ML Greyscale preview, it will literally tell you that even though it looks ugly, at least the framing is correct.

RAW -> Preview -> ML Preview.

#7
Ok. I tried. I did try to find a way to reproduce the 29 fps issue. I did not succeed. I will post the image right here, so you can see for yourself.



I've been recording in every way imaginable to trace down what causes the fps to switch from my desired 23.976 to 29.976. I don't know what else to do. Everytime when I thought I know now what it is, it was not possible to reproduce it, and when I thought the settings I have now are fine, it happened again. Until I gave up, that is, a couple of minutes ago. Arbitrarily it happens... at least in my humble opinion. Its not the time its not the Preview mode, its not the lens, its not the ISO, its not the audio, its not the intervall between shots, its not the preallocation of memory, its not the extra hacks...

How can I provide you with something you smarter guys than me can work with?? Am I really the only one having that problem??

BTW, this afternoon I switched to the newly released version of ML, the one from yesterday.

From 1817 to 1858 I was changing settings like an idiot, I did everything, but obviously not a single clip came out 29 fps... that is very weird in my opinion...

SHORT EDIT: I manually changed (using Phil Harvey's ExifTool) the Framerate with that string: -IFD0:FrameRate=23.976 on all the clips that had different framerates. I couldn't synch the audio, though. But then again, I had Canon audio switched off and tried it by simply lining it up by timecode. Which I thought it should work if the time in camera and the audio recorder's time were synched.
I hope I'm not getting off topic here. Will continue to look for the cause right now.

Phil
#8
Does that mean we can be sure that this also causes the fps override issue? And is that a "real" bug or are the fps just wrongly written into the meta data, so that rawcdng or DaVinci get a faulty reading? Whatever it is I can do to help, I will do it as long as I am able :)
#9
Hello NedB, just to quickly clarify, Canon sound disabled and Filenaming were not the two issues I linked/connected. I connected the fps override issue with the Canon Sound issue. I will now post a couple of pictures by which I try to illustrate the aforementioned:

I uploaded a series of pictures to Google. Please read the captions and the appended notes to them. I hope I could describe the issue I have here as thorough as possible.

Thank you very much for taking interest!

https://plus.google.com/u/0/photos/103593325688024422825/albums/6037026448453372961
#10
Hello there and thank you for your replies, also thank you for developping ML, I don't wish to come across as someone who doesn't appreciate the effort others make in order to realize such a project. However, I did read quite a bit and I have so far shot only in "unreal" conditions. It means I did some testshots, played a little with this and that, liked it and decided that I now want to explore a proper workflow for "real" projects. So I jumped on YouTube and looked for a tutorial. I found one and liked it, so yesterday was the day for me where I started a little project in order to finish it from A to Z. The problems I came across I managed to solve some of them myself, some of them I couldn't yet fix and some of them are above me; about the latter I was hoping to gain some insight by asking about them. The problem with the green cast I managed to solve by fixing the BlackLevel. About the other problems I don't know where to go anymore, even though I tried to find threads in the forum about similar problems, I did find one concearning the fps override issue, but it wasn't (at least to my knowledge) solved.

So when I tried to reproduce the issue with the fps override, I didn't succeed. I had several guessings, though. I will list them:

ii) ML lets you choose between writing files into one directory or just in the DCIM folder. In choosing the option with the seperate directory, ML creates a folder that is named Mdd-hhmm.MLV. If you were to record two or more clips within the same minute, ML puts two (or more) folders on the CF-Card, all named the same. So in windows the path leads to only one file, even though all the files are there. My workaround is that I rename the files that came double myself, these aren't a lot usually. It doesn't happen too often that you record several clips within the same minute. A batch renamer would do the job as well I think. What also works is cut the folders on the CF-Card and paste it one after another, because (that's my amature-guessing) windows will clear one file and frees the way to the next file that was under the same path. Like M16-1234 exists 4 times on the CF-Card, cutting and pasting will clear the first one, then the next one and so forth. When prompted you just choose Copy, but keep both files and everything is there.

So I figured out issue ii). I don't know, as I said, much about programming and stuff, but I counted the characters that ML uses to name the files and folders, and they are 8 Characters long. That number is the same that canon uses. So I'm guessing that it is obligatory to name files 8 characters long? Would it be possible to leave the hyphen aside and replace it by upcounting number, so that the filenaming would be like:
M1611234
M1621234
M1631234
M1641234
M1651234
M1661237
...
M1791532
M1701532

So that the number counts from 1 to 0 no matter in what difference of timeintervalls clips are recorded, but ensuring that clips within the same minute will never be the same. And 11 clips in one minute is something not to consider.

I thought the option take in the mlv menu would do smth like that but it doesn't.

So far for the 'Recording several clips within the same minute with the option directory enabled'.

If the option create several directories is not enabled, the files count up and in that case the indicated time is off.

i) For the problem with the fps override I couldn't find a fix. In my previous post I literally spelled it out that I did set the fps override specifically on 23.976 in order that the regular recording and the crop recording match.
I couldn't find a way to reproduce this, I tried several things, though:

I tried recording with mlv_sound enabled, with it turned off. I tried it with a lot of different ISO settings, Aperture-values. I never changed the exposure time, I left that at 1/50th of a second.
It seems to me that it occurs arbitrarily with no recognizable cause. It happened so far on both of my CF-Cards, with all lenses I used.

I have tried all morning since 9am to reproduce that error that occured yesterday a couple of times, today everything seems fine.

Here's exactly what my setting was:

Canon 5D Mark III
Firmware: 123
ML Version: Date: 2014-07-04 00:01:21 +0200
Canon Sound: Disabled
(yet dim-wittedly on my side) MLV_Sound turned on.

This moring when I tried reproducing the tha fps override error I turned Canon sound on, I then, after turned Canon sound on I executed my testing with MLV_Sound on and off.

The error never occured again so far, so could it really be that this whole problem is due to the fact that I had Canon Sound disabled? I was recording the audio with my external recorder so I didn't need it, I didn't even need a synchsignal, that's why I didn't bother at all.

In the meantime I have insalled the latest version as of yesterday and tested a couple of recordings, in everyone of them the fps override did its job, Crop, Non-Crop. All is well so far. I will later in the day redo the testing with Canon sound disabled again, so if the error occurs again, I think I have found a reproducable cause for the default.

If you want me to provide you with more information, I will be happy to do so.

Thanks again for developping the ML Hack, that is really awesome of you guys!

Phil
#11
Hey there!

I've been playing for a while now with the RAW stuff and it amazes me. That being said, I wanted to "simulate" a real project under real conditions. I'm gonna make it short, what problems I ran into:

i) Some of the clips I took were recorded in 29.976 fps, even though I specifically set the fps override to 23.976. I shot about 30 clips, 4 are in 29.976 fps. That's weird, what could it be??

ii) If I took shots within the same minute, ML seems to keep both files, but overwrites them, so that only the last one taken can be decoded. It's in that format: M16-1510. The other folder has  the exact same name and the file it contains seems to be an exact copy of the other file, named M16-1510 as well. So one of the two will always be missing. What can I do?

I shot everything in 1920x1080, 23.976 fps, I used a Komputerbay 64 GB card as well as the latest ML version. Any help in solving these issues will be highly appreciated!

Phil
#12
Now, in a second attempt/test I used the Adobe Dynamic Link Manager to send the Ae comp into the Pr Timeline. When I now encode it into the exact same format, it goes roughly 75% faster. Qualitywise I'm not too sure yet. I would have to render the same clip probably with both methodes. But anyway, are you saying by this that the Adobe MediaEncoder uses ACR and the builtin Pr encoder does it differently?

/ I haven't even tried messing with all that other sweet stuff, like Hyper/Timelaps and multiISO, so for now I'm looking to establish a decent workflow for the "regular" stuff, if you know what I mean.
#13
Post-processing Workflow / ML, 5D3, RAW, AfterFX
May 28, 2014, 11:48:34 AM
Hi guys! So I did finally make the leap and installed ML 1.2.3 on the 5D3. After a couple of initial tests, I wanted to take a first glance at the graded footage. In order to do so, I wanted to use 3 methodes (Premiere, can't input DNG-files, DaVinci, looks disgusting, don't know why, flickers every couple frames, AfterFX). About the latter I want to ask my question.

AfterFX produces a pleasing image (I can't even tell you how ugly the image from DaVinci looks :-X ). But the problem ist that the mediaEncoder takes 50!!!! Minutes to render a 1.5 Minute clip. Now that can't be right?! DaVinci did the same clip, rendering at roughly 15 fps, in 2 Minutes. I usually never use Ae so I can only compare it to Pr, which usually renders my projects in a significantly shorter amount of time, even with Effects applied to the footage. I don't even know where to start.
Maybe I should provide you with my system's info:

16 GB Ram
Xeon E3-1275 V2 @ 4x4GH
GeForce GTX 770, 2 GB VRAM (it's plenty)
used disk:  SSD 480 Gig
I'm running the latest version of Adobe CC on Windows 7 Pro

I converted the *.RAW with raw2dng, graded it in Lightroom and imported the sequence into Ae, then, without any adjustments, sent it to the Me and it encoded it to YTHD in 50!!! Minutes.

So is anyone able to help me out here, like I said, I wouldn't even know where to start looking, since Ae is unknown territory for me.

If I ever were to put together a larger project, it would not be possible using this particular postprocessing method because the time it takes is just retarded

Thank you so much!
Phil