Personal View site logo
Wiki discussion
  • cyfernoacyfernoa
    Hello all. In a recent thread there was much discussion of creating a GH2 hack wiki. Vitaliy agreed that if (someone or more than one) would be willing to donate time and energy in maintaining it he would support it. So this is basically a calling out to anybody skilled in the art of making wiki's to get the ball rolling so we can all keep the boards free from the same repetitive questions and create an environment that is better suited to the testing and creation of better patches.

  • 40 Replies sorted by
  • duartixduartix

    Great to hear that! Thanks.

  • Vitaliy_KiselevVitaliy_Kiselev

    We'll certainly have such section. Just wait for new version a little, ok?

    As we'll need to move many things out of developer section to amke it available for active settings authors.

  • balazerbalazer

    I could create a new wiki page for GH2 testers, but I think we should put the question to Vitaliy, since it looks like he already had some idea of where the information should live and who should be allowed to update it.

    There is a lot of information locked up in individual testers' heads that they haven't bothered to share in the forum. It would be great to consolidate that info.

  • duartixduartix

    @balazer : Been looking a bit more deeply at the wiki and it has a lot of useful and well organised information, but just not for patchers. I don't know how many of us are doing it on our own and need more info on the Patch for Testers parameters but I'd really like to see it.

  • duartixduartix

    See? That's the kind of info that shouldn't be "reserved" for the "elite". ;)

    I'm really not complaining because when I was trying to build my patch I asked around by PM and I eventually got all the answers by you, by driftwood and lpowell, yet I believe it would be an asset to the community if that info was organised and readily available.

    As for that parameter, I run a few (uncontrolled I should say) tests yesterday and got the impression that the only influence on P-Frame size was the Quantizer Tables. Perhaps shooting a static scene might have something to do with it. Anyway it's a pity that this information is so spread and that the wiki is empty regarding these matters... :(

  • balazerbalazer

    The "Quantizer for 1080 modes" setting most definitely affects P and B-frames.

    As for a wiki, there is a wiki page at linked from the tooltips of several of the PTool settings, but the page is essentially empty and it's asking for a password to edit it. I'm all for having a wiki page somewhere to consolidate findings about the various PTool settings. There's also an Encoder Research page in the new wiki, but I don't have permission to edit it.

  • duartixduartix

    Where do we put information about the undocumented hack parameters? Let's say I would like to share something like: "Quantizer for 1080 modes" - Regulates the size/quality of I-Frames in 1080 modes. Does not seem to affect P/B-Frames.

  • RebelPhotonRebelPhoton

    I don't have the camera at the moment, I've been borrowing one from a friend. I'll test the next time I get hold of it, but I only have access to 30Mb/s Sandisk cards.

    Depending on the kind of shoot it's a feature that you might need, so knowing it a concrete patch disables it is very useful to help choose the right patch.

  • balazerbalazer

    If someone wants to figure out which patch settings support in-camera playback, that can be added to the wiki. I don't think the memory card is a factor.

  • RebelPhotonRebelPhoton

    Great charts in the new wiki.

    Is it possible to add a new field in the "effective bitrate/spans/vmm80% 30p/ETC" chart that states whether a patch+card combination allows for in-camera playback or not?

    It is quite important for many collaborative shoots and many people might want to choose a lower bitrate patch to be able to keep this functionality working.

  • jeffryalanjeffryalan

    That is a pretty cool factoid, 143 divided by bit rate, multiplied by card space in GB = time left for shot.

    Thanks for that @balazar

  • balazerbalazer

    143 is a constant. Say you are shooting with one of Driftwood's 146 Mbps patch settings. 143 / 146 Mbps = 0.98 minutes per gigabyte. A 32-GB card holds about 30 GB, so that gives you 30 * 0.98, or about 29 and a half minutes.

    Card performance is another issue altogether. There are many dimensions of card performance, so it is hard to predict which cards will work with which patch settings, even if you had detailed benchmarks. Card recommendations are based on testing of actual cards while shooting video in the GH2.

  • jeffryalanjeffryalan

    So, is that a variable affected by minimum/maximum read/write throughput rates?

    For example, the Sandisk Extreme Pro 16Gb 45MB/s has a sequential transfer rate for reading at the top end of 44.8 MB/s and a low of 37.2 MB/s, but the reason that it fails spectacularly for the GH2 is that it's WRITE throughput goes from 36.6 MB/s to a miserable 800 KB/s. The speed on the card does not necessarily reflect the actual average write throughput.

    We could assume a potential media allowance through simple calculation but will that be only a rough estimate or are benchmark tests needed to find the actual length of media? It would be easy then to compile a chart with min/max times per recommended card in relation to the significant patches.

    (ASQ) Another Stupid Question: is 143 a constant for all calculations?

    http://www.tomshardware.com/reviews/sdxc-sdhc-uhs-i,2940-12.html

  • balazerbalazer

    Thanks, @jeffryalan. A simple bit of math should suffice to convert bit rates to recording times.

    143 divided by the bit rate in Mbps = minutes per gigabyte

  • jeffryalanjeffryalan

    @balazar, great work, love the charts with comparison of patches.

    Is it possible to also add media times to chart as to each recommended card? I shoot a lot of long timelapse and look for stable spanning for shots as long as I can until card is full.

  • PhenixonePhenixone
    This is a great initiative Vitaliy! Something I was waiting for a long time.
    Now every time a newcomer asks a simple question, we'll have to change out comment from "no spoon feeding" to "go look at the FAQ".
  • Vitaliy_KiselevVitaliy_Kiselev
    @balazer

    I added breadcrumbs, could be enough for a start.
    I'll change template later.
  • balazerbalazer
    Vitaliy, I noticed that there are no navigation links in the wiki header, like back to the wiki root or to the p-v root. Can you add those kinds of links in the wiki config, or should we just create links within the wiki pages? A person coming into one of the wiki sub-pages from Google wouldn't necessarily know there was anything more to p-v.
  • Vitaliy_KiselevVitaliy_Kiselev
    @balazer

    Please, move all general things (like ETC, video editing, etc) outside GH2 hack FAQ main page.
    You can make page lie "GH2 Usage tips".
  • balazerbalazer
    I have completed my first passes of the PTool FAQ, the GH2 Hack FAQ, and the GH2 Usage FAQ.

    http://www.personal-view.com/faqs/

    I'll take your comments and suggestions here.
  • cyfernoacyfernoa
    Great News now we just need to get the ball rolling. Start looking at all the main repeated questions and start editing. Thanks a lot everyone involved.
  • Vitaliy_KiselevVitaliy_Kiselev
    I installed Wiki at
    http://www.personal-view.com/faqs/

    You can register, but new users don't have editing rights until approval.
  • jeffryalanjeffryalan
    excellent news!

    There is such a vast amount of info not only on the GH2 hack but all the work previously that relates to it, hopefully this will greatly reduce the questions that have already been addressed.
  • balazerbalazer
    I have begun work on a wiki page. I will send it to Vitaliy when I'm done, probably around the end of this week.
  • Vitaliy_KiselevVitaliy_Kiselev
    @balazer

    Do not worry, just write the part you think you know and send me to PM.
Add a Comment