In my studio, it’s not blackmagic only. it happens in my MacBook Air too
Same here. With a MacBook Pro same crash without Blackmagic. With MacPro, every time I change sample rate, crash happens.
I have had video engine crashes as well with no Blackmagic being used.
However, it does look like all reported instances, on this thread at least, are mac users.
Darren “Mac Attack” Ingram
I reckon it’s a Mac Nuendo video engine thingy.
I use a Blackmagic Intensity on a windows 7 I7 64bits daw nearly daily without a video engine crash ever.
Also on Mac here.
I am finding the crashes very quiet now since I swapped in a ProRez (HQ) file instead of the H264 that was provided by a client. I am NOT saying this is the cause, but it could be.
To complicate diagnosis, I also have been trying switching off Bluetooth and Airport (wireless on the Mac) as I just had a hunch.
Anyways, let’s see what happens over the next few days - as I have also found the problem to come in “waves”. Which makes me also wonder if there might be a memory leak or something.
If SB need I can forward the H264 that was provided by client although it is copyright sensitive (and I will need some assurances before releasing it).
It is interesting that this does look to be a Mac issue. Maybe there is a variance in QT versions across the platforms?
Continuing - so far no crashes working with Apple Pro Res.
Apple Pro Res here causes crashes.
Here it crashes even without video, just changing the sample rate frequency.
Yes - it’s definitely not working correctly. I am NOT saying in my previous post that this is solved. At all.
In fact, client files never caused a problem in earlier versions.
to all of you on OS X, with and without BMD cards that are getting crashes in the Nuendo video engine.
Can you please list the contents of this folder:
And I’d also like from you what version of the Blackmagic driver you are on?
I can see from a couple of crash logs that some are on version 10.2, but please list it.
IF it is possible for you BMD guys to take the card out of the computer for a few hours and test with N6.5 It’d also help.
I work a whole lot with such systems, and might be able to help you.
My folder data:
drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 AppleAVCIntraCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:51 AppleHDVCodec.component drwxr-xr-x+ 3 root wheel 102 16 sep 02:52 AppleIntermediateCodec.component drwxr-xr-x 3 root wheel 102 25 ago 2013 AppleMPEG2Codec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 AppleProResCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DVCPROHDCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:50 DVCPROHDMuxer.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DVCPROHDVideoDigitizer.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DVCPROHDVideoOutput.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DVCPROHDVideoOutputClock.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DVCPROHDVideoOutputCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DXVCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:48 DesktopVideoOut.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 FCP Uncompressed 422.component drwxrwxr-x+ 3 antipop wheel 102 16 sep 02:51 FLACImport.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 IMXCodec.component drwxrwxr-x+ 4 antipop wheel 136 16 sep 02:43 XiphQT.component
For a test, move components out of the /Library/QuickTime folder to a safe location so the result looks like this:
drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 AppleAVCIntraCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:51 AppleHDVCodec.component drwxr-xr-x+ 3 root wheel 102 16 sep 02:52 AppleIntermediateCodec.component drwxr-xr-x 3 root wheel 102 25 ago 2013 AppleMPEG2Codec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 AppleProResCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 DVCPROHDCodec.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:48 DesktopVideoOut.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 FCP Uncompressed 422.component drwxrwxr-x+ 3 root wheel 102 16 sep 02:52 IMXCodec.component
/Library/QuickTime/FCP Uncompressed 422.component
Try what I described above!
But we won’t be able to run our video files if we do this. I wish SB would chime in here before we mess with our systems.
Also we know this problem is not exhibited with earlier versions of Nuendo, despite the system files already present.
Yes you will. You do not need all those DVCPROHD files to support DVCPROHD
I’m asking because we’ve had problems with the exact same with ProTools also.
I wonder where they come from all those DVCPROHD files?
Also DivX Decoder you don’t need to get Nuendo to work.
And this also just a test!!
Hmm. Looking closely I see you have suggested leaving active the core useful codecs. So yes, I take back what I said.
I had no idea PT was suffering too.
I think those codecs get installed by FCP. Or compressor. Don’t know…
Sometimes hard to realise we are 21st century and still struggling with all these things!
No, those other DVCPRO codecs must come from somewhere else because I haven’t seen them in a while.
We have FCP7, FCPX, Premiere CC, Compressor 4 etc. at work on all Macs, and they aren’t there.
We had problems with a BMD card apprx. a year ago, then I had to wipe all the quicktime components and get new ones, it was hard to sort. Today it is a little bit easier.
To make sure the core is updated, download the latest Pro Apps Codec update
This is the latest as of now:
This may be absolutely nothing at all, but I was looking at my mac’s Activity Monitor and noticed the processes videopreload, videooutput and videocode activate when Nuendo 6.5 is running. However, these processes quickly turn red and are marked as Not Responding. This is without any project loaded. Also, they are flagged as 32 bit processes. Should I be concerned about this?
Darren “32 bits ain’t what they used ta be” Ingram