I've managed to set up an acceptable system (for my needs anyway) using the MPE.

Using two quadro fx3800 graphics cards, although I'm not sure whether you need the secondary card to be the same as your primary CUDA one. This should work with any decent secondary graphics card on a suitable workstation (I think!).

My primary FX3800 card outputs to one monitor for the program and one preview out (via a dvi/vga to s-video converter box) to my CRT broadcast monitor.

Then my secondary card outputs my second monitor display for my dual screen setup. essentially its a three screen setup as my crt is always displaying part of my desktop until Premiere previews through it. This is actually more useful for me as it gets more use than previously through firewire, As I can make use of it when not using Premiere or AE.

Then If I need to export to tape I'll have to switch to software renderer but hopefully that will change in the future.

Initially I tried to preview out to my CRT through my secondary FX3800 but I was dropping frames (on the preview monitor not the program monitor) so I assume that MPE is only working on the primary card as theres no sli support for this card on my system.

So for me this is a stellar improvement over CS4 so I can't complain too much, still hoping Adobe/Nvidia will fix the firewire out soon though!

How do I set my projects to software rendering?

I have succesfully bypassed the problem by switching MPE to Software only.  Thanks to all for the advice.  Can anyone advise how I will know when Adobe/nVidia have fixed the problem?

J Eaton

The first post about this CS5 bug was in May.  It is now Augusut and still no fix? 

Every time I'm about to place my order for CS5, I find out about another "gotcha' problem.  I'm still on CS3 and am seriously wondering whether I should continue to move forward with Premiere.

I still use an older "DPS Velocity Quattrus" system and it still leaves Premiere in the dust.  Unfortunately Harris, who bought Leitch/who bought DPS, has discontinued the product.  A software developer from Itlay is attempting to breathe life into it (ivsEdits.com), but it isn't a fully operational system.

Yes, "Firrewire" output is still a Big Deal.  There are many of us who use our editing systems as a business tool.  Going back and disabling the Mercury Engine, then re-rendering as "software only" is a waste of my time.

Come On, Adobe & Nvidia, get this fixed!

J Graves wrote:

 

The first post about this CS5 bug was in May.  It is now Augusut and still no fix? 

 

Every time I'm about to place my order for CS5, I find out about another "gotcha' problem.  I'm still on CS3 and am seriously wondering whether I should continue to move forward with Premiere.

 

I still use an older "DPS Velocity Quattrus" system and it still leaves Premiere in the dust.  Unfortunately Harris, who bought Leitch/who bought DPS, has discontinued the product.  A software developer from Itlay is attempting to breathe life into it (ivsEdits.com), but it isn't a fully operational system.

 

Yes, "Firrewire" output is still a Big Deal.  There are many of us who use our editing systems as a business tool.  Going back and disabling the Mercury Engine, then re-rendering as "software only" is a waste of my time.

 

Come On, Adobe & Nvidia, get this fixed!

Well...i'd guess that CS5 hold it's own against a system like yours for flexibility...though if the way that card works is in your workflow "sweet spot" then I guess you're probably best served to stay with it.

If you have a system that has the juice to even run CS5, i can't imagine that running a CUDA-augmented system for Mercury is even remotely necessary for editing DV...  as far as using our systems as a business tool...I'm not sure what you're implying.  Most of us who are in the production business -in general- have moved to some form of HD some time ago, most of my peers made the move during CS2...

Are you implying the rest of us aren't professionals, even as you are lobbying for aggressive support of a consumer-oriented I/O configuration?  I hope not.

It's not a bug BTW...it's a configuration that a few people don't like...but when your effects render is out on the display card, that's the way the pipe is routed.  Even HDSDI card manufacturers are finding that pulling those frames back off the display card negates some of the speed gains.

If you have a system that is qualified for it, I think you should download the demo and try it before you assess PPro CS5 any further.  You are making lots of sweeping statements about a piece of software released almost 4 years ago running on a hardware system that was discontinued 4 years ago being better than the newest software running on up-to-date hardware without understanding what its performance is really like...even without a CUDA card.

I can shut off CUDA and rip through DVCProHD like there's no tomorrow on my 3 year old dual dual core AMD...I have to believe you'll be able to -shred- DV on even an average-ish machine by today's standards.

