Reply to thread

Message

Sorry for what might be a stupid question: what exactly do you mean when you say "it"?

The more specific you are, the more able I am to help. Screenshots, log files, videos... all helpful.
Always keep in mind that I've never seen or used TV4Home, and I can only work with what you tell/give me.

I have to assume that when you say "tuners tab" you're talking about MediaPortal TV Server Configuration's tuner list. If my assumption is correct, I've already explained why this is the case: the version of MediaPortal's TV Server that ships with TV4Home doesn't support CableCARD tuners like your HDHR PRIME. I'd like to point out that this particular issue is nothing to do with the "guts" of whatever TV4Home actually is, and it has everything to do with the version of MediaPortal TV Server.

Again, I'm assuming when you say "channels tab" you actually mean MediaPortal TV Server Configuration's "TV Channels" section.

You're going to have to be more specific if you want me to actually help you with this.
For a start, what does the error say!

This makes absolutely no sense to me! WebEPG has nothing to do with MPExtended, and as far as I know neither WebEPG nor MPExtended are directly related to TV4Home. Therefore I'm not even going to attempt to address this.

If you mean MediaPortal TV Server's database structure when you say "database APIs" then I absolutely agree.

Okay, now I think I understand why you're wanting to try MS SQL... and if I've understood correctly, I can tell you that any such attempt will be absolutely pointless. To understand why it would be pointless, you have to understand the difference between the database engine and the database structure.

MySQL 5.1, MySQL 5.6 and MS SQL are database engines. The API for the database engines has not changed. Any given version of MediaPortal's TV Server - including the ancient version installed by TV4Home - and/or TV4Home itself can use any of the aforementioned database engines.

The thing that could break compatibility between TV4Home and MediaPortal's TV Server is a change to the database structure. By structure I mean [for example] a change to the data that is stored (eg. a new tuner property, or a new type of channel, or a new type of schedule etc.). The database structure has changed several times between the version of MediaPortal's TV Server installed by TV4Home and the newest version.

As explained above: I think trying the MS SQL database is pointless.

With the greatest respect, I'm also starting to wonder: do you understand the difference between MediaPortal TV Server Configuration and TV4Home?
I'm wondering this because the two specific issues you've mentioned so far - HDHR tuners not showing with the TV4Home version of MediaPortal's TV Server, and the "channel tab" error - have nothing to do with TV4Home (!).

Maybe it would be more beneficial for you to simply install the latest version of MediaPortal before installing TV4Home so you can see what is provided by MediaPortal. You may find that what you thought was provided by TV4Home is actually a default part of MediaPortal's TV Server, and so you may not need TV4Home at all. At the very least I hope you'll better understand the divide between what is MediaPortal stuff and what is TV4Home stuff.

<blockquote data-quote="mm1352000" data-source="post: 1237423" data-attributes="member: 82144">Sorry for what might be a stupid question: what exactly do you mean when you say &quot;it&quot;?The more specific you are, the more able I am to help. Screenshots, log files, videos... all helpful.Always keep in mind that I've never seen or used TV4Home, and I can only work with what you tell/give me.I have to assume that when you say &quot;tuners tab&quot; you're talking about MediaPortal TV Server Configuration's tuner list. If my assumption is correct, I've already explained why this is the case: the version of MediaPortal's TV Server that ships with TV4Home doesn't support CableCARD tuners like your HDHR PRIME. I'd like to point out that this particular issue is nothing to do with the &quot;guts&quot; of whatever TV4Home actually is, and it has everything to do with the version of MediaPortal TV Server.Again, I'm assuming when you say &quot;channels tab&quot; you actually mean MediaPortal TV Server Configuration's &quot;TV Channels&quot; section.You're going to have to be more specific if you want me to actually help you with this.For a start, what does the error say!This makes absolutely no sense to me! WebEPG has nothing to do with MPExtended, and as far as I know neither WebEPG nor MPExtended are directly related to TV4Home. Therefore I'm not even going to attempt to address this.If you mean MediaPortal TV Server's database structure when you say &quot;database APIs&quot; then I absolutely agree.Okay, now I think I understand why you're wanting to try MS SQL... and if I've understood correctly, I can tell you that any such attempt will be absolutely pointless. To understand why it would be pointless, you have to understand the difference between the database engine and the database structure.MySQL 5.1, MySQL 5.6 and MS SQL are database engines. The API for the database engines has not changed. Any given version of MediaPortal's TV Server - including the ancient version installed by TV4Home - and/or TV4Home itself can use any of the aforementioned database engines.The thing that could break compatibility between TV4Home and MediaPortal's TV Server is a change to the database structure. By structure I mean [for example] a change to the data that is stored (eg. a new tuner property, or a new type of channel, or a new type of schedule etc.). The database structure has changed several times between the version of MediaPortal's TV Server installed by TV4Home and the newest version.As explained above: I think trying the MS SQL database is pointless.With the greatest respect, I'm also starting to wonder: do you understand the difference between MediaPortal TV Server Configuration and TV4Home?I'm wondering this because the two specific issues you've mentioned so far - HDHR tuners not showing with the TV4Home version of MediaPortal's TV Server, and the &quot;channel tab&quot; error - have nothing to do with TV4Home (!).Maybe it would be more beneficial for you to simply install the latest version of MediaPortal before installing TV4Home so you can see what is provided by MediaPortal. You may find that what you thought was provided by TV4Home is actually a default part of MediaPortal's TV Server, and so you may not need TV4Home at all. At the very least I hope you'll better understand the divide between what is MediaPortal stuff and what is TV4Home stuff.</blockquote>

