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

#1
Hi Lasting Image,

Thanks for the comments!  I think the stuttering you speak of can happen in a lot of different places in the equation.  I was having the same problem watching videos, even mine, through Vimeo and Youtube even though they were fine when watching them in the NLE or in Quicktime.  It turned out the browser I was using, Firefox, was causing the problem.  I've switched to Chrome and sometimes use Safari and they work fine.  As far as framerates go, I don't think it should matter on playback on a computer.  I'm not expert in this, but unless you specify a different framerate in your timeline from what you shot with, there shouldn't be the stuttering.  Again, you're probably asking the wrong person for troubleshooting.  From my experience, though, try using a different browser and see if that makes a difference.  Cheers!
#2
Thanks for the nice comments Canon Eos M!

Nikki, the workflow was pretty simple.  It's been a few years since I've used a 5d with ML, so pardon me if these features have changed.  I used the crop feature in ML, which is nice because it blacks out the rest of the image.  I like that better than actually seeing a grayed out area below and above the crop marks.  What you see is what you get.  That is, until you go to edit it.  ML isn't actually cropping the image, so you get the full 16:9 in your editor.  And that's nice, because occasionally you need to slide the image up or down a bit in post and you have the freedom to do that.  But, depending on what NLE you use, there's a cropping function that allows you to get the same crop you had in camera.  And that's all we did differently for this project.
#3
I love the cropmarks function on ML.  I shed a tear, though, as I crop away more than 200 lines of image when processing the 2.35:1 image.  Since these DSLRs have plenty of pixels in their sensors, could there be a way to make a 2538x1080 movie that wouldn't require a widescreen crop and wouldn't be wasting pixels?  It seems, to my simple non-tech savvy mind, that if bitrates of 90MB/s or higher are possible with a 1920x1080 sized image, that it could be possible to do a larger image.
#4
I think the biggest problem is not being able to play it back for others around, like the director, and having to explain, "don't worry, the movie is fine, we just can't watch it here.... I'm sure it's fine."  And then breathing a sigh of relief when you see it in post.

To be honest, I didn't really see much difference.  But I didn't do any serious grading.  For me, I might save higher bitrates for things I know will be jacked with in post, or for green screen stuff.
#5
I'm new to using ML and I am running ML unified on a 5DmkII.  I was more interested in some of the other features, like cropmarks and focus peaking, but finally wanted to play with higher bitrates.  I tried 1.4x bitrate, after looking at the wiki table for what my cards should be able to handle.  I am using the Sandisk Extreme UDMA 60MB/s 16GB cards.  The video recorded fine, never going above one white square in the buffer.  However, in playback, it would only play for a few seconds and stop.  I could press play again and it would do a few more seconds.  When I dumped the card onto my computer, it played back fine.  But, I can't see doing a shoot like that, not being able to immediately watch the video back.  Is anyone else experiencing this?  Is this normal?  Thanks!
#6
I shot this using ML Unified on the 5D2.  I used the Focus Peaking feature as well as the cinemascope cropmarks.  Other than a couple user errors, ML worked really well and was pretty stable.  Though, one of my CF cards(sandisk extreme 60MB/s UDMA 16GB) wouldn't load ML.  I put the firmware on there like the other cards, which all worked fine.