Hevc не открывается в vegas pro

Обновлено: 06.07.2024

One of the main reasons that I upgraded to Vegas Pro 14 was that H.265 support was listed as a feature of this release. When I try to open an H.265 video file I am told that the file contains no video. What do I need to do to use H.265 files?

What's the file container type? MP4, MOV, other? Maybe post a MediaInfo report to give some information on your file.

It's an MP4. Here is an export of MediaInfo for this file. In case it matters, this file was generated by a DJI Phantom 4 Professional camera drone. The file plays flawlessly on my Windows 10 machine.

General
Complete name : E:\Drone\2016-12-04 Ranch Distance Run (P4P)\DJI_0018.MP4
Format : MPEG-4
Format profile : JVT
Codec ID : avc1 (avc1/isom)
File size : 3.81 GiB
Duration : 5 min 28 s
Overall bit rate : 99.8 Mb/s
Comment : DE=None, Mode=P

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L5@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 5 min 27 s
Bit rate : 100.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.402
Stream size : 3.81 GiB (100%)
Title : DJI.HVC
Language : English
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Other
Type : meta
Duration : 5 min 28 s
Default : No
Bit rate mode : VBR

There are a couple of items that look a little strange in that info. Its the whole listing?

"Codec ID : avc1 (avc1/isom)"

I am not sure why avc1 is up there in the file header. avc1 is for AVC files and not HEVC files. The isom is common and normal.

I don't know what the "Other meta" stream is at the bottom

From reading posts on this forum the Vegas HEVC decoder has been kinda finiky. Maybe it is confused by the avc1 in the header and complaining about that. Maybe it should ignore that file header item since the ID in the video stream header is correct and that is the one that really matters. Maybe the meta stream is confusing the Vegas decoder.

Those are my thoughts. Have you contacted Magix support yet?

I don't have a DJI media file but I can load HEVC MP4 files into Vegas 14 that have been generated by ffmpeg based utilities.

You could try remuxing the file with ffmpeg or something else. That should get rid of the avc1 in the file header which can help to see if that is a workaround until Magix can truely sort the issue. Here is a Windows batch file that you can drag and drop file(s) onto and it will remux the file. The new file has the same name as the source with an _mux appended. Change the path to whereever you unzip ffmpeg. Zeranoe is a good place to get an ffmpeg binary. You can name the batch remux_hevc.cmd. Any name is fine. You just want cmd or bat as the file extension.

That's everything that was in the export file. I went back and checked the "Advanced" box but MediaInfo output the same data. Below is a MediaInfo export of an H.264 file from the same drone. It appears to have more information in it. I have not contacted support yet but that will be my next step. Just wanted to try the forum first. Thank you for the observations/thoughts and the information about ffmpeg.

General
Complete name : E:\Drone\2016-11-06 JCWMA Camp Area\DJI_0802.MP4
Format : MPEG-4
Format profile : JVT
Codec ID : avc1 (avc1/isom)
File size : 1.37 GiB
Duration : 3 min 15 s
Overall bit rate mode : Variable
Overall bit rate : 60.0 Mb/s
Encoded date : UTC 2016-11-06 10:11:52
Tagged date : UTC 2016-11-06 10:11:52
Comment : 0.91.142
©xyz : +35.041462-95.479394+3.000
©xsp : +0.00
©ysp : +0.00
©zsp : +0.00
©fpt : +4.80
©fyw : -51.90
©frl : +0.30
©gpt : +0.00
©gyw : -51.10
©grl : +0.00

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings, CABAC : Yes
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=8
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 3 min 15 s
Bit rate mode : Variable
Bit rate : 60.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.241
Stream size : 1.37 GiB (100%)
Title : DJI.AVC
Language : English
Encoded date : UTC 2016-11-06 10:11:52
Tagged date : UTC 2016-11-06 10:11:52
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

In another thread the OP made a sample file available. I copiped the text of my response from there to here.

I downloaded and tried the file. Vegas does think the file is AVC. Probably for the reasons I mentioned in your other thread on this topic.

This is the text from a right click on the media file in Vegas, choosing properties and then looking at the general tab. compoundplug in the Vegas code used for general MP4+AVC file input.

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\compoundplug
Format: AVC
Version: Version 14.0 (Build 201) 64-bit
Company: MAGIX Computer Products Intl. Co.

The ffmeg remux command I mentioned in the other thread does fix this until MAGIX gets this fully sorted. I don't think DJI should be outputting the avc1 ID in the file header since avc1 indicates AVC video. The video stream correctly lists hvc1. Still DJI stuff is out there and people need it to work so Vegas should compensate.

If your DJI can output MOV files that may work around this issue more directly.

Last changed by NormanPCN on 12/12/2016, 9:27 PM, changed a total of 1 times.

I have V16 last build 352 on a PC with CPU í7-3770K and Windows 10 Pro V1803.

I'm doing 4K video only from stills 4912x3264 on the videotrack and with accompanying music on the audiotrack

The result of rendering in the MAGIX HEVC codec is a bastard with good audio, but the video is only 47 seconds long and has frame rate 449,438.

The same task works well in Vegas Pro 14 with Intel HEVC(* .mov) codec

