Intensity Pro 4K Media Express crashes on ProRes capture

Anyone else having issues capturing via Media Express on OS X 10.11? I have an Intensity Extreme Thunderbolt and when i click capture, it crashes with the following error:

Code: Select all

Process:               MediaExpress [13485]
Path:                  /Applications/Blackmagic Media Express.app/Contents/MacOS/MediaExpress
Identifier:            com.blackmagic-design.mediaexpress
Version:               ???
Code Type:             X86 (Native)
Parent Process:        ??? [1]
Responsible:           MediaExpress [13485]
User ID:               501

Date/Time:             2015-10-01 18:57:04.655 -0700
OS Version:            Mac OS X 10.11 (15A282a)
Report Version:        11
Anonymous UUID:        37D512F4-77C9-C217-A76F-7EC83083CC19


Time Awake Since Boot: 42000 seconds

System Integrity Protection: enabled

Crashed Thread:        13

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000004
Exception Note:        EXC_CORPSE_NOTIFY


I've been digging into this issue a little more and found that Media Express only crashes if i am using a ProRes codec. If using uncompressed it captures find. I also tested capturing in Premiere and there's no problem using ProRes. I've also tried on both my iMac 5k and MacBook Pro and the issue is the same. I did talk to support and they said that they haven't certified the drivers yet for OS X 10.11 so hopefully that will fix the issue when they release the certified/updated drivers.

I am on the latest El Capitan beta, and media express always quits when i stop capture (and it just leaves a corrupted and unusable file). I dont think I had this issue on the El Capitan official (non-beta) release (or maybe i just didnt try). Nope, just checked with the official non-beta release, same thing.

[Tony Rivera]

Can you provide more system info, product you're using and how you're capturing so we can have this passed along?

I have had this exact same issue occur with my Intensity Pro 4k and Media Express on the GM of El Capitan.

An excerpt from the crash log (let me know if you need more):

Code: Select all

Process:               MediaExpress [655]
Path:                  /Applications/Blackmagic Media Express.app/Contents/MacOS/MediaExpress
Identifier:            com.blackmagic-design.mediaexpress
Version:               ???
Code Type:             X86 (Native)
Parent Process:        ??? [1]
Responsible:           MediaExpress [655]
User ID:               501

Date/Time:             2015-10-07 13:54:04.669 -0700
OS Version:            Mac OS X 10.11 (15A284)
Report Version:        11
Anonymous UUID:        24DB2F26-ECFF-5FBC-40F2-9701A76F138D


Time Awake Since Boot: 1000 seconds

System Integrity Protection: enabled

Crashed Thread:        17

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000004
Exception Note:        EXC_CORPSE_NOTIFY


My system specs:

MacPro5,1,
2 x 6-Core Intel Xeon, 3.06 GHz
48 GB RAM
NVIDIA GeForce GTX 770 (4096 MB)

Intensity Pro 4K is in PCIe slot #2.


Hope to get this resolved soon. Let me know how to proceed.

I have El Capitan on a z97 pro wifi motherboard, with a 4790k Intel processor, 16gb of ram, and a Samsung evo SSD. Media Express was working great before I upgraded to El Capitan from Yosemite.

I have narrowed down the issue. The issue only happens when I am using any of the prores capture formats. If I use the quicktime uncompressed, or the DPX format, it works. I assume this may be related to either El Capitan, or the new Pro Video Formats version (2.0.3). I am trying to find an older version to test.

UPDATE

I tested both the El capitan official release, and the latest beta, same issue. I tested the newest desktop video drivers and the previous ones, same issue. Also, I managed to find older "Pro Video Format" installers, and same issue. In all of these, Media Express crashes when I stop capturing, if I capture with one of the prores settings, but it works with uncompressed and DPX. Please fix this as the only ones I use are the prores (uncompressed leaves too large files, and DPX just makes tons of individual files)

