The Official Dirac Live Thread: Start w/1,2,3 🙋‍♂️

[ttocs]

Aug 21, 2021 17:59:09 GMT -5 LCSeminole said:

Aug 21, 2021 17:15:11 GMT -5 ttocs said:

I always uninstall the previous Dirac version using their Maintenance Tool. I did this earlier today and installed 3.1.1 with no issues. Ran it and loaded new filter.

I will suggest that if you get it running to always do a Cold Boot after running Dirac. I found this out a while back that weird things can happen with Levels if a cold boot is not done.

No matter what I do, when I run the Dirac software on my laptop, I get "No Devices Found". I would assume that my RMC-1 has been dropped from the Dirac servers as a licensed/approved processor since it is no longer being found. It worked a month ago on this same laptop, so I'm just not sure what if anything has changed. I've filled out the Emotiva form with my Name/Processor/MAC Address again and submitted it, so I guess I'll give this a go again next weekend. I doubt I'll have any time to call and talk with Tech Support this week as I've been averaging 65-70hrs/week at work lately so hopefully its a license glitch and it gets straightened out.

The cold boot has been my standard practice for quite some time as well.

Is the LED link light on your router for the RMC lit up?

I noticed something a couple weeks ago about reboots. With the latest FW it takes longer for reboots to have a successful network link for some unknown reason. I used to do Cold and LPS reboots for only a 1 minute off time. But now I've found that if I do a LPS reboot for less than 1:30 the network link isn't always successful for the processor. Likewise, if I do a Cold Boot, I found that it needs to be for 2 minutes of off-time, plus waiting 20 seconds after turning on the Rear Power Switch before pressing the On button on the Remote. The Link Light for the processor on the router will light up within 5 seconds if the link is successful, waiting for it to light up after this is pointless, it just takes 5 seconds. I think it has to do with the internals all getting revved up after being powered off, so waiting 20 seconds seems to work every time for me.

[LCSeminole]

Aug 21, 2021 18:41:57 GMT -5 ttocs said:

Aug 21, 2021 17:59:09 GMT -5 LCSeminole said:

No matter what I do, when I run the Dirac software on my laptop, I get "No Devices Found". I would assume that my RMC-1 has been dropped from the Dirac servers as a licensed/approved processor since it is no longer being found. It worked a month ago on this same laptop, so I'm just not sure what if anything has changed. I've filled out the Emotiva form with my Name/Processor/MAC Address again and submitted it, so I guess I'll give this a go again next weekend. I doubt I'll have any time to call and talk with Tech Support this week as I've been averaging 65-70hrs/week at work lately so hopefully its a license glitch and it gets straightened out.

The cold boot has been my standard practice for quite some time as well.

Is the LED link light on your router for the RMC lit up?

I noticed something a couple weeks ago about reboots. With the latest FW it takes longer for reboots to have a successful network link for some unknown reason. I used to do Cold and LPS reboots for only a 1 minute off time. But now I've found that if I do a LPS reboot for less than 1:30 the network link isn't always successful for the processor. Likewise, if I do a Cold Boot, I found that it needs to be for 2 minutes of off-time, plus waiting 20 seconds after turning on the Rear Power Switch before pressing the On button on the Remote. The Link Light for the processor on the router will light up within 5 seconds if the link is successful, waiting for it to light up after this is pointless, it just takes 5 seconds. I think it has to do with the internals all getting revved up after being powered off, so waiting 20 seconds seems to work every time for me.

Just to verify, what color is the link light on the back of the RMC-1 once connected successfully?

[ttocs]

Aug 21, 2021 19:23:44 GMT -5 LCSeminole said:

Aug 21, 2021 18:41:57 GMT -5 ttocs said:

Is the LED link light on your router for the RMC lit up?

I noticed something a couple weeks ago about reboots. With the latest FW it takes longer for reboots to have a successful network link for some unknown reason. I used to do Cold and LPS reboots for only a 1 minute off time. But now I've found that if I do a LPS reboot for less than 1:30 the network link isn't always successful for the processor. Likewise, if I do a Cold Boot, I found that it needs to be for 2 minutes of off-time, plus waiting 20 seconds after turning on the Rear Power Switch before pressing the On button on the Remote. The Link Light for the processor on the router will light up within 5 seconds if the link is successful, waiting for it to light up after this is pointless, it just takes 5 seconds. I think it has to do with the internals all getting revved up after being powered off, so waiting 20 seconds seems to work every time for me.

Just to verify, what color is the link light on the back of the RMC-1 once connected successfully?

There are two lights, amber and green. Only the amber is lit on mine right now and it's linked to the router.


My router is what I look at because it's easy to see. The left pair of lights are the XMC-2 on far left (#4), EDNIB to its right (#3).

[thompson12]

Aug 21, 2021 19:23:44 GMT -5 LCSeminole said:

Aug 21, 2021 18:41:57 GMT -5 ttocs said:

Is the LED link light on your router for the RMC lit up?

I noticed something a couple weeks ago about reboots. With the latest FW it takes longer for reboots to have a successful network link for some unknown reason. I used to do Cold and LPS reboots for only a 1 minute off time. But now I've found that if I do a LPS reboot for less than 1:30 the network link isn't always successful for the processor. Likewise, if I do a Cold Boot, I found that it needs to be for 2 minutes of off-time, plus waiting 20 seconds after turning on the Rear Power Switch before pressing the On button on the Remote. The Link Light for the processor on the router will light up within 5 seconds if the link is successful, waiting for it to light up after this is pointless, it just takes 5 seconds. I think it has to do with the internals all getting revved up after being powered off, so waiting 20 seconds seems to work every time for me.

Just to verify, what color is the link light on the back of the RMC-1 once connected successfully?

I have this problem all the time I have to power down XMC-2 unplug the power from the little black Dirac box for about 30 seconds plug it bach in reboot and it seems to work every time.

I have to do the Same thing all the time to make the android app work.


Mitch

[geebo]

Aug 21, 2021 17:59:09 GMT -5 LCSeminole said:

Aug 21, 2021 17:15:11 GMT -5 ttocs said:

I always uninstall the previous Dirac version using their Maintenance Tool. I did this earlier today and installed 3.1.1 with no issues. Ran it and loaded new filter.

I will suggest that if you get it running to always do a Cold Boot after running Dirac. I found this out a while back that weird things can happen with Levels if a cold boot is not done.

No matter what I do, when I run the Dirac software on my laptop, I get "No Devices Found". I would assume that my RMC-1 has been dropped from the Dirac servers as a licensed/approved processor since it is no longer being found. It worked a month ago on this same laptop, so I'm just not sure what if anything has changed. I've filled out the Emotiva form with my Name/Processor/MAC Address again and submitted it, so I guess I'll give this a go again next weekend. I doubt I'll have any time to call and talk with Tech Support this week as I've been averaging 65-70hrs/week at work lately so hopefully its a license glitch and it gets straightened out.

The cold boot has been my standard practice for quite some time as well.

I just tried 3.1.1 and it worked fine for me. I first tried 3.0.14 just to make sure then went to DL Dirac 3.1.1. While I was there I checked for my license and I also got the no valid licenses found error. I installed 3.1.1 and it went right in and found my RMC-1L. I loaded a project and it took a couple minutes to convert and then I exported the filters and exited Dirac without incident. But apparently the no license found message on the Dirac site doesn't mean much.

[ttocs]

Aug 21, 2021 20:16:21 GMT -5 thompson12 said:

Aug 21, 2021 19:23:44 GMT -5 LCSeminole said:

Just to verify, what color is the link light on the back of the RMC-1 once connected successfully?

I have this problem all the time I have to power down XMC-2 unplug the power from the little black Dirac box for about 30 seconds plug it bach in reboot and it seems to work every time.

I have to do the Same thing all the time to make the android app work.
Mitch

This brings up a great point, and I must amend what I said before. The EDNIB gets in the way of the processor getting a link.

It's been a long time since I've thought about this because I'm so used to leaving my EDNIB powered all the time, no reason really, it's just easy to leave it connected. The EDNIB is known to interfere with the processor in getting a link to the network, but this is highly dependent upon the router it's connected to. I have an old router that doesn't get bothered by the EDNIB at all but it's slow, I have another one that hates the EDNIB and would never let the processor get attention, and then there's the one I bought recently that is easy enough to work with so long as the reboot time is adhered to.

Without the EDNIB it is easy to get a link. LPS will work, but if you're already experiencing difficulty then a cold boot is best. Power off for a minute then it should just work when the EDNIB is disconnected or powered off. I guess it's just because I have the EDNIB connected that it needs a longer cold time before powering up. My apologies for misstating (whoever she is).

During the writing of this I did both an LPS and Cold Boot and both worked. Five seconds into each bootup the network link light illuminated.

[LCSeminole]

Gentlemen, Thanks for all of the ideas. I've gone as far as re-wiring the whole network switch and replacing some of the ethernet cables and no dice. I even went one step further and simply plugged the EDNIB/RMC-1/Laptop straight to the modem and still nothing. The RMC-1 allows me to "ENABLE" Dirac Live in the Speaker Preset menu, the RMC-1 plug in the back looks exactly as ttocs picture, but the software on the laptop when I run it spins on the "Select Device" screen and comes back when finished with "No Devices Found". At this point my only conclusion is that my RMC-1 MAC address must have been deleted/disabled/corrupted from the Dirac license servers and thereby not recognizing my RMC-1 when prompted.

Just for another verification, does the power light on the EDNIB stay RED, or does it change colors when loaded and ready?

[ttocs]

Aug 21, 2021 20:44:53 GMT -5 LCSeminole said:

Gentlemen, Thanks for all of the ideas. I've gone as far as re-wiring the whole network switch and replacing some of the ethernet cables and no dice. I even went one step further and simply plugged the EDNIB/RMC-1/Laptop straight to the modem and still nothing. The RMC-1 allows me to "ENABLE" Dirac Live in the Speaker Preset menu, the RMC-1 plug in the back looks exactly as ttocs picture, but the software on the laptop when I run it spins on the "Select Device" screen and comes back when finished with "No Devices Found". At this point my only conclusion is that my RMC-1 MAC address must have been deleted/disabled/corrupted from the Dirac license servers and thereby not recognizing my RMC-1 when prompted.

Just for another verification, does the power light on the EDNIB stay RED, or does it change colors when loaded and ready?

Yeah, if you get to ENABLE Dirac then the processor is linked.

My EDNIB's red light is on all the time, and so are both network lights.

[LCSeminole]

Aug 21, 2021 20:55:40 GMT -5 ttocs said:

Aug 21, 2021 20:44:53 GMT -5 LCSeminole said:

Gentlemen, Thanks for all of the ideas. I've gone as far as re-wiring the whole network switch and replacing some of the ethernet cables and no dice. I even went one step further and simply plugged the EDNIB/RMC-1/Laptop straight to the modem and still nothing. The RMC-1 allows me to "ENABLE" Dirac Live in the Speaker Preset menu, the RMC-1 plug in the back looks exactly as ttocs picture, but the software on the laptop when I run it spins on the "Select Device" screen and comes back when finished with "No Devices Found". At this point my only conclusion is that my RMC-1 MAC address must have been deleted/disabled/corrupted from the Dirac license servers and thereby not recognizing my RMC-1 when prompted.

Just for another verification, does the power light on the EDNIB stay RED, or does it change colors when loaded and ready?

Yeah, if you get to ENABLE Dirac then the processor is linked.

My EDNIB's red light is on all the time, and so are both network lights.
View Attachment

I'm highly convinced at this point that this problem is on DIRAC's end, as everything works but the Laptop/software giving me the "No Devices Found". I can't even load any of my previous projects, so until my laptop connects(and I've now tried another laptop and desktop), I can't do a thing.

[ttocs]

Aug 21, 2021 21:15:30 GMT -5 LCSeminole said:

