ProRes support totally broken

dmac_ wrote on 10/5/2018, 10:13 AM

NOTE: I tried submitting this as a support ticket, but I receive the error "Unfortunately there was an error during sending your request, please try again later", so it seems the support form is broken right now too.

Hi there,
There are many ProRes files which don't open correctly in Vegas 15 (latest build).
One common problem is that the file is 23.98fps but appears in Vegas as 24fps.
Another even more common one is that the video opens, but only every fourth frame is decoded: for example, if the source has these frames:

1 2 3 4 5 6 7 8 9 10 11 12

It appears in Vegas as:

1 1 1 4 4 4 7 7 7 10 10 10

This software is becoming useless to me because of this problem. I need to transcode almost everything just to get it to work.

Can someone from support contact me please?

Comments

Eagle Six wrote on 10/5/2018, 10:55 AM

Hi dmac,

It appears to be working fine for me. MVP16 build 261, Windows 7, ProRes HQ 1080 23.976p. Recorded at 23.976, show 23.976 in Vegas, plays frame by frame correctly. My source files are from an Atomos Ninja Flame and GH4.

Perhaps there is something going on in your system or with your source media. Can you provide additional information? What device or camera are you using? Mediainfo (in text mode) screenshot of your source media specs? Are you matching project properties with the source media? Did this just start happening? Have you had good results in the past with the same type source media? The more information you provide, the better chance someone will be able to assist.

Last changed by Eagle Six on 10/5/2018, 11:01 AM, changed a total of 1 times.

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Marco. wrote on 10/5/2018, 11:16 AM

ProRes works fine here in VP15 build 384. No frames doubled or tripled and 23,976 fps is read as 23,976.

It would help to have such a source file causing the trouble available

Eagle Six wrote on 10/5/2018, 11:27 AM

Yes, I should have added that as well. Same results with MVP15 build 384, frame by frame works fine, 23.976 is read and played back as it should. And same results with SVP13 build 453, frame by frame works fine, 23.976 is read and played back as it should.

Last changed by Eagle Six on 10/5/2018, 11:28 AM, changed a total of 1 times.

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

dmac_ wrote on 10/5/2018, 11:38 AM

It's not with every file. Unfortunately because I'm dealing with copyrighted film material, sharing files is not possible.

For example, this one plays fine:

 

General

Format :QuickTime

Format/Info :Original Apple specifications

File size :120 GiB

Duration :1 h 37 min

Overall bit rate mode :Variable

Overall bit rate :177 Mb/s

Encoded date :UTC 2018-09-11 22:32:39

Tagged date :UTC 2018-09-11 22:32:39

Writing library :Apple QuickTime

 

Video

ID :1

Format :ProRes

Format version :Version 0

Format profile :422 HQ

Codec ID :apch

Duration :1 h 37 min

Bit rate mode :Variable

Bit rate :175 Mb/s

Width :1 920 pixels

Height :1 080 pixels

Display aspect ratio :16:9

Frame rate mode :Constant

Frame rate :24.000 FPS

Color space :YUV

Chroma subsampling :4:2:2

Scan type :Progressive

Bits/(Pixel*Frame) :3.517

Stream size :119 GiB (99%)

Writing library :apd0

Language :English

Encoded date :UTC 2018-09-11 22:32:39

Tagged date :UTC 2018-09-11 22:32:39

Matrix coefficients :BT.709

 

 

 

But this one, which was output from Digital Vision Nucoda/Phoenix, doesn't:

 

General

Format :MPEG-4

Format profile :QuickTime

Codec ID :qt 0000.00 (qt )

File size :135 GiB

Duration :1 h 37 min

Overall bit rate :198 Mb/s

Encoded date :UTC 2018-10-02 16:48:26

Tagged date :UTC 2018-10-02 17:27:14

Writing library :Apple QuickTime

 

Video

ID :1

Format :ProRes

Format version :Version 0

Format profile :422 HQ

Codec ID :apch

Duration :1 h 37 min

Bit rate mode :Constant

Bit rate :198 Mb/s

Width :1 920 pixels

Height :1 080 pixels

Display aspect ratio :16:9

Frame rate mode :Constant

Frame rate :23.976 (24000/1001) FPS

Color space :YUV

Chroma subsampling :4:2:2

Scan type :Progressive

