Issues after employing 'shot match' feature

mojoaudioguru wrote on 4/10/2017, 4:48 PM

I have edited a 4 camera video shoot, that also includes a 12 track multi-track digital audio soundtrack. (I taped a 40 piece orchestra, and recorded the audio using a Zoom R16 digital multi-track recorder, for the audio) Because one of the cameras employed was a Canon DSLR, I had to use the 'Shot Match' feature to match the DSLR to the 3 remaining matching Panasonic HMC Series video cameras. The edit is complete. it's 41 minutes long. Shot in 1920x1080p. 30fps. But now, during playback, the video will stop after about 30-35 seconds of play. No reason is given. It just stops playing. I haven't burned it to Blu-ray yet. I was playing it back for final visual verification. No matter where I begin play of the 9 chaptered video, it simply stops after 30-35 seconds of play time. I've been utilizing MEP since 1999, so I'm not a novis. My computer is a Windows 7 Ultimate 64bit, with a liquid cooled Q9550 CPU, (Overclocked to 3.55 GHz), with 10 gig of DDR3 RAM, an EnVidia GTX750Ti, with it's own 2 gig of DDR5 RAM. I'm employing MEP 2017 Pro Plus. I've never had this issue with any previous versions of MEP. Does anyone know why it stops playing? Or, has anyone experienced the same thing? I currently have version 16.0.3.66  This is the 3rd time I've edited a video for this client and his orchestra.  However, the previous videotapings only encompassed 3 exact video cameras, and required no 'shot match' utilization. Anyone have any thoughts? The computer has no other issues with any other software.  

 

Comments

johnebaker wrote on 4/11/2017, 2:53 AM

Hi

. . . . 4 camera video . . . . a 12 track multi-track digital audio soundtrack . . . . to use the 'Shot Match' feature. . . .

Shot match is a very processor intensive effect and depending on the track arrangement, e.g. Multi-cam editing was used, is enough to reduce any PC to a crawl / stop when viewing in the Preview monitor

If you have not done so try the following:

  1. Turn on Proxy files in the projects settings
     
  2. Render the timeline for smoother playback
     
  3. Export to mp4 to test

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.

Scenestealer wrote on 4/11/2017, 6:39 AM

Good to see someone else has struck this issue. I have observed it also with VPX and was starting to think it may be my system. In my case it occurs with 7 short 1080 50P 3 - 8 sec clips all with Shotmatch and little else. It never plays through them all without quitting. It is almost as though the PC runs out of RAM but TM shows no unusual increase in usage. Playback is smooth until it stops.

The feature, when first added in VPX8, was very heavy on processor load and one of the subsequent updates indicated that they had made it less resource hungry, which it now seems to be.....but this???

I have not exported the projects I have found the problem on, have you Mojoaudioguru? The only other thing I see common at present is Panasonic. My footage is from an HDC-SD900.

Peter

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

browj2 wrote on 4/11/2017, 8:00 AM

Hi,

This is not a solution to the Shot Match problem but a workaround. Did you try exporting to mxv and running that in a project. If that works, then save the original project, do a save as with a new name, delete everything from the timeline and replace it with the mxv file. I think that the chapter markers will still be in the correct locations, but you should check.

This is my procedure when I use Neat Video to any great extent. Otherwise, the encoding takes a very long time and has sometimes resulted in stuttering in the output file.

John C.B.

VideoPro X(16); Movie Studio 2025 Platinum; Music Maker 2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB, 12TB, 14TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos