LCSeminole
Global Moderator 
Res firma mitescere nescit.
Posts: 20,852
|
Post by LCSeminole on Feb 25, 2021 16:31:24 GMT -5
Dirac 3.0.13 crashed all but one of the dozen times I ran that version. 3.0.11 works just fine. This is my experience with v3.0.13 as well, v3.0.11 just works. |
|
|
|
Post by vmbray on Feb 25, 2021 17:13:44 GMT -5
Updated to 2.2, worked fine the first day. Came back after a few days and turned the xmc2 on and had no signal on one hdmi, changed inputs, lots of popping sounds, got signal. Turned unit off and unplugged for 30 seconds per the network note, on reboot got no network. Unplugged again and wait, reboot, got lan again, on first hdmi got a loud blast of sound, switch inputs, clicks and pops, back to first hdmi, clicks and pops, got signal. The behavior of looping out after a few days was happening on 2.1 but the reboots weren’t accompanied by clicks and pops and so on. I may go back to 2.1 I don’t know.
|
|
|
|
Post by JKCashin on Feb 25, 2021 17:24:50 GMT -5
Unfortunately 3.11 is not available for Mac. The link is there, but it gives you 3.09
|
|
|
|
Post by doc1963 on Feb 25, 2021 17:51:51 GMT -5
Updated to 2.2, worked fine the first day. Came back after a few days and turned the xmc2 on and had no signal on one hdmi, changed inputs, lots of popping sounds, got signal. Turned unit off and unplugged for 30 seconds per the network note, on reboot got no network. Unplugged again and wait, reboot, got lan again, on first hdmi got a loud blast of sound, switch inputs, clicks and pops, back to first hdmi, clicks and pops, got signal. The behavior of looping out after a few days was happening on 2.1 but the reboots weren’t accompanied by clicks and pops and so on. I may go back to 2.1 I don’t know. With a full cold shutdown (power removed from the unit), 30 seconds is not long enough for the network interface card to reset. KeithL recommends at least one minute, but I personally would wait a bit more. I don’t know what seems to be so much different between the XMC-2 and my RMC-1L, but I haven’t experienced any of this “popping” behavior. It may be of interest, but I do not use Dirac. In fact, my Dirac kit is still in its shipping box. If you are using Dirac, have you downloaded a fresh set of filters after the firmware update...? Or, if you haven’t used Speaker Preset 2, does it still demonstrate the popping issue if Dirac isn’t part of the equation...? |
|
|
|
Post by jra on Feb 25, 2021 17:58:42 GMT -5
The problem is that, when you have processes that run in real time, the logging code itself alters the timing... And adds more of a processing load... And offers the opportunity for the added code to cause new and different problems...
And offers the opportunity for the log files themselves to overflow and cause problems... And, since the code isn't physically monitoring the hardware, it can only tell you when the code stopped...
And, of course, if your logger crashes, then it won't have time to save the data you want anyway...
It reminds me of a very humorous thing that happened way back when I was in high school... One of our computers sprang to life and typed: "System going down in..........." Of course it never completed the message... because it had crashed...
We do have such things... And we use them when and where useful and appropriate...
But they are not a silver bullet by any means...
Are you saying because a logger could crash or overflow there’s no reason to try to log? Other programs use this feature all the time. Among other nice code testing features. These betas with loggers activated should not be spread in public. So if they crash or misbehave is really not a problem. Btw you could simply log the startup as it seems the issue with the NIC is located there. Btw could you inform us why the Kernel hasn’t been updated since jan 2018 while your here? There must have been A LOT of bug fixes and improvements in Linux since then? And speed? Maybe this alone could help with the NIC issue? Are you seriously suggesting "update the kernel to see it fixes.stuff"? That way lies madness. An XMC box is not a rolling Linux distro where you can update to the latest and greatest to see if it's better. It's an embedded system with integrated components for hardware and software. You have to make changes one thing at a time and with great care and regression testing. Just because it's based on a commodity kernel doesn't mean you can randomly swap stuff in and expect it to keep working. In my day job you'd be laughed out of a design meeting for suggesting that ! |
|
|
|
Post by richter250 on Feb 25, 2021 18:27:43 GMT -5
Unfortunately 3.11 is not available for Mac. The link is there, but it gives you 3.09 Correct. 3.09 seems to be the latest for Mac. It works just fine for me. 3.13 crashes almost every time and it is a pain to get back up and running again. I don't really trust it even when it says the filters did transfer successfully. Stick with 3.09 if you have a Mac and wait for Dirac to come out with some new firmware. |
|
|
|
Post by trappistkane on Feb 25, 2021 18:36:21 GMT -5
Hi all,
I've been lurking in this forum for a few months now. I recently bought an XMC-2. I just want to share my experience so far. My experience have been smooth other than a few initial HDMI ARC issues. I updated it to the newest firmware as soon as I got the unit (before even connecting it to the tv). I have been experiencing some popping noise every now and then. Also, audio loss at the beginning of a tracks or pause/play. I was able to run the latest version of the dirac (still learning to use it). Definetly a different experience over my Denon...
|
|
|
|
Post by davidl81 on Feb 25, 2021 18:54:04 GMT -5
I have not been following the thread too closely, but after upgrading to FW 2.2 are others experiencing much more bass from their subs? Do I need to re run DIRAC? I’m just going to turn the subs down for now, but yeah it’s a big jump.
|
|
|
|
Post by krauley on Feb 25, 2021 19:03:15 GMT -5
Hey guys can you check something out for me. I added a new component to my system hence I changed the name under the input section. But after restarting it the old name was back. I changed it again and did a back up to both the system and to a usb drive. Then this morning when I turned it on the old name was back. Not sure if I have a problem or if its an issue with the new firmware (2.2). Could someone change the name of an input on an xmc-2 (dont think it matters which system you do it on) and see if it stays or reverts back to the old name after a shut down please? And more precisely try it on input #3. FW-2.2 Did you "back out" of the Menu? Arrow left, left, left, etc until all the way out. Some settings need this to "set" the setting. I just changed Input 1 and Input 3, Low Power Standby for a minute, then bootup. It's powered up now and the two Name changes are the new names I entered. yes i did but maybe i didnt so i will look into doing that the next time to see if maybe i didnt ?? thanks for replying and doing the check for me! and i must have not backed all the way out and just went straight to the backup which means im the problem. but thats good news because i would rather my XMC-2 be flawless then me be  All good. |
|
|
|
Post by yeeeha17 on Feb 25, 2021 20:18:03 GMT -5
So for some reason now I can’t get ARC to work and the system frozen and I had to reboot from the back switch. Tried everything to get it to work again but no luck. A work around was I ran an optical cable and that’s doing the trick. This will have to do for my wife as of now until I try the new 2.2 update. x2 - ARC just stopped working. I also ran an optical cable temporarily but then that started causing super high volume staticky/scratchy audio on the optical input. I checked the cable and connections and all seemed fine. I am not going to buy a 2nd optical cable so have been trying to get ARC to work all week with no luck. Seems I am going to have to buy a streaming stick and use the XMC-2 HDMI inputs from now on. Well I took it all apart, I mean unhooked all cables to the XMC-2 and TV and reinstalled everything again. So far it’s working like it’s supposed to. Let’s see how many days I can get it to stay working. |
|
cawgijoe
Emo VIPs 
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,033
|
Post by cawgijoe on Feb 25, 2021 22:17:05 GMT -5
Updated to 2.2, worked fine the first day. Came back after a few days and turned the xmc2 on and had no signal on one hdmi, changed inputs, lots of popping sounds, got signal. Turned unit off and unplugged for 30 seconds per the network note, on reboot got no network. Unplugged again and wait, reboot, got lan again, on first hdmi got a loud blast of sound, switch inputs, clicks and pops, back to first hdmi, clicks and pops, got signal. The behavior of looping out after a few days was happening on 2.1 but the reboots weren’t accompanied by clicks and pops and so on. I may go back to 2.1 I don’t know. With a full cold shutdown (power removed from the unit), 30 seconds is not long enough for the network interface card to reset. KeithL recommends at least one minute, but I personally would wait a bit more. I don’t know what seems to be so much different between the XMC-2 and my RMC-1L, but I haven’t experienced any of this “popping” behavior. It may be of interest, but I do not use Dirac. In fact, my Dirac kit is still in its shipping box. If you are using Dirac, have you downloaded a fresh set of filters after the firmware update...? Or, if you haven’t used Speaker Preset 2, does it still demonstrate the popping issue if Dirac isn’t part of the equation...? I have an XMC-2 and use Dirac and don’t have these pops and ticks. I have not run Dirac in awhile. |
|
|
|
Post by vmbray on Feb 25, 2021 22:35:59 GMT -5
I noticed that the dirac result sounded bright/harsh at volume so I turned it off and it sounds much better, smoother. So far pretty underwhelmed with dirac, have measured before/after and it doesn't even hit the target curve. Yes I've spent hours, different mics, etc. It's weird because it actually manages to leave whatever response bumps are there and somehow manage to make it sound worse. The firmware note says 30 seconds for network reset, my experience says two power offs, maybe I should wait a while, or go get coffee, or a snack. The good news is when the processor works, it sounds good. I'll probably do a full reset and not bother with dirac and see how things are, next time I have time.
|
|
|
|
Post by JKCashin on Feb 25, 2021 23:16:38 GMT -5
Unfortunately 3.11 is not available for Mac. The link is there, but it gives you 3.09 Correct. 3.09 seems to be the latest for Mac. It works just fine for me. 3.13 crashes almost every time and it is a pain to get back up and running again. I don't really trust it even when it says the filters did transfer successfully. Stick with 3.09 if you have a Mac and wait for Dirac to come out with some new firmware. Oh that's good to know, thanks so much |
|
|
|
Post by jasonf on Feb 26, 2021 1:15:29 GMT -5
I have not been following the thread too closely, but after upgrading to FW 2.2 are others experiencing much more bass from their subs? Do I need to re run DIRAC? I’m just going to turn the subs down for now, but yeah it’s a big jump. Yeah, the most common comment about 2.2 has been the resulting bass boost. Playing around a bit, I've noticed it changes depending on your speaker/size config. Overall I think it sounds better. On my system it doesn't just feel like there is more bass, the bass seems more defined and more punchy. |
|
|
|
Post by panasonicst60 on Feb 26, 2021 4:02:51 GMT -5
I noticed that the dirac result sounded bright/harsh at volume so I turned it off and it sounds much better, smoother. So far pretty underwhelmed with dirac, have measured before/after and it doesn't even hit the target curve. Yes I've spent hours, different mics, etc. It's weird because it actually manages to leave whatever response bumps are there and somehow manage to make it sound worse. The firmware note says 30 seconds for network reset, my experience says two power offs, maybe I should wait a while, or go get coffee, or a snack. The good news is when the processor works, it sounds good. I'll probably do a full reset and not bother with dirac and see how things are, next time I have time. Adjust Dirac eq target to fix the harshness. Increasing mid bass and or bass can help. I don't touch anything over 2k. You can try different targets and see what works in you room/system. |
|
|
|
Post by marcl on Feb 26, 2021 6:15:37 GMT -5
I noticed that the dirac result sounded bright/harsh at volume so I turned it off and it sounds much better, smoother. So far pretty underwhelmed with dirac, have measured before/after and it doesn't even hit the target curve. Yes I've spent hours, different mics, etc. It's weird because it actually manages to leave whatever response bumps are there and somehow manage to make it sound worse. The firmware note says 30 seconds for network reset, my experience says two power offs, maybe I should wait a while, or go get coffee, or a snack. The good news is when the processor works, it sounds good. I'll probably do a full reset and not bother with dirac and see how things are, next time I have time. This will sometimes happen right after calibration. Dirac should never sound harsh like that. It's a problem I have had many times, especially if Dirac crashes after the filter download. It seems to leave the processor in a strange state. Do a hard reboot of your processor. Any time you hear distortion or the overly bright/harsh sound and levels sound louder - especially the left/right channels - try a reboot and it should fix the problem. |
|
|
|
Post by rbk123 on Feb 26, 2021 9:19:34 GMT -5
I don’t know what seems to be so much different between the XMC-2 and my RMC-1L, but I haven’t experienced any of this “popping” behavior. It may be of interest, but I do not use Dirac. In fact, my Dirac kit is still in its shipping box. I don't get these with my XMC-2 and I also haven't set up Dirac yet, but I'm still on 2.1 (haven't had a chance to upgrade, hopefully this weekend). I used to get "chirps" and zaps within a movie, occasionally, with my MC-700, but that went away when I switched to premium cables. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,033
|
Post by cawgijoe on Feb 26, 2021 9:24:49 GMT -5
I don’t know what seems to be so much different between the XMC-2 and my RMC-1L, but I haven’t experienced any of this “popping” behavior. It may be of interest, but I do not use Dirac. In fact, my Dirac kit is still in its shipping box. I don't get these with my XMC-2 and I also haven't set up Dirac yet, but I'm still on 2.1 (haven't had a chance to upgrade, hopefully this weekend). I used to get "chirps" and zaps within a movie, occasionally, with my MC-700, but that went away when I switched to premium cables. As I said in an earlier post, I do use Dirac with my XMC-2 and I don't have this popping behavior. Not sure what might be causing this issue. |
|
|
|
Post by Goodfella on Feb 26, 2021 9:35:09 GMT -5
I don't get these with my XMC-2 and I also haven't set up Dirac yet, but I'm still on 2.1 (haven't had a chance to upgrade, hopefully this weekend). I used to get "chirps" and zaps within a movie, occasionally, with my MC-700, but that went away when I switched to premium cables. As I said in an earlier post, I do use Dirac with my XMC-2 and I don't have this popping behavior. Not sure what might be causing this issue. I had pops and click prior to using Dirac and after. The issue happens when switching from DTS to Atmos or the other way. It is far worse with Loudness enabled. I can try switching HDMI cables to see if that makes any difference but I had no issues with these cables with my old processor. |
|
|
|
Post by brewmaster on Feb 26, 2021 9:41:02 GMT -5
|
|
All good.