Same issue for me on a 13" 2013 MBP:
2.8Ghz Intel Core i7
16GB DDR3 RAM
Recording to the internal SSD.
Running El Capitan (problem wasn't there with Yosemite)

Any of the Prores formats just cause Media Express to crash either when I start recording (ProRes 422 Proxy) or when I stop recording (ProRess 422 LT). Works fine for Uncompressed, but I haven't got the storage space for that! Please fix

Same issue here with 2D Teranex
Model Name: Mac mini
Model Identifier: Macmini6,2
Processor Name: Intel Core i7
Processor Speed: 2.6 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
Using latest Teranex 4.2 update, capture with 3.4.1 ME with both 10.10/10.11.
1) 10.10.5 capture and exit normal.
2) 10.11 capture seems normal exit crashes system (can send complete crash report if desired). File is corrupt and unusable. Happens 100%. Stopped using under 10.11, have too much work to do.
Only tried it with ProRes 422, ProRes 422HQ and ProRes 4444
Hopefully a solution soon.

I'm glad I read this because I've just upgraded a similar spec Mac Mini to El Capitan but not yet upgraded Media Express. I'll hold off right now - especially since I have a lot of captures to ProRes to perform and I don't need the hassle!

I looked at the crash log, and it says thread 18 crashed, so here is the paste for thread 18. El Capitan has been out for months now so there is little excise for this guys.

Code: Select all

