Aaron Star
Forum Replies Created
-
Since you have no other boards installed, you may need to contact ASUS and ask them what that means. It could also be a bug in GPU-z not correctly understanding the x99 board. It’s hard to say what the issues really is. Have you check the motherboard manual for that X4 or Auto settings? I would think AUTO would work with such new hardware on both the MB and GPU.
I also have to correct my multi GPU statement. Depending on the 59xx series CPU you have, you may be able to run 2x GPUs at 16x speed. If you have the 59xx series CPU with only 28 lanes, obviously you can run only 1 GPU at 16 lanes speed. This should not really factor into what we are troubleshooting because you only have one card.
-
As far as my understanding of how millisecond effects video editing, an 8MS monitor should be good for about 125FPS editing. Assuming that 8MS monitor is actually refreshing the screen faster than 125Hz. 30FPS is only like 33ms response.
-
My question on the x16 GPU issue. Is the GPU installed in the PCIe slot closest to your CPU, or is it installed in the slot furthest away from the CPU. The 2 slots nearest the CPU should be x16 capable on an x99 board, meaning you should be able to run dual GPUs at full speed.
Could you post a photo of how you have your boards installed into the motherboard? Board placement for accessory boards is sort of important, so that you do not impede the GPU bandwidth.
x4 v1.1 is like 1GB/s when you should be getting 16GB/s through to the board.
-
With only 4GB of memory, I would reset that value to the default and then leave it alone. Increasing that setting with so little memory will increase the amount of memory swapping. Use Shift+M vs Shift+B if you need the preview function, it will use less memory.
-
I would convert the large file in question to some other container like, AVI or .MXF. This can be done with FFMPEG, Quicktime pro, or one of the Sony Catalyst products. HDCAM-sr-lite, XDCAM-ex, or Cineform.avi would be good minimize generational loss. However, you could just use FFMPEG to copy the file contents over to an .MP4 container which would likely solve your problems.
Quicktime for windows is purposely gimped by Apple, and has limitations with file size and in some cases file quantity. Windows users are waiting patiently for Apple to upgrade QuickTime to 64-bit. I think peace in the Middle East will come 1st however.
-
wow that sucks man. Bios is normally a pretty easy to upgrade, what with manufacturer update apps and stuff now. Might be for the best, if you installed the correct BIOS, maybe there was something else wrong with the board if it failed.
Post again when you get back up, would like to know how things turn out.
-
The camera you posted comes up as a 1080-50P camera, but your project settings show you in 29.97. What frame rate and bit rate you shooting on your camera?
Is your media in .MTS format when you edit? I do not recommend editing in .MTS format for stability issues I have seen in the past. Convert your footage to XDCAM-EX, or Cineform(low).AVI then edit that material.
Do you not use the GPU on you system for stability reasons? With only 4 cores and 4 processing threads, you could really use the added abilities of the GPU in that system.
I would make sure to render out to Sony AVC.mp4 to the exact same video settings (profile) as the source material is shot in (Frame rate, resolution) “Media info” can help with determining the exact video formats:
https://mediaarea.net/en/MediaInfo
For youtube and based on what you posted about your workflow, you might want to try this path:
- Camera > Vegas
- Rendering Camera footage in Vegas to Sony.MFX>XDCAM-EX.MXF
- Edit the resulting XDCAM.MXF files.
- Render to XDCAM-EX, which should be a smart render if you have not done a lot of color correction and pretty much just cut/dissolves and titles.
- Upload the resulting XDCAM file directly to YouTube.
You might consider using a DSLR camera in timelapse mode, then import the stills as an image sequence. The you can very the playback speed by import at different frame rates. You can also use playrate like you are doing it now. The DSLR would give your drawings a richer look.
-
Well the temps look good during render, I do not see much of an issue there.
In Vegas, make sure your GPU is selected under Options>Preferences> Video> GPU acceleration. Restart Vegas if it was not selected.
You might try posting some images from GPU-z : https://www.techpowerup.com/downloads/2524/techpowerup-gpu-z-v0-8-5/
On the sensor tab of GPU-z, you can monitor GPU utilization during playback. Try this with a simple straight up file, and then one with Sony Min and Max filter applied. With Min/Max applied you should see some heavy GPU utilization.
One the 1st page of GPU-z if you roll over the “Bus Interface” field, you should get a popup that shows your GPU interface speed. This should read max speed.
An alternate is AMD System Monitor: https://support.amd.com/en-us/kb-articles/Pages/AMDSystemMonitor.aspx
This app provides a Task Manger like view of CPU+GPU utilization during playback.
I personally like Speccy – If you could post a .speccy file, that gives a lot more comprehensive view of the system config. File > Save Snapshot.
In Speccy – you can verify memory settings, Storage interface connection standards, Heat, see details on drivers loaded, and motherboard specifics.If you are trying to create 1080-60P material, your project settings frame rate should be 1920×1080-59.94 Progressive. You can use the Match media Icon Button in the upper right corner to match your project to the source material.
There have been other posts on Hero 4 footage issues. For HD most like to convert the footage to Cinform.avi using the Hero app, then edit the resulting files. Converting to HDCAM-SR-Lite, or XDCAM-EX.MXF would be another Vegas optimized way of editing that content. Since the Vegas render profiles are dated, you will need to create your own 60P profiles by changing the Frame rate to 59.94.
For the 4K hero footage in Vegas, converting your footage to Sony XAVC-intra.mxf Same here for the render profiles and 59.94/60P if you do not have one that matches.
8-Bit mode vs 32-bit Video Levels in project settings – for smoothest playback stay in 8-bit mode. 32-bit video levels for converting 10-bit video formats to 10-bit capable codecs (HDCAM, Cineform, XAVC-I.) Also most believe you should color correct in 32-bit VL mode. However, if do not have a deep color / wide gamut monitor attached properly, your display is just previewing in 8-bit color mode.
The w8100 is 30-bit/10-bit video capable, but does require proper monitor and cabling. Obviously you will not see 10-bit video levels while previewing in 8-bit playback mode.
***Note on 60P material – most people posting render times are doing so for 24-30P material. Rendering 60i or 60P is rendering 2x the amount of frames so render times will need to be correlated to like for like. 2x the amount of time to render 2x the amount of frames is logical.
-
What codec and file format is your source footage?
What camera is it from?
What is your workflow? Meaning are you dropping camera original on the timeline and rendering to mp4 to upload to YouTube or something else?
What is your display destination for your edited material?
What codec are you rendering to for the final?
Have you used “AMD system monitor” or GPU-z to verify that the GPU is being used during timeline playback? Is the GPU enabled under preferences? Is your GPU running the latest AMD driver?
What are your current project settings?
Have you tried converting your UHD footage to XAVC-I.mxf, and not using LGOP format the camera likely shoots in?
For HD material, have you tried XDCAM-ex, or 422, or HDCAM-SR-Lite 60P, or Cineform.AVI?
System Things to check:
- Latest Video Driver from AMD
- Latest BIOS from motherboard manufacturer
- Latest Motherboard Chipset INF from Intel for your given chipset.
- Latest Network & Sound from chipset manufacturers
- All updates applied from MS, and non waiting to complete on system reboot
-
You should be good normally with just dragging and dropping footage on to the timeline. Vegas is one of the better NLEs that handles varying footage types. Other NLEs would have you convert your footage into a format that the NLE requires. You should not need an external program, I always call Vegas the Swiss Army Knife of video.
I would try the Disable Resample on each of your clips, this is done by right clicking on the timeline media and going to properties.
My suggestion of converting the footage is more of a conforming media suggestion. That way Vegas is just editing and not converting also on the fly.