[Greg Sage]

I’ve never used that plug, but generally speaking, it sounds similar to the difference between the “hue” and “color” overlay modes.

If you apply a layer style to it, for instance (Layer/Layer Styles) with a color overlay, then choose the color you want in the color picker, you’ll notice if you set the overlay mode to “hue”, it will only change the color but leave the saturation intact. If you change to “color”, it will add more specific color even though the saturation may have been very low (gray, white, etc)

You’ll notice the same thing if you use the hue and saturation effect. The hue alone won’t be changing it, but if you check the “colorize” box, you’ll start to see it narrowing in on the chosen hue vs the full broad spectrum light (white).

[Greg Sage]

Gotcha. I had a hunch. That’s what’s kept me from pulling the trigger on the faster pure pcie solution. 500 gigger at SATA III rates via pci-e it is. Should be night and day from what I’ve gathered vs my current 7200 rpm platters.

I ordered more ram to kick it up to 32Gb, so between the two, I should be putting a good deal of my lag issues behind me. Nailing down a gtx 570 or 680 (probably 570) is up next. What a difference a week makes.

thx.

[Greg Sage]

Well, it really comes down to capacity vs speed… at least as the budget works it’s way in.

So long as the speed is fine either way… If my total project files top out at 150Gb or so (size of the project folder), am I likely to need anything larger than a 256Gb cache drive? That’s the part I’m less sure about… how much the size of the cache drive matters.

[Greg Sage]

Yes, cache.

I ran across that thread when researching, but it didn’t appear to be addressing what I’m seeing.

The issue in that thread was “…the warning kicks in if the space that you’re allotting for the disk cache is more than 80% of your free space.”

… but in my case, I’ve got a 256Gb drive with (at first) nothing but system software and Adobe cc on it. Even then, and even when I stepped down from 100Gb down to 30Gb, I still got the warning. For that warning to be kicking in due to the 80% rule would mean that a fresh install of mavericks and Adobe cc ate up more than 200Gb.

I can’t see how I could be near 80% of free space with those figures, but I’ll dig into the stats tomorrow to make sure.

[Greg Sage]

My install said it went correctly. It shows up under Windows… but nothing at all happens. I’ve watched all the tutorials I can find, and they all just show it launching pluraleyes automatically at that point.

[Greg Sage]

Absolutely. This has been a niggling issue for some time, and it looks like the direction I’m going, it’s going to become increasingly important to get right as I’m relying on hopping back and forth to line up markers hundreds of times over.

Email sent.

[Greg Sage]

My first thought was to go with Dropbox, but I thought it might be too slow as the internet can be dodgy around here.

If I understand… relative path means regardless of which drive… so long as everything from the project down, right?

Sounds like you’ve ironed out exactly the sort of issues I need straightened, so at which stage are you organizing? Prior to importing into AE in the finder? Doing all organizing prior to beginning AE project? After the fact by collecting to force finder to match organizing done in AE?

Just looking for a formula to stick with. thx

[Greg Sage]

I’ll look for that in prefs. It’s a new install since I just moved over to cc, so I haven’t changed anything from default yet.

As for clicking through main comp… I’d fill up the tabs with garbage constantly as I’m flipping back and forth between subcomps stacked 10 or more deep in many cases. There must be some way around that bit… I’m hoping…

Basically, I have a subcomp for footage, the footage has been marked prior to AE, then I need to jump back and forth between this footage comp, back up 10 levels or so to main comp, back down to another footage comp, back up, etc. I try to do as much as possible in the main comp, but it’s not always workable to avoid having to go out to get something done.

[Greg Sage]

OK, that makes sense.

So where would pluraleyes fit into this workflow. If I have scratch audio for each clip, some music for a segment in the middle (which I imported into AE with markers in order to time AE events to those markers), and some intro and outro music…

Should I jsut wait to do pluraleyes until after I’m done and rendered out of ae, then use it to sync all the bits (dialog and music) to the corresponding bits in AE, then export out a PR file from AE.

So, if I’m understanding…

1 load raw clips into PR. Toss the bad ones, mark the good ones. Save.

2 Import the PR project from within AE, and drop in the clips and scooch as necessary.

3 Render out a/v from AE uncompressed.

4 Drop AE render, music clips, and dialog good audio into Plural eyes and sync all (used) clips and audio to their AE scratch counterparts.

5 Export to PR (I haven’t done this before. Tried twice, but something went wrong, so I’ve been doing just mated renders out.

6 Send audio clips out from PR to AU for cleanup as necessary. (should I be doing the whole PR sequence in AU here in one swing?

7 Audio back into PR (haven’t gotten this working yet)

8 Render out of PR (ideally uncompressed then into Media Encoder, but with our schedule, probably try compressing to delivery format at this point.)

Does that sound right? I’ve done about 2/3 of this stuff before, but there are a few unknowns for me. Thx for the help.

[Greg Sage]

I’ve got C4d, I just don’t use it much. I’m thinking more about what I might want to do but haven’t done much of yet… like dig into Element 3d which looks cool, but I just haven’t had time yet. I know I want to dig deeper into the Pixel Bender Accelerator which runs on GPU. Not sure if that could benefit from Cuda or not. It’s not 3d, so maybe not.

I think I’m going to have to run a dual boot for a while as I have a few programs where one bit or another can’t upgrade the OS for various reasons. This is why I want the card flashed… to be able to select boot drive (and any troubleshooting that may arise).

I am using Mandelbulb 3d rather heavily, but I’m not sure if it can benefit from cuda or not. It’s all about ray tracing, but between it being ported over from PC code, etc… I have no idea if or how to optimize it on this system.

Either way, the card’s not my top priority. Got to get the drives sorted.