Aaron Star
Forum Replies Created
-
Post screenshots of the “MediaInfo” (freeware app) on your source files, your Vegas Version, Vegas Project settings, and the render template you are rendering to.
Also what application are you capturing with?
-
This is very close to my other post on the issue.
https://forums.creativecow.net/thread/280/13371
The Dx000 series Nikons are all pretty much the same sensor wise, only the video processors and resolution are different. The actual Dxxx series are the higher end full frame models. Getting “DX” lens are the matched lens for the DX cameras. The N series Nikon lens are much higher quality lens with more resolution. You can use a full frame lens on a DX camera with a crop factor. The older manual 35mm lens will work with DX cameras in manual mode and likely have better resolution. The DX sensor is basically 1:1 with motion picture frame size, where as the full frame sensor matches 35mm still. This is due to one 35mm format running vertically vs horizontally.
-
Some googleing found this:
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
I researched some time ago, and reached the conclusion that getting a better pro camera that supports recording to MXF (which supports timecode) is better than audio track time code.
I believe AVID has functions to read linear audio track TC. Maybe download a trail copy.
If you can get the 1st frame of TC, then convert the footage to .mxf format so you can set the TC data, will allow pretty much any NLE or DAW to see the TC.
-
The “PhotoIO Cineflat”, “TassinFlat”, and Flaat_12P are probably what you are looking for.
Select the profile, download it, and copy it to the root of your card. Then use the Nikon menu to load a custom profile, choose it your shooting mode.
You can see if https://nikonhacker.com/ has a firmware for your camera, which can give you higher bitrate recording at the cost of less record time.
I find my D5100s seem to be native at about 200ISO, 100 looks to overly contrasted, and 400-640 starts to grain up.
Using a non-kit lens (lens that came with the camera) can give you much more resolution and often time faster stops. A set of 18, 24, 28, 35, 50, 85, 135 F2 primes is what I use. The older manual Nikon lens are sharp and great, much better than the auto focus DX series lens. With manual lens in Manual mode, keep your shutter speed the same as the frame rate, or double. Do not go higher as you will get more strobing on moving objects. Pan slower than you think to avoid the pronounced rolling shutter and AVC motion artifacts.
I still tend to use lens filters like pola and ND grads to help with increasing the stop range.
I also still use an incident meter, because you cannot trust the onboard monitor in certain lighting conditions. You can get histograms by hitting the down arrow in picture review mode. Taking a snap shot, and then checking the histograms is a good way to verify your not over. Make sure your whites on the histogram are peaking above 235, if 255 is the far right side. AVC codec captures best keeping image details/info you want to see within 16 to 235 or sRGB levels.
-
Is there a specific reason you are editing lossless, vs using xavc-intra, hdcam, or cineform? Those codecs will yield just as good as results with less problems. Even dnxhd would be a better choice than legality in terms of editing.
If you are concerned about generational loss, then you may need to re-think your workflow. Capture, edit, output workflows are generally designed to take into account image loss by the end, and still maintain image quality. Unless you are doing animation and heavy compositing, then image sequences like exr would be the best uncompressed format.
-
What is the size of the new file after combining the files?
Were you able to determine the number of files on the timeline that vegas stopped working?
-
That seems to be an issue with the AMD OpenCL library.
I would check for virus/malware with “malware bytes”, use the free version as you only need to run it when you are having issues.
Check your disks for errors, failing drives can create corruption: chkdsk c: /offlinescanandfix from an Admin Command Prompt (right click Start button)
Check your memory for errors, there should be zero errors – google Memtest86+
Apply all windows updates, including any .NET updates.
Uninstall any old applications or utilities no longer used.
Run CCleaner Registry cleaner and repair issues. Reboot.
sfc /scannow from an admin command prompt. Verify you get:
“Windows Resource Protection did not find any integrity violations.”
repair any issues here. Reboot and re-run if issues repaired until you get the message above. RebootLoad the latest Win7 GPU driver from AMD, correct the resolution issue, and then possibly reload VP-B453 update if all the other stuff checks out.
Without system specifics on your machine, its hard to recommend more specific drivers, or if the GPU is even compatible with OpenCL operation.
-
When you do conversions from Prores to another format, make sure your levels and gamma are the same on the scope.
-
As described in countless posts on levels, YouTube and most other video players will stretch levels from sRGB to cRGB. So if you place your blacks at 0 in photoshop, the YouTube player will stretch those levels darker then 0. If you place your blacks at 16, those levels will get stretched to 0. The same goes for the top end.
You can see you levels in the waveform monitor.
These issues have to do with Video not really being a computer standard application. Video was once its own system before computers, and computers do their best to represent it in cRGB. Its up to the operator to understand these issues.