Malcolm Matusky
Forum Replies Created
-
I have been shooting with a Canon 7D since it came out, I make industrial films (corporate video) and thought I would just rent a 2/3 camera with a powered zoom when I needed it, I have not needed it. I started making films with a Bolex, a real one, not the “Digital Bolex” of rumor on the web. I am also thinking of what’s next? Stick with DSLR’s or move to something else? I have looked at everthing on the market, and soon to be on the market and have decided to wait, and continue with the 7D for now.
Perhaps not the solution you were looking for, but all the “large sensor” video cameras have some operational defect that has not made me jump yet. The BM camera looked good, but…small sensor, big mount, dumb idea. I have to have wide angle lenses for interiors. Most offices are small and I have to be able to get two people in a shot from a few feet away. I have an 11~16 and it works great on the APS-C sensor of the 7D.
Thought about the 5DIII, shallower depth of field is not an advantage for me. Full frame is out for now.
The M 4/3 is good, still much larger than S16 / 2/3 video, but the wide lens options are not great. I prefer working with zooms and Canon has fast (f2.8) wide lenses, constant aperture and stabilized! None of the M4/3 lenses have these specs.
Af100 No EF mount option with control, not viable. The GH2 with the hack is arguably a better camera, except for some of the “video” touches, on camera sound, etc, which are useful. A “hackable” AF100 would be very good, if Metabones made a working adapter for EF lenses, it would be amazing! HD-SDI out for a recorder, good, HDMI for monitoring, good. 8 bit, oh well.. Can it be hacked?
FS100 with adapter there is aperture control, possibly IS but no focus control! UGH! I have an OKI II, works great! Nice looking sensor, only one hdmi? stupid, need one for monitoring (better SD-HDI for signal out, and an HDMI for an EVF. On camera sound, useful, waveforms useful. This is the closest to meeting my needs so far, yet is it worth 3x the $$ of my 7D, no not really.
FS700, really not worth it for me.
Black Magic Camera, Weird looking, so what, so is a DSLR compared to a video camera. Great tech specs, LANC control of EF lenses, GOOD! Smaller sensor than M4/3!!! UGH. No adaptable lens mount to M4/3 lenses, EF or F only. Very dumb. A M4/3 or E mount would have enabled a wider lens choice made for the smaller sensor, which is actually smaller than the M4/3 standard. Canon does have an 8~15, but…how am I going to use ND filters on a lens that projects so far from the filter threads? I’m not. Not viable for my work. I wanted this to be the “answer” it’s not, perhaps version 2.0 will be.
Digital Bolex: S16 sided sensor, so am I back to the bolex rex 5 for shooing after 30 years? Possibly. Good specs, but like the BMC, till I see some footage, I’ll wait. No stabilized lenses, I like them, but not a complete disaster. I would prefer a larger sensor, but if this camera is a functional tool and not a poorly thought out toy, it’s viable.
Raw workflow is not a “killer app” for me, it would be a nice option, but not the prime reason to buy a camera for me. I shoot for the “little” screen and those shooting for festivals or theatrical release will have different needs.
Very interesting things on the horizon, but for now, nothing to make me change just yet! Soon though, soon…
M
Malcolm
http://www.malcolmproductions.com -
set your project to 8 bit, made a big difference for me.
M
Malcolm
http://www.malcolmproductions.com -
I have this book and CD, I just change the wording from “photograhper” to producer and add anything else that I need to specify in a contract.
Cheers,
Malcolm
Malcolm
http://www.malcolmproductions.com -
I had the same issue last week, set project properties to 8 bit color depth on render file and on any nested veg files. I was able to successfully render a project after having trouble for three days!
Good luck,
Malcolm
Malcolm
http://www.malcolmproductions.com -
Well, I finally figured out the source of my persistent render crashing. 32 bit floating point. I have been using this setting with VP11 and never had issued with it, but last week (something) happened and by adjusting my project settings to 8 bit, and the nested veg files as well, I was finally able to render out my project today without issue.
My thanks to Cineform’s Jake Seagraves for working with me on this issue, obviously not their fault, but he was willing to take the time to diagnose the problem.
Now I am wondering why did this start to occur as of last week? An update? Microsoft?, nivdia? I made 2 versions of my timeline, one using the cineform files and the other using my cameras h.264 files; both were crashing, and now they both work. So it’s something within VP11, and I just updated to build 683 “just in case” they fixed something.
I’ll have to do more tests with the project settings to see if I can use 32 bit for anything, from what I have read on the subject this seems like the preferred setting, but obviously not for my system!
I’m running an Intel i7 930 @2.8GHz Asus motherboard, 12 Gig ram Win 7 64bit Nvidia GTS 250 1Gig card with latest drivers. ESATA raid & separate render to drive.
If anyone has thoughts on the 8bit vs 32bit FP issue, I would like to hear about it.
Regards,
Malcolm
Malcolm
http://www.malcolmproductions.com -
I’m working with Jake Seagraves of Cineform right now, he did a remote access on my computer to see what was going on and I’ll update this post when everthing is straightened out, or not. If I cannot get VP11 to render I’ll take you up on your offer, thanks’ Steve.
Regards,
Malcolm
Malcolm
http://www.malcolmproductions.com -
Has anyone used Sony’s tech support; $30 for one tech call?
I once had “support” from Dell, all they could recommend was to reinstall my operating system and all my software, that advice I don’t’ need to pay for!
M
Malcolm
http://www.malcolmproductions.com -
Just deleted and reinstalled VP11, still crashing!
Now I don’t’ know what else to do.
Malcolm
Malcolm
http://www.malcolmproductions.com -
I’ll try this again, I think I reinstalled vegas before removing the codec pack.
I thought this was a cineform issue, I have been transcoding my clips, but I spend a day+ relinking all my clips back to the H.264 camera originals and regraded the project. Trying to render this morning was still frustrating. Crash, crash, crash!
I tried using 0,1,10 for the preview ram box, crashed with all settings.
I set my project preferences to exactly match my render parameters, still crashing.
This is a disaster for me, project was due on Monday, UGH! computers!!!
Malcolm
http://www.malcolmproductions.com -
Yes, I was dumb, installed the codec pac and the “player” which changed all my clip ikons, strange. I uninstalled the player and codec pac and things are still weird.
I was able to render an old video I cut months ago, I will now try and swap clips on my timeline to see if any of my media is corrupted. VP seems to crash on the first clip, just after titles, and i’m using the legacy titler, found another post where the new one has issues.
Fortunately the client is understanding, and I can deliver later this week, having only one edit system is not a resilient way to work! That’s why I’m thinking a cloned C drive sitting on the shelf may be a good strategy, in lieu of another workstation.
Cheers,
Malcolm
Malcolm
http://www.malcolmproductions.com