You can use Vegas to change to XAVC-Intra. What is the issue with using it straight in Vegas though? Not able to install Quicktime for 13, or is the timeline preview too slow?

ProRes 4:2:2 @UHD plays back tolerably accelerating with an R9 290 on 13 (Preview at a quarter frame).

(Windows 7)

Found this through one of the tutorial links; could be helpful.

"What is the issue with using it straight in Vegas though? "

The clips go black after some editing, and previewing them in Vegas explore the Prores clips are black and can not be brought onto the Vegas timeline after they have went to total a black playback.

So it's not frame rate issue. I just need to get the clips converted into a HQ 4k format other then Prores

My point was on 13, with Quicktime installed on Win7, there is no issue with ProRes other than perhaps the speed due to the processing being proxied through Quicktime. I assume you are running 14 then since you are using Windows 10? ProRes support is supposed to be native in 14, so there should not be an issue there either. Since I am not running Vegas 14 or Windows 10, I'll have to defer to those that are running that setup.

I'm using v13. HD prores no issues in v14....4k prores 422 LT the issues are there.

V14 crashes soon after it loads the few prores clips on the tack.

Posting information about your media as detailed by the application may help others provide some advice.

This shows you where to get the info.

Here is my result on a ProRes 4:2:2 file as reported via file properties in Vegas 13 on Windows 7, proxying through Quicktime:

General
  Name: NJAFLM_S001_S001_T002.MOV
  Folder: C:\Users\Public\Documents\Vegas_Temp
  Type: QuickTime
  Size: 41.04 GB (42,024,771,072 bytes)
  Created: Monday, March 06, 2017, 10:15:41 PM
  Modified: Wednesday, August 10, 2016, 4:48:08 PM
  Accessed: Monday, March 06, 2017, 10:15:41 PM
  Attributes: Archive

Streams
  Audio: 00:06:21.248, 48,000 Hz, 32 Bit (IEEE Float), 4 Channel, 24-bit Integer
  Video: 00:06:21.248, 29.970 fps, 3840x2160x24, Apple ProRes 422 (HQ)

Summary
  Software: NinjaFlame - 7.03   
  [GUDE]: {7BB3FE15-954A-4E75-B5E1-45EE98F74990}
  [TCFM]: 25769803782

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: qt7plug.dll
  Folder: C:\Program Files\Sony\Vegas Pro 13.0\FileIO Plug-Ins\qt7plug
  Format: QuickTime 7
  Version: Version 13.0 (Build 453)
  Company: Sony Creative Software Inc.

I appreciate your help. I really need a transcending option so I can make the deadline and troubleshoot when I have the time.

Well if you have the cash, you may want to look into MainConcept TotalCode. Nothing dealing with Apple ProRes is both free and LEGAL at the same time . . .

Have you tried Sony Catalyst Prepare?

Much cheaper than TotalCode, that's for sure.

Have not tried Catalyst Prepare yet...I'll test it out. Yea that is a cheaper then TotalCode.

Have not tried Catalyst Prepare yet...I'll test it out. Yea that is a cheaper then TotalCode.

I have the last perpetual license of Catalyst Prepare; they changed to a subscription model already.

Ok Catalyst Prepare works great!

I have the last perpetual license of Catalyst Prepare; they changed to a subscription model already.

I missed the perpetual license ;] No fun paying for something I'll use infrequently.

Acrovid FootageStudio is another converter worth testing.

Wow, how my workflow is limiting the quality. I tried Catalyst Browse and converted a ProRes 4:2:2 HQ 10-bit recording into an XAVC-Intra 480 class Rec.2020 file and the difference is amazing, despite the resultant file being 8-bit. I cannot find a 10-bit file type to convert to that is recognized in Vegas 13. 10-bit XAVC output support is strangely missing it seems. I'm surprise the 480 class file isn't 10-bit, but Browse confirms it is 8-bit.

you can also transcode in sony browse (FREE)

I AM NOT TROLLING...

but am very curious as to why anyone needs such esoteric 10bit di's, or even lossless codecs unless they're working on intensive greenscreen or animation for broadcast or cinema release?

i used to regularly do work for a number of broadcasters and, in general, never went more than 2>3 generations, and hardly ever used di's (source was usually hdcam mp4 @ 35 or 50mbs).

i only started using di's when i needed to work with outside facilities, and that was usually dnxhd. now, with resolve i use xavc-i.

CineForm will be supported with its 10 bit properties in Vegas Pro and it plays smooth (if only your storage allows for the data rates). FootageStudio offers CineForm output.

@ushere I'm trying to stick with using Vegas 13 for now, so it appears CineForm is a must. While utilizing 10-bit formats throughout may not be "required," I tend to take every effort I can to ensure quality, with the possible exception of when the desire for quality causes enormous render times when I could hardware accelerate older codecs (h.264). Whether there will be any difference when the end result is an 8-bit encoding depends on the processing along the way (like LUT usage and type, color adjustments and FX, etc). For now I am still learning, and I'm trying to figure out the steps needed to ensure 10-bit file formats all the way through.

Besides, the future is 10-bit HDR.

@Marco.  Thanks for the CineForm information!

@cogdiv. thanks for the reply. i have to say i'm happy that i won't be having to deal with the future since i'm now semi-retired and my existing clients are a bunch of equally old farts like myself whose main concern is script rather than anything else ;-)

i regularly go to the big electric stores and check out what's new in the way of screens, and to be perfectly honest, i find 4k a little too sharp, almost 'brittle', and not at all lifelike. the very few examples of hdr i've seen are even more removed from reality. but i suppose it sells boxes - obviously 3d didn't since i saw hardly any the last time i looked....