Jump to content

FilmMan

Members
  • Posts

    1,086
  • Joined

  • Last visited

Posts posted by FilmMan

  1. Quick read on 4K.
    [url="http://broadcastengineering.com/shows/disappointing-3dtv-sales-makes-4k-next-big-thing"]http://broadcastengineering.com/shows/disappointing-3dtv-sales-makes-4k-next-big-thing[/url]
  2. Hey everyone,

    Andy600 from Magic Lantern had two 3 second clips put up for a quick look via download. He was testing the higher bitrates. I downloaded his clips and color graded one of them. It is posted below. Note: The clip he had for download was compressed, so I was working with compressed footage. It was very robust to grade even though it wasn't the original. Forgive me for my color grading as I use a tv as a monitor. His camera was the Canon 600D.

    [url="http://vimeo.com/49267057"]http://vimeo.com/49267057[/url]
  3. [b]From the Magic Lantern site:[/b]

    [b]7D support[/b]
    We didn't give up, but we are not able to start the main firmware from user code. Currently it is possible to blink the LED and draw on the screen, but that's all. The problem is the dual DIGIC.
  4. Here's the 2nd last post. It is a good read so I'm being repetitive here. This is from the programmer 1%. He was responding to "because there is no interframe dependence"

    [b]Quote[/b]
    [indent=1][b]because there is no interframe dependence[/b][/indent]



    [b][i]Yep, I frame dropped from buffer almost immediately. P frame sticks around for a while while its doing more passes, etc.

    The P frames are only a little bit more compressed and really the main reason to use them is file size/buffer. 1GB a minute is hardcore no matter how you do it. Also, no B frames yet... Gop3 is where its closer to old file sizes and doesn't write almost all the time. I think the I frame has to be like 10-15% bigger for the same quality so instead of a decent 130mbps you end up at 160-170mbps and you actually do crash if the encoder slows down or the card does. Should test gop of 2,3-6... any more than that and too much is held in the buffer.

    Qscale drops like a stone when the buffer warning comes on but it ramps up right away with the faster polling. You can turn on debugging and watch it. Qscale with canon functions only moved by one. With slice you can go from 128 to 87 instantly. [color=#FF0000]I think canon was really going for consumers and smaller files rather than quality. They want you to buy a more expensive camera rather than using a 600D, etc. [/color]The weird thing is that they don't like offering swappable lenses on their camcorder offerings. Heavy grading will really show if the bit rate dips matter or not. If a few frames get all funky out of a whole sequence then we'll know.


    Other cameras:

    50D = Did not change gop.
    550D = no breaking 4gb limit so you'll have all of 4 minutes of footage.
    60D = untested for both limit and gop.
    T3 = can probably pull it off
    5d3 = different encoder, different hacks
    5d2 = don't have one and nobody has really looked in on it. Encoder also slightly different. CF cards should in theory do more than 20MB/s write. A1ex has one so he'd be the guy to try it. But still have to hack the 4gb limit and 5d2 is the same generation as 550D so maybe only 32bit value for file size [img]http://www.magiclantern.fm/forum/Smileys/default/sad.gif[/img]

    What's left?

    MJPEG might end up giving better results and actual full frame video, none of this 1600x960 crap. Although maybe native recording and resizing later might give better results for regular H.264 than in camera resized 1920x1080. [color=#FF0000][size=6][u][u]I can continually take shots at S1 which is like 2592x1728 so 2k video seems possible. [/u][/u][/size]Ma[/color]x file size per frame would be like .83MB to get 24p out of that. .67 for 30P... not a whole lot of room. SD interface max speed at 48mhz is 25MB but no card seems to want to keep up. How good can you get at that data rate?

    Line skip is likely so it can fit the entire frame into reduced resolution without resizing the whole image and taking up CPU time, etc. It IS controllable since 600D has 1:1 crop and even zooming. But the issue will be that the frames are bigger and more complex to encode.. hence static and trees are very evil.

    Right now, encoder in the hand is worth 2 in the theoretical stage. [/i][/b]
  5. I'm getting a little excited here. Magic Lantern Programmer 1% and others have been making some progress and talking about 2K and 422 color space. It is premature but worthy of mentioning again - In case you haven't been following the [color=#FF0000][b]115 mbp/s??? CANON DSLR link (read the 2nd last post on the link).[/b][/color] [url="http://www.eoshd.com/comments/topic/1203-115-mbps-canon-dslr/page__st__20"]http://www.eoshd.com/comments/topic/1203-115-mbps-canon-dslr/page__st__20[/url]

    Why do I say sub $1000? Well, programmer 1% has been tweaking his 600d which is priced as low as $480!!!
    [url="http://www.myshopping.com.au/PR--384480_Canon_600D_Camera"]http://www.myshopping.com.au/PR--384480_Canon_600D_Camera[/url]

    It is still early. Here's some conversation from 1%...

    [color=#0000FF][i] 4:2:2 already being thrown away. 2k is just next size up. If the frames can compress < card rate should be possible. Will probably need to be zoomed to not have line skip. It was probably the only way to fit 20MP sensor in <3MP video[/i].[/color]

    Donating $5 to $10 to their cause at Magic Lantern would probably go a long way.
  6. Latest from 1% programmer. A very interesting read...


    [b]Quote[/b][indent][b]because there is no interframe dependence[/b][/indent]



    [b][i]Yep, I frame dropped from buffer almost immediately. P frame sticks around for a while while its doing more passes, etc.

    The P frames are only a little bit more compressed and really the main reason to use them is file size/buffer. 1GB a minute is hardcore no matter how you do it. Also, no B frames yet... Gop3 is where its closer to old file sizes and doesn't write almost all the time. I think the I frame has to be like 10-15% bigger for the same quality so instead of a decent 130mbps you end up at 160-170mbps and you actually do crash if the encoder slows down or the card does. Should test gop of 2,3-6... any more than that and too much is held in the buffer.

    Qscale drops like a stone when the buffer warning comes on but it ramps up right away with the faster polling. You can turn on debugging and watch it. Qscale with canon functions only moved by one. With slice you can go from 128 to 87 instantly. [color=#FF0000]I think canon was really going for consumers and smaller files rather than quality. They want you to buy a more expensive camera rather than using a 600D, etc. [/color]The weird thing is that they don't like offering swappable lenses on their camcorder offerings. Heavy grading will really show if the bit rate dips matter or not. If a few frames get all funky out of a whole sequence then we'll know.


    Other cameras:

    50D = Did not change gop.
    550D = no breaking 4gb limit so you'll have all of 4 minutes of footage.
    60D = untested for both limit and gop.
    T3 = can probably pull it off
    5d3 = different encoder, different hacks
    5d2 = don't have one and nobody has really looked in on it. Encoder also slightly different. CF cards should in theory do more than 20MB/s write. A1ex has one so he'd be the guy to try it. But still have to hack the 4gb limit and 5d2 is the same generation as 550D so maybe only 32bit value for file size [img]http://www.magiclantern.fm/forum/Smileys/default/sad.gif[/img]

    What's left?

    MJPEG might end up giving better results and actual full frame video, none of this 1600x960 crap. Although maybe native recording and resizing later might give better results for regular H.264 than in camera resized 1920x1080. [color=#FF0000][size=6][u]I can continually take shots at S1 which is like 2592x1728 so 2k video seems possible. [/u][/size]Ma[/color]x file size per frame would be like .83MB to get 24p out of that. .67 for 30P... not a whole lot of room. SD interface max speed at 48mhz is 25MB but no card seems to want to keep up. How good can you get at that data rate?

    Line skip is likely so it can fit the entire frame into reduced resolution without resizing the whole image and taking up CPU time, etc. It IS controllable since 600D has 1:1 crop and even zooming. But the issue will be that the frames are bigger and more complex to encode.. hence static and trees are very evil.

    Right now, encoder in the hand is worth 2 in the theoretical stage. [/i][/b]
  7. Sounds interesting. Perhaps too hopeful or not?

    1% programmer:

    [i]600D already does ALL-I 176mbps.. I've gotten past 200 for short periods. I'm actually trying to slow it down at this point. Card sustained is only 160. T4i will probably do like 400mbps in UHS-1. 2k and 4:2:2 can probably happen if we get at what's being fed to the encoder.[/i]
  8. JGHarding,

    You'll like this. 1% added this today.

    [b][i]In daylight it still works, ramp down is good, ramp up is a little too fast I think. 1 second polling for BR and buffer is a little too slow, would like .5 seconds. Bit rate is a little bit jaggy (follows card write) but better quantizer used overall than CBR function or VBR function and mostly stops overruns unless they happen really suddenly or scene is already too big to encode. I set buffer warning to like 50/60% and had success at ISO 80-2500.

    [color=#FF0000][u]Low points of BR are usually above default rate of 40.[/u][/color] Footage is overall 1GB per minute. A 7minute continues shot was ~7GB. [color=#FF0000][u]Average BR is over 120, peaks 160-200.[/u][/color] The drop downs aren't really noticeable in watching, I have to see if they show up in post but I doubt they will as BR at worst quantizer is still usually very high. [/i][/b]
  9. [b] [url="http://www.sonyalpharumors.com/sr5-hot-first-sony-a99-image-leak-via-xitek/"](SR5) Hot: First Sony A99 image leak (via xitek)[/url][/b]

    [url="http://i1266.photobucket.com/albums/jj524/picrumors/Sony_SLT_A99_FF.jpg"][img]http://i1266.photobucket.com/albums/jj524/picrumors/Sony_SLT_A99_FF.jpg[/img][/url]
    An anonymous reader sent us this picture found on the chinese Xitek (P.S.: He forgot to send me the link…you may send it to me?). My sources told me that this is a 100% correct picture of the upcoming new Sony A99 Full Frame SLT camera. The camera will be announced next week on Wednesday September 12th. As I told you before Sony wanted to realize the best hybrid video and still Full Frame camera on market by beating the current [url="http://go.redirectingat.com/?id=19445X767312&xs=1&url=http%3A%2F%2Fwww.amazon.com%2FCanon-Frame-Full-HD-Digital-Camera%2Fdp%2FB007FGYZFI"]Canon 5DmarkIII[/url]. What is coming along the A99 is not only a camera but also a whole system of innovative accessories around it. It also marks the possible end of the classic DSLR Full Frame line with optical viewfinders. The [url="http://rover.ebay.com/rover/1/711-53200-19255-0/1?icep_ff3=9&pub=5574825908&toolid=10001&campid=5336676702&customid=&icep_uq=Sony+A850&icep_sellerId=&icep_ex_kw=&icep_sortBy=12&icep_catId=&icep_minPrice=&icep_maxPrice=&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg"]A850 (Click here)[/url] and the [url="http://go.redirectingat.com/?id=19445X767312&xs=1&url=http%3A%2F%2Fwww.amazon.com%2FSony-Alpha-24-6MP-Digital-Camera%2Fdp%2FB001FOREK4"]A900 (Click here)[/url] were the last two models with viewfinder.
    Below you can find the full A99 specs and the info about all the rest of the Sony stuff that is going to be announced on the same say.[color=#ff0000][size=5][b] I want to highlight once again that I can confirm that there is also a new unexpected professional NEX camera coming too! I am working on that rumor but it looks like only few people on the world have access to the info. It’s the best kept Sony secret ever. I have been told this is a “[u]Game Changer camera[/u]”.[/b][/size][/color] I highly recommend you all to follow SonyAlphaRumors in these days. Sony may be the big star at Photokina if all those rumors are correct. And to not miss any single news be sure to follow the [url="http://www.alphacameradeals.com/feed/"]RSS feed[/url] and [url="https://twitter.com/SonyAlphaRumors"]Twitter[/url] stream and join the [url="https://www.facebook.com/pages/Alphacameradeals/376585815746742"]Facebook fan page[/url]!
    [b]Sony A99 specs[/b][list]
    [*]24.3 Mpx Full frame CMOS Exmor sensor
    [*]SLT technology
    [*]New Bionz imaging engine
    [*]14 bit RAW recording
    [*]10 fps
    [*]ISO 100 up to 25.600
    [*]50 ISO extended (with lower dynamic range)
    [*]102 AF point AF (11 cross).
    [*]AF range
    [*]MF assist
    [*]Dual Phase detection system (with AF phase pixels on sensor)
    [*]30 sec and 1/8000 maximum shutter speed
    [*]Time Lag 0.05 sec.
    [*]Shutter life guarantee of 200,000 cycles
    [*]2.360k OLED electronic viewfinder
    [*]3″921k LCD with same tilting system of the A77
    [*]Full HD video recording at 1920×1080/50p (US: 60p) AVCHD 2.0 format.
    [*]Clean HDMI output
    [*]Built-in stereo mic
    [*]Auto HDR capability
    [*]New multi-segment low pass filter
    [*]Photodiode expansion technology
    [*]Light concentration technology
    [*]Selective noise reduction
    [*]Ultrasonic anti dust system
    [*]In body image stabilization
    [*]Two memory slots: SD and SD+MS cards
    [*]USB: 2.0
    [*]Announced on September 12, 2012
    [*]Available in stores in late October 2012
    [*]New accessories to be released with the a99: battery grip, flash, remote control, microphone etc.
    [*]Very light, weather sealed magnesium alloy body.With 730 g this is the lightest FF body on market!
    [*]Price unconfirmed yet but should be at around 2800 Euro/Dollars.
    [/list]
  10. [b]Some Positive news![/b]

    Programmer 1% comments:


    Found new thing about CBR mode. If you're using ALL-I CBR will not adjust qscale/slice quality. This means that next qscale value is calculated from P frames not I frames. Can anyone confirm? Set slice 0, reboot, turn on debugging and see if slice quality changes in all I. Even in gop2 qscale changes, gop 1 is a default of 120, I think thats -8.


    *Edit:

    More good news... slice QP can be adjusted by as much as you want. For now I set it to drop by 4 when buffer gets to warning level and no errors + no buffer overruns but quality drops down quickly so I need to find a good mathematical solution either by buffer or bitrate.

    Something quick:

    [url="https://bitbucket.org/OtherOnePercent/tragic-lantern/downloads/autoexec.bin.quickcbr"]https://bitbucket.org/OtherOnePercent/tragic-lantern/downloads/autoexec.bin.quickcbr[/url]

    If buffer warning drop slice q by 2, if BR < 75mbps raise by 1. Its working at ISO5k in crop mode but its too dark right now for me to test + fine tune. Mainly doing this for ALL-I ... I'll try in longer gops next.
  11. [url="http://nikonrumors.com/2012/09/07/nikon-d800-goes-to-hollywood.aspx/"]http://nikonrumors.com/2012/09/07/nikon-d800-goes-to-hollywood.aspx/[/url]

    [color=#000000][left][background=#ffffff]
    [b] Nikon Establishes Hollywood Video Credentials as the D800 Lands Leading Roles[/b]

    [b]FX and Showtime Networks Cast Multimedia HD-SLR and NIKKOR Glass for Hit Television Series "Wilfred" and "Dexter"[/b]

    Read more on NikonRumors.com: [url="http://nikonrumors.com/2012/09/07/nikon-d800-goes-to-hollywood.aspx/#ixzz25ubnfppV"]http://nikonrumors.com/2012/09/07/nikon-d800-goes-to-hollywood.aspx/#ixzz25ubnfppV[/url][/background][/left][/color]
  12. I saw the Expendables 2 a few weeks ago. I went to the AVX theater ([b]bigger screen[/b], and even more leg room). There was a fair bit of noise in the night scenes. Overall, it had the "older gritty look" and I'm not referring to Stallone, Chuck, Arnold, or the other seniors. The image seemed reminiscent of the 80's action movie genre. In the previews, the new James Bond movie trailer played. It looked very clean image wise (shot on an Alexa) as opposed to the Expendables image. Perhaps they were going for that certain look. The movie, The Grey, shot on the Arriflex 235 had alot of noise too. I'm preferring the cleaner look now. My 2 cents.
  13. More on the 1DC

    [url="http://www.hurlbutvisuals.com/blog/2012/09/canon-1dc-camera-tests-from-the-ticket/comment-page-1/#comment-15580"]http://www.hurlbutvisuals.com/blog/2012/09/canon-1dc-camera-tests-from-the-ticket/comment-page-1/#comment-15580[/url]
  14. And Leon's response:

    [color=#ff0000]In burst mode, there isn't any zooming though, is there? It's only managing to write 2MB per second in silent frames to my camera when I use burst mode.

    Seems so strange that it would waste processing encoding to jpeg and then decoding it to send it to the H264 encoder, unless it is somehow forced by the way their hardware is wired up and communicates. If the jpcore part is already a bit compressed, [i][u][b]maybe that can be written directly to the card bypassing x264. We only need a 7:1 compression overall (or 4:1 compared to 4:2:2) to get 1080p down to being 20MB/s.[/b][/u][/i][/color]
×
×
  • Create New...