-
23.976 -> 29.97 10 Bit still doesn’t work with 5.2.4 / DVC ProHD audio problems.
I’ve posted this twice before but still no response. Does anyone from BM monitor this site anymore? In any case I tried the 5.2.4 drivers and my 23.976 timeline will not play in the 23.976 -> 29.97 mode. It works when I go back to 5.1.2.
Also I had been reporting problems with DVC ProHD HD-SDI audio compatibility for months – this works perfect with my Kona 2. I tried with the new drivers as I saw this mentioned in the 5.2.4 description. The problem is still there. What was weird was I was playing back a 720 timeline with the FCP video out set to 1080 and the audio worked! But when I realized the setting was wrong and put it into 720, it went back to normal which is the audio cutting in and out at the deck in EE mode or record – I have tried every sort of sync setting on the deck and tried every setting in FCP. This is HD-SDI. AES works OK but you can only record 2 channels then. And as I said it works perfectly with my Kona 2 without having to do anything.
My system is a Dual 2.5 ghz G5 PCI-X with an HD Pro card in slot 4 and an xserve raid. This is FCP 5.04, QT 7.03
-
4 Replies
-
Hi Robert,
Sorry you haven’t received a reply to your questions just before and after Christmas as we’ve had a number of staff away on leave but they are back now.
[Robert Brown] “I had been reporting problems with DVC ProHD HD-SDI audio compatibility for months”
This problem is an odd one for several reasons:
1. Our AES audio output is de-embedded from the SDI output. So if the SDI audio had a problem, then the AES audio should have a problem. However you have reported that the AES audio output to the deck works fine. This suggests and issue with how the deck is handling SDI embedded audio.
2. You have mentioned that this problem only affects the Panasonic DVCPRO HD AJ-HD150 deck and does not affect other decks such as your Sony decks.
3. Other Cow reports have mentioned a problem with the way the AJ-HD150 handles SDI-embedded audio, eg Embedded audio input limitation on Panasonic AJ-HD150.I suspect this is going to be one of those situations where some hardware will work with it and some won’t based upon customer reports and those found on the Internet. Other DVCPRO HD models of decks appear to have no similar audio problems. Can you please check with Panasonic to see if there is a firmware/software update available for your model of deck as these can often solve tricky problems. Please let me know how you go.
Regards,
Luke Maslen
Blackmagic Design -
Hi Robert,
[Robert Brown] “In any case I tried the 5.2.4 drivers and my 23.976 timeline will not play in the 23.976 -> 29.97 mode. It works when I go back to 5.1.2.”
I’ve split this question in to a seperate sub-thread to make it easier to keep track of your two problems. I shall schedule this problem for testing and will let you know as soon as we have succeeded or failed in replicating the problem and work out what to do then.
Regards,
Luke Maslen
Blackmagic Design -
Hi Robert,
We’ve tested and replicated your problem and have a scheduled a fix for this coming release. Thank you for your report and sorry for the slow feedback of Christmas – New Year.
Regards,
Luke Maslen
Blackmagic Design -
Luke, Thanks for the response. It must be nice living in Australia, here were lucky to get a day or two off – work, work, work. In any case I suspect there is a general incompatibility – audio wise – between your card and this deck. The Avid tech description matched what is happening. But the Kona 2 does work. I have found though the Kona 2 and AJA IO to be incompatible with a JVC digi-s deck I have. Maybe AES is a loose spec? In any case I saw this mentioned in your driver description and so I wasn’t sure if you guys were able to duplicate it or not. Possibly it is just a problem between the BM chips and this deck. I don’t think there is anything else to check on my end. My settings are correct on the deck and in FCP and it never works except for that one time when FCP was in the wrong mode – weird.
The 23.98 -> 29.97 problem is a definite bug though and does it everytime with 5.2 or later drivers and not earlier.
Reply to this Discussion! Login or Sign Up