Collaboration with Premiere Pro editors - best export/import settings

Craigster wrote on 4/16/2020, 8:11 PM

In this "stay at home" Covid-19 era, I am working in VPX while my primary collaborators have Adobe Premiere Pro.

We have been exchanging files back and forth, exporting as MP4, full HD (1080i, 1920x1080, 29.97), via h.264.

Is this optimal?

Is this approach likely degrading our video through multiple back-and-forths? (i.e. Are 3 round-trips worse than 1, or the same?)

Is there a better, recommended approach?

Like, can Premiere accept AVCHD Transport Stream?

Thank you so much!

System 1: Gigabyte Z390 Designare, i9-9900k, 64GB RAM, Radeon RX580/Intel 630, Apollo X6, multiple Black HDD & SSDs. System 2: Gigabyte Z390 Aorus Pro WiFi, i7-9700k, 64GB RAM, Radeon RX560/Intel 630, Audient iD44, multiple Black HDD & SSDs.

Comments

johnebaker wrote on 4/17/2020, 3:49 AM

@Craigster

Hi

. . . . We have been exchanging files back and forth, exporting as MP4, full HD (1080i, 1920x1080, 29.97), via h.264. Is this optimal? . . . .

That depends on what the edit/render cycle is - these files are a compressed format and every time you re-render them you lose a bit of quality.

Ideally you should be exchanging in an uncompressed format, eg AVI, however this is often not practical due to the massive files sizes ~ 150 - 250 MB per second of video.

AVCHD files are compressed more than h.264. Premiere can read them depending on the version.

As with many things , this is a balancing act and the acceptable final product is your and your collabs final decision on what is acceptable for the final product.

HTH

John EB

 

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Craigster wrote on 4/17/2020, 4:39 PM

 

That depends on what the edit/render cycle is - these files are a compressed format and every time you re-render them you lose a bit of quality.

 

This gets to the heart of what I wanted confirmation on.

I'm an audio guy. I know what I'm dealing with when I compress a .wav file to .mp3; or re-compress an .mp3 to .aac or vice versa (which can sound truly terrible).

What I've found encouraging on the audio side of things is that exporting an existing .mp3 audio file to .mp3 does NOT recompress it. It remains the same. I believe this to also be true with .mp4/.aac audio files. I was hoping that MP4 video exported as MP4 video would similarly not take an additional quality hit, if the bitrate was the same.

Wondering if the difference is:

- In Audio software, I can work with either the actual .mp3/.aac file OR bring it in as a .wav file, and when it exports back to .mp3/.aac it does the exact same compression as the original process (unless I've added further audio processing, obviously).

- In Video software, I assume now that VPX, like FCPX and Premiere Pro, they are actually first converting the MP4 info to a proprietary program format, and then re-exporting via an additional conversion process (so the MP4 is changed twice each time, rather than either remaining the same or being re-encoded identically). Thus, an additional quality hit each round trip.

Does this sound correct?

I wonder if anyone has done a controlled test on this to determine a "rule of thumb" (i.e. 1 RT - undetectible, 2RT - slightly noticeable in contrast or shadowing, 3RT - color fading, action begins to blur, 4RT - unrecommended; or something of this sort. I'd be VERY interested in such data or known/established info., if it exists.

System 1: Gigabyte Z390 Designare, i9-9900k, 64GB RAM, Radeon RX580/Intel 630, Apollo X6, multiple Black HDD & SSDs. System 2: Gigabyte Z390 Aorus Pro WiFi, i7-9700k, 64GB RAM, Radeon RX560/Intel 630, Audient iD44, multiple Black HDD & SSDs.

johnebaker wrote on 4/17/2020, 5:02 PM

@Craigster

Hi

IIRC mp3 compression is a constant compression technique the only thing that changes the compression ratio is the bitrate - which is not as complex like video which requires more complex techniques then audio to maintain quality.

. . . . VPX . . . . they are actually first converting the MP4 info to a proprietary program format . . .

Only if you are using proxy files, however these are only to improve timeline playback.

The proxy files are not used for rendering, the original clips are used, they are in effect imported / decoded to create a cmplete image per frame of video, manipulated if you have any effects and then encoded again into the new file.

There is a quality hit on each round trip.

. . . . I wonder if anyone has done a controlled test on this to determine a "rule of thumb" . . . .

A general rule of thumb would be as few times as possible - however with round robin trips tthe 'rule' depends on the final destination, video resolution and acceptable limits of quality degredation you can accept there are too many variables to generate -a 'general rule of thumb'.

In your situation the ideal process would be to change the workflow so as not involve any round trips, eg one person does all the video editing using the original video clips from the collabs.

HTH

John EB

 

 

 

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

CubeAce wrote on 4/17/2020, 5:52 PM

@Craigster

No I don't think you are correct on a second encoding of an MP3 file not producing a deteriorating second copy. If you keep recompressing that format there will be a general eventual deterioration of the sound quality not only effecting frequencies with phase complications but an increase in floor noise levels. Each pass is a rounding off of varying bit depths. It's the same with any format that is not lossless. Wav. is a direct copy of the waveform if bit depths and sampling frequencies are matched.

The same is true of digital still images or video compressed formats.

For digital still images there are two ways to capture a non-compressed image within the camera if the camera supports the file formats but there are still compromises with both file types.

One is the tiff format and only normally found on higher end digital cameras. They can produce, depending on just how high end the camera is, 14bit or 16bit images as taken directly from the sensor with each photosite's recorded photon capture level recorded and placed into it's corresponding place within the image. This results in what looks like a noisy image that is also very soft looking with no white balance, noise reduction, sharpening, or other alterations that the cameras' second processing unit dedicated to those tasks would normally clean up. The advantage to those who are good enough at editing is the wider tonal range you can get using greater bit depths. But as most sensors and their corresponding DACs work in 16bit, those cameras that can only give a 14 bit output will lose out quite a lot in that respect.

The second file type is DNG or Digital NeGative (More commonly referred to as raw files) is not an image file at all but an instruction set that within an editor capable of reading it can reproduce an image from the instructions within the file. If you have the corresponding codec on your system you can view thumbnails within windows, but they are not the image. They are smaller embedded jpgs within the file to show up within folders for easier identification.

The advantage of a DNG file is it also records all the camera settings at the time the shot was taken, including white balance, sharpening, noise reduction and so forth, so you can at least have a starting point. Any converting or altering of such a file is not permanent and can be reworked as and when needed. The converted output to a useable file format will be slightly compressed though compared to what you will see in the editors window if your monitor has a high enough bit depth of reproduction that few if any have.

When you use a video editor, as far as I'm aware, the file is loaded 'as is' and only loses any quality on export as it also works on instruction sets as far as I'm aware. This is why there is a list of useable codecs on every NLEs specification sheet.

As john said, there are lossless file types you can choose for export, but the resultant file sizes as much larger than the original files unless the original files came directly from a camera sensor and encoded into a digital raw format that MEP at least can't handle.

I agree with John's summary.

Last changed by CubeAce on 4/17/2020, 5:56 PM, changed a total of 2 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."