Oppo Heads Up
vining
X Member
A few month back I updated the fw on an Oppo BDP-103 and I recently received the word that forward and rewind no longer work. In Oppos Proto v1.1 you just had to send "'#REV',$0D" or "'#FWD',$0D" but now in Proto v1.2.2 you have to send a speed parameter as well.
so now it need to be:
"'#REV 1/16',$0D" or "'#FWD 3',$0D"
it also means that in order to sequence through the speeds you have to track and store your current speed so for a quick fix I just did:
REV 1/16 1/8 1/4 1/2 1 2 3 4 5 Set Fast Reverse Play speed. FWD 1/16 1/8 1/4 1/2 1 2 3 4 5 Set Fast Forward Play speed.
so now it need to be:
"'#REV 1/16',$0D" or "'#FWD 3',$0D"
it also means that in order to sequence through the speeds you have to track and store your current speed so for a quick fix I just did:
(* FYI, speed is received and the tracking var set in the RX parsing not here *)
if(sOppo.sFB[DVD_FB_PLYBAK_STAT].nValue != PLYBAK_STAT_FFWD)
{
sOppo.cREWFWD_Spd = '';
}
SWITCH(sOppo.cREWFWD_Spd)
{
CASE'1/16': {cSpd = '1/8';}
CASE'1/8': {cSpd = '1/4';}
CASE'1/4': {cSpd = '1/2';}
CASE'1/2': {cSpd = '1';}
CASE'1': {cSpd = '2';}
CASE'2': {cSpd = '3';}
CASE'3': {cSpd = '4';}
CASE'4': {cSpd = '5';}
CASE'5': {cSpd = '1/16';}
DEFAULT: {cSpd = '1/16';}
}
fnDEV_Q_Cmd(TX_CMD_ARRY[TX_CMD_INDX_FWD],cSpd);
same thing for reverse.
I used a common var for both fwd and rev that resets on any other transport press. It would had been nice if Oppo kept the old method still valid so if no spd parameter is sent, don't throw an error but sequence through the speeds as it did before. Doesn't make sense to make us track this, should just be a simple toggle sequence the way it was.Comments
-
That is just silly
-
Yeah, breaking $hit for no good reason is just wrong. Don't have a clue what they were thinking. Of course they'll probably realize it was a mistake and change it back.
-
Well that was irresponsible. I'm trying to think of a use case to even need a "direct speed access". It's not like I would ever put all the speeds as buttons on a touchpanel. When would toggling through never be enough? Unless you just always wanted a certain speed. Hell, for commercial I'll probably just choose 3 and use that. Really hope the calls don't start coming in but our stuff is rarely updated by the user so I doubt it.
-
Having written plenty of parsers on the AMX end of things, I'd have to say it's just lazy not to allow the command without any parameter to work at some default behavior so that existing implementations do not break.
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums