Any drawbacks using "Windows Imaging Component" ?
Hi,
Is there any drawbacks using the "Windows Imaging Component" for the Media Rendering engine?
I am running Media Pro 1.1 and Capture One Pro 6.3.2 on Windows 7 64-bit. I am not able to get my full previews correctly rendered using "phase One" as engine.Only the thumbnails is rendered ok.
I am only going to use Media Pro for organizing and metadata. All editing is done in Capture One.
So.. any drawbacks NOT using C1 as engine inside Media Pro?
Is there any drawbacks using the "Windows Imaging Component" for the Media Rendering engine?
I am running Media Pro 1.1 and Capture One Pro 6.3.2 on Windows 7 64-bit. I am not able to get my full previews correctly rendered using "phase One" as engine.Only the thumbnails is rendered ok.
I am only going to use Media Pro for organizing and metadata. All editing is done in Capture One.
So.. any drawbacks NOT using C1 as engine inside Media Pro?
0
-
The only drawback is that your edits in CO1 are not reflected.
After that on windows 7 64 bit as long as you have the codecs it's miles better, bigger offline previews ability to view your raw images full size.
Unless its just me on W7 64bit then using the PhaseOne engine you are limited to
1- no offline previews and just thumbnails.
2-A maxum of 800px size for viewing.
Aas I said if it is not just me then this is really poor and pathetic for a dam program using the PhaseOne engine. 😭0 -
I have edited my first post - my thumnails are ok with the capture one engine, but not the full previews of the NEFs when running on win7 64-bit.
So we are in the same boat :-S0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare