-
[quote user="danlasvegasnv"]I see no need to burden a system with the "lead boots" of an antivirus program if one just surfs known "safe sites." ... By the way, I have no anti-virus on this computer as well and have yet to suffer an infection.[/quote] Well with the ever-increasing use of file-based editing systems and formats
-
Thanks for that Carl. I've probably posted a few too many AVG remarks and taken the thread a little off topic anyway, so apologies on my part. I was simply puzzled by someone experiencing quite a bit of bother with a program that doesn't remotely get in my way. I genuinely hope that JohnnyReboot finds some success, somewhere along the line,
-
Well on this we'll have to agree to disagree. Instructions on upgrading software versions are common and yes, many apps will say it can be done without hassle. However, in real-world situations, simple upgrading can be extremely problematic. Microsoft say you can purchase Windows 7 and upgrade over Vista with minimal hassle. I mean, afterall, it's
-
[quote user="JohnnyReboot"] I installed AVG Free v9 over v8.5 as per previous upgrades of Free. There's no indication on AVG's site that a previous version should be removed for a clean install. [/quote] Well there's nothing on the Avid site that says users may have to 'trash' user preferences and/or 'trash' media
-
[quote user="JohnnyReboot"] AVG Free 9.x had the most from what I saw. Each upgrade was a larger install too unless I'm mistaken [/quote] That's certainly true. There are more processes with V9, but as I mentioned, I never saw excessive memory use or over-the-top CPU utilisation with any of them. The installer package is marginally
-
[quote user="JohnnyReboot"] AVG Free hogs more and more system resources with every upgrade. [/quote] Really? I've been using AVG since 7.x and I'm now happily running 9.0.698. All Task Manager processes for the AVG components total less than 12MB for me. There are memory spikes when accessing EXE files upon first access/execution
-
I checked out a trial of MC 3.x.x (can't recall the exact version) and I noticed two things. 1.) A much crisper image when parked. 2.) The console information I highlighted from early Xpress Pro and Media Composer versions changed from a maximum frame buffer size of 1920x540 to a proper 1920x1080 frame. I honestly believe that Avid engineers finally
-
[quote user="Sycophant"] If you haven't already, you should get involved in the FFMpeg mailing list - the main developer is very active there, and a few BBC techs as well. [/quote] I never thought of that. Doh. Upon reading some archived mail logs it does appear that work is underway on resolving the colourspace issues I saw when conducting
-
"Ingex encodes data with ffmpeg and writes to MXF files. The BBC contracted an Open Source developer to build a DVCPro-HD codec for ffmpeg. According to Stuart Cunningham, one of the team's software developers quoted in a computerworld.uk article on the system, this resulted in better performance than most hardware-based decoders can deliver
-
[quote user="redreini"]how can you tell that it is a fast import? Is there any hint in MC while importing.[/quote] XPP and MC will specifically use the words "FAST IMPORT" on the import progress bar.