Version History
0.6.0 - 29 Agust 2007 - Compatible with WebScheduler PRO 4.3. - Configurable policies about how to handle conflicts with upcomimg scheduled recordings. - Minor fixes ================================================================= 0.5.0 beta - 10 February 2007 - JTVLAN now supports WebScheduler 4. Previous versions of WebScheduler are no more supported. - Fixed a serious problem in the client related to the local recording functionality. ================================================================= 0.4.0 - 29 August 2006 - Added new logic to handle in a consistent way multiple clients connected to the same server. - Fixed some minor bugs and some layout adjustments ================================================================= 0.3.0 - 25 June 2006 - Added controls to the client GUI to change deinterlace, aspect ratio, crop settings during playback - Added control to to enable/disable the full VLC full interface on the fly while JTVLANClient is playing - Added controls to override the default capture type defined on the server side. - Added video scaling option among the transcoding settings - Client can ask server to burn subtitles - More detailed logging ================================================================= 0.2.0 - 22 May 2006 - Support for WebScheduler authentication - Volume control on the main JTVLANClient window - Toggle fullscreen control on the main window - Client now warns when WebScheduler needs the user to free the capture card to be able to perform a scheduled recording - More accurate file splitting - Solved compatibility problem with Java 1.4 ================================================================= 0.1.4 - 6 May 2006 - Transcode options. Client may ask the server to stream at a lower bitrate, an useful option when the client is on a slow net - Auto splitting. Client can ask the server to limit file size of temporary buffers and recorded shows to a given value. NOTE: this feature has been implemented very roughly. File size is only approximate and there is a gap in live tv and recordings of about 15 seconds when the files are splitted. - User preferences are persisted to an user properties file. When the client is launched it remembers its previous settings. - A new tab pane shows some details of the current activity. Known Problems -------------- - JTVLANClient has some problems with Java 1.4. Java 1.5 is strongly recommended for running the client. - Closing the VLC player window while JTVLANClient is playing puts the JTVLANClient in an inconsistent state: it continues to play but no video is shown since the viewing whidow has been closed. To reset the state just restart playing. ================================================================= 0.1.3 - 1 May 2006 - Fixed some JTVLANClient cros platform problems. JTVLANClient should now support Linux (tested) and possibly MacOS (not tested) - Client side recording - Auto full screen playback - Always on top channel list (requires Java 1.5) - JTVLANServer setup checks for possibly incompatible versions of WebScheduler and warns about it - Fixed a problem which caused WebScheduler to lock all the cards if WebScheduler version was not supported (e.g. 3.0.x). TODOs ----- - Make channel list retain focus when it is always on top and playback starts - Persist the values of the options when the JTVLANClient is closed - Transcoding options for local recording - Autosplitting of recorded files ================================================================= 0.1.2a - 28 Apr 2006 - Jakarta HTTP client replaced with the LGPL HTTP client library to avoid license incompatibilities - Basic use of RC interface to detect VLC playback problems. Still some work to do though. - Full source code included in distribution package Known Problems -------------- - JTVLANClient does not start playback properly on non-Windows platforms - Unpredictable behaviours with WebScheduler 3.0.x versions ================================================================= 0.1.2 - 25 Apr 2006 - Rework on the code which controls VideoLAN. Release 0.1.2 does not use HTTP interface any more to control VideoLAN in favour of starting and killing VideoLAN each time is needed. This approach proved to be more stable and simpler to configure - Configuration utilities both for client and server - Rationalization of the JTVLANServer HTTP interface. Now every action on JTVLANServer should be invoked through the single /servlet/JTVLANServerRes entry point - Extensive server side logging to trace problems - Simplified distribution structure (4 files for JTVLANClient and 3 files for JTVLANServer) Known Problems -------------- - Sometimes, even if the client says it is playing the video, no video is shown. This seems to be related to corruption of the data flow. - There seems to be problems when the capture file size reaches the 4GB limit. TODO ---- - Use the VideoLAN RC interface to detect data flow corruption, and warn the user and implement retry policies. This should fix the first of the Known Problems. ================================================================= 0.1.1 - 19 Apr 2006 - JTVLAN: modified the communication protocol between client and server to correclty handle error states generated by WebScheduler - JTVLAN: more control on connection timeouts and connection retries between client and server. - JTVLANServer: improved handling of shared resources (capture cards) usage. JTVLAN now allocates and deallocates the capture card in use in a WebScheduler compliant way - JTVLANClient: improved overall stability and process handling, in particular about the local VLC instance controlled by JTVLANClient - JTVLANClient: dialog notification about the main error conditions (communication problems, no available free cards to use,...) - JTVLANClient: several UI bugfixes Known Problems -------------- - Sometimes after clicking the Play button, WebScheduler starts recording successfully but JTVLANServer is not able to start streaming and the JTVLANClient gui remains freezed. When the gui is in this state it can be closed with the standard window close button and the WebScheduler recording is then correctly stopped. This seems to happen more frequently with some channel rather then with others. ================================================================= 0.1.0 - 14 Apr 2006 - The first version of JTVLAN
