Arabic titles in PPro CS5 are left-to-right

Hi,
I'm trying to add Arabic subtitles in Premiere Pro CS5 (PC).
When I copy and paste the text, it switches from right-to-left to left-to-right.
I need it right-to-left.
Can anyone help?

Found a solution that may work, although I used windows, Premiere Pro CC cloud version (2014):
Export tout of the Arabic word doc as a .pdf
select the text in ADOBE ACROBAT. RIGHT CLICK and “copy with formatting” then
paste into premiere.
May have to paste it LINE BY LINE and occasionally tweak the ordering.  Pay careful attention.
The type of PDF export may be important too but I haven’t tested that.  I just know it’s working for me.
If there is an English word in the middle of the Arabic just select that word and not the punctuation and COPY FORMATTING and it should paste ok too.
-www.mellenheadprods.com

Similar Messages

  • PPro CS5: Titles have wrong color and thickness in Timeline

    Hi there
    if i'm writing a Title in PPro CS5, everything is ok and like in PPro CS4 in the Title-Window. Then i'm changing to the Timeline and the Title gets bright and thin in the Program Window. The Title has not it's origin color, as selected in the Title-Window. Also it has a different thickniss, it is hard to read on TV.
    Here is a Screenshot of the Title in the Title-Window (picture above with green border) and the Title in the Timeline-Program Window (picture below with red border):
    http://666kb.com/i/bj4dbxa1nxbv53s6b.jpg
    Anyone here has this problem too?
    Thanks.

    I found out something important. Having the Titles rendered with the Mercury Playback Engine ON causes the problem. Turning it OFF and the titles are the same as shown in the Title Window or in PPro CS4. I'm using a Zotac GTX 285.
    Anyone here has the same problem?
    Thanks.

  • Copying Titles in Title Window causes PPro CS5 to crash

    Hi Community,
    when i copy a title in the title window, PPro CS5 crashes immediately after pressing "STRG+C" or right-click "Copy" (Windows) with a heavy error-message and premiere closes itself. This happens with Mercury Playback Engine ON and OFF.
    Anyone experienced the same problem?
    Greets and thanks.

    I can't reproduce this at all.
    I can cut copy and paste in the title window, create a new title based on the current ine (using the icon top left) and I can cut copy and paste titles in the project window. No crashes at all.
    Can you give us some more exact steps to follow and I'll see if it works here. Include project presets etc.
    Paul.

  • Area Surrounding Mouse Pad-Left and Right-Suddenly Sensitive To Touch

    I have a 13" White MacBook that is suddenly acting really odd. The area (left and right) surrounding the mouse pad has become almost untouchable. If I touch those areas sudden and varying input occurs.
    I write code on occasion and noticed a few days ago that errors would pop up with bizarre text causing the problem. Now, even the slightest touch will cause problems...maybe a copy and or paste, a simple highlight of text, the enter key is pressed, etc....
    My Mac rarely leaves the desk, so no damage has occurred to the hardware.
    Another issue I noticed that started a few weeks ago is that the cursor will go away for a brief second or two.
    Any ideas???
    Thanks...RedRacer123
    Model Name: MacBook
    Model Identifier: MacBook4,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.4 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 3 MB
    Memory: 4 GB
    Bus Speed: 800 MHz
    Boot ROM Version: MB41.00C1.B00
    SMC Version (system): 1.31f1
    Serial Number (system): W8836AGxxxx
    Hardware UUID: 9ABA4ECA-EC9D-5640-8D8F-ED2FA4309934
    Sudden Motion Sensor:
    State: Enabled

    Save your work, connect the power adapter and remove the battery. Does the behavior persist without the battery?
    ~Lyssa

  • Title issue with ppro cs5

    I read this on a Creative Cow forum:
    "Never use premiere for effects, titles, ect. Use After Effects then render it to a uncompressed animation clip - alpha settings selected. reimport to premier lay it down and gaze at beauty. Compression is bad, premier compresses everything it renders, the more you compress-layers, the more degredation and pixelation"
    If this is why my titles look so fuzzy with ppro, can someone give me some advice as to the best workflow?  I have a basic knowledge of after effects.  I have a ppro cs5 project with titles that I have already created.  There are about 10 identical titles (names vary, style, size, do not).  I imagine that  there is an efficient way to do this, help, please...
    Regards,
    Lisa

    I would ignore that post on the Creative COW forum.
    If you have a question about how to best work with titles in premiere Pro, then I recommend asking on the Premiere Pro forum:
    http://forums.adobe.com/community/premiere

  • PPro CS5 will not open now that 5.5 is installed and I need it (Mac)

    I installed premiere pro 5.5 and now the previous version 5.0.4 will not open on my Mac.
    What I really need is the title templates and title font style presets I created in the CS5 version, but I can't find the location to import those. They don't appear to be in /Adobe Premiere Pro CS5/Presets/Templates or /Styles, just the standard ones.
    Where are the user created styles and templates (ones that get customized in premiere not photoshop or anything like that)?
    Why can't I open ppro cs5 anymore?

    I'm not sure how it works on a Mac, but on Windows, styles are saved to a file called "workingset.prsl" unless you specifically create a new style library. You could try searching for that file, and then copy it into the similar path for CS5.5.

  • PPro CS5 GUI on mac really jerky

    Moving clips around on the timeline of CS5 on the mac is like playing Russian roullette; you never know where the clip is actually going to fall. It's like the interface has a refresh rate of 5fps or something. It seems to take forever for clips to snap against each other, and this lag causes the user to think something is wrong and then move the clips around more than necessary.
    Please please tell me that this will be addressed in a point release. I don't want to have to pay to upgrade for a solution to a problem that should never have made it to a full release.

    Hi Jeremy,
    here, when snapping is turned on, the region goes all kind of places (Tries to snap) which is expected (By me at least)
    however, when turning off snapping and just attempting to drag the region from i.e. left to right it feels like it wants to stick to the position where it was previous located. I work fast and scoot regions about all the time. 50% of time I drop the region where I 'thought' it would be in the correct location (Based on the graphical region-representation) but after letting go, the region will position itself differently.
    At the moment I am resorting to alt+arrow-moving the region to get rid of this nuisance!!!
    Jeremy, if you want to get the feel that would LOVE to be in PPRO then do this
    1) Open AE
    2) Create a new Comp
    3) Create a new null and set in & outpoint so that it is shorter than the comp... (So that you can drag it about)
    4) Drag it from left to right etc etc etc... and take note of that feeling.
    Now, go into PPRO and start dragging. You will immediately feel that something is wrong (or better yet, NOT conforming to standard)
    AE is conforming to a standard that I have come to know the past 10 working with either NLEs and DAW (Digital Audio Workstation) Pretty much, ANY app that has a timeline and regions to move about in it...
    PS - Dont wanna coma across as if PPRO aint GREAT. It IS.... Perhaps, THE MOST intuitive NLE I have ever worked with. However, this little drag-thing is really a nuisance...
    To OP...
    THere a MANY ways of positioning a region in PPRO...
    Grab a cup of cappuccino and take a close look at all the shortcuts available.
    There is but ONE missing and I would call it 'Move Clip to PlayHead'
    I would JUMP HOOPS to get that short cut. Basically, all it would do is to place a video clip's (already in the timeline) start or end point right at the playhead. That feature would save my life --- HEY... If I have MISSED it and it is already possible, PLEASE -- Make my day and tell me how
    You can find one 'Move Playhead to Cursor' which is saving me hours per day.
    You will have to assign your own key to it (Not pre-assigned) but what it will do is that where ever your mouse cursor is hovering it will place the playhead. and THAT get really fun if you keep the shortcut depressed. That enables Turbo-shuttling with the mouse as Jog. (Little off topic, sorry)
    Anyway, the point is that in the keycommands there are stuff hidden that can change your workflow. I.e. Opt+LeftArrow will move the selected clip left in time. If you, like me, a lot times wanna drag the clip about 5 frames you are really getting frustrated by PPRO and mouse-dragging. Instead, select the clip and hit opt+Left Arrow 5 times OR opt+sht+LeftArrow to move the clip 5 frames left !

  • Technical problem: PPro CS5.5 won't play DSLR MOVs

    Hello!
    I am new to PPro CS5.5 (first day, actually) and I cannot play back .MOVs from my Canon 5D Mk2 (with audio). Every other file format that I tried worked, which is quite bad because I bought the Production Premium package just to work with DSLR footage.
    It doesn't matter whether I create a sequence (still haven't figured what that is for) with/for the file or not, it doesn't matter what project settings I have. After I start the application I can play (or scrub) DSLR files for ten seconds max before the output starts to jump erratically within the clip (the playhead doesn't) and then turns green (RGB: 0x008600), sometimes interjected with images from other clips that have been played before, sometimes even garbage. There is no recovering from this. All other file formats continue to work fine. "Project New" or exiting the application then may take up to a minute while the program remains unresponsive and looks like it has crashed. It is totally unusable (the competition and every other software works fine with the files).
    I have a Win7 64Bit 3.4GHz Sandybridge system with 16GB RAM. The harddisks are large, fast and quick enough to handle DSLR video. There are no other applications running in the background (really nothing as the computer is of course not connected to the internet) and there's lots of memory and harddisk space available.
    What can I do or what did I do wrong? Thanks in advance.
       ...Mike

    To edit/play MOV you must have Quicktime installed... what version of QT do you have installed?
    CS5 User Guides - online and PDF (right click PDF link to save PDF to your hard drive)
    http://blogs.adobe.com/premiereprotraining/2010/08/help-documents-for-creative-suite-5-pdf -and-html.html
    Here Tutorials
    http://forums.adobe.com/thread/913334
    http://forums.adobe.com/thread/845731?tstart=0
    -and http://forums.adobe.com/message/3234794
    Encore http://tv.adobe.com/show/learn-encore-cs4/
    A "crash course" http://forums.adobe.com/thread/761834?tstart=0
    A Video Primer for Premiere http://forums.adobe.com/thread/498251?tstart=0
    Premiere Tutorials http://forums.adobe.com/thread/424009
    CS5 Premiere Pro Tutorials http://forums.adobe.com/message/2738611
    And http://blogs.adobe.com/premiereprotraining/2010/06/video_tutorials_didacticiels_t.html
    And http://blogs.adobe.com/premiereprotraining/2010/06/how_to_search_for_premiere_pro.html
    CS5 Tutorials http://bellunevideo.com/tutlist.php
    PPro Wiki http://premierepro.wikia.com/wiki/Adobe_Premiere_Pro_Wiki
    Tutorial http://www.tutorialized.com/tutorials/Premiere/1
    Tutorial http://www.dvxuser.com/V6/forumdisplay.php?f=21
    Tutorial HD to SD w/CS4 http://bellunevideo.com/tutorials/CS4_HD2SD/CS4_HD2SD.html
    Premiere Pro Wiki http://premierepro.wikia.com/wiki/Main_Page
    Exporting to DVD http://help.adobe.com/en_US/premierepro/cs/using/WS3E252E59-6BE5-4668-A12E-4ED0348C3FDBa.h tml
    And http://help.adobe.com/en_US/premierepro/cs/using/WSCDE15B03-1236-483f-BBD4-263E77B445B9.ht ml
    Color correction http://forums.adobe.com/thread/892861?tstart=0
    Photo Scaling for Video http://forums.adobe.com/thread/450798?tstart=0
    -Too Large = Crash http://forums.adobe.com/thread/879967?tstart=0
    After Effects Tutorials http://www.videocopilot.net/
    Authoring http://www.videocopilot.net/tutorials/dvd_authoring/
    Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/
    And more Encore http://library.creativecow.net/articles/devis_andrew/
    Surround Sound http://forums.adobe.com/thread/517372

  • Tests with Speech-to-Text transcription in PPro CS5

    As a follow up to my earlier thread about the apparently reworked or, at least, enhanced speech transcription capability in PPro CS5, I just conducted a few tests to see if it is indeed any better than what we had come to expect of it from CS4. The results are, well, encouraging...
    QUICK BACKGROUND: I have an approximately two-minute long voiceover, verbatim from a script, professionally recorded, that was originally delivered to me as a 192kbps, 44.1kHz MP3. Since transcription won't work on MPEG assets (at least, not in the trial which is what I'm using--the files import, but the transcription "analyze" button is grayed out), I used Soundbooth to convert it to a 48kHz, 32-bit floating point WAV. I created a couple of copies, so that each one would have its own transcription metadata. I always used the High quality (slower) option.
    I ran the test four times, as follows:
    Just the WAV, without a reference script
    The WAV with a verbatim reference script as a text document (.txt), with "Script Text Matches Recorded Dialogue" option checked
    The WAV with a verbatim reference script as an Adobe Story script document (.astx), with "Script Text Matches Recorded Dialogue" option checked
    The original MP3 in Soundbooth CS4
    I've linked to a text document with the results of these tests (no editing), along with the original text from the script, if you're interested in seeing how they stack up: right-click and save as.
    As one would imagine, #1 (no script) was... not perfect. However, I think it did a decent enough job for most purposes. Granted, this was a professionally-recorded voiceover, with not competing background noise, but it was still marginally useful. What's funny to note is that the transcription process seems to trip up every now and again and then it seems to lose its momentum for awhile. It'll bobble a "difficult" word, and then for half-a-dozen words following, it's all over the place. Once it regains its footing, though, it'll be pretty much spot on for a sentence or so. Unfortunately, this repeats, but again I think you could make use of it.
    For #2, the transcription was LEAGUES better... but still not perfect. That part is bewildering to me. The transcription generated a couple weird passages--for example "Enjoy" became "and Gillian"--which I could understand if there was NO reference script. However, my impression of how the reference script should work--particularly if the "Script Text Matches Recorded Dialogue" option is activated--is that the transcription should basically copy and paste the reference script into the metadata, NOT invent words and phrases that don't exist in either the script or the dialogue/speech. This process actually preserved capitalization (though punctuation was discarded), so that means it is definitely using that reference script; there is no way to discern capitalization from the spoken word.
    I thought that maybe, just maybe, I could eliminate the anomalies by using Adobe's own script format, generated by the new Adobe Story--hence test #3. I copied and pasted the text into a new Story script, downloaded the ASTX file, and used that as a reference script as above. Unfortunately, it fared no better than the text document (I suppose this makes sense, but I was hoping...), but it was still about 98+% accurate. I'm reasonably satisfied.
    For giggles, I tried test #4, where I used Soundbooth CS4 to transcribe the original MP3 file. Since CS4 doesn't have the reference script capability, this would more or less pit the transcription engine in CS4 against that in CS5. As expected, it turn the dialogue into textual chop suey, BUT... it actually did BETTER than CS5 sans reference script did on some phrases! Observe:
    Original script: Our Club is YOUR CLUB.
    CS5, no script: our love is your laugh
    CS4, no script: our club is your class
    Mish-mash that only Mad Libs could love! For the record, the tests that used the reference scripts were spot-on, capitalization included.
    So, I'm feeling better about using this for the massive documentary and archival project I'm about to embark upon. I have human-typed transcripts for most of the interviews in this project--over 100 interviews, constituting some 200-plus hours--and keeping that text with the footage is going to be a great thing. There are some flaky things--I wish the punctuation could be preserved--but all in all, the reference script addition seems to make this feature much more plausible in a working production environment.

    Did you link the Adobe story script through OnLocation?  For some reason this is required (to my knowledge) to do an exact match.
    When you import an adobe story script into OnLocation; it creates a shot list that is linked to the script.   You then either shoot footage ot fill the shot list; OR link existing assetts to the shot list.  This creates the linkage between the adobe story script and the shot list.
    If you just add itin premire; I think it is the same as just linking a text file.   But if you have ONE assett to ONE script; perhaps you will get the same results anyway.   In Onlocation you can link multiple assets to one script.
    Then all this metadata come in to Pr script attached.
    Some more details pasted from Help:
    Improve speech analysis with Adobe Story, OnLocation, and Adobe Premiere Pro
    You can use Adobe Story, OnLocation, and Adobe Premiere Pro to create the most accurate speech analysis. Import a script written in Adobe Story into OnLocation. OnLocation produces a list of shot placeholders for each scene. Either record these shots using OnLocation during production, or link the placeholder shots to their respective video files when you import the video files into OnLocation. In either case, OnLocation embeds the text for each shot from the original script into the metadata of the shot.
    When you import the clips into  Adobe Premiere Pro, it automatically uses the Adobe Story script as a reference script. When Adobe Premiere Pro finds enough matches with the embedded script, Adobe Premiere Pro replaces the analyzed speech text with the embedded script text. Adobe Premiere Pro carries over correct spelling, proper names, and punctuation from the reference script, benefits that standard speech analysis cannot provide.
    The closeness of the match between the embedded script text and the recorded dialog determines the accuracy of matched-script text. If 100% accuracy is important, edit and revise the script text first. Ensure that the script matches the recorded dialog before using it as a reference script.

  • Partial footage/black screen when replacing footage in PPro CS5

    Let's see if I can get all the relevant info down here.
    Started off with a project in PPro CS5; using two source files (one an MP4 from a Flip cam - not the footage I am having an issue with) the other a direct-stream feed from a 3D application, converted to Lagarith. Both were dragged into the timeline and manually synced so the footage matches up - the MP4 is overlayed over the direct-stream in the corner of the frame, scaled down.
    I have been using the razor tool to cut both sequences into short clips at the same time in the timeline to maintain identical in/out points. The Lagarith-encoded stream is lower resolution than I would prefer, so due to some other additional factors I have taken the stream and scaled it up from the original 640x360 to 1280x720 using a neat app called "Video Enchancer".
    Now, here comes the issue; I have been editing with the 360p footage, and would now like to replace it with the 720p footage (basically proxy editing). "Replace Footage" function to the rescue, right? Apparently wrong.
    Once I replace the footage, most of the timeline gets diagonal stripes across the cut clips, as well as a black screen in the program monitor for preview - indicating that the footage is still missing (though no red "media offline" image). Oddly enough, of the three 360p original files I used to edit with, the first replaced perfectly fine, the second replaced fine up until a certain point, and the third didn't work at all.
    The oddest thing of all, however, is that I can view the replaced footage in the source monitor without any issues, and PPro reports no issues with either the video or the audio stream (audio is uncompressed PCM WAV). I can even drag the replaced footage (now 720p) into the timeline, and watch it in the program monitor.
    The scaled-up 720p footage is of the exact same length as the original 360p footage; down to the frame count. Both are using Lagarith - yet for some reason, replacing the 360p footage with my scaled 720p footage doesn't seem to work correctly. Even selecting "reveal in project" over one of the cut clips that shows no video/audio points me to the correct source file!
    What's going on here?
    If there is any additional info you would need or like, feel free to ask and I'll provide it. Sorry for the long post.

    I'm editing my reply, and going to post a new thread, as I figured out at least what the issue is: PPro is not detecting the correct duration of my footage.
    Message was edited by: XNtricity
    Reason: New, more succinct question needs to be asked, as root cause of problem was discovered.

  • Opened a .ai file, found that left and right side are cut off (landscape vs. regular the issue?)

    Information all in the title.  I open a .ai file and the left and right sides of the image are cut-off based on the "page" box

    Did you open it in a lower version?
    It looks like you opened the PDF part of the file instead of the AI part.

  • Third party garbage matte for ppro cs5?

    Hi there!
    I started using ppro cs5 some months ago, coming from fcp, because of the gamma issue in fcp, because of the fact that you can import Red's r3d's directly and because ppro and redcine x communicate nicely. To my amazement there's no decent way of handling a garbage matte, i.e. smoothing it or using edge feather. I'm not about to spend another large sum on after effects--if it communicates directly with ppro like redcine x I will, but I'm afraid it's a question of exporting and importing, which I really dislike--in other words: does anyone know about a third party plugin with a decent garbage matte for ppro cs5?
    Many thanks,
    Hans

    The build in gargage is no good as you cannot feather it BUT...
    ....you can make your own garbage matte in the Titler. Make a filled bezier shape in pure white.
    superimpose over you footage and add a blur to make it feather.
    Add Track Matte Effect to footage and set this to the matte.
    If you want an animated matte drop the garbage matte effect on a white color matte, add the blur and keyframe the points over time.

  • .dlx-files not loading in PPro CS5

    Hi Community,
    just upgraded from PPro CS4 to CS5 (no Trial). I tried to move the .dlx-videofiles from my Sony DSR-DU1 HDD Drive to PPro CS5 and it says "File Format not supported". The same file on the same machine worked just an hour ago with PPro CS4. Officially .dlx-files are supported (http://help.adobe.com/en_US/premierepro/cs/using/WSd79b3ca3b623cac97fa024001235833a568-800 0.html), but i can't load them into PPro CS5.
    Though Adobe states that .dlx-files are supported they can't be imported to PPro CS5.
    What is the problem?
    Thank you for your help.

    I'm not sure what wasn't compatible, but that list wasn't updated - the VDU support was lost in PPro's port to 64 bit native.
    Sorry

  • Fresh install of PPro CS5.5 on Mac - missing presets and AVCHD support

    Oh, this is crazy.  How on earth is this not bug-fixed?
    I'm in the middle of setting up a new editing suite for my Secondary school where I am a Media Studies teacher.  I've got a handful of Macs running fresh installs which I've installed new legal, site licensed Premiere Pro CS5.5 installs on.  By default, as in many workplaces, the Macs require admin passwords for internet and install settings, which I applied.  None of the machines have had trial versions od PPro CS5.5 or previous versions of PPro.
    The issues:
    None of the fresh installs contain the presets for  AVC-Intra, AVCHD, Digital SLR, XDCAM EX, XDCAM HD422, and XDCAM HD.  Which is kind of a disaster, as we have brand new Panasonic HDC-SD900 AVCHD cameras waiting to load up footage for editing.
    Further to this, none of the macs will load or recognise the AVCHD footage when I try to add it.  I get "unsupported compression type" errors.
    Am I missing something basic here, or am I about to enter the "delete everything adobe, reboot, reinstall, reboot" loop from hell to try and fix an entire roomful of machines?   Is there ANY way to check if the presets are on the Macs?  Is there any way to link them back into PPro if they are?  And finally, is there any way to get CS5.5 to recognise AVCHD as a recognised format (which is why I bought the site license in the first place!  Premiere Pro is meant to have the easiest AVCHD compatibility of all the editing suites!).
    Grr.  Dammit.
    Ideas?

    Okay, this turned out weird.  Fixed now, but WEIRD.  After the deafening silence on this forum, I went and did some reading on other threads and with other people having similar (but it seems not the same) issue.  It seems that there could have been three different causes: here's what I did to fix things, I'd be fascinated if anyone with closer links to Adobe comes up with the technical explanation of why this turned out the way that it did.
    Possible issues:
    (1) Install may need to be done as Admin, rather than standard user on a Mac
    (2) firewall/proxy server maybe isn't allowing some anonymous callback from premiere to adobe to register presets/codecs
    (3) something else weird involving registration... some people have had issues with time zones, of all things.  see below.
    What I did:
    (0) Took everything off the school network and put on my home wireless network: no firewall, direct connection to internet.
    (1) Tried Ann Bens's suggestion above.  Was unable to deactivate software while logged in as Admin on my mac.  Came up with error code 255:255 in the notification box, even though I never had a trial version installed on this box.  This was the same error I got at school, so I'm tentatively ruling out proxy/firewall issues.
    (2) Read the forums some more.  I'm in New Zealand, it's currently daylight savings time (GMT +13) here.  In http://forums.adobe.com/message/4007876, someone in NZ had a different but similar problem with registering/deregistering Premiere Pro software during NZ daylight savings time, and found that changing to ANY other time zone fixed their issue.
    (3) Thought "what the hell", changed the time zone to Samoa (couldn't bring myself to do Australia...) and rebooted as admin.
    (4) Successfully deactivated software, no error messages.  Interesting.
    (5) Uninstalled premiere pro.  Rebooted as admin.
    (6) Ran adobe cleaner tool.  Found some scraps, killed them off.  Rebooted as admin to be on the safe side (still on Samoa time)
    (7) Installed Premiere, no issues at all.  Registered, no issues at all.  All preset settings present and correct, no issues getting AVCHD files.
    (8) Changed time zone to NZ day light savings time. 
    (9) Everything still works.
    Hm.  Adobe, SOMETHING is wrong with the way your software is handling timezones and registration of codecs/software on Premiere Pro CS5.5.  Seriously, does anyone have a clue why this might be happening?
    So, solved.  Shall I give myself a tick for "correct answer" and "helpful answer", given I solved my own thing with no help from tech support?

  • PPro CS5 not talking to NVidia Quadro 4000...

    Apologies in advance if this has been covered a million times on here (and feel free to point me to a thread), but...I have a new Mac setup, Adobe PPro CS5, and the NVidia Quadro 4000 card with MPE/Cuda. And PPro is not using the GPU.
    I do have the latest drivers (for the card and for CUDA). The card was installed a month ago and I grabbed the drivers at that time.
    Recently I worked on a simple 7-minute non-HD video, with no effects and minimal editing...and the publish time was 7 minutes or so.
    I was expecting faster. And while it was publishing, my computer's CPU gauge said it was running at around 90%. I made sure the PPro project setting pointed towards the card GPU.Obviously the MPE and/or CUDA is not kicking in.
    I have spoken to PNY (where I bought the Nvidia card) and they said if I have the latest drivers and could actually see something on my screens, then the card is working and...you know...it must be a problem with the PPro aoftware.
    Oh, the Mac is a 2010 model, 8-core with a ton of RAM on it.
    Thoughts?
    John

    You are not understanding how the MPE engine works. The MPE engine does not lower the overall load of the CPU as far as usage. It lowers the instructions ie the types of code/threads it has to handle in a given time period. The CPU has to handle all  of the Decoding/encoding of the codecs/ie material that you are using. It will also have to process any non accelerated effects. It also handles all memory management and interrupts that is required by the applications, machine code, and hardware. The GPU handles the scaling, interpolation, and some of the effects besides drawing and GUID code. The CPU has to process the Decode then cache the material to ram so it can cache over to the GPU card Ram for CUDA processing. Once threading is done via the GPU then it caches back to the system ram for the CPU to final encode and adjust further frame data for effects. All of this means the entire pipeline happens faster the more load the CPU can handle focused on specific functions and at what GHz those process through the system during a given time. So basically the MPE allows the system to process more work in a given time period simultaneously essentially. So the higher the load on your CPU the faster your entire workflow will process. In simple terms, this means you want the highest CPU load you can get because that means the GPU, system ram, disks, or board throughput is not slowing anything down. Your at 62%. That means your system somewhere in the pipeline is not allowing the cpu to run at max performance in that given time period. I hope that clarify's what you are seeing and why.
    And yes, OS/Application threading and caching is also included in not allowing the CPU to run at max capacity.
    Eric
    ADK

Maybe you are looking for