MEP generates 'Perfbounce' files

terrypin wrote on 11/11/2012, 9:58 AM

I'm occasionally finding my project folders contain strange 'perfbounce' files. Two types seen so far: HO like these:

https://dl.dropbox.com/u/4019461/MEP2013-Perfbounce-1.jpg

As you see, when opened in a hex editor they seem to contain what I'd call 'nothing'.

And the other type is MPG which when played just seem to be parts of projects. I have 5 of them, ranging from 20 MB to 440 MB.

Anyone have any idea what they are please?

--
Terry, East Grinstead, UK

 

 

Last changed by terrypin on 11/11/2012, 10:02 AM, changed a total of 3 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Comments

emmrecs wrote on 11/11/2012, 10:39 AM

Hi Terry.

I've also seen these files and my belief is that they are the results of any pre-rendering you ask MEP/VPX to do.  i.e. when a pre-rendered section is played back MEP actually uses these "Perfbounce" files rather than the "original" footage.

HTH

Jeff

Last changed by emmrecs on 11/11/2012, 10:39 AM, changed a total of 1 times.

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

terrypin wrote on 11/11/2012, 11:57 AM

Hi Jeff,

Thanks, you're clearly right. I just did a pre-render and it created an .HO and an .MXV file. The latter can run in MEP or Photo Manager (its default). Odd that previously MPG files were created. Edit: From further tests the reason is that MX pre-rendering creates MPG and 2013 creates MXV.

--------------------

Maybe you can clarify a couple of points about pre-rendering for me please? As you see from the following, a test took well over 3 minutes to render an 8 second section! In practice. Edit: Just repeated with MX, which took only 1 minute - 3 times faster.

I'm not sure what resolution the MXV is (neither MediaInfo nor GSpot support that file type, and Photo Manager 8 tells me nothing) but even if it's 1920 x 1080, the project setting, it's still a bit slower than exporting to that quality MP4. And the big advantage of that alternative is that I can then re-import and work with just one clip on one track (or two if I display any audio). Whereas I'm stuck here with 5 or 6 tracks. That's not only untidy but if, for example, I want to move those 'pre-rendered' objects to my main project that requires great care to slot them into available tracks.

So why would you choose this instead of simply exporting it and re-importing?

--
Terry, East Grinstead, UK

Last changed by terrypin on 11/11/2012, 12:35 PM, changed a total of 4 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Scenestealer wrote on 11/11/2012, 10:38 PM

Yeah - funny name eh Terry - but yes that is where the Preview Rendering files are created. Please see my comments in your other post about H/W Accel.

As I mentioned in another post "MEP 2013 Review"  I find this feature rather dubious for several reasons:

1.These files stay there until you delete them from the folder.

2. The section in the timeline is tied to the timecode and not to the object so, any slight change to the preview rendered section or any change in object length upstream of it means that it needs to be created again. It does not overwrite the previous large file either.

3. It would be almost as quick and sometimes better (as you point out) to export the section and bring it back to the timeline. I guess the factors against this is that if you want to tweak a complex effect you would have to build it again. Also, when the final project is renderd this section would be another generation down unless you were using Smart Render.

It is nice to know its there though.

Last changed by Scenestealer on 11/11/2012, 10:38 PM, changed a total of 1 times.

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.

terrypin wrote on 11/12/2012, 2:49 AM

Thanks Peter.

Until convinced otherwise, I'm going to ignore this feature. But I'd love to hear from anyone who is using it regularly to advantage.

BTW, those speed tests I did earlier proved hard to reproduce. Once again I suspect some settings interaction I hadn't accounted for. I'll try again after a brief break to do some creative work!

--
Terry, East Grinstead, UK

Last changed by terrypin on 11/12/2012, 2:49 AM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)