SVP14 H.265 Very Poor Performance Performance

[Matthew Jeschke]

I just finished trying a MP4 container for h.265. Vegas won’t allow me to add the clip to the timeline.

I have a theory but unsure how to fix / test. I had VLC player on my editing machine. VLC player will not play h.265 it has the same issue as vegas. I was woundering if Vegas is using the VLC decoder to run timeline playback. I uninstalled VLC player but not sure if it removed the codecs.

How does one know what codecs / DLL(s) vegas is pulling from ?

————————————–

I do Architectural Photograph & Cinematography as a part of being a Residential Real Estate Consultant.

Some of my work can be seen at,
https://www.youtube.com/keystoaz/
https://www.vimeo.com/matthewjeschke/
https://www.keystoaz.com/

PS. It\’s an excellent excuse to ride off what I love, Camera equipment 🙂

[Graham Bernard]

[Matthew Jeschke] ” I was woundering if Vegas is using the VLC decoder to run timeline playback. I uninstalled VLC player but not sure if it removed the codecs.

How does one know what codecs / DLL(s) vegas is pulling from ?”

Supported formats
Import
4K XAVC S, 4K XAVC, XDCAM EX, XDCAM Optical, DV, HDV, AVCHD, NXCAM, MOV, MP4, WMV, MPEG-1/2/4, H.264/AVC, H.265/HEVC, WAV, FLAC, AAC, MP3, OGG, WMA, Surround Sound/5.1, BMP, PNG, JPEG, TIFF, OpenEXR-, DPX- and WDP image sequences

Export
DVD, Blu-ray Disc, AVCHD Disc, (DV-)AVI, MJPEG, MXF, MOV, WMV, XAVC, XAVC S, MPEG-1/2/4, H.264/AVC, H.265/HEVC, WAV, MP3, BMP, PNG, JPEG, TIFF, OpenEXR- , DPX- and WDP image sequences

As to your theory viz VLC being used by VP – not so much! – Read on and weep….

From reading widely on the OFFICIAL MAGIX VegasPro site, regarding the niceties of this specific H.265 it appears that the DJI drone output for H256 has a CODEC identifier within the File Header that is NOT recognised in VP, namely, here in BOLD:

Codec ID : avc1 (avc1/isom)

If you go to the more detailed sheets/displays in MediaInfo you should spot it. There are HEXADECIMAL hacks for this and as such is waaaay beyond my competence. Mostly I have a self-enforced embargo on anything that is more than just “User-Usability”. IMO this is far more fundamental than either of us contemplated.

You’d have to determine directly from DJI just what the feature-rich option that comes with this in the Header. I’m sure they will be helpful. Maybe it’s an iThang?

Here, if you haven’t read it already is one of the many, many places that has highlighted this Header issue

https://forum.dji.com/thread-75719-1-1.html
https://forum.dji.com/thread-88330-1-1.html

So, what will you decide to do? Get funky with the HexDec VooDoo? Transcode? Capture in a VP friendly format? – Word to and from the wise: Any new piece of kit, I obtain or capture myself Media, I then trial it through Vegas Pro before laying down the plastic!

And yes, I’m still awfully jealous of your piece of kit!

* Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Matthew Jeschke]

I think we may have arrived at similar points. I read something where premiere will not handle a lens profile in the metadata and was throwing premiere for loop too. I am not shy to dive into editing the metadata ☺ thanks for that post i will give it a whirl.

Worse comes to worse i will shoot in h.264. I know that works fine.

Thx btw p4p is highly rec9mmended 🙂

————————————–

I do Architectural Photograph & Cinematography as a part of being a Residential Real Estate Consultant.

Some of my work can be seen at,
https://www.youtube.com/keystoaz/
https://www.vimeo.com/matthewjeschke/
https://www.keystoaz.com/

PS. It\’s an excellent excuse to ride off what I love, Camera equipment 🙂

[Yevgeniy Pakkel]

Hi, i am also having problems playing back Samsung NX1 h265 files, and wondering and wanna beg for someones help.

i have I7 5820k at 4.2 gtx 1080 and xeon 22 cores/44 threats at 2.6 and as well as gtx 980ti and both machines cant playback smoothly. Im at 29.97 fps 99% of the time but it stutters every 2 seconds or so to like 25fps and then back to 29.97 but in reality it completely stutters and freezes for a maybe 5-10 frames and then its back to smooth for another 1-3 seconds

