Aaron Star
Forum Replies Created
-
Why are you rendering to 23.4? That is no standard I know of, were you under cranking so other standard?
-
I would check your windows logs for what issued the reboot, or research your X99 MB for similar issues.
things to check:
- Verify RAM is error free with Memtest86+ outside of windows.
- Verify that temps are good for the MB and CPU.
- Check for hardware errors in the Windows System logs.
- Verify all Windows Updates have been applied.
- Verify you are running the latest Firmware for your x99.
-
if you uploaded or shared an .r3d frame and the resulting .dpx frame, people might be able to help you more.
More information on your workflow from camera to final display format would help people help you.
You need to have your vegas project settings correct for the media you dropping on the timeline. Pixel format, compositing gamma, and view transforms is what I am referring to here.
Using Sony “levels” at the media lvl, track lvl, preview or effect level is probably what you are looking for. Set the gamma, and your input and output to get your footage in spec. But you need to understand the project settings in Vegas and level changes you are making through out the workflow.
I would try Epic footage -> RedCineX -> .dpx -> vegas for edit.
or
Epic footage -> RedCineX -> Cineform.avi -> Vegas for edit
or
Epic footage -> RedCineX -> .exr -> Vegas for edit w/proxy for smooth playback. Working in EXR will retain your color depth information from the epic. 10-bit dpx will clip that information.
If your final display output is DPC, that format is 12-bit JPEG2000 capable. So retaining better than 12-bit information will optimize this conversion. But ultimately you need to conform your camera footage to the edit intermediates required, or your final display format.
Mainly I would think your CC would be done in RedCineX, Resolve, or Vegas with the proper display hardware to grade the footage correctly. If you going to work with a CC house that uses one of the Unber pro CC systems, then work with them on the format you need to deliver to them.
-
I would start at the bottom and work your way up.
1 – get a copy of Memtest86+ V4+ run atleast one full pass on the memory to eliminate any memory hardware issues.
2 – try the following I have posted before:
You may also want to run the following on your machine and verify a few things, generally in this order:
“chkdsk /f” from a command prompt, choose yes on next reboot. Reboot
Apply all windows updates, including any .NET updates.
Make sure GPU driver is latest.
Uninstall any old applications or utilities no longer used.
Remove any AV software that is not MS Defender or Malwarebytes. Reboot.
Run CCleaner Registry cleaner and repair issues. Reboot.
Run a Windows defender scan, and Malware Bytes scan, and repair issues found, reboot if issues found and re-run scans.
“dism /Online /Cleanup-Image /RestoreHealth” from an admin command line. You should get:
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.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.Make sure Vegas 13 is running the latest version (build 453), reboot if upgrade is needed.
Verify Hardware temps are ok during playback and rendering with something like Speccy or another program like it. Repair clogged heat fins or cooling issues if high temps are present.
After doing all that, if the system still hangs, try MS “Process Monitor” and isolate the problem that Vegas is stopping at. More often than not, this is some memory issue, harddisk issue, network resource not found, or registry entry that is no longer present or over written.
Just some things to try.
-
I would try John’s suggestions for easy of use and editing in Vegas 1st.
Here are some other things I noticed:
1 – FFMPEG – What other file formats are available? With FFMPEG you maybe able to set the encoder to produce .MP4 and even intra frame mp4.
The encoder company may have already determined what formats work the best with their hardware.2 – AVI – What other codec options are available for .AVI? If Cineform is available, this might produce good editable content for Vegas.
3 – .MP4 – Hardware encoding to .MP4 might produce the least overhead to your gaming machine, leaving more resources to the game. Adjusting the bit to 22-30+mbs, then run a short capture test, investigate the file properties with ‘MediaInfo.” The file should be Constant frame rate, not variable. Some capture devices do not produce compliant video formats. For 60P work the bitrate would be double the 30P rate. In the end the trade off of system load vs editing abilities in Vegas, will have to be tested by yourself.
4 – Transcode – You can always transcode the capture media in Vegas to an editing codec like Cineform, HD-CAM, XDCAM-ex, or XAVC-Intra which will add time to your editing. During the transcode process, you can re-encode only the parts you intend to post or “selects” to be edited inti the timeline. Thus reducing the amount of transcode time. Working the above codecs will be the most stable for compositing, effects, or overlay type transistions. Also Vegas GPU assist works the best with the above codecs.
-
Yes. You are correct.
-
With windows drive lettering is pretty closely tied to the port its plugged into. If you move portable media around to different USB ports, then windows assumes its a different drive.
With CD or external HDD media that you really do not want have the drive letter changed, set the drive to x,y,z. I move all DVD drives to Z 1st thing on a new configuration. Hard disks will always be seen 1st and given asending lettering. If you leave portable drives in while rebooting, these are treated like Hard disks on the system and lettered accordingly. Place electrical tape over USB ports you do not need is a good way of making sure you use the same USB port every time for portable media. This should curb your bouncing drive letters.
If you go into your device manager, and choose show hidden devices, you will see under HHD all the instances of drives that are not active on the system. removing the inactive drives will reset your drive lettering for portables. Then the next time a device is inserted it will build a new profile for it with letter.
-
Another thing to keep in mind when configuring a system that supports Dual or Quad channel ram, is that memory slot population can matter. On some motherboards, if all slots are populated, then chances are you will not be operating in quad channel. Only 2 sticks of identical memory per channel. Once you go to full population on the memory slots, the memory controller will drop to single channel speeds.
Dual and quad channel is also where the matched speed timings come into play. One DIMM out of timing and the controller will generally drop to single channel mode.
-
“Winsat mem” on an admin command line will show your memory bandwidth as Windows sees it. You can do your trials, and in the case of quad channel memory, more bandwidth is better for Vegas.
-
Use integrated Windows Defender, and then run Malware-bytes about once a month. If you stay off dirt bag site you should not have a problem. Windows Defender has really low overhead compared to other AV software.