[Job Ter burg]

Tinyurl of the version matrix:
https://tinyurl.com/7hakjp

[Job Ter burg]

I’m pretty sure the solution is this:
In your Quicktime player settings, make sure to uncheck DirectX and choose GDI-only. It’s a known issue that this setting can cause issues with QT exports on v3 and later. I had it myself, and this fixed it for me.

As said, you probably rolled back too far on your QT version, though. Check the version matrix to make sure.
https://avidtechnology.custhelp.com/cgi-bin/avidtechnology.cfg/php/enduser/std_adp.php?p_faqid=75147&p_created=1202760115&p_sid=pqo_72sj&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NTIsNTImcF9wcm9kcz0yNzYmcF9jYXRzPTAmcF9wdj0xLjI3NiZwX2N2PSZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PW1hdHJpeA**&p_li=&p_topview=1

[Job Ter burg]

Not sure what version you are in, but MC v3 and later allow you to switch your project format from 25i to 25p with a click. I don’t think it is really necessary to recapture your footage. Also, I’m not sure what happens to effects when you do that.
If you are pre-v3, you should try to create a new 25p project, open the bin with your sequence (from the original 25i project), and you should be able to play and edit that sequence. Again, not sure if you would really need to batch capture to get your effects right, but perhaps you can give it a try.
Be sure to copy your sequence before modifying anything. Just in case you hate the result 😉

[Job Ter burg]

Close the application. Rename the OMFI MediaFiles folder. Create a new OMFI MediaFiles folder. Drag a few hundred files from the old folder into the new one. Launch MC, it will rebuild the database. Close MC. Move some more files into the new folder. Repeat.

[Job Ter burg]

That would be 2.7 and later (see http://www.avid.com/p2 and check the step-by-step guide). A new version of MC (3.5) has just been released (yesterday). Upgrading from 2.6 to 3.5 would cost you 395 USD on the Avid webstore. 3.5 also features AMA, which allows for improved workflows with filebased footage.
But P2 media works fine on 2.7/2.8/3.0/3.1. Just make sure to check the step-by-step guide to fully understand the process.

[Job Ter burg]

Very likely you have too many files in the folder. Should be under 10.000, preferable under 5.000, or else reading those mediafiles folders becomes a chore for the OS. This is even more true when using Mac drives on PC’s.

[Job Ter burg]

What are you exporting to and with what purpose?
The 709 setting will not alter any levels, so you retain all original levels of the source footage. So that would be the best setting when exporting for color correction.

[Job Ter burg]

Symphony v3.x absolutely benefits from Vista 64b. The increase in available physical RAM alone was worth it for me.
That said, I did tweak V64B, turned off a lot of fancy stuff, and such.

[Job Ter burg]

Those are not plasma, but TFT and LCD.

The 226 is a 1680×1050 monitor. Is your graphics card set to that resolution? It needs to feed the 226 monitor its native resolution, or else you’ll be seeing softness and other scaling issues.

Another thing: does the same happen with other fonts?
If you export a still file at the native resolution you are working on, are you seeing the same issue on that exported still? Can you export a still and post it, so we can get a better idea of what it looks like?

[Job Ter burg]

What type of monitor are you watching this on? Are you looking at the native resolution? If any scaling is involved (either on screen or through a monitor, that might seriously interfere.