Aaron Star
Forum Replies Created
-
I am not sure there is much you can do with the D5000. The D5100 does 1080-30p, and with a NikonHacker firmware upgrade, you can get manual ISO and increased bitrates. The D5000 does not appear to have a hacked firmware that can be applied, so you are stuck with the video modes on the stock firmware. If you have to use the camera select very well lit area to shoot in. Nikon of that generation used auto everything in video mode, and would ramp the ISO before altering the shutter or stop. There is likely a menu setting for locking the exposure before you roll, so it is not changing during the shot.
The fact it shoots in MJPEG is not necessarily bad, since it is a intra frame codec vs AVCHD.
Audio sucks and so you better have an zoom or something running for audio.
I would say have them ebay the d5000, and get a ebay d5100 or better, if they have lens they want to keep.
-
I understand your situation better.
If you want to try the hackentosh route that could work, I always wanted to try that myself.
However, since your editor will work in Premier, shooting ProRes and editing in Premier might be easier to do, and the pc hardware better in the end. This due to the limits of what MAC OS supports. Building an X99-Core i7-5960X, 32-64GB DDR4, 1000w PSU, R9-390x or Fury X would have much more crunch power than a Mac Pro. The Fury X with HBM is like 8000 GFLOPS of Single point processing, vs the 2000 GFLOPS of the Mac Pro. Install all that in a case with a couple 5 1/4 bays, then works some Icydock ToughArmor MB998SP-B, and you could use the Raid integrated on the X99 with 1TB SSD. 339GB/h times 10 is only 4TB, so one Icydock would give 8TB, plus the internal slots. The X99 has enough PCI lanes to support internal cards beyond the chipset ports. Add an internal Raid card, and another MB998SP-B and would have a pretty small unit with a bunch of power and killer amounts of storage. Keeping your storage directly connected to the PCIe bus will be faster and more responsive than traversing the Thunderbolt bus. Of course this route would be Win7 or 10.
-
Do your own plans from the video you like, and make the drawing in Google Drawing or Visio. Several sites and videos will include parts lists.
-
Embedded CC requires broadcast codecs like HDCAM, XDCAM, WMV, and I think MPEG2. Normally CC is a ride along text file.
Using YouTubes CC editor is maybe the best. Google will auto recognize, then you just go in and correct the CC found. The CC file can then be downloaded and included with your export file.
-
Ebay the Titan and get a 390x. Vegas needs a card that supports OpenCL better than NVidia anything. The 390x will significantly accelerate your Timeline, and small aspects of rendering. You still need to render the timeline during render, so you do get GPU assist during renders.
Uninstall the Nvidia drivers back to Windows default, reboot, then shutdown again, before pulling the GPU. Install the AMD as normal, card then drivers.
-
Your DP wants to shoot on his DSLR to a device that records in ProRes.
Your Editor works in FCP X.
That’s sounds pretty much like a what ever Apple has on the shelf you can afford type of problem. Why do you need to build a PC? My guess the issues with FCP X stem from people that do not like the change or do not have enough MAC to work the footage. If you cannot afford a trash can and array to edit the media directly, Proxy edit and then you are working with footage that any MAC that can run FCP can edit. Ask the MAC store to demo you a system that can do what you need with samples you bring in.
800Mbs is not that much bandwidth these days. A multi disk array or SSD can deliver 400-500MBs. I would recommend nothing less than Raid 1 on your media, and then also have backup copies of your camera media.
If you plan on projecting DCP, consider renting something RAW, like an ARRI, RED, F55, or Blackmagic. Then edit in ACES. The DCP will have much better color, and you can always go down to BD.
Also the LPs I know would not let their DPs bring their own gear, lights, and in some cases crew. Mainly because if the DP becomes an issue, only he leaves the set and not his toys. If the DP is renting the production gear, make sure the employment and rental contracts are separate.
-
You could just grade it yourself, and then you would have a filter preset to apply to other footage.
I see pretty much a clean film exposure with daylight film, a Kodak 35mm grain overlay at 24p, dirt layer, Vignette layer, and then playing with the CC until your look matches. Using a still frame from the movie that matches your rough camera angle, then use split screen to show both. CC until the left matches the right.
There are various sites that you can download 35mm grain to composite overlay on your footage. Do not use the Sony plug in. YouTube has videos on how to do this.
The Sony Soft Contrast filter in combination with others above will get you close.
less effect is more.
-
Vegas has no recommended RAM settings, so I am not sure what menu you are referring to.
For future projects, I would highly recommend this process:
Record game footage > Convert game capture files in Vegas to Sony MXF HD XDCAM-EX 1280×720-60p > Edit the XDCAM files in a new project file > Export timeline to either the same XDCAM profile, or Sony AVC Internet 720-60p profile. YouTube will accept XDCAM files directly, no need to convert to mp4.
The game capture recorder might not be creating compliant video files, due to them trying to keep costs down. Using an intermediate format can help you have a more stable experience.
-
-
Can you upload that sample, or a short 5 sec clip with the error to dropbox?
What is the “media info” – https://mediaarea.net/en/MediaInfo on the source video.
What OS and system specs do you have.
Have you disabled the GPU under Options > Preferences > Video > GPU acceleration? Then restart Vegas and test.
Are your GPU and sound drivers fully updated from the manufacturer?
Are all the windows updates applied and your system restarted after any installs?
To me that looks like corrupt video file, an odd codec that vegas is not decoding correctly, or GPU software fail.