So there's some semantics that have been a problem since 'Mercury'

was first 'uber-leaked' everywhere...It's independent of the CUDA card.

Having a CUDA card is  certainly helpful for lots of effects on big rasters (HD stuff) and you may find that very helpful as you edit in HD.  However, another part of Mercury that is available, CUDA card or not, is the ability to drop resolution to a lower pixel count for faster response during editing.  Even at its lowest resolution settings, it doesn't fall much below standard def.  I'm not even certain you can drop res on a DV timeline...I've not tried it.

The bottom line here is you have one switch to flip in the sequence settings and you're in software Mercury and the FW is live.  If you prefer, you could use Media Encoder to output the DV file along with the MPEG files and whatever else the stations want delivered from your HDV timeline all at once, and place the DV file on the DV  timeline and send it out to tape...no rendering necessary.

I think you may be grossly over estimating the amount of inconvenience involved here.  In your workflow description, i just can't see where having the CUDA card live for just that dump to tape will give you any remarkable benefit for DV material, the computer just wouldn't be under stress.  For demos, I'm switching it on and off all the time...it's quick.

...with one last caveat.

No MPEG based file types are supported in the trial...MPEG codec licensing, etc.  But DV is certainly supported.

I keep forgetting about the MPEG thing...which knocks out a ton of formats unfortunately.

But you'll be able to see how DV works.

And DVCProHD is in there if you want to play with an HD workflow.

(sigh)

It's just how it is unfortunately.

Todd_Kopriva wrote:

 

> No MPEG based file types are supported in the trial.

 

 

Not exactly. Here's the precise answer about what's not in the trial:

http://forums.adobe.com/message/2997829#2997829

Well...OK.

I suspect that for most people who want to download the trial to actually explore the format support, the essence of what I said is true...

While I understand the reason they're not in there, I don't think I'm interested in splitting that particular hair with users who can't load their camera footage as that's a pretty thin caveat that would likely be considered a bit insulting to even bring up..

But thanks for the clarification.

:-)

Tim

If this doesn't work for you, you should start your own thread (as your issue is separate from the main gist of this particular thread), but do you have the Export to Tape option activated properly?

Either click the Output button on the Program Monitor (the RGB circles icon) or go to Sequence > Sequence Settings > Playback Settings and verify that External Device is not set to None. For whatever reason, Adobe has split the preview output and the export-to-tape output into two different settings, and this is a pretty common "gotcha." You can crash record without this setting specified (as long as the External Device under Realtime Playback is set to your DV device), but you can't use the Export to Tape procedure without this setting.

Again, if this doesn't correct the issue, start a new thread to focus on the particular issue you're having.

AFTERTHOUGHT: Also, check your device control settings in Edit > Preference > Device Control:

You don't necessarily want the settings shown here, but you can verify that your device is being recognized and is controllable. You have to do a sort of Vulcan neck pinch on Premiere in order to get it to export to tape sometimes.

Hi BC, by chance are you trying to output via firewire from a Standard Definition timeline or from a High Definition timeline?  In CS3, I can only "print to tape" from an SD timeline.

....just once more thing to check.

Hello Graves

I am going from SD timeline to SD DV/DVCAM format recording. From CS3 I can output to HDV from an HDV timeline (1440x1080) as well, ony HD is what firewire doesn't do.

Hello Tim

Time code is DF on the timeline and DF on the recorder, both 30fps.

Thanks.

-Bala Chandran.

Well..... I just installed the full upgrade to CS5 Production Premium and can verify that the DV output does not appear to be working.  I will post on the new thread since this reallyl doesn't have anything to do with the MPE.  Yes, I followed all the steps outlined above.

I'm still finding my way around forums.  Please can J Greaves point me to his new forum?

Any news on this?

For me it's practically useless feature, as I'm using HDV/DV recorder for output, so MPE GPU is always disabled.

This ever get resolved?

Hi,

I am trying to ouput my timeline to my HVR M15N.  PPro CS5 shows it controls the VCR but I have black video and no sound recorded on the tape.

I heard about MPE but I don't kwnow anything about it. What is it? How and where can I disable it or turn it to software only? I work with an RTX 2 but I think it dosen't matter in this case, right?

Sorry about my english, i'm from Brazil. Please, help.

Thanks