John-michael Seng-wheeler
Forum Replies Created
-
[Karim Daire] “If Premiere has this big minus, that is a huge impact and I wonder why i never read about that.”
You’ve never read it from all the people who don’t consider it a minus. If you would like to get the word out, you’re welcome to. I feel like there should be a forum just for FCP to PP switchers.
[Karim Daire] “I mean exactly the final part is where deadlines and last minute corrections tend to get annoying.”
I deal with this by rendering an uncompressed master of my video, and I insert any changes into the master and render again. On my computer, a powerhouse PC, renders are offen faster then real time, possibly quite a bit faster.
Don’t forget that your computer is providing you the low end of what Premiere can do. CS6 can take advantage of the GPU in your laptop, so I’d download a trial and give that a spin. You may find things a little or even a lot faster. (it depends on the kinda editing you’re doing. The GPU doesn’t do any encoding or decoding. Also, you can really bog down a render if it has non GPU affects in it.)
However, if you really want to fly you need a tower.
[Karim Daire] “I heard that basically its a waste to use Adobe software (AE and Premiere) on a MAC. Is it true that performance is better on Windows machines?”
I wouldn’t call it a waste, but yes, performance is indeed better on windows. Couple of reasons for that:
Better and higher end hardware selection,
Better access to the GPU by programs, especially OpenGL (which is used by AE. This is why games run better on windows.)
And possibly, although good coders could work around this, the fact that Premiere took a hiatus from OSX.
-
“Mercury Playback Engine GPU Acceleration” Is what you want. That’s what I meant by “MPE hardware mode” I just couldn’t remember what the menu called it.
Anyway, Point is, you are now using the GPU. Before you edited the text file, “Mercury Playback Engine GPU Acceleration” would have been grayed out and software only would have been your only option.
-
just a note about the XDCAM .MOVs: The XDCAM quicktime codecs are Mac only, (they’re installed by FCP,) so if you ever need to switch to Windows use them on windows you’ll have to unwrap them.
-
Sounds reasonable, but you should also try CS6 which may improve things somewhat as well.
Download the trial and give it a spin!
-
The idea is that, instead of converting all your footage to ProRes at the beginning of the project, then editing it and stitching it all together, PP edits the footage natively, and then renders it all to your deliverable format at the end.
It’s actually faster in total time spent, since you don’t have to convert any footage that you don’t ultimately use.
And you should avoid using the “use previews” option when rendering unless your previews are set to uncompressed. Since PP can’t “stitch things together” when you select “use previews” you’re having premiere use the preview files as a source to render from, which causes you to incur an additional generation loss.
In short, Premiere just works differently. (not better or worse, just differently.)
As for the blue bug, I’ve run into footage turning blue myself, though no alphas were involved. I’ve found that when things go wonky when rendering I switch programs. If I’ve been rendering in Adobe Media Encoder, I switch to exporting directly inside Premiere and vice versa. The two rendering engines are different code, and so far every bug I’ve come across in one hasn’t been present in the other.
I’ve no idea if it’ll work for you, (and you said you managed to work around the bug anyway) but if you’re curious you might try rendering in what ever program you weren’t using before.
-
What Adobe did here is actually rather smart. There are just too many different Nvidia cards out there for Adobe to test them all, (when you add in the mobile cards which can have different specs depending on the manufacturer, there’s at least 100 different cards, if not more.) So they rigorously test a few and officially support just those. But since most Nvidia cards do work, they provide a very easy way to hack the program and make it work, without having to officially support any of those cards which would be near on impossible.
-
[Bobby Cullipher] “NVIDIA Geforce GT555M 3GB (cannot believe this is not on Adobes list)”
Have you tried editing the text file? Might work.
In case you need it, here’s a how to:
(note these instructions are for CS5.5. They also apply to CS5 and probably to CS6. You didn’t mention what version of Premiere you’re using, so I’m assuming 5.5.)
0) shutdown PP
1) right click on notepad in the start menu and select “run as administrator” (If you don’t do this you will not have the privileges to save the text file after you edit it.)
2) point to File>Open and navigate to the Premiere Pro application folder. (usually “C:Program FilesAdobePremiere Pro CS5.5”)
3) Open cuda_supported_cards.txt which you will find there.
4) on a new line, add “GeForce GT 555M”, which is the name of your card.
5) Save the file. (if you didn’t run notepad as administrator it will complain that it doesn’t have the permissions required to save.
6) start PP again and go to the project setting panal and enable MPE hardware mode.
note: if it’s still grayed out, ether you have the name of your GPU wrong, or PP is smart enough to know it won’t work. The former is far more likely.
-
Cody, If you just combine the contents folders into one everything will import properly.
On windows, this is as simple as dropping one CONTENTS folder into the same folder that the other one is in.
On Mac it’s a matter of coping all the video files into the other video folder and the same with the audio and clip and image folders.
Then it’ll all import correctly.
-
I have this problem on windows. The fix I’ve found is a little odd, but this is what I do.
1) Import all the audio files. (they all show as 00:00:00:00000.)
2) select all the files, right click, select modify>Timecode, enter something ramdom, hit ok.
3) Go back into modify>Timecode again, and hit the “Revert” button.
Sometimes that fixes it but if not, the last step:
4) Minimize Premiere and click any other program or the desktop, Then bring Premiere back. (this causes Premiere to reload all the files because it’s checking to see if you made any changes to any of them.)
-
So I just hit a similar bug, and I think I might have found the problem.
The files you were having trouble with weren’t created in MPEG Streemcilp were they? I’m having similar timecode reading issues with ProRes from MPEG Streemcilp in Premiere, and I discovered that Premiere thinks that the files are Non-Drop Frame, when the original files (HDV captured in FCP) were Drop-Frame and MPEG Streemcilp wasn’t told to change the frame rate.
I don’t know if the problem is MPEG Streemcilp, Quicktime, or Premiere, but it’s sure annoying.