#Blackmagic desktop video 12.0 for mac os#
#Blackmagic desktop video 12.0 pro#
#Blackmagic desktop video 12.0 trial#
#Blackmagic desktop video 12.0 download#

Included software: Media Express, Disk Speed Test, LiveKey, Blackmagic Desktop Video Utility and Blackmagic drivers for Mac OS and Windows Media Express, Blackmagic Desktop Video Utility and Blackmagic drivers for Linux.Supported codecs: AVC-Intra, AVCHD, Canon XF MPEG2, Digital SLR, DV-NTSC, DV-PAL, DVCPRO50, DVCPROHD, DPX, HDV, HEVC, XDCAM EX, XDCAM HD, XDCAM HD422, DNxHR & DNxHD, Apple ProRes 4444, Apple ProRes 422 HQ, Apple ProRes 422, Apple ProRes 422 LT, Apple ProRes 422 Proxy, uncompressed 8 bit 4: 2:2, uncompressed 10 bit 4:2:2, uncompressed 10 bit 4:4:4.

Computer interface: Thunderbolt 3 (Mac OS, Windows and Linux).HDMI audio inputs: 8x channels embedded in SD/HD.SDI audio inputs: 16x channels embedded in SD/HD.SDI video inputs: 1x SDI rates 270 Mbit, 1.5G, 3G.

#Blackmagic desktop video 12.0 pro#

DaVinci Resolve, Avid Media Composer, Adobe Premiere Pro CC and many more

Records uncompressed and compressed video in highest 10-bit quality and is compatible with all common video software, e.g.

** Requires the latest Blackmagic's Desktop Video (version 12.0.

Fixed bug in device selection by index script.

Fixed bug with DeckLink output frame completed callback being out of expected order.

Fixed startup bug with first frame not being output.

Removed multiple initialisation calls at startup.

Internal rendering system heavily refactored.

Added new UI element to show output buffer health.

Added better detection of already in-use devices.

Split frame reading and writing from GPU and placed writing on DeckLink consumer thread via custom render context for more optimal throughput.

Performance improvement by removing lock (within lock) from frame expected display time tracking.

Added support to DeckLinkOutput to generate timecode output, and if synced to input stream it will pass that timecode through.

Added support for adjusting Unity frame-rate based on output health status, and added proactive rather than reactive late/dropped frame correction resulting in more robust frame drop prevention.

#Blackmagic desktop video 12.0 download#

** Please remember to download the latest version of BlackMagic's Desktop Video (11.5.0+) when upgrading to this new version.ĪVPro DeckLink version 1.9.0 has just been released! Please report any issues here on the forum, or preferably to our GitHub Issue tracker

Fixed IL2CPP support (by correct bool return size).

Fixed support for 10-bit 720p, 2K, 4K DCI modes where they wouldn’t be displayed correctly.

Fixed issue where switching from an 8-bit to a 10-bit mode would just show a blank screen.

Fixed genlock pixel offset not being set correctly.

Plugin now requires Unity 5.6 as a minimum.

Added Audio Mixer component for controlling levels of multiple audio channels.

Audio input and output performance and latency optimisations.

Audio input and output has better support for arbitrary number of channels (up to 64).

#Blackmagic desktop video 12.0 trial#

You can find the updated version on the Asset Store and the free trial version on our website. If you have any issues/questions please post to our GitHub so that our support team can reply:ĪVPro DeckLink version 1.8.2 has just been released! I hope this helps to answer some of your questions. In the future we hope to add more options to avoid this need for a second camera. One possible way around this would be to only use a single camera and then to blit the Camera.targetTexture to the screen after it has rendered. This could mean that the scene is rendered twice if you are usual an additional camera just for the DeckLinkOutput. The DeckLinkOutput component uses a Camera that you specify for it's rendering. The frame is also usually in an intermediate format like YUV422, so it's not ideal to use even if you could get hold of the memory. Uploading to the GPU happens inside out DLL plugin, so currently there is no way to get hold of it before then. If possible I would recommend trying to find a way to do any modification of the texture on the GPU.

This is why was created - however it is a scheduled event, so it will add latency to your video feed. Doing CPU processing can be very slow because the GPU will have to stall the rendering pipeline if you want to grab the texture immediately from GPU memory into CPU memory.