I'm trying to export a 25 min HDV file and Encoder is saying it will take 60 hours?

When I tried Neo HD it exported in 6-8 hours

Hardware
2.1 ghz Quad core AMD
8GB Ram
74 1000rpm OS
400GB Raid 1 Editing
800GB Raid 0 Scratch

There has been no other difference in SW/HW so I'm a little confused.

Right a little update. I reinstalled the trial of Neo HD (Got 5 days left)

Exported the same video and again took 60 hours. Tried difference disks same outcome.

Tried exporting the video as interlaced as that what the source footage is - Same 60 hours.

The only other thing I did was disable 2 audio tracks, 3 + 4. So enabled these again and just deleted the audio from these tracks and exported.

Back down to 8 hours!

Very Odd? Any reason why disabling audio tracks in PP would increase the export time from 8 hours to estimated 60 hours?

After this video has exported I'll move back to Neo Scene and test again.

We resently see Premiere projects get confused (even in CS4) and the result was crazy long render times. And the classic fix for Premiere confusion: Start and new project and import the old project into it, open the original sequence and export. Yesterday we was a system that a 3 minute timeline was going to take 32hrs, we did this project import and the export took 11minutes. Some things in Premiere never change.

Cheers David I'll remember that one for next time but it seems that just disabling the audio tracks sent the render times from 8 hours to 60 hours.

Deleted the audio from those tracks and enabled them reverted it back to 8 hours.

Tis very Odd this CS4

...Yesterday we was a system that a 3 minute timeline was going to take 32hrs, we did this project import and the export took 11minutes.

David, one thing that still holds me off from buying the CineForm codec is just this. I mean, is a three minute Timeline that takes eleven minutes to export? Yes, its better than 32 hours, but those eleven minutes is still close to 4x RT. I just cant justify those render times with long Timelines, ~ 45 minutes and longer.

Export CFHD to MPEG2 is bad but somewhat acceptable while the encoding times from CFHD to CFHD for a master file is insane.

I have a trouble ticket open regarding this issue but want to hear if a three minute Timeline export that takes eleven minutes is a normal render time when working with the CFHD codec.

I have been testing CFHD workflows for a couple of days now, and the culpit seems to be to decode the a CFHD file. Encode from lets say AVCHD to CFHD is ok, but CFHD to CFHD is insane and not worth the wait when working with long Timelines.

Dont get me wrong David, i really do love the image quality i get from the CF codec, but i strongly think that render times must be adressed. If it is Adobes fault, hunt them until they fix it, if it is Microsofts fault, haunt them, if it is CF's fault, fix it, if it is Adobe+CF, fix it, pretty please. :)

Following CF's advise to transcode the source footage to CFHD > Edit CFHD > Archive to CFHD takes to long time because the issue when one encode to CFHD from a CFHD source, 8-bit or 32-bit float.

Yes, i do work with long Timelines so i really pay attention to render times and have done that for years. :) Feel free to contact me for render tests if any improvements are being made. I prefer to focus on the whole chain, transcoding from lets say AVCHD > Edit the footage > Archiving the footage.

Kind regards, Roger :)

It is all Adobe. We have support questions to them, we do have to pester them more for answers, but we've been busy with other items. Our encoding is many times RT on modern system but Premiere will not provide the frame fast enough (we can encode 100+fps, yet adobe only gives us 6-10.) Remember CineFOrm can capture and encode HD live from HDMI or HDSDI sources. You can prove this putting a still on the timeline, we compress each frame as if it where unique, so the encoder has same work to do, and we encode around 50fps (Adobe still slow) as we only use 30% of the system. Now repeat this test with a opacity ramp on the source still, and the export is 2-5 times slower (random it seems) -- all Adobe, adobe importer, adobe filter, the export options did not change. Your support question should (also) go to Adobe. We expect that will be one of the faster export formats, once we find the magic words to tell Adobe ("go fast -- please!!!" or "have you heard of threading" doesn't seem to work.)

My issues are random.

25 mins HDV 1440*1080 ranges from 8 hours to 60 hours
10 mins HDV 1440*1080 can't get below 20hours

It just seems each time I have to go back and send the project to AME and it picks a number of out its head and thats how long it will take.

:(

Please start your Adobe calls.

David, did you try importing the project into a new project -- clean up a lot of Adobe mess.) Also try this: Export -> Movie -> Quicktime, select the CineForm HD codec, and set the resolution. Often Premiere get this right, then you can rewrap the results to AVI (Neo HD and above.) For BNeo Scene users of shorter projects (user 4min) the Video for Window export seem to work less randomly.

Please start you Adobe calls.

David, did you try importing the project into a new project -- clean up a lot of Adobe mess.) Also try this: Export -> Movie -> Quicktime, select the CineForm HD codec, and set the resolution. Often Premiere get this right, then you can rewrap the results to AVI (Neo HD and above.)

Hi David,

Yeah I tried a new project and again massive amount of hours. I havent tried the Quicktime export and I only have Neo Scene so can't convert it back.

My Issues are something to do with either the audio tracks 2+3 because when I delete the audio it reverts to 6-8 hours. With these tracks in place it says 60 hours.

David,

What type of audio is on those tracks (mp3, wavs, camera audio, etc.) While we do nothing with audio -- that is all Adobe, it would be nice to produce test case to send to Adobe.

Roger,

4X is not the norm. I was just venting some frustration we have with Adobe's slowness. We are already one of the fastest I-frame exports, a simple 1 minute timeline here took me on 1m23s to export (it is annoying that Adobe only used 25% of the CPU.) Quicktime PhotoJPEG of the same sequence took 2m30s. We can be faster. Other interesting stats, the same timeline with a First Light look applied (white balance, saturation, gamma and 3D LUT) took 1m55s, the same timeline with a single Adobe "Fast Color Corrector" took 3m52s (three-way color over 12minute.) So Adobe is the major bottleneck. We have work to do, but so does Adobe.

Hello David (Sorry for my hard words)

I cannot keep myself silent anymore, I think this is totally insane with these render times. How could you expect people to buy and work with your lovely codec with this render time?

I have bought v3 Prospect HD and I love it but the v4… together with CS4 is just a no no.
You can’t expect that people will cope with the task of being a beta tester for a 6 month or more and all we hear is that it’s all Adobe’s fault. What kind of reply do you at CineForm get from Adobe, is it moving at all (when will this API bee fixed)?

I was promised one year a go that the Deckling Intensity Pro was going to work as a timeline program monitor card for CineForm but nothing has happened. My working colleagues did get from your support a promise that it would be ready in two moth, it's been five months now?

I work at some of the biggest broadcast TV stations here in Sweden and I did just check today on how our various editing system did handle the ingest of different media when it comes to split the stereo files in to separate mono files. Every one (Avid, Final Cut, Premier and Premiere with MainConscept MPEG PRO did split the files in to mono files. Why do you think people would like to have stereo files instead of mono tracks. How often do you believe that people are recording an interview in stereo?

Your answer at July 21st, 2009:”We are unlikely to change the audio support in that way, not enough cameras/users will benefit”.

Me and all my colleague answer to this is WHAT?????

We also need to be able to set a proper output path when ingest the media like P2, this does not work at all right now.

I won’t go in to AVC-Intra support, but I think this is super critical too.

Sorry David and CineForm for my hard words but I thing you’ll have to be more precise in your status one these issue and several other things on what’s going on, if not you will lose me and many more customers.

Best Regards
Mikael
Sweden

(we can encode 100+fps, yet adobe only gives us 6-10.)

But why is AVCHD to CFHD waaay faster than CFHD to CFHD if the only limitation is "Adobe only gives us 6-10" and Adobe is the one to blaim? If "..only gives us 6-10" is the correct answer it should apply to all renders to CFHD but thats certainly not the case here. And i dont get the threading issue mentioned earlier issue either. My eight cores pegs at around 60% - 65% during render to CFHD and that looks like a pretty good threading. Is that the kind threading we are talking about? I have seens other codecs thread way less than 60% - 65% but it exports faster despite the lower threading. Its about using the threadings one get...

After years dealing with hardware and software companies i have found out that they always love to blame each other. This happens everytime, company X blaims company Y while company Y blaims everything at company X and then nothing gets done because all involved is happy because its not their fault. I talk from experience and have been knocking my head many times by this...

To be clear, i do certainly not want to insult any person or CF, i just want to be able to use the codec with human render times. In my world intermediate codecs should be fast. :)

I can cope with a render time 6-8 hours depending on the project size but its jumping from 2 hours to 20+.

Futher to the problem in my OP if music tracks 3+4 are enabled it sends the render time tripple fold. If I delete the tracks it drops back to normal ish time.

My music tracks are on the same disk as the raw HD footage? Would this cause any problems?

Can anyone help?

**EDIT**

Moving the extra tracks to a different disk didnt make any difference.

Another update.

Exporting with the extra audio mp3 tracks causes the render times to goto 20+ hours, take away these tracks and it exports within 30 mins for a 10min HDV project.

Not sure if its the tracks I'm using or the project. So I'm exporting a Cineform AVI then will try add the tracks again.

Another update.

Exporting with the extra audio mp3 tracks causes the render times to goto 20+ hours, take away these tracks and it exports within 30 mins for a 10min HDV project.

Not sure if its the tracks I'm using or the project. So I'm exporting a Cineform AVI then will try add the tracks again.

Thanks, that sort simple test we can repeat, and report to Adobe as needed.

Thanks, that sort simple test we can repeat, and report to Adobe as needed.

Well I exported my master Cineform AVI file and added the extra music tracks - Goes back to 20+ hours. So later on I'll get some other MP3s and test them just incase there is something wrong with the MP3.


Hope to get to the bottom of this tonight!

Oh forgot to add exporting to H264 MP4 exports fine so I'm guesing its something to do with Cineform/Adobe AVI?

Thanks for the feedback, I can now reproduce the export delay with stacked mp3s. Working on it now.

David great news!! Glad it wasnt just me. Its been driving me mad.

And it was driving us mad to, but we found it with your input regarding mp3s. It was a moderate Adobe glitch causing our export to think Adobe had crashed. We put watchdog timers in many of our tools so if the calling application dies/locks (Premiere -- it used to do that a lot) we auto close our tools to clean up memory. BUT if you had many mp3s (I stacked 3) or other more complex audio types, CS4 was taking 15-20 seconds to return the frame worth of audio data -- our watchdog timer kicked in at 10 seconds to say Premiere has locked so shutdown. It seems the CS4 is slower than we thought :), so we set this timer to 100 seconds to get CS4 more time to wake up. Now a reported 20hour export is saying 3 minutes. Note: this threaded rendered component is the same used in CS3 (10s was plenty for that product), so this just another example of CS4 weirdness we constantly hit with, slowing CS4 development.

Here the component with the longer timeout.
http://www.cineform.com/downloads/CFRenderProc20090812.zip

Unzip and copy over CFRenderProc.exe in:
C:\Program Files (x86)\Adobe\Common\Plug-ins\CS4\MediaCore\CineForm
C:\Program Files (x86)\Adobe\Adobe Premiere Pro CS4\Plug-ins\Common\CineForm

The full release with this patch will be out in a few hours.

David

Great news David - Testing it now.

Yeah it works - Export says est of 40mins which I can deal with!! Doesnt max out my CPU/Memory though but not fussed it doesnt say 20 hours to export a little video.

Cheers David and many thanks for the quick reply/fix.

We regularly export 8-10 tracks of .wav and have none of these probs, so it would certainly seem to be MP3 compression specific. Using stacked MP3's can introduce other probs as well. We've found a good workaround is to use ONLY .wav or similar.

Same thing is true for .jpg still compression probs we still have once in a while (flashes, green output, and wierd behavior). That's the main reason we convert EVERY still to PNG or similar. Kills the probs before they happen.

We regularly export 8-10 tracks of .wav and have none of these probs, so it would certainly seem to be MP3 compression specific. Using stacked MP3's can introduce other probs as well. We've found a good workaround is to use ONLY .wav or similar.

Same thing is true for .jpg still compression probs we still have once in a while (flashes, green output, and wierd behavior). That's the main reason we convert EVERY still to PNG or similar. Kills the probs before they happen.

Cheers Stephen. I have seen the green flashes so I will convert thes to PNG from now on and the MP3 bug shouldnt happen anymore now.

