-
I don' t believe that TGA contains any source metadata like timecode other than file name. What can Quantel use for conform? You can put file name and frame count in the DPX or VFX column and generate an XML file on that, but I do not believe Quantel supports the XML. The DPX will also be part of the AAF file if it can parse it properly. Did you
-
Setting the system to modify to 23.976 only deals with metdata, not the actual video. Your best bet is to work in v4 and open the 30i (with pulldown sources) into a 23.976 project. The adaptor will remove the pulldown for editing. Michael
-
Use MetaCheater to get an ALE from the QuickTime wrapped SI-2K files (assuming Cineform) and download the free cineform player codec from their site: www.cineform.com MetaCheater will create an ALE with the metadata from the files. Import the ALE, select all, batch import the QT files. Canon is a 30.000fps camera. What frame rate is your timeline? H
-
Thanks for the detailed description! Can you do a quick test to see if you have the same playback sync issues when edit rate is set to 25 instead of 24? Michael
-
The SDK has been updated to persist the unique file ID at the end of the file into the R3D header. The next version of MetaFuze will have that change to that all apps can now be consistent in Tape Name being the 16 character file name. Michael
-
Keep in mind that a PAL 24p project is still a 25fps timecode since PAL is a 25 frame format. That would explain some of your discrepancies depending on what you were expecting project wise. Timecode from BWF files are calculated based on "samples from midnight." when imported you indicate frame rate used and then the START timecode is calculated
-
Make sure audio settings are correctly set for the pullup/pulldown. Also, audio would be easiler since it playing back faster at 24fps (recorded) than the slowed down picture at 23.976. Once a file is recorded, you cannot stampe it as 48048 and expect it to slow down, it needed to be recorded that way on set. For a file already recorded as 48kHz, you
-
The fact that it is listed as 1080i means that the 24fps is inserted with a pulldown into a 59.94 interlace format which is why 1080i should work. Don't know what is up with the timecode. Try turning the TC track off in the capture window to see if it can be captured that way. Michael
-
You'll have to go 1080i project if the footage has 24 with pulldown. Timecode errors are proably due to the the 30 and 24 fps conflict. Michael
-
For picture you can do a QT export - open a 25p SD project and import after entering "ignoreqtrate true" in the console. This will create a 1:1 import resulting a 25fps playback. Qt ref out for encoding as needed. Audio as Job says need to be treated for the 4.1% speed up. Michael