I'm highly convinced at this point that this problem is on DIRAC's end, as everything works but the Laptop/software giving me the "No Devices Found". I can't even load any of my previous projects, so until my laptop connects(and I've now tried another laptop and desktop), I can't do a thing.

Yep, I think you're right. Getting that message means it connected to the servers otherwise you'd get an error saying can't connect to servers. bummer.

[LCSeminole]

Aug 21, 2021 21:26:19 GMT -5 ttocs said:

Aug 21, 2021 21:15:30 GMT -5 LCSeminole said:

I'm highly convinced at this point that this problem is on DIRAC's end, as everything works but the Laptop/software giving me the "No Devices Found". I can't even load any of my previous projects, so until my laptop connects(and I've now tried another laptop and desktop), I can't do a thing.

Yep, I think you're right. Getting that message means it connected to the servers otherwise you'd get an error saying can't connect to servers. bummer.

I just opened up a ticket with Dirac as well, though I don't think they'll help with this as I'm sure they'll need Emotiva to verify my MAC Address and do whatever it is they do. Until then, I'll simply set the Speaker Preset to "User" and get on with my weekend.

I'll also update this thread when I get a resolution and what the problem is/was.

[LCSeminole]

Update on my "No Device Found" problem. I opened up a ticket with Dirac support and they sent me back a link for "Troubleshooting: No Devices Found": I've copied and pasted this below. Anyhow, I got half way through and tried their suggestion, "Switch Windows network type to Private from Public", and this particular fix worked by changing my Windows 10 network type to "Private". Don't understand why as I've always had this on "Public", so for those of you having a similar problem, you may want to change this setting. In Windows 10, Start --> Settings --> Network & Internet --> Properties --> Under Network Profile change from "Public" to "Private".

-------------------------------------------------------------------------------------------------------

You may sometimes have a problem seeing Dirac-enabled devices, like AVRs or the Dirac Live Processor, inside the Dirac Live application. "No devices found" shows in the "Select device" screen. This is usually caused by a problem with communication inside your home network, so let's investigate.

Causes

Your AVR or Processor is not sending the proper signal to Dirac Live.
Dirac Live cannot access the signal being sent by your AVR or Processor.
The AVR or Processor's signal is being delayed.
Traffic inside your network is being rerouted or modified.
Often caused by firewall or antivirus software, or proprietary network setups.
Home network UPnP/File Sharing/Device Discovery is disabled.
This means that devices on your network cannot directly communicate with one another.
Dirac Live cannot access or read the IP of your AVR.

Solutions

Ensure that both the device running the Dirac Live application and the AVR or Processor are connected to the same network, with full internet connectivity.
Enable UPnP/File Sharing/Network Discovery on your router and all devices in your Dirac chain.
macOS: Set up file sharing on Mac - Apple Support
Windows: How to enable UPnP in Windows (computerhope.com)
Router: Instructions vary per device, usually accessible under "File Sharing," "Network Discovery," or UPnP in your router's settings. Please check your user manual or a web search for more info.
Connect your devices to your router via ethernet.
NAD units tend to have more consistent connection via wireless network connection. Try restarting your unit and connecting to wifi before accessing it with Dirac Live.
Switch Windows network type to Private from Public.
Make sure all devices are on the same subnet.
If your router or network switch supports IGMP Snooping, deactivate this feature.
Temporarily disable your desktop firewall or network security software to complete the measure and filter export process, and then reactivate it.
Kaspersky on Windows can particularly problematic. Here's our guide to fixing it: Troubleshooting: Problems with Kaspersky (Windows)

Find the device IP (usually accessible inside firmware menus) and connect to it directly using the "IP" button in the top left menu of the Dirac Live "Select device" screen.
You might also try assigning new IPs to your devices via your router settings menu. Setting a static IPs for the AVR might also help.
Assign a static IP to your AVR via router DHCP settings. Guide: How to Set Static IP Addresses On Your Router (howtogeek.com)
Deactivate any VPN connections on your network or devices where you will be running calibration.
Reduce complexity in your connection chain. If you are connecting the device to your network or computer through multiple stages, switches, or cables, please simplify this arrangement to the minimum number of transfers with the shortest cables. Reroutes and long cables can lead to timeouts.
Restart your AVR or Processor and the device hosting the Dirac Live application.
In extreme instances, a factory reset of your AVR might help.
Update to the latest firmware available for your device, as well as the latest Dirac Live or Processor (if applicable) version.

