Aaron Star
Forum Replies Created
-
SmartScope or Ultra scope from Blackmagic will accept HDMI.
If you are using Nikon DSRL, https://www.cinematographerpro.com – has live histogram which is the same thing different format to the info.
You do not really say what camera you are trying to do this from.
-
Are you shooting RAW video or AVCHD?
The clip with the tree issues is not long enough to see beyond the camera shake for me. If the leaves are going soft in the background, could be the bit rate to capture that detail is to high for the codec your are recording/processing to. Shooting handheld raises the bar on codec bandwidth requirements, due to the amount of picture change. Same goes for the Steadicam shot, large picture change challenges the low processing power in DSRL cameras. Best to record individual frames, then try and determine if your moves are to fast for your frame rate.
The Steadicam shot looks a little like a combo of rolling shutter and LGOP compression artifact with MP4. I would see if you get the same issue shooting in an intra frame codec like RAW video. Could also be something with your workflow to vimeo, its hard to say really.
-
GoPro as far as I know just records in h.264 at 60Mbs. I would think your system would decode even that high of a bitrate just fine. I would try using vegas to convert the gopro original file to Cinform.avi, HDCAM-SR-Lite.MXF, XDCAM-EX.MXF, or XAVC-intra.MXF. Try the playback of one of those formats and let us know if the playback is better.
Since the Vegas render profiles are dated, you will need to create your own 60P profiles by changing the Frame rate to 59.94.
-
The videos are not embedded or are no longer posted. Hard to see what the issue is.
-
A simple way to do this would be to create a generated black clip the length you want. Then cut, enable ripple edit, then paste/insert that clip at the event between each clip on the timeline. Click, paste, click, paste…
I do not know of any script that does that, but you could write one.
-
I would see if FFMPEG can recompress that 444 footage into prores422-hq format. Should work along with the other files in Vegas after that.
-
Read the expansion slots section in the manual, page 8. Clearly you need to keep the M2 enabled. The GPU needs to go in a non shared full bandwidth slot. The slots are marked on the board. The devil is in the details of the ** notes. The diagram on page 1-13 and 1-14 could help as well.
Due to the way they have implemented the M2, that slot shares bandwidth/pci lanes on the cpu side. You need to determine the slot that maintains full bandwidth when things like the M2 and USB 3. Supposedly slot pci16_1 one does this, but there is still something that is not right.
In bios look for advanced, then check the following:
DMI – gen 2.0 should be disabled.
NB PCIE Configuration – pcie16_1 should be Gen3, not auto. Per documentation on page 3-38. Auto for other pcie slots on the board.
I do not believe the x16 issue will solve all playback performance issues, especially if you drop a compute heavy plugins on a clip. For optimization reasons, you want to max the bandwidth from the memory/cpu to the gpu memory/gpu for the best opencl performance and playback.
-
So this is what I am talking about. Prepare exports openexr, yet edit has no support for image sequence formats like dpx, or exr. Unless there is some other way to import that I am not seeing.
-
I would post “media info” on the media file. Media info is an app. That way people can offer some suggestions.
Have you tried converting to another file format like xdcam, hdcam, cineform, or xavc-i?
Have you verified the mac is not overheating?
-
Catalyst Edit is much improved over the 1.0 version tried originally. It still feels much like 1.5 version software.
Some of the notable issues I saw was:
ACES support but no EXR support.
F5 RAW support to ACES, but no export to a non 709 format.
Cineform.avi did not seem to be recognized.
Prores-HQ.mov on PC did not see to be recognized.