Command line to bypass CPU sniffing by MEP17+

pmikep wrote on 3/18/2011, 11:59 AM

The marketing material for MEP17+ says the product sniffs your CPU and changes presets depending on what CPU you have.

"PC performance benchmarking

In order to always offer the most optimal presets when editing AVCHD material, MAGIX Movie Edit Pro 17 Plus automatically offers the best settings for your PC."

I don't want it to do that. I want to get the best quality, no matter how much time it takes. Is there a command line switch or a checkbox I can click so that MEP17+ bypasses the CPU preset feature?

========

MORE: I have MEP17+ installed on two desktops at two different offices where I work. One with an overclocked E4500 Core 2 Duo, the other with an AMD II X2, both running 3 GHz. When I encode a project to WMA with the C2D, it takes 2 minutes, but the file size is 144 MB. When I encode the same project to WMA on the AMD, it takes 8 minutes at 14 MB. When I encode the same project with MEP15+ on the C2D, it also takes 8 minutes at 14MB. I want to tell MEP17+ to ignore what CPU I'm using and "just do it."

Comments

yvon-robert wrote on 3/18/2011, 8:25 PM

Hi,

You can produce the same quality with slow or fast computer. When Magix check your computer and I suppose you place on timeline a full HD project 1920 x 1080 it suggest to convert to less quality 1280 x 720 if you answer don't convert it use the maximum quality also when your burn a DVD or Bl-Ray you can adjust the bit rate to maximum or use variable bit rate. Naturally if you specify conditions with Encoder Setting button a slow computer need much time to create the disk file the burning time can be the same. Slow computer is more problematic than new generation.

Regards,

johnebaker wrote on 10/26/2015, 6:03 AM

. . . . Is there a command line switch for videoplus or perhaps for mxoutprocmem.exe that will bypass the CPU sniffing or tell 17+ to always use the best quality presets? . . . .

AFAIK there is no way of turning off the 'sniffing'

. . . . the product sniffs your CPU and changes presets depending on what CPU you have. . . .I don't want it to do that. I want to get the best quality, no matter how much time it takes. . . . .In order to always offer the most optimal presets when editing AVCHD material

If you do not let it do this you could end up seriously crippling the program - the optimisation is about how the program runs for best performance not best quality of output. Output quality is determined by the settings you use on export and whether you use GPU acceleration and which codec is used.

If you have installed one of the all in one codec packs then this can also affect which codec is used and, from my experience, usually have a negative effect.

. . . . I export (i.e., encode) the project into WMA with EXACTLY the same parameters on both machines. (Quality 75, complex encoding, etc.) I get two different results in the quality of compression . . . .

Unless the two computers are absolutely identical then this is normal, however even this does not guarantee that the installations are identical - Windows was notorious for doing this.

HTH

John EB