This is the NEWS file for kbtv

30-07-2006: 1.1.3, point release (bugfixes)

- when changing size (restarting viewer) bktr would sometimes freeze, increase
  sleep time to 1 sec, don't sleep if using saa (Kbtv/kbtv_part.py)

24-07-2006: 1.1.2, point release (saa/MK3 fixes)

NOTE! IF YOU USE THE KBTV PORT YOU SHOULD "make rmconfig" BEFORE "make"

- fixes for saa with MK3 tuners, including IF section programming -- may
  benefit other tuner types as well
- it should now be possible to select PAL B/G, I, D/K, L, L', NTSC M/N,
  NTSC Japan broadcast standard (obviously I can only test my own, PAL B/G)
- problems where tuning won't work (unless card already used in another OS) 
  should be gone now -- my Avermedia card works now after power off/on
- in buildprefs.py (or port options) one should set tuner API type and
  broadcast standard, iic address is now detected at runtime
- this stuff is reflected in the saa module by the new functions tuner_if_init
  and tuner_init, as well as the revised tuner_frequency_set function -- the
  original saa support code for tuner programming is not used/compiled anymore
- adapt hardware and GUI code where needed
- misc bugfixes, probably also introduced a few new ones :)
- update this file, README and KDE docs

25-06-2006: 1.1.1, point release (bugfixes)

- fix runtime problem (implicit cast was asssumed) in bt848.c on AMD64
- a few btsetup bugfixes
- swig version must be taken into account, we need swig13 (+), not swig11
- update imported pwcbsd codebase to latest version (1.3)

04-06-2006: 1.1

- new SDL viewers for bt848 and saa, currently they are rather minimal 
  stand-alone apps and wrapped as BTBackEnd objects in python as were 
  formerly mplayer and tvv
- required to build/install/run now: SDL, SWIG, and PyKDE, plus pygame for pwc
- add menu entry for size, small-medium-large, saaviewer is SDL downscaled
  while btviewer changes the actual capture size because this produces 
  a better image at smaller than maximum capture size
- free resizing has been shelved for now, expect this to come back later
  though; it requires moving the viewers into a library and pushing Qt
  resizing events into the SDL event loop (the stand-alone btviewer and
  saaviewer, while having -w and -h switches to set the initial size, are
  freely resizable)
- update this file, README, KDE docs, pydocs, upload some screenshots
- make a new port that properly deals with the new pwcbsd port (the pwc 
  python module is built from the pwcbsd included with kbtv anyway, but 
  pwc kernel module should be/have been installed from the pwcbsd port)

23-04-2006: 1.0.1 (never released)

- add support for USB webcams made by Philips, Logitech and others, that work
  with the pwc kernel module from raaf.atspace.org
- the driver is included and built with kbtv (see buildprefs.py)
- rendering is done internally, requires pygame (formerly py-sdl)
- the GUI has a driver switch (pwc may be greyed out)
- instead of channel-up and -down functionality as with TV cards, with pwc
  you get panning (left-right) and tilting (up-down) provided your camera
  supports it
- channel editor makes no sense with a one-signal webcam, it's greyed out
- expand btsetup to include pwc (where it makes sense)

10-04-2006: 1.0

- add support for Philips SAA chip based TV cards, -- AverMedia and others --
  using the kernel module and TV viewer from purpe.com
- tuning and input source switching functionality is in the saa module 
  (works exactly the same as bt848 module) and viewer backend is tvv
- the driver and viewer are included and built with kbtv
- some differences with bktr: saa has no AFC functionality, for embedding 
  the viewer must be launched first (contrary to mplayer) so you see it pop
  up and then embed, the video standard (PAL or NTSC) and tuner type 
  (Philips, LG, Alps, Temic) are compile-time options, as well as the IIC 
  addresses to be used; see buildprefs.py
- if there is saa support (and module loaded), saa is used, if not bktr
- if both are supported, the GUI has a driver switch (saa may be greyed out)
- hardware info changes if another driver is selected
- channel editor and behaviour remains the same, independent of the driver
- both backends use XV and there's no longer a GUI switch to choose this
- expand btsetup to include saa (where it makes sense, saa has no sysctls
  for example)

10-02-2006: RC3

- redesign and rewrite ground-up
- new build/install scripts
- the format how channel lists are saved has changed, sorry
- add full-screen switch
- now for adding to channel list it's possible to enter a list of frequencies 
  and/or a channelset and/or a composite device. Freqs/chansets can use AFC 
  (default) to autotune up to +/- 2 MHz. Then after its shown the user still
  has the chance to manually tune (same range) and accept or reject it
- integrated mplayer input config file (see below rc2) into backend code
- mainwindow is now a kpart, I'm not sure what for but it is :)
- dcop interface renewed, has all GUI actions and most get/set things
- default kbtv rendering is now xv, default size back to 400x300
- btcontrol removed (now bt848 module), btsetup utility added
- new (KDE) docs written, python modules have docstrings all over

16-12-2005: rc2

- make the default size a bit smaller; 360x270 for the video now, better for
  lower screen resolutions
- make kbtv resize back to its default size when changing rendering method
  (probably the best solution for now)
- deal with keyboard input when focus is on the video widget, well frankly,
  dodge dealing with them by using the "mute" command for mplayer key bindings
  (mplayer has no dummy command, and kbtv's audio isn't handled through mplayer 
  anyway so mute can be my dummy). Reason is that otherwise the user can stop 
  mplayer by keyboard with no clear way to restart it. The user is also not 
  expected to know all of mplayer's default key bindings. Changes been made so
  that no unexpected things can happen from using the keyboard when focus is on
  the video area. The one exception is the space bar which pauses and unpauses
  the video (useful and harmless)
- this requires installing an mplayer input.conf file (input.kbtv) and having 
  kbtv symlinking this to user's ~/.mplayer dir if not already
- a few minor bugfixes (I hope), docs unchanged for now
- become release candidate 2, PR updated port (plist, portrevision, distfile)

04-12-2005: rc1

- add DCOP interface; to try run kbtv and then `kdcop' or `dcop kbtv Kbtv'
- in conjunction, add functionality to directly enter a channel number
  or a composite when prefixed with "E"
- put this inputbox together with the volume slider as one toolbar widget
- update Kbtv documentation to explain/reflect this plus screenshot
- become release candidate 1, PR the port now, I need testers

29-11-2005: beta2

- add functionality to retrieve ALL frequencies from channelsets (by norm)
- also make it possible to add/substract 1 or 2 MHz for more accutare tuning
- best method remains entering frequencies if user knows, both work together
- update Kbtv documentation to explain/reflect this, enhanced "Add" dialog
- if no audiosource is reported by btcontrol, make it be 0 in btcontrol.py

25-11-2005: beta1

- remove the scanner, it just doesn't work reliably using status (thanks Steve)
- remove the test scripts
- remove signal (status) from btcontrol
- add functionality to add (a list of) frequencies to channel list
- reflect changes in manpage and kbtv documentation
- hold funeral for scanner and go beta to forget it

23-11-2005: alpha5

- fix bug in scanner that has krept in; scan result got lost
- add warnings when bktr or tuner device doesn't exist or is not user RW
- remove scan console output again, keep test scripts

10-11-2005: alpha4

- added a test script that runs some progressive tests and in the end kbtv;
  the tests are to be expanded/changed as needed.

06-11-2005: alpha3

- handle hw.bt848 sysctls for card, tuner, format if they are set (whether
  they work or not)
- temporarily have (rudimentary) console output for frequency scanning so you 
  can see/report what happens
- more heuristics for frequency scanning, now it runs a prescan to see if
  the uppermost signal value should be discarded or not (with both my cards
  it should be, with others apparently it should not)

03-11-2005: alpha2

- btcontrol.c should build with gcc295 and on non-i386 now
- partially fixed side effects having to do with the editor being a
  persistant object; scanned frequencies now appear in the editor as they 
  should, they always get appended to the list though (merge/replace broken) 
- a few other small things

01-11-2005: initial alpha version
