Forum Replies Created

Page 10 of 14
  • Bernhard G.

    May 4, 2012 at 1:28 pm in reply to: Media Composer 6 and Color Precision

    Thank You,

    but before I try a product I enjoy reading the manual!

    In my opinion, manuals should be separately downloadable as PDFs.

    Best regards,
    Bernhard

  • Bernhard G.

    April 30, 2012 at 3:36 pm in reply to: Thunderbolt is a good idea but…

    [Mel Feliciano] “Am I the only one exited about this product?”

    Hello Mel! No, You aren’t the only one who is excited!!!

    Thought I hoped for a product more like the Matrox CompressHD board
    (Teranex Mini in PCI-E form factor) for F I L E – B A S E D PROCESSING,
    I find the new BMD Teranex very well designed and very affordable.
    It has the spirit of democracy in it!

    BMD’s concept of making Teranex rack-able Thunderbolt I/O devices is really great and future proofed,
    thought a second port for daisy chaining would be reasonable!
    Thunderbolt also does have more than enough bandwidth for F I L E – B A S E D PROCESSING.

    Starting a small app; set HW in well designed interface up; Quicktime file in; processed quicktime file out!

    F I L E – B A S E D PROCESSING is an absolute must have for such a device in the 21st century!
    Can’t believe the other vendors still don’t have options for that on their boards with HW-scalers…

    F I L E – B A S E D PROCESSING means:

    Starting a small app; set HW up; Quicktime file in; processed quicktime file out!

    That is F I L E – B A S E D PROCESSING !

    Best regards,
    Bernhard

    PS: Have I mentioned that I would like to see
    F I L E – B A S E D PROCESSING
    on BMD’s Teranex products? 🙂

  • Hello Floh,

    Thank You for replying!

    We have updatet Open-E to V6. But I don’t think this is the problem since
    the problem occurs with the update to M100 V2.1

    Best regards,
    Bernhard

  • Bernhard G.

    March 28, 2012 at 1:11 pm in reply to: Premiere Pro 6 to 5.5 frame grab comparison

    Hello,

    FCP-X does not use Quicktime, it uses A/V Foundation, the new media framework.
    (Not to mistake Quicktime the player app and container format with Quicktime, the framework.)

    FCP7 was a Quicktime native app, as Media100 is by the way
    (and is also fast; but since we can expect the EOL of Quicktime framework … )

    PP needs to use the Quicktime framework as a translator that decompresses the
    images and passes them to the Mercury Engine.

    Other formats are directly translated my the Mercury Engine.

    Best regards,
    Bernhard

  • Hello,

    what I really would like to see at NAB are all the great hardware scalers
    in our I/O-Hardwares being enabled to work F I L E – B A S E D!

    We are very proud of our 100% file-based workflow here. But when it comes to video scaling,
    every single software out there is simply a mess. I’ve tested them ALL…
    I can’t hear nor read “bicubic” and “bilinear” algorithm any more!!!

    The point is, we already do have the best scalers with
    content adaptive scaling and anti-aliasing in our workstations!
    But we simply can’t use them file-based; qt file in – processed qt file out.
    (Exception: Matrox MAX; really nice but 8bit and H.264 only)
    The current workaround sending a live signal out of the computer
    to scale and re-capture it is simply a pain! It doesn’t fit into the 21st century!

    Best regards,
    Bernhard

  • Bernhard G.

    March 18, 2012 at 9:54 am in reply to: Premiere Pro 6 to 5.5 frame grab comparison

    Hello,

    the problem with AVC-Intra is the same as it was with DVCPro50:
    They are superb codecs for (camera-)recording from uncompressed,
    but are not robust enough for high-end post production.
    (robust = significantly keeping quality at re-encoding)

    They are perhaps the best native camera codecs for DNG, but nothing for DI.
    That said, one of the most popular DI codecs before Apple released ProRes,
    was DVCPro50 …

    But the more I think about the problem, the more I like DIRAC PRO aka Schroedinger …
    https://diracvideo.org/
    It’s open source!

    Best regards,
    Bernhard

  • Bernhard G.

    March 17, 2012 at 1:23 pm in reply to: Premiere Pro 6 to 5.5 frame grab comparison

    Correction of my former post:

    DIRAC actually does support 4:4:4 and currently up to 16bit,
    and resolutions up to 8K (theoretical no restrictions at all):
    https://diracvideo.org/

    BTW: the enduser-version of DIRAC is called “Schroedinger”

    Coding HW is very affordable:
    https://www.numediatechnology.com/
    Would be rediculous if no one could build a field recorder around it …

    Best regards,
    Bernhard

  • Bernhard G.

    March 17, 2012 at 8:57 am in reply to: Premiere Pro 6 to 5.5 frame grab comparison

    Thank You for the clarification, Dennis.

    There is still an alternative to ProRes, DNxHD and Cineform:
    No, not GV HQX, but BBC’s Dirac Pro:
    https://www.bbc.co.uk/rd/projects/dirac/diracpro.shtml

    It is an Open Source (!) codec developed by the BBC
    (doesn’t Adobe cooperate with the BBC according to Adobe’s marketing on CS5?),
    it’s based on Wavelet like Cineform, and does 10bit 4:2:2.
    As I have seen, HW-coding / decoding chips are available.
    The only thing that is missing is 12bit 4:4:4

    This could be an viable option.

    Best regards,
    Bernhard

  • Bernhard G.

    March 16, 2012 at 2:29 pm in reply to: Premiere Pro 6 to 5.5 frame grab comparison

    Hello Dennis,

    there is one more important thing to consider.
    External field recorders are very popular today.
    And since Apple starts to dominate the market with ProRes
    in conjunction with all the recorders it is simply true:
    the availability of field recorders determines the choice of NLE;
    at least for all those who want a bit of more quality than
    the camera manufacturers would allow to us.

    We also stuck at FCP here and are still interested in the development of FXP-X,
    only because of ProRes and our KiPros…

    So if Premiere would get a high-end intermediate codec,
    Adobe would also need to take care that there are
    enough field recorders to support it immediately;
    e.g. by giving away free licenses of the codec to the HW-manifacturors
    (if technically possible to implement as firmware update)

    Best regards,
    Bernhard

  • Bernhard G.

    February 18, 2012 at 9:20 am in reply to: I can only dream

    Hello, I dream of:

    – BMD acquiring Woodman Labs, manufacturer of the GoPro Cams and owner of the Cineform Codecs;
    allowing BMD to implement Cineform on the HyperDecks and giving away licenses of the best Intermediate-Codec available today with every BMD Product. One superb codec that works on all NLEs on all platforms!

    – BMD fully integrating the Teranex-assets into the company, leading to extreme highend-image-processing on BMD-Hardware and allowing a product like the Teranex Mini in a form of a PCI-E board,
    doing FILE-BASED image processing – quicktime file in / processed quicktime file out. Also integrating Teranex algorithms into DaVinci, CUDA-accelerated. And PLEASE get rid of Teranex’ premium-product philosophy: this has broken it’s neg and doesn’t fit into the 21st century any more…
    once again: F I L E-B A S E D ! ! !

    – a realtime streaming encoder based on the ProRecorder

    – an evolvement of the ATEM switchers: some kind of convergence of HW / SW,
    somewhere into the direction of a Newtec TriCaster with virtual studio, etc.

    Best regards,
    Bernhard

Page 10 of 14

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy