Jump to content

jcs

Members
  • Posts

    1,839
  • Joined

  • Last visited

Everything posted by jcs

  1. Pretty cool, however it's highly aliased. Perhaps useful for what the app aims to do: select a still from a burst group. Adding an anti-alias filtering and rendering at 1920x960 still had a little aliasing but might be usable.
  2. Requires iOS 5(!) to work full res. A colleague sent a frame (iOS 6.x) and it was less than an HD video frame in resolution. Nice UI and marketing.
  3. The Internet- the great equalizer.   Our own footage streamed from Vimeo and Youtube now looks better than what Netflix and Amazon are streaming down for paid content...   Even at reduced resolution, the 7D footage looks excellent.
  4. +Sanken CS3e and Sennheiser MKH-60 (~$500 over $1k; very popular).   If it has to be under $1K, Audio Technica 4053b is a great value for $600.
  5. Schoeps CMIT5U (when it's on sale for $1000 ;))
  6. Now that you've reviewed the G6, when will you review the G650?
  7. I had seen the previews for Pacific Rim and wasn't really motivated to see the movie. Giant robots fighting giant aliens? If somehow giant aliens from another dimension were stomping around Earth, simple bunker-buster bombs with high explosives, tactical nukes (actually overkill), would be sufficient to stop them. Even current lasers would work- these slow moving creatures could be cooked slowly as they approached cities. Microwaves or masers could also work, as could biological agents. That's what flashed through my mind after seeing the previews and I gave it no further thought.   A director friend of mine called me today and asked if I wanted to see a screening of Pacific Rim at the Linwood Dunn theater in Hollywood, with a Q&A afterwords with the director Guillermo del Toro and VFX superviser and head of ILM, John Knoll (who also created Photoshop back in the 90's). I hadn't seen my friend in a while and the Q&A sounded interesting, so I went. At the beginning of the screening we were told Guillermo was sick, but John Knoll would still be available for Q&A.   The movie was presented in Dolby 3D, which uses glasses that have a metallic orange and greenish reflection. I have found the Real 3D circular polarized 3D glasses provide the best stereo 3D experience, however a special silver screen which preserves light polarization is required (not needed with Dolby 3D). The Dolby 3D glasses use 'wavelength multiplex visualization' which is somewhat like anaglyph in that it uses a color filter, but unlike anaglyph, provides full color. More info here: http://en.wikipedia.org/wiki/Dolby_3D.   With very low expectations, the movie started. The stereo 3D effect was excellent, and well done: no eyestrain and the use of depth actually helped the presentation. There was action immediately, with amazing special effects. As a guy who has written a great deal of code for graphics rendering and physics simulation, I was blown away by the sheer amount of physics simulation and rendering effects happening at once. Rigid bodies, fracturing, soft bodies, tearing, skin simulation, light scattering, radiosity, large and small scale fluid dynamics, smoke & gas simulation, dust & clouds, character IK, and the list goes on. Pretty much every VFX effect was used and for an incredible story telling and entertaining effect. The music and sound FX were also excellent, building emotion and maintaining pace all the way through to the end. It was easy to ignore some of the weaker acting as there was so much entertainment and excitement. To sum up the plot: a mix of Armageddon and Independence Day with a touch of Godzilla (other than giant robots, nothing like Transformers except the destruction). Ridiculous plot? Yes! Great movie? Yes!   The Q&A with John Knoll was cool. The best quote perhaps was it would take 7000 years to render the movie on a single modern fast workstation. John explained what we saw: an insane amount of effects were used in the movie. It sounded like the most complex VFX work done by ILM to date.   The box office hasn't been great for Pacific Rim yet, however an 8/10 at IMDB is pretty good: http://www.imdb.com/title/tt1663662/. Read some of the reviews- passionate! This movie is so cool with so many amazing shots/scenes, I'm motivated to see it again. I can't remember the last time I wanted to see a movie again. I would think that once word gets around that this is actually a great movie, it will have legs and perhaps be a top movie of the summer. This movie is also a lot deeper than many folks realize- paying homage to many other movies, genres, & cultures. 10 out of 10!  
  8. MJPEG is essentially JPEG per frame. JPEG uses a fixed 8x8 DCT which has been highly optimized (along with fast/simple quantization and additional steps for final compression output). So MJPEG might be possible on ARM. The bigger problem is high-quality de-Bayering. Even Resolve 9 doesn't do a very good job compared to ACR.
  9. While Cinema DNG plays in real-time in Resolve (MacPro 12-core and Quadro 5000), and it's a little over 2x faster to transcode to DNxHD (for editing in PPro), ACR + AE looks much better due to higher quality de-Bayering and noise reduction (no NR for R9 lite?).   Played with R9's tracker today (for Power Window correction)- very fast and very cool...
  10. Thanks! So June 3 ML and May 30 raw2dng.exe are spot free?
  11. I've googled a bit and haven't found a June 3 release of raw2dng. https://bitbucket.org/hudson/magic-lantern/downloads/Raw2Dng.exe is the same version I have. Andrew's link is dead. Link to June 3 release? thx!
  12. Has this been reported yet? (May 22 ML) [attachment=525:spots.jpg]   ACR in AE CS6.
  13. ok- guess that's the first non-test I posted here :)
  14. FS700 + Speed Booster cut with 5D3 RAW and iPhone 4S [video]https://www.youtube.com/watch?v=D6NKjnKPAU8[/video] Vimeo (HQ 1080p available for download) https://vimeo.com/67540334  
  15. Here's a version using Deshaker to stabilize:   http://www.youtube.com/watch?v=thaUgx-9Qog Vimeo: (can download 1080p high quality version) https://vimeo.com/67533830
  16. How does the deBayer quality compare to ACR? e.g. direct PPro editing or Resolve vs. AE + ACR => 10+bit 422/444 codec.
  17. Thanks mtheory!   MacPro 12-core running SSDs and a bunch of hard drives, USB3 PCIe card for fast USB3 card readers, Quadro 5000, GeForce GT120 (for OSX boot), 3 monitors (2560x1600, 1920x1200, and 1920x1080 HDTV) and Win7x64 with Adobe Master Collection CS6 has been rock solid (Adobe tools seem to have more bugs on OSX and run slower as well (same hardware)).   AE CS6 is still unfortunately somewhat buggy, which I why I had turned off multi-frame processing. However, for raw processing,  multi-frame processing rocks: no crashes or other issues yet. 6FPS is pretty cool for raw conversion to DNxHD 10-bit (Cineform also works, though their codec hasn't been as stable as DNxHD).   In PPro CS6 in Win7x64, Matrox I-frame only HD (a really nice MPEG2 codec, free) in an AVI container was not as fast to work with as DNxHD in a MOV (QuickTime) container, which is surprising (QuickTime code path is typically slower).
  18. YouTube http://www.youtube.com/watch?v=vwgSWqdbniM Vimeo (downloadable): https://vimeo.com/67472338   First part used an LED light on camera; last part is ambient light.   Workflow: raw2dng => DNGs to ACR+AE => rendered as 175Mbps 10-bit 422 DNxHD MOV => edited in Premiere Pro CS6. AE CS6 Render Settings / Render Depth set to 16-bit and Output Module / Depth set to Trillions of colors (to make sure DNxHD was getting >= 10 bit color). 12-Core MacPro (running Win7x64) renders DNG to DNxHD at ~6FPS. Komputerbay 32GB 1000X (supports 1920x1080). Have 2 64GB 1000X on order. 128GB 1000X can only support 1920x900; was going to return it however Amazon offered a very generous discount to keep it (useful enough to keep).
  19. It's running at 99% CPU with 1.5GB per processor set in AE CS6. Didn't try setting to 1GB per proc as it's already running at full speed (24 cores are available). Was running at .5FPS before, so ~12x speed up once using all cores (as expected).
  20. I had turned off Render Multiple Frames at once in AE CS6 due to stability issues for other tasks. I turned it back on with 1.5GB per render and 10 processors (12 core 2.93GHz MacPro).   Hit 99% CPU- used all 12(!) cores, up to 21GB of RAM (24 total)) and rendered 6FPS (1/4 real-time). Rendered out to 150Mbps Matrox MPEG2 I-frame HD (422) for editing in PPro CS6.
  21. Thanks for the tip Julian- Bridge CS6 on a 12-Core MacPro also choked with 2813 files. AE works so far- will also explore the other tools mentioned on the ML site.
  22. Using the May 22 ML and latest raw2dng, with 2800+ DNG frames, PS CS6 chokes...
  23. Sorry- working on other project with PNGs- meant DNG. Corrected original post. The TIF workflow to ProRes or DNxHD will get you color bits > 8.
  24. 1. Convert to DNG with raw2dng 2. Open all DNGs with Photoshop CS6, this opens up ACR 3. Press Select All and Synchronize (upper left on screen) 4. Grade, do noise reduction, etc. 5. Press Save All and save to JPG at 100% (grading is done, so 8-bit is OK). 6. In Premiere CS6, import first JPG, then press checkbox for Image Squence. 7. Modify clip- Interpret Footage as 23.976.   This is pretty fast once you do it a few times (much faster than an AE workflow), and plays back in real-time in Premiere. To get a 10-bit 422 workflow, Cinema 5D recommended saving first to 16-bit TIF, then converting to ProRes (Mac. On PC can do DNxHD, etc.).   A 4GB RAW file produces around 270MB in 100% quality JPGs (47 seconds).
×
×
  • Create New...