Sony F5 and Vegas 13

farss wrote on 4/17/2015, 6:58 AM
Shot some quick test with the beast, thought I'd try S-Log3.
Figured out that I needed to RClick the media to select the colour space in Vegas.
Why is that, the camera records everything Vegas needs to know to get it right without user intervention.
But, no S-Log3 option either, only S-Log2 which is what the F65 shoots and isn't enabled on the F5 as yet.

Still running Build 373, checked manual, checked release notes, nothing about this area of Vegas in later builds. Anyone got any clues?

Bob.

Comments

ushere wrote on 4/17/2015, 7:34 AM
ah - just you wait bob - all that will be available in new, improved, whiter than white catalyst ;-)
videoITguy wrote on 4/17/2015, 10:02 AM
Has been in Catalyst as a feature already out.
farss wrote on 4/17/2015, 5:15 PM
Downloading Catalyst Browse now.
Will be interesting to see if after installing it that S-Log3 appears as an option in Vegas 13.

The "feature" to use IDTs has been in Vegas 13 since release.

Bob.
videoITguy wrote on 4/17/2015, 6:02 PM
Bob, think you need Cat Prepare or Edit - and in case your thinking may be going down one path:
refer to this

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=923038

for understanding why CAT and Vegas are on different tracks.
farss wrote on 4/17/2015, 6:35 PM
[I]"
for understanding why CAT and Vegas are on different tracks."[/I]

I can accept that.
That doesn't mean they cannot share data table(s).
An IDT is a LUT is a table of data, simple. The ACES has specified a format for that data.
At the very most an application might wish to store that data in a more efficient format, no problem, give the user a function to import the ACES data file into the applications data file. There's also the issue of where is the data file, not a complex issue to resolve with basic code.

Bob.


videoITguy wrote on 4/17/2015, 7:28 PM
CAT in at least one iteration uses a very simple LUT file transfer structure - which is just merely a text file if you care to play with it. Of course, the trick is to find structural code (for example inside VegasPro) that would care to read it. Well really more problematically since that would be too simple, try to get SCS resources to see THAT this would be a worthwhile feature of the Vegas app.
farss wrote on 4/17/2015, 7:49 PM
[I]"Well really more problematically since that would be too simple, try to get SCS resources to see THAT this would be a worthwhile feature of the Vegas app. "[/I]

That is the whole intent of the ACES effort. Somewhat disingenuous to claim that your software supports something when it fails to embrace the very intent of the thing.


On a positive note, installed the latest versions of Catalyst Browse and Prepare.
My test footage looks impressive despite being shot through a cheap Canon cine prime and me only having a 2K monitor. Browse does manage to play the files at 25fps, Vegas 13 can at best manage 4 fps but I think we've already had that conversation.
What impresses me most is how far one can push the image without it falling apart and I'm only working with XAVC 422. Someone had left some footage on the card and at first glance compared to mine it looked unrecoverabely over exposed but I could pull it back to a quite acceptable result.
Next step, F5 RAW :)

Bob.