|
Post by marcl on Aug 18, 2020 11:55:28 GMT -5
The idea of a bug tracking tool for customers to report tools and also for Emotiva to transparently communicate what they are working on has come up several times in the last years. During the XMC-1 HDMI board V3 beta I also formulated a simple checklist / guideline as a help for filling out good bug reports. No interest in continuing this apparently. I guess they just don´t have a responsible head of QM with enough weight in their organisational structure. Otherwise there should have been some noteable process improvements in the last years. In my experience every engineering organization has a tracking tool. It may be defects only, or may combine defects, enhancements and the more generic "issues". It often is connected to their code configuration management process that links issues to the specific code that fixes them, and the release in which they are to be included. As for how the customer side connects to this, there's no way customers would ever see the internal engineering list. Unlikely even to let us see a report from the tool. More likely, there's another tracking system for customer reported issues and requests that is managed by Customer Support and/or a Marketing function. It makes sense to have two systems because very often there is not 1:1 correlation. A single customer issue may break out into two or more development issues that may be fixed at different times. And of course you will have the same issue reported by many customers and they need to be triaged and combined or split, etc. All this typically happens in a meeting of Quality Assurance, Customer Support and Development. There may be fields in each system to trace issue numbers between them, but often not a physical connection ... usually a manual process. How Emotiva does it, I have no idea of course. But if they haven't dealt with all the scenarios I mentioned so far, they certainly would if they went down the road of a customer reporting tool. Let's give them the benefit of the doubt ... they have a process, and they really have no obligation to let us see it.
|
|
|
Post by vmbray on Aug 18, 2020 13:17:09 GMT -5
I’m having an issue on my xmc2 (2.0 fw) where it doesn’t sync hdmi with the display when powered on. Sources are TiVo mini and oppo 203. For example if it’s turned on and source is set to TiVo, I’ll get audio but no picture and the display says no signal. Changing the input to the oppo, letting it sync, and changing it back resolves it. Have swapped cables, etc exhaustively and it’s pretty consistent. Once in a while it works but usually have to change sources and back. I can macro that in my remote but it’s slow and seems like there might be a better solution. Saw some older posts about using dr hdmi etc but would rather not if I don’t have to.
|
|
|
Post by doc1963 on Aug 18, 2020 13:27:51 GMT -5
I’m having an issue on my xmc2 (2.0 fw) where it doesn’t sync hdmi with the display when powered on. Sources are TiVo mini and oppo 203. For example if it’s turned on and source is set to TiVo, I’ll get audio but no picture and the display says no signal. Changing the input to the oppo, letting it sync, and changing it back resolves it. Have swapped cables, etc exhaustively and it’s pretty consistent. Once in a while it works but usually have to change sources and back. I can macro that in my remote but it’s slow and seems like there might be a better solution. Saw some older posts about using dr hdmi etc but would rather not if I don’t have to. Which TiVo Mini are you using...? If an older, non-4K supporting model, have you set the HDMI version of the input you're using for your TiVo on your XMC-2 to "HDMI > 1.4"...?
|
|
|
Post by monkumonku on Aug 18, 2020 13:35:43 GMT -5
I have an odd issue and I wonder if anyone else has experienced this.
When I change the volume on the XMC-2, the OSD and the XMC-2 display both show the change. But when the OSD goes off, the display on the XMC-2 still shows the old volume. If I press the volume key then it shows the correct volume after the change, but otherwise it doesn't register on the XMC-2 display once the OSD disappears. Not a big deal since I know the volume has changed, but I find it odd. This happened with firmware 1.1 and also happens under 2.0.
|
|
|
Post by SticknStones on Aug 18, 2020 13:36:53 GMT -5
The idea of a bug tracking tool for customers to report tools and also for Emotiva to transparently communicate what they are working on has come up several times in the last years. During the XMC-1 HDMI board V3 beta I also formulated a simple checklist / guideline as a help for filling out good bug reports. No interest in continuing this apparently. I guess they just don´t have a responsible head of QM with enough weight in their organisational structure. Otherwise there should have been some noteable process improvements in the last years. In my experience every engineering organization has a tracking tool. It may be defects only, or may combine defects, enhancements and the more generic "issues". It often is connected to their code configuration management process that links issues to the specific code that fixes them, and the release in which they are to be included. As for how the customer side connects to this, there's no way customers would ever see the internal engineering list. Unlikely even to let us see a report from the tool. More likely, there's another tracking system for customer reported issues and requests that is managed by Customer Support and/or a Marketing function. It makes sense to have two systems because very often there is not 1:1 correlation. A single customer issue may break out into two or more development issues that may be fixed at different times. And of course you will have the same issue reported by many customers and they need to be triaged and combined or split, etc. All this typically happens in a meeting of Quality Assurance, Customer Support and Development. There may be fields in each system to trace issue numbers between them, but often not a physical connection ... usually a manual process. How Emotiva does it, I have no idea of course. But if they haven't dealt with all the scenarios I mentioned so far, they certainly would if they went down the road of a customer reporting tool. Let's give them the benefit of the doubt ... they have a process, and they really have no obligation to let us see it. I created a UMC Tracker tool that had a form with dropdown and firmware version and then a Spreadsheet that logged all the forms in it. I had spoken with Lonnie and they had a very robust bug tracking software (Bugzilla) that they used and this was in 2010. Tracker Tool Thread Link
|
|
|
Post by marcl on Aug 18, 2020 13:44:41 GMT -5
In my experience every engineering organization has a tracking tool. It may be defects only, or may combine defects, enhancements and the more generic "issues". It often is connected to their code configuration management process that links issues to the specific code that fixes them, and the release in which they are to be included. As for how the customer side connects to this, there's no way customers would ever see the internal engineering list. Unlikely even to let us see a report from the tool. More likely, there's another tracking system for customer reported issues and requests that is managed by Customer Support and/or a Marketing function. It makes sense to have two systems because very often there is not 1:1 correlation. A single customer issue may break out into two or more development issues that may be fixed at different times. And of course you will have the same issue reported by many customers and they need to be triaged and combined or split, etc. All this typically happens in a meeting of Quality Assurance, Customer Support and Development. There may be fields in each system to trace issue numbers between them, but often not a physical connection ... usually a manual process. How Emotiva does it, I have no idea of course. But if they haven't dealt with all the scenarios I mentioned so far, they certainly would if they went down the road of a customer reporting tool. Let's give them the benefit of the doubt ... they have a process, and they really have no obligation to let us see it. I created a UMC Tracker tool that had a form with dropdown and firmware version and then a Spreadsheet that logged all the forms in it. I had spoken with Lonnie and they had a very robust bug tracking software (Bugzilla) that they used and this was in 2010. Tracker Tool Thread LinkSure ... Bugzilla, Jira, TFS, etc. Main thing is a good process.
|
|
|
Post by vmbray on Aug 18, 2020 13:46:50 GMT -5
It’s a TiVo mini 4K. I also did try setting the 1.4 hdmi version. I have the main TiVo bolt 4K on an atlona 1080p matrix and prior to the mini I was hooked to the matrix and had same issue, and figured it was the matrix (although it works perfectly with denon and with plain TVs) and had tried setting 1.4 because of the fhd matrix but that didn’t help. That’s when I put the TiVo mini there to eliminate the matrix as part of the issue.
|
|
|
Post by doc1963 on Aug 18, 2020 13:57:51 GMT -5
It’s a TiVo mini 4K. I also did try setting the 1.4 hdmi version. I have the main TiVo bolt 4K on an atlona 1080p matrix and prior to the mini I was hooked to the matrix and had same issue, and figured it was the matrix (although it works perfectly with denon and with plain TVs) and had tried setting 1.4 because of the fhd matrix but that didn’t help. That’s when I put the TiVo mini there to eliminate the matrix as part of the issue. Okay... what do you use your Mini for...? Just TV or do you also use it to stream (Netflix, Amazon Prime, Hulu, etc...)...? If you stream, do you stream 4K UHD content, or just HD...? What I'm getting to is this... what is the video output resolution setting in your TiVo Mini currently set to...? FWIW, I also have the 4K Mini VOX. But since I don't use it as a streaming device (TV only), I have it hard-set to output 1080p/60 video with DD audio. Using these settings, I don't have any problems with it.
|
|
|
Post by ttocs on Aug 18, 2020 14:17:12 GMT -5
I have an odd issue and I wonder if anyone else has experienced this. When I change the volume on the XMC-2, the OSD and the XMC-2 display both show the change. But when the OSD goes off, the display on the XMC-2 still shows the old volume. If I press the volume key then it shows the correct volume after the change, but otherwise it doesn't register on the XMC-2 display once the OSD disappears. Not a big deal since I know the volume has changed, but I find it odd. This happened with firmware 1.1 and also happens under 2.0. Someone else had the same thing happen with volume on the display not matching the OSD, I think it was last week. Hasn't happened to me, but other weird things happened to me with the front panel display with various FW versions. I reported when these things happened, but like I say, it's FW dependent.
|
|
|
Post by monkumonku on Aug 18, 2020 14:25:20 GMT -5
I have an odd issue and I wonder if anyone else has experienced this. When I change the volume on the XMC-2, the OSD and the XMC-2 display both show the change. But when the OSD goes off, the display on the XMC-2 still shows the old volume. If I press the volume key then it shows the correct volume after the change, but otherwise it doesn't register on the XMC-2 display once the OSD disappears. Not a big deal since I know the volume has changed, but I find it odd. This happened with firmware 1.1 and also happens under 2.0. Someone else had the same thing happen with volume on the display not matching the OSD, I think it was last week. Hasn't happened to me, but other weird things happened to me with the front panel display with various FW versions. I reported when these things happened, but like I say, it's FW dependent. Thanks. In my case, the OSD and display match when changing the volume but once the OSD goes off, then the XMC-2 display shows the previous volume. A click of the volume key corrects it. Now, I have the default display set to show just the volume and not any other info so I don't know if that has something to do with that particular screen.
|
|
|
Post by ttocs on Aug 18, 2020 14:52:55 GMT -5
Someone else had the same thing happen with volume on the display not matching the OSD, I think it was last week. Hasn't happened to me, but other weird things happened to me with the front panel display with various FW versions. I reported when these things happened, but like I say, it's FW dependent. Thanks. In my case, the OSD and display match when changing the volume but once the OSD goes off, then the XMC-2 display shows the previous volume. A click of the volume key corrects it. Now, I have the default display set to show just the volume and not any other info so I don't know if that has something to do with that particular screen. Ok, now I get it! Yes, it's when it's set to show only Volume. Seems to be what I like to call "sticky". Where a setting doesn't want to "let go" of a previous setting until kicked.
|
|
|
Post by monkumonku on Aug 18, 2020 14:57:14 GMT -5
Thanks. In my case, the OSD and display match when changing the volume but once the OSD goes off, then the XMC-2 display shows the previous volume. A click of the volume key corrects it. Now, I have the default display set to show just the volume and not any other info so I don't know if that has something to do with that particular screen. Ok, now I get it! Yes, it's when it's set to show only Volume. Seems to be what I like to call "sticky". Where a setting doesn't want to "let go" of a previous setting until kicked. So that's it.. I'm too lazy to change the default display to the info screen to see what happens so I'll take your word for it. It's just behaving like people do, then.
|
|
|
Post by marcl on Aug 18, 2020 15:05:53 GMT -5
Thanks. In my case, the OSD and display match when changing the volume but once the OSD goes off, then the XMC-2 display shows the previous volume. A click of the volume key corrects it. Now, I have the default display set to show just the volume and not any other info so I don't know if that has something to do with that particular screen. Ok, now I get it! Yes, it's when it's set to show only Volume. Seems to be what I like to call "sticky". Where a setting doesn't want to "let go" of a previous setting until kicked. Here's another quirk .... After doing a Dirac calibration and disabling Dirac in the menu, when it returns to the main screen the Volume is set to -32 ... AND A HALF! Yep ... -32.5 ... and then as I adjust the Volume from then on, I can only get .5 ... no .0. Have to cycle to standby and back to clear it.
|
|
|
Post by ttocs on Aug 18, 2020 15:14:52 GMT -5
Ok, now I get it! Yes, it's when it's set to show only Volume. Seems to be what I like to call "sticky". Where a setting doesn't want to "let go" of a previous setting until kicked. Here's another quirk .... After doing a Dirac calibration and disabling Dirac in the menu, when it returns to the main screen the Volume is set to -32 ... AND A HALF! Yep ... -32.5 ... and then as I adjust the Volume from then on, I can only get .5 ... no .0. Have to cycle to standby and back to clear it. Yep, same here. Although I did not pay attention to this to verify this happened when I did the last Dirac run a couple days ago. I think they should delete the .0 altogether. Half steps, don't want it, don't need it.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,211
|
Post by geebo on Aug 18, 2020 15:21:28 GMT -5
Ok, now I get it! Yes, it's when it's set to show only Volume. Seems to be what I like to call "sticky". Where a setting doesn't want to "let go" of a previous setting until kicked. Here's another quirk .... After doing a Dirac calibration and disabling Dirac in the menu, when it returns to the main screen the Volume is set to -32 ... AND A HALF! Yep ... -32.5 ... and then as I adjust the Volume from then on, I can only get .5 ... no .0. Have to cycle to standby and back to clear it. You can simply run the volume all the way down then back up to clear it.
|
|
|
Post by vmbray on Aug 18, 2020 21:08:27 GMT -5
Thanks that is helpful. I put the mini there to troubleshoot so I went back to the matrix/bolt and set the bolt to 1080, and also set the oppo to 1080. The projector is 1080 so there’s nothing lost doing that. I’ll try it, the one thing is that the oppo had same behavior if it was the first source when powering on. There are two displays, a 4K tv and the Sony hw45. Was testing just using the tv because both displays have done same but I’ll leave things all set for 1080 and see. Both inputs on xmc2 are set for 1.4
|
|
|
Post by bblv on Aug 18, 2020 23:29:21 GMT -5
Here's another quirk .... After doing a Dirac calibration and disabling Dirac in the menu, when it returns to the main screen the Volume is set to -32 ... AND A HALF! Yep ... -32.5 ... and then as I adjust the Volume from then on, I can only get .5 ... no .0. Have to cycle to standby and back to clear it. You can simply run the volume all the way down then back up to clear it. Simply? 😂 How is this type of thing still happening and when is the next firmware fix coming?
|
|
|
Post by marcl on Aug 19, 2020 5:44:16 GMT -5
Here's another quirk .... After doing a Dirac calibration and disabling Dirac in the menu, when it returns to the main screen the Volume is set to -32 ... AND A HALF! Yep ... -32.5 ... and then as I adjust the Volume from then on, I can only get .5 ... no .0. Have to cycle to standby and back to clear it. You can simply run the volume all the way down then back up to clear it. I tried running the volume all the way up and back down, but that didn't work out so well ;-)
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,211
|
Post by geebo on Aug 19, 2020 6:23:56 GMT -5
You can simply run the volume all the way down then back up to clear it. Simply? 😂 How is this type of thing still happening and when is the next firmware fix coming? Well, for me it's pretty simple. I just hold the remote volume button down for a few seconds then adjust back up to taste.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,211
|
Post by geebo on Aug 19, 2020 6:26:09 GMT -5
You can simply run the volume all the way down then back up to clear it. I tried running the volume all the way up and back down, but that didn't work out so well ;-) Whenever it's happened to me I've run the volume all the way down to zero and it's worked. Did not have to go all the way up. Just to zero and back up to where I wanted it. I heard it from another member so I know it doesn't just work for me.
|
|