Aaron Star
Forum Replies Created
-
You may also try:
Nuke
Mocha
Blender
Youtube tuts for all of them.
-
Edit could be a rebrand attempt true. I would think they would continue both until Edit has a few versions, or greater market share.
-
Calm down John Rofrano. No one said he rendered Prores on the PC. He said he rendered XDCAM on the PC, then took that file to the Mac and was having issue.
Apple has its share of bugs just like every company on the planet. The only reason the distributor can tell the encoder is because the meta in the file header. FFMPEG is not going to allow that to be changed for legal reasons. Prores is not Apple magic, it just a codec that has apple labeling, and they protect it with a whole bunch of lawyers. I was only trying to say that the XDCAM format may not be that compatible with such low end software. Upgrading to Final Cut with the Sony file extensions may solve the problem.
I was not belittling your people.
-
Processor. No portable GPU will ever come close to desktop GPU compute performance, mainly due to power draw and heat reasons. Do not expect desktop i7 performance from that yoga, but you can edit reasonably well single screen on an i5 with 8GB of ram.
-
If you rendered to xdcam422, it is most likely a problem with the Apple software reading the file. XDCAM422 is a pro codec that has 8 discrete audio channels. Channels 1 and 2 are normally the stereo recording. Final Cut, with the Sony extensions would most likely understand the file format properly.
FFMPEG supports renders to Prores and HQ.
-
Sounds like maybe the water pump is not working (flowing) or there may be a gap/poor contact between the water block and CPU. In shipping things can come loose, make sure you have a good seat/contact with the CPU. the pump should make some noise as these things are not totally silent.
-
Do you get the same BSOD if you disable GPU rendering under options in Vegas?
Try a test project with footage rendered to XDCAM-EX and see if you crash then.
Blue Screen is usually hardware. Memory, device driver or a peripheral that the device driver is running, could be a bad motherboard. Verify you have the latest driver for the Chipset, SATA controller, GPU, Audio, and Network.
Next get a tool like Speccy or something that monitors temperature. During render or before the BSOD watch the temps on the GPU and CPU, make sure they are not overheating.
Get a copy of MemTest86 and verify the RAM at least one pass. Make sure in BIOS that you are not over clocking the memory or CPU.
I would verify that the GPU is interfacing the motherboard at 16x speed and not 4 or 8x. Most systems will knock the pcie bandwidth in half if you have an add on board in a wrong slot. You want maximum bandwidth path between memory, cpu, and gpu. The 1st page of gpu-z will tell you the interface speed, when you roll your mouse over the slot speed. Some USB-3 implementations steal PCI lanes for “Turbo mode,” disabling turbo mode can free up the GPU for 16x operation.
One last thing to check would be DPC Latency. Google DPC Latency Checker. The DCP latency of the machine should not be running in the red, nor should you be seeing spikes into red. You should be seeing a relatively flat, continuous line in the 500(Green) to 1500(yellow.) If you see spikes that repeat on interval, or mainly red indicators across the board, then you have a system driver that needs to be disabled / updated to remedy the problem.
LatencyMon – is another more complex view
Windows Performance Analyzer – also offers this view under Computation.With GPU enabled in Vegas:
You can monitor GPU with gpu-z or “amd system monitor” When the time line is at speed, you should be seeing the gpu being used, but not necessarily at 100%. In fact you should not see more than about 50-75% for smooth playback. 75%+ gpu while playback, and you most likely need a stronger gpu.
-
Try outputting to Wav64, or segmenting the output, or use a compressor like AC3, MP4/MP3. File size limitation was one of the main reasons for WAV64.
-
Have you tried nesting the file into your next project? Obviously you can save your project file as a new file removing anything you do not want in the new nested file. Then import that .VEG as a media element.
-
have you tried changing the extension to .mp4 from m4a? M4a is a mac thing to visually distinguish between audio and video file (m4v)