[leonski]

GOOD! I don't understand those nuances in Windows any more....but can't arugue with it WORKS NOW!

[uwe]

Aug 24, 2021 21:17:23 GMT -5 LCSeminole said:

Update on my "No Device Found" problem. I opened up a ticket with Dirac support and they sent me back a link for "Troubleshooting: No Devices Found": I've copied and pasted this below. Anyhow, I got half way through and tried their suggestion, "Switch Windows network type to Private from Public", and this particular fix worked by changing my Windows 10 network type to "Private". Don't understand why as I've always had this on "Public", so for those of you having a similar problem, you may want to change this setting. In Windows 10, Start --> Settings --> Network & Internet --> Properties --> Under Network Profile change from "Public" to "Private".

-------------------------------------------------------------------------------------------------------

You may sometimes have a problem seeing Dirac-enabled devices, like AVRs or the Dirac Live Processor, inside the Dirac Live application. "No devices found" shows in the "Select device" screen. This is usually caused by a problem with communication inside your home network, so let's investigate.

Causes

Your AVR or Processor is not sending the proper signal to Dirac Live.
Dirac Live cannot access the signal being sent by your AVR or Processor.
The AVR or Processor's signal is being delayed.
Traffic inside your network is being rerouted or modified.
Often caused by firewall or antivirus software, or proprietary network setups.
Home network UPnP/File Sharing/Device Discovery is disabled.
This means that devices on your network cannot directly communicate with one another.
Dirac Live cannot access or read the IP of your AVR.

Solutions

Ensure that both the device running the Dirac Live application and the AVR or Processor are connected to the same network, with full internet connectivity.
Enable UPnP/File Sharing/Network Discovery on your router and all devices in your Dirac chain.
macOS: Set up file sharing on Mac - Apple Support
Windows: How to enable UPnP in Windows (computerhope.com)
Router: Instructions vary per device, usually accessible under "File Sharing," "Network Discovery," or UPnP in your router's settings. Please check your user manual or a web search for more info.
Connect your devices to your router via ethernet.
NAD units tend to have more consistent connection via wireless network connection. Try restarting your unit and connecting to wifi before accessing it with Dirac Live.
Switch Windows network type to Private from Public.
Make sure all devices are on the same subnet.
If your router or network switch supports IGMP Snooping, deactivate this feature.
Temporarily disable your desktop firewall or network security software to complete the measure and filter export process, and then reactivate it.
Kaspersky on Windows can particularly problematic. Here's our guide to fixing it: Troubleshooting: Problems with Kaspersky (Windows)

Find the device IP (usually accessible inside firmware menus) and connect to it directly using the "IP" button in the top left menu of the Dirac Live "Select device" screen.
You might also try assigning new IPs to your devices via your router settings menu. Setting a static IPs for the AVR might also help.
Assign a static IP to your AVR via router DHCP settings. Guide: How to Set Static IP Addresses On Your Router (howtogeek.com)
Deactivate any VPN connections on your network or devices where you will be running calibration.
Reduce complexity in your connection chain. If you are connecting the device to your network or computer through multiple stages, switches, or cables, please simplify this arrangement to the minimum number of transfers with the shortest cables. Reroutes and long cables can lead to timeouts.
Restart your AVR or Processor and the device hosting the Dirac Live application.
In extreme instances, a factory reset of your AVR might help.
Update to the latest firmware available for your device, as well as the latest Dirac Live or Processor (if applicable) version.

Hopefully needless to say:
A prerequisite for finding the Emotiva processor is also the activation of the Dirac session in

Setup > Speaker > Preset 1 / 2 > Dirac Live > Enable

[bitzerjdb]

Hopefully this is an easy question. I haven't updated Dirac in a while, is the latest version 3.1.1 stable? I know there were issues with previous versions and really don't want to break something that is working OK today.

[KeithL]

There are a few IMPORTANT things that you need to know if you're digging into network issues... (which the guys at Dirac seem to have missed)...

(These apply to the XMC-2, RMC-1, and RMC-1L... but NOT the XMC-1.)

With our processors the Dirac Live software on your computer does NOT talk directly to your processor.

The processor talks directly to the NIB (Network Interface Box; aka the Raspberry Pi)...

The Dirac Live software then talks to the processor THROUGH the NIB.

If you are able to check the Enable Dirac box on the processor then the processor IS ABLE TO TALK TO THE NIB OVER YOUR NETWORK.

This means that both the processor and the NIB have been successfully assigned IP addresses and a connection has been established between them.

If, at that point, the Dirac Live software reports that it "can't find the processor", it is actually the NIB that the software is failing to find and connect to.

So, if that's the case, it is the routing and network connection between the software and the NIB that you need to troubleshoot.

(And, while it's theoretically possible that this part would work, but the NIB could otherwise not be working properly, we've never seen this happen.)

Aug 25, 2021 5:00:48 GMT -5 uwe said:

Aug 24, 2021 21:17:23 GMT -5 LCSeminole said:

Update on my "No Device Found" problem. I opened up a ticket with Dirac support and they sent me back a link for "Troubleshooting: No Devices Found": I've copied and pasted this below. Anyhow, I got half way through and tried their suggestion, "Switch Windows network type to Private from Public", and this particular fix worked by changing my Windows 10 network type to "Private". Don't understand why as I've always had this on "Public", so for those of you having a similar problem, you may want to change this setting. In Windows 10, Start --> Settings --> Network & Internet --> Properties --> Under Network Profile change from "Public" to "Private".

-------------------------------------------------------------------------------------------------------

You may sometimes have a problem seeing Dirac-enabled devices, like AVRs or the Dirac Live Processor, inside the Dirac Live application. "No devices found" shows in the "Select device" screen. This is usually caused by a problem with communication inside your home network, so let's investigate.

Causes

Your AVR or Processor is not sending the proper signal to Dirac Live.
Dirac Live cannot access the signal being sent by your AVR or Processor.
The AVR or Processor's signal is being delayed.
Traffic inside your network is being rerouted or modified.
Often caused by firewall or antivirus software, or proprietary network setups.
Home network UPnP/File Sharing/Device Discovery is disabled.
This means that devices on your network cannot directly communicate with one another.
Dirac Live cannot access or read the IP of your AVR.

Solutions

Ensure that both the device running the Dirac Live application and the AVR or Processor are connected to the same network, with full internet connectivity.
Enable UPnP/File Sharing/Network Discovery on your router and all devices in your Dirac chain.
macOS: Set up file sharing on Mac - Apple Support
Windows: How to enable UPnP in Windows (computerhope.com)
Router: Instructions vary per device, usually accessible under "File Sharing," "Network Discovery," or UPnP in your router's settings. Please check your user manual or a web search for more info.
Connect your devices to your router via ethernet.
NAD units tend to have more consistent connection via wireless network connection. Try restarting your unit and connecting to wifi before accessing it with Dirac Live.
Switch Windows network type to Private from Public.
Make sure all devices are on the same subnet.
If your router or network switch supports IGMP Snooping, deactivate this feature.
Temporarily disable your desktop firewall or network security software to complete the measure and filter export process, and then reactivate it.
Kaspersky on Windows can particularly problematic. Here's our guide to fixing it: Troubleshooting: Problems with Kaspersky (Windows)

Find the device IP (usually accessible inside firmware menus) and connect to it directly using the "IP" button in the top left menu of the Dirac Live "Select device" screen.
You might also try assigning new IPs to your devices via your router settings menu. Setting a static IPs for the AVR might also help.
Assign a static IP to your AVR via router DHCP settings. Guide: How to Set Static IP Addresses On Your Router (howtogeek.com)
Deactivate any VPN connections on your network or devices where you will be running calibration.
Reduce complexity in your connection chain. If you are connecting the device to your network or computer through multiple stages, switches, or cables, please simplify this arrangement to the minimum number of transfers with the shortest cables. Reroutes and long cables can lead to timeouts.
Restart your AVR or Processor and the device hosting the Dirac Live application.
In extreme instances, a factory reset of your AVR might help.
Update to the latest firmware available for your device, as well as the latest Dirac Live or Processor (if applicable) version.