[QUOTE="mm1352000, post: 1237423, member: 82144"] Sorry for what might be a stupid question: what exactly do you mean when you say "it"? The more specific you are, the more able I am to help. Screenshots, log files, videos... all helpful. Always keep in mind that I've never seen or used TV4Home, and I can only work with what you tell/give me. I have to assume that when you say "tuners tab" you're talking about [B]MediaPortal TV Server Configuration's[/B] tuner list. [B]If[/B] my assumption is correct, I've already explained why this is the case: the version of MediaPortal's TV Server that ships with TV4Home doesn't support CableCARD tuners like your HDHR PRIME. I'd like to point out that [B]this particular issue is nothing to do with the "guts" of whatever TV4Home actually is[/B], and it has everything to do with the version of MediaPortal TV Server. Again, I'm assuming when you say "channels tab" you actually mean [B]MediaPortal TV Server Configuration's [/B]"TV Channels" section. You're going to have to be more specific if you want me to actually help you with this. For a start, what does the error say! This makes absolutely no sense to me! WebEPG has nothing to do with MPExtended, and as far as I know neither WebEPG nor MPExtended are directly related to TV4Home. Therefore I'm not even going to attempt to address this. If you mean [B]MediaPortal TV Server's database structure [/B]when you say "database APIs" then I absolutely agree. Okay, now I think I understand why you're wanting to try MS SQL... and if I've understood correctly, I can tell you that any such attempt will be absolutely pointless. To understand why it would be pointless, you have to understand the difference between the database [B]engine[/B] and the database [B]structure[/B]. MySQL 5.1, MySQL 5.6 and MS SQL are database [B]engines[/B]. [B]The API for the database engines has not changed.[/B] Any given version of MediaPortal's TV Server - including the ancient version installed by TV4Home - and/or TV4Home itself can use any of the aforementioned database [B]engines[/B]. The thing that could break compatibility between TV4Home and MediaPortal's TV Server is a change to the database [B]structure[/B]. By [B]structure[/B] I mean [for example] a change to the data that is stored (eg. a new tuner property, or a new type of channel, or a new type of schedule etc.). [B]The database structure has changed several times between the version of MediaPortal's TV Server installed by TV4Home and the newest version.[/B] As explained above: I think trying the MS SQL database is pointless. With the greatest respect, I'm also starting to wonder: [B]do you understand the difference between [U]MediaPortal TV Server Configuration[/U] and [U]TV4Home[/U]?[/B] I'm wondering this because the two specific issues you've mentioned so far - HDHR tuners not showing with the TV4Home version of MediaPortal's TV Server, and the "channel tab" error - have nothing to do with TV4Home (!). Maybe it would be more beneficial for you to simply install the latest version of MediaPortal before installing TV4Home [B]so you can see what is provided by MediaPortal[/B]. You may find that what you thought was provided by TV4Home is actually a default part of MediaPortal's TV Server, and so you may not need TV4Home at all. At the very least I hope you'll better understand the divide between what is MediaPortal stuff and what is TV4Home stuff. [/QUOTE]