[David Intrator]

Hi Kevin,

First of all, my set up:

Mac Pro (Early 2009) 2 X 2.66 GHz Quad Core
16 GB Memory
ATI Radeon HD 4870 512MB Graphics Card

Running Yosemite 10.10.1

I had also gotten crashes occasionally on Mavericks, but it’s really grabbed my attention on Yosemite with PP CC 2014.2

I do not have NVDIA GPUs.

The Chrome Extension Pushbullet” is not installed.

More recent crash incidents that might illuminate the problem:

Just finished up a project: 8 crashes in two days. Most of them happened while trying to export.

The crashes appear to be random, meaning, I’ll try to export a sequence and it crashes 99% of the way in.
Then I render the sequence before exporting (don’t know if that really helps, but what the heck), and it exports ok.

Then I try another export of the same sequence with the same export settings and it crashes, this time about 5% in.

Then I try again and crashes.

Then I quit PP, restart my computer, and it exports fine the next time around.

Other crash incidents involved simple things like moving a matte with my mouse a few frames to the left or right.

With this project the sequence settings were the exact same as the source footage settings. There was some B-roll however with different specs. I would render those when I brought them into the timeline. In addition, very few dissolves or motion graphics.

So there’s the export problem, plus a general crash problem apparently when I move certain items in the timeline.

It’s really quite infuriating and I’m not sure what to do. Should I go back to PP 6? Back to PP CC 2014.1? Move on to Avid?

I’ve tried all the suggestions written up here and other places online, but they dont’ really seem to help.

Any way for me to provide you with crash logs?

Need to solve this.

Like I said, I used to have occasional crashes with PP, but now continual crashing is part of my workflow.

I would suggest that you upgrade to Yosemite. The fact that an Adobe rep would not upgrade even to Mavericks is thought-provoking to say the least.

Once again, thanks.

[David Intrator]

Hello Craig,

Thank you for responding, but your response is unacceptable.

For one, large companies like Adobe and small ones like Sound Siphon have been able to deal with Yosemite with little or no problem. And many who did foresee problems informed their customers to wait before upgrading to Yosemite.

This idea of keeping your customers in the loop is key. If it is Telestream’s policy to wait until the final build to begin working on a update, it is Telestream’s responsibility to inform its customers, (and to tell Ustream to inform its customers) not to upgrade.

No notice was given by Telestream nor by Ustream until after the Yosemite problems surfaced.

To place the burden of responsibility on the customer to assume that developers of a paid application have not even begun to address potential problems due to an important and well-publicized upgrade is patronizing, to say the least.

And finally, there is a reason OS upgrades are announced in advance, and beta versions are provided. Indeed, there might be issues to address with the final build, but it at least gives developers the chance to foresee problems that might arise, start working on their code and then tweak it when the final build comes out. It gives them a critical head start on resolving conflicts, and like I said, let their customers know about it.

It is now about 2 and one-half weeks since Yosemite was released, and there is no word from Telestream or Ustream concerning when an upgrade will be available.

Instead, as I have read on the Telestream forum page devoted to this issue, the company takes the position (as you reiterate here) that the customer is at fault. In effect Telestream is loudly announcing “Caveat Emptor– Buyer Beware. It is your responsibility, Dear Customer, to assume that we do not have our act together and that we don’t even care enough to inform you about it. That you trusted us to do otherwise reveals your naiveté and lack of professionalism.”

This is a peculiar approach to customer relations.

(And as for the trashing of preferences, I’ve tried it and it doesn’t work. And if you read the Telestream forum page, it appears to only work temporarily for those for whom it worked at all.)

On a positive note, I do speaking engagements at corporations as well as universities about branding, customer relations and the like. This episode provides a wonderful case study of what a company should not do: be ill-prepared for an important upgrade, keep its customers in the dark, and then blame them for its own mistake.

[David Intrator]

I’m using Ustream Producer, which is Telstream’s Wirecast, white-labeled for Ustream.

It is not compatible with Yosemite, which I’ve found out the hard way.

To make matters worse, Telestream does not say when Wirecast will be available on Yosemite, and Ustream’s tech support did not even know what Yosemite was when I spoke with them 4 days after Yosemite’s release!

I’ve been on top of this issue since I discovered the problem and have been stonewalled by both Ustream and Telestream.

I’m looking for alternatives. Do you know of any?

It’s not like Yosemite wasn’t in beta for 5 months.