Hopefully needless to say:
A prerequisite for finding the Emotiva processor is also the activation of the Dirac session in

Setup > Speaker > Preset 1 / 2 > Dirac Live > Enable

[KeithL]

Glad you got it sorted out...

The "Public" and "Private" setting in part determines how the firewall acts...
Basically, it "lowers your security settings when you tell it you're connected to a private network"...
(And, apparently, at least sometimes, the default "public" settings interfere with the Dirac Software...)

This is a good find since it's not something we'd heard about before...

[ Edit... at least one other person reported that Windows changed their setting from "Private" to "Public".

      This leads me to suspect that a recent Windows Update may have changed the default...   ]   

I've thrown in a bit of information below that may prove useful to others...

None of what you had going on has anything to do with your MAC address.

That gets checked AFTER the Dirac Live software connects to the processor.

If your MAC address hadn't been entered, or had gotten deleted, you would get a message from the software saying: "Unable to find an active license for your unit ID"
But that message would appear in a popup window in the software AFTER it had successfully connected to the processor.

Incidentally, your processor's license is tied to the MAC address alone...
It is NOT specifically tied to your name and there is no way to verify it on the Dirac Live website.
There is a SEPARATE option where you can "create a Dirac account" which will let you save projects online.
That has nothing to do with running the program, or with its not running, and you don't need to do it at all.
As long as the program can verify your processor's license, as per the MAC address, it should work.
(I suspect that this account isn't tied to your processor in particular at all - but I haven't really looked at it.)

What you've actually got is the software on the computer being unable to connect to the NIB.

The RED power light on the NIB should light and remain solid red whenever it is plugged in.
There is a tiny green LED right in the corner of the big red one.
That one should flicker quite a bit for five or ten seconds then die down to an occasional flicker (it's the equivalent of a hard disc activity light).
A pattern of four slow blinks from that tiny green light indicates a faulty boot-up on the NIB (usually a bad SD card).

Note that, if your AC line power "flickers", it may cause the NIB to crash and fail to reboot properly.
(It will reboot if powered off for several seconds - but sometimes not after a brief flicker.)
If that happens then you simply need to unplug it for several seconds to reboot it...

Aug 24, 2021 21:17:23 GMT -5 LCSeminole said:

Update on my "No Device Found" problem. I opened up a ticket with Dirac support and they sent me back a link for "Troubleshooting: No Devices Found": I've copied and pasted this below. Anyhow, I got half way through and tried their suggestion, "Switch Windows network type to Private from Public", and this particular fix worked by changing my Windows 10 network type to "Private". Don't understand why as I've always had this on "Public", so for those of you having a similar problem, you may want to change this setting. In Windows 10, Start --> Settings --> Network & Internet --> Properties --> Under Network Profile change from "Public" to "Private".

-------------------------------------------------------------------------------------------------------

You may sometimes have a problem seeing Dirac-enabled devices, like AVRs or the Dirac Live Processor, inside the Dirac Live application. "No devices found" shows in the "Select device" screen. This is usually caused by a problem with communication inside your home network, so let's investigate.

Causes

Your AVR or Processor is not sending the proper signal to Dirac Live.
Dirac Live cannot access the signal being sent by your AVR or Processor.
The AVR or Processor's signal is being delayed.
Traffic inside your network is being rerouted or modified.
Often caused by firewall or antivirus software, or proprietary network setups.
Home network UPnP/File Sharing/Device Discovery is disabled.
This means that devices on your network cannot directly communicate with one another.
Dirac Live cannot access or read the IP of your AVR.

Solutions

Ensure that both the device running the Dirac Live application and the AVR or Processor are connected to the same network, with full internet connectivity.
Enable UPnP/File Sharing/Network Discovery on your router and all devices in your Dirac chain.
macOS: Set up file sharing on Mac - Apple Support
Windows: How to enable UPnP in Windows (computerhope.com)
Router: Instructions vary per device, usually accessible under "File Sharing," "Network Discovery," or UPnP in your router's settings. Please check your user manual or a web search for more info.
Connect your devices to your router via ethernet.
NAD units tend to have more consistent connection via wireless network connection. Try restarting your unit and connecting to wifi before accessing it with Dirac Live.
Switch Windows network type to Private from Public.
Make sure all devices are on the same subnet.
If your router or network switch supports IGMP Snooping, deactivate this feature.
Temporarily disable your desktop firewall or network security software to complete the measure and filter export process, and then reactivate it.
Kaspersky on Windows can particularly problematic. Here's our guide to fixing it: Troubleshooting: Problems with Kaspersky (Windows)

Find the device IP (usually accessible inside firmware menus) and connect to it directly using the "IP" button in the top left menu of the Dirac Live "Select device" screen.
You might also try assigning new IPs to your devices via your router settings menu. Setting a static IPs for the AVR might also help.
Assign a static IP to your AVR via router DHCP settings. Guide: How to Set Static IP Addresses On Your Router (howtogeek.com)
Deactivate any VPN connections on your network or devices where you will be running calibration.
Reduce complexity in your connection chain. If you are connecting the device to your network or computer through multiple stages, switches, or cables, please simplify this arrangement to the minimum number of transfers with the shortest cables. Reroutes and long cables can lead to timeouts.
Restart your AVR or Processor and the device hosting the Dirac Live application.
In extreme instances, a factory reset of your AVR might help.
Update to the latest firmware available for your device, as well as the latest Dirac Live or Processor (if applicable) version.

[marcl]

Aug 25, 2021 8:29:20 GMT -5 bitzerjdb said:

Hopefully this is an easy question. I haven't updated Dirac in a while, is the latest version 3.1.1 stable? I know there were issues with previous versions and really don't want to break something that is working OK today.

No issues so far.  I've converted projects measured in 3.0.14.  And I've run a couple new calibrations.  No crashes, no problems ... and the results seem to be a little better than 3.0.14 in terms of final measured frequency and phase response.

[bitzerjdb]

Aug 27, 2021 11:35:55 GMT -5 marcl said:

Aug 25, 2021 8:29:20 GMT -5 bitzerjdb said:

Hopefully this is an easy question. I haven't updated Dirac in a while, is the latest version 3.1.1 stable? I know there were issues with previous versions and really don't want to break something that is working OK today.

No issues so far.  I've converted projects measured in 3.0.14.  And I've run a couple new calibrations.  No crashes, no problems ... and the results seem to be a little better than 3.0.14 in terms of final measured frequency and phase response.

Thanks!!!!!

[LCSeminole]

Aug 27, 2021 11:35:55 GMT -5 marcl said:

Aug 25, 2021 8:29:20 GMT -5 bitzerjdb said:

Hopefully this is an easy question. I haven't updated Dirac in a while, is the latest version 3.1.1 stable? I know there were issues with previous versions and really don't want to break something that is working OK today.

No issues so far.  I've converted projects measured in 3.0.14.  And I've run a couple new calibrations.  No crashes, no problems ... and the results seem to be a little better than 3.0.14 in terms of final measured frequency and phase response.

I just ran the 13pt measurement since my LCR substantially changed position-wise. It seems to me that the process of taking the 13 measurements was smoother or maybe it was more streamlined?....and the filter creation after the measurements along with the upload of the filter set to the RMC-1 seemed to be faster as well. While I can't put my finger on it, I think Dirac took more time on this new v3.1.1 to refine it, and seems to be optimized in the way it runs. I'm also quite pleased with how smooth the sound is, though this may be the result of me changing out my Klipsch Legend LCR's and Klipsch Reference surrounds(side/back) for an all Emotiva Reference timbre matched setup(ERT-8.3/ERM-6.3/ERM-6.2side/back), as the movie playback is thus far seemless.