John-michael Seng-wheeler
Forum Replies Created
-
How about this: (note, this was tested on a single computer and on CS5.5. Your Mileage on CS5 and multiple computers may vary. )
Create a new PP project. Name the project something that will eventually be a bin, lets say “Scene 1”.
Click cancel on the New Sequence settings window. You don’t want this project to contain a sequence.Import your footage, and organize it into bins, lets say, a couple of shots into bin Scene 1A, a few shots into bin “Scene 1B” ect…
Save the project.
Now, open your Master Project. This is the project you’re doing the editing in.
Point to File> Import, and select the project file with the bins in it.
You will now have a new bin in your project called “scene 1” and bins inside that bin called Scene 1A, 1B, ect and your footage in those bins.
You can repeat this method with as small or as large chucks as you want… You could do it on a Scene by scene basis, or a shot by shot basis, or even take by take. You just need your Assistant make a new project, and that will become a bin.
Does this work for you?
-
Well, it’s probably related. I think the issue behind both your issue and the one I linked to is the way quicktime saves timecode and Premiere’s rather incomplete support for it. I’ll be eager to hear whether your problem goes away with CS6, seeing as this incident with Jeffery Harrel has brought rather a spotlight down on Premiere’s rather bad Quicktime support.
-
Another possibility is that the Master is set to 16 Channel.
-
I’ll bet this is it: https://blogs.adobe.com/premiereprotraining/2012/03/a-couple-of-timecode-issues.html
-
What happens when you use Premiere now?
-
I just had an idea.
Since you have FCP, stick this messed up file in a matching timeline, set the timeline start timecode to match the first frame of the file (probably you should use the number Premiere gives you, since I’m pretty sure that’s the “correct” one. I can explain why) and render out same as source! That should generate a new file with no generation loss and a fixed timecode.
If this was anything other then a ProRes file it wouldn’t work… at least without generation loss, Lucky!
-
you can always copy and paste into the new timeline…
-
You should probably try an older, known good version of the drivers then.
This happened to me, (not on such a grand scale) and I had to go back a few driver versions.
-
A GTX480. I’m waiting for Nvidia’s next GPU architecture, then I’ll upgrade. (I guess if the naming convention continues that’d be the GTX680)
How much faster it would be depends entirely on the kind of editing you’re doing.
As far as I know, the CPU is still responsible for encoding, so straight renders will be no faster. If you apply lots of effects and compositing you might see quite an increase.
The point is that only in places where the GPU is currently the limiting factor will a new GPU make any difference.
-
[Keith Moreau] “Should I take out my Quadro 4000 and put in a GTX 580?”
Maybe, Maybe not.
While the GTX580 is technically faster, if the Quadro 4000 is giving you realtime playback then the performance increase in some situations may not be worth the cost.
If you were deciding which one to buy, the GTX is a far better choice, since it’s faster and cheeper.
Since you already own the Quadro, however, unless you’re pushing the limits of the power of the quadro, the upgrade probably isn’t worth the price. (unless, that is, you can sell the Quadro…)
If you do decide to buy the GTX, you should buy from a company that doesn’t charge a restocking fee for returns. Then, if you don’t see enough of a performance increase, you can send it back.