SLOW ending time for AME conversion

Report · Mar 02, 2019

Having updated my video card from a GTX 1050Ti to an RTX 2070, I have been impressed by two things: the zippier speed of Premiere Pro and the lack of failure of the preview window - often a problem with the 1050Ti. Also, the speed of transcodes from XAVC-S files to h264 MP4 files that incorporate edits and effects (and the lack of failures there also) seem to result from the much-beefier card.

One problem I have experienced (so far on only one video but still it's annoying!) is the hang of AME after it appears to have fully processed a video. The timings in the AME window for this 2-hour 11-minute video shows elapsed 2:32:59 and 0 remaining. However, the software hasn't given up the file yet and still appears to be processing. On my hard drive are the .aac file and .m4v file which obviously need to be coupled with each other. The coupling of these files so far is in excess of two hours...remember this is AFTER the progress bar has indicated that it has finished.

It appears that the coupling process is the last part of the puzzle and in the past was very swiftly done. Can anyone shed light on where the process may be hanging up?

The last frames of my project are of a PNG file over which runs the end of a rolling title (credits) created in the Essential Graphics panel with a dissolve effect at the very end.

Report · Mar 02, 2019

Muxing is the process of combining the separate video and audio files into one. It does normally occur pretty swiftly, and is most affected by disk speeds.

Look there for possible explanations.

Report · Mar 02, 2019

Hi, Jim, and thanks for chiming in so quickly.

I've checked the logs for further information.

Here's the log for a 10mbps transcode of the file:

03/01/2019 04:39:24 PM : Queue Started

- Source File: C:\Users\Jay\AppData\Local\Temp\CONSUL 2.prproj

- Output File: O:\SCROOGE 2018 Media\0118 CONSUL COMPLETE.mp4

- Preset Used: Match Source - High bitrate

- Video: 3840x2160 (1.0), 29.97 fps, Progressive, Hardware Encoding, 02;11;44;19

- Audio: AAC, 320 kbps, 48 kHz, Stereo

- Bitrate: VBR, 1 pass, Target 10.00 Mbps

- Encoding Time: 03:14:40

03/01/2019 07:54:04 PM : File Successfully Encoded

Here's the same info for the one encoded - same folder, same drive - at 40mbps:

03/02/2019 10:47:09 AM : Queue Started

- Source File: C:\Users\Jay\AppData\Local\Temp\CONSUL 2_1.prproj

- Output File: O:\SCROOGE 2018 Media\0118819 CONSUL COMPLETE.mp4

- Preset Used: YouTube 2160p 4K Ultra HD

- Video: 3840x2160 (1.0), 29.97 fps, Progressive, Hardware Encoding, 02;11;44;19

- Audio: AAC, 320 kbps, 48 kHz, Stereo

- Bitrate: VBR, 1 pass, Target 40.00 Mbps

- Encoding Time: 05:50:03

03/02/2019 04:05:04 PM : File Successfully Encoded

The drive in question is an external 3.1 USB (Gen-1) connected directly to my new Asus Prime Z390-A motherboard (rear connector). The primary system drive is a 500GB Samsung SSD.

The original footage comes from my two camcorders, both Sony, one an FDR-AX100 and the other an HXR-NX80, and results from a multi-camera rendering of the opera THE CONSUL by Menotti. The original footage is around 55-58mbps.

The quality of the later (and much larger) file is obviously better. Sharper, better color rendition. What doesn't make sense is the muxing process taking so long! In each case, the actual encoding of the video file was within 30 minutes of the actual length of the project (2h11m44s19f). So the 40mbps took 3 1/2 hours longer...and it was all muxing.

I'll experiment with different drive usage. I can also write to a RAID connected via eSATA; I can try that with the next performance of the show that I'm editing now. If the log info strikes you as informative, do let me know. Again, thanks for your input which will inform further testing.

Jay

Report · Mar 03, 2019

My first thought is to use only internal drives for editing. Save externals only for backups and archiving.

Ideally, a five drive system is a good starting point. It offers both excellent speed and organization.

C: Windows & Programs

D: Project files, audio files, image files

E: Cache & Scratch

F: Camera media and proxies

G: Exports