Thread 18 Crashed:
0   com.blackmagic-design.mediaexpress   0x00b97144 MediaLib::FileWriterMovImp::onClose() + 564
1   com.blackmagic-design.mediaexpress   0x00bed796 MediaLib::Recorder::closeFileWriters() + 70
2   com.blackmagic-design.mediaexpress   0x00beb8cc MediaLib::Recorder::finishRecording(MediaLib::Errors::Error) + 76
3   com.blackmagic-design.mediaexpress   0x00bed1a9 MediaLib::Recorder::processMessage(boost::shared_ptr<MediaLib::Messaging::Message>) + 585
4   com.blackmagic-design.mediaexpress   0x00b9ff3c MediaLib::MediaHub::processMessage(boost::shared_ptr<MediaLib::Messaging::Message>) + 412
5   com.blackmagic-design.mediaexpress   0x00ba0c70 MediaLib::MediaHub::postMessage(boost::shared_ptr<MediaLib::Messaging::Message>) + 48
6   com.blackmagic-design.mediaexpress   0x00ba7ca7 MediaLib::MediaHubElement::postMessage(boost::shared_ptr<MediaLib::Messaging::Message>) + 55
7   com.blackmagic-design.mediaexpress   0x00b2e43d MediaLib::DLCaptureImp::stopCapture(MediaLib::Errors::Error) + 253
8   com.blackmagic-design.mediaexpress   0x00b3ad29 boost::detail::function::void_function_obj_invoker1<boost::_bi::bind_t<void, boost::_mfi::mf1<void, MediaLib::DLCaptureImp, MediaLib::Errors::Error>, boost::_bi::list2<boost::_bi::value<MediaLib::DLCaptureImp*>, boost::arg<1> > >, void, MediaLib::Errors::Error>::invoke(boost::detail::function::function_buffer&, MediaLib::Errors::Error) + 41
9   com.blackmagic-design.mediaexpress   0x001288f0 boost::signals2::detail::slot_call_iterator_t<boost::signals2::detail::variadic_slot_invoker<boost::signals2::detail::void_type, MediaLib::Errors::Error>, std::__1::__list_iterator<boost::shared_ptr<boost::signals2::detail::connection_body<std::__1::pair<boost::signals2::detail::slot_meta_group, boost::optional<int> >, boost::signals2::slot<void (MediaLib::Errors::Error), boost::function<void (MediaLib::Errors::Error)> >, boost::signals2::mutex> >, void*>, boost::signals2::detail::connection_body<std::__1::pair<boost::signals2::detail::slot_meta_group, boost::optional<int> >, boost::signals2::slot<void (MediaLib::Errors::Error), boost::function<void (MediaLib::Errors::Error)> >, boost::signals2::mutex> >::dereference() const + 64
10  com.blackmagic-design.mediaexpress   0x00127ce8 boost::signals2::detail::signal_impl<void (MediaLib::Errors::Error), boost::signals2::optional_last_value<void>, int, std::__1::less<int>, boost::function<void (MediaLib::Errors::Error)>, boost::function<void (boost::signals2::connection const&, MediaLib::Errors::Error)>, boost::signals2::mutex>::operator()(MediaLib::Errors::Error) + 456
11  com.blackmagic-design.mediaexpress   0x00b5675a MediaLib::DeviceHandler::onFrameDropped(unsigned long long) + 426
12  com.blackmagic-design.mediaexpress   0x00b2d2ee MediaLib::DLCaptureImp::processMessage(boost::shared_ptr<MediaLib::Messaging::Message>) + 718
13  com.blackmagic-design.mediaexpress   0x00b9ff3c MediaLib::MediaHub::processMessage(boost::shared_ptr<MediaLib::Messaging::Message>) + 412
14  com.blackmagic-design.mediaexpress   0x00ba4d80 boost::_mfi::mf1<void, MediaLib::MediaHub, boost::shared_ptr<MediaLib::Messaging::Message> >::operator()(MediaLib::MediaHub*, boost::shared_ptr<MediaLib::Messaging::Message>) const + 64
15  com.blackmagic-design.mediaexpress   0x00ba4cab void boost::_bi::list2<boost::_bi::value<MediaLib::MediaHub*>, boost::arg<1> >::operator()<boost::_mfi::mf1<void, MediaLib::MediaHub, boost::shared_ptr<MediaLib::Messaging::Message> >, boost::_bi::list1<boost::shared_ptr<MediaLib::Messaging::Message>&> >(boost::_bi::type<void>, boost::_mfi::mf1<void, MediaLib::MediaHub, boost::shared_ptr<MediaLib::Messaging::Message> >&, boost::_bi::list1<boost::shared_ptr<MediaLib::Messaging::Message>&>&, int) + 59
16  com.blackmagic-design.mediaexpress   0x00ba4c5d boost::detail::function::void_function_obj_invoker1<boost::_bi::bind_t<void, boost::_mfi::mf1<void, MediaLib::MediaHub, boost::shared_ptr<MediaLib::Messaging::Message> >, boost::_bi::list2<boost::_bi::value<MediaLib::MediaHub*>, boost::arg<1> > >, void, boost::shared_ptr<MediaLib::Messaging::Message> >::invoke(boost::detail::function::function_buffer&, boost::shared_ptr<MediaLib::Messaging::Message>) + 45
17  com.blackmagic-design.mediaexpress   0x00ba5a82 boost::function1<void, boost::shared_ptr<MediaLib::Messaging::Message> >::operator()(boost::shared_ptr<MediaLib::Messaging::Message>) const + 66
18  com.blackmagic-design.mediaexpress   0x00ba514f MediaLib::MessageQueue<boost::shared_ptr<MediaLib::Messaging::Message> >::runMessageQueueThread() + 591
19  com.blackmagic-design.mediaexpress   0x00ba6d9a boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, MediaLib::MessageQueue<boost::shared_ptr<MediaLib::Messaging::Message> > >, boost::_bi::list1<boost::_bi::value<MediaLib::MessageQueue<boost::shared_ptr<MediaLib::Messaging::Message> >*> > > >::run() + 42
20  com.blackmagic-design.mediaexpress   0x0036fd5f boost::(anonymous namespace)::thread_proxy(void*) + 127
21  libsystem_pthread.dylib          0x94638794 _pthread_body + 138
22  libsystem_pthread.dylib          0x9463870a _pthread_start + 155
23  libsystem_pthread.dylib          0x94635fa6 thread_start + 34

I looked at the crash log, and it says thread 18 crashed, so here is the paste for thread 18. El Capitan has been out for months now so there is little excise for this guys.

