Hi! Having a pretty weird issue with Quicktimes with any flavor of DNXhd exported from Autodesk Flame or Smoke, they crash ANY CC application, but they work perfectly fine on any other Adobe CS6 application, or any other application, called Dofital Fusion, Media Composer, etc...
This happens on all of the computers where we installed CC, Mac and PC, desktop, laptop, etc, 8 machines, all the same problem...
I think most of you are going to say, report it to Autodesk, I already did, but think, CS6 and any other app open these movies just fine, only CC crash with them..... Anyone from Adobe here that would like to get a small QT to check what is going on and get it fixed? This is extremely disruptive for our workflow and is preventing us from using CC
Thanks I will.... by the way.... I see that I have 8 support cases to use on my contract.... but being on the phone for 2 hours listening to music waiting for someone to pick up the phone.... the schedulle a call back does not work either.... is this the new support for teams? I would say kind of not very useful...
I will export a short clip and post the link as soon as I have access to my computer.
here is a link..
a simple color bar 1 second long.
Opens fine CS6, crash any CC app, in MAC or PC or anything we have in here.
hope is an easy fix, we have a whole library of media in this format that we can not use in CC and works fine in CS6.
I would appreciate an update of when this could be fixed since have to avoid using CC until I can use my footage library.
And no problem with opening a formal support case, if I could get someone to pick the phone.
I to o have some DNxHD QuirkTime material. I believe that there are too many codecs and that some standards need to be set between camera makers and software makers.
The Apple vs Adobe contest is not helping here.....maybe cameras should be ADOBE CERTIFIED....like the video cards are......or, at least a current ,and frequently updated list ofproblem codecs. Adobe should thoroughly test all likely codecs, BEFORE " releasing product"
well... Adobe is not the only app in the world to do post production :-) ....
and this is not a camera issue, this is exported from another software, and works with anything but Adobe CC.
In this case, I take that is impossible for Adobe to test absolutely every codec in the market.... I understand that, with them fixing this and releasing a fix soon, I would be happy.
The fact that these same movies work with anything else and even with CS6, makes me thing that there is a problem within CC and not with the prorgams that generate these movies. Reported it to to Autodesk, but as it does not crash anyone else, and they do not have a way to debug Adobe apps, not much they can do.
Hate codecs too :-)
No I do not have anything like that, I don't even know what it is. Have you downloaded the Quicktime and tried on your system? It fails on every place I try even outside of my work enviroment, tested it yesterday in two laptops, MAC and PC, crashes both of them in CC and not in CS6.
Yes, I tried it and it crashes the application on Mac. Please file a bug report from your end, and I'll report it from my end.
Here's the bug report form: http://www.adobe.com/go/wish
does bug reports actually do anythign? I have reported many in the past and I never even get an email with a case number or a courtesy email informing of the status... nothing, and frankly, I think this is a showstopper....
I also reproduced the crash. Thank you for providing the sample file this is very helpful.
I've logged a bug and will report back here as soon as I have any info.
Sorry for the inconvenience.
Yes, it sure does make a difference even though it doesn't seem that way. As far as emailing you with a case number, etc. due to a bug report. That does not occur too frequently, sorry.
If you want a dedicated case number, etc. for reference's sake, I recommend contacting support: http://helpx.adobe.com/support.html
I know this is a crummy bug, so I'll do my best to raise its awareness.
Sorry I didn't get back to you earlier. The last couple of days were quite busy for me, so I didn't have too much time to hit the forums. But I see that Peter and Kevin covered well for me.
Since we can make no promises as to when a fix for this will be released, have you considered workarounds such as re-encoding from the original source in Flame or Smoke to an alternate format or transcoding through CS6 to an acceptable digital intermediate? The help for Smoke indicates that projects can be saved as EDLs. It's worth checking to see if Premiere can import them (unless, of course, you already know that it won't work...)
While I understand that these workarounds are a real hassle, an inconvient but viable workaround is better than being dead in the water.
I don't understand at all, how on earth and EDL would be of help on this? An EDL is just a bunch of text, what you want me to do with it? Just curious what are you thinking.
Re export or transcode the whole library is unreal, and since this is a regression on the software, I think it should be considered of high importance.
Now if you know what causes it and it something that can be avoided at software design level, you can let me know and I will pass it sling to Autodesk design team since I'm a beta tester working very close with them and I'm sure they will consider it of high importance and fix it. Although is sort of impossible for them to guess what makes your app to crash with something that was working before.
By the way, we deliver spots to 90% of the TV stations using this format, so if at some point they start upgrading stuff to CC, you are going to have a bunch of angry and troubled customers.
I understand you can't make promises, I'm just trying to illustrate the importance of this.
I've never worked with EDLs, but my impression was that they're one of several types of files (along with OMF, AAF, and FCP XML) that can be exported from one post production program, distilling a sequence to a series of clips, cuts, transitions, etc., for purposes of importing into another program. If my understanding is incorrect and an EDL is in no way suitable for this purpose, then I apologize.
We're aware of the importance of this issue. My purpose in discussing workarounds was simply to help find a way for you to continue working with PPro CC. Under the best-case scenario, if the management team decided tomorrow to put out a critical patch and engineering checked in a fix immediately, in my experience it would be at least a matter of weeks before the update would be released.
As I had no problem editing these DNxHD QuickTime files, ( which I believe are 32 bit and trigger the " QuickTime importer" ), using PPro5.03......I am wondering what is happening with these newer versions. The software appears to be GOING BACKWARD in some areas, and going ahead in others. With all the bugs and problems I am reading about.....it appears Adobe must spend some of its CC income on THOROUGH AND EXHAUSTIVE TESTING before releasing new versions.....perhaps, an enlarged Beta program to uncover unknown problems in advance of a general release.
An EDL is just an Edit Decision List. A text file that contains the timecodes of Ins and Outs of clips, not even containing paths, formats or anything, it’s and all and obsolete format being replaces by AAFs and XMLs, but certainly not a format that includes or have any sort of media. AAF is the only format that might include media as a wrapper, and not widely used by anything but Protools.
I appreciate you try to find a workaround, but in this case, an EDL is not the answer, since it is just basically a just a cut, once I get the EDL back to Premiere, I still need to export the media in a format that PPro can understand. For future jobs, I can switch the media format, in fact I’m using MXFs now, but I have a huge library of stuff that worked fine and now it does not, and I can’t change that neither transcode hours of material because CC apps have a regression and can’t open them.
Plus, Extreme Reach, one of the biggest distributors of spots to TV networks, takes DNXHD QTs as the deliverable, and once studios and people start to roll to CC, you are going to have a storm of ….. hitting the fan… that is why I’m suggesting to take this very seriously and rush a patch for it.