Failed to initialize Red Decoder

I have looked for a solution for this problem for a long time and havent seemed to to find one yet.

When i log in I see the message "Failed to initialize RED Decoder with the configured number of decoders" I have been able to work with RED footage, and I have been getting this message for over a year. I am now on 12 though, and I am experiencing strange things, like the whole frame going funky for a single frame, or everything inside a window going blue for a frame, and its only with RED footage.

Im thinking it could be related. Either way Id like to finally put a stop to it.

I have read that sometimes torrent programs running in the background will cause this error message.

I have read that sometimes torrent programs running in the background will cause this error message.

is there a joke I'm not getting?

[Dwaine Maggart]

Mac or Windows?

Mac or Windows?

Mac

Mac or Windows?

Hey Dwaine.
Sorry for the slow interaction. I would really like to solve this problem, so if you have a solution, it would be very appreciated!
Thanks.

[Dwaine Maggart]

Detailed Mac troubleshooting below.

Note that if you have Splashtop Remote Access installed, it will cause this issue, and the previous solution has been to remove it.

You can probably skip the Resolve reinstall in the list below, as lately, it's usually one of the other issues listed causing the issue.

Failed to initialize Red Decoder Troubleshooting

"failed to initialize red decoder with the configured number of decoders"

This message occurs if the Resolve app cannot communicate with the DPDecoder processes.

The DPDecoder processes are background apps that are used to decode Red r3d files when there is no Red Rocket card available.

If this message appears, first thing to try is to save the Resolve Preferences and restart Resolve. This has fixed the problem for some people.

If that doesn't help, reinstall Resolve. This has fixed the issue for some people.

If that doesn't help, open the Mac Activity Monitor app and sort by Process Name, and see if the DPDecoder processes are running. There should be 8 DPDecoder processes running. If all 8 DPDecoders are not running and accessible, you'll get the "Failed to initialize" message.

If there are NOT 8 DpDecoder processes running, run CaptureLogs and send that to us.

Assuming there are 8 DPDecoder processes running, open a Terminal window and type: ping localhost

If that fails, then there is an issue with the Mac networking setup. That will need to be fixed. Fixing such an issue is beyond the scope of our ability to help.

If ping localhost works, then try this:

In the Terminal window, type the following line 8 times, and increment the 1000x from 10000 to 10007, then grab a screenshot of the Terminal window and send it to us:

sudo lsof -iTCP:1000x -sTCP:LISTEN

The first time you type this, it will ask for a password. Which is your user password.

If this comes back with no response, nothing is listening to the port.

DPDecoder chats over TCP ports 10000 through 10007. If something else is attached to any of those ports, then Resolve won't be able to communicate with that DPDecdoer app.

The lines above will show what (if anything) is listening on those ports.

I am having the same problem on OS X.

After pinging the ports I get issues with 10001 and 10007:

DPDecoder 9669 docbrown 5u IPv4 0x78fed03421f34499 0t0 TCP *:scp-config (LISTEN)
DPDecoder 9675 docbrown 5u IPv4 0x78fed03421f31771 0t0 TCP *:mvs-capacity (LISTEN)

Any ideas?

I am downloading 12.5.4. I have 12.5.2 on OS X 10.11.4.

I notice that Resolve starts much faster if I don't have Wi-Fi on. Also now I get this on port 10000

DPDecoder 1232 docbrown 5u IPv4 0x5ce112c76e6e1769 0t0 TCP *:ndmp (LISTEN)

Hey,
Just to add my report, I've always had this message (OSX.8 then .11) when µTorrent was running, nothing if not. JP Perry's previous post was no joke

I'm not running uTorrent though. This is my response in Terminal:

