Dennis Radeke
Forum Replies Created
-
[Alex Frizzell] “When I try to playback the files even with all effects turned off my computer will not do it.”
You should know that you should bring down your playback quality in the source and program monitors to something like 1/4 instead of ‘full’ which it might be on. Then at least your playback experience should be fine.
If you don’t know what I’m talking about, look on the bottom right side of either the Source or Program window and you should see something that says “full”, “1/2”, “1/4”, etc. If it is full or half, then bring it down to 1/4 and it should help your playback experience. What this does is instead of trying to playback 4k, it reads every 4th line and essentially gives you 1k playback which is visually terrific – especially if you’re publishing out to YouTube.
Also, while I applaud you not giving Premiere Pro all of your RAM, I think you’ve given it a tad too little. As a rule of thumb, you should give Adobe applications 50-60% of available system RAM. In your case, I would raise it to 16 or maybe 18GB and see how you do.
Hope this helps,
Dennis – Adobe guy -
What Nils said…
Dennis – Adobe guy
-
Running extremely hot should be a big concern, do get it checked before you do a lot of other tests.
Make sure you’re installing an NVIDIA driver that includes CUDA which should help you a lot.
If it’s not hardware and not NVIDIA drivers, then try trashing your Premiere Pro preferences.
Good luck,
Dennis – Adobe guy -
Excellent commentary and points as always.
-
Thanks for the clarification Tim. It has been purported as fact for as long as you state the thing to have been. I was at an Avid reseller at the time this happened and it was told to us as fact via Avid channels. Regardless, its good to get the facts from someone who was there at the time.
-
[Mitch Ives] “what Adobe did to us Mac users when they were in their “petulant child” phase was far worse than anything Apple has ever tried.”
Of course, everyone is entitled to their opinion. I will just try to lay out the facts and counterpoints if you find them informative or useful.
Avid went PC only for a time based in part on what Apple was doing (going from 6 to 3 slot Macs and I believe system 9 to the first OS X).
Apple has never been cross platform so if we were to turn this on its head…
In addition, I’m sure we could all go back to June 21, 2011 and see the threads of the first couple of weeks and see what the actual comments were at the time. Even to this day in fact. Does that make them a petulant child? I think not!
More to the point, lets talk about why Adobe made this change.
As for Adobe, we are talking about the fact that Premiere Pro wasn’t cross platform for a time and was only available for the PC. This is true, but is not representative of products such as Photoshop and After Effects which at the time were (and some would argue still are) the more important products (especially to FCP and Avid users). They were cross platform for the entire time and remain so to this day. Whether Apple was up or down, we have been mostly cross platform on nearly all products. Why then did Premiere Pro go PC only for a time?
The engineering effort at the time of moving from Premiere to Premiere Pro (different product, different code base, different architecture) was such that we had to pause our initial effort of bringing the product to both platforms. It actually was a fairly late decision from what I heard. At the time also, FCP was starting to ascend and our market performance was stronger on the PC side at the time. Maybe not decisions that you agree by but certainly rational ones regardless of opinions.
Adobe didn’t ‘come to our senses’ so much as we wanted to get back to a true cross platform integrated software suite which saw its first fruition come at CS3. There we were able to see a complete suite of applications centered around the NLE as the central hub of a video workflow.
Hopefully, this clears up any misunderstanding for the folks on the forum. Clearly, all software makers have made their faux pas’ but in nearly all cases, they change directions and corrected course based on market demand. We’ve seen this true in Adobe, Apple and Avid’s cases.
Dennis – Adobe guy
-
[Scott Witthaus] “Doing it this way, I still have to drill down through the folder structure to get to the media I want to use, correct?”
Not normally. Media Browser is designed specifically for file-based cameras so that you can cut through the folder structure and express just the video essence that you care about.
In the image below, you can see what camera based formats Media Browser natively recognizes as well as how to turn ‘off’ this capability and folder dive if the need arises.
By selecting “file directory” (off by default) it allows you to see the folder structure. In this case, this is RED media. Look at the difference when I have RED selected.
It has revealed just the video media and none of the other file types that might be in the folder. If you import RED media, it also brings over any RMD data for color and allows you to access it in the source settings of RED clips.
Also notice on the left hand side of either image. You’ll see that I’ve got local drives (which can include network mounted volumes) and above it Favorites. The favorites option is to have folders of media you hit immediately at your finger tips to prevent diving down folders. To make a folder a favorite, right click on the folder you want and “Add to Favorites”
Hope this helps,
Dennis -
Hi Scott,
I appreciate your passion for FCPX. In an effort to help you loathe Premiere Pro less I would just point out a few things.
crowded – you can remove or move any of the panels. They are all ‘dockable’ and if you don’t need them, simply close them and it will automatically be saved as a part of your workspace
dim – You can adjust the brightness of the interface. Most UI’s including FCPX are dark to help the user focus on the media itself, but there are controls to help adjust to your personal preference.
media import – You definitely should use the Media Browser panel if you’re not already. Dock your favorite or current Media directories as favorites. If you’re still using cmd+I to import media into Premiere Pro, then I can completely understand your frustration (with any NLE that does that).
title tool – The internal title tool is extremely powerful but the details and the UI make it needlessly complicated. You can check out Tim Kolb’s excellent presets via s4t but also pick up some tutorials on how to leverage this more effectively. That said, I think we acknowledge that we need to do some work on this tool in the future to make it more accessible and reactive to the user in the future. I’d also point out that you can use Photoshop as an excellent title tool if you prefer (file>new>new photoshop file)Cheers,
Dennis – Adobe guy -
[Oliver Peters] ”
I have yet to see a developer like a MAM company create a dockable or floating panel for their tool that works right inside FCP X as a window into their application. Examples? I’m not talking about plug-ins. That’s certainly possible, such as with Color Finale. Not the same thing at all.”Jumping in mid-conversation here…
Dockable panels (internally we call them Content Panels) are a core part of Adobe’s open architecture strategy. I would guess we have at least a dozen panel integrations with MAMs alone (probably more) and over 50 in total with various companies. You can even check out Pond5 Adobe Plugin to see how easily they can work with things like stock footage companies.
I would point to this as one of the key reasons we have made serious inroads into broadcast, sports, etc. over the last few years. It’s not just about the editor itself per se, but about connecting to the larger workflow within the facility. The Content panel by the way is HTML5 so easy to develop.
HTH,
Dennis – relaxing Adobe guy after NAB… -
Always salient points and we love to debate (in this forum especially) but I will definitely take the under.
