Aaron Star
Forum Replies Created
-
Have you verified your black levels are actually black with the scopes?
Do you have an understanding of RGB vs sRGB in terms of black levels?
Is your black level on your monitor calibrated?
-
Aaron Star
January 30, 2017 at 11:01 pm in reply to: Vegas 14 render issues, problems, crash, Vegas 13 fineJust to be clear. What is your project settings, source media type, and render as profile you are using?
What are your system specs?
I am sure it work on VP13, just would like to know what type of settings and hardware you are having trouble with.
-
Testing would be the only thing I can think of.
See if there is a glitch in the media that goes black.
Do you get the same results if you disable all the effects?
Have you tried disabling all the effects, and re-enabling until you get the error?
Have you tried an alternate codec like cineform.avi, or Sony AVC vs Mainconcept to see if they turn black too?
Disabled GPU timeline accell, and turning off GPU accel in the render as template?
-
-
If you are looking to improve your disk sub-system, I would look into the differences between SATA, SAS, and NVME. With SAS and NVME your motherboard/CPU need to support the PCI bandwidth properly, and not gimp your GPU bandwidth.
SATA is a half duplex interface
SAS is a full duplex interface – it used to offer advantage of command queue, but now SATA also offers command queue
NVME is a massively parallel, deep queue, full duplex interface
https://electronicdesign.com/digital-ics/whats-difference-between-sata-and-nvme
I think the data center drives are a bit over kill unless you have needs for the extra support and warranties. I personally run Blue and Black drives mirrored in OS.
-
“Record mode setting is 1080/50p”
but
Project is 1080/50i, and render is 50i , which is 25FPS. This would create stuttering during high motion, as its a low frame rate. You want to make a 50P FPS rendered file.I would verify the record settings on the camera. Record in the top mode the camera supports which should be (1920 x 1080p / 50 fps (28 Mbps)). This will allow you to throw away bitrate in the render process, when you step it down to 8-20Mbs for playback.
Then open a new project window, and drag and drop camera media to the timeline. This should align your Project settings to the camera media. Vegas sets the project settings to the 1st file dropped on the timeline.
Then render as to a Sony AVC Internet template that “=” the project settings. The bit rate should be about 8-24Mbs, depending on how much the camera is recording and how much you want to squeeze it down. A SmartTV should playback AVC/h264 file from a flash drive in the side.
You can create an AVC template that matches your camera codec bit rate of 28Mbs, by modifying an Internet profile and saving it as a new profile. “Media Info” application can help with determine the codec details on your camera media. These file will be bigger, and some TVs or slow thumb drives may not keep up with higher bit rate. Testing is the only way around this.
-
Aaron Star
January 27, 2017 at 6:18 am in reply to: Vegas Pro After-Render Video Pixelation/Sharp Gradient ProblemWhat is your camera / timeline source footage format , codec, and bitrate?
What is your Render As settings when you render out to say AVC/.264?
What it looks like to me from the images posted is 8-bit banding due to a low bitrate.
-
Aaron Star
January 27, 2017 at 5:49 am in reply to: VP 12 suddenly crashing on launch – Unmanaged Exception (0xc0000005) related to compoundplug.dllWhat Media type are you using (Codec and file format (.MTS, .MOV, .MXF))
What project settings are you trying to open?
Do you have any special audio or video hardware, or are you using only system board audio hardware and a standard GPU?
I am not saying your issue is exactly the same as the one I experienced, but I would try the following.
- Make sure Vegas is up to the last build they offered for V12.
- Make sure all Windows updates are pushed, and the .NET updates.
- Make sure your Audio and GPU drivers are the latest.
- Try installing the Trial of VP14 and seeing if that works better.
- Verify system memory with Memtest86+, run through a complete test sequence. There should be no errors.
- If you are using special external audio hardware, try removing it and seeing if Vegas starts. Try this for other extra hardware you may have slotted in your motherboard. Then replace them one by one until you find the problem.
Working one day and then not the next is how things break. It makes me think that either an update change happened, or hardware failed in that time.
I had a bad audio card once that refused to work in vegas, but worked in Windows. I also had another instance where one bad memory DIMM was causing issue with Vegas crashing, but somehow Windows was working around it.
-
Aaron Star
January 23, 2017 at 2:40 pm in reply to: PLEASE HALP ME (deadline is soon and i really need to fix this)Why not upload that image using the CCow image upload. I do not download random files from cheesy file hosting services. Pretty sure most of the rest of the community will not either.
-
You have a hard time going back on things you do in camera. But on the flip side, in camera effects can save a huge amount of render time. Most FLAT settings in camera reduce sharpening and expect that to be done in Post.
I used to work with a DP shooting 35mm Audi commercials back in the early 90ies. His philosophy was to shoot low ISO stock, and pretty much shoot clean. Producing well balanced RGB layers in the film, but also well exposed, dense negative. Then make all artistic grading choices in telecine. I think that still pretty much applies to our digital workflows. The only flip being that with digital, we want to slightly under expose to save the highlights, or compress them with HDR.
With my Nikons, I leave the sharpness at default but flatten the picture settings. I always assume that the engineer selected that setting based on optimizing signal from the sensor through to the encoded file. That might be giving them to much credit. Running your own camera tests using your workflow, and shooting resolution charts/color charts is the only way to determine what works best for your rig.
Shooting AVC LGOP and then converting to an intermediate to edit will drop the sharpness a little. You can see this by using pan/crop and zooming in on some fine detail, then A/B between the 2 different formats. We are talking about c-hairs of difference here, and pretty much video engineer levels of difference. But that attention to detail is what separates consumer from pro level video signals.
Never buy a camera that shoots in a LGOP format, only buy cameras that shoot in an intraframe codec, or use an external recorder.
For drag and drop timeline performance in Vegas, use cameras that drop REDCODE, XAVC-intra, HDCAM, XDCAM, cineform, or Prores. That will keep your editing stable, and sharpness optimized for Render As outputs.