Anyone dealing with NX1 files can shine some light for me please?

Thank you!

[Matthew Jeschke]

Tech support at Magix is assisting. Hopefully we can get it figured out.

I tested various h.265 clips downloaded from the web. Seems issue is not isolated to a few cameras / metadata… but rather the h.265 decoder itself as all clips behaved similarly in vegas.

I also contacted DJI to see if they updated their metadata and or h.265 encoder. They have not.

Will keep you apprised of what I find out.

————————————–

I do Architectural Photograph & Cinematography as a part of being a Residential Real Estate Consultant.

Some of my work can be seen at,
https://www.youtube.com/keystoaz/
https://www.vimeo.com/matthewjeschke/
https://www.keystoaz.com/

PS. It\’s an excellent excuse to ride off what I love, Camera equipment 🙂

[Matthew Jeschke]

After several weeks of emailing back and forth with Magixs I have given up. Their suggestion was to use Proxies ☹

My final question was, do you have any hardware you have tested that works with h.265. I am still awaiting response on that message. My thinking is the decoder for Vegas Pro h.265 remains to be optimized.

I see Premier Pro has support and am reading good things about it. Hate to switch though as I have thousands invested in software packages for a Vegas workflow.

Anybody else have luck with Vegas h.265 performance?

On another note, I don’t know why none of these NLE’s have a proxy setup where you can simply click render from proxies folder or render from originals when creating your final output.

————————————–

I do Architectural Photograph & Cinematography as a part of being a Residential Real Estate Consultant.

Some of my work can be seen at,
https://www.youtube.com/keystoaz/
https://www.vimeo.com/matthewjeschke/
https://www.keystoaz.com/

PS. It\’s an excellent excuse to ride off what I love, Camera equipment 🙂

[Aaron Star]

From the AMD marketing materials on the RX480:

“The Radeon RX series features accelerated H.265 encoding and decoding, enabling …”

This means that media player would utilize onboard GPU playback through the video drivers.

Vegas’s software video engine does not work that way. Vegas decompresses the h.265 video to RGB in CPU/OpenCL, then attempts to work the video in 4096x2160x128x30-60fps in a Floating Point mode. This is what give you the quality of working at very high color levels. That works out to about 4.2- 8.5GB/s. Even though you have a nice system rig, it cannot keep up frame wise with the decode calculations, then the conversions to RGB, then send that back to the display driver, and do that faster than 30-60FPS. 30-60 FPS is 16-34ms. That means your system has to turn a frame in less than 16-34ms, with all the other system overheads, to maintain real time playback.

Windows media player uses the display driver directly, then the GPU offloads the h.265 calculations to an ASIC or register on the GPU specifically designed to handle that problem quickly. Then feeds the playback results to a window overlaid on the screen display, everything happens internally to the GPU at that 256GB/s available bandwidth.

Vegas’s mode of operation allows you to mix and effect the RGB information. GPU playback is just that, you cannot effect the info being shown to screen. Its a trade off.

All that is why they are telling you to work in proxy mode. Your system does not have what it takes to process the software engine in real-time. Convert your media to a format that has less calculation overhead/complexity. h.265 is really meant to be a playback format and not editing. This all echos back to the early days of h.264 and editing, before CPU/GPU power advancements. Even h.264 is a playback codec, and yet CPU/GPU performance is so high now its overcoming the end users slack in avoiding workflow steps.

[Matthew Jeschke]

Finally a real answer. I’d figured it might be something to this effect. I wanted Magix’s support to pass my question onto the software engineers and ask them what hardware does work for h.265 but such luck. I hate to purchase a massively expensive processor just to learn it doesn’t work either.

I just tried the trial version of Vegas Pro 15. No further enhancements in h.265 from what I could see. I guess we’re just too close to the cutting edge of this codec to learn much more on what works / what doesn’t?

I simply went back to h.264. Would love to use proxies but workflow appears to be a PITA so kind of avoiding it at all costs. I use proxies with RAW footage simply because I cannot get Vegas Pro to take Cinima DNG sequences (maybe you know how to do that?)

THanks a million for your help. Very much appreciated 🙂

————————————–

I do Architectural Photograph & Cinematography as a part of being a Residential Real Estate Consultant.

Some of my work can be seen at,
https://www.youtube.com/keystoaz/
https://www.vimeo.com/matthewjeschke/
https://www.keystoaz.com/

PS. It\’s an excellent excuse to ride off what I love, Camera equipment 🙂