Bits/(Pixel*Frame) :3.982

Stream size :135 GiB (100%)

Title :Core Media Video

Writing library :adv0

Encoded date :UTC 2018-10-02 16:48:26

Tagged date :UTC 2018-10-02 17:27:14

Color primaries :BT.709

Transfer characteristics :BT.709

Matrix coefficients :BT.709

D7K wrote on 10/5/2018, 11:43 AM

My system works fine with PRORES even those generated by Mercalli. Where are you files created. How to you expect us to know your issue when you don't give us all the info : system specs, source of files, Vegas settings.

It works on lots of machines so what ever your doing it something specific to your setup.

Eagle Six wrote on 10/5/2018, 12:27 PM

dmac, the specs you provided are almost identical to those I have as source files. There is nothing that jumps out as perhaps the cause of your issue. Also, I would find it hard to believe that Digital Vision would supply a format that would cause problems, but of course that doesn't make any difference in your situation.

Are any of the other source media files which do not playback properly also from Digital Vision? Are any of the source media files which do not play back from any other source or have different specs? I think it is going to be difficult without a sample source file to see if others can duplicate your issue on their system.

As an easy to determine outside chance, have you recently done a full reset of your Vegas Pro and dump the application cache data? It is quick, easy and cheap, and just maybe could have something to do with it, although I would guess not.

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Marco. wrote on 10/5/2018, 12:32 PM

I see the file which doesn't work correctly is constant bitrate. Not sure, but I think this breaks the ProRes standard which is meant to be variable bitrate only. At least I've never seen a CBR ProRes file before and also the Apple ProRes White Paper mention VBR only.

dmac_ wrote on 10/5/2018, 12:47 PM

Thanks all. Yes, this survives a system reformat, etc. It also happens to another editor who is also using the most recent version of Vegas. It didn't happen on the older Sony versions (like v12).

It's hard to know what the trigger is since it's not always possible to find out what application wrote the file.

Musicvid wrote on 10/5/2018, 5:43 PM

Unfortunately because I'm dealing with copyrighted film material, sharing files is not easy. 

Please read the Terms of Service and Community Rule #5 thoroughly before continuing. This type of post presents a Conflict of Interest for some professional contributes, my signature should give you the idea.

The customer is also obligated not to procure, install, use, execute, or make available software, files, information, or other content relating to MAGIX services for which he/she does not have the necessary rights, which infringe upon the rights of third parties, especially national and international copyrights or commercially-protected rights, like trademarks, registered designs, or patents, or which infringe upon the personal rights of third parties, or to get access to information not meant for end users.

5. Promotion of illegal copies and illegal downloads, and pornographic, racist, or discriminating contributions

Requesting, promoting, advertising, and linking to copyright-protected material for illegal purposes is strictly forbidden. Linking to, advertising, and displaying pornographic material will not be tolerated. Entries which incite racial hatred or provoke seditious actions may be punishable by law. Discrimination against minorities will not be tolerated.

dmac_ wrote on 10/5/2018, 5:49 PM

^ Updated wording to be more clear. In case there was any doubt, there is zero possibility of sharing copyrighted material without permission. My original phrasing of "not easy" meant "not easy to get permission".

Musicvid wrote on 10/5/2018, 6:03 PM

And when you get that permission, as I have done successfully, feel free to share.Unti then.

dmac_ wrote on 10/5/2018, 6:21 PM

Yes, I'm aware of the workings of copyright law, thanks.

Musicvid wrote on 10/5/2018, 6:55 PM

And that makes it a lot easier on us pastured pros, who still may have something to lose.

Thanks.

NickHope wrote on 10/5/2018, 10:37 PM

As a workaround, you could try installing Quicktime for Windows and disabling Vegas Pro's native ProRes codec by renaming the folder C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\mxhevcplug\. Playback performance may be poor since Quicktime for Windows operates via a 32-bit "surrogate", but if it decodes correctly then you could re-encode the problem clip to something else like XAVC-I.

dmac_ wrote on 10/5/2018, 10:47 PM

Thanks Nick - I wasn't aware that was an option! I know Quicktime for Windows is a supposed security risk hence it being phased out, so by comparison, running proxies with FFMPEG isn't so bad...

Former user wrote on 10/6/2018, 7:38 AM

That security risk thing is not an issue. I have always had QT on my computer and never any security problems.