Jump to content
c4forums | The Control4 Community


c4Forums Member
  • Posts

  • Joined

  • Last visited

  • Days Won


jrdiandrea last won the day on May 29

jrdiandrea had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jrdiandrea's Achievements

  1. jrdiandrea

    Speed is life

    It' been a very long time but I am really glad to read your report. And thank you for taking time to communicate this info. Just last night i was wondering if it was even on anyone's radar. It may not seem like an issue to most but I only use my ios devices...mostly my iPhone but sometimes my ipad, and not the c4 hard remotes (though I do have a c4 wand). It gets very tedious to wait till it connects...usually around 3 seconds. I know it doesn't sound long but when you need to stop something in a hurry...or you need to adjust whatever multiple times in a vey short period, it gets frustrating. The slider & up/down buttons were just fixed yesterday and that was a welcome surprise! I know the c4 structure is much more complex than most realize and, as you described, actually takes the cooperation of many people and groups. And each groups project is the most important! Anyway...just wanted to comment and thank you for the update and to say how much I am looking forward to the improvement! Good luck to all of you.
  2. Not a beta tester. But I did get a c4 app update that rolled out this morning. With this update both the slider and buttons and the position on the processor are all working and syncing as they should. The slider and buttons are working together now and I see no anomalies. I only spent about 5 minutes testing it but looked good to me. I did not test the mute button.,....
  3. The behavior is still erratic and not working as it should.. However, the slider, when I use that exclusively, longer jumps around. However, I cannot use both the slider or the up/down buttons. I can only use one or the other. Some times the up/down buttons work adjusting the volume. Some times it doesn't. The slider always works. However, if I attenuate the the volume with the slider, then if I adjust it with the up/down buttons by say 4-5 steps, the adjustment is made on the receiver but the slider number value on the app does not change. Then, if i move the slider just one step in either direction the reciver will spring back several steps to whatever the slider was. EXAMPLE: If I set the slider to 50. Then using the up/down buttons lower it to 45, then move the slider down just one step the receiver will jump up to 49. I'm using the most recent app version on my ios 12 Pro.
  4. I just received an update to the iOS app and very quickly tested it. I am experiencing the same issues…. Changes made with up/down are not reflected in the Slider volume.
  5. Additionally, I have noticed another anomaly that appears to be miner at this point. When I first power my system up and adjust the volume up several steps about a second or two later it will jump up one step. It has done this quite a bit. Just about every time I ve powered my system up. It will do it several times in a row and then stop. After the first couple times it seems to become random. It’s even occurred when adjusting the volume down. Ive not been able to operate my music or audio system since the app update earlier this week but will tonight. So my observations have been based a several brief tests of the app for a few minutes at a time. Don’t know if anyone else has noticed this or not..
  6. My up/down buttons do not work either. Only the slider.
  7. I just received an app update on both my iphone and ipad. Unfortunately this did not fix the problem in either device. This is becoming quite irritating. Not only is it Inconvenient but it can be important to know the actual volume setting on my processor.
  8. Yea...this is definitely a new problem. I can't think of any other reason than a bug in the app but I have no idea. This is a new problem for me and is a pain. I now do not know what the actual volume level is. It does finally correct itself but I have no idea how long it takes. Last night I watched a two hour film and near the end of the movie I did notice that the app displayed the correct percentage. I should look more closely next movie but who wants to be distracted from a good moving to watch this?! How can we get c4 to look at this and get a response from them?
  9. After rebooting the Datasat it continues with the odd behavior. When I turn up the volume on the Datasat via c4 the Datasat respinds appropriately to the correct db. The audio output level and the db reading on the Datasat remains stable. It is only the c4 level reading that snaps back to the previous output reading but the drop does not impact the Datasat. Only when i increase or decrease the c4 setting, even by just one point, the output level on the Datasat will immediately drop back to the output level where the c4 dropped back to. Therefore my assumption is that it’s c4 causing the issue and not the Datasat. But I could easily be wrong!
  10. I just completed the movie i was watching and powered down the Datasat and unplugged it. It has rebooted. I’ll be running it again later this evening and will report back. thx!
  11. Ugh. Didn’t think far enough…. It’s probably the Datasat, huh?
  12. Thx for replying. My processor is a Datasat. That’s the device I’m controlling. I’m watching a movie using an Oppo 203.
  13. I’m using the most recent ios app on an iphone Pro 12. C4 is v 3.2.1. Erratic behavior just started today I’ve not noticed it ever before Ex: the volume slider will read 40 on the app. I slide the volume up to 53 or tap it up in increments. Within 1-2 seconds later the slider snaps right back to 40 BUT the audible volume level stays at the new setting of 53. Then, the second i again move the slider up one notch or more, to something like 58, the audible volume instantly lowers back to 40. Then responding slowly To the increase, the audible volume level will go back up to the new setting of 58 within seconds but the slider will snap back to read 40. Then 10-20 minutes or more volume level reading may be correct. I have no clue why this would happen. I unplugged and rebooted both the c4 controller and repeater. I also rebooted the whole system with no improvement. Has anyone ever seen this behavior before?
  • Create New...