Buffer Hit Ratio % -- Whats the right query ?

Whats the right query to track Buffer Hit % ;
Using this :
prompt BUFFER HIT RATIO %
prompt ===============
select 100 * ((a.value+b.value)-c.value) / (a.value+b.value) "Buffer Hit Ratio"
from v$sysstat a, v$sysstat b, v$sysstat c
where
a.statistic# = 38
and
b.statistic# = 39
and
c.statistic# = 40;
Buffer Hit Ratio
99.9678438
However, using this :
Select
Round((Sum(Decode(name, 'consistent gets',value,0)) +
Sum(Decode(name, 'db block gets',value,0)) -
Sum(Decode(name, 'physical reads',value,0))) /
(Sum(Decode(name, 'consistent gets',value,0)) +
Sum(Decode(name, 'db block gets',value,0)) ) * 100, 4)
from V$sysstat;
Comes up as : 67.7069 %
So which is the right one ?
Thanks.

user4874781 wrote:
Well, I recently joined this organisation and that was the script that was used since long to check Buffer Hit Ratio%.
But when I ran a TOAD report, using the other query, the value came up different.
So am confused .. Whats the difference and which is the right one ?
Try running the following query:
select
        statistic#, name
from
        v$sysstat
where
        statistic# in (38,39,40)
