"Failed to initialize RED decoder" error at DR 14 start-up

Hi; been a long time since my last post here

Even though I have no RED hw - every other DR 14b4 launch I'm getting this error:

resolve error.JPG (16.05 KiB) Viewed 8240 times

What can be causing it - a bug, or is there sth wrong with my installation? Cheers

Piotr

[Dwaine Maggart]

What's most likely to cause it these days on Windows is a Signiant client running in the background.

It uses one of the 8 ports that Resolve uses for running 8 background DPDecoder processes.

It's not possible to change the Resolve DPDecoder port assignments, and I'm not aware of a method to change the Signiant port assignment.

Thanks Dwaine - would you care to elaborate what a Signiant client is? I couldn't find anything like that in Task Manager's Processes or Services tab..

Regards

Piotr

I once had this screen a long time ago (V12.x?). I restarted the PC in safe mode without changing anything and I restarted the PC in normal mode. Since I never had this screen. I think (of memory) that it is following to have installed a program (but which one?). I thought that if it does not come back, I must have made a mistake somewhere ... Piotr, it's only once or all the time that this screen comes?

Jean-Claude - definitely more than once, but not at each and every launch of Resolve...

Cheers

Piotr

[Dwaine Maggart]

Signiant is what a lot of large post houses and studios seem to be using to securely move large files around:

https://www.signiant.com/

I would expect any Resolve users dealing with large post houses and studios might have a Signiant client installed.

Resolve uses TCP ports 10000 through 10007 to support the DPDecoder background processes. These processes are used to decode Red .r3d files if you don't have a Red Rocket card and you are not using Resolve GPU debayering. Almost all people will have one of these 2 things active. So the Failed to initialize messages are not critical and not impacting anything for the most part, except for being annoying.

This is a free app you can run on Windows that will easily show you what's using which ports. It should show you what might be using one or more of the TCP ports in the 10000-10007 range that Resolve wants to use:

http://www.nirsoft.net/utils/cports.html

Please let us know what you find.

Thank you Dwaine: good to know.

I get this msg when a torrent app running in background.

[Dwaine Maggart]

Yes, that is the traditional source of this error.

Thanks Dwaine!

Piotr

Solving the issue if uTorrent is using the 10000 TCP port:

1.- Open uTorrent
2.- Options -> Preferences
3.- Advanced -> net.discoverable
4.- Change from "True" to "False"
5.- Restart uTorrent

From now on uTorrent will not make use of the TCP 10000 port so Resolve will not complain.

Dwaine, thanks for the information. It was, indeed, a Signiant client causing the error here.

Hi Blackmagics,

on my MacBookPro14,1 / High Sierra 10.13.4
I have the same issue with DR14:
"Failed to initialize RED Decoder with the configured number of decoders"

the TCP-ports (without DR14) look good (without any occupation from 10000 to 10007)
the TCP-ports (with DR14) are occupying10000 to 10007.

to me that looks fine.
But DR14 does not work at all: no kind of media can be imported

any hints or recommendations?

thanks!
Patrick



the TCP-ports (without DR14) look good:

Last login: Tue Jun 12 12:49:49 on ttys000
DrPFK-MBP:~ patrick$ sudo lsof -i -P | grep -i LISTEN
Password:
cupsd 164 root 5u IPv6 0x4b07493054371aef 0t0 TCP localhost:631 (LISTEN)
cupsd 164 root 6u IPv4 0x4b074930537a90f7 0t0 TCP localhost:631 (LISTEN)
rapportd 318 patrick 3u IPv4 0x4b07493059f5b3b7 0t0 TCP *:52632 (LISTEN)
rapportd 318 patrick 4u IPv6 0x4b074930543720af 0t0 TCP *:52632 (LISTEN)


the TCP-ports (with DR14) look like this (10000 to 10007 are listening):