DPDecoder 6505 docbrown 5u IPv4 0x5ce112c78a268071 0t0 TCP *:ndmp (LISTEN)
DPDecoder 6506 docbrown 5u IPv4 0x5ce112c77a031b89 0t0 TCP *:scp-config (LISTEN)
DPDecoder 6507 docbrown 5u IPv4 0x5ce112c779d69769 0t0 TCP *:10002 (LISTEN)
DPDecoder 6508 docbrown 5u IPv4 0x5ce112c78a14ae61 0t0 TCP *:10003 (LISTEN)
DPDecoder 6509 docbrown 5u IPv4 0x5ce112c76e6e2979 0t0 TCP *:10004 (LISTEN)
DPDecoder 6510 docbrown 5u IPv4 0x5ce112c78a148281 0t0 TCP *:10005 (LISTEN)
DPDecoder 6511 docbrown 5u IPv4 0x5ce112c77a030071 0t0 TCP *:10006 (LISTEN)
DPDecoder 6512 docbrown 5u IPv4 0x5ce112c789f57281 0t0 TCP *:mvs-capacity (LISTEN)

[Dwaine Maggart]

Those appear to be normal responses to the lsof command, so apparently no issues with some other app hijacking those ports.

Please post a link to a Resolve Diagnostics log. With Resolve running, hold the Option key, and select the Help menu, then "Create Diagnostics Log On Desktop".

Ok thanks. Here is the diagnostic log:

https://we.tl/kojMSBTrdd

Does anyone have any ideas?

I have 7 DPDecoder running. And here is my logs.Tried to reinstalled and I uninstalled all the splashtop stuff but these made no difference.

DaVinci-Resolve-logs-20170104-190917.zip

(523.88 KiB) Downloaded 355 times

Hi, here is my log. I saw 7 DPDecoders running in the Activity Monitor. And I have tried to reinstall and uninstall all the splashtop staff but these just made no difference. Thank you!

[Dwaine Maggart]

I've just returned from time off. It appears Eugene has deleted his logs. If you'd like to post those again, I will look at them.

Weibo, something has port 10000 blocked on your system, so Resolve cannot open the 8th DpDecoder process on that port. That's why you only see 7 processes running, and that's why Resolve is complaining.

If you do the lsof test I posted above on port 10000, it should show you what's using the port.

Aside from being a nuisance, the DpDecoder warning is not usually critical. It doesn't matter at all unless you are using Red .r3d files. And even then, Resolve normally defaults to using GPU decoding of those files. Only if you disable that in Resolve Prefereces, and do not have a Red Rocket card, do the DpDecoder processes get used.

Same issue on 10.12.3

I do have splashtop but it's not running.

Tal

[Dwaine Maggart]

You run the lsof command 8 times.

You replace the x with a 0 through 7 each time.

So you check port 10000, 10001, 10002, 10003, 10004, 10005, 10006 and 10007.

sudo lsof -iTCP:10000 -sTCP:LISTEN
sudo lsof -iTCP:10001 -sTCP:LISTEN
sudo lsof -iTCP:10002 -sTCP:LISTEN

etc, etc.

If you have a Signiant client installed, it's probably that using one of the ports.

So I get this (see attached)... is there a way to fix?
I don't have Signiant client installed.

Thanks.
Tal

[Dwaine Maggart]

That would be the Splashtop Remote product using port 10000.

You will need to kill that, or configure it to use a different port (if possible).

Or ignore the message.

Here is what splashtop is telling me, any idea?



Support (Splashtop Business - Support)

Apr 18, 17:10 PDT

Hi,

Splashtop only uses port 443 for external communications. It uses TCP port 6783-6785 for local communications. I don't understand the screenshot but will pass this to our tech team to review.

Regards,
Splashtop Support Team

Good news!
Splashtop has released a new version that is not using port 10000 Problem just went away.

Tal

Same problem in windows 10...
any ideas?

thanks

[Dwaine Maggart]

viewtopic.php?f=21&t=60820

Thanks again Dwaine!!

Hi,

I'm having this issue as well. Just got the new 2018 MacBook pro and merged all my info over from my previous laptop (2016 MBP) Running DR15 Studio Beta 6

I check activity monitor and I do have 8 decoders running.

Any help is greatly appreciated.

Its ( the error messsage frim the title) a well known thing and so far it was in most cases in normal setups, caused by having the red decoder processes running beeing from a different release then the resolve version. (Not counting crazy network stuff or splashtop etc as dicussed above)

