[Brad Bussé]

Well, I run my Adobe software on Macs, and awhile back I had the Netsession showing up in my Activity Monitor as constantly utilizing 100% of one of my CPU cores:
https://osxdaily.com/2010/10/07/uninstall-akamai-download-manager-and-com-akamai-client-plist/

Exactly how Adobe implements and utilizes Netsession, I don’t know for sure … it’s probably outlined in the EULA. But, why choose a download manager based on a technology which according to the Akamai FAQ states that one of the benefits is to; “enable secure, closed peer-to-peer networking so that websites can deliver files to their users economically and with faster downloads.”

I know that I was seeing Netsession constantly trying to connect, so I blocked it with Little Snitch.

Here’s some other interesting reading about Adobe’s integration of P2P tech in Flash Player:
https://torrentfreak.com/adobe-flash-to-eliminate-bandwidth-costs-with-p2p-100519/

[Brad Bussé]

“Adobe has an article in their knowledge base explaining what notifications CS5 sends and how to remove Growl. They have also published a blog post all but apologizing for installing Growl on users’ systems without permission, and saying that they are “actively working to mitigate the problem”.”

I just found some of the wording in that article to be funny as an official PR letter from a company, saying that their angry that other companies are installing Growl without the users’ permission. Don’t they have some say in the matter?

FYI, Adobe CS5 also installs something called Akamai NetSession. Essentially, it’s a P2P client, that lets Adobe leverage your computer and your net bandwidth to deliver their software quickly when someone downloads an Adobe demo or other Adobe downloadable files. It saves them $ on file servers, by sneaking their customers into unwittingly sharing their own resources. I believe NetSession is listed in the EULA, but I’m not sure about Growl. Either way, we all know no one actually reads EULAs besides attorneys.

[Brad Bussé]

JOanne, glad I could help. With transferring footage that was filmed as interlaced, the best conversion you can hope for is one which will have some loss of resolution, but will minimize the interlacing which shows up as horizontal offset lines.

I haven’t heard of the deinterlacing application that you mentioned, but I’m glad that you found something that works better than the standard approaches in FCP. I know there are a couple of other options out there too, but I can’t remember which developers. Check out Red Giant, ReVisionFX, and The Foundry. I think 2 out of those 3 offer some of the better software approaches to deinterlacing footage for progressive workflows.

[Brad Bussé]

Well I fixed it just by slightly altering a couple of the attributes for the Particle World. That was annoying, but whatever works I guess.

[Brad Bussé]

JOanne, that sounds like a bear of a project. Dealing with interlaced footage that has been converted improperly can be a pain to work with. What is the HDV down-converted to, DV? Was all of the footage shot as interlaced or progressive? If progressive, you can set your timeline and the clips themselves (right click the field dominance attribute in the bin) all to progressive. Again, even if the HDV footage was shot as progressive, it could have issues to contend with if it wasn’t converted properly.

Also, read the section of this article which talks about setting the canvas to 100% to see both fields, in case you’re not using a studio monitor:
https://www.kenstone.net/fcp_homepage/motion_text_in_fcp_spencer.html

The compression artifact blocks in the reds is a weakness of DV and DVCPROHD (I’m not sure about HDV, but HDV has a higher compression rate to begin with).

[Brad Bussé]

Okay, so it’s dynamically scalable by the OS. So, if you’re OS would normally want to consume 230 GB of drive space for the virtual RAM, how much would it slow the system down in normal operation to limit the virtual RAM to 1/3 to 1/2 of that optimum size?

[Brad Bussé]

Is that offer directly from Adobe? If so, do you have a link? Also, does Adobe have NGO pricing for the Production or Master Suite?

Yes, it’s definitely worth the $, but you’ll need to invest the time as well to learn the workflow. Things like cropping an image are handled differently than FCP or Photoshop, as is nesting (which is pre-composing in AE), there’s no grouping like in Photoshop–you have to precomp, but then you have to make sure that the pre-comps have a high enough resolution to not get cropped. Hmm, I just realized that you could use pre-comping as an alternative method for cropping, but it’s not preferred since you’d lose a lot of control. Anyhow, it definitely requires some time and effort to learn, but it’s well worth it.

[Brad Bussé]

Gotta love that patronizing photo taken, what, 25 years after women had already dominated the cutting room.

[Brad Bussé]

I switched from CCC to SuperDuper a couple of years back. One word of caution; after cloning, it’s worth verifying the sizes of the original and clone drive. I cloned a FCP media drive last year, and found that the clone size was quite a bit smaller. I compared folder sizes until I found out that one very large source video file did not copy over (it can’t even copy over when dragging via Finder, to be fair), but I wish that SuperDuper had alerted me to the fact that a file couldn’t copy instead of just saying that the process was complete with no indication.

There are some differences. I can’t remember what exactly, but the Mac tech. at my last job recommended the change as there were some very specific reasons why SuperDuper was a better match for our needs. Come to think of it, I believe it was specific to the fact that we needed something which could handle automating the backup of a 5.7 TB XRAID array to a network folder, by breaking the backup into modular chunks of folders for different nights of the week.

[Brad Bussé]

the CCC site says the latest update is ready for Lion. I switched to SuperDuper a couple of years back. One word of caution; after cloning, it’s worth verifying the sizes of the original and clone drive. I cloned a media drive last year, and found that the clone size was quite a bit smaller. I compared folder sizes until I found out that one very large source video file did not copy over (it can’t even copy over when dragging via Finder, to be fair), but I wish that SuperDuper had alerted me to the fact that a file couldn’t copy instead of just saying that the process was complete with no indication.