[Phil Incorvia]

Helps a lot! Thanks for your contextual response – very cool.

I’m mostly working with HD-DSLR stuff right now, and am a bit obsessed with babying the footage as much as possible so that I can pull it (mostly in Color) in different directions when I need to.

I was trying to hone in on the suggestion that your post above made that there are reasons to go ProRes 4×4 with heavy effects work. So far, vanilla ProRes has left me fairly happy given the compressed state of the camera original footage. Sounds like there isn’t a lot to be gained with the DSLRs, but keeping HQ and 4×4 in mind for RED and EX1 footage might be smart. Just always looking for that last bit-o-quality or latitude in grading to hang on to!

Setup:
2×2.8GHz Octocore
16GB RAM
ATI Radeon 4870 graphics card

FCS 3 – all up to date
OS 10.6.2

[Phil Incorvia]

[gary adcock] “Using the HQ codec only offers advantages if you are planning on doing heavy effects or corrections within the ProRes codec or the FCS3 suite, and if you are you should be working in the lossless 4444 version, You gain nothing going to HQ if the compositing is being done outside of the FCP/ Color workflow, nothing at all. “

Hey Gary. I’ve read several times that it often makes sense to stay with regular ProRes and had that experience with all the HD footage I’ve worked with. Your statement above suggests that there is some advantage if the footage will be experiencing ‘heavy’ manipulation. Could you give some examples of what ‘heavy’ has meant in your experience? In other words, what post production work/workflow seems to trip the need to move into the 4444 version to keep highest quality?

Thanks!
Phil

Setup:
2×2.8GHz Octocore
16GB RAM
ATI Radeon 4870 graphics card

FCS 3 – all up to date
OS 10.6.2

[Phil Incorvia]

Thanks for your prompt answers and wisdom! Walter, you pretty much confirmed my plan of attack, including the lower and hourly rate.

Take care!

Setup:
2×2.8GHz Octocore
16GB RAM
ATI Radeon 4870 graphics card

FCS 3 – all up to date
OS 10.6.2

[Phil Incorvia]

Hey Walter,

I’ve never been able to use virtual clusters direct from FCP (have to make a reference movie for Compressor) due to the way FCS runs its licensing – looks like two machines w/same serial #,etc. Is this a possible cause for the hangup? One test might be to try opening any other FCS app, like Motion, and seeing if that hang it, also.

[Phil Incorvia]

Okay, I *think* I get it…

Set up a virtual host for “somesite.com” with a port (say 8000). Would that look like this in my
httpd.conf file?

NameVirtualHost *:8000

DocumentRoot /Volumes/mydrive/mydocs/somesite.com
ServerName somesite.com

If that’s right, to access the site, do I just type in the server’s address and the proper port number to get to the site?

If all this is what you meant, I think I get it. I was looking for a way to not have to remember port numbers, which is why I’ve gone with the .dev suffix for my same-machine test sites.

Thanks, Curts. You’re always incredibly helpful!

Phil

[Phil Incorvia]

Thanks Jeremy. That’s actually the way things are. I’m quite confused. I actually dragged some old plugins from a non-universal version into the folder and they work. I’d still like to know how things are working and why. But that’s just a general thing 🙂

Phil

[Phil Incorvia]

[Phil Incorvia]

I did – it is set at 100%, the way it should be.

I read somewhere that when you engage borderless printing on an Epson printer, it blows the image up to make sure there is no white border on your paper. Can anyone confirm this awful feature? Is there a way to turn it off?

Thanks!
Phil

[Phil Incorvia]

I can’t tell you how much I appreciate your time and knowledge!

I think I’m closer, but still not getting something.

I’ve zipped up the code so you can see it:
Here’s the code!

So here’s my thinking using the variables in place in this script…

The page creates $imnum number of images, each with pulldowns to select quantities of 5×7, 8×10, 10×15 and 15×18 sized prints.

I would like the returned value for the first image’s (image 1) 5×7 quantity to be a variable called $5x7_1, the second image’s to be called $5x7_2, etc.

Currently, I’m using a for loop with the $rowmaker variable controlling the loop. This $rowmaker variable can also be used to tack on the appropriate _1, _2, etc end to the print size variables, but I can’t get the script to read it as $5x7_1 when I use $5x7_$rowmaker. I think I tried using the {} in all combinations, but it still won’t work.

Ideally, the script would just use $_POST[‘5x7_$rowmaker’] to read these values, but I don’t even know if you can get it to read a variable in the $_POST context.

I’m trying to make the page values sticky – when the user updates the cart, the page reloads. It isn’t until they checkout that they move on to a new page.

Again – thank you so much for taking any time at all with this!

Phil

[Phil Incorvia]

https://www.seebigbelly.com/gallerybeta2.php