Review has potential, but isn’t useful to us unless we can review takes in-context. Screening Room had the Cuts Tray where the number of context shots can be adjusted, and I haven’t been able to find similar functionality in Review. Please let me know if I am missing something!
Hello! You should be able to access your cuts with the same level of control from the Context menu located here:
Once the cut is loaded it will automatically set the ins/outs at two shots at the head and two at the tail if available. You can then adjust by using the controls on the player bar or dragging the ins and outs by grabbing the marker on the timeline. Zoom to range is also an option if you want to focus on just the content within the in and out markers.
Let me know if you have any other questions and if this is working for you!
Hello, thank you for your reply and apologies for the delay in mine.
I see that those functions exist, but when I play a take in the context of a cut, the timeline is blurry, only spans 23 frames, and cannot be played or scrubbed. The playback rate is also incorrect, at 23.976 fps instead of the source’s 30 fps (for individual takes and in-cut context).
Might this be an issue with how we are submitting cuts to Flow? I’m happy to raise this with my team if it may be user error.
The 23.976 framerate issue has been there since the early days on the closed beta and it’s pretty concerning from a reliability standpoint. I flagged this back in April here and there should be something in the closed beta threads that @contardom can confirm.
Building on top of the in/out markers conversation, there should be a way to snap them to the nearest cut in the timeline. Right now the Review App doesn’t have that option or any way to configure the Mini-cut feature as the Cuts Tray allowed, so you’re either guessing visually or scrubbing through and setting them manually. The UI wording is also confusing — “Reset {Start/End} of Range” makes it sound like it’ll reset or remove the in/out to the entire cut, when really you want “Set {In/Out} Point” or “Set {In/Out} Frame.”
Cheers!
Thank you both for the feedback! I will follow up individually for more details on your specific issues. In the meantime I can share our documentation for custom transcoding that may shed some light on how things are working with the information we’re using in Review.
Let me know if either of these links helps and if not what is missing. We’re still improving these and trying to figure out what is missing for users.
Hi Michael,
The main issue is that our entire pipeline is end-to-end 25fps and using the native transcoder without customizations.
We don’t know where the 23.976fps comes from in the first place.
Thanks!