So if you just upgraded resolve, reboot and it will be gone.
Or kill these processes manualy and the right versions will be started when you start resolve.

Otherwise reinstall the target version of resolve again and reboot

[Dwaine Maggart]

Certainly try Glenn's suggestions, but if you still have the error, make sure you don't have a Signiant process running. Or any of the other Mac issues that might cause the problem listed in this thread.

necro...

Ok all was fine up to v15.0.1.wathver. I installed version 15.1.0.024 (IBC version) and i'm getting the error...

Anyone else?

still doing this to me EVERY time I start resolve Win 10

[Dwaine Maggart]

In Resolve 15.1, we've changed the DPDecoder ports, in an effort to avoid things like Signiant clients.

We now use ports 56790 - 56797, instead of 10000-10007.

So use the same troubleshooting steps as mentioned above, but for the new port range.

If you previously had this issue, it's hopefully gone in 15.1.

If you didn't have the issue, but starting with 15.1, you have the issue, then apparently something on your system is using one of the new ports. Or in the case of Windows, perhaps the firewall config needs to be updated to accommodate the new port range.

Dwaine,

I've just noticed that port 56797 in your new range of 56790-56797 is shared by LanSchool (Lenovo Software) on the Mac. Thus we get this error on all of our classroom stations. Is there any way to limit the number of decoders to seven, or manually/dynamically change the ports used within DaVinci? Many of our students use Red footage and the instructors use LanSchool- so disabling that is not an option. Any help would be appreciated.

Thanks so much!

You can add the following to the advanced tab in the resolve system preferences pane and restart Resolve.

DPDecoder.1.Instances = 7

Thanks Glenn!!! That seems to work!

Does anyone have any ideas?

Under windows 10 i just quit from skype before launch DaVinci.

I have exact the same problem and closing utorrent solved it.

You can add the following to the advanced tab in the resolve system preferences pane and restart Resolve.

DPDecoder.1.Instances = 7

Not working for me in this way, but working OK if change 7 for 0.

iMac 2013 High Sierra
Mac Mini 2018 Mojave
DVR 15.3 in both

Hi everyone

I'm desperate ..
Any of these solution are not working for me

Any news about this ?

[Dwaine Maggart]

Why are you desperate? Just ignore the error message.

Or do you have some issue other than the error message at start up?

For Mac Users getting this PITA error

Dwaine's steps from 2015 (above Tue Dec 08, 2015 6:37 pm) are still relevant. Here is the extra step that worked for me.

If ping localhost cause's an error
ping: cannot resolve localhost: Unknown host

Open the following file with TextEdit, Vi/Vim, or Nano. You will need to sudo if you are using Vi/Vim/Nano
/etc/hosts

Make sure that the file has all of the next 4 lines:
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost

Save the file, and re-open DaVinci Resolve.

If you are on Windows I think the host file is located at c:\windows\system32\drivers\etc\hosts. I cannot confirm the location because my windows machine is a paper weight at this point.

Hopefully, you are good to go. The root cause of this error for me: Skyfonts, a tool I use to manage fonts re-wrote one of my entries in etc/hosts

Hi,

I'm using Resolve 15 version 15.1.1.005. and I'm going to grade a project with RED footage.

I've tried all of the solutions posted above and none seem to work for me.

Is it too dangerous if I just ignore the message and keep on with the grading?

Thks!

[Dwaine Maggart]

Assuming you have a decent GPU that can handle the Red debayering, you can ignore the messages.

Is there some reason you are not using 15.3.1?

Hi,

Just found today that also the last NVIDIA CUDA devellopers kit do the same error. I just removed it and no more problem.

If it can help

Matt

Now this virus has also hit me (Win 10, Version 16.1.2.026). Yes - I know I only have to click away this error each time - but mabe there is a solution coming after all these years...

Having this issue in Resolve 16.1.2.

Is it OK to Deliver RED files even though I'm seeing this error?

[Dwaine Maggart]

See my messages in this thread.