David

Hi David,

I might have another bug. I'm exporting a video slideshow that is 1 hour 10 mins long and again it says 166 hours to export?

It is Cineform AVI 1920*1080 Square pixels with music in the background. The AVI is 1 complete file. No effects inside the AVI.

Run the latest version, as there was a fault found with MP3s being so slow in CS4 the export engine would timeout. If that is still occurring -- we put the timeout at 100seconds thinking Adobe can't be that slow (however it was take 15seconds to return the first sample, so who know how bad CS4 is.) The workaround (in addition to contacting support), export the audio only to wav an import that to replace your MP3s.

Run the latest version, as there was a fault found with MP3s being so slow in CS4 the export engine would timeout. If that is still occurring -- we put the timeout at 100seconds thinking Adobe can't be that slow (however it was take 15seconds to return the first sample, so who know how bad CS4 is.) The workaround (in addition to contacting support), export the audio only to wav an import that to replace your MP3s.

Yeah I'm already at full updated version. Even tried the bug fix in this thread.

Exporting video on its own = 5 hours
Exporting audio = <3 mins
Exporting video+audio = 166/180 hours

This video is just 1 hour of pictures with MP3s attached, I guess Adobe can't handle these so I will just have to convert them to WAV before I use them!

Video with attached WAV file is about 6 hours.

So its just another step I need to take to export a video.

Your 1st bug fix seems to work with MP3s upto about 40 mins but any longer and reverts back to massive hours.

Come on Adobe!

Adobe must be decoding all mp3s to a cache somewhere before return the first sample, pretty simplistic (not clever,) I'll increase the "is Adobe dead yet?" time out.

This thread should be required reading for everyone who is contemplating buying Premiere. Perhaps reputable dealers could require that people read it and sign a performance waiver before selling Premiere to anyone.

On the more serious side, I have a theory about flaky engineering support from Adobe. I suspect that in some cases people who understand the software code and have the ability to fix problems have left the company. It's hard to believe that Adobe would refuse to fix problems just out of bull-headed stubbornness; I suspect there is no one there who knows how to fix it.

This thread should be required reading for everyone who is contemplating buying Premiere. Perhaps reputable dealers could require that people read it and sign a performance waiver before selling Premiere to anyone.

On the more serious side, I have a theory about flaky engineering support from Adobe. I suspect that in some cases people who understand the software code and have the ability to fix problems have left the company. It's hard to believe that Adobe would refuse to fix problems just out of bull-headed stubbornness; I suspect there is no one there who knows how to fix it.

I agree! I moved from Pr 1.5.1 and although I didnt have any of the fancy features of CS4 it worked and worked well! So after 3 versions how can they get it so wrong?

Also its not just Pr its also Encore. If I launch En with my Bluray burner attached En crashes the PC. No CTRL ALT DEL, stone dead crash nothing can recovery it.

I worked out if I disable the BR in device manager the program works fine and I can create a ISO BR disc then exit the program and burn it via Nero!

I can't be the only one having so many problems with CS4?

I can't be the only one having so many problems with CS4?

You're not the only one.. I've got exactly the same Encore + BR-Burner bug.. and many many other bugs (don't get me started on Fireworks). It's really unbelievable just how bug ridden CS4 is! And that's after several updates/patches that the already released...

But I guess it will be the same this time: it will continue to be a total bug fest and before anything is really fixed they will release CS5.. yeah.. sorry, but I'm really sick of it.

My condolences go to David Newman and his crew... it's not only Adobe / Premiere where they have to deal with so many bugs and problems.. at home I'm using Sony Vegas and looked into updating to 9.0.. wow, what a instable bug ridden mess that version is!
It was shortly followed by 9.0a .. some bugs fixed, several new ones introduced (for me it was basically unusable) .. a few days/weeks later already 9.0b.. still not really stable.

Somehow - and I don't know why - it seems incredible hard (or impossible?!) to write a _stable_ and _user friendly_ editing software for PCs... *sigh*
Sorry for the rant, but I'm sooo tired of all this software failing so many times when you're on a dead line.
It seems they drag too much old stuff (old code) around from version to version...