Aaron Star
Forum Replies Created
-
Blender is really the most cost effective solution, if you can get over the learning curve. I liken Blender to a canvas, set of brushes, and mixing board. All the tools are there, the Pros vs the Scrubs are quickly weeded out due to artistic talent and understanding of their medium.
-
If you are just looking for an HD camera, I would seriously look into ebaying a PMW_200. This is a pro level camera that records in XDCAM422, which is a 50Mbs Constant bit rate codec, which will drop onto the timeline and be fully GPU accelerated. This is the codec that Vegas Pro was pretty much designed to operate, and is the choice of a lot of News stations.
Encoding from XDCAM to H.264 will be quick, and if you have the upstream bandwidth you can upload the resulting xdcam file directly to Youtube.
XDCAM is also smart render capable, which makes it a good choice if you are not making a lot of changes with effects. Timeline renders will be slow only through rendering graphics and whatnot. The rest of the timeline will be a direct copy at disk speeds.
The PMW_200 will not do 1080-60p, but will do 720-60p
Something to think about.
-
You may want to post a screenshot of Speccy;s overview page. This would clue the forum into the specifics of your configuration.
If you are having trouble with 4K playback, it is likely due to your system hardware not being able to keep up.
-
At this moment in release schedules, the i7-5960 or 5930 would be the most powerful system you can assemble without going multi CPU Xeon. The X99 chipset is better than the 170 due to the quad channel memory controller, and the amount of PCI lanes. The skylake series is a more economical chipset and design.
There are a couple of pending releases that may be worth waiting for, if at least waiting for the price drops on existing designs. The 490X release will make the 390X and Fury X much more reasonable price. The CannonLake series of intel processors will include something called AVX-512, this will feature to a software developer like Magix will offer performance advantages.
We are all just looking in the crystal ball from our positions. This is what I see.
-
This may not have been worded right. Most Canon DSLRs will kill the HDMI when you hit record, and record to the internal card. You are correct when you say that monitor and external recorder are the same when hanging off the HDMI port. It is something to test depending on how you are planning to record. The C100 runs a continuous HDMI feed even when recording to the internal card.
-
Hey you can always do what you want to do, myself and other on the forum are only trying to help.
“when you pass from CPU rendering to GPU rendering. ” I do not think you get that Vegas is OpenCL based and in no way Cuda based. The MC encoder is the only Cuda part of vegas, unless some 3rd party plug has coded for Cuda. You should do some research into what OpenCL is and how to optimize it on your system. Here are a couple links:
https://en.m.wikipedia.org/wiki/OpenCL
https://www.anandtech.com/show/9390/the-amd-radeon-r9-fury-x-review/24 – this shows the monumental GAP in performance that AMD holds in OpenCL. Luxmark 2.0 utilizes OpenCL in the same way Vegas sees the system resources, and so makes for a good test utility.
-
I have not tried this, but I have been told the following.
You can open the file in a binary editor, and replace the header and footer with one from another file of like project settings. If you can decern the image data from header/footer, then you could trim out any errored info where the recording failed.
Clearly you would want to try this on a copy of your file. Google turns up a bunch of repair tools that are likley just doing what is described above. Watch out for malware, and scan anything you try with Windows defender, and malware bytes before installing.
-
Rendering times are subjective in Vegas. Render times vary greatly based on source codec, timeline GPU effects used, the type of effects used, the compositing layers required, drop shdows, ect. GPU assist can improve frame building prior to hitting the encoder, which can improve the encoder output FPS.
The OP has a new system which has an I5 installed where an i7 should be. A discreete GPU would be an improvement to this system, but the CPU is gimped compared to an i7. A very high end GPU might seem like its not being utilized due to the CPU bottlenecking. However, a highend GPU would be utilized, with the results being returned so fast that the normal GPU utilization monitors do not show the spikes.
High system utilizaton does not nessesarily mean good performance, as we do not drive our cars around the street at 6000RPM all the time. Improved render times might be speedometer that everyone uses, but there are other factors in terms of system latencies that factor in. The old Sony Timeline benchmark is outdated, and needs to be upgraded to 4K, and possibly run in at least 32-bit Video level mode. With an upgraded benchmark, we would see a much greater gap between system configurations and GPUs, and it would be much easier for people to see what they are getting for the money.
Most do not require the MC GPU encoder anymore, and either use the Sony AVC or Handbrake system for MP4 output.
I posted this a day or two ago on another thread.
Just use the onboard GPU if you are waiting on a 480. The RX480 is great on power usage, but not the top in calc speeds. If you want to just stick in a temp card to enable OpenCL/GPU benefits, there is always ebay. I would recommend the following in order:
AMD:
5770 (1360 gflops)
r9-270x
6970
7970-ghz
RX480
r9-290x
R9-390x
R9-FuryX (8600 gflops)The i7-6700 is around 113 gflops, so if you do any blurs or other GPU effects adding a GPU will help even a modern CPU. If you are planning on running a 4K monitor, then use the onboard GPU, and the add on GPU for compute only. 7970 and above are the only cards to support 4k. There is a difference between display resolution ability and computational performance.
-
When you shoot DSLR and do not record to an external recorder, the DSLR shuts off the HDMI output. Maybe they corrected this on the your DSLR. The C100 will output HDMI and record at the same time.
When I used to work with the C100, I would use the onboard screen for handheld operation, and a large HD monitor on a stand for tripod / video village work. A large HP dreamcolor on a stand with the C100 is a really nice way to work, as you can instantly judge soft focus, and color accuracy. There are other manufactures of high quality 10-bit monitors, and if you go super pro end those monitors will include scopes and what not. A monitor and laptop rig on a stand/cart running BM ultrascope would seemlike a nice way to work, but I have never used it.
You did not really say you needed a small monitor, so I thought I would just add this.
-
Vegas supports OpenCL and not Cuda, with the exeption of the MC mp4 encoder that is no longer supported by the latest Nv cards. NV cards/drivers do claim they support OpenCL, but whether its poor gflops performance or poor driver support in lieu thier propriatry CUDA offering, the stability in Vegas does not seem to be there. AMDs hardware/driver support of OpenCL from user experience in Vegas seems to be much better, and more stable.
It is my belief that people often build their systems in the reverse fashion. They know what they want in terms of the latest hardware and whats hot in marketing at the time they have money to purchase. When they really should be concidering the needs of applications like Vegas, then building a system that meets those needs to be best of their financial ability. A frame or 2 more on a video game, but then pulling your hair out in Vegas because you have the wrong video card seems backwards to me.
Other Video NLEs have based their engines on CUDA and so make more sense if you have build your system with NV in mind.