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

Pages: [1] 2 3 4
General Help Q&A / Re: How to view Enfuse Image on Canon 'M'
« on: January 25, 2018, 09:19:14 AM »

Raw Video / Re: Image sequence in premiere is 25% faster
« on: February 15, 2017, 08:38:29 PM »
Great! You're quite welcome.

Raw Video / Re: Image sequence in premiere is 25% faster
« on: February 14, 2017, 11:32:05 PM »
@Alexmach: Did that do it? It would be nice to know that you read the answer. Thanks.

Raw Video / Re: Image sequence in premiere is 25% faster
« on: February 13, 2017, 09:37:37 PM »
@Alexmach: There is a default setting (Indeterminate Media Timebase) in Premiere which assigns a frame rate to an imported image sequence. In this case, it has almost certainly assigned a frame rate of 29.97 (NTSC) instead of what you want, which is 24. Find the setting and change it to 24, and your problem should go away.

Try this: Go to Edit>Preferences>Media... and change the Indeterminate Media Time Base to what you want (23.976 or 24)...problem solved.

Guys - sorry for (stupid?) question (not a beginner, been using ML since 2012). Downloaded and installed dfort's 10-bit/12-bit build from Nov. 19 for my 550D. But, try as I might, I cannot find where to set the bit depth to 10-bit or 12-bit for testing purposes. Anybody wanna cut me some slack and point it out explicitly for me? Does it require certain modules to be loaded or other settings to be set correctly in order to appear? Thanks, gentlemen!


Edit: Thank you very much for insanely quick reply, Levas!

General Development / Re: Linux on your Canon DSLR? Why not?
« on: April 02, 2015, 10:58:12 AM »

Raw Video Postprocessing / Re: Noob 5D3 and MLV RAW pp - any easy way?
« on: December 29, 2014, 08:42:38 PM »
Yes, that's correct. Cheers.

Duplicate Questions / Re: 2-3k footage without crop
« on: October 05, 2014, 11:32:08 AM »
@RWBrooks: See an explanation for this at, reply #3.

In no sense are the "UHD frame sizes" deactivated, so that a simple "activation" would change this. ML raw, at this point in time, relies on whatever the camera sends to LiveView. Only in so-called crop view are resolutions greater than the native resolution of the LiveView display possible. So it's either normal view, up to display resolution, or crop view, up to some limit which varies depending on the camera model.


P.S. @swinxx: say what? Or do you mean, "buy another camera"?!

Raw Video / Re: Issue with all video takes cut short by 6 seconds.
« on: September 14, 2014, 11:04:10 AM »
@acoustified: In After Effects, in the Project window, select the clip, right-click on it, select Interpret Footage>Main>Frame Rate>Assume this frame rate, and type in the correct fps.

Explanation: When you first install AE, it defaults to using 30fps for all imported image sequences. If you never changed that default (Edit>Preferences>Import>Sequence Footage), it will continue to do this. If most or all of your footage is a particular frame rate (like 29.97, 25, 23.976, etc.), then change it here. Otherwise you have to make sure to check and/or change the Frame Rate for each imported clip. Cheers!

...oh, and let me know if this helped, ok?

General Help Q&A / Re: True Resolution of H.264 Video
« on: August 18, 2014, 08:10:44 AM »
Yes, this seems to be the case.

@squidman90: ML captures and records the data from the path that also sends the picture to LiveView. So in "normal" mode, the highest resolution you can get is the native resolution of your LiveView display, which varies from camera to camera. In your camera, that is 1728x972, and that is achieved by processing the entire sensor area via line-skipping (in all cameras except the 5dIII) or pixel-binning (for the 5dIIII, a much higher-quality process). BUT, when you hit the 5x zoom button, your LiveView display is showing a zoomed-in version of what you saw before, and it is doing that by simply cropping out a rectangle from the entire sensor area with no line-skipping or pixel-binning. It is simply a 1-1 view of a part of your sensor. Since it is not reducing the rectangle to fit into your LiveView display, it can be either smaller or bigger than your native display resolution. Just how much bigger varies by camera. That's why you have to be in so-called "crop mode" to get a bigger resolution than 1728x972. If you want to get around this, buy a 5dIII (at least for now, who knows what the ML wizards will come up with in the future!). Cheers.

Raw Video / Re: Uncompressed 14-bit RAW video testing - 5D Mark III
« on: July 17, 2014, 02:51:49 PM »
@Phillight: I think the reason you have not been able to reproduce the error is that it can't/didn't happen. I'm pretty sure that a1ex and the other devs thought about this problem when they developed .raw and .mlv. As far as I know, ML uses the current time to name the clip unless that name has already been used, in which case it is incremented by one (unless that name has also been used, etc.). This is a quick fix and I guess a bit of a hack, but given that they only had the 8 characters, there wasn't much choice. So the "time stamps" for .mlv (and .raw, I think) clips are more-or-less accurate, except for this caveat that they may be off by a few if you shoot multiple shots beginning in the same "wall-clock" minute. I think this is what a1ex meant by "it should never happen". No offense meant, hopefully none is taken. I just don't believe there were any "hidden files" with the same name, I don't think ML allows it. Not sure to make of what happened (or seem to have happened) in your case... But, cheers!