or      name in (
                'consistent gets',
                'physical reads',
                'db block gets'
;The you will understand the point the previous answer was making. It's a bad idea to rely on things like the statistic# being consistent across different versions of Oracle - names tend to be safer.
But neither query is correct. If you want any sort of vaguely meaningful "buffer cache hit ratio", you should be quering v$buffer_pool_statistics. See also: Re: Testing of buffer cache reveals these results: and http://jonathanlewis.wordpress.com/2007/09/02/hit-ratios/
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge." Stephen Hawking.

Similar Messages

  • Low buffer hit ratio

    Hi all,
    could anyone please let me know how I can improve upon the buffer hit ratio in Oracle 8.0
    I have increased my buffer size by 40% in the init.ora parameters but there has been no gain at all in the buffer hit ratio after the system has been bounced and up by 42 hrs so could any let me know..
    Thanks
    Akkama

    Why don't u try pinning the objects accessed frequently - even pinning tables are possible.

  • Which is a better measure of buffer hit ratio?

    which out of these gives a better measure of buffer hit ratio?
    consistent gets from cache
    db block gets from cache
    physical reads cache
    or
    consistent gets
    db block gets
    physical reads
    from v@sysstat?

    Hi,
    Well you can always edit your reply.There is a button out there to do that.
    About the question,I am not clear with the question.What do you mean by "better measure of hit ratio"?
    From the PT guide,
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/memory.htm#i56283
    The formula includes all three of them in the calculation,
    SELECT NAME, VALUE
      FROM V$SYSSTAT
    WHERE NAME IN ('db block gets from cache', 'consistent gets from cache', 'physical reads cache');
    Using the values in the output of the query, calculate the hit ratio for the buffer cache with the following formula:
    1 - (('physical reads cache') / ('consistent gets from cache' + 'db block gets from cache')All three of them are part of the hit ratio.When you wrote the three statistics second time,I am not sure how they were different from the first one.All you did was that you removed "cache" word.
    There is no "better measure" statistics in the calculation.All three are there.
    If your question had some other meaning than I would appreciate if you rephrase and elaborate it please.
    Aman....

  • Oracle Buffer Hit Ratio

    I m using this query to find Oracle Buffer Hit ratio .Is this query right.Is there some other way of getting more accurate ratio
    select trunc((1-(sum(decode(name,'physical reads',value,0))/(sum(decode(name,'db block gets',value,0)) + (sum(decode(name,'consistent gets',value,0)))))) * 100) from v$sysstat

    Asif,
    Too bad we couldn't meet when I happened to come to Bdesh coz if we could , we would had talked about the same topic for hours. If you are using this hit ratio as the tuning technique than you are not alone. There are so many dbas who are using hit ratio and loose sleep seeing not to a particular %. It was a method that was given years ago by Oracle reason being that at that time, databases , their loads, they were not too much. But now things have changed so should be the troubleshooting techniques. Search over this forum for the same topic and you would see some "cool" threads where some top-notch experts are talking about the same issue.
    Aman....

  • STATSPACK REPORT (BUFFER HIT RATIO)

    my statspack report shows that my buffer ration is 83%...what factors i need to look to imporve the buffer hit ratio. Thanks

    I deleted because i realized that i took the statspack report of 1 day period.
    Below is the Statspack report of 1 hour. Can you please let me know if i still need to increase database buffer cache?
    STATSPACK report for
    Database DB Id Instance Inst Num Startup Time Release RAC
    ~~~~~~~~ ----------- ------------ -------- --------------- ----------- ---
    4254163 TEST1 1 28-Jun-07 23:30 10.2.0.3.0 NO
    Host Name: Linux3 Num CPUs: 2 Phys Memory (MB): 7,968
    ~~~~
    Snapshot Snap Id Snap Time Sessions Curs/Sess Comment
    ~~~~~~~~ ---------- ------------------ -------- --------- -------------------
    Begin Snap: 32 03-Jul-07 11:59:13 23 11.0
    End Snap: 42 03-Jul-07 14:07:33 26 11.3
    Elapsed: 128.33 (mins)
    Cache Sizes Begin End
    ~~~~~~~~~~~ ---------- ----------
    Buffer Cache: 100M Std Block Size: 8K
    Shared Pool Size: 100M Log Buffer: 33,823K
    Load Profile Per Second Per Transaction
    ~~~~~~~~~~~~ --------------- ---------------
    Redo size: 1,259.57 8,598.13
    Logical reads: 148.39 1,012.92
    Block changes: 6.41 43.76
    Physical reads: 41.91 286.09
    Physical writes: 0.73 5.02
    User calls: 15.66 106.91
    Parses: 4.07 27.77
    Hard parses: 0.27 1.85
    Sorts: 1.70 11.61
    Logons: 0.01 0.07
    Executes: 9.59 65.47
    Transactions: 0.15
    % Blocks changed per Read: 4.32 Recursive Call %: 83.09
    Rollback per transaction %: 6.03 Rows per Sort: 11.39
    Instance Efficiency Percentages
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Buffer Nowait %: 100.00 Redo NoWait %: 100.00
    Buffer Hit %: 71.77 In-memory Sort %: 100.00
    Library Hit %: 93.15 Soft Parse %: 93.34
    Execute to Parse %: 57.58 Latch Hit %: 100.00
    Parse CPU to Parse Elapsd %: 97.12 % Non-Parse CPU: 86.74
    Shared Pool Statistics Begin End
    Memory Usage %: 91.37 92.38
    % SQL with executions>1: 77.55 80.43
    % Memory for SQL w/exec>1: 83.11 84.69
    Top 5 Timed Events Avg %Total
    ~~~~~~~~~~~~~~~~~~ wait Call
    Event Waits Time (s) (ms) Time
    CPU time 132 48.3
    db file sequential read 89,745 91 1 33.4
    db file scattered read 29,289 35 1 13.0
    control file parallel write 2,558 6 2 2.1
    log file parallel write 2,294 3 1 1.0
    Host CPU (CPUs: 2)
    ~~~~~~~~ Load Average
    Begin End User System Idle WIO WCPU
    0.11 0.11 2.26 2.65 95.09 0.90 0.24
    Instance CPU
    ~~~~~~~~~~~~
    % of total CPU for Instance: 1.06
    % of busy CPU for Instance: 21.63
    %DB time waiting for CPU - Resource Mgr:
    Memory Statistics Begin End
    ~~~~~~~~~~~~~~~~~ ------------ ------------
    Host Mem (MB): 7,967.6 7,967.6
    SGA use (MB): 316.0 316.0
    PGA use (MB): 57.8 62.6
    % Host Mem used for SGA+PGA: 4.7 4.8
    Time Model System Stats DB/Inst: TEST1/TEST1 Snaps: 32-42
    -> Ordered by % of DB time desc, Statistic name
    Statistic Time (s) % of DB time
    sql execute elapsed time 212.3 92.7
    DB CPU 124.2 54.2
    parse time elapsed 21.6 9.4
    hard parse elapsed time 19.7 8.6
    PL/SQL execution elapsed time 4.3 1.9
    hard parse (sharing criteria) elaps 1.4 .6
    connection management call elapsed 1.4 .6
    PL/SQL compilation elapsed time 1.2 .5
    repeated bind elapsed time 0.1 .0
    hard parse (bind mismatch) elapsed 0.1 .0
    sequence load elapsed time 0.0 .0
    DB time 228.9
    background elapsed time 48.2
    background cpu time 39.3
    Wait Events DB/Inst: TEST1/TEST1 Snaps: 32-42
    -> s - second, cs - centisecond, ms - millisecond, us - microsecond
    -> %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
    -> Only events with Total Wait Time (s) >= .001 are shown
    -> ordered by Total Wait Time desc, Waits desc (idle events last)
    Avg
    %Time Total Wait wait Waits
    Event Waits -outs Time (s) (ms) /txn
    db file sequential read 89,745 0 91 1 79.6
    db file scattered read 29,289 0 35 1 26.0
    control file parallel write 2,558 0 6 2 2.3
    log file parallel write 2,294 0 3 1 2.0
    db file parallel write 2,179 0 3 1 1.9
    log file sync 1,089 0 2 2 1.0
    os thread startup 7 0 1 120 0.0
    latch free 3 0 0 89 0.0
    SQL*Net break/reset to client 640 0 0 0 0.6
    direct path read 140 0 0 1 0.1
    control file sequential read 3,599 0 0 0 3.2
    SQL*Net more data to client 2,121 0 0 0 1.9
    db file parallel read 49 0 0 1 0.0
    cursor: pin S wait on X 2 100 0 16 0.0
    read by other session 4 0 0 5 0.0
    direct path write 24 0 0 0 0.0
    latch: shared pool 1 0 0 2 0.0
    SQL*Net message from client 120,211 0 47,282 393 106.6
    wait for unread message on broadc 7,631 100 7,517 985 6.8
    Streams AQ: waiting for messages 1,540 100 7,512 4878 1.4
    Streams AQ: qmn slave idle wait 275 0 7,508 27302 0.2
    Streams AQ: qmn coordinator idle 554 51 7,508 13553 0.5
    Streams AQ: waiting for time mana 25 52 6,643 ###### 0.0
    SQL*Net message to client 120,215 0 0 0 106.6
    class slave wait 7 0 0 1 0.0
    SQL*Net more data from client 146 0 0 0 0.1
    Background Wait Events DB/Inst: TEST1/TEST1 Snaps: 32-42
    -> %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
    -> Only events with Total Wait Time (s) >= .001 are shown
    -> ordered by Total Wait Time desc, Waits desc (idle events last)
    Avg
    %Time Total Wait wait Waits
    Event Waits -outs Time (s) (ms) /txn
    control file parallel write 2,557 0 6 2 2.3
    log file parallel write 2,290 0 3 1 2.0
    db file parallel write 2,179 0 3 1 1.9
    os thread startup 7 0 1 120 0.0
    db file sequential read 1,456 0 1 0 1.3
    db file scattered read 25 0 0 8 0.0
    control file sequential read 156 0 0 0 0.1
    latch: shared pool 1 0 0 2 0.0
    rdbms ipc message 25,017 92 59,496 2378 22.2
    pmon timer 2,576 100 7,513 2917 2.3
    Streams AQ: qmn slave idle wait 275 0 7,508 27302 0.2
    Streams AQ: qmn coordinator idle 554 51 7,508 13553 0.5
    smon timer 26 96 7,148 ###### 0.0
    Streams AQ: waiting for time mana 25 52 6,643 ###### 0.0
    Wait Event Histogram DB/Inst: TEST1/TEST1 Snaps: 32-42
    -> Total Waits - units: K is 1000, M is 1000000, G is 1000000000
    -> % of Waits - column heading: <=1s is truly <1024ms, >1s is truly >=1024ms
    -> % of Waits - value: .0 indicates value was <.05%, null is truly 0
    -> Ordered by Event (idle events last)
    Total ----------------- % of Waits ------------------
    Event Waits <1ms <2ms <4ms <8ms <16ms <32ms <=1s >1s
    LGWR wait for redo copy 7 100.0
    SQL*Net break/reset to cli 640 99.2 .6 .2
    SQL*Net more data to clien 2121 100.0
    control file parallel writ 2558 84.2 12.0 .7 1.4 1.5 .2
    control file sequential re 3599 99.9 .1
    cursor: pin S wait on X 2 100.0
    db file parallel read 49 93.9 2.0 4.1
    db file parallel write 2179 68.2 19.9 6.8 4.0 .9 .1 .1
    db file scattered read 29K 90.7 6.0 .5 .5 .6 .8 .9
    db file sequential read 89K 89.4 2.8 1.3 3.6 1.5 .7 .6
    direct path read 140 87.1 2.9 .7 1.4 7.1 .7
    direct path write 24 100.0
    latch free 3 100.0
    latch: messages 1 100.0
    latch: shared pool 1 100.0
    log file parallel write 2294 77.4 17.3 2.0 1.3 1.1 .8 .2
    log file sync 1089 62.4 28.8 3.3 1.7 2.5 1.1 .2
    os thread startup 7 100.0
    read by other session 4 50.0 25.0 25.0
    SQL*Net message from clien 120K 95.2 1.6 .9 .3 .1 .2 .1 1.7
    SQL*Net message to client 120K 100.0
    SQL*Net more data from cli 146 100.0
    Streams AQ: qmn coordinato 554 49.1 .2 .2 50.5
    Streams AQ: qmn slave idle 275 100.0
    Streams AQ: waiting for me 1540 .2 99.8
    Streams AQ: waiting for ti 25 36.0 16.0 48.0
    class slave wait 7 85.7 14.3
    pmon timer 2577 .5 .1 .1 99.3
    rdbms ipc message 25K 2.3 1.3 1.4 .4 .4 .3 32.1 61.8
    smon timer 26 100.0
    wait for unread message on 7631 .0 .0 100.0 .0

  • One reason why buffer hit ratio just might be bogus

    Hi.
    Still trawling through statspack trying to make some sense of it ...
    But looking at this, (on undo segments) I have perhaps another reason to sneer at the old buffer cache hit ratio: (in the sense of using it to tune, or of using it to justify action / lack of action).
    "The header is also a data block that is frequently modified , so it generally remains in the buffer cache. Therefore, gets of the rollback segment header block increase the buffer cache hit ratio; this artificial increase in the hit ratio can mislead you into thinking that you have allocated enough data blocks to the buffer cache"
    :taken from the OP Exam 033 text, p.295

    Hi Dan,
    The problem is about the usefulness of ratio's in-general, it's not specifically about the BCHR. . . .
    This whole thing arose from the Oracle7 performance tuning classes where Oracle Corporation suggested that the BCHR be kept over 90%. . . .
    Is the BCHR "bogus"? It is what it is, a ratio. . . .
    I agree wit Ben, it does have limited use as an "indicator", that the buffer cache MIGHT be too small to cache the working set of frequently-referenced data blocks. I have my notes here:
    http://www.dba-oracle.com/t_buffer_cache_hit_ratio_value.htm
    Oh, and as to the buffer cache advisory, it's not perfect (as is any predictive model) and I rarely see one that does not suggest that adding RAM will reduce physical I/O.
    Anyway, in just a few years all this will be a moot issue, espeially since solid-state disk has hit $100 per gig. Without spinning platters, there is no need for a large buffer cache at all . . . .
    Hope this helps. . .
    Donald K. Burleson
    Oracle Press author
    Author of "Oracle Tuning: The Definitive Reference":
    http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

  • Buffer hit ratio

    I am using the following:
    SELECT ROUND(((1-(SUM(DECODE(NAME, 'physical reads', value, 0)) /
    (SUM(DECODE(NAME, 'db block gets', value, 0))+
    (SUM(DECODE(NAME, 'CONSISTENT GETS', value, 0))))))*100), 2) || '%' BCHR
    FROM V$SYSSTAT
    to calculate the buffer hit ratio. This query is returning: -1753.28%
    Can someone explain why I am getting this crazy number?
    Thanks,
    mdp

    >>
    Many folks misunderstand that bit about "setting your own BHR", and falsely conclude that it's a useless metric. It's not useless.
    <<
    The buffer cache ratio is useful only when considered in relation to other statistics. The problem is that the majority of users seem to think that that a high ratio value is good and a low ratio value is bad based on absolute values and do not understand that the static is dependent on how SQL plans are being solved. If you measure the ratio when the dominant work on the system is being done via hash joins, full scans that touch the target blocks only once, or make use of PQO during the process you can get a fairly low value, but the system is performing well. On the other had poorly performing SQL can result in a high value for the statistic. The value of the statistics bears no direct relationship to performance of the system and it needs to be emphasized that the ratio must be used in conjunction with other available information. The ratio by itself should be considered useless.
    >>
    If the BHR was totally useless, why does Oracle continue to include it in OEM alert thresholds, and STATSPACK and AWR reports?
    <<
    Over the years Oracle has done lots of things that turned out to be wrong so just because Oracle includes the statistics in certain products does not really provide a lot of support for the validity of the statistic. Known errors in the documentation have made it through two full releases. Again it is the misapplication of the statistic that is really at issue. Unfortunately, many poorly written DBA Administration and Tuning books in the past claimed that ratio could be used to measure database performance, and in point of fact the ratio has only a passing relationship to performance depending on the application.
    HTH -- Mark D Powell --

  • Buffer hit ratio (to be negative)

    Hi All,
    My DB Version: 10.2.0
    OS: Windows Server 2003
    When i am checking snapshots at peak time and comparing it with one when there is no load on the server the buffer hit ratio (to be negative), the buffer cache is too small and the data in is being aged out before it can be used so it must be retrieved again.
    So i just want to know that whether should i increase the value of db_cache_size.
    What exactly happens when i do this.

    Hi;
    DB_CACHE_SIZE specifies the size of the DEFAULT buffer pool for buffers with the primary block size (the block size defined by the DB_BLOCK_SIZE initialization parameter).
    The value must be at least 4M * number of cpus * granule size (smaller values are automatically rounded up to this value). A user-specified value larger than this is rounded up to the nearest granule size. A value of zero is illegal because it is needed for the DEFAULT memory pool of the primary block size, which is the block size for the SYSTEM tablespace.
    Source:
    http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams043.htm
    Regard
    Helios

  • How should i increase over all buffer hit ratio.....

    Hi all,
    As shown below if my DB2 databse buffer Qulaity is low .. How should i increase over all buffer hit ratio..
    Please advice on any sap standrd notes or procedures
    Number                                    1
    Total Size                           80,000  KB
    Physical Reads                         6.65  ms
    Physical Writes                        0.00  ms
    Overall Buffer Quality                86.05  %
    Data Hit Ratio                        85.79  %
    Index Hit Ratio                       87.50  %
    No Victim Buffers                259,079,295
    --rahul

    One of the options is to simply increase the bufferpool size using the following command
    db2 alter bufferpool immediate <bufferpool name> size <new bufferpool size>
    However, this will affect the hit ration for a particular bufferpool. If you have more than one bufferpool, you need to identify the bufferpool(s) with worst hit ratio. In the SAP DBA Cockpit, check using
    Performance -> Bufferpool
    The victim buffer information is only useful in case you use alternate page cleaning.
    Note that there are other options to fight bad bufferpool hit ratio - however, with your small bufferpool size (80MB) maybe increasing the size is the appropriate step.
    Malte

  • Differents values for Buffer Hit Ratio

    Hi Everyone!
    I have only a buffer_pool(8k) and when I execute this two querys(below). The "Buffer Hit Ratio" results are very different.
    Anyone know why does this happen?? I searched on the Internet and find out just V$SYSSTAT gather dates of all buffer pools
    while V$BUFFER_POOL_STATISTICS maintains statistics for each buffer pool. But i can't understand why it is so different.
    Any suggestion?
    Thanks!
    SELECT 1- ((p.value - l.value - d.value) / s.value) "Buffer Cache Hit Ratio"
    FROM v$sysstat s, v$sysstat l, v$sysstat d, v$sysstat p
    WHERE s.name = 'session logical reads'
    AND d.name = 'physical reads direct'
    AND l.name = 'physical reads direct (lob)'
    AND p.name = 'physical reads';
    Buffer Cache Hit Ratio
    ,970655577
    SELECT NAME, PHYSICAL_READS, DB_BLOCK_GETS, CONSISTENT_GETS,
    1 - (PHYSICAL_READS / (DB_BLOCK_GETS + CONSISTENT_GETS)) "Hit Ratio"
    FROM V$BUFFER_POOL_STATISTICS;
    Hit Ratio
    ,584760575
    ORACLE VERSION: Oracle Server 9.2.0.8.0
    OS: IBM/AIX

    See metalink note STATISTIC "cache hit ratio" - Reference Note 33883.1 for the correct formula to use in your calculation.
    The ratio is of limited value. In and of itself it tells you nothing about the performance of your database.
    There have been numerous threads on the ratio in this forum. You can use search to find them if interested.
    HTH -- Mark D Powell --

  • How can i pass the cmrs-100-certified medical reimbursement specialist exam, ed.3 hitting up all the right answers?

    How can I prepare for the cmrs-100-certified medical reimbursement specialist exam, ed.3 hitting up all the right answers? because I do not want to fail this test.
    Sincerely,
    SonnyBoy

    How can I prepare for the cmrs-100-certified medical reimbursement specialist exam, ed.3 hitting up all the right answers? because I do not want to fail this test.
    Sincerely,
    SonnyBoy

  • P-ATA S-ATA whats the right setting

    I just got a 865PE NEo2-V and trying to set the BIOS the right way.
    I have 2 SATA discs and 3 IDE and a DVD.
    I want XP installed on one of the SATA discs and finally made it so.
    But the settings in the BIOS puzzles me, what is the right settings for the SATA disc.
    I wonder because i takes way to long to boot up XP now and i think it might have something to do with my set-up for the drives.
    To get it to even recognize my IDE drives in BIOS, let alone in XP i haft to have this set-up >>
    On-Chip ATA(s) Operate Mode: Native Mode
    ATA Configuration P-ATA Only
    S-ATA Keep Enabled Yes
    P-ATA Keep Enabled No
    P-ATA Channel Selection Both
    Combined Mode Option (not available)
    S-ATA Ports Definition P0-1th. / P1-2nd
    If i set it to just S-ATA in the ATA Config option, my IDE wont show up.
    If i set it to Legacy Mode in the On-Chip ATA-setting i get it also messed up.
    What is the diffrence between all these settings, first of all i dont have P-ATA discs, as far as i know of, second, what is this Legacy and Native settings and can a faulty setting in here cause my slow boot-up for XP??
    A other question is if the 6.2 BIOS maybe can fix all this ( I have the 6.1 now) and is it worth the risk updating it to 6.2?
    Are there any benifits with it?
    .

    The setting is correct. However, you can try this:
    On-Chip ATA(s) Operate Mode: Native Mode
    ATA Configuration S-ATA Only
    S-ATA Keep Enabled -
    P-ATA Keep Enabled YES
    P-ATA Channel Selection Both
    Combined Mode Option (not available)
    S-ATA Ports Definition P0-3rd. / P1-4th (just dun set them to be the 1st and 2nd...)
    In the Boot Device Sequence setup, make sure you put your OS HDD at the first.
    Regarding, Legacy or Native, Legacy only allow 2 channels - 4 devices. Native allow you to use all the SATA and IDE ports, give you accessible to 6 (or 8?) devices.
    What do you mean you don't have P-ATA discs???! What is the "3 IDE" you mentioned if they were not P-ATA?  fyi,  P-ATA = IDE.
    There is nothing wrong and I don't believe 6.2 BIOS did any changes here.
    Slow boot up, this is pretty normal to XP when you have plenty of IDE devices.

  • How do I convert 1080 24p NTSC to PAL format, - whats the right frame rate ?

    I have some footage* that I want to convert to PAL HD.   Currently its in NTSC HD.
    What is the best frame rate / frame size  to convert into?  Do I have to convert it up to 50fps (or 25fps) and turn it into interlaced?
    General
    Complete name                            : my.mov
    Format                                   : MPEG-4
    Format profile                           : QuickTime
    Codec ID                                 : qt 
    File size                                : 168 GiB
    Duration                                 : 2h 18mn
    Overall bit rate mode                    : Variable
    Overall bit rate                         : 173 Mbps
    Encoded date                             : UTC 2014-09-08 17:29:17
    Tagged date                              : UTC 2014-09-08 20:14:37
    Writing library                          : aapl
    ©TIM                                     : 00:00:00:00
    ©TSC                                     : 2997
    ©TSZ                                     : 125
    Video
    ID                                       : 1
    Format                                   : ProRes
    Format version                           : Version 0
    Format profile                           : High
    Codec ID                                 : apch
    Duration                                 : 2h 18mn
    Bit rate mode                            : Variable
    Bit rate                                 : 173 Mbps
    Width                                    : 1 920 pixels
    Height                                   : 1 080 pixels
    Display aspect ratio                     : 16:9
    Frame rate mode                          : Constant
    Frame rate                               : 23.976 fps
    Color space                              : YUV
    Chroma subsampling                       : 4:2:2
    Scan type                                : Progressive
    Bits/(Pixel*Frame)                       : 3.484
    Stream size                              : 168 GiB (100%)
    Writing library                          : Apple
    Language                                 : English
    Encoded date                             : UTC 2014-09-08 17:29:17
    Tagged date                              : UTC 2014-09-08 17:29:17
    Color primaries                          : BT.709
    Transfer characteristics                 : BT.709
    Matrix coefficients                      : BT.709
    Other
    ID                                       : 2
    Type                                     : Time code
    Format                                   : QuickTime TC
    Duration                                 : 2h 18mn
    Time code of first frame                 : 00:00:00:00
    Time code settings                       : Striped
    Language                                 : English
    Encoded date                             : UTC 2014-09-08 17:29:17
    Tagged date                              : UTC 2014-09-08 17:29:17

    PAL is 720 x 576 pixels interlaced (bottom first).
    If it's 16:9 aspect ratio, you need to select "Anamorphic" and the frame rate it 25 fps.
    If you need help with Compressor settings - I use Best for everything including re-sizing - processing is slow but the result is excellent.
    I believe you can use MPEG Streamclip for converting, but I have not tried it.
    Andy

  • Whats the right Digital Camera to show video Clips on my new iMac OS X Lion

    Hi, Can anybody tell me what Type or Model of Digital Camera (with Video Clip Facility) to purchase succesfully down loading on to my brand new iMac OS X Lion?? I'm new to Apple iMac, found out that my 2 year old Samsung camera when downloading Photos and video clips, only shows the photos but not the video clips in my iPhoto folder. the clips are just shown in a black blank square!! Please HELP...Thank You

    Christa,
    Have you tried using iMovie for your video clips? If you aren't familiar with iMovie here is a link to the iMovie tutorials. I would think your current camera should be just fine.

  • [solved] whats the right place for community repository bug reports?

    was about to write a bug report, but there was no category for packages:community.. is the forum the correct place for this?
    pacman -S freevo
    resolving dependencies...
    error: cannot resolve "python-pysqlite-legacy", a dependency of "freevo"
    error: failed to prepare transaction (could not satisfy dependencies)
    :: freevo: requires python-pysqlite-legacy
    Last edited by schuay (2008-12-11 18:17:21)

    schuay wrote:
    was about to write a bug report, but there was no category for packages:community.. is the forum the correct place for this?
    pacman -S freevo
    resolving dependencies...
    error: cannot resolve "python-pysqlite-legacy", a dependency of "freevo"
    error: failed to prepare transaction (could not satisfy dependencies)
    :: freevo: requires python-pysqlite-legacy
    When you go into the bug tracker, there's a drop down list on your left that says "Arch Linux". Go into there, select "Community Packages", and pres the "switch" button right next to it.

Maybe you are looking for