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
MediaPortal 1 Talk
Hauppauge HD-PVR & Colossus Support
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="sjevtic" data-source="post: 968703" data-attributes="member: 118214"><p>Hi Pascal,</p><p></p><p> </p><p>I have never really looked into what those XML files are used for, but I do know that they are written out at least when you change particular card-related aspects of the TV Server configuration (e.g., recording quality preference). I never bothered to understand if they are used to influence the behavior of TV Server in any way, or if they are just intended to provide you with an easily readable summary of the capture configuration.</p><p></p><p>You can do this in the GUI. It's just slow work because you have to open a dialog for each channel, and then open a subsequent dialog for each tuning detail. I put a screenshot of the dialog where you can edit the video source and audio source for a particular tuning detail a <a href="https://forum.team-mediaportal.com/threads/hauppauge-hd-pvr-colossus-support.94850/page-92#post-967253" target="_blank">few posts up</a>.</p><p> </p><p>The name of the database table where this is kept is called TuningDetail. The fields in question are videoSource and audioSource. If you do directly modify the database though, be careful as you query, since you need to obviously set the values differently based on the card that a particular tuning detail is associated with (think: ChannelMap table).</p><p> </p><p>By the way, one thing I have found very useful for poking around inside the TV Server database is Microsoft Access, which can function as a reasonable client for just about any data source for which you have an ODBC driver. If you're like me and not a database professional, the query editing tools can be a big help. Running a query from sqlcmd might be convenient once you have perfectly formulated your query, but when you're trying to get a grasp on the database schema and understanding what your queries are doing, the GUI is particularly handy. Here's an example of what using Access to work on your database looks like:</p><p> </p><p>[ATTACH=full]122746[/ATTACH]</p><p> </p><p>Obviously, in addition to designing queries that update your data, you can do all the standard sorts of things you'd expect to be able to do--manually edit fields, use search and replace, etc.</p><p> </p><p>Sasha</p></blockquote><p></p>
[QUOTE="sjevtic, post: 968703, member: 118214"] Hi Pascal, I have never really looked into what those XML files are used for, but I do know that they are written out at least when you change particular card-related aspects of the TV Server configuration (e.g., recording quality preference). I never bothered to understand if they are used to influence the behavior of TV Server in any way, or if they are just intended to provide you with an easily readable summary of the capture configuration. You can do this in the GUI. It's just slow work because you have to open a dialog for each channel, and then open a subsequent dialog for each tuning detail. I put a screenshot of the dialog where you can edit the video source and audio source for a particular tuning detail a [URL='https://forum.team-mediaportal.com/threads/hauppauge-hd-pvr-colossus-support.94850/page-92#post-967253']few posts up[/URL]. The name of the database table where this is kept is called TuningDetail. The fields in question are videoSource and audioSource. If you do directly modify the database though, be careful as you query, since you need to obviously set the values differently based on the card that a particular tuning detail is associated with (think: ChannelMap table). By the way, one thing I have found very useful for poking around inside the TV Server database is Microsoft Access, which can function as a reasonable client for just about any data source for which you have an ODBC driver. If you're like me and not a database professional, the query editing tools can be a big help. Running a query from sqlcmd might be convenient once you have perfectly formulated your query, but when you're trying to get a grasp on the database schema and understanding what your queries are doing, the GUI is particularly handy. Here's an example of what using Access to work on your database looks like: [ATTACH=full]122746[/ATTACH] Obviously, in addition to designing queries that update your data, you can do all the standard sorts of things you'd expect to be able to do--manually edit fields, use search and replace, etc. Sasha [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Hauppauge HD-PVR & Colossus Support
Contact us
RSS
Top
Bottom