Edit: Good effort at debugging and trying to find the source of the "problem", but I think the chances are very small that this file-renaming issue (if it really exists) had anything at all to do with whether or not you had Canon sound disabled.

General Development / Re: SRM job memory buffers
« on: July 09, 2014, 06:19:14 PM »
@mk11174: Man, that's service! Thanks very much for the upload. Have downloaded and will check to confirm Rewind's results for the 550D. But I have to admit I had forgotten that the SD bottleneck was only half as bad on the 650D as on the 550D, so I now realize we won't get a really great frame count for higher resolutions without some other amazing developer insight! Cheers...

General Development / Re: SRM job memory buffers
« on: July 09, 2014, 11:51:45 AM »
@mk11174: These results on the 650D from Rewind are very encouraging. If the recording times on the 550D for near-HD (like 1600x672, etc.) start getting up in the 10-20 seconds range, that changes things a lot. I'm turning to you because you were the driving force last year behind getting raw up and running on the 550D.

Am I correct in viewing the current situation as regards the increased SRM?:
1. Various contributors are busy finding stubs and compiling ML and associated modules for particular cameras
2. These compiled ML versions and modules are being tested by these contributors and they are reporting their results
3. Right now, if you want to try out and/or test these cutting-edge versions, you have to compile them yourself

Have you been able to work on the 550D in this context? Do you have an ML version/modules you could share for testing purposes?  Thanks very much in advance and Cheers!

Shoot Preparation / Re: Cook Picture Styles
« on: April 09, 2014, 08:56:46 PM »
oh look, it's our old buddy apefos! Cheers!

@baldand: Windows 7, 64-bit. All .raw files and .mlv files I throw at 1.1.4 seem to play perfectly. Laptop with ATI/AMD Mobility Radeon HD4570. What could be causing @SoulChildPaul's problem with a black screen? Anything I could help test? Cheers and thanks so much for your really fantastic software.

Raw Video / Re: Greater than 30fps in crop mode?
« on: April 06, 2014, 02:17:10 PM »
@rainless: This is my understanding of what is known in ML and this forum as "crop mode".

1. Raw video is not created by ML. It is simply captured directly from the already-existing data stream which the camera sends to the LV display in Video mode.

2. Therefore, when you are in, let's call it "normal" mode (you haven't hit the Zoom button yet), you can get, as a maximum, the native video resolution of the LV display. This resolution has increased since the older cameras, so that the 50D, for example, can do "only" 1584x1058 whereas the 5D Mark III can do 1920x1080.

