Is a MPEG h264 faster to render than a QuickTime PNG?

I have a 2 minute composition (1920 x 1080). I renered it out once as a mpeg 4 (h264) and resized the final output to 852 x 480. It took roughly 12 minutes. I rendered it out again at the full size (1920 x 1080) as a Quick Time with the PNG sequence codec. It takes over an hour. I know the Quick Time with the PNG sequence codec is a much more high resolution format....so that is why it took longer to render, right?

I was going to ask you about MP.... MOST MOVIE CODECS, avi, mov, wmv, do not support multi processing Some kill it badly. I only have MP turned on if I am not using AE's 3D Ray-tracing turned on, I am not using any 3rd party plug-ins, I am not rendering audio, I am rendering to an image sequence. That's more than 95% of the time that I have MP rendering turned off.
How can I take the increase in rendering time you ask? Simple, I never wait for renders unless all my other work is done. I do my work in AE, send the Comps to the Adobe Media Encoder, then jump back in AE, or Premiere, or Photoshop and continue my work as my projects render in the background. That's the only way I can be productive. Working in AE, droping a comp in the Render Cue and then waiting for the render to move to the next step is just not an option. I have not worked that way, or cued things up to render overnight, since the AME has been available.
Disk cache, caching previews in the background, and the other workflow improvements do make AE easier to use, and I utilize them but never at full rez. I also never do full frame full rez ram previews, seldom do ram previews longer than a few seconds, or waste time looking at things over and over again and tweaking a frame or two here and there that isn't perfect. Once you gain some experience you will know what you've got when you set up your animation, check a few motion tests, color correct a few critical frames, and send things off to render. I spent years shooting 16mm and 35mm film and sending it off to the lab and except for a very few occasions the first 3 months of my career, I got back exactly what I expected. It's all a part of learning your craft.

Similar Messages

  • HT3775 I have a webpage where I embeded more than 2 quicktime players. I want that at a time , only one player is played. When second player is played the first one should stop. I am using simple EMBED / OBJECT tags to embed the player.

    I have a webpage where I embeded more than 2 quicktime players. Only one player need to play at a time. When second player is played the first one should stop. I am using simple EMBED tags to embed the player.

    I have a webpage where I embeded more than 2 quicktime players. Only one player need to play at a time. When second player is played the first one should stop. I am using simple EMBED tags to embed the player.

  • Large h264 files on render

    I'm having a problem with AME rendering out files 3 to 4 time larger than "normal". That is, when I render out a similar file the size should be around 3GB and now they are rendering out at over 10GB.
    These are two camera multi-track files using the H264/Vimeo 1080p 29.97 preset.
    When I called Adobe on this a couple of weeks ago, they removed Premiere and reinstalled 8.1. That seemed to fix the problem. However, I saw an update the other day, installed it and I'm back to the same problem.
    Going through the process of uninstalling and reinstalling both Premiere Pro and AME.
    Anyone else experiencing this issue? I'm wondering if it's a Yosemite problem?
    Thanks,
    John

    Like you, I'm not "hot" on knowing exactly when to change any of the settings, though I've found that for some of my work some alterations are better ... and had to figure those out mostly with help and then save that as a preset 'cause I'm *not* going to remember the details.
    Now that we've got this up, let's see if Bill Gehrke or Ann Bens or SAFEHARBOR11 can pop in ... they might give some intelligent help.
    Neil

  • Faster video conversions than itunes?

    ive tried usind the itunes video conversions and its agonizing slow is there any program i can download thats faster at converting videos to mp4?

    ive tried usind the itunes video conversions and its agonizing slow is there any program i can download thats faster at converting videos to mp4?
    The QT preset used by iTunes is a high quality, H.264, multi-pass conversion and, therefore, very slow. If you have QT Pro installed, you can always perform the conversion in the single pass mode which would take half as long or switch to the MPEG4/AAC converter in either single or multi-pass mode -- both of which are faster than the more complex H.264 codec but require larger files for the same level of quality.
    If you don't have QT Pro installed, then you can download MPEG Streamclip (free) and use the iPod H.264 preset which is, by default, a single-pass converter. If you go this route, be sure to read the instructions carefully regarding the QT Player vs the alternative QT and MPEG2 codec installation.

  • Video streaming faster on 3G than WIFI?

    I've noticed that when watching Youtube or QT streams that they are much faster to load on the cell networks than on WIFI. Correct me if I'm wrong but it looks like the iPhone streams a higher quality video when connected to the WIFI? This is all good except the result is that it takes SO much longer to download.
    More often than not I'm perfectly happy with the lower picture quality. Is there any way to force the phone to always download the lower quality video?
    I know I can turn WIFI off but then I'm using up my cell data which isn't very cost-effective.

    I dont think that might be the problem. My roomate and I did a speed test with his iPod touch 2g on the same video. His loaded the 2m36s video in about ten seconds. My brand new iPhone never even began loading the video until about 30s later. Then the video took about 15m to fully load.

  • Speedgrade FX freeze rendering or take up to 4x longer to render than Magic Bullet Looks

    I've found that using a lumetri "preset" on a clip, the clip is played back beautifully in real time, however, when using my own speedgrade looks (with 2-3 looks layers) the clip plays back choppy (which is normal as it happens with magic bullet looks).  But.... when it comes time to render... The sequence graded with Magic Bullet Looks takes as long as it always has in CS6, while the same sequence graded with my Speedgrade presets takes up to 4x longer and sometimes even freezes (causing an unknown error) both in Encoder CC  and when exporting straight out of PPro CC.... 
    I'm working with the untranscoded .MOV video files from my Nikon D7000
    my machine is
    15in Macbook Pro Late 2011
    2.4 Ghz Intel Core i7
    16 GB 1333 MHz DDR3
    AMD Radeon HD 6770M 1024 MB
    OSX 10.8.4 (12E55)
    I'm not sure if it's a bug or a settings issue... just trying to find out if anyone else is having the same problem.  Thanks. 

    True... an oversight of a first time poster... Exporting is exactly what I meant... as a matter of fact regarding rendering int he timeline... ... when applying the Magic Bullet effect, you get the red bar and you can render and then you're all set... with the speed grade (presets or my own) it just remains with the yellow bar and plays a bit choppy, some effects more than others, but when it's time to export that's when it either does it extremely slow, freezes or displays the unknown error message...
    I do like being able to create these looks with speedgrade and i thought it was an awesome step forward, but i'm not sure what i'm doing wrong as i don't think they would design it to take so much longer to export than MBL...
    this is the link to my SG file... it's in a zip as exported looks from Speegrade    
    http://depositfiles.com/files/zdzbjucb1

  • Airport Fast on Windows than Mac

    Airport Express / PBG4 1.5ghz 1GB RAM OsX 10.4.11 / HP Compaq Pentium 4 WIndows XP 512MB RAM
    Both running Safari 3.
    I find that the PC is much faster on my ADSL conection via Airport & Ethernet than my PowerBook G4.
    Is there any particular reason for this?
    Christo.

    davidoff wrote:
    Arguably an R rather than Arch question I realize but:
    my colleague and I both have brand new Lenovo ThinkCentres.  Same specs but he has more RAM (I don't think that's the issue).  We run the same program
    length <- 2*10^6
    a <- runif(length)
    b <- runif(length)
    print(summary(lm(a~b)))
    I take 16 seconds in Arch 64, but never bump against a memory constraint (looks like about 1/3 of RAM used max).
    My colleague, with Windows, takes 7 seconds.
    The R documentation says 32 bit R is about 10% faster in some cases, but that doesn't explain a 50% difference.
    I *think* I have compiled 32 bit R on my system and it doesn't seem to go any faster.
    By contrast I run a python loop a bit faster than my colleague.
    Thoughts?
    If I run that on my Arch64 box, it takes 23 sec.  If I run it a second time it takes 6 sec.
    Jay

  • Mpeg 2 audio much louder than H.264???

    Hey all,
    For the last year I've been exporting past projects as H.264s and flipping them to mpeg2 TS on my PC. More recently I've been playing around with mpeg2 settings in Compressor to trim a step off the whole process. All the mpeg2 settings I'm using are working great, save for the audio. I set all my ads to -12dB in Final Cut. After I send a spot to Compressor and throw the mpeg2 preset on it, it is noticeably louder than it should be. I watch the .m2t files back with MPEG Streamclip. As a test I exported a .aiff file from streamclip and imported it into Final Cut and it's upwards of 6 dB louder than it should be.
    I can't find ANYTHING on the internet about this or how to fix it. What am I missing? Help me, please!

    To make sure the Dolby AC3 setting does not alter your audio with normalization or compression, you need to turn off dialog normalization and compression.
    a) Click your audio setting and have a look at the Encoder tab in the Inspector window.
    b) Under the Audio tab, change the Dialog Normalization from -27 to -31 to disable it.
    c) Click the Preprocessing tab and set the Compression Preset to None.
    d) Deselect the Low-Pass Filter and DC Filter
    Compressor User Manual -> Creating Dolby Digital Professional Output Files
    Important: It is critical that you set the Dialog Normalization setting correctly if you intend to use any of the Compression Preset settings. The Compression Preset settings assume that the audio, after the dialogue has been normalized, is at the normal listening level of 31 dBFS. Levels that are consistently louder than that result in distorted sound and erratic levels.
    If you do not know the sound level of the source file or for some other reason want to ensure the Dolby Digital Professional encoder does not affect your sound levels, enter –31 for the Dialog Normalization and choose None in the Compression Preset pop-up menu (located in the Preprocessing tab).

  • Firefox: Faster under WINE than Native?

    I just got sent this link: http://tech.slashdot.org/article.pl?sid … 13/0058251
    Apparently, the windows version of Firefox runs better under wine than the native linux version, possibly because the linux version isn't optimized.  Can anyone take a look at this and see if they can confirm it?

    kensai wrote:Yeah, there is no difference between the same machine running windows and firefox than linux and firefox. The difference is only when it is run on wine, so this is even better for the wine developers.
    That is definitely not true in my tests.  I've done it multiple times, because I though that openjdk6 and jde/jre could make a difference, and I always got results that were consistent with the findings of the Slashdot article.  I tested on a fairly slow computer (Intel Atom based netbook) and the performance differences were very clear.  I'm not sure why others are getting different results -- perhaps pgo-optimized builds of Firefox are slower than the generic Arch build?  I'm very skeptical of those findings that claim that performance is the same in Linux and Windows, because Linux/Windows performance actually differs for every individual test in sunspider test suite -- in some cases Linux is actually faster, but in most cases Windows versions of Firefox performs better.
    Last edited by fwojciec (2009-02-25 06:32:43)

  • MPEG-4 and Realtime Render

    Hi: if I Import an MPEG-4 Video (shot on my Direct to Disk Digital Video Camera) can FCP configure to accept it natively so it doesn't have to Realtime Render to play it ? (I see an H.264 Easy Setup but not MPEG-4, I'm still new so I may have missed something) Thanks, MLR
    MacBook Pro 17" 2.16GHz 2GB RAM 100GB Drive 7200rpm 256MB Graphics   Mac OS X (10.4.6)   FinalCutStudio5.1, LogicPro7.2, 12" G4 PowerBook 867MHz 640MB RAM Panther
    MacBook Pro 17" 2.16GHz 2GB RAM 100GB Drive 7200rpm 256MB Graphics   Mac OS X (10.4.6)   FinalCutStudio5.1, LogicPro7.2, 12" G4 PowerBook 867MHz 640MB RAM Panther
    MacBook Pro 17" 2.16GHz 2GB RAM 100GB Drive 7200rpm 256MB Graphics   Mac OS X (10.4.6)   FinalCutStudio5.1, LogicPro7.2, 12" G4 PowerBook 867MHz 640MB RAM Panther

    Try this tip:
    www.proapptips.com/shane Editing with non-native codecs in FCP.
    Shane

  • Faster Hard Drive than Stock

    I want to upgrade my HD to something faster than the stock hard drive that comes with the system, but is still pretty quiet. The standard HD is very quiet and I'd like to sacrifice just a little noise for some performance. Any upgrade suggestions?

    You'll find suitable drives at the following:
    MacSales.com
    Buy.com
    NewEgg.com
    As well as other online retailers you can find using Google. As for speed you really haven't too much choice. Notebook drives are either 5400 RPM or 7200 RPM (more RPM, faster drive) and cache sizes of 8 MBs, 16 MBs, or 32 MBs (larger is faster/better.) Most drives are fairly quiet.
    You can find drive benchmarks at Bare Feats, Storage Review, or Tom's Hardware Reviews.

  • Different resolution in render than in scene Premier and Ae

    Hello,
    Got this weird problem..
    My scene size is 2568x 768 px (yes its weird reso, we use pandoras box to map different sections of this resolution)
    and when i render it out with premier the reso is only 1920 x 592?
    What could be wrong with my rendering settings? Have double checed it many times.
    Same kind of trouble with Ae, but when render it out there is those black blocks witch takes certain area of my reso?
    P.s. I am new with Premier, why cant i change frame (scene) resolutions during editing? Is there some purpose?
    In Ae its easy, just from comp settings..
    Thanks,
    Kalle

    The answer to the question "Why" is pretty simple. We used to spend hours and hours helping people who had fouled up their sequence settings.
    It is much easier to tell them to drop the video on the "New Item" button. That creates a sequence of exactly the right size.
    In your case, you should drop one video on the new item button, delete it of of the timeline, then copy and paste everything on that new timeline as suggested by Joe in Post #1. 
    I just tried creating a sequence wth the settings of 2568X768 using 29.97 and square pixels. I started creating the sequence by using the standard DSLR 1080p30 preset, then I went into the Settings tab and changed the frame size.
    I then put a large still on the timeline and exported it. Once again, I started with the YouTube 1080p settings for 29.97 and then changed the frame size. I had to unlock the link between the Height and Width to get the ratio I wanted, and to do that I had to increase the Profile to high, which messed with my frame rate, so I had to change the frame rate back to 29.97.
    The export came out at exactly the right size. Note: Do not use the render files. They will just get you into trouble.

  • 10g query running faster with RBO than CBO

    I am running a query in Oracle 10g that is taking 1minute 15 seconds to run using the CBO. All the tables and indexes in the query are fully analyzed. However if i add a /*+ Rule */ hint to the query and force the optimizer to RBO it runs in 5 seconds.
    Anyone any ideas why this would occur? it's contrary to everything Oracle says about CBO and problematic as RBO is no longer supported in 10g
    Any help / advice greatfully appreciated
    Thanks
    Declan

    My "best" CBO explain plan is......
    Explain complete.
    Elapsed: 00:00:01:90
    PLAN_TABLE_OUTPUT                                                                                                                           
    | Id  | Operation                          |  Name                          | Rows  | Bytes |TempSpc| Cost  |                               
    |   0 | SELECT STATEMENT                   |                                |  3364K|  2553M|       |   666K|                               
    |   1 |  SORT ORDER BY                     |                                |  3364K|  2553M|  5840M|   666K|                               
    |   2 |   VIEW                             |                                |  3364K|  2553M|       |   273K|                               
    |   3 |    UNION-ALL                       |                                |       |       |       |       |                               
    |*  4 |     HASH JOIN                      |                                |  2269K|  1415M|       |   255K|                               
    |*  5 |      TABLE ACCESS FULL             | NODE                           |     6 |   198 |       |   183 |                               
    |*  6 |      HASH JOIN OUTER               |                                |  2269K|  1344M|       |   255K|                               
    |*  7 |       HASH JOIN                    |                                |   710 |   266K|       |  2179 |                               
    |*  8 |        HASH JOIN OUTER             |                                |  1219 |   165K|       |   355 |                               
    |*  9 |         HASH JOIN                  |                                |  1219 |   154K|       |   318 |                               
    |* 10 |          HASH JOIN                 |                                |  1219 |   138K|       |   260 |                               
    |* 11 |           HASH JOIN                |                                |  1219 |   127K|       |   224 |                               
    |  12 |            TABLE ACCESS FULL       | TMP_NODE_WALK_ALL_NODES        |  8168 |   311K|       |    17 |                               
    |* 13 |            HASH JOIN               |                                | 10896 |   723K|       |   201 |                               
    |  14 |             INDEX FAST FULL SCAN   | PK_NODE_RULES_NODE_ID_RULE_ID  | 10896 |   106K|       |     6 |                               
    |  15 |             TABLE ACCESS FULL      | NODE                           | 73004 |  4134K|       |   183 |                               
    |  16 |           INDEX FAST FULL SCAN     | IDX_NODE_CIX2                  | 73004 |   641K|       |    33 |                               
    PLAN_TABLE_OUTPUT                                                                                                                           
    |  17 |          INDEX FAST FULL SCAN      | IDX_NODE_CIX1                  | 73004 |   998K|       |    54 |                               
    |  18 |         INDEX FAST FULL SCAN       | IDX_NODE_CIX2                  | 73004 |   641K|       |    33 |                               
    |* 19 |        TABLE ACCESS FULL           | RULES                          |  6344 |  1517K|       |  1820 |                               
    |  20 |       VIEW                         |                                |   405M|    89G|       | 43581 |                               
    |* 21 |        HASH JOIN OUTER             |                                |   405M|    23G|       | 43581 |                               
    |  22 |         TABLE ACCESS FULL          | TMP_NODE_WALK_ALL_NODES        |  8168 |   103K|       |    17 |                               
    |  23 |         TABLE ACCESS FULL          | UNIVERSAL_RULES                |  3377K|   157M|       | 43256 |                               
    |* 24 |     HASH JOIN OUTER                |                                |  1094K|   410M|   148M| 17453 |                               
    |  25 |      MERGE JOIN CARTESIAN          |                                |   390K|   143M|       | 15029 |                               
    |  26 |       NESTED LOOPS                 |                                |    70 | 25060 |       |  2849 |                               
    |  27 |        NESTED LOOPS                |                                |    70 | 21000 |       |  2779 |                               
    |  28 |         TABLE ACCESS BY INDEX ROWID| UNIVERSAL_RULES                |  1392 | 76560 |       |  1387 |                               
    |* 29 |          INDEX RANGE SCAN          | IDX_UNIVERSAL_RULES_ACCOUNT    |  1392 |       |       |     6 |                               
    |* 30 |         TABLE ACCESS BY INDEX ROWID| RULES                          |     1 |   245 |       |     1 |                               
    |* 31 |          INDEX UNIQUE SCAN         | PK_RULES_RULE_ID_VERSION_ID    |    20 |       |       |       |                               
    |* 32 |        TABLE ACCESS BY INDEX ROWID | NODE                           |     1 |    58 |       |     1 |                               
    |* 33 |         INDEX UNIQUE SCAN          | PK_NODE_NODE_ID                |     6 |       |       |       |                               
    |  34 |       BUFFER SORT                  |                                |  5616 |   153K|       | 15028 |                               
    |  35 |        TABLE ACCESS BY INDEX ROWID | NODE                           |  5616 |   153K|       |   174 |                               
    |* 36 |         INDEX RANGE SCAN           | IDX_NODE_NODE_TYPE_ID          |  5616 |       |       |    11 |                               
    |* 37 |      INDEX FAST FULL SCAN          | IDX_RULES_RULE_ID_STATUS       | 42293 |   289K|       |    48 |                               
    PLAN_TABLE_OUTPUT                                                                                                                           
    Predicate Information (identified by operation id):                                                                                         
       4 - access("NODE"."NODE_TYPE_ID"="SN"."HIERARCHY_TYPE_ID")                                                                               
       5 - filter("NODE"."PARENT_NODE_ID" IS NULL)                                                                                              
       6 - access("SYS_ALIAS_1"."RULE_ID"="UR"."RULE_ID"(+) AND "SYS_ALIAS_1"."VERSION_ID"="UR"."VERSION_ID"(+))                                
       7 - access("NR"."RULE_ID"="SYS_ALIAS_1"."COMBINED_RULE_ID")                                                                              
       8 - access("SN"."PARENT_NODE_ID"="SP"."NODE_ID"(+))                                                                                      
       9 - access("AN"."START_NODE_ID"="SN"."NODE_ID")                                                                                          
      10 - access("AN"."EFFECTIVE_NODE_ID"="EN"."NODE_ID")                                                                                      
      11 - access("AN"."SHORTCUT_NODE_ID"="N"."NODE_ID")                                                                                        
      13 - access("N"."NODE_ID"="NR"."NODE_ID")                                                                                                 
      19 - filter(',A,P,' LIKE '%,'||"SYS_ALIAS_1"."STATUS"||',%')                                                                              
      21 - access("UR"."NODE_ID"(+)="AN"."START_NODE_ID")                                                                                       
      24 - access("R"."RULE_ID"="RP"."RULE_ID"(+))                                                                                              
      29 - access("UR"."ACCOUNT_ID"='0069')                                                                                                     
      30 - filter(',A,P,' LIKE '%,'||"R"."STATUS"||',%')                                                                                        
      31 - access("UR"."RULE_ID"="R"."RULE_ID" AND "UR"."VERSION_ID"="R"."VERSION_ID")                                                          
      32 - filter("N"."HIERARCHY_TYPE_ID"=9)                                                                                                    
    PLAN_TABLE_OUTPUT                                                                                                                           
      33 - access("UR"."NODE_ID"="N"."NODE_ID")                                                                                                 
      36 - access("NODE"."NODE_TYPE_ID"=9)                                                                                                      
      37 - filter("RP"."STATUS"(+)='P')                                                                                                         
    Note: cpu costing is off                                                                                                                    
    28 rows selected.
    Elapsed: 00:00:02:45
    68 rows selected.
    Elapsed: 00:00:05:76While my RBO explain plan is
    Explain complete.
    Elapsed: 00:00:01:23
    PLAN_TABLE_OUTPUT                                                                                                                           
    | Id  | Operation                                |  Name                        | Rows  | Bytes | Cost  |                                   
    |   0 | SELECT STATEMENT                         |                              |       |       |       |                                   
    |   1 |  SORT ORDER BY                           |                              |       |       |       |                                   
    |   2 |   VIEW                                   |                              |       |       |       |                                   
    |   3 |    UNION-ALL                             |                              |       |       |       |                                   
    |   4 |     MERGE JOIN OUTER                     |                              |       |       |       |                                   
    |   5 |      SORT JOIN                           |                              |       |       |       |                                   
    |*  6 |       TABLE ACCESS BY INDEX ROWID        | NODE                         |       |       |       |                                   
    |   7 |        NESTED LOOPS                      |                              |       |       |       |                                   
    |   8 |         NESTED LOOPS                     |                              |       |       |       |                                   
    |   9 |          NESTED LOOPS                    |                              |       |       |       |                                   
    |  10 |           NESTED LOOPS                   |                              |       |       |       |                                   
    |  11 |            NESTED LOOPS                  |                              |       |       |       |                                   
    |  12 |             NESTED LOOPS OUTER           |                              |       |       |       |                                   
    |  13 |              NESTED LOOPS                |                              |       |       |       |                                   
    |  14 |               TABLE ACCESS FULL          | TMP_NODE_WALK_ALL_NODES      |       |       |       |                                   
    |  15 |               TABLE ACCESS BY INDEX ROWID| NODE                         |       |       |       |                                   
    |* 16 |                INDEX UNIQUE SCAN         | PK_NODE_NODE_ID              |       |       |       |                                   
    PLAN_TABLE_OUTPUT                                                                                                                           
    |  17 |              TABLE ACCESS BY INDEX ROWID | NODE                         |       |       |       |                                   
    |* 18 |               INDEX UNIQUE SCAN          | PK_NODE_NODE_ID              |       |       |       |                                   
    |  19 |             TABLE ACCESS BY INDEX ROWID  | NODE                         |       |       |       |                                   
    |* 20 |              INDEX UNIQUE SCAN           | PK_NODE_NODE_ID              |       |       |       |                                   
    |  21 |            TABLE ACCESS BY INDEX ROWID   | NODE                         |       |       |       |                                   
    |* 22 |             INDEX UNIQUE SCAN            | PK_NODE_NODE_ID              |       |       |       |                                   
    |  23 |           TABLE ACCESS BY INDEX ROWID    | NODE_RULES                   |       |       |       |                                   
    |* 24 |            INDEX RANGE SCAN              | IDX_NODE_RULES_NODE_ID       |       |       |       |                                   
    |* 25 |          TABLE ACCESS BY INDEX ROWID     | RULES                        |       |       |       |                                   
    |* 26 |           INDEX RANGE SCAN               | IDX_RULES_COMBINED_RULE_ID   |       |       |       |                                   
    |* 27 |         INDEX RANGE SCAN                 | IDX_NODE_NODE_TYPE_ID        |       |       |       |                                   
    |* 28 |      SORT JOIN                           |                              |       |       |       |                                   
    |  29 |       VIEW                               |                              |       |       |       |                                   
    |  30 |        NESTED LOOPS OUTER                |                              |       |       |       |                                   
    |  31 |         TABLE ACCESS FULL                | TMP_NODE_WALK_ALL_NODES      |       |       |       |                                   
    |  32 |         TABLE ACCESS BY INDEX ROWID      | UNIVERSAL_RULES              |       |       |       |                                   
    |* 33 |          INDEX RANGE SCAN                | IDX_UNIVERSAL_RULES_NODE     |       |       |       |                                   
    |  34 |     NESTED LOOPS OUTER                   |                              |       |       |       |                                   
    |  35 |      NESTED LOOPS                        |                              |       |       |       |                                   
    |  36 |       NESTED LOOPS                       |                              |       |       |       |                                   
    |  37 |        NESTED LOOPS                      |                              |       |       |       |                                   
    PLAN_TABLE_OUTPUT                                                                                                                           
    |  38 |         TABLE ACCESS BY INDEX ROWID      | NODE                         |       |       |       |                                   
    |* 39 |          INDEX RANGE SCAN                | IDX_NODE_NODE_TYPE_ID        |       |       |       |                                   
    |  40 |         TABLE ACCESS BY INDEX ROWID      | UNIVERSAL_RULES              |       |       |       |                                   
    |* 41 |          INDEX RANGE SCAN                | IDX_UNIVERSAL_RULES_ACCOUNT  |       |       |       |                                   
    |* 42 |        TABLE ACCESS BY INDEX ROWID       | NODE                         |       |       |       |                                   
    |* 43 |         INDEX UNIQUE SCAN                | PK_NODE_NODE_ID              |       |       |       |                                   
    |* 44 |       TABLE ACCESS BY INDEX ROWID        | RULES                        |       |       |       |                                   
    |* 45 |        INDEX UNIQUE SCAN                 | PK_RULES_RULE_ID_VERSION_ID  |       |       |       |                                   
    |* 46 |      INDEX RANGE SCAN                    | IDX_RULES_RULE_ID_STATUS     |       |       |       |                                   
    Predicate Information (identified by operation id):                                                                                         
       6 - filter("NODE"."PARENT_NODE_ID" IS NULL)                                                                                              
      16 - access("AN"."START_NODE_ID"="SN"."NODE_ID")                                                                                          
      18 - access("SN"."PARENT_NODE_ID"="SP"."NODE_ID"(+))                                                                                      
      20 - access("AN"."EFFECTIVE_NODE_ID"="EN"."NODE_ID")                                                                                      
      22 - access("AN"."SHORTCUT_NODE_ID"="N"."NODE_ID")                                                                                        
      24 - access("N"."NODE_ID"="NR"."NODE_ID")                                                                                                 
      25 - filter(',A,P,' LIKE '%,'||"SYS_ALIAS_1"."STATUS"||',%')                                                                              
    PLAN_TABLE_OUTPUT                                                                                                                           
      26 - access("NR"."RULE_ID"="SYS_ALIAS_1"."COMBINED_RULE_ID")                                                                              
      27 - access("NODE"."NODE_TYPE_ID"="SN"."HIERARCHY_TYPE_ID")                                                                               
      28 - access("SYS_ALIAS_1"."RULE_ID"="UR"."RULE_ID"(+))                                                                                    
           filter("SYS_ALIAS_1"."VERSION_ID"="UR"."VERSION_ID"(+) AND                                                                           
                  "SYS_ALIAS_1"."RULE_ID"="UR"."RULE_ID"(+))                                                                                    
      33 - access("UR"."NODE_ID"(+)="AN"."START_NODE_ID")                                                                                       
      39 - access("NODE"."NODE_TYPE_ID"=9)                                                                                                      
      41 - access("UR"."ACCOUNT_ID"='0069')                                                                                                     
      42 - filter("N"."HIERARCHY_TYPE_ID"=9)                                                                                                    
      43 - access("UR"."NODE_ID"="N"."NODE_ID")                                                                                                 
      44 - filter(',A,P,' LIKE '%,'||"R"."STATUS"||',%')                                                                                        
      45 - access("UR"."RULE_ID"="R"."RULE_ID" AND "UR"."VERSION_ID"="R"."VERSION_ID")                                                          
      46 - access("R"."RULE_ID"="RP"."RULE_ID"(+) AND "RP"."STATUS"(+)='P')                                                                     
    Note: rule based optimization                                                                                                               
    28 rows selected.
    Elapsed: 00:00:04:42
    78 rows selected.
    Elapsed: 00:00:08:86Any additional help appreciated
    I am going to try and run a trace against the sql now and see if i can get any more information
    Thanks in advance
    Declan

  • Upload time faster on wintel than solaris

    I posted a similar question before but have not resolved the issue so...
    I setup WLS 6.1 on a wintel, 500MHz laptop
    and WLS6.1 on a E220R running Solaris 8
    my client browser is IE 5.5 running on Win2k
    I tested the time it takes to upload a file using the console to upload an
    EAR file
    when I upload a 2.5Mb EAR to wintel it takes about 5 seconds to upload and
    install
    on the solrais box it takes about 35 seconds, most of this time is spend
    uploading the file
    why is it so much slower to upload to solaris?
    any help on this will be greatly appreciated
    Jim Durnford [email protected]

    Thanks for the tips, Varjak.
    I never use so-called 'download accelerators', nothing like more useless software on the system.
    My anti-virus programs and settings are such that they don't affect my downloads.  Anything that I download from other sites (Google, Netflix, etc) come in at similar speeds regardless of whether I'm on the PC, Mac, tablet, or whatever.
    It's not really an issue, I was just curious if anyone else has compared their PC vs. Mac and noticed the same thing I experience.
    This happens across all other OS's, not just Windows.  The Mac isn't faster anywhere else only on the Apple-based iTunes.  I just find it funny and it wouldn't surprise me at all if their system 'sniffs out' Macs and gives them the fast lane for downloading from iTunes!

  • CS 5 OnLocation not any faster with HDV than CS3?

    I've been using CS3's OnLocation for dozens on on-site shoots for several years now and regularly sings it praises wherever I travel.  I've used an older 2.1 Ghz single processor Dell laptop, and more recently been using a Quad-core I-5 Toshiba.  My primary camera is a Canon XHA1s; among others, I also use a Sony FX7 and Z5U.
    Recently I've been increasingly shooting HDV to tape with a desire to capture same to my laptop using OnLocation with its field monitor.  After initial testing showed ongoing artifacts in my video stream (both recorded and on-screen), I changed to an external SIIG Firewire card which completely resolved those problems for artifact-free footage.
    One problem which remained, however, is unacceptable field monitor performance using OnLocation with HDV.  With full frame-rate features enabled, I was getting as much as a 10-second lag time! (yes.. 10 SECONDS).  When I cut back which frames are being displayed (OnLocation settings), the lag goes down somewhere between .5 and 1 second (still pretty bad IMO), and is pretty stuttery.
    I was hoping that CS5's OnLocation would be more optimized for HDV and perform better, and installed a friend's version of CS5 OnLocation to test this out.  Sadly, not only did it perform *NO BETTER*, but after some period of capturing (10 minutes one time, an hour another time.. did not seem consistent) the laptop's screen would go blank (not off) and the computer remained unresponsive (required a hard boot).  After this repeated several times, I tried using CS3's OnLocation again, but it too was experiencing the "blank screen then lock the laptop" problem -- although I haven't tested it, I do hope that uninstalling CS5's OnLocation and re-installing CS3's will remove the offending DLL or Codec and avoid future "lock-up" problems.
    My question here is -- is the lag and stuttery (like a low frame rate or shutter speed) field monitor the expected behaviors with OnLocation and HDV?  Yeah yeah.. I've read excuses that "HDV requires more processing" but I've captured and previewed full framerate HDV using Sony Vegas's capture while simultaneously capturing a DV stream using the same software, and had no issues at all while experiencing fluid previews.
    Any thoughts on what's going on?  If I knew CS5 would fix the problem and/or was more optimized, I'd happily pay for the upgraded Master Collection, but my experience has not proven so well
    Help?!
    :-/ Rob

    heres a test. try importing a single 42gb timeline of 1080p into encore cs5, and now do the same thing for cs6. rendering may or may not be faster for menus, but you can get right to work on your project in cs6, while it processes in the background, vs cs5 having to stare at the yellow status bar for 90 minutes (it seemed, lol)

Maybe you are looking for