Adobe Community
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
jasonvp
Advocate
jasonvp
Advocate
Activity
‎May 21, 2014
05:37 AM
Jrjl wrote:
I have an imac from mid 2011. So I think maybe I should look into getting a solid state hard drive or more ram instead of the mac mini. Or getting that laptop.
I'm not sure how well that iMac is going to serve you due to the storage limitations of it. If I'm not mistaken, a 2011 iMac is prior to Apple's shift to Thunderbolt. It means that external storage will be limited to USB 2 and/or Firewire, neither of which are any good. With Pr, you generally want several storage volumes (scratch space, media, output, etc). That's much harder to accomplish with the older iMacs. If you can stomach selling the iMac and investing that money into a new Macbook Pro along with an external Thunderbolt 2 RAID array, you'll be much better off. But, that solution isn't cheap...
... View more
‎May 20, 2014
06:16 AM
jrjl wrote:
I am looking to get another computer for video editing. Do you think a Mac Mini with these specs:
You're going to have a rough time with a Mac Mini because it doesn't have a discrete GPU (nVidia/AMD). It relies on the Intel 4K integrated with the CPU. Given that, you'll get absolutely no help from the hardware MPE in Pr. Everything will be software-only, and fairly slow at that. Minis are crap, really; good for small file servers if you can attach a ton of external disk; good for print servers, etc. They're not good for computationally-heavy tasks. Save your sheckles and get a 15" Macbook Pro with a discrete GPU (it means spending some more money). It'll run Pr a lot better than the Mini does.
... View more
‎May 14, 2014
07:31 AM
safehouse909 wrote:
Jason I guess changing my tone can be had to do at times when my clients are not happy with the turn around time.
Flies, honey, etc.
honestly if you could see how basic these last to jobs have been you would be surprised. The post work is very basic. No color correction no hard compositing ,nothing
Did you start these projects in CS6 by chance, and then import them? Do you have the CUDA drivers installed by chance? Those get sneaked in by another piece of software, and they can royally truck things up on the Mac with Premiere.
... View more
‎May 14, 2014
05:51 AM
safehouse909 wrote:
Why is it that everyone at Adobe will say Adobe Premiere CC works great with the new Mac Pros but mine crashes just about every time when I try to render a video using "GPU"?
Perhaps we can figure it out within the community; I'd suggest perhaps changing the tone of your opening statement. I can understand frustration, but subtle sniping at Adobe isn't going to help.
I have called into support at Adobe and had a remote screen session and they to have seen the render crash and LOCK UP the Mac! After an hour or so they just say " we about the problems with the graphic cards and the only work around is to use "Software Only" render settings.
What source footage are you editing? What are you exporting to? What aftermarket plugins are you using?
I have also called in to Mac and have tried to get it worked out. The only software on my Mac that will lock up my Mac is Premiere. A 5000.00 Mac, 2500.00 Pegasus2, and a 50.00 monthly software lease and I can still not get GPU!!! I will posted a video to see if someone has a clue because No one has a clue at Adobe or Mac.
Calling Apple regarding this isn't going to result in much, unfortunately. I wouldn't recommend doing that. Their service and support folks are top notch; literally the best in the industry. This specific issue is with Pr and something in your computing environment, I suspect. In other words: nothing Apple can help with.
... View more
‎May 06, 2014
06:09 AM
2 Upvotes
denniscarrollAV wrote:
After getting everything installed and tweaked I have to say that I am floored by the performance so far.
I upgraded from a 2009 Mac Pro dual Quad 2.66, w/48gb Ram, Quadro 4000m, (3) 10,000rpm drives.
I'm pretty surprised by the performance of the new Mac as well. I got the 8-core with the D700 cards. It replaced a highly modified Mac Pro 5,1 with aftermarket 3.46Ghz 6-core Xeons (x 2) and a GTX570 nVidia card. My standard benchmark is to the export of one of my race track videos. It's 2 1080p AVCHD inputs and a separate sound file (WAV). One camera is PiP'd on top of the other; that same camera is also scaled down 50%, cropped from the bottom by 30%, and then horizontally flipped so it looks like a rear view mirror image. From there, the entire video is scaled to 720p and exported to h.264 MPEG4. My old Mac Pro could do it in real time plus some epsilon. My new on can do it in real time minus some epsilon. The kicker is that it makes no sound, whatsoever, while it's doing it. And it has one less Xeon processor in it. Is it an order of magnitude faster than the last one? No. Is it even twice as fast? Nope. But it's doing more with less, and that's impressive. ETA: I don't know if the OP is still following this thread. For what it's worth: I performed the same benchmark on the latest Final Cut Pro X, since they have a 30-day free trial. The executive summary is: Premiere is still faster for what I do. On my last Mac Pro, the same export would take twice real time with Final Cut Pro X. The main reasons: nVidia GPU that performed poorly in OpenCL, and an older, less-optimized version of FCPX. On the new Mac Pro with the latest FCPX, the export went from twice real time to half real time plus some epsilon. So basically: as fast as Premiere used to be on my old Mac Pro. A huge improvement for FCPX, no question. But the application doesn't want to edit raw AVCHD footage without putting a .MOV wrapper around it first. When your files are gigs and gigs in size, this takes: a while. And it slows the editing process down. And, ultimately, the export process is still slower than the latest Premiere. Given all of that: I'm sticking w/Adobe.
... View more
‎Apr 07, 2014
07:00 AM
2 Upvotes
cc_merchant wrote: Don't you mean "Very Expensive" Take the the fan-boy sniping elsewhere.
... View more
‎Feb 22, 2014
11:11 AM
eschillay wrote: I'm expecting delivery soon of a new Mac Pro, nicely loaded, which I purchased mainly because of all the work I do with video. Did you already place the order with Apple? Based on the "expecting delivery" statement, I'm guessing you did. I'd have chosen a slightly different path, and if you haven't pushed the "Order" button yet, you might consider it... • 3.5GHz 6-core with 12MB of L3 cache • 32GB (4x8GB) of 1866MHz DDR3 ECC • 1TB PCIe-based flash storage • Dual AMD FirePro D700 GPUs with 6GB of GDDR5 VRAM each The built-in SSD is super-fast, but, IMHO, optioning up to the 1TB one is a significant waste of money. The included drive should ideally be used for the operating system and any applications you're using. In all honesty, you probably don't need much more than 40GB or so for that, in total. The smallest SSD is the best bet there; if you're doing a lot of video editing then you know you need more drives anyway. Pick the smallest SSD available, and then add a couple of external multi-drive Thunderbolt chassis. The memory is another point where money can be saved. Swapping RAM in the Mac Pro is ridiculously easy to do, even for the most neophyte of neophytes. Seriously. Buy the Mac with the lowest possible memory configuration, and then add aftermarket RAM to it. Save yourself some more cash.
... View more
‎Jan 02, 2014
05:03 AM
Trilo Byte wrote: According to Adobe's published information, the current versions of Premiere Pro CC and After Effects CC are able to recognize dual GPU's and put them to work, no special customizations or tweaks required. Pr and AME (I have no AE experience) should use the cards without any modifications, but you'll be warned about using an "unsupported card". Delete the opencl_supported_cards.txt files from the Pr and AME installation directories, and you won't get the warnings.
... View more
‎Jan 01, 2014
09:23 PM
chfilm2 wrote: I'm curious for those question as well! I'm planning to get a new mac Pro, but can't decide if the d700 is worth the upgrade over the d500, considering I'm mostly working in Adobe CC Tools. The cost difference between the D700 and D500 is so minimal after spending that much on a decked out Mac Pro that it seems silly to cut corners there. Spend the money, make the text file alterations for OpenCL support, and enjoy. Also, read this.
... View more
‎Jan 01, 2014
09:16 PM
smartcel71 wrote: I don't have the CUDA preference panel in my System preferences. Do I have to install a driver from NVidia? Just deleting the text files in the contents folder of PP made my project playing back realtime again on the new MBPr. If you deleted both text files, you enabled the OpenCL support, but not the CUDA support. Without the CUDA driver from nVidia, it won't work with Premiere and AME, etc.
... View more
‎Dec 30, 2013
08:24 PM
desnosx wrote: my problem is not on Adobe but apple or nvidia cuda won t load Do you have the CUDA preference panel installed in your Systems Preferences? Can you take a screen shot while running that panel and upload it to the forums here? Make sure that the discrete nVidia GPU is actually running and that the system isn't relying on the Iris. This application will allow you to see which GPU is being used, and to force it to the nVidia if necessary.
... View more
‎Dec 30, 2013
01:44 PM
desnosx wrote: ok , but Cuda option is not working Validate that your Macbook Pro has the nVidia GPU, and is not just relying on the Intel Iris. There are 2 15" MBP Retina models available in late '13. One has the nVidia GPU, the other does not. Install the latest CUDA drivers from nVidia, found here. Delete the cuda_supported_cards.txt file found in the Adobe Premiere Pro directory Delete the cuda_supported_cards.txt file found in the Adobe Media Encoder directory (if using CC) Enjoy CUDA acceleration with Premiere Pro and AME.
... View more
‎Dec 20, 2013
05:08 PM
jordanedit wrote: Does Mercury Engine work with the new Mac Pro Dual AMD FirePro D700? A few things are at play here. 1. AMD GPUs are only good for OpenCL, which requires Pr CS6 or greater. 2. If you want to use both GPUs, then you need to be running Pr CC. Anything prior to that will only support using one of the GPUs. 3. As of the latest Pr 7.2, the AMD GPUs on the new Mac Pro are not listed in the proper text file. Pr will still use them, but AME will not. In order to make AME use the cards, you'll need to delete the file or add the GPUs to it (I've always found deleting the file to be easier).
... View more
‎Dec 17, 2013
05:06 AM
Tjeerd Paul Jacobs wrote: All you need to do is Right Click on the Application Premiere or After Effects Yes, you certainly can do all of this. Or, you can just delete the file altogether and it'll just work. It's much easier, and you don't have to chase down the exact model name and number of the GPU to make it work properly.
... View more
‎Nov 17, 2013
06:25 PM
gibsonjsh wrote: So what text files do I delete? I can't help with AE, as I've never used it before. But I'll bet its directory structure is identical to Premiere Pro's, or darn close to it. To get Pr and AME to use the nVidia GPU in your Macbook Pro, look in the directory: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents There are 2 text files in there, opencl_supported_cards.txt and cuda_supported_cards.txt. Remove them both.
... View more
‎Nov 04, 2013
08:22 AM
1 Upvote
Chrisstockwell wrote: Is it worth getting the 15" MacBook Pro with the Nvidia graphics card over the 15" version without for use with both Premiere Pro & After Effects CC? You'll spend a bit more to get the one with the nVidia GPU, but I don't think you'll regret it. Out of the gate, CC isn't likely to natively support the card. But like me, all you have to do is delete the CUDA and OpenCL (if you want) text files from the CC install directory, and it'll instantly recognize the card for use with both APIs. It'll do so without presenting you with a warning that you have to click through, and more importantly, AME will use it as well. [For those unaware: when using a non-supported GPU with CC, you'll get a warning that it's not tested, but you're welcome to use MPE in hardware mode regardless. However, AME will not use the card. In order to get AME to use the card, you have to either edit the text files, or delete them. I prefer the latter, of course.]
... View more
‎Oct 23, 2013
06:57 PM
For what it's worth, I have both a Mac Pro 5,1 and a first-gen Retina Macbook Pro. Both were nuked from orbit and had Mavericks installed using a thumb drive. Both run Premiere Pro CC without issue.
... View more
‎Oct 23, 2013
11:52 AM
SWDoctor wrote: It hasn't worked for both scenarios. I have reinstalled OSX Mavericks as well as Premiere but to no avail. A complete format and re-install? In other words: nuking everything on your drive? You're familiar with how to do that with Disk Utility during the installation process, right? And you created a bootable USB thumb drive to do it?
... View more
‎Oct 23, 2013
10:46 AM
Sandeep Singh wrote: Please try to uninstall and reinstall Premiere Pro CC. and then try to launch. And IF that works, I'd recommend folks on Macs do a complete re-install with Mavericks. That means formatting your HD and reinstalling from scratch. Apple's OS upgrades are fairly bullet-proof, but they're not 100% so. Something will always jump up and bite you in the backside when you least expect it. Going between dot-revisions (10.X.2 to 10.X.3) isn't a problem. Those are easy patches. But going whole versions (10.8 to 10.9) is where you'll want to format and re-install.
... View more
‎Sep 09, 2013
06:13 AM
Steven Gotz wrote: Where you work is a rather secretive place for good reason, I imagine. The "where I work" and "what I do" isn't necessarily secret, I just don't discuss them on public forums. The "what exactly am I doing right now" part is something I don't generally discuss with anyone at all because it's really no one's business. And I've signed all sorts of NDAs anyway.
... View more
‎Sep 09, 2013
01:54 AM
Steven Gotz wrote: Jason, did you go to Clarkson University? Uh oh... I've been found out. Poking around on linked-in I see...
... View more
‎Sep 08, 2013
06:25 PM
shooternz wrote: Wasting time and procrastinating on the Adobe Forums - Editing and posting vids of my buddies and me playing the Battlefield 3 video game. Premiere helps immensely with this task. - Prepping my gaming rig for the next generation of video games such as Battlefield 4 and the new Batman: Arkham Origins. Preperations include removing the single GTX680 card and replacing it with 2 GTX Titans SLI'd. -(Im)Patiently waiting for Intel to release the new Ivy Bridge Xeons, so that I can build a dual-CPU Hackintosh rig. Already have the Gigabyte motherboard picked as well as the case and power supply. The decision after that: which CPUs and which video card(s)? Perhaps 2 more Titans? Great googly moogly! - Stuff for my real job at work, which I can't necessarily discuss, but is fun all the same. I still can't believe they pay me to do what I do.
... View more
‎Aug 31, 2013
08:30 AM
Jim Simon wrote: Dude, I never thought of doing this. I ran some tests and found that AME no longer respects GPU acceleration like it did in CS6. I suspect this is why my export tests were so much faster than yours were. I just deleted the file, which has the same effect as adding the cards to it. FWIW, I deleted the OpenCL file as well, so that I always have the choice between the two.
... View more
‎Aug 18, 2013
09:45 AM
Steven Gotz wrote: But filing cabinets make great legs, don't they. To revive a sub-conversation about workstations we were having almost a month ago... Here's my solution for a 'cheap' computer desk. The door was trimmed down in length by the folks at the hardware store, but you get the general idea: It isn't stylish or beautiful. But it is functional and sturdy enough to hold 3 22" CRTs back when I used those types of monitors (ie, 50lbs a piece). That's my gaming station as I don't trust Windoze for anything but. For work, I turn to the right and see this: I bought that desk long before I did the door-and-filing cabinet thing, and it was a waste of money. But since I still have it, and it serves a purpose, I figured I'd continue using it.
... View more
‎Aug 09, 2013
04:04 PM
Steven Gotz wrote: Most people don't ever go back to old projects. As I mentioned in a thread on the main Pr forum: I decided to subscribe after thinking long and hard about my disagreement with the licensing model. And please note: I still do not and will not advocate it. I think it sucks, and would rather see a permanent licensing structure. But this is what we have so far. A note: I only sub'd to Pr and Ps versus the entire suite because I was thinking about longer term savings. In a year or two it doesn't make much sense. Over a few years, it does. And I have no use for the rest of the suite, so why pay any extra money for it? Anyway, my thought process went like this: I never go back to old, saved projects. It literally takes me about 10 minutes to recreate one of my vids, and it doesn't have to be perfect by any stretch. Given that, I can safely move to Pr CC knowing full well that if I decide to stop renting, I can just as easily revert to CS6. That is, of course, assuming Adobe does eventually deliver the AVCHD patch. Otherwise, it's CS5.5. Either way, I haven't lost anything. What have I gained? One: a chain around my neck. Yep, I'll admit it's there and I'm not happy about it. But, so be it. Again, I can just shake it off when I decide to. Two: better tech! Pr CC edits AVCHD like a breeze. It can make use of multiple GPUs to help speed things up. It's moving in the right(?) direction with coninual improvements to its OpenCL code, thereby freeing folks from the requirement of having nVidia cards in their rigs. It took a little critical thinking on my part to come up with this decision, and ultimately I decided to add some salt to the crow and eat up. The crow may not be tasty enough to others, salt or no. I get that, and again, I'm not trying to convince you to change your minds.
... View more
‎Aug 09, 2013
04:39 AM
Andy Bay wrote: Sometimes the review stops right there, because of a single major issue that is a so called deal breaker. In those situations, it is not necessary to write more on the issue. Writing more would simply be a waste of time and energy. While I hesitate to agree with Jim on most things, I do on this one. Here's what your blithering is actually similar to. Let's say you were going to review the lastest blockbuster movie out of Hollywood. Right before it's released, your local theaters all raised the ticket price by $5 (ARGH! Let's not give them any ideas!) You decide not to pony up the extra money, and therefore don't see the movie. Someone asks: "Hey Andy, what did you think of so-and-so movie?" Now, here you could say: "Well, I didn't feel like paying the extra $5 for the ticket, so sadly I didn't see it." Instead, you say: "The excess cost of the ticket has convinced me that the movie is terrible and not worth the price of admission. I'll never step foot in another theater again nor fill the Hollywood coffers unless they lower the ticket prices! All of their movies are garbage!" See how the messages are getting mixed up here?
... View more
‎Jul 31, 2013
03:05 PM
Jim Simon wrote: Curious. Perhaps more testing is in order. Indeed, and I did just that. I mispoke (seriously) when I said the software-only MPE took 2t. It turns out that both exports took less than t, but the hardware-enabled version was still 4 minutes faster. The footage was 00:20:11 in length. With the hardware enabled, AME exported it in 00:09:17. With it disabled, AME exported it in 00:13:19. So there's still some play w/the hardware there.
... View more
‎Jul 31, 2013
11:33 AM
Jim Simon wrote: That's actually been disabled in CC. No GPU acceleration at all with AME, only via direct Export. I'm aware of your tests Jim, but my own haven't really born that out. Unless I'm misunderstanding things. My usual benchmark is a 20 minute AVCHD video with a second 20 minute AVCHD video PiP'd inside. The second is scaled down by 50%, horizontally flipped (accelerated), and cropped 33% from the bottom (accelerated). The entire video is then scaled down to 720p on export to h.264 MP4. Driving that through CC's AME results in 1/2 real time. In other words: 10 minutes to do the work. If I clear everything, disable MPE, and re-export the same exact way, it takes.. a whole lot longer (about 2t, give or take). Is that because PPro already did the work before AME got its hands on it? Or is it not that cut and dry that AME isn't accelerated?
... View more
‎Jul 24, 2013
07:29 AM
Steven Gotz wrote: I am looking at the desktops at Ikea that run less than $50 each. Then you can choose the type of leg you want to use. What kind of material are the desktops made of? Particle, or solid wood? Or metal? Or...? But filing cabinets make great legs, don't they. They do. And darn functional, too.
... View more
‎Jul 24, 2013
06:41 AM
able123 wrote: I sorta ran out of room for more tables ( not even an end table woulda fit well where pig is now )..but everything is cool... I've become less and less of a fan of computers on the floor over the years because of dust. They act like giant vacuum cleaners. My proposal would have been to replace the entire table you have in the photo, and put both machines along with all of the LCDs on it. But again, it assumes that you have enough room.
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices