Dennis Radeke
Forum Replies Created
-
[Daniel Frome] “what would finally complete construction of this video death star?”
Nothing! Customer requirements will always continue to come and therefore there will always be one more laser cannon to build, another Tie Fighter.. wait a second, I thought we’re the rebel alliance – I want to be the good guys!!!
Seriously, we will always be innovating to try and satisfy as many potential customers as we can.
Dennis – Adobe guy (and secret spy for the Rebel Alliance!)
-
For the future, you might use this instead or at least have it in your troubleshooting toolbox: Adobe Cleaner Tool
Dennis – Adobe guy
-
I have the 7D too and it’s a wonderful camera. You need to know about it’s limitations (and the limitations of a given codec).
I don’t use my 7D a lot for video but when I do, I try to never be above 320 iso and really aim to 160. If you just can’t do that, then consider some tactfully placed lights to help light the scene. If that isn’t possible, try shooting a bit darker and see if you can bring back the color in post whereby you’ll preserve the (no)grain in the blacks.
HTH
-
Unfortunately Jana, this is related to the plugin itself as far as I can determine. In fairness, some of the moves and animations are relatively complex so I can understand how it would take a while to render out. However, are you able to preview the effect without preview rendering? That is always the goal of Premiere Pro. If you’re coming from FCP and you think that anything red in the timeline must be previewed rendered, then you should look for some tutorials that cover your preview options like full/half/quarter, etc.
Assuming that you are doing these things correctly, then the issue still lies with either your system resources or the plugin itself. We have made our GPU hardware acceleration available to 3rd party plugins, but not all have embraced it as of yet. You should reach out to FX Factory and inquire.
HTH,
Dennis – Adobe guy -
[Bret Williams] ” Hey Dennis! Yeah I did meet you briefly at both the Cutters meetings.”
Well, lets make sure you introduce yourself next time so I can put the face with the forum!
[Bret Williams] “Adobe, subscription model aside, is making great strides. I wish I could support it more. The upside for myself, and likely many others is that Motion is getting another look from us long time AE veterans. I still prefer precomposing over groups and the render que over Motion’s more basic exporting but the real time engine of Motion and the rigging and publishing are just light years ahead of AE.”
Well as I said, there are good things about every program. However, at the risk of coming off a tad haughty (and I don’t mean to), I think the amount of possibility that After Effects offers, the 3rd party ecosystem, the absolutely infinite amount of tutorials, its 20+ year pedigree, its versatility at both motion graphics and visual effects, etc. put it just a tiny bit in front of Motion. 😉
[Bret Williams] “Well, as a Mac user you probably understand I disagree somewhat.”
Well, I was speaking specifically about Premiere Pro performance in my example and not After Effects, but as a rule, Adobe absolutely, positively never wants to make the OS (Mac or PC) a part of your decision. We strive to have performance parity across both platforms at all times. And when we have comparable on both Mac and PC we do pretty well IMO.
[Bret Williams] “As I mentioned above, AE is still stuck in render cache land”
There are a lot of reasons for why this is but I will start with the most important part… Yes, we agree. And we’re working very hard to make that better. In the past, if you asked a user which would he/she rather have nifty feature ABC or make it faster, most people have said in the past, “give me the feature.”
Another way to I describe After Effects is thusly: You can take anything into it, do anything to it and spit out anything you want. Yes, somewhat of an exaggeration but you get the idea. We support almost anything and can do almost anything. With that, comes a certain amount of computational intensity when it comes to previewing frames! On top of that, we strive to give many options in terms of balancing accuracy/visual quality vs. speed of previewing as I’m sure you’re already familiar with.
[Bret Williams] “CS3 or 4 when Adobe brought it back to Mac, and because it didn’t support whatever graphics card I had it’s 64bitness still didn’t beat the RT I could get with 7 and later X.”
Comparing the real-time capabilities of CS3 to where we are now is like comparing a broken bicycle to a Ferrari. I know you’re very happy with FCP X and that’s great, but if and when you have an opportunity, give the latest version of Premiere Pro a spin on a good Mac and tell me what you think.
Thanks for the conversation,
Dennis – Adobe guy -
Hi Jamie,
I will forward this to a few folks and see if I can get them to jump in. As far as physical limits to the number of assets, that is generally tied to RAM. You will hear more details about long form features like Gone Girl in the coming months but suffice it to say, there are a lot of assets…
Each clip has a bit of memory used to point to the location of the file on the storage (that’s my understanding anyway.) Eventually, you can gobble up a lot of your RAM if you have lots of assets.
If it is possible for you to try to put in 64GB of RAM, see if that addresses your problem.
This also might be related to your issue: Memory Preferences
Like I said, I will email this thread to a few folks to see if I can get some help.
Cheers,
Dennis – Adobe guy -
[Bret Williams] “I’m literally blown away at the Atlanta Cutters group. They literally look at X users as sub class. The barely even acknowledge it’s existence. But the connection between Motion and FCP X should be a huge discussion point. Instead it’s somewhat predictable. When the Adobe guys were there showing off CC 2014 (hey adobe I thought there weren’t going to be versions anymore?) everyone oohed and aaaahed over the ability to edit AE text from within premiere. A feature FCP has had for what, a decade and WITH drop zones? I guess if we could have a demonstration on publishing it might blow their minds. And if they saw rigging in action there’s no telling.”
Hi ya Bret,
First, I hope you came up and introduced yourself as I was there at the meeting and would have appreciated meeting you in person. Perhaps we did and its my senile memory playing tricks on me. Regardless, let me address your points.
Version numbers: Overall, it’s still Creative Cloud, but you need to be able to distinguish a release from another so it makes sense. I think it makes sense and hope it doesn’t get you too upset.
Live Text: Let me give acknowledgement that FCP/Motion had this functionality before us. Clearly having the ability to edit the text without going into a tool like After Effects isn’t unique and something Adobe has wanted to do for some time and will continue to develop.
That said, there are ALWAYS going to be features or workflows that some programs have before others. That is true for all NLEs. What I like about Adobe is that we try to admit when it should be, ‘yeah, we should have this a while ago, but other things took priority.’ Certainly, that’s what I communicate when I talk with customers and if you had spoken with me, I hope I would have said that.
A couple of examples where Premiere Pro led the way would be when it went 64-bit native several years before all but Sony Vegas. We were also the first to truly tap into the GPU and remain the leader in that regard. I could go on (and on!) but you get the idea.
As for the focus of user groups, they stand or fall based on the focus of the community and their needs.
Thanks for the feedback,
Dennis – Adobe guy -
Hi there Nathaniel.
QT is a container that can contain many things including H.264 whereas H.264 itself is a video codec.
In the Premiere Pro export dialog there are several things to look at. First is the format. There you can choose H.264 or QT (or MPEG4). From there, you need to choose a preset or look below and build your own based on the video, audio, multiplexor, etc tabs.
If your source material is HD (e.g 1080) and you choose H.264 as a format, then probably the best thing to try for easy results is the “Match Source – high bit rate” preset which will match the frame size of your original source material and give it a high bit rate.
HTH,
Dennis – Adobe guy -
[Brett Sherman] “I will take a look at Prelude. Is it on CS6?”
Unfortunately, the file renaming feature is a part of Creative Cloud, but Prelude is a part of CS6.
Metadata in Adobe applications is based on XMP. File name and basic meetadata that are intrinsic to the file such as frame size, frame rate, etc. will come across, but other metadata (such as temporal metadata from Prelude) I don’t think would come across.
-
Well, I like Paul’s suggestion best (‘cuz it uses Premiere Pro!) but Richard is right on…
You can ingest (transcode or not depending on your preference) and do a batch rename that is custom and saved as a preset directly in Prelude. It’s pretty easy to set up. The only nagging thing for me personally is that it doesn’t allow spaces in the names, so I am in the habit of using an ‘_’ in place of a space.
Bridge is superfluous in this case but a great tool for batch renaming.
HTH – Dennis