home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
External Receiver (Digital Cable Box)?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anonymous" data-source="post: 449"><p>I was able to obtain the full SDK for the USB-UIRT. It doesn't look too terrible, it's a Pascal exported C DLL with about 8 functions. IR codes are actually stored and played back as strings (char pointers). The DLL shouldn't be too terrible to wrap up in a managed wrapper. I even got the C# source from CVS and looked at where it could be implemented. </p><p></p><p>My suggestion would be to make an ITuner interface that has the same methods and properties as the Tuner class in the DirectX.Capture module. Then, TVCaptureDevice in the TVCapture namespace would hold a reference to the ITunder interface rather then the Tuner class. A plugin for any tuner would then simply implement the ITuner interface. The only trick would be changing the TVCaptureDevice class to obtain the plugin rather then the actual capture devices tuner (if that's what the user setup in the configuration screen).</p><p></p><p>Finally, the capture device configuration screen would have to allow the choice of a tuner plugin, and there would have to be a button to configure the plugin. In the case of the USB-UIRT, it would be a dialog that would let the plugin "Learn" from the users remote which buttons they wanted to use to perform which functions.</p><p></p><p>All in all, it's certainly doable. I could easily contribute some code for enumerating and loading plugins (I do this all day at work). I might even be able to port the USB-UIRT DLL into C# and make a nice wrapper around it. I could POSSIBLY even go so far as to make the configuration screen and the interface. But I'm not promising anything because I'm already working 10 hour days right now. The only part I would deffinately NOT want to do would be merging it all in (especially touching the TVCaptureDevice class). I see how it persists its configuration using automatic serialization and the class is a little hairy. I wouldn't want to get down and dirty in there.</p><p></p><p>If one of the devs would like to work with me on this, I can see if I can set some time aside. But no promises. Really, weekend time is about all I have and even that is limited right now. That may change in a few months...</p></blockquote><p></p>
[QUOTE="Anonymous, post: 449"] I was able to obtain the full SDK for the USB-UIRT. It doesn't look too terrible, it's a Pascal exported C DLL with about 8 functions. IR codes are actually stored and played back as strings (char pointers). The DLL shouldn't be too terrible to wrap up in a managed wrapper. I even got the C# source from CVS and looked at where it could be implemented. My suggestion would be to make an ITuner interface that has the same methods and properties as the Tuner class in the DirectX.Capture module. Then, TVCaptureDevice in the TVCapture namespace would hold a reference to the ITunder interface rather then the Tuner class. A plugin for any tuner would then simply implement the ITuner interface. The only trick would be changing the TVCaptureDevice class to obtain the plugin rather then the actual capture devices tuner (if that's what the user setup in the configuration screen). Finally, the capture device configuration screen would have to allow the choice of a tuner plugin, and there would have to be a button to configure the plugin. In the case of the USB-UIRT, it would be a dialog that would let the plugin "Learn" from the users remote which buttons they wanted to use to perform which functions. All in all, it's certainly doable. I could easily contribute some code for enumerating and loading plugins (I do this all day at work). I might even be able to port the USB-UIRT DLL into C# and make a nice wrapper around it. I could POSSIBLY even go so far as to make the configuration screen and the interface. But I'm not promising anything because I'm already working 10 hour days right now. The only part I would deffinately NOT want to do would be merging it all in (especially touching the TVCaptureDevice class). I see how it persists its configuration using automatic serialization and the class is a little hairy. I wouldn't want to get down and dirty in there. If one of the devs would like to work with me on this, I can see if I can set some time aside. But no promises. Really, weekend time is about all I have and even that is limited right now. That may change in a few months... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
External Receiver (Digital Cable Box)?
Contact us
RSS
Top
Bottom