I tried to do the same you did as I see it, see my first screenshot
The second is the result, nothing wrong I thought

I did not see what you saw, what were your (customized?) rendersettings and what were your exact projectsettings?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 21H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti, Intel HD graphics 630
Laptop :Asus EVO37T, W10 home version 21H2, CPU i7-10875H, 16 GB RAM, Intel UHD Graphics + NVIDIA GeForce RTX 2070. VP 17,18,19 and VMS PL 17 are installed, all latest builds, both Nvidia GPU's have driver version 472.47 Studiodriver. both Intel GPU's have driver: 30.0.9864
TV :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR .

Thank you for your quick response

My project settings is here

In the codec setting I have not customize anything

I tried using this setting to render a standard footage from my sony ax-100 camcorder and everything works fine

That's exactly the same I did.
Very strange that render with you.
Besides to reset Vegas to the default values is should not know anything to help you further.
To reset those Vegas default settings first be sure you saved your project, than start Vegas with hold Ctrl and Shift buttons and check this box that will pop-up.

When Vegas started again try your project again.

met vriendelijke groet
Marten

My slogan is: BE OR BECOME A STEMCELL DONOR .

Try rendering without using Intel (QSV). Render only with the CPU.

Last changed by Former user on 12/22/2018, 3:58 PM, changed a total of 1 times.

I do not have the QSV rendering enabled (It does not matter because my processor does not have QSV for the H265)

I reset Vegas to the default value but nothing has changed

I tried to render one image of duration 5 and then 10 seconds - the result was fine.

When I tried the duratin of 20s, the result was 11:06 and the frame rate was 44,698 Hz, which approximately corresponds to 20 * 25 / 44,698 = 11,19 (the number of times the frame rate increases, the duration is reduced)

I do not have the QSV rendering enabled (It does not matter because my processor does not have QSV for the H265)

You showed us here the rendersettings you used of the Magix HEVC Intel QSV render option.
If you should have no processor to do that ( in fact you have one with your Intel® HD Graphics 4000) that option and codec would not show up in the list.
The only thing you have to do is to switch to the Mainconcept HEVC in the customized setting by choosing it in the options you have.
Those are (your screenshot)

and after making the choice

to choose the mainconcept your on board graphics GPU) will not be used, only the CPU.

Last changed by j-v on 12/22/2018, 6:10 PM, changed a total of 1 times.

met vriendelijke groet
Marten

My slogan is: BE OR BECOME A STEMCELL DONOR .

I do not have the QSV rendering enabled (It does not matter because my processor does not have QSV for the H265)

That is a bug with vegas16 then. Magic HEVC gives default option of Intel QSV even though his Quicksync does not do h.265 encoding & should not show as option.

I get the same issue here in VP16 build 352.

My Intel i7-5960X does not have QSV but when I choose MAGIX HEVC/AAC MP4 I only see templates with "(Intel QSV)" after them.

If I render stills with "Intel QSV" selected as the Encode mode, the rendered video stream is too short.

If I render stills with "MainConcept HEVC" selected, the rendered video is OK.

If I render video media (not stills) with either "Intel QSV" or "MainConcept HEVC" selected, the result is OK but it is subtly different.

An "Mainconcept HEVC" render requires additional activation whereas the "Intel QSV" does not.

I'm assuming "Intel QSV" encode mode falls back to a CPU (non-QSV) encode if QSV is not available, but using a different encoder than the Mainconcept one. There is evidence of that in this old comment (in relation to the original "Intel HEVC" encoder) from a Magix developer (@VEGASHeman Could you possibly clarify?).

The term "Intel QSV" in the template name and in the "Encode mode" menu is misleading if you haven't got HEVC-capable QSV and would be better if it was just "Intel".
Intel CPU HEVC rendering of stills (without QSV) results in an incorrectly short video stream.

If I render stills with the "Intel HEVC" encoder, the rendered video is OK.

Last changed by NickHope on 12/23/2018, 1:46 AM, changed a total of 1 times.

народ что делать с кодеком vp80 от гугла. это файл не принимает ни один конвертор и вегас его тоже не распознает

Андрей, я распаковал контейнер и вставил отдельно AAC и AC3
Не приняло, перекодировал в MOV и доделал.

Владислав, исходный контейнер был какой? И происхождение звука в ас3?

Андрей, в целом всё как обычно, mp4 и отдельно без звука он его принял.
При этом, файлы mp4 c аудио AAC принял без проблем. А вот с AC3 стопорнулся. как-то не охота переустанавливать, не так уж и сложно предварительно в редакторе перепаковать звук не вынимая из контейнера.

Владислав, куда уж обычнее.
Просто для понимания -из Вики:
Контейнер MPEG-4 Part 14 поддерживает следующие форматы данных:

Видеопотоки: H.264/MPEG-4 Part 10, MPEG-4 Part 2, H.262/MPEG-2 Part 2, H.261/MPEG-1 Part 2.
Аудиопотоки: MPEG-4 Part 3, MPEG-2 Part 7, MPEG-1 Audio Layer III, MPEG-1 Audio Layer II, MPEG-1 Audio Layer I.
Субтитры: MPEG-4 Part 17.
Статичные изображения: JPEG, PNG.
Попробуй найти тут АС3

Читайте также: