Disklavier

Glenn,


Any new information with your Mark IV volume problem? Hopefully, Kevin's suggestions have solved your issue. I remember someone else reporting this problem 6 or 7 years ago. If I remember correctly, the customer had made a volume change using the iOS app and the PRC100 could not override the volume setting. I had the customer check his iOS device and make the volume change from it.


Are your OMNI Outputs currently being used? One option would be to use those outputs instead of the OUTPUTS connected to your Mark IV speakers. 


Bill



-----Original Message-----
From: Glenn Smutny G.SMUTNY@... [disklavier] <disklavier@yahoogroups.com>
To: disklavier <disklavier@yahoogroups.com>
Sent: Fri, Oct 28, 2016 9:25 am
Subject: Re: [disklavier] Mark IV reset



  
    
                  
Thank you. I will try this this evening. 


Glenn Smutny
G.SMUTNY@...







On Oct 28, 2016, at 11:04 AM, Kevin Goroway kgoroway@... [disklavier] <disklavier@yahoogroups.com> wrote:







Sorry for the double post...I said I was late to t he thread...and I was...I hadn't read this far back.


This is interesting...I've never heard of such a problem, or that the protocol had changed to make this less likely (I certainly never noticed a protocol change at all...).


The fact is that the protocol is exceedingly poorly designed, and the fact that it works as well as it does is mostly though the magic of software.  Both the PRC, and TRC (and DKVBrowser, and any other participant) needs to be keenly aware that there are others involved.  A better protocol could have avoided a whole lot of the problems that this causes...but I suspect that the tablet and handheld teams over in Japan were in some sort of competition to see whose controller would ship with the piano, and didn't concern themselves with the fact that both might end up being avai lable.  Anyway, I'm guessing, and this is all speculation.  Back to the point.


The way the protocol works is a client says to the piano, for example:
"Hey, make the volume 50."  (this is point to point, no other clients hear it)


The piano responds with:
"Hey, everyone, the volume is now 50." &n bsp;(this is *also* point to point, but the piano says it individually to every client who has connected)


There isn't much more to it.  Except, now software is involved...and, imagine, if you would, a piece of software that says, "Huh, that's odd, my user says the volume should be 75, not 50, so I'm going to tell the piano to make it 75."


And, now things appear broken. It feels like you have no control over the volume.


But, here's what I am getting at... software could be causing this issue.  Shut dow n everything.  Every piece of software that you have that connects to the piano.  Shut it down.  iOS/Android/Windows/PRC/TRC.  Make sure you get 'em all.


Reboot the piano.


Run DKVBrowser (or the PRC or TRC) and have a look at what the piano is announcing as the volume.  If it is 80, change it to 60.  And wait 5 seconds.  If it sticks, no one is arguing with you about the volume.  If the volume isn't appropriate for the level chosen, I would investigate other things as I mentioned in my prior post.


-Kevin





From: "Bill Brandom billbrando@... [disklavier]" <disklavier@yahoogroups.com>
To: disklavier@yahoogroups.com 
Sent: Thursday, October 27, 2016 11:32 PM
Subject: Re: [disklavier] Mark IV reset



 


Ken,


I agree with you. I kind of remember hearing of this problem and it had something to do with volume setting in the Disklavier iOS app. 


Bill

Love God. Love People. Make a difference.




On Oct 27, 2016, at 7:58 PM, ken@... [disklavier] <disklavier@yahoogroups.com> wrote:


 
I've seen this problem, too! I first noticed it when using the IOS remote. I'm wondering if it's being caused when you have more than one remote communicating with to your piano and a volume change on one remote does not successfully receive and execute notification of the change - creating an out of sync issue . And then the volume is adjusted it again on the other remote. 


I remember something about the  software protocol was changed to optimize this communication protocol without the doublecheck and verifying all remotes were in sync before the I/O center made the change.  


Does this ring a bell with anyone?