OK - so in our new "Video and Audio Production" VP14 software - even if I wanted to wait ages and render my Slog footage to something viewable using ACES (LUTs are not supported at all) - it's impossible, as Vegas just quits within several seconds... Bravo, Magix!
Piotr
PS. Why doesn't this board support even a basic spell checker?!!!
Pitor,
have you enabled GPU acceleration? Either for the preview or in the render templates? If yes, please try to disable that.
Second: I can try to repro that on my machine during the next weekend. But to do so I need much more details.
- type of footage (your FS7?)
- complete project settings
- settings for the footage in terms of color space since you need that in ACES
- complete render settings.
Beside that it also the question what type of workflow you follow here. I for my side tend to follow another approach. Two different ways:
a) I use a LUT plugin (either from Hitfilm or Looks3, of the free vision color plugin), and grade the footage in Vegas. I edit my 10bit Cineform or XAVC I footage or ProRes footage in 8bit project settings, only for rendering I go to 32bit floating point.
b) I grade the footage in Resolve or in Catalyst prepare to rec709. From Resolve I render to Cineform, from Catalyst to XAVC I. And then I edit the footage (without LUT plugin) in Vegas what tends to be pure cuts any more, and render to 10bit using the 32bit floating point mode.
Dear Wolfgang,
Of course work-arounds are always possible, but that's not my point. It's just plain broken... Yes, I do mean my XAVC-I FS7 footage in UFHD, 25 fps. ACES RRT is sRGB; the particular clip color space - F65 (5500K). Actually, the colors are pretty nice in 10 bit on my Decklink, but... I cannot even prerender to RAM, cause the thing just disappears (I mean VP 14, not the picture)... And, I'm also using Resolve Studio and never use ACES as I find RCM much more powerful. As to the free LUT plugin (the one from Vision Color) - c'mon it's a joke (a 32-bit plugin). Does Hitfilm or Looks3 have some trial plugins I could check the performance of?
Thanks
Piotr
PS. I guess that if I really wanted to stay serious about Vegas, I'd be using the free Browse to de-LUT my log footage and transcode to some intermediate .... Getting the proper 709 look is easy (actually - similar to Resolve RCM). One thing I will miss so much about Vegas is its efficient cutting, that's about it - now that even AC3-Pro has been take away :(
Anyway, it could be very helpful to know if same error happens when GPU support is turned off in options/preferences.
Yes - with GPU off, Vegas also crashed after several seconds of SHIFT-B. The only "positive" difference being that that color space changes didn't flash on and off, as with GPU on.
OK, so finally I managed to create my RAM preview of several seconds worth of an ACES-transformed video. I even rendered it out to my M.2 NVMe scratch drive (HEVC, P3 D60 output transform as my Quantum Dot HDR-ready Samsung SUHD looks best with the color space/gamma, but I'm digressing). My good Lord - isn't a RAM preview, which has all the timeline processing rendered into it already, supposed to play full speed? It's jsut the pathetic 3-4 fps... Same with the "selectively prerendered" files from my 2500 MB/s capable cache drive!
For RAM preview, I set the buffer to some 20,000 (I have 64GB of RAM). Don't the Release Notes explicitely mention
*Improved playback and editing performance when using a Dynamic RAM Preview cache size greater than 200 MB
???
Piotr