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

#1
1880 at 16:9 is nearly 80 MB/s at 24P, I have never seen anyone get that continuous on a MKII. Not to mention on MLV with audio won't be. That was the least important thing since the point was if the little bit of extra resolution was worth the effort. If you really want it they can probably add in both and you can crop off the extra 8 pixels in post.

My point is that the dev's do this work for us in their spare time and if they want to make things easier for them by sacrificing some resolution that is basically unnoticeable, maybe that is the best thing for ML.
#2
I realize we are all resolution junkies here but I seriously doubt anyone could pick out a 1856 frame upscaled to HD vs a 1880 frame upscaled to HD. It is less the 2% difference in resolution. I  bet if someone posted 10 shots with 9 1856 and 1 that was 1880 scaled to HD you wouldn't be able to pick out the 1880. Pixel peeping at %200 percent is virtually unnoticeable even when toggling back and forth, I can only see the slightest difference it very high contrast areas. Everywhere else shows no change and I certainly cannot say that one looks better than the other. I had to constantly remind myself which on was which when I was trying to determine if one was better. I have 20/15 vision BTW.

The difference in quality is so tiny it really isn't even worth the extra effort, I don't think it should even be called a quality difference just a difference. I would recommend shooting 1856 to get longer record times and smaller file sizes - 1856 is continuous and 1888 is not after all. I know there will be the "I want the highest resolution and best quality possible even if it is 1 pixel" replies, but in reality the quality difference is only in your head. If you disagree show us an example of how much better it is, if you can.
#3
Quote from: 5Djp on February 18, 2014, 07:00:47 AM
After tons of work, using dng's, and premiere, .. and afterfx.. The workflow sucks.. hands down.
Any chance of extracting the raw to .exr?  Its open source and followed by multiple programs.  Nuke, Afterfx, Premiere..etc
I'm doing the latest build on the Canon 5D Mark iii and MLV (extracting with MLV Converter).

I am sure it could be done, but it would be a fair amount of work and I bet you will have a hard time trying to find someone to work on that when there are many more pressing issues. I may be wrong but I believe mlv can dump to tiff's? If you want exr's you would have to export them form after effects, which I personally don't recommend since AE only does 32 bit- no half float option. 10 bit dpx files using a log camera profile is a good alternative and is much faster to work with than exr's even in nuke. Also if you are using nuke you can work with the dng's directly if you install the j_ops plugin, don't think it works with nuke 8 yet though.

You could also give a resolve a try, it can open the dng's and it exports much faster than AE, adobe debayer is still the best in terms of quality though.

Unfortunately the raw workflow is much more intensive, that is the price we pay.
#4
Raw video does not, has never, and probably never will work properly in 10x mode, so don't use it while recording.
#5
You press the zoom button on the upper right on the back of the body near the LCD screen, the same one that allows you to zoom the LV. Just press it once to 5x zoom, it doesn't work properly in 10x zoom.
#6
I found using the latest a.d. build 02/04 to be the most unstable one so far. I was recording on a 5D2 using mlv with audio at 1728 x 934 23.976 without FPS override, global draw on with magic zoom and digic peaking enabled.

I had several "Audio Failed to Stop" errors where I had to pull the battery.

I had several times when I pressed record I go a frame counter of -1 and the recording just froze. I had to turn off the camera where I got a message saying the camera didn't shut down cleanly and module loading would be skipped.

I had one card that about half way full just would not record any more, it acted like the card was full and I thought it was until I checked it on a computer. That card had some sort of .tmp file with the mlv's that caused issues why I tried to copy the files off the card, the mlv's copied just fine but the computer would not copy the .tmp file saying it was damaged and couldn't be copied. I was able to delete it though.

Out of 68 recordings of about 20 seconds long, I had 10 mlv's that were missing 1 frame, interestingly they were all right around frame 350 ranging from 349-354. I was shooting a a slower card with a max number of frames of about 450. I suspect these may have been recordings where the buffer filled up and the recording stopped automatically. All of the recordings had at least 420 frames so it is not the last frame that is getting dropped.

These are all very random so hopefully some of this info will help.
#7
I found using the latest a.d. build 02/04 to be the most unstable one so far. I don't what to double post so I put the details on the mlv modules forum.

http://www.magiclantern.fm/forum/index.php?topic=7122.msg100790#msg100790
#8
When the camera takes video the sensor captures an image that is 5616x3744 pixels in size. In order to get a HD size video the camera needs to reduce the size of the images to HD size. It does so by only reading every 3rd pixel from the image in width and height, 5616/3 = 1872 pixels(This is why the max resolution in non crop mode is 1872 and not 1920). Since it is reading every 3rd pixel instead of doing some sort of averaging the result is an under-sampled image that has aliasing and moire.

In crop mode the camera reads every pixel on a smaller portion of the sensor, about 1/3 of it. Since it is now reading every pixel and no longer skipping the image no longer has any aliasing or moire. It is internally performing and operation similar to opening the image in a editing program which is 5616 pixels wide and cropping out a section in the middle that is only 1872 pixels across. This effectively increases the focal length of the lens 3 times or mimics a camera with a crop factor of 3. This is also why it is called 3x crop mode even though you are using the 5x zoom on the camera. It is exactly the same as a 48 mm lens on a super 35 mm camera having the same field of view as a 24 mm lens on a super 16 mm camera.
#9
@giacomari

1.) The moire was always there it was just covered up somewhat by the h264 compression, the only way to reduce this is with a VAF Filter or shoot in crop mode as it doesn't have this problem.

2.) MLV is a new container for holding raw data with extra features like audio and meta data. The raw data is the same with both RAW and MLV. MVL is just a file format so it works on all windows, MAC and Linux(I think), there are some tutorials around that go through the process of using MLV and RAW as well.

3.) The newer builds merged in MLV and as a result some of the custom additions that a.d. added are no longer there since his was/is a custom build. The reason why 1880 is not there is because only the 5D2 can use it, the other cameras don't work well with it so it was not included to keep things consistent across all cameras.

4.) The size of the image you can shoot in crop mode is different than in non crop. Specifically you can shoot higher resolutions horizontally but lower resolutions vertically. The 1058 is probably the max possible height in crop.
#10
Thanks for the link I will check it out.
#11
Feature Requests / Re: H264 Custom pixel aspect ratio?
January 31, 2014, 10:52:28 PM
Thanks I believe I looked into those. The problem I am getting is that none of them seem to work with mov files, the ones already listed seem to only work with mkv, mpg, mp4, or avi. So far I would need to convert from mov to another format and that defeats the whole purpose as I might as well just fix the aspect ratio at the same time. Thanks for the suggestions though.
#12
Thanks that is the answer I was looking for and what I suspected. I just wasn't sure if there was something in the way ACR works that in some way limited the dynamic range of the output, sometimes there are compromises that are made for reliable output/color reproduction, were the log curve might retain a little more.

Thanks for answering my question.
#13
I guess what I am really wanting to know is would exporting a 16bit tiff file using your log profile offer any benefit over just exporting a 16bit tif without it. I realize if I decide to go with a 10bit intermediate then it is obviously worth it but for 16bit it may not be unless the profile working during the debayering process increases the useable dynamic range for example.

I am going to be doing some vfx work and having a log encoded image presents some issues that require some extra steps that may not be worth going through if I decide to go with 16bit intermediates. So far I have been getting pretty decent performance using 16bit. Now if the log encoding increases dynamic range then going with a 10bit log and dealing with those issues might be worth it.
#14
@Andy600 If I am going out to a high bit depth intermediate like 16bit, is there any benefit to using your log profile?
#15
Feature Requests / Re: H264 Custom pixel aspect ratio?
January 30, 2014, 10:32:54 PM
Thanks for the suggestion but it doesn't appear to work on mov files.
#16
Quote from: ted ramasola on January 28, 2014, 06:54:04 PM
On the mkII? What MLV version did you use that you experience this? What settings did you use, like resolution etc?
I'm trying to compile the report to devs on the nightly builds having problems.
As I posted earlier, jan 6 is stable on my tests.

It doesnt help just saying its not stable without a specific report on what build and settings you use.
I also experienced having shots without audio, but I realized it was my fault having failed to turn on MLV Sound in the menu.

I suggested devs turn off the audio meters when MLV_snd.mo not turned ON so it gives the user a hint.

