Skip to main content
S
SageousStudios
Participant
May 19, 2018
Question

Import ERROR of .MOV Files - TIRED OF BUGS - MAY LOSE CUSTOMER!

  • May 19, 2018
  • 2 replies
  • 499 views

Adobe,

I am a paying customer that is becoming increasingly tired of the bugs that you fail to test out before an update is released and it in turn costs your customers their time and their money on projects. You are at risk of losing many customers on here with so many neglected and serious bugs.

How can you not already have an update for something as simple and yet crucial as importing image sequences (especially DPX sequences) and .MOV files with codecs like H.264, JPEG2000, and Animation? All of this worked in earlier versions, and now it doesn't?

I have contacted customer support about this several times and all I hear is "try an older version" or "we are working on it and have no estimate as to when an update can be released". I have tried older versions and it does not help me since NONE of the project files that have been saved in recent versions of your software is backwards compatible. So I end up being stuck losing project files that I work on, not being able to import, edit, or transcode media, and unable to do my job.

Still no update on what I contacted support about yet.

So why should any of us stay with Adobe, paying for software that is supposed to be tested before it is released and service that we are not really getting, if you guys can't take this seriously enough?

This topic has been closed for replies.

2 replies

GLOBAL STOCK FOOTAGE
GLOBAL STOCK FOOTAGE
Known Participant
June 11, 2018

Da Vinci Resolve is your solution.

R Neil Haugen
R Neil Haugen
Legend
May 19, 2018

NO question that what troubles you're having are painful. But I'm still curious why you can't work in say 2017 until this gets hashed for those who are having this trouble. You can't open a whole project backwards, but if you're having so much trouble in 2018 I don't know why you started past the third project there.

Yea, I've had releases where I had to stay with the older version for several months because a bug in the newest release hammered my workflow. But I still got the work out. In fact, I normally have 3 versions of PrPro installed as I tend to keep older projects in their original build series.

One thing that might help with the projects you've done in PrPro 2018 is to export an XML file out, importing that into the 2017 version. You'd at least get your cuts there.

And again, no question about your troubles ... and full sympathy. Especially at feeling a need to rant, which I certainly have done a number of times. But in general, this release has had fewer major bugs than previous ones, so ... in general, I think the progress is good. Which is NOT to say that some haven't been hammered.

When this first came out, I had a couple days struggling with the workspaces not keeping my custom ones 'up' on the bar. Finally got that sorted on my machine. Past that, it's a very useful build for me. Hoping you can get relief soon, and in the meantime, use 2017 to just keep at work.

Neil

Everyone's mileage always varies ...
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices