[mythtv-users] Sell mythtv "set-top" boxes

[Mark Cooper]

Ben Bucksch wrote:
<CUT>
> Info missing:
> 
>    * Country, video standard (PAL/NTSC etc.)

OK, good point.


>    * Backend only or frontend only or combined

This is ( currently ) a MythTV specific option, whereas I'm trying to 
keep the database sortta generic. The comments section is available to 
identify whether the system is a backend or frontend.


>    * How many tuners

Although the database only handles one tuner at the moment, its a case 
of where do you draw the line? Three, four, five? I think the majority 
of people use one tuner, and again the comments section can be used to 
provide extra info.


>    * Which *exact* model each, ideally including exact tuner model and
>      purchase date, because the vendors change models without changing
>      their name.

 From experience, not everyone has been able to fill in the tuner field 
with 100% accuracy :) Asking people to open up their PC and look for the 
chip revision isn't practical. Some people *have* included this 
information however.


>    * Video encoding bitrate

This is in the database already.


>    * How good the encoded video is - are there framedrops, artifacts,
>      lagging pictures, "half-pictures", in which circumstances (camera
>      moves, dark scenes, 2 recordings at the same time, ...)
>    * Similar for audio - noticable stereo, washed out or clear etc.
>    * CPU load (give instructions how to determine it) per recording,
>      for live tv. anything special, e.g. does it get worse out of
>      proportion when they are combined, i.e. |cpuload(2 recordings and
>      livetv) > 2 * cpuload(1recording) + cpuload(livetv)|?
>    * TV model and type of connection/cables used
>    * tv out settings - resolution/settings used, overlay, xfree config
>    * How good the video output (tvout) is - overlay, sharpness,
>      flickering, maybe deinterlacing and jitter, are the relevant
>      features enabled in the frontend / driver?, anything odd like
>      green borders
>    * Similar for audio

This all falls under the rating and comments section I think.


> For setup:
> 
>    * Which software was used - distro, drivers, xfree, mythtv, version
>      of each

Already in the database.


>    * *Exact* drivers used (not just "Alsa", but which concrete driver,
>      which version, which config)

OK, good point.


>    * Where to get the software (if non-obvious)

erm? google? :)


>    * which config used (linux kernel config, modules.conf, xfree
>      config, any other compile parameters, anything else in /etc/)

This is outside the spec of something you can put in database fields and 
is what the comments section is intended for.


>    * Time needed to get everything running

This is subjective. What might take me five minutes to get working, 
might take a newbie many days...


>    * What had to be done, describing each step, esp. the non-obvious
>      ones which took time to figure out
>    * Satisfaction with config, with reasons. what the author would do,
>      if he had to do it again -  would he buy the same card again?
>      would did he do wrong during the setup?

Again, the freeform comments section..


>> If anyone has any constructive suggestions, I'm happy to listen to them!! 
> 
> 
> That's great. I didn't know that you're listening at all, much less 
> willing to improve it.

Where did you get that impression??


>> The amount of variables involved in ensuring two configs provide the 
>> same 'satisfaction' is HUGE!! 
> 
> 
> Maybe, but those variables would need to be captured or at least made 
> explicit somehow somewhere. Isn't that exactly the point?

GIGO. The database is only going to be as good as the information people 
put in it. While I would love to see more information being captured in 
the database, its a case of how to capture it in a consistant and 
reliable manner. BTW I don't see your config(s) in the database?

-- 

Mark Cooper
http://netmangler.sourceforge.net - Network Management with Attitude
http://pvrhw.goldfish.org - Open Source PVR Hardware Database