Actually the betas have been around for a few months, but the final release came out on Sept 30th. As Apple have changed thing on previous versions at the last minute that have stopped programs from working I suspect BM decided not to bother looking at it until the final release came out. Bear in mind that lots of other programs are also not working with El Capitan, which makes me think that Apple changed quite a bit under the hood. None of the Avid suite is supported under El Capitan yet and they recommend not to use it at this point

Intensity Pro 4K, Desktop Video 1.5, El Capitan 10.11, Mac Pro 2010.

When I click 'Capture' using ANY of the ProRes codecs, Media Express immediately crashes.

It does NOT crash when I use QuickTime Uncompressed or DPX. However, I don't have the storage space to use these codecs.

It didn't crash on Yosemite, but it's way too much of a pain to roll back everything. Hoping for a fix soon.

Here's a portion of the crash report…

Code: Select all

Process:               MediaExpress [15507]
Path:                  /Applications/Blackmagic Media Express.app/Contents/MacOS/MediaExpress
Identifier:            com.blackmagic-design.mediaexpress
Version:               ???
Code Type:             X86 (Native)
Parent Process:        ??? [1]
Responsible:           MediaExpress [15507]
User ID:               501

Date/Time:             2015-10-17 10:43:22.211 -0400
OS Version:            Mac OS X 10.11 (15A284)
Report Version:        11
Anonymous UUID:        496DBF0A-FD0C-BB57-D26B-C20322DE48EC


Time Awake Since Boot: 53000 seconds

System Integrity Protection: enabled

Crashed Thread:        17

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000004
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x4:
-->
    __TEXT                 0000000000091000-0000000000dd8000 [ 13.3M] r-x/rwx SM=COW  /Applications/Blackmagic Media Express.app/Contents/MacOS/MediaExpress


I have this issue as well.

Just installed released 10.11.1 OS same problem. Media Express 3.4.1 crashes (Thread 14, if Blackmagic wants crash log let me know) as soon as attempting to capture ProRes 422. Works fine with 10.10.5. Just tested with several earlier developer beta's (10.11.X) same problem. So this has been around for several months. Since I have several boot volumes with different OS versions I can avoid 10.11.X until it is fixed. However it would be nice if there was an ETA on a fix. Thanks.

Oh jesus. Why is it that jesus never makes life easy. He is a real jerk that guy. Anyhow. I have the same problem. Surprise!!! But for me the crash happens when I try to start the capture using Prores. The big ass format is no problem but.. it is a problem size wise. SOOO... What do here?

Just like you are saying it worked fine before El Capitan but no more.. I am using the Blackmagic Intensity Extreme.

Blackmagic: I do like you and I have quite a lot of your products but things like these make me wonder if I really should have bought that intensity extreme for almost 500 bucks.

I am looking forward to a solution to this shortly. I have a deadline coming up. When do you think this can be fixed?

Thank you!

It's not only Intensity Extreme, Media Express crashes with all cards when ProRes codecs are selected. BMD is working on a solution.

Just stating that I have exactly the same problem. Recording in Uncompressed 8-bit is taking up too much room...

Having the same issue, uninstalled and reinstalled desktop video, but still not working, regardless of what flavour of prores or uncompressed video captured.

Crashes upon recording stop, and quicktime file is corrupt and unusable.

Same issue here! Media Express crashes when I try to record in any Prores format after El Capitan update. I already reinstalled FCP-X, Pro-codecs, and Desktop Video 10.5. All software work fine, except for Media Express that keeps crashing only on Prores. It does work fine with DVCPRO though.

Does anyone have a clue of what is going on here?

You have to wait for the BM update to support El Capitan properly.

El Capitan was announced back in June and I'm guessing the beta versions had this problem too. It's hard to believe the problem wasn't on BM's radar months ago. Pretty frustrating that's it's taking so long to fix.

Wouldn't be the first time that Apple changed the OS on the final release compared to the Betas, which makes it impossible for companies to get things working before it's released. BM aren't the only ones not having working software, this is the statement from Avid 5 days ago
http://avid.force.com/pkb/articles/en_U ... N-and-ISIS