3. This represents the entire image sensor dimensions mapped onto the size of the LV display. For example, the entire 5760x3240 of the 5D Mark III sensor is mapped [via a black-box process we don't completely understand] to the dimensions of the LV display in Video mode (1920x1080 for this camera, less for other cameras.) This mapping is done in the camera, and ML has no control over how it is done. It simply uses the result.

4. BUT, once you press the "Zoom" button, it's another story. Now you go into "crop mode". By zooming into the image we see on the LV display in "normal" Video mode, we see objects larger than we did before. Exactly how much larger varies by camera. But what happens when you're running ML is that now the data stream sent to the LV display  can in effect be larger (or smaller) than the native video resolution of the LV display. That's why, in "crop mode", you can record, for example 2000x1080 on the 50D and 3584x1320 on the 5D Mark III. The difference is that now this rectangle you are recording is a 1-to-1 pixel mapping of only a portion of the image sensor, that is, a smaller rectangle which represents only part of the entire image sensor rectangle. The highest resolution you can record in "crop mode" depends on the camera model you have and is probably a hardware limitation in most cases.

5. The display, on the other hand, which you see when you are in "crop mode" is selectable. It is also ONLY a display, it is not what you are recording. Basically you have the choice between ML grayscale, which shows an accurate representation of the boundaries of the rectangle you are recording, but a low-frame-rate and low-pixel-count picture, and Canon internal, which displays in the correct frame rate and in color, but as far as I understand, with no guarantee that you are seeing the correct boundaries of what you are recording. You just have to pick which is more helpful to you while shooting, remembering that it's only the display and doesn't change what you are recording.

I hope others will chime in with corrections and/or additions, and that this helps a bit. Cheers.

Girls, girls, you're both pretty. Why don't the two of you just grow up and shut up if you can't be polite in a public forum. Just PM each other and get it over with.

My two cents. Cheers!

@Jared: Download exiftool and exiftool GUI (google them). Change tag "BlackLevel" to a value of 2046. Problem fixed.

We've seen this before, for various reasons. It seems to be only a metadata problem: i.e., your .dng's are actually ok, if you just change this one value. I tried it on the .dng you uploaded and it now looks normal. Cheers

@chris_overseas: Trying to confirm this at the moment, but I think the "floating MLV arrow" is a demo watermark that will stay there until you actually purchase the plug-in. So unless one is willing to pay $495 (the current price for the Adobe version of the Drastic MediaReactor Workstation), this amazing workflow will remain out of reach for now. In the words of the immortal Walter Brennan from "The Real McCoy's": Dagnabbit!! Cheers.

Raw Video / Re: Read Meta data of RAW file
« on: January 29, 2014, 10:57:25 AM »
@schlemiel29: If you run raw2dng.exe to extract the .dng's from your .raw file, it shows this information in the command box as it opens up each RAW file and you can write it down (of course, if you've already extracted the .dng's, you can delete the ones you are now creating). Also, the tool RAWanizer.exe (google it) shows the fps of each raw file it finds. Cheers!

General Help Q&A / Re: 5d3 60P with MLV
« on: January 27, 2014, 10:55:10 PM »
@5D3shooter: I may be mistaken as I do not own a 5dIII myself, but my understanding of ML raw in general is that it derives from whatever is presented to LiveView, and apparently when shooting 50p/60p, the data presented to LiveView is anamorphic, with a ratio of between 1.4 and 1.6 or so, depending on the camera model. ML takes this into account, which is why it will only let you select the anamorphic 1280x448 ratio when the Canon menu is set to shoot 50p/60p. I don't think you could have shot 1280x720 in an older build, at least not at a 16x9 ratio. By the way, this is why the aliasing is apparently worse in 50p/60p mode, because whatever process Canon uses to lower the resolution from stills resolution to video (whether it's line-skipping, as in the older models, or pixel-binning, as in the 5d3), the process is exaggerated for the anamorphic mode. Not sure whether this applies to the 5d3, because aliasing in 24/25/30p mode seems to be almost non-existent for that camera, but for the other cams, it's worse. If anyone else knows different, please chime in!

Short answer: you're not doing anything wrong, but right now you can't shoot 50/60p non-anamorphically. Cheers!

Raw Video / Re: Slow Motion on Canon Mark 3 Raw
« on: January 26, 2014, 09:28:49 PM »
Arggghh, sorry guys. Forgot about the 1.6x factor in 720p (i.e. 60p) mode. Be that as it may, (1920x508x14bits/pixel)/8 bits/byte means 102,412,800 B/s, or 97.66MB/s. This is probably right around the limit for your card. Because the card isn't quite fast enough to keep up with the data rate (or not even really close, I don't know what your benchmark is), the buffer fills up very quickly and you start dropping frames after only 5 seconds. If you have it set to stop on dropped frames, then that's what happens: it stops.

To test, drop down to a lower total resolution (start much lower) and see if that works, then work your way back up. Where you have a problem, that's probably the limit of your card. But even if you can't shoot 1920x508, a 5dMkIII with practically no aliasing should allow you to shoot at 1728x456 or whatever the next lower resolution at 2.35 (in 60p) is. If you blow it up now to 1920, it should still look pretty damned good. Although there is apparently MORE aliasing (because of the additional 1.6 stretch) when shooting 60p. You're probably going to have to do some thorough testing.


Raw Video / Re: Slow Motion on Canon Mark 3 Raw
« on: January 26, 2014, 08:06:59 PM »
1920x508? I'm shooting with the 2:35 aspect ratio.

I don't quite get this. 1920x508 is a ratio of 3.77, not 2.35. Can you check your post and correct or explain this? Is "1920x508" a typo or is the typo "2.35"? I started to answer your post with some calculations, but this jumped out at me and needs a response before I continue. Cheers!

Tragic Lantern / Re: 50D Raw video
« on: January 18, 2014, 11:58:12 PM »
@brandonmarsh: Check your AE project. I'm pretty sure you will find that AE has interpreted your DNG sequence as being at 30fps, which is the default value for image sequences for a new install of AE, if you never change the default. If you select the sequence in the Project panel, you will probably see that it shows as 30fps. Since these sequences are just a series of individual frames, and not a video, you actually have to tell AE what frame rate it should be. As I said, if you don't change the default, AE assumes that all imported image sequences are 30fps. To change the interpretation, right click on the clip in the Project panel>Interpret Footage>Main, and change the frame rate to what you shot it at, which is 24fps.

You can also change the default by going to Edit>Preferences>Import and changing the value for 'Sequence Footage' to whatever you want it to be: if you are always shooting 24fps, then make it 24fps. No matter what the default is set at, you can always change the interpretation of an individual clip with the procedure I describe above. Hope this helps.


Pages: [1] 2 3 4