Forum Replies Created

Page 23 of 428
  • Michael Phillips

    December 1, 2017 at 1:20 pm in reply to: Adding metadata from ALEs later in the process

    For a traditional conform, you are probably fine as you are. A lot of the other metadata can come in handy for a VFX pipeline in addition to color space, LUT and other associated image metadata. I would check with whoever is doing your conform.

    You can always merge. I would suggest you delete any metadata from the ALE that you don’t want to change in your already logged clips. So things like Name, Scene, Take, etc. in the ALE should not be present. But all the camera metadata you mentioned should remain.

    Michael

  • Michael Phillips

    November 30, 2017 at 4:19 am in reply to: Adding metadata from ALEs later in the process

    Is there anything else being logged in Resolve that you find missing in the clips? If not, there should be no issues as long as a minimum, you have the proper value in TAPE column and timecode.

    You can merge the ALE into existing master clips. Some columns may have their information updated that will propagate to the subclip. Which ones to be exact is unknown, but some will. When you open the ALE, anything in there that you feel is needed that you don’t already have logged?

    Michael

  • Michael Phillips

    November 28, 2017 at 3:13 am in reply to: Transcode Issues

    A Video only AAF will be fine back to Resolve.

    Michael

  • Michael Phillips

    November 27, 2017 at 3:20 pm in reply to: Transcode Issues

    Yes, the audio media would be imported into a 35mm/4 perf project type to get access to 1/4 frame resyncing capabilities. See my blog on that topic here:

    https://24p.com/wordpress/?p=16

    Also, I don’t trust any audio via AAF back from Resolve. If you do create VA dailies in Resolve, then use the importing of the msmMMOB.mdb file to create master clips. Do not import AAF to create the master clips.

    The method I outlined in my previous link was using Resolve to create the sync relationship as metadata, then actually sync clips in Media Composer based on the timecode reference made in Resolve based on waveform sync which Media Composer does not have for AutoSync.

    Michael

  • Michael Phillips

    November 25, 2017 at 11:32 pm in reply to: 60 fps footage – how to import Zoom sound?

    it seems that only a few Zoom models support timecode, such as the Zoom F8 multitrack. So knowing which recorder was used would help. Or you can open one of the WAV files in Sound Device’s Wave Agent application and see what it can parse from the metadata.

    Free download: https://www.sounddevices.com/products/accessories/software/wave-agent

    The fact that Media Composer did not even guess at a frame rate would lead me to believe that these files have no timecode in them, so select the frame rate of the project type being used will be your next best bet.

    Michael

  • Michael Phillips

    November 25, 2017 at 9:49 pm in reply to: Transcode Issues

    I prefer syncing in Media Composer only because you get all the metadata and ability to sync by 1/4 frame. But I just did post a blog on using Resolve to sync dailies only for the metadata, and still use Media Composer for import/sync of WAV files.

    See: https://24p.com/wordpress/?p=372

    As far as transcode in Media Composer, you need to set MC up to transcode to project settings when linked. Also, MC will default to FULL debayer so make sure you are at 1/2 or even 1/4 for doing HD proxies for dailies.

    Michael

  • Michael Phillips

    November 25, 2017 at 9:45 pm in reply to: 60 fps footage – how to import Zoom sound?

    Is there real timecode on the Zoom files? If not, just pick the rate that matches the project rate. If there is on set production timecode, then choose whatever rate was used on set.

    Audio does not have a frame rate, but the frame rate helps calculate the intended timecode by dividing the total number of “samples from midnight” by the frame rate.

    Michael

  • Michael Phillips

    November 21, 2017 at 1:22 pm in reply to: Ensure the Red Camera Proxy in Avid Workflow

    I’m glad you got a solution working. Would it be possible to get a sample Helium R3D file from you that production allows you to send? I don’t care what the image is. What version of RedCineXPro were you using that AAF’s were not working? I would like to test that out on my end.

    if possible, wetransfer.com, filemail.com, dropbox, etc to michael[at]24p[dot]com

    Michael

  • Michael Phillips

    November 20, 2017 at 9:14 pm in reply to: Trouble swapping and relinking new transcodes

    I actually got ahead of myself with OP1a – you will need a format that Media Composer can IMPORT and no link to, so make MOV wrapped DNxHD. “Batch Import” relies on what is supported via Import, so…

    As to why you are getting half your OPAtom with links and half not, I don’t know. Very strange. There’s some conflict or confusion with existing clips, but I am not sure what is could be.

    Michael

  • Michael Phillips

    November 20, 2017 at 1:43 pm in reply to: Ensure the Red Camera Proxy in Avid Workflow

    The one scenario I have not tested is Windows 10, but I have not heard of similar issues from systems running Windows 10. If making dailies, I prefer Redcine X Pro over Resolve, as it makes all the file needed in one saved set up.

    I assume the same steps with another codec/format work fine and it’s just the R3D? Very strange.

    Michael

Page 23 of 428

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy