RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40ĭisk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)ĭisk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drivesĭisk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642Ĭase: LIAN LI PC-90 Black Aluminum ATX Full Tower CaseĬPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System GPU: Currently intel on-die video adapter Motherboard: ASUS ProArt Z790-CREATOR WIFIĬPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K The metadata for the FFMpeg re-wrapped video looks like this: So does the original file's header contain something that confuses Vegas? ![]() I see some differences in the metadata header. I found a workaround: if I import the video file to MyFFPMpeg and rewrap it as another mp4 (pass through video and audio), the new video file imports to Vegas OK, with audio and video included. The videos play OK in VLC, but Media Player Classic goes "cannot render file".įFMPeg shows the following info of the video file:Ĭlean aperture display aspect ratio : 2.000 However, when I try to import these MP4 files to Vegas Pro, they import as audio only, and are considered audio files by Vegas. I decided to use high bitrate MP4 as the intermediate editing format, because the CineForm files (the other format AVP can render) are gigantic and slow to render. ![]() I'm rendering VR videos out of Kolor AutoPano Video Pro for furher editing in Vegas Pro.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |