Blackmagic Forum

Mark Grgurev wrote:

John Paines wrote:This is Windows, after all. "Upgrades" often don't go well. Also, privacy concerns with 10.

I've heard so many people say this but I've really never had problems upgrading Windows. Just makes me think people don't know what they're doing.

Said no one ever till it happens to them. A "piss poor release" from MS, pretty much put them on top. Let us use an analogy: "'Better to do and ask forgiveness than to ask permission'"; the MS version, Better to release and beat our competitors than to lose market share - we'll roll-out HOTFIXES as necessary.

As with many things (companies, management decision makers), their *MS* "Risk Management" area assesses the downside vs upside with their crafted algorithms, then pulls the trigger or not.

My IT $.02 says a best practice would be, do NOT upgrade(s) software or hardware, manually or automatically if you are in a valuable project - just complete it. Even having taken the precaution of a backup, archive, "restore" etc., will be a creative distraction and cost you valuable time you need or could be better invested.

We have a brand new workstation (HP, factory installed W10, 1803 version) no chance for back. The BM Resolve Studio intalled in BM dealer/support center and not working with .MTS files.

Please download and install 15b5. It has a fix for the Windows 10 1803 AC3 audio issue.

Dwaine Maggart wrote:Please download and install 15b5. It has a fix for the Windows 10 1803 AC3 audio issue.

Just updated to 1803 and then upgraded to 15b5 and I can confirm audio is now working for my AVCHD files. Thank you Blackmagicdesign!

Thanks! Working fine.

When Rel.15.0b5 was announced, I replaced the deffective Rel. 14.3 with it and got AC3 audio working fine !

Helas, that didn't last very long; When I reopened the project containing the fixed audio track, it got mute and I never managed to restore the sound track. The problem is different than the previous one (audio waveform is visible, but even the prescan of the clip is mute). Audio works fine outside of Da Vinci Resolve. I had both DELL and Microsoft look at the problem. Since the computer is new, they accepted - relunctantly- to assist , ran their diagnostics but could not find any fault in Windows nor in the HW set up :

Needless to say, I have tried all tricks that I can think of, including :
I have already re-installed Rel 15.0b5
I have tried Da Vinci Resolve most recent Rel 15.0b6,
I have reinstalled the Realteck audio driver
I have tried external speakers
I have created a DVR project with only an audio track on the time line.
I have check the sample rate - 48 KHz - for AC3 audio track,

Can anybody think of something else that I can try to fix this new problem ?
Many thanks,

Michel Sterling wrote:When Rel.15.0b5 was announced, I replaced the deffective Rel. 14.3 with it and got AC3 audio working fine !

Helas, that didn't last very long; When I reopened the project containing the fixed audio track, it got mute and I never managed to restore the sound track. The problem is different than the previous one (audio waveform is visible, but even the prescan of the clip is mute). Audio works fine outside of Da Vinci Resolve. I had both DELL and Microsoft look at the problem. Since the computer is new, they accepted - relunctantly- to assist , ran their diagnostics but could not find any fault in Windows nor in the HW set up :

Needless to say, I have tried all tricks that I can think of, including :
I have already re-installed Rel 15.0b5
I have tried Da Vinci Resolve most recent Rel 15.0b6,
I have reinstalled the Realteck audio driver
I have tried external speakers
I have created a DVR project with only an audio track on the time line.
I have check the sample rate - 48 KHz - for AC3 audio track,

Can anybody think of something else that I can try to fix this new problem ?
Many thanks,

Hello,

Windows Control Panel => Hardware and AUDIO => Sound:
How is the sound card configured? This is the default device?

Post screen captures your configuration and also the control panel of Davinci Resolve.

From a workflow perspective I would avoid working directly with AVCHD.
I would convert the audio to wav and remux the new audio and video stream to mp4.

Resolve will handle this without any problems.

Interesting suggestion ! Could you tell me why - in your opinion - one of the most popular video formats should not considered when using Resolve ?

Michel Sterling wrote:Interesting suggestion ! Could you tell me why - in your opinion - one of the most popular video formats should not considered when using Resolve ?

There is added processing overhead. Resolve and the system have to spend additional resources decoding the footage to play it and work with it and avoid issues. This isn't unique to Resolve.

Better off transcoding h.264 and AVCHD footage you are working with to a format such as Proress or DNxHD/DNxHR.

The problem with transcoding is that it adds quite a significant extra step to the workflow when you're dealing with non-studio-quality footage (such as that uploaded to YouTube).

Many other NLEs cope with AVCHD and other H264 formats quite competently so although I understand that Resolve is not targeted at that market, I really think that handling AVCHD/MP4 files is a very important feature these days for any NLE.

I've chose Resolve as my NLE despite the issues with H264 because of its other many strengths and I'm pretty sure that if concessions were made to the group who find this codec more than adequate for their needs, a much greater market share could be had for the product. And, even though I'm just editing for YouTube, I'm still laying out my $300 because I believe in paying for the tools I use -- and many others in this community have similar ethics.

Michel Sterling wrote:Interesting suggestion ! Could you tell me why - in your opinion - one of the most popular video formats should not considered when using Resolve ?

I am talking from a practical perspective.

I believe that remuxing the video (or transcoding) and converting the audio to wav format will make your life easier.

RCModelReviews wrote:The problem with transcoding is that it adds quite a significant extra step to the workflow when you're dealing with non-studio-quality footage (such as that uploaded to YouTube).

Many other NLEs cope with AVCHD and other H264 formats quite competently so although I understand that Resolve is not targeted at that market, I really think that handling AVCHD/MP4 files is a very important feature these days for any NLE.

I've chose Resolve as my NLE despite the issues with H264 because of its other many strengths and I'm pretty sure that if concessions were made to the group who find this codec more than adequate for their needs, a much greater market share could be had for the product. And, even though I'm just editing for YouTube, I'm still laying out my $300 because I believe in paying for the tools I use -- and many others in this community have similar ethics.

+1