I am using the Jan 14th build from a.d. I have experienced all of these except for the audio problems on earlier builds including the nightlies. So far these occurrences seem very random and fairly rare, I cannot pinpoint any specific trigger. I have filed some bug reports but I have no idea how to reproduce any of them. I am shooting either 1728 x 1036 or 1728 x 934 at 23.976 (no fps override), I have global draw on with digic focus peaking and magic zoom enabled. I believe I was using buffer fill method 2. Also all of the missing audio clips were from one card which had no audio on any shot, when I switched to a different card the remaining shots all had their audio.

One unrelated question does MLV audio work with FPS override enabled? I tried it when I first switched and it didn't buy I may have done something wrong.
#17
Yes MLV is magic lanterns own format but the raw video is the same as it was in the older raw format. MLV has more meta data, audio, card spanning on the MKIII, etc... However I would say that MLV is not a stable as raw, I am running into some little bugs like the camera hanging, missing frames in the middle of a sequence, audio that is shorter than its video, and recently I had 14 GB worth of video clips that had no audio at all, probably 20 different shots all on one card. At this point I would be hesitant to use it for paid work.
#18
Quote from: crazypig on January 27, 2014, 03:48:07 PM
Dear developers,

Is it possible to add TIMECODE in MLV file and the Audio WAVE file?

So we can auto sync the audio in Davinci Resolve...

5D3 can render timecode for h264 video.

Best regards,

Sean

Yes this would be awesome and a huge time saver.
#19
It was time lapse footage, he shot raw photos, cr2, and made a movie from that. There is no way it could be raw video.
#20
Feature Requests / H264 Custom pixel aspect ratio?
January 24, 2014, 06:03:04 AM
 I was wondering if it could be possible to override the pixel aspect ratio of an h264 recording? This would be awesome for anamorphics to be able to view the movies correctly with out having to post process them. It seems very silly to me to have to run the videos through an video editing app to ultimately make a change  that could easily be changed with a single modification to the file header(I suspect). Even if this isn't possible in camera a simple stand alone program to make the change would be great. Thanks.
#21
You will just need to upscale your footage a little bit, 106.7%. That would give you 2048x854, looks like the DCP you are going with is expecting a 2.39 aspect rather than 2.4. This is a very small upscale and should still look great. You could shoot 2048 in crop mode but I personally don't like shooting that way. Good luck.
#22
Quote from: looyod on January 22, 2014, 11:56:16 AM
2) In about 3 shots out of over 400 we had the issue of skipped frames, they are just missing. The Sound is fine.

I have ran into this a few times my self, seems totally random and rather rare. I am using a 5D2, I have also had some issues where the camera will not stop recording when the button is pushed. Going into the menu shows stopping... but never does (Well is does stop recording frames but never returns to normal function camera must be turned off and on). This issue is just as rare as the other.
#23
Raw Video / Re: Raw video on 5DMK2
January 15, 2014, 11:10:13 PM
Quote from: edgewood58 on November 08, 2013, 12:26:17 AM
Has anyone Used an ExtremePro 64gb SD card with 95MB/s in a SDHC/SD Extreme CF adapter when trying to shoot Raw on there 5D2? All that extreme must have canceled something out because it's extremely slow.

I am guessing that the 95 MB/s is the max read speed for the card may card advertise their highest possible speed usually read and it is generally much higher than the write speed. I have found that the write speeds on most cards is roughly half of the max speed posted for the card. So if you are getting around 45 MB/s, I would say that sounds right to me.
#24
Quote from: Shield on January 07, 2014, 08:56:44 PM
Still not getting a file that is readable in notepad.  I'm going to setup a batch for exiftool to just grab the info from the dng's extracted from the MLV browser.  What would really be slick is an option in MLV browser to "Export selected files as .dng +.wav +.txt"...I realize you're busy, but wow, things are really close.  The audio sync is perfect now.

try mlv_dump -v file.mlv > file.txt
#25
I have been using the newest build for a little while and have noticed a few things. Sometimes the recording will start go a few frames and then freeze up, the buffer no longer fills and the number of frames recorded stays the same but it acts like it is still recording. I stop the recording and go into the menu the MLV Raw menu shows stopping... but never does. I have to turn of the camera to get things working again.

Second occasionally when I run mlv_dump --dng, I will get a missing dng. A recent recording was missing just frame 181 out of 367 frames for example. Anyone else experiencing any of these?

Also I am using sound recording as well, so that may have something to do with it.