Out of curiosity. Why do you think think this is a solution
WHEN A SIMPLE UPDATE ENABLING MERCURY PLAYBACK / OPEN CL SUPPORT WOULD SOLVE 99 PERCENT OF MY PROBLEMS!
You have this...
1GB NVIDIA 650M graphics card
Is that not a supported card?
BTW - what is your hard drive set up ?
What media are you editing?
Did you update O.S lately, recently...? What is it?
Why do you particularly think "nests" are the issue?
What actually is a "fatal error"? Never seen one and is that a Mac only "error/message"?
Other Mac Users (not me) should be able to advise you on their experiences with similar hardware...but I doubt that they will do so here in this forum. Mac issues and otherwise seem to be unspoken of by Mac "evangilstas".
"Evangilstas..." No doubt, right? Hope that settles in with you in a good way.
CS 5.5 Does not support the card for Open CL / Cuda. I'd never use CS2014 if it did! I'm paying $22 a month just to have that feature! What a waist of time and money!
It seems after some research that the fatal error might be connected to the 650M Graphics Card chosen by Apple for the early 2013 Macbook Pro Retina. This card seems to suffer from heating / lagging. I'm thinking that it is tied into some type of a mis-synced clock type configuration whereby Premiere Pro suddenly needs to back out of it's operation. For example, when switching from the Open CL software to Cuda, I loose the preview monitor and source monitor entirely. It's a black screen. If I close the program and restart the program I'll get an image, but there are some strange lines and shapes that overlay on the image with scrubbing and sometimes with playback on occasion. Then, after the card warms up, I'll loose all visuals from the timeline and have to close Premiere Pro again. Oddly, Open CL really hasn't created this issue, just CUDA. But, for some reason, the OpenCL is acting up and causing a ton of lag on my current project. However, a project with a higher resolution timeline the computer screams through it in Open CL as if it were nothing. I hate to point the finger at Apple's bad decision to choose this graphic card and also at Premiere Pro for not providing a consistent professional program, but some type of fatal error and or crash is happening on every single project at some point during the edit and that's that.
I've got a 512GB SSD with 300GB free space... I've had this issue with the PR since Mavericks, and now Yosemite.
I typically use "Nests" to apply warp stabilizer effects. I get random errors with Warp Stabilizer and random fatal errors even without using warp stabilizer and just simply using nests to create my sequences.
A "Fatal Error" means that Adobe, not Apple, states that the program is forced to shut down and will attempt to save the project file. The problem is completely random!! So if I don't have my timeline to auto save every 2 minutes I'm sure to loose a ton of work and time when I go searching for all the additional copy of project, copy of copy of project, copy of copy of copy of project files.... and so on.
Heard from any Mac evangalistas yet?
You appear to be working with a single Drive ( SSD). !!!
You say the issue started with Mavericks and then followed onto Yosemite ! Assumably everything was fine before then.?
You appear to have identified a hardware issue *( from Mac) with the 650m card. Heat / lagging.
You have somethings (clues) to trouble shoot. The drive and the card being priority. I believe some of the OS issues are caused by "permissions" Check out Forum with a search.
For the record as regards
"a consistent professional program"
I have been pounding my CC2014 12+ hours a day (editing 10 TVCs) for 15 days straight to meet a deadline ( yesterday).
Nests, warp stabilisers, SG Links, multiple sequences in 10 separate projects, grafix, AEFX DIs, Motion, masks, titles, layererd psds, prores, AVCHD...
One crash from a drop shadow effect.but other wise flawless performance.!
The crash message by the way was " A serious error..." and not described as a "Fatal error..."
I simply reopened the project and continued.
A serious error occurs every time I edit footage. It's easy to reopen the project and continue, however, this process, after having faced it every day since CS2014 was first released, is not full-proof. I send user data / crash reports every single time and never hear anything from anyone about what's wrong.
Here is an example of one of last night's random crashes...
So what about the hardware "issues" you mentioned?
What about the hardware question I asked? eg single drive?
Have you taken a look at others experiences with those two Mac O.S's and potential fixes?
Maybe some one will chime in on that particular error message.
I'm going to the Apple store to address the possible hardware issue with the graphics card.
The OS and PR are running off the Apple 512GB internal SSD on the MBP Retina.
I have no idea how to change the coding of Premiere Pro to make it stop freaking out. I'll get in touch with Adobe Support again and again in the meantime.
The OS and PR are running off the Apple 512GB internal SSD on the MBP Retina.
Thats fine and standard...but where is the source media , scratch files, caches....etc ?
A single drive is not the way to get best performance out of an NLE. ie "bottle necks"
He does say that he has CC2014 and th error message seems to confirm that.
Thanks for the "you're ready for a teacher" comments. Should I start
talking about every other little thing I learned from my teachers? Let's
take a step back and let some others address this situation. I say so,
because I don't think that you're methodology is going to address the root
of the problem. Sorry.
Editor / Shooter / Writer
(1) 214-883-7381 (mobile)
Thanks for the "you're ready for a teacher" comments.
You never confirmed your hardware single drive drive set up or otherwise....so I guess you have eliminated that..
Happy to leave you to your Adobe rants and advice from others. I note you aint got much from the MAc users.
I realize he has CC 2014, but he was implying that he had no problems with CS5.5 except he could not get GPU acceleration, which is absolutely not true.
"and the last program bundle I bought was CS5.5 Production, which works so much better than CS2014!! How about a big old, YOU'RE WASTING MY TIME AND TAKING MY MONEY AND NOT MAKING ANYTHING BETTER WHEN A SIMPLE UPDATE ENABLING MERCURY PLAYBACK / OPEN CL SUPPORT WOULD SOLVE 99 PERCENT OF MY PROBLEMS!"
The other thing that confused me is his error message which has 2014.09???????????
He has blown me off Bill ..so I dont much care anymore.
Here is an example of the random Serious Errors from using PR CS2014 earlier today.
Process: Adobe Premiere Pro CC 2014 
Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Version: 8.1.0 (8.1.0)
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: Adobe Premiere Pro CC 2014 
User ID: 501
Date/Time: 2014-12-13 14:58:53.061 -0700
OS Version: Mac OS X 10.10.1 (14B25)
Report Version: 11
Anonymous UUID: 0FE6A156-AD12-5E1A-DC5D-6613517D8681
Time Awake Since Boot: 2000 seconds
Crashed Thread: 42 Dispatch queue: opencl_runtime
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
VM Regions Near 0x8:
__TEXT 0000000100000000-0000000100003000 [ 12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Thread 0:: Dispatch queue: com.apple.main-thread...
(DELETED A LOT OF DATA)
Model: MacBookPro10,1, BootROM MBP101.00EE.B05, 4 processors, Intel Core i7, 2.7 GHz, 16 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (126.96.36.199.10)
Bluetooth: Version 4.3.1f2 15015, 3 services, 19 devices, 1 incoming serial ports
Network Service: Wi-Fi 2, AirPort, en0
Serial ATA Device: APPLE SSD SD512E, 500.28 GB
USB Device: Backup+ Desk
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4
PR CS 5.5 Does not support the Macbook Pro. I am unable to use Open CL and/or Cuda! I'd much prefer to use that program because it doesn't crash on my every time I use it. I've tried the patch key stuff that adds the NVIDEO 650M graphics card to the native list of supported graphics cards, but the program monitor was black often times and Adobe Media Encoder doesn't apply Open CL / Cuda Support. It's significantly slower.
If there is a way to use Open CL and Cuda with this Macbook Pro I'll be done with CS2014 in an instant. Are we aware of a solution to that?
If I render the same file using Encoder CS 5.5 and Encoder CS 2014 encoder CS 2014 is nearly 2 - 3 times faster. Additionally, when editing GH4 footage in CS 5.5 it is choppy and doesn't respond quickly, essentially because it's software and not Open CL in my current setup. CS2014 is making GH4 footage edits quick and streamlined, but with serious errors every time I use the program at some random point.
For example, earlier today, I made a nest sequence of some GH4 footage because I edit in 3072x1728 and Warp Stabilizer doesn't work unless the file is the same width and height as project file. PR finished analyzing the file and then began to stabilize the video. However, the program suffered a serious error and had to quit before applying the stabilizing. After saving a copy of the file, I found a way to finish the stabilization, but every time the playhead came up to the stabilized footage area PR crashes.
I've had to erase the nest and wasted a ton of time trying to stabilize footage because of all the crashes. Now, I'm back to editing the project without the stabilized footage and will have to add that shot to the visual effects After Effects post production phase.
Re-Installed the Cuda Patch for the Macbook for PR 5.5. It's working great over the last 10 - 15 minutes just playing around with the GH4 files. However, when attempting to export an EDL and/or an XML CS 5.5 states that a generic error occurred and that it cannot load the project. Here comes the ranting... Therefore, the powers that may be, have once again failed to build the bridge between the past and present. Blackmagic Design's DaVinci ingests the XML files from PR CS2014 just fine but CS 5.5 cannot. I'd edit on DaVinci but my computer isn't supported by DaVinci. I've basically got the lastest model of Macbook Pro 15 Retina's to not be supported because of the 1GB graphic card. Definitely a tip of the hat to Adobe for working with this Macbook. 4K is easy to edit, but HD is nearly impossible to edit and skips frames in DaVinci. Hope this helps others see what type of trap this particular model of computer is, even when combined with Adobe.
The CS 5.5 Cuda patch is causing my computer to completely crash and shut down. I was trying this because CS5.5 in software support only was always reliable. Anyway, the Macbook screen freezes and I loose the ability to do anything with the mouse or keyboard. It's happened twice in the last 15 minutes.
Two nights ago I spoke with tech support and they remote viewed my computer. When adjusting settings inside of PR CS2014 my computer crashed. It happened not long after CUDA was turned on. They never contacted me to tell what it means or why it might happen. I'm guessing that this Macbook Pro Retina suffers from some type of graphic-card failure... Anyone have any insight?
Update your GPU and the CUDA drivers!
Search the forums for Retina problems.
I'm using the latest Cuda driver 6.5.25 and have no idea how to update the GPU... That seems like it could be my problem. Looking online, it appears that numerous Macbook Pro Retina owners experienced crashes and black screen program windows and serious errors like what I'm experiencing but the majority were like a year or two ago.
Could you please provide information how to update the GPU? Thanks.
Sorry, but I am not a Mac owner.
Folks. all versions of all software used by the app have to be compatible with each other. let me guess you have some old plugin chillin somewhere on you machine from sole old version of some NLE? yup, it will crash everything because of capability problems.
Good answer. This was a small portion of the issue. Had some stuff related to Snow Leopard from Blackmagic Design that would automatically load on startup.
This case was related to the Macbook Pro Retina experiencing kernel panics as a result of Cuda Acceleration. Had the motherboard replaced (graphic cards too) along with the entire operating system wiped and re-installed (Mavericks and Yosemite). Nothing helped. The most stable I ever got the Apple to work in Cuda Acceleration was to have the program monitor completely turn black (randomly turned black after 5 seconds) and not show any footage. But, PR didn't shut down or crash.
On the flip-side, Open CL was working fine, but there was about 15% greater render speeds with Cuda and it was kind of frustrating to think that a Macbook Pro Retina couldn't utilize the "Pro" side of the graphics card. Ended up selling the computer and haven't bought an Apple computer since. Been a long road away from ProRes, outside of the Blackmagic Cinema Camera.