And Adobe software also still has issues as well

I just updated to 10.5.1, released 'Last Wednesday'.

Still crashes. ugh.

Although this time, rather than bombing out as soon as you click capture, it actually lets you capture footage for a while – it just crashes when you stop!

As previously, DVCPRO 50 and Uncompressed works fine, but I don't want to use those.

To be fair to BM, the 10.5.1 installer didn't state El Capitan as a supported system, it just said Mac OS X 10.10 Yosemite or later.

How long is it gonna be for ANOTHER Desktop Video update?

After checking every day for the past three weeks for software updates or post replies to this problem without success, I stumbled on a different thread in which davidcherrie and Adam Simmons were discussing audio driver problems with Desktop Video. In the discussion they mentioned their favorite old versions of Desktop Video.

I tried their favorites, uninstalling my 10.5.1 and trying 10.4.1 and 10.3.1.

The Media Express that comes with Desktop video 10.3.1 works fine with the ProRes 422 LT codec on my El Capitan system using an UltraStudio Express.

Exactly the same problem here... Where stopping capture on Media Express & using any Prores format, instant crash... Using El Capitan latest release...

Any ideas? Im stuck.

Same issue on my iMac running El Cap 10.11.1 Attempting ProRes 422. Crashes as I end capture. Let me know if you need more info.

Do other formats seem to work? I do not want large files, but could reduce later through QT if necessary.

As Dan said, going back to 10.3.1 seems to work for some people assuming your device can use those drivers

I just updated to 10.5.2, released today.

Still crashes. Like 10.5.1, it now crashes when you stop capture. Frustrating.

You might want to try an earlier driver, although the one that most people are having success with is 10.3.1 which won't work with the IP4K

I've had entirely different problems with earlier drivers. There was a period where analog audio would not be captured with video. I've had this Intensity 4K since April, and I would bet that 75% of that time i've had show stopping driver issues of one form or another. Hard to not feel angry about that.

I fully understand, on the PC side the most stable drivers are 10.4.3 but they crash when capturing RGB source into Mjpeg, have an issue with color space through component and won't autodetect a UHD signal from the Panasonic GH4. (Although BM claim it does with their GH4, just not with any other) The 10.5.1 drivers fixed the Mjpeg issue, but cause Win 10 to Blue-screen as do the 10.5.2

Sorry you're having issues too.

For the record I just tried all previous drivers, down to 10.4.1 (the version that fixed the audio issue I was having). Every one of them exhibits the ProRes crash.

Hello.
I have a Macbook Pro with Mac OS X El Capitan I just upgraded the Video Desktop to version 10.5.1 (and 10.5.2) and Media Express to version 3.5. I have UltraStudio Express capture and still not working.
The application starts up properly and apparently well recorded, but fails to stop recording. Fails only if the configuration is in Apple ProRes. If the setting is uncompressed video works correctly.
With Yosemite everything worked properly.

I hope that an urgent solution and is hurting me seriously

A greeting.

Note: I installed a version 10.3.7 as recommended and surprisingly it works correctly.

I have exactly the same issues described here with the Intensity Shuttle (thunderbolt). Uncompressed and DPX work fine - neither is useful to me though.

all ProRes capture formats crash Media Express. Downgrading to previous versions result in a purple screen.

Interestingly, After Effects CC2015 also crashes instantly when you try to render a ProRes 720x576 comp (using their 'PAL D1/DV' comp preset). This is the EXACT same frame spec as what's making Media Express crash.

Seems it seems like ProRes was modified in El Capitan in some way and 3rd party apps need updating to work again.

Today, Adobe released AfterEffects CC2015 13.6, which FIXES their ProRes crash. Your move, Blackmagic!

I was lucky I had premiere on my laptop, so I could go on with the on set editing job I did, when I had to find out recording wouldn`t work.
For the second day I installed 10.3.7, and it worked correctly.
Dear folks @ Blackmagic, I really appreciate your accomplishments with making resolve free, and creating amazing value cameras, but I have to ask:
How do you test thunderbolt device drivers, if not on mac computers with the latest software available?

I've used Media Express for several years with no issues. It's been rock solid whether recording ProRes from a capture device through thunderbolt or via USB to .mp4 from my ATEM TVS. But recently I've experienced crashes where a file is created with the right amount of data judging from size, but not recognized as a video recording. A friend of mine was able to rescue audio data out of that jumble but not the video, in the case of the mp4 file. My workflow for video capture, except for the cameras, is all Black Magic Devices to Mac. It's very frustrating because Media Express was very very reliable for work and now it's very risky, and useless for professional work. I often record long events as single large video files (like TED talks) so I wish the program would save the file at regular intervals so at least some of the video is salvageable. Right now if the app crashes during or at the end of the recording the entire recording is lost.

Hi I was wondering if there is some kind of update to media express to where it won't quit on me when I try to capture in prores format.i am using the shuttle and the version of media express that came with the device.thanks for your time.

Well you don't say which version of the BM software you have installed, but you can get different versions by going to the support website

Sry for the late reply.my current version is 3.5.i have looked on the support part of the website but can't seem to find any updates or newer versions maybe I'm looking in the wrong place?

Thanks for your time and help,it is much appreciated

You could try using a slightly earlier version

Experiencing the same challenge with OS X 10.11.2 Cannot find any resolution to this issue online or on the forums.

Where could I get an earlier version(link possibly) and I'm using El Capitan if that makes any difference.thanks for your time and have a merry Christmas.

You can download various versions from the BM Support page. Although there has been a newer release since your original post (10.5.3)

I have exactly the same issue of Media Express crashing when trying to record to a ProRes format. I have tested this on both my iMac and MacBook Air with the exact same results.

Hopefully, BlackMagic Design will address this issue in a prompt manner or if this is an Apple issue to strongly encourage Apple to find a fix if the problem is on their end.

So now that blackmagic has released about 2 updates since, can anyone confirm if it is now fixed or not?

Oh, I had missed the Dec 23 10.5.3 update as I was out of town for Christmas. Just updated.

Guess what. NOT FIXED. This is INFURIATING.

For the record, this is the THIRD update since I raised the issue on here and directly with them via email support.

Here's all that's new. Not even a mention of El Capitan in the requirements. Pathetic.

What's new in Desktop Video 10.5.3

Adds new features for the Blackmagic Cintel film scanner.
• Increases vertical stability range.
• Status M densities now used for negative colorimetry.
• Fixes some machines unloading during shuttle.
• Image framing position remembered.
• Print black smoothness improved.
• Improvements in Auto Black accuracy.
• Improved error notifications in DaVinci Resolve.

Minimum System Requirements

• Mac OS X 10.10 Yosemite or later.
• Mac OS X 10.9 Mavericks or later.
• Mac OS X computer with either Thunderbolt, PCIe slot or USB 3.0.
• 4 GB of system memory.

I ONLY bought this card to digitize analog video. I don't do HDMI in or out. So it's effectively been useless since September.

For all you saying I should just roll back to Yosemite… why should I? I shouldn't be forced to work in an older version of the operation system just to make this card work. Blackmagic has a responsibility to keep their products working. especially one they're still selling. They've known about El Capitan since the first betas in the summer for crying out loud.

I suspect when it eventually get's fixed, the next OS X release will be right around the corner and we'll be in the exact same boat for ANOTHER six months. Last Blackmagic product I will ever buy.

this has been an issue (media express crashing when capturing in prores) ever since el capitan came out about 4 months ago. Can anyone confirm if this has been fixed either by a Desktop Video update or an El Capitan update? I downgraded to yosemite about 2 months ago when it broke.

OK, so today saw the release of the FOURTH update since this issue was reported. Desktop Video 10.5.4.

What's new in Desktop Video 10.5.4
• Adds support for DNxHR capture on Artist DNxIO.
• General performance and stability improvements for all models.

Still no mention of El Capitan in the requirements. And of course… STILL NO FIX. UGHHHHHHHHH