DrPFK-MBP:~ patrick$ sudo lsof -i -P | grep -i LISTEN
cupsd 164 root 5u IPv6 0x4b07493054371aef 0t0 TCP localhost:631 (LISTEN)
cupsd 164 root 6u IPv4 0x4b074930537a90f7 0t0 TCP localhost:631 (LISTEN)
rapportd 318 patrick 3u IPv4 0x4b07493059f5b3b7 0t0 TCP *:52632 (LISTEN)
rapportd 318 patrick 4u IPv6 0x4b074930543720af 0t0 TCP *:52632 (LISTEN)
Resolve 1341 patrick 11u IPv4 0x4b0749305d3e9797 0t0 TCP *:29001 (LISTEN)
DPDecoder 1349 patrick 3u IPv4 0x4b0749305b5dbd17 0t0 TCP *:10000 (LISTEN)
DPDecoder 1350 patrick 3u IPv4 0x4b0749305d8e4a57 0t0 TCP *:10001 (LISTEN)
DPDecoder 1351 patrick 3u IPv4 0x4b074930663d1a57 0t0 TCP *:10002 (LISTEN)
DPDecoder 1352 patrick 3u IPv4 0x4b0749305d3ebd17 0t0 TCP *:10003 (LISTEN)
DPDecoder 1353 patrick 3u IPv4 0x4b0749305a3fa797 0t0 TCP *:10004 (LISTEN)
DPDecoder 1354 patrick 3u IPv4 0x4b07493063522d17 0t0 TCP *:10005 (LISTEN)
DPDecoder 1355 patrick 3u IPv4 0x4b0749305d91c0f7 0t0 TCP *:10006 (LISTEN)
DPDecoder 1356 patrick 3u IPv4 0x4b0749305d9c8797 0t0 TCP *:10007 (LISTEN)
DrPFK-MBP:~ patrick$

[Dwaine Maggart]

That error will not prevent any media from working. If you can't see any media, you've got some other issue.

viewtopic.php?f=32&t=71894

I'm a fairly casual user of Resolve 15 on a PC that's more configured for business than gaming or editing. I've been getting this message at DR15 startup for a couple of months. In the past, I've ignored it, proceded and everything seemed to work fine. Today I get no audio out of DR15. Other applications, VLC audio & movies, etc. sound is fine, volume indicators in DR15 EQs show live audio output I checked the obvious (system sound, DS15 master volume - everything says its good. Rebooted DR15 twice, still no sound output from DR15. Based on previous experience, I'm suspecting something other than this "Failed to initialize RED decoder" message - but what? I have not yet tried booting in Safe Mode - that's such a pain but I guess I will try that now and monitor his forum for ideas.

[Dwaine Maggart]

This message is specifically related to Red media, and would have nothing to do with audio.

Go into Resolve Preferences - System - Video and Audio I/O, and toggle the Speaker Configuration setting, click Save, then go back into Prefs and toggle it back to it's original setting and click Save.

Does that fix the issue?

Rebooting my PC system got audio going but volume is very low - thanks for the guidance to a more correct resource. I still get this message about RED decoder but it doesn't seem to prevent any functioning. I'll just have to reboot every now and then.

I'm getting the same "Failed to initialize RED decoder" error on a MacBook Pro.

Seems like this issue has existed since 2013 and there's no definitive answers that I can see.

Has anyone got any ideas I can try?

Thank you

[Dwaine Maggart]

Detailed troubleshooting for Mac in this thread:

viewtopic.php?f=21&t=41858&hilit=+red+decoder

Go towards the end where I describe the new ports that DPDecoder uses starting in Resolve 15.1. Assuming you are using current Resolve code.

Windows 10 Pro
NVIDIA GTX 1080
AMD RYZEN 1700X
16GB RAM

Interestingly, no DPDecoders are active in the task manager. I checked the CPU Ports and don't see anything in the 1000 - 1007 area. Any help would be much appreciated here.

Link to the DR 16 B3 Log: Download active till 06-05-2019
https://we.tl/t-DEOlMxlaG2

Thanks.

[Dwaine Maggart]

The decoders are all being initialized.

This message can occur when you have multiple versions of Resolve installed. Might that be your scenario?

Good day,

Just 16 Beta. Hmm?

[Dwaine Maggart]

I give up?

There are no errors in the 8 DPDecoder logs. All 8 are happily launching and ready.

That being the case, the only other thing I'm aware of that will cause this error is having multiple versions of Resolve on a system, i.e. you renamed or copied the C:\Program Files\Blackmagic Design\DaVinci Resolve folder to something like C:\Program Files\Blackmagic Design\DaVinci Resolve15, so that you could have both 15 and 16 on the system.

At any rate, this is not a critical error, and you can just ignore it.

I just got this error on Windows 10 after upgrading 14 to 16. During the install, I elected not to install Davinci Panels. After v16 was installed, I started it and closed it several times, and got the error at each start up.

Turns out that Davinci Panels was still installed from v14, and v16's installation did not remove them. I was able to correct the "Failed to initialize RED decoder" error by uninstalling Davinci Panels from Window's control panel. So, check to make sure whatever options you selected when upgrading either match the previous installations options, or go and manually uninstall whatever is left over from the previous version, that you didn't select to install with the newer version.

The tip off was the previous post from Dwaine about possibly having two versions of the software installed. Hope this helps someone!