|
Post by AudioHTIT on Jul 22, 2021 8:08:07 GMT -5
I’m thinking the 12 second POD is was causes it to look like it’s done, but it’s really still delaying in the background. I think the key is whether it changes inputs properly, which would happen after the POD. In my case it did not change the input to the one I chose in the activity. I will give it another try tonight though. What are you using for turn-on input? Mine is still set at Last Used from my ‘workaround’ solution. That could be the issue as Last Used avoids an extra input switch late in the process. I have been doing random tests of my test activities and they’ve mostly worked, I’m getting the correct input, and it’s not throwing the timeout error. However it hasn’t been perfect, and occasionally a test will fail to set the input correctly. (I’m trying to make sure I test an activity that wasn’t the last used input) Here’s a sample test activity, they’re pretty simple (the way they’re supposed to be)
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,181
Member is Online
|
Post by geebo on Jul 22, 2021 8:20:42 GMT -5
In my case it did not change the input to the one I chose in the activity. I will give it another try tonight though. What are you using for turn-on input? Mine is still set at Last Used from my ‘workaround’ solution. That could be the issue as Last Used avoids an extra input switch late in the process. I have been doing random tests of my test activities and they’ve mostly worked, I’m getting the correct input, and it’s not throwing the timeout error. However it hasn’t been perfect, and occasionally a test will fail to set the input correctly. (I’m trying to make sure I test an activity that wasn’t the last used input) Here’s a sample test activity, they’re pretty simple (the way they’re supposed to be) View AttachmentI got the timeout error once out of the two times I tried. I noticed you are using the phone app to do everything where I'm using Windows to go to the Harmony configuration website. I wonder if that might make a difference.
|
|
|
Post by AudioHTIT on Jul 22, 2021 8:34:39 GMT -5
Mine is still set at Last Used from my ‘workaround’ solution. That could be the issue as Last Used avoids an extra input switch late in the process. I have been doing random tests of my test activities and they’ve mostly worked, I’m getting the correct input, and it’s not throwing the timeout error. However it hasn’t been perfect, and occasionally a test will fail to set the input correctly. (I’m trying to make sure I test an activity that wasn’t the last used input) Here’s a sample test activity, they’re pretty simple (the way they’re supposed to be) View AttachmentI got the timeout error once out of the two times I tried. I noticed you are using the phone app to do everything where I'm using Windows to go to the Harmony configuration website. I wonder if that might make a difference. Hmmm, don’t know, maybe. I do just about all my configuration on the iPad, but use the Physical Remote, iPad, and iPhone for my actual remote and tests. I haven’t loaded the Windows or Mac versions for some time, I think they dropped Mac support when Apple went all 64 bit.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,181
Member is Online
|
Post by geebo on Jul 22, 2021 8:42:51 GMT -5
I got the timeout error once out of the two times I tried. I noticed you are using the phone app to do everything where I'm using Windows to go to the Harmony configuration website. I wonder if that might make a difference. Hmmm, don’t know, maybe. I do just about all my configuration on the iPad, but use the Physical Remote, iPad, and iPhone for my actual remote and tests.I haven’t loaded the Windows or Mac versions for some time, I think they dropped Mac support when Apple went all 64 bit. I know they are different in some ways. For example, I cannot configure my LIFX light or Z-Wave device in Windows and must use the phone app for that. I use the actual Harmony remote 99% of the time. I may have to try adding the device via the phone app just to see.
|
|
|
Post by rogerlons on Jul 22, 2021 9:16:43 GMT -5
That’s the same one LCSeminole posted a page back. I tried it a few years back and had trouble getting it to clear the hub, maybe the older hubs are slightly different, still have them, I’ll try again. I had trouble with these as well. It was not really possible to get two of these into the back of a hub. For me, the cables were a better option.
|
|
KeithL
Administrator
Posts: 9,929
Member is Online
|
Post by KeithL on Jul 22, 2021 9:55:38 GMT -5
I don't currently have a Harmony Remote...
But it's not at all unusual to be offered very different options, and depths of detail, with various different configuration apps. They're often written by entirely different programming groups - and one may be updated far more frequently than another. It used to be that the Windows app would offer more in-depth control than the phone app... but today the reverse may be true. (Each vendor seems to consider one or another to be the preferred method... )
Hmmm, don’t know, maybe. I do just about all my configuration on the iPad, but use the Physical Remote, iPad, and iPhone for my actual remote and tests.I haven’t loaded the Windows or Mac versions for some time, I think they dropped Mac support when Apple went all 64 bit. I know they are different in some ways. For example, I cannot configure my LIFX light or Z-Wave device in Windows and must use the phone app for that. I use the actual Harmony remote 99% of the time. I may have to try adding the device via the phone app just to see.
|
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,490
|
Post by LCSeminole on Jul 22, 2021 9:55:39 GMT -5
That’s the same one LCSeminole posted a page back. I tried it a few years back and had trouble getting it to clear the hub, maybe the older hubs are slightly different, still have them, I’ll try again. I had trouble with these as well. It was not really possible to get two of these into the back of a hub. For me, the cables were a better option. I was hesitant after I ordered these, but they have ended up much smaller than expected and have plenty of room for both ports to be used.
|
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,490
|
Post by LCSeminole on Jul 22, 2021 10:00:02 GMT -5
That’s what I’ve done so far, and what they asked me to do, just leave the defaults. Once we’ve determined how well it works or what problems still exist, then it probably wouldn’t hurt to play with it. The cosmetic issue I spoke of is that the remote ‘thinks’ the Activity has completed and returns control to the user while it’s still starting up. At this point any key you press may be ignored, or possibly queued for later, and you may keep pressing thinking it’s broken, but really it’s still starting up. I think adjusting the POD may fix this, but haven’t tried yet. Just downloaded the new RMC-1L device from Logitech. It has a default POD of 12 seconds but I tried a new activity anyway. It completed (or thought it did) way before the RMC completed booting. I then changed the POD to 60 (max) and basically get the same behavior that I get with the old RMC-1L device. So I tried downloading the device again with the same results. I'm curious if LCSeminole is seeing the same thing. Hopefully I’ll be able to get to this tonight. Work has been consuming but it looks promising today.
|
|
|
Post by AudioHTIT on Jul 22, 2021 12:51:04 GMT -5
Hmmm, don’t know, maybe. I do just about all my configuration on the iPad, but use the Physical Remote, iPad, and iPhone for my actual remote and tests.I haven’t loaded the Windows or Mac versions for some time, I think they dropped Mac support when Apple went all 64 bit. I know they are different in some ways. For example, I cannot configure my LIFX light or Z-Wave device in Windows and must use the phone app for that. I use the actual Harmony remote 99% of the time. I may have to try adding the device via the phone app just to see. Just downloaded the new RMC-1L device from Logitech. It has a default POD of 12 seconds but I tried a new activity anyway. It completed (or thought it did) way before the RMC completed booting. I then changed the POD to 60 (max) and basically get the same behavior that I get with the old RMC-1L device. So I tried downloading the device again with the same results. I'm curious if LCSeminole is seeing the same thing. Hopefully I’ll be able to get to this tonight. Work has been consuming but it looks promising today. Today, I’m having no luck with my test activities, I always end up on my “last used’ input, which is what you’d expect if it was sending the command too early. It’s possible I may have inadvertently (Purple Haze?) hit my workaround activities a couple times thinking I was testing. It’s also important that we clarify in our tests the following: Standby : LPS or VOSTurn-on Input: Last Used or SpecifiedState : From an Off Condition, or switching from Another ActivityTo report on this test you should have: Added a new / second processor Device specifying Emotiva RMC-1L, and built one or more ‘test’ Activities including the newly loaded Device. Use only the Activity Setup Wizard, specifying Input Selection as part of the process when you build your Activity — no modifications, pauses, or added steps. Do not modify the POD (Power On Delay). I personally see no value in testing a system using VOS, the test Device Driver is designed to help with the longer boot time of LPS systems, but there’s no reason it shouldn’t work with VOS as well (lengthy discussion here). Testing: Check for proper power up of devices needed for the activity. Check for proper input selection of each device. Check for normal operation, including the remote. All my tests have been LPS, Last Used, the tests I’ve previously reported on have been from an Off State. All my tests from an On State have been successful (as expected). As of today none my Test apps when started from an off condition are working. *Disclaimer: Yesterday I reset my RMC-1 to factory defaults and did not restore the backup, I re-entered all of my preferences, inputs and speaker settings (just about to do distance and levels). I don’t think this should affect the results, but it’s certainly possible.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,181
Member is Online
|
Post by geebo on Jul 22, 2021 14:47:44 GMT -5
I know they are different in some ways. For example, I cannot configure my LIFX light or Z-Wave device in Windows and must use the phone app for that. I use the actual Harmony remote 99% of the time. I may have to try adding the device via the phone app just to see. Hopefully I’ll be able to get to this tonight. Work has been consuming but it looks promising today. Today, I’m having no luck with my test activities, I always end up on my “last used’ input, which is what you’d expect if it was sending the command too early. It’s possible I may have inadvertently (Purple Haze?) hit my workaround activities a couple times thinking I was testing. It’s also important that we clarify in our tests the following: Standby : LPS or VOSTurn-on Input: Last Used or SpecifiedState : From an Off Condition, or switching from Another ActivityTo report on this test you should have: Added a new / second processor Device specifying Emotiva RMC-1L, and built one or more ‘test’ Activities including the newly loaded Device. Use only the Activity Setup Wizard, specifying Input Selection as part of the process when you build your Activity — no modifications, pauses, or added steps. Do not modify the POD (Power On Delay). I personally see no value in testing a system using VOS, the test Device Driver is designed to help with the longer boot time of LPS systems, but there’s no reason it shouldn’t work with VOS as well (lengthy discussion here). Testing: Check for proper power up of devices needed for the activity. Check for proper input selection of each device. Check for normal operation, including the remote. All my tests have been LPS, Last Used, the tests I’ve previously reported on have been from an Off State. All my tests from an On State have been successful (as expected). As of today none my Test apps when started from an off condition are working. *Disclaimer: Yesterday I reset my RMC-1 to factory defaults and did not restore the backup, I re-entered all of my preferences, inputs and speaker settings (just about to do distance and levels). I don’t think this should affect the results, but it’s certainly possible. I'll have to check my Turn-On input but I am otherwise testing with LPS and from an off condition.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,181
Member is Online
|
Post by geebo on Jul 22, 2021 19:56:21 GMT -5
I know they are different in some ways. For example, I cannot configure my LIFX light or Z-Wave device in Windows and must use the phone app for that. I use the actual Harmony remote 99% of the time. I may have to try adding the device via the phone app just to see. Hopefully I’ll be able to get to this tonight. Work has been consuming but it looks promising today. Today, I’m having no luck with my test activities, I always end up on my “last used’ input, which is what you’d expect if it was sending the command too early. It’s possible I may have inadvertently (Purple Haze?) hit my workaround activities a couple times thinking I was testing. It’s also important that we clarify in our tests the following: Standby : LPS or VOSTurn-on Input: Last Used or SpecifiedState : From an Off Condition, or switching from Another ActivityTo report on this test you should have: Added a new / second processor Device specifying Emotiva RMC-1L, and built one or more ‘test’ Activities including the newly loaded Device. Use only the Activity Setup Wizard, specifying Input Selection as part of the process when you build your Activity — no modifications, pauses, or added steps. Do not modify the POD (Power On Delay). I personally see no value in testing a system using VOS, the test Device Driver is designed to help with the longer boot time of LPS systems, but there’s no reason it shouldn’t work with VOS as well (lengthy discussion here). Testing: Check for proper power up of devices needed for the activity. Check for proper input selection of each device. Check for normal operation, including the remote. All my tests have been LPS, Last Used, the tests I’ve previously reported on have been from an Off State. All my tests from an On State have been successful (as expected). As of today none my Test apps when started from an off condition are working. *Disclaimer: Yesterday I reset my RMC-1 to factory defaults and did not restore the backup, I re-entered all of my preferences, inputs and speaker settings (just about to do distance and levels). I don’t think this should affect the results, but it’s certainly possible. My settings are: Standby : LPS Turn-On Input : Last Used State : From full off I just downloaded the RMC-1L on my iPad using the Harmony app and created an activity. The results are the same as when using Windows 10 to set things up. The resulting activity ended after about 15 or 20 seconds and did not setup the RMC-1 properly. The default POD in the new device is 12 seconds and I'd have to say that's what it used. The max is still at 60 as you mentioned earlier. I'm wondering if they actually changed the device in their database.
|
|
|
Post by AudioHTIT on Jul 22, 2021 22:14:45 GMT -5
My settings are: Standby : LPS Turn-On Input : Last Used State : From full off I just downloaded the RMC-1L on my iPad using the Harmony app and created an activity. The results are the same as when using Windows 10 to set things up. The resulting activity ended after about 15 or 20 seconds and did not setup the RMC-1 properly. The default POD in the new device is 12 seconds and I'd have to say that's what it used. The max is still at 60 as you mentioned earlier. I'm wondering if they actually changed the device in their database. I was thinking the same thing, I’m not sure why I was getting false positives before, but it acts just like a 12 second driver. I’m going to write them back with a fail. It’s possible 60 seconds is really 120 seconds, and I asked them if that was the case, but they said to use the defaults. Thanks for testing.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,181
Member is Online
|
Post by geebo on Jul 23, 2021 6:31:49 GMT -5
My settings are: Standby : LPS Turn-On Input : Last Used State : From full off I just downloaded the RMC-1L on my iPad using the Harmony app and created an activity. The results are the same as when using Windows 10 to set things up. The resulting activity ended after about 15 or 20 seconds and did not setup the RMC-1 properly. The default POD in the new device is 12 seconds and I'd have to say that's what it used. The max is still at 60 as you mentioned earlier. I'm wondering if they actually changed the device in their database. I was thinking the same thing, I’m not sure why I was getting false positives before, but it acts just like a 12 second driver. I’m going to write them back with a fail. It’s possible 60 seconds is really 120 seconds, and I asked them if that was the case, but they said to use the defaults. Thanks for testing. With the first try I did try taking POD out to 60 seconds but there was no improvement over the old driver. Let me know if there is anything else I can test.
|
|
|
Post by AudioHTIT on Jul 23, 2021 7:41:54 GMT -5
I was thinking the same thing, I’m not sure why I was getting false positives before, but it acts just like a 12 second driver. I’m going to write them back with a fail. It’s possible 60 seconds is really 120 seconds, and I asked them if that was the case, but they said to use the defaults. Thanks for testing. With the first try I did try taking POD out to 60 seconds but there was no improvement over the old driver. Let me know if there is anything else I can test. Thanks geebo, I’ll let you know what they say.
|
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,490
|
Post by LCSeminole on Jul 24, 2021 14:44:05 GMT -5
Sorry gentlemen, a family health situation on Thursday evening took precedence. It does however look like you two came to a conclusion that the new device hasn't changed. Hopefully Harmony responds with a fix.
|
|
|
Post by AudioHTIT on Jul 24, 2021 16:57:24 GMT -5
Sorry gentlemen, a family health situation on Thursday evening took precedence. It does however look like you two came to a conclusion that the new device hasn't changed. Hopefully Harmony responds with a fix. Yes, not worth your time, I’ve already written them that this test was a bust, stopped just short of complaining about wasting our time.
|
|
|
Post by AudioHTIT on Jul 29, 2021 9:51:51 GMT -5
Ok, testing round two. Logitech got back to me yesterday and said the Emotiva RMC-1L Device had again been updated with a 120 second POD. So if geebo, LCSeminole, or anyone else wants to test the latest it’s now available. I have done a brief test and it’s definitely different, but I was distracted and don’t have specific results; it did throw the time out error before it seemed to complete successfully. So to test, use the same procedure: * If you loaded the previous test Device from last week, delete it. * Add a new Emotiva RMC-1L Device * Create an Activity using the new Device (I re-setup my previous test activities) * Do not modify the Device POD setting (though we are now going to want to make it shorter) * Test and report back — as before, specify: LPS / VOS, Last Used / Specific HDMI Startup Input, Testing from power off condition or from a running activity. Again, if you use VOS you probably won’t want to use this test Device, and if you’re loading a Logitech G3P Device driver for the first time, I would recommend using the XMC-2 driver for the time being. This driver takes a little patience as I believe the 120 second delay is working (I’m hoping they’ll be able to give us 1 to 120).
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,181
Member is Online
|
Post by geebo on Jul 29, 2021 11:13:54 GMT -5
Ok, testing round two. Logitech got back to me yesterday and said the Emotiva RMC-1L Device had again been updated with a 120 second POD. So if geebo, LCSeminole, or anyone else wants to test the latest it’s now available. I have done a brief test and it’s definitely different, but I was distracted and don’t have specific results; it did throw the time out error before it seemed to complete successfully. So to test, use the same procedure: * If you loaded the previous test Device from last week, delete it. * Add a new Emotiva RMC-1L Device * Create an Activity using the new Device (I re-setup my previous test activities) * Do not modify the Device POD setting (though we are now going to want to make it shorter) * Test and report back — as before, specify: LPS / VOS, Last Used / Specific HDMI Startup Input, Testing from power off condition or from a running activity. Again, if you use VOS you probably won’t want to use this test Device, and if you’re loading a Logitech G3P Device driver for the first time, I would recommend using the XMC-2 driver for the time being. This driver takes a little patience as I believe the 120 second delay is working (I’m hoping they’ll be able to give us 1 to 120). I'll try to test it out tonight. I'll try the default but does the POD time now go out to 120 seconds or does it still read 60 as the max. I have occasionally gotten the time out error but the activity always fully completes.
|
|
|
Post by AudioHTIT on Jul 29, 2021 11:51:46 GMT -5
Ok, testing round two. Logitech got back to me yesterday and said the Emotiva RMC-1L Device had again been updated with a 120 second POD. So if geebo, LCSeminole, or anyone else wants to test the latest it’s now available. I have done a brief test and it’s definitely different, but I was distracted and don’t have specific results; it did throw the time out error before it seemed to complete successfully. So to test, use the same procedure: * If you loaded the previous test Device from last week, delete it. * Add a new Emotiva RMC-1L Device * Create an Activity using the new Device (I re-setup my previous test activities) * Do not modify the Device POD setting (though we are now going to want to make it shorter) * Test and report back — as before, specify: LPS / VOS, Last Used / Specific HDMI Startup Input, Testing from power off condition or from a running activity. Again, if you use VOS you probably won’t want to use this test Device, and if you’re loading a Logitech G3P Device driver for the first time, I would recommend using the XMC-2 driver for the time being. This driver takes a little patience as I believe the 120 second delay is working (I’m hoping they’ll be able to give us 1 to 120). I'll try to test it out tonight. I'll try the default but does the POD time now go out to 120 seconds or does it still read 60 as the max. I have occasionally gotten the time out error but the activity always fully completes. Thanks for asking, I forgot to check, it now reads up to 120 where it is set by default. So it looks like after testing the default, we can lower it to where it’s long enough to get the Input setting correct, but doesn’t make us wait any extra after that. With the original driver, I get the timeout error whenever I’m above 57.5 seconds, so that’s where my ‘workaround’ activities are st. I assume this is some kind of communication error, because as you say, it usually complete successfully even after throwing the error. When I report back on our POD results I’ll explore getting this fixed as 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,181
Member is Online
|
Post by geebo on Jul 29, 2021 12:27:33 GMT -5
I'll try to test it out tonight. I'll try the default but does the POD time now go out to 120 seconds or does it still read 60 as the max. I have occasionally gotten the time out error but the activity always fully completes. Thanks for asking, I forgot to check, it now reads up to 120 where it is set by default. So it looks like after testing the default, we can lower it to where it’s long enough to get the Input setting correct, but doesn’t make us wait any extra after that. With the original driver, I get the timeout error whenever I’m above 57.5 seconds, so that’s where my ‘workaround’ activities are st. I assume this is some kind of communication error, because as you say, it usually complete successfully even after throwing the error. When I report back on our POD results I’ll explore getting this fixed as well. View AttachmentI've had mine set to 60 seconds for a long time now and only get the time out error once in awhile. It'll be interesting to see if I get it with the 120 second default POD. Thanks for your work on this.
|
|