- #Using chroma key in edius pro 8 how to#
- #Using chroma key in edius pro 8 movie#
- #Using chroma key in edius pro 8 full#
Like Resolve, title has no noticeable effect. Example from my GH5 of course UHD 60P just plays in one track in EDIUS with no colour space correction ( PCC kills it ) but in Vegas will play with two tracks ( one PIP ) corrected and a title with CPU still only at 54% and GPU at 25%. My only performance comparison is to do the same files in Vegas and EDIUS. There are other controls for stereo tracks etc for the mixer. I usually always use stereo for my projects. Audio will get displayed in this format for each file if it is set as the project setting. If you bring in 8 mono tracks of audio in the source file it will display them. Each track will display the audio associated with that source. Doesn't mean other sources will display in this format just that source. If you place a video track with 5.1 audio in the timeline, it will display 5.1 audio for that source. Not sure what you did for audio but it has unlimited audio tracks and will do correct 5.1 if that is your choice. In Auto for any of the selections it will try and maintain the project frame rate but just like EDIUS it can be forced to a selection. As such you can setup for realtime speed for editing or arrange for higher quality for grading. The controls for playback are setup on the top left of the preview window. I have never got external preview to work successfully on Vegas so do not bother as most of my use is for audio.
#Using chroma key in edius pro 8 how to#
Just like Resolve you really need to know how to set up Vegas. I’ll also try using a dedicated Title track, I always use video tracks for titles and never have dedicated Title tracks, maybe there’s a difference between how Edius processes assets between Title and Video tracks? Again, it’s worth me trying. I’ll change the output type of QuickTitler, I believe there are two output types that can be selected when saving, although I’m not sure that these would be completely different formats that would have such huge differences on CPU usage but it’s always worth a try. When I’m back at my machine later tonight or tomorrow, I’ll try some tests. I also doubt that it’s only you and I that are observing and feeling the high CPU usage when using QuickTitler assets. Maybe there could also be something to do with system hardware? Maybe the types of video codecs being used at the same time as the QuickTitler assets. I wonder if this could be down to the other media and assets also being used at the same time. That’s interesting that you also have a similar high usage when using a QuickTitler like I do and Anton is saying that in his edits QuickTitler is using no CPU power at all.
#Using chroma key in edius pro 8 full#
Still keeping the full resolution playback set, now when we apply the chroma key 92% CPU buffer = 2 real time playback just on the edge.
#Using chroma key in edius pro 8 movie#
Lastly If we replace the XAVCI clip by render and add to timeline with HQX movie we start to see the effect chroma key has.Ĭlip on its own full resolution selected gives a 19% CPU load Render clip itself: real time not recovered no point in rendering surely that's not right either? (Render clip issue been like that for ages since Edius 7). This is very high for one clip.Īdd chroma key no clip on V1 - real time lost Original green screen clip XAVCI 50p on V2 no chroma key 54% CPU. Render and add to timeline blocks editing as it puts up an unavailable clip which displays a checkerboard pattern - wrong in Edius 9 the clip is only applied when rendering is complete. QT also slow updating screen and Decklink HDMI output disappears, restored on closing QT Vistitle typing in subtitle text painfully slow about half a second per character. In order to transcribe speech and create subtitles real time playback is required.
Replace jpeg under chroma key with png no change. Remove render and add to timeline chroma key clip, reverting back to clip with chroma key applied 1/4 resolution required for real time of stack of clips. Reduce resolution to 8Bit Real time regained, CPU 82%.
Replace jpg with png 71% CPU real time maintained
Remove QT and add Vistitle for subtitles CPU 78% real time maintained. Now add QT 92% CPU load and real time lost. Take away QT clip and add JPG (1024 by 768) reduced to PIP with layouter 44% CPU load. CPU Load 19%Īdd Quick Title with big letters "TEST" across screen movie from chroma key on XAVCI clip (Chroma key also is heavy on CPU resources see below dotted lines in this message). V1 rendered and add to timeline Grass Valley HQX. This is revealing a can of worms as Dave suggested But in my case it is a combination of clip types that conspire to reduce real time playback.
0 kommentar(er)
