|
| ||||||||||||
|
Current Release/Bug ListsLast Updated: 26th June 2008 Release notes Freeware release
Retail Release
Beta/Test release
Which release have I got? Selecting the 'About' button from the 'Help' menu of Playout or Playout Manager will display the version number. To simplify matters, from version 3, both applications will have the same number, more recent versions of Playout also display the release number on the main title bar. System Dependencies
Operation under Windows Vista is unknown at this time.
Development status Following represents the current issues and known bugs for the current release(s). Critical issues are highlighted in red. Bugs, Improvements ------------------ Please send bugs, improvement suggestions to: beta@onasticksoftware.co.uk Development status & latest bug fixes are being maintained at: http://www.onasticksoftware.co.uk/playout.html Known Issues ------------ Microsoft DirectSound (p/o DirectX) ----------------------------------- The DirectSound component of DirectX is utilised for audio playback by OAS Playout. DirectSound is the Windows sound system utilised for audio playback by OAS Playout. 1. Short sound bursts may be heard when a track is paused, cued elsewhere then resumed. Occuring on the main player and cue points dialog. The same bursts can aslo be heard by using MS Media Player by moving the seek bar and resuming playback hence it is a fault of DirectX itself not Playout. This affect appears to be OS/DirectX/hardware dependent - in short a given combination of all three may alleviate the problem. DX can be freely downloaded from http://www.microsoft.com. An alternative is to utilise the ASIO driver if your soundcard supports it. See the online help for more information. Playout V3.x (latest release versions) ---------------------------------------- 1. Audio tracks may skip at random intervals. This problem has only been seen on high end processors where the MP3 decoding time is very fast. This problem applies to all Playout releases prior to v3.1. This problem can be rectified by upgrading the audio core to the latest version. Fixed in v3.1 2. v3.2x: When loading tracks into a Player from a playlist/jingle list, the next time the 'Load' button is pressed, the original playlist may not be re-displayed, instead another one is displayed in it's place. Fixed in v3.22 3. Playout only supports stereo, 44khz audio files - attempting to utilize files which do not correspond to this format will generate an error dialog of the form: v2.x: "OAS Audio system failed to execute cmd 0, error code 1" or v3.0+: "Whilst executing the command 'Input Open', OAS Audio generated the following error: Input Open Error - file not found or unsupported file format" By default OAS Playout Manager will not import unsupported file formats however this may be overriden and can also be experienced using the freeware/trial version. Fixed in v3.06 - this error may of course still be generated when encountering an unrecognized/unsupported file format however as of this release the full range of audio formats are supported 4. Load Dialog: If Artist/Title search box has focus, the next time a selection is made on the listview, the box is not updated with the new contents. 5. If the 'Disable Playlist Updates' checkbox is enabled (Settings, Preferences menu), Playlist automation mode will not work properly - the first few tracks in the list will be repeated continuously. Fixed in v3.06: Playout will now not enter automation mode if this setting is enabled, instead a warning dialog is displayed. 6. ShoutCast Track Lister may populate the 'last 10 tracks played' with the current track. This can occur if your communication with the Shoutcast server goes through a proxy or web cache (since v2.5, Playout utilities Internet Explorer's proxy/connection settings). At least one version of the Squid web cache has exhibited this problem. Workaround: If possible, set IE to bypass any proxy or cache for Shoutcast servers. This problem appears to be related to the Shoutcast protocol for updating track details to the server in that it does not reply to the HTTP request used to perform this update. As such Squid (and possibly others) retry the request a number of times causing the details to replicate in the track history. 7. Playout may not migrate v2.x soundcard settings when upgrading to v3.x - they will be reset back to the default 'Primary Sound Driver'. Fixed in v3.02 8. v2.61+: If button wall playback is stopped whilst in 'auto-fade' the main player volume level is never restored, it is left at the decreased volume level. Fixed in v3.02 9. Voicetrack scheduler will execute programmes at incorrect times if system time is is NOT set to GMT (or UTC). Fixed in v3.03 10. If voicetrack programme is the first playlist (or only playlist) in the system, the scheduler will never automatically execute the programme. Fixed in v3.03 11. v3.03+: 'Hotkey' buttons (instant launch '1' & '2' plus Button Wall selects) not working in enhanced mode. Fixed in v3.06 12. Playlist/Advanced Settings, duplicate artist check can filter out jingles, adverts etc. Fixed in v3.06 13. v3.06+: 'Speed Controls' (Enhanced display mode only) do not work correctly if using audioformat other than 44khz. Fixed in v3.1 14. Excessive event notifications are generated if Playout cannot enter FailOver mode. Fixed in v3.08 15. Track lister updates may stop working for no apparent reason, they may often then resume normally sometime later (this was previously noted in the 'proxy/web cache server issue' (5) but is now confirmed to be a distinct problem. Fixed in v3.07 16. Auto scheduled voicetrack programmes will run erroneously if 'Disable Playlist Updates' (Settings, Preferences menu) is checked. Fixed in v3.1 - auto scheduling will be disabled if this option is enabled 17. Launching a second instance of Playout or Playout Manager (on the same computer) generates the error message 'File Damaged'. 18. If button wall category lists are filtered to exclude certain lists, changing the contents of unassigned buttons may not work ie. the button remains blank and no error is reported. The net effect is that the button change will have been applied to another button wall category list. Fixed in v3.09 19. When dragging the scrolling message bar on dual monitor systems, if you "drag" the mouse cursor from one monitor onto the other the scrolling message freezes and will never move again. Fixed in v3.09 20. aac files (raw, not m4a) will not play with ID3v2 tags present. Fixed in v3.09 21. The order of clips loaded into a button wall may randomly change ie. not the order they are presented in Playout Manager. A temporary workaround is to perform a 'Compact' of database which should restore the order. A patch for v3.09 is now available to rectify this issue, please email for details. Fixed in v3.1 22. v3.09 only: The new audio core included with the 3.09 release can truncate the final second of playback early (noticeable in auto/automation mode). This problem may be rectified by upgrading the oas-audio.dll to the previous release which can be downloaded from the OAS Audio page. Simply copy the dll into your playout installation folder. Fixed in v3.1 23. v3.09, v3.1, v3.2x: If a button wall file is not accessible, Playout gets stuck repeatedly generating "Audio File Not Available" messages. Fixed in v3.11, v3.22: due to a misconfiguration is also in early versions of v3.2x. 24. Sound card setting change does not affect 'floating' button wall until it is either closed/re-opened or the assigned player is toggled. Fixed in v3.2 25. Enhanced mode only: The display of the Speed Control slide bar is not restored if the control is hidden then reactivated again. Fixed in v3.2 26. Program crash when starting a playlist (from the Playlists, Start) menu. Workaround: From the Playlists menu, choose Setup then press the Advanced button. Ensure all the options are unchecked then click OK. Restart the playlist. Note that this problem will only occur once (if at all) as it is due to a damaged configuration file created after initial installation. Fixed in v3.2 27. Playout enters FailOver mode if an automated playlist is started which has no entries it AND the playlist is set to loop. Fixed in v3.2 28. First few entries in an automation sequence keep being played. Playlist, button wall changes & profile changes all fail with an error message. The root cause of this behaviour is that the Playout database can only be accessed as 'read only', as such all updates (required for the functionality that fails) will not work properly. This condition normally arises if the database has been located onto a network server but the file permissions have not been setup to support writes in the network share HOWEVER Playout does not report this in a user friendly manner. Fixed in v3.21 29. 'Help' buttons do not work if a Playout database/error warning dialog is displayed when the package is first activated. Fixed in v3.21 30. v3.2: Volume/speed controls not updating if scrolled with arrow keys. Fixed in v3.21 31. End cue points may trigger 1 second earlier than required. 32. Windows Media (.wma) files will not seek correctly on long (>7 minutes) tracks. Fixed in v3.2 OAS Playout Manager v3.x ------------------------ (Retail Version only) 1. If an item is deleted through the 'Component Editors' - Artist, Album, Category etc. & then attempted to be added back in (without first performing a Database Update) an error dialog is generated indicating the update failed. Workaround is to perform the Update then re-try the add. Partially fixed in v3.03 - the editor will flag this up rather than indicating a database update error 2. ID3v2 tags may not update correctly, resulting in duplicate fields being stored in the file - this seems to be isolated to the 'Track Duration' field only and causes ID3 comparison checks to always fail. 3. Batch operation 'Path Update' can sometimes introduce an extra backslash at the start of the pathname eg. 'c:\\music' (instead of 'c:\music'). Has no functional impact. Under investigation. 4. Search of RuleList will always be performed in the original rulelist order such that if the order is changed (by clicking on a column eg. "Title" the search will jump all over the list still following the original sequence) on each consecutive pressing of the 'Next' button. 5. Search (by Artist) on Music Edits and Playlist Management can fail to select an entry matching the search criteria if the initial matching artist held in the database has no track currently by said artist 'in view'. In most cases this means that the artist has no associated track in the database however when applying Playlist filters this becomes more noticeable and may well not function at all. 6. Playlist may not display in Playout Manager tool immediately after Playlist generation has completed. Reselecting the list will re-display it correctly. Fixed in v3.05. A slight delay has been introduced to the code to allow the database driver to 'catch up' - this appears to have resolved the issue. 7. When adding tracks to a rulelist, if the default sort order is changed they appearto be added randomly in the list. This is because insertions are made according to the original sort order, restoring the sort will show the tracks in their "correct" order. 8. Cue points editor may not allow track/cue position to be set at or near the very end of a track. The track duration for audio is rounded _down_ to the nearest second ie. if a track is 34.8s it will be displayed as 38s. This is in line with many other popular MP3 players and should not pose a real problem in normal usage. Whether track durations should be rounded up is pending investigation. 9. The 'Revert' button on the Playlist Management page does not discard all edits & reload from the database - specifically any PlayList name modifications or deletions remain. Workaround: Select another tab & switch back to the Playlist tab to ensure database settings are reloaded. 10. Component Editor: You may find after performing a series of updates on a page that attempting to delete "core components" with the editor - invoked by pressing the 'e' button next to items such as Playlist Names, Artists - will fail when you update the database. Workaround: Either use the 'Revert' button to refresh the page, then perform the delete or toggle to another tab then back again. 11. Voicetrack Segue Editor allows "track 2" start point to be positioned prior to "track 1" start which can cause an erroneous voicetrack programme to be produced. Fixed in v3.01 12. Voicetrack track start times may not be recalculated correctly if you delete an item then insert another one directly after it without performing a database update. Fixed in v3.02 13. Cue Points Editor: Whilst setting 'Cue End', audio playback of the track may not start if the editor is displaying audio near the start of the track. Typically this condition may arise if setting cue points for short audio clips. Fixed in v3.03 14. Copy/Paste of voicetrack lists does not transfer all voicetrack information and in addition will have unpredictable results with regard to maintaining database consistency. Paste is disabled in v3.03 until a suitable fix can be implemented 15. Database entries for voicetrack segues are not removed when a voicetrack list is cleared via the 'Clear List' button (or manually deleting entries). Once the segue editor is re-invoked, they are still listed although unusable because the files have been removed. Fixed in v3.03 16. If file access difficulties occur when invoking the segue editor (voicetracking) the programme will hang indefinately. Fixed in v3.04 - error dialogs are generated under these conditions 17. v3.04, 3.05: Voicetrack: When recording and saving a new segue, the error message 'Error adding new segue to the database' is generated. Fixed in v3.06 18. Playout Manager will not import or recognize ID3 tags stored as Unicode. Attempting to update an existing unicode tag is liable to corrupt the ID3 header. A patched ID3 tagging library which may be incoporated into any release of Playout is available here. Download and unpack the DLL into Playout's installation folder. Note that since v3.09 of Playout this DLL is included as standard so this update need should not be applied. Fixed in v3.09 19. 'ReAssign' button doesn't work in core editor. Fixed in v3.09 20. Crash can occur when Playout Mgr tries to report a database import error during music import. Fixed in v3.09 21. v3.09: Attempts to write ID3v2 tags to files which do not already have a tag will fail with the message 'Error - unsupported ID3v2 revision'. Fixed in v3.1 22. In Playlist generator 'Automation Sequencer', cannot select the same categories to be classed as 'Jingles' and 'Adverts', if they appear in both 'Jingles' will take precedence. Fixed in v3.1 23. Playout log view does not update fully following a database change leading to likely crash. Fixed in v3.1 24. If a clip is deleted from a Custom Audio Cliplist (but not yet updated to the database), the player can play the wrong clip in the list. Fixed in v3.11 25. MP4 metadata for composer is incorrectly stored as lyricist in the database. Fixed in v3.2 26. There is an important step missing in the help documentation regarding the automatic generation of playlists - prior to invoking the playlist generator all changes (particularly to the rulelist) must be saved to the database by pressing the Update button otherwise they will not be applied. Fixed in v3.2 27. Import of non-ASCII (US-English) filenames does not work properly. The import appears to succeed however the file will not play and the system reports 'file inaccessible'. On closer inspection, the non english characters will have been replaced. Support for non ASCII filenames (or metadata) ie. Unicode is not available in Playout. You will need to rename the file to include only ASCII characters. 28. MP4 encoding information is always marked as Variable Bit Rate (VBR). 29. Attempt to perform any database updates will always fail. This is due to the Playout database can only be only be accessed as 'read only' This condition normally arises if the database has been located onto a network server but the file permissions have not been setup to support writes in the network share HOWEVER Playout does not report this in a user friendly manner. Fixed in v3.21 30. 'Help' buttons do not work if a Playout database/error warning dialog is displayed when the package is first activated. Fixed in v3.21 31. When viewing Music/Ad logs with 'Filter Duplicates' checked, some items meeting the filter criteria are not displayed. 32. Windows Media (.wma) files will not seek correctly on long (>7 minutes) tracks. Setting End Cue Points will also behave unpredictably. Fixed in v3.2 Support for Variable Bit Rate (VBR) MP3s ---------------------------------------- Since Playout v2.4, support for VBRs is significantly improved. There is now logic in place within Playout Manager to detect and process any VBR files in order to correctly determine the track length. OAS Playout will now also display the length correctly and positioning of the 'cue slider' is now much more accurate. However due to the general difficulties in detecting VBR files this logic is not infallable and some tracks may pass through the checks. Also the seek positions, whilst improved will still not be totally accurate. As before, the presence of a complete Xing VBR header is still highly recommended and will give the best reliability with these file types. Alternative database engines ---------------------------- Support is available within Playout to utilise two alternative database platforms (MySQL & PostgreSQL) over the stock MS-Access based solution. Hosting on one of these offers a number of advantages & disavantages, for more information see the 'readme' files under in the relevant 'Engines' sub-folder of the Playout installation folder. MySQL ----- Development is considered to be at a late 'beta' state of testing, notably having been successfully deployed on a recent RSL. Testing and integration has been performed mostly with the 3.51.6 ODBC connector which has proven to be a reliable solution however one issue has come to light in that logged time stamps between 12am and 1am are mangled. This issue has been fixed in later releases of the connector, however this has been negated by the fact that the most recent connectors have a serious bug which prevents Playout from connecting to the database at all. MySQL AB have recently released the 3.51.14 connector which has been tested and is known to work with Playout v3.01 and later releases. However we have not yet performed any extensive testing with this connector. BE AWARE THAT ALL VERSIONS OF THE CONNECTOR FROM 3.51.7 to 3.51.12 DO NOT WORK WITH PLAYOUT. Known Issues: - Playout does not work with certain releases of the MySQL connector (see above). Fixed in v3.01, with MySQL connector 3.51.13 - Entries in the music log are always associated with a playlist even if the track is picked from outside a list. Fixed in v3.02 - 'Compact Database' menu item crashes Playout Manager. - There is a possibility of inserting invalid data into the database if Playout utilises an item which has been deleted by Playout Manager - the obvious area is in music or advert logging where the system can log an 'invalid' advert or song. This will then crash the log viewer in Playout Manager. - During database creation, MySQL may generate an error on line #403 'ALTER TABLE PlayLists ADD COLUMN Trigger INT ;'. You can rectify this by replacing the word Trigger with StopPoint then deleting line #413. |
|||||||||||