Forum Replies Created

Page 65 of 76
  • David Eaks

    December 25, 2011 at 4:29 pm in reply to: lost work???

    Did you ever save the project?

  • David Eaks

    December 19, 2011 at 9:27 pm in reply to: New user needs advice on mixer/recorder

    [Ty Ford] “Without knowing how you were using it, I can’t respond to the noise issue. Usually hiss in a Mackie is a op error impedance mis-match or gain staging problem.”

    Testing each board with two Neumann KM 84’s, listening with Sony MDR 7506 headphones. Switching out the mixer from FX8 to 1402 VLZ Pro and back again to compare the sound of each board in the same setup.

  • David Eaks

    December 19, 2011 at 10:08 am in reply to: New user needs advice on mixer/recorder

    Also to mention that I agree with Peter about the mics. I have Sony ECM 55 and have not used ECM 77’s, but his over-all concept in choice of mic is “sound”.

  • David Eaks

    December 19, 2011 at 9:52 am in reply to: New user needs advice on mixer/recorder

    FWIW a while ago I bought a Mackie VFX 8 after years of using 1402 VLZ Pros, and was quite disappointed. Inputs were not clean and silent but “hissy” by comparison with VLZ Pro. I am VERY happy with my new 1402 VLZ3 though. Very clean, wide gain range and tons of headroom.

  • David Eaks

    December 9, 2011 at 10:07 pm in reply to: The World’s Most Basic FCP Question

    I do know what your saying, you feel like WTF changed?! It’s simple things like moving the playhead and maybe others like changing the active window, collapsing a bin or even if autosave, saves, FCP will want to do a save. Even though it’s not a “change” in the edit. Haven’t really tested for everything that does/doesn’t trigger the need to save though.

    I have a habit of: Open a project, move the playhead, hit command-s, begin working. I do this because long ago I misinterpreted something I read, that auto-save isn’t triggered until the project has been is saved. That is definitely true for a new unsaved project but I’m pretty sure auto-save kicks in as soon as you open a project already in the works, but the habit lingers.

    [Miriam Lefkowitz] “FCP also asks if you want to save your project after saving your project and immediately exiting the program. I always figured it was just being extra careful.”

    Not if you hit the shortcuts, command-s (or option-command-s for multiple open projects) then immediately command-q. At least in my experience, thats how I quit FCP: cmd-s, -q. If you move the playhead after saving, FCP wants to save that “change”.

  • David Eaks

    December 7, 2011 at 1:10 pm in reply to: Opening an Old FCP Project on a new system

    Since the edit is very basic with only a few transitions/fades, couldn’t you just use the original media and rebuild the edit in the NLE of your choice? Do you think FCP X would fit your needs (putting aside the inability to open FCP Legacy projects)? Of course FCP 7 is great… It’s just dead.

    Trying too hard and spending too much money just to open one simple edit in an EOL’d App seems like it’s going to be more difficult both mentally and financially than just rebuilding the edit. Is working with the original edit THAT important?

    Maybe the edit is more complex and harder to rebuild than I think.

    Just my $0.02

  • [Rachel Kodner] “How can I convince my company not to buy 7D cameras?”

    Print this thread, highlight all of the comments that state exactly why DSLR’s are not right for your type of work and show it to the people in need of convincing.

    The inability to record an entire live show/event in one clip should be enough of a reason all on it’s own. Having to deal with 12 min clips (with a short gap of missing footage between each clip) from 3 cameras on a ~2 hour shoot is just plain ridiculous.

    It’s not the right solution for your company.

  • David Eaks

    December 6, 2011 at 1:25 pm in reply to: FCPX UI goes ‘screwy’

    Yeah that is strange. As for the HDD space issue, do you have 100’s of Gig’s worth of unneeded render files that you could delete?(Select project or event, File> delete project/event render files)

  • David Eaks

    December 6, 2011 at 1:08 pm in reply to: Image quality of NX5U and similar HD cameras

    I own 2 NX5U’s and Neat Video. I feel your pain regarding the grain! I’ve felt much the way you did about the picture quality and this thread did ease my mind a bit. No complaints from customers though, shooting recitals, meetings and the like it’s all Ohhh’s and Ahhh’s because they are so impressed with HD. They don’t even see the noise.

    But I must say that Neat Video is Awesome! You can make huge, vast improvements to noisy low light clips and it’s got decent sharpening as well. Just don’t over do it and be prepared for the long render times!

    Also, it is very helpful to keep in mind that Neat Video needs to build a noise profile based off of an area with no detail, like a flat black background. It can be tough to get a good profile if you don’t have a good section of the frame to work with. So be sure to shoot with that in mind if you plan to use Neat.

    Does anyone have picture profile settings that they use specifically for low light situations, that they would like to share?

  • David Eaks

    November 30, 2011 at 9:04 pm in reply to: Buffer Overload on new camera

    I think Michael covered the issue you had with recording pretty well. It is in the manual. I’ve had two NX5’s for some time now, recorded many hours on both class 6 & 10 SD cards without a hitch.

    As to the focus being soft, these cameras do have a back focus problem. As you said, you zoomed in, focused and zoomed out. That’s the problem, it doesn’t hold your focus. You have to focus “where you are”, the peaking feature helps.

    Sad to hear you returned the camera.

Page 65 of 76

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy