Dennis Radeke
Forum Replies Created
-
clear cache, trash prefs, restart – all the general stuff and see if that helps. Otherwise, if it’s working on your work system and not on your home we need to look at the system in question to see if there’s something weird going on.
-
Virgil,
Have you tried the CC 7.0.1 update yet? This issue is dependent on Main Concept if I remember this correctly. We may have gotten a new drop that was put into the .01 build. Can you give it a go and let me know?
-
Got some early feedback. Try setting your data rate higher (or really high) and test again.
-
Hi guys,
From the information here, there seems to be several possible issues that may or may not be related. I will point this thread out to the engineers again and see what they come back with.
-
[John Heagy] “True, but blades aren’t know for their GPU power which a render/encode farm could take advantage of.”
I’ve certainly seen and used single and dual rack space blades with Quadro or Tesla cards in them, so they’re definitely out there.
-
[Steve Connor] “Perhaps you can help us – how well will Adobe Apps support Open CL on the AMD cards in it when it comes out? If there is no NVidia and therefore CUDA Option will there be a massive performance benefit from using a PC instead of it?”
We support certain OpenCL chips today with CS6 and I’m confident that you will see more about OpenCL on June 17th. 😉 More info then!
-
Hey Nicholas,
Didn’t read your initial post that way at all. Besides that…What Shane said… 😉
Cheers,
Dennis -
[Andy Field] “I’m consulting with a large federal agency that has over 500 seats of FCP 7 and 6. It integrates with their Dalet server and they broadcast programs around the world. Some are still on FCP 6…some are still cutting SD DV material……”
I think I know said agency and even if I didn’t – the bigger issue for large enterprises (be it gov, edu or broadcast) is that editing is a part of a larger toolset. Because of this, I would say that the integration between other systems (Dalet in this case) and Adobe are the central issue. To this point, Adobe has really been embraced as the successor to Avid and Apple in terms of integration with over 120 vendors showing Adobe at NAB with over 40 with working panels directly inside of Premiere Pro. This level of integration is unique among NLEs and provides a tightness of integration that cannot be found elsewhere to my knowledge.
Its because of this integration capabilities that I think Adobe serves large enterprises including gov agencies well…
Cmd+Tab to switch to another app for the creative process is just so 2007… 😉
Dennis – Adobe guy
-
[Nicholas Zimmerman] “I honestly can’t see any reason to stick with Legacy other than an aversion to change. If you want to edit in FCP7 with a modern UI and 64-bit speed then get Premiere Pro, if you want to have a major speed boost in both tech and editing systems then move to FCPX. If you work in a massive multi-user environment with a lot of others, make the move to Media Composer. “
You are making some assumptions on Premiere Pro that may not be true. You assume that it is merely a 64-bit ‘knock-off’ of FCP7 which it is most definitely not. You assume that you cannot be as fast as FCPX, which is merely an argument that your hammer is better than mine. In the end, it’s the person who wields the hammer that makes the difference and that decision is up to each person to decide for themselves. You also assume that only Media Composer allows a multi-user environment when in fact there are lots of products out there that enable multi-user for multiple NLEs. EditShare, Film Partners and others exist today for Adobe, Avid and Apple. Adobe also has Anywhere coming in just a short while as well: Adobe Anywhere
That said, I will always reiterate that choice is good for everybody as is the competition between multiple vendors for your attention!
Cheers,
Dennis – Adobe guy -
Some interesting and good information, but I would point out a couple of things here…
Saving Project: there is an auto-save that is turned on by default. I’m also a big proponent of using the Media Browser to keep project tidy, but that’s a whole ‘nuther conversation…
Preparing to export: Are you saying you’re having a 1 minute delay before you can export? I’d like to dive into that with the details about the project…
Exporting a clip: Two GIANT points here. You’re not factoring in all of the transcoding you did with FCP7 on the inbound side. This cannot be overestimated in most scenarios. Second, FCP7 has smart rendering on ProRes on output which decreases the export time. We have added that (along with many other codecs) for Premiere Pro CC.
At the end of the day, download a trial (either CS6 today or CC upcoming) and see how it works for you Alison…
Dennis – Adobe guy…