Premise Tivo - AB and MB

  • Thread starter Thread starter chucklyons
  • Start date Start date
Motorola Premise
C

chucklyons

Guest
Thanks to ETC and 123, I am ready to release v1 of the Tivo Module. Serial controlled; javascript keypad ripped off from ETC's security module, it offers all (most) that the iPhone & iPad offer. 100% positive response, includes some backdoor commands (for skipping thru the menu commands)...this version is one-way only, meaning it's 'fire and forget', no feedback from the Tivo unit.

Tested w/ WP7, Android-based 3i and 10i devices. Chrome, FF, and IE.

Now the scary part. Anybody willing to try it and give me some feedback?
 

Attachments

  • ABTivo.gif
    ABTivo.gif
    19.3 KB · Views: 16
  • MBTivo.gif
    MBTivo.gif
    17.3 KB · Views: 15
How does the stock AB keypad handle digital cable channels that have sub-channels (10-1, 10-2 etc...) as I don't see a dash or dot button? The reason I'm asking is I'm working on a Panasonic TV driver and I'm debating on whether to write my own AB keypad...
 
I don't have sub-channels, so I didn't include it into the Tivo module.However, it is doc'd in the Tivo protocol...

Good question! Maybe - Television Tuner->Channel (Plugins->Controls-Misc Controls->ChannelSelector). Create a dupe, use sub-channel as the target property? At first glance, you'd probably have to tweak it a bit, otherwise you'd have to enter the channel, then do the same process using the subchannel selector. I didn't try the Receiver frequency controls, but that may be easier to modify?
 
Thanks Chuck. I figured I might be missing something so I thought I'd ask. Unfortunetaly, I don't own a Tivo, but your module looks very nice!

This may/may not be applicable to a Tivo, but for the newer TVs, they have "internal" sources such as HDTV tuners, SD card readers, browsers, netflix etc...

What I'm doing in my Panasonic ST50 module is modeling these internal sources as sys://Schema/Device/AudioVideoStream objects. This is because sys://Schema/Device/AudioVideoInput inherits from MediaInput and AudioVideoStream; since there's no MediaInput (e.g. a physical input connection), it makes no sense to use the AudioVideoInput object. Luckily, I've found discrete commands to point to all of these internal sources for my TV :)

To do this is kind of complicated, since the new input objects are not created by scripts directly in my case, but are hard coded in the XML of the xdo files. It turns out some other things are handled like this such as aspect ratios. This is why a TV object only has four inputs when you use the wizard. If you export a TV module, you can easily add more AudioVideoInput objects, just be sure NOT to use duplicate GUIDs! I'll post the module once it's finished so it can serve as an example...
 

Similar threads

C
Replies
2
Views
949
Back
Top