=============================================================================== == UPDATE INFORMATION FOR SS32 == =============================================================================== ************************************************************ *** PLEASE NOTE: Applications SS32, VT, AS, SS_EV and *** *** SSENT now require the file SCOTTBTN.DLL to be in the *** *** default directory or WINDOWS\SYSTEM directory. *** ************************************************************ 81129 (5.1.0) ------------------------------------------------------------------------------- ADDED: Support for adapter 6714. This was a "blind add", meaning no testing was done specific to this adapter. It was added as mostly a "clone" of 6740, differing only in number of inputs and digital capability. CORRECTION: The 6740 adapter, added in version 81116, was mistakenly categorized internally as having digital inputs and outputs. This only means that if configured for digital, it will try to play/record digital and likely throw an error. As of this version of SS32, the 6740 is correctly identified as analog only. 81116 (5.1.0) ------------------------------------------------------------------------------- ADDED: Support for adapter 6740, including auto-detection of those adapters which require host buffer allocation. UPDATED: HPI interface files updated to latest SDK. In theory, SS32 should run on any driver version that supports the adapter but in trying a few, this is not the case. For reference, this update was done using 4.20.15. Drivers that fail: 4.16.9 4.18.21 Drivers that work: 4.20.15 4.20.18 NOTE ON ASIHPI32.DLL: This DLL is installed when the ASI driver is installed, thus additional versions of this DLL should be purged from the system to prevent linking with the wrong DLL. MESSAGEBOX CHANGE: Sometimes when the "Error before setup" messagebox appeared, the first error would cascade into dozens of follow up errors, making it difficult to exit the application. A "Cancel" button was added to the box to block all subequent error messages to allow user to exit SS32. Do not use "Cancel" unless it is understood that no more errors will be displayed until SS32 is reloaded. MINOR COSMETIC CHANGE: More room created for the display of serial numbers. 21017 (5.1.0) ------------------------------------------------------------------------------- ADDED: Support for adapters 6614 and 6640 assuming same as 6514 and 6540. CHANGED: This version of SS32 has been recompiled to work with the ASIHPI32.DLL so that it can run on W7 and 64-bit Windows using ASI drivers above 3.xx.xxx. To differentiate SS32 builds that work with this DLL from possible future (and previous) versions that do not, the build number on the configuation/SysInfo page has the suffix "+ DLL". 20821 (5.1.0) ------------------------------------------------------------------------------- ADDED: This build is the same as 20620 except that support for the 6685 ASI adapter has been added (without testing) under the assumption that it is identical in functionality to the 6585. 20620 (5.1.0) ------------------------------------------------------------------------------- CORRECTED: Testing code for the Regional Split feature was accidently left in the 20420 compile which created encoded versions of the title and placed them in the trivia/notes field. 20420 (5.1.0) ------------------------------------------------------------------------------- CHANGED: This build can use the ASI 6585 adapters since it will no longer stop on a #401 mixer error. (This error is ignorable since these adapters do not have this particular mixer control). Also, though untested as of this writing, this build should be able to access all 8 devices on this card. 10713 (6.2.2) ------------------------------------------------------------------------------- CORRECTED: When support for ASI 6640 was added, there was no case statement included for the code block that created peak meters for playback and so the adapter audio streams always read as the same value in cart recorder (usually max volume). 10405 (6.2.2) ------------------------------------------------------------------------------- MODIFIED: The use the dMarc XML parser in messaging handling has been greatly reduced and message handling in general has been simplified. Also, messages targeted for other radio stations are now discarded much earlier in the parsing process in case they have been causing periodic collisions. 10324 (6.2.2) ------------------------------------------------------------------------------- MODIFIED: The majority of entries in the apperror.log seem to involve discarding memory block by the dMarc-era code when handling messages to and from CS. In this version of SS32, significant changes were made in the way messages are created and discarded, especially XML messages that were being auto-discarded. 10222 (6.2.2) ------------------------------------------------------------------------------- MODIFIED: An apperror.log showed that function GetBeginTagOs threw an exception. There appeared to be nothing in this function that would do this under normal circumstances but since the stack dump shows the exception apparently occurred when freeing a temporary std::string, GetBeginTagOs has been reworked to not use this string at all. 10214 (6.2.2) ------------------------------------------------------------------------------- MODIFIED: When the embedded VT application exits, it goes through a shutdown sequence for a few moments while displaying a banner to that effect. During this short period of time, it was posible to hit the exit button one or more times and cause the enclosing SS32 to crash. As of this version, the exit button can send only one "exit" message. (Though it does not seem possible, should the VT application get stuck and cannot exit because of this new capability, the user can cycle the "options" button to manually clear the flag that prevents exiting). CHANGED: For some reason, the exception reporting in the apperror.log has alwayslisted the line and function name of the excpetion handler itself instead of the function thorwing the exception. To make things more helpful, the apperror.log now lists the troublesome function, the file it is found in and the line number. ADDED: Since the previous version of SS32, a few hundred more functions have been enclosed in try/catch blocks in an on-going effort order to try to capture every remaining exception (if any), harmless or not, in the apperror.log file. CHANGED: The method "Deck::IsVT()" in "vt_deck.cpp" has appeared in the apperror.log file as throwing a handled exception so it has been reworked. CHANGED: A minor cosmetic change was made to the Periodic Ram check line in the AIR log so as not to overwrite the ')' character. 10124 (6.2.2) [Special version: Use only if directed] ------------------------------------------------------------------------------- ADDED: The function called "AllocateBuf" was reworked after showing up in a DrWatson log in hopes of preventing the seemingly random crash-to-desktop. 10121 (6.2.2) [Special version: Use only if directed] ------------------------------------------------------------------------------- CHANGED: In resppnse to an exception noted in the apperror.log, all code that used the SetAirTime(SYSTEMTIME *) and SYSTEMTIME2MsgString() methods were reworked so that these two functions could be eliminated. ADDED: Just to make things clearer, SS32 now writes a signon string to the apperror.log upon startup. 10119 (6.2.2) [Special version: Use only if directed] ------------------------------------------------------------------------------- ADDED: In order to reduce the number of exceptions that are showing up in the apperror.log file, try/catch traps have been placed around the function that draws the clock to the screen and the function that parses the elements of an XML message within the dMarc XML parser. When an exception is trapped by either of these two functions, a line will appear in the apperror.log to the effect "...exception averted." This will allow these exceptions to still be noted even though handled. For this release, logging messages to the apperror.log (see 01220) has been removed as having served its purpose for the time being. 01222 (6.2.2) [Special version: Use only if directed] ------------------------------------------------------------------------------- CORRECTED: This is a corrected version of 01220 (6.2.2) to fix the problems when using the embedded voice track applicaton. See details below. 01220 (6.2.2) [Special version: DO NOT USE] ------------------------------------------------------------------------------- DIAGNOTIC ADDED: This special version logs all XML messages that use the parsing mechanism to the "apperror.log" file in hopes of discovering which messages are causing the "cannot continue" error message. So as not to fill the file too rapidly, these mesages are trucated to approximately 200 characters and are preceded with this tag: MSG(xx)--> (where xx is the length of the message). Since this diagnostic is somewhat resource- intensive, it is recommeded that this version be removed once the problem has been corrected. FIXED: On startup, a harmless exception was showing up in the apperror.log file (characterized by a stack that started with the "startup" function and ending with "realdrawevent") which was caused by a non-NULL pointer in the empty structure that all events point to upon SS32 startup. This fix is purely cosmetic since the exception was otherwise successfully ignored. 00517 (6.2.2) ------------------------------------------------------------------------------ ATTEMPT TO FIX: An observation has been made that if the embedded voice track application is exited while the stack is placing a new event on-air, an "SS32 has encountered an error and needs to shut down" message will be generated. Since this behavior cannot yet be reproduced, an "educated guess" fix has been applied to this version which causes the embedded VT application to check the stack for upcoming transitions before actually exiting. So that there is the maximum chance to catch this, attempts to exit within five (5) seconds of a stack advance are delayed. This slows down the exiting process somewhat but if it confirms that the problem goes away, there might be some fine-tuning that can be done later to speed it up. As a fail-safe for unanticipated situations, the embedded voice track will eventually exit without checking after 60 seconds. 00507 (5.1.0) ------------------------------------------------------------------------------ FEATURE ADDED: Support for Regional Split of spot playback has been added. For every spot that needs to be split, a CIC cue is sent out that indicates the spot that replaces it. The message that goes out is in the form: 0:LTRN:BTRN_YHTY-6454:* which can be thought of as four "fields" separated by the ':' character. The first field ( 0: ) and last field ( :* ) are stable so only the second and third field need be indicated. These two fields are to be placed in one of the three primary text description locations in the audio file header: Title, Artist or Trivia. The two CIC fields are "encoded" using the hopefully unique "pipe" character '|' like this (using the example above): |LTRN|BTRN_YHTY-6454 (The 'pipe' character is used to detect and locate the CIC so this character should not be used anywhere else in title, artist or trivia since it will trigger a false UDP message.) The encoded CIC string can appear in anywhere the chosen text description (Title, Artist or Trivia) where there is room. The Regional Split capablity is configured on the new "Regional Split" page of Options/Configuration. All items on this page can be changed without the need to reload SS32 for them to take effect. Settings on this page (that are not text-entry boxes) are changed the same way as on other pages: That is, using left and right mouse clicks. Since each CIC cue is sent to two ports, there is space to indicate two UPD IP and port addresses. In the event that each CIC needs to be sent more than once on each port, the number of times sent can be adjusted but it is unlikely that this value should be anything other than "1". A port number of zero (0) should be used to deactivate a UDP port. Once a location for the CIC codes is chosen (Title, Artist or Trivia), SS32 should be told where to look for them using the "Search for CIC in" setting. The "{Not Active}" setting should be used to deactivate the search for CIC cues entirely. CIC cue are sent prior to spot playback by the amount indicated. 0.10 (100 msec) is suggested but should be adjusted to the needs of the UDP environment. To cause a sample CIC to be sent for testing purposes, there are six buttons (one for each stack position). Of course, an event with a proper code in the proper field must be in that stack position. Since CIC cues tend to be similar, a set of four optional "macros" has been provided which can be used when entering the CIC cues into the audio file headers. A single character can be programmed to represent a string of characters. For example, a '%' could represnt "LTRN" and '$' could represent "BTRN_" so that your entry might look like this: |%|$YHTY-6454 which would be expanded to this: 0:LTRN|BTRN_YHTY-6454:* Even though any character can be selected, macro characters must be chosen carefully to ensure that they will never appear otherwise in any CIC encoding and since the delimiter character is '|', that should never be selected as a macro character. Using macro characters is optional and should be left at "none" if not used to prevent accidental expansions. 00412 (5.1.0) ------------------------------------------------------------------------------ CHANGED: Splash screens for SS32 5.1.0 and embedded VT have been brought up to date using WideOrbit graphics and dMarc icon removed. This is primarily in anticipation of adding new features and is not necessarily intended to be a released version. 00126 (6.2.2) ------------------------------------------------------------------------------ CHANGED: The ability for SS32 to display the versions of the embedded apps (Voice Tracker and Cart Recorder) was lost in the hand-off from Google to WideOrbit and in this version, it has been restored. Even though these embedded versions have had no functionality changes, their version numbers have been reset to the current date to signify code changes made to restore version numbers. 00122 (6.2.2) ------------------------------------------------------------------------------ CHANGED: The recent roll-over to 2010 presents a good opportunity to review the meaning of the build number: SS32 and related apps use a five-digit build number created from the month and date of compile prefixed by the last digit of the year. This trails the traditional, dotted major and minor version digits to form a complete version, as in this example: 6.2.2.00122 BUG FIX: A flaw in processing edit messages prevented Playlist Editor from editing some of the future SKD files that were buffered in memory in SS32. In this version, any of the four buffered schedules can be manipulated from Playlist Editor. PROTECTION ADDED: A try...catch block was placed around the midnight-upload of Air files in an attempt to circumvent unexpected failures during this process. 91013 (6.2.2) ------------------------------------------------------------------------------ WIDEORBIT VERSIONS: Under WideOrbit, SS32 became "legacy code" with minor maintainance changes. The version numbering system was returned to the "classic" x.x.x. format. This version added a new EULA and a WideOrbit" splash screen. NEW FEATURE: A new checkbox "Add bold" was appended to the "Use larger font" checkbox in the "misc settins" section of the "System" configuratin page. This adds the bold attribute to the font used in the title/artist/trivia lines in the stack. As always, this font take n the color of the category being displayed. SS32 must be reloaded for this setting to take effect. dMarc/Google versions ------------------------------------------------------------------------------ DOCUMENTATION CHANGE: SS32 was converted to SS32 "A.I" with major version numbers of 6.0 and then 6.2 and a different scheme for build numbers. The change log was kept elsewhere. 606xx (5.1.2.) [In-house] ------------------------------------------------------------------------------ BEHAVIOR CHANGED: In previous versions, if errors were generated by the initialization of the audio cards before the error- and log-reporting mechanism was fully functional, a messagebox for each error (labeled "Error before Setup") would be displayed and the execution of SS32 was halted until the operator cleared the error message box. As of this version, all errors generated before it is possible to report them to the operator are collected and sent in a batch to the AIR log under the heading of "Initialization Errors". This allows SS32 to come up unencombered even if such errors occur. (Note: This does not include a failure to connect to ActiveMQ--which will still displays a message box and wait for user intervention since this error has no automatic recovery.) 60330 (5.1.0.) [In-house version only] ------------------------------------------------------------------------------ ATTEMPT TO CORRECT: This version is test only to see if audio starvation is affected by this change: Delay placed in Inbox loop. 60329 (5.1.0.) [In-house version only] ------------------------------------------------------------------------------ ATTEMPT TO CORRECT: This version is test only to see if audio starvation is affected by this change. 603xx (5.1.1.) ------------------------------------------------------------------------------ REPAIRED: The same fix for AP events noted below (at 60323) has been applied to version 5.1.1 as of this build. 60323 (5.1.0.) ------------------------------------------------------------------------------ REPAIRED: When using AP events, if a slight delay or other conditions allowed the system clock to tick into the next whole second before the event following the AP event was able to start, the system would be tricked into generating a "system EOM" and cause that next event to be taken off the air in favor of event following it. 60303 (5.1.0.) ------------------------------------------------------------------------------ NEW CAPABILITY: The Netfill feature can now be used across midnight. In pervious versions, if the size of the spot break to be Netfilled was large enough to cross midnight or if the schedule was running late and a netfilled break was forced to cross midnight, the target value of the calculation would exceed 23:59:59 and would never be reached. As if this version, this condition is detected and the calculation is corrected. Two more codes have been added to the "To Fill" AIR log entry to assist in diagnostics: Recalc='S' Target time is a safe distance from midnight. Recalc='X' Target crosses midnight and is not yet corrected. 60228 (5.1.0.) ------------------------------------------------------------------------------ NEW CAPABILITY: The Powerfill feature can now be used across midnight. Also, in previous versions, if a Powerfill sequence was operating too close to midnight (with, say, a fill target at 23:59:59), there was a possibility of the system clock flipping over into the next day right at the time of fill calculation, causing SS32 to erroneously try to fill the entire next day (nearly 24 hours). As of this version, the context of the fill calculation is taken into consideration and adjustments are made. For diagnostic purposes, the "To Fill" line in the AIR log now has an extra piece of information called "ReCalc=" which has the following meanings: ReCalc='N' Normal calculation, no dangerous context detected ReCalc='C' The target of the Powerfill was found to cross midnight ReCalc='F' The system clock flipped into the next day at a critical moment. 51220 (5.1.1.) ------------------------------------------------------------------------------ BEHAVIOR CHANGED: For stations using Wheatstone consoles, if the SS32 audio devices are always assigned to the same channel (fader) and is it not necessary to use the "dynamic assignment" feature (described at 51214), it is now possible to avoid having a physical IP connection to the router and to have a simpler setup routine. Follow these steps instead: o Be sure that the "Active" checkbox for Router IP and port address is NOT checked. This will alllow a button called "Map Devices" to appear. o Click the Map Devices to show the grid of current assigments. These assignments default to 1->1, 2->2, 3->3, etc. o Click the "Learn" button down (active). o Click those squares that describe which SS32 device is on which console channel (that is, if Device #2 is on Channel #4, for example, click the square where those values intersect). This will draw a blue dot to represent this connection. Since only one connection is allowed per device, making a connection may result in another connection disappearing. To remove a connection, click an existing blue dot to toggle it off. o When done, click the "Learn" button up (off). Reloading SS32 after plotting new Wheatstone connections is not necessary. However, if a connection is replotted while it is on the air, since the new routing is immediately in effect, SS32 will not know to shut off the previous connection at the end of the event and, in fact, SS32 may shut off a channel that is on the air (depending on what changes were made). Thus this practice is discouraged but not prohibited. CORRECTED: If an "XA" event was assigned, waiting for a pin closure to activate it and a Named Schedule was loaded in the meantime, the Named Schedule would become the schedule that was used when the closure for the XA event finally came. As of this version, Named Schedules no longer "take over" any pending XA events. {5047} BEHAVIOR CHANGED: When using the "Hot+" to select a new hot button page, the "Hot+" now button becomes a "cancel" button in case this button was selected in error or it is otherwise unnecessary to change pages. This behavior change has a side effect that addresses a rarer but more severe condition: If the hot buttom index page is showing and the operator presses ALT-TAB either BEFORE or AFTER touching an area of the screen NOT PART of the the hot button index screen and Windows has no other application to switch to, the index page closes, leaving the control buttons disabled. Previously, without the "cancel" button, there was no alternative to regain button control other than reloading SS32. With this version, the "cancel" button is left enabled after this unusual sequence and touching it will "resync" the buttons with the state of the index page and, in effect, restore the functionality of the remaining control buttons. {4671} 51214 (5.1.1.) ------------------------------------------------------------------------------ FEATURE ADDED: The interface with the Wheatstone console now has the capability of tracking changes to the "source" knobs on the console in order to correctly choose which channel (fader) that currently contains the audio device needed by SS32. This renders obsolete the section in configuration where audio devices were permanently associated with console channels and thus that section has been removed. Theory of Operation: SS32 uses the concept of Audio Devices (numbered 1 thru last) to select an output for a given audio event. Since Audio Devices coming into the Wheatstone console can change dynamically, they are no longer permanently associated. Instead, SS32 monitors all source changes on the console and keeps an interal record of where each of its Audio Devices is currently connected. When it comes time to place an audio event on the air, SS32 consults this internal chart and sends the switching messages to the appropriate channel(s) to turn on that channel. Since the operator is locked out of changing sources on a given channel while that channel is on the air, SS32 does not re-check the location when turning off the channel. Set up: This feature requires preparation. First, the Wheatstone console router must be connected to the workstation where SS32 resides (in addition to the console TCP/IP connection). Consult the Wheatstone documentation for details. Be sure that the proper port number and router IP address are entered on the "Console" page of SS32 configuration (in the "Wheatstone IP Addresses" section of the Wheatstone tab). Also be sure the "Active" checkbox is checked. If "Auto Connect" is used, reload SS32 to establish a connection. Also the manual connection button can be used. If all is well and "View Msgs" is checked, a new message should appear in the window about every six seconds. Next, click "Router Link Setup" button. This reveals a chart where the Wheatstone audio channels are listed across the top and the SS32 play devices are listed down the left side. Normally this chart is in the "display" mode where connections between Audio sources and Wheatstone destinations are shown as green dots to represent known associations. However, connections cannot be determined until SS32 has learned the ID values of the hardware. This is accomplished as a one-time procedure as follows: o Click the "Learn" button down (active). o Click on the first ("1") Wheatstone channel number to highlight (yellow) o On the console, select ANY source into the first channel that was not there before (that is, a different source than it was). Consult Wheatstone documentation for specifics but it should involve the "Take" button. The ID of this channel should appear in the box in the upper left corner instead of the word "none". o Repeat for every Wheatstone channel (1 thru x) that might host an SS32 audio device. o Highlight the first SS32 audio device ("1") o On the console, select the input source that is the FIRST SS32 AUDIO DEVICE into ANY Wheatstone channel where it was not selected before. (The ID should appear in the display box). o Repeat for all SS32 Playback Audio Devices in use. o When done, the IDs can be checked by highlighting any channel or device to see its ID. (If the various internal ID are known, this can be used to verify them). o When finished, click the "Learn" button up (off). After this setup sequence, the system can be verified by making various changes at the console and observing the green dots on the chart. Whenever an ID of a known audio device is detected by SS32, its location (or removal) is diagramed on the chart. In addition, on its own, every six seconds, SS32 will poll another known Wheatstone channel to keep its internal table up to date (in case the change at the time it was made was missed). Therefore, upon reloading SS32 from desktop (with "auto connect" on), it will take six seconds times the number of channels it knows about to fully populate its internal table. (As an example, four channels would take 24 seconds to fully learn where each Device is and perhaps more if any inquery is lost.) This is only important if SS32 is reloaded. CHANGES MADE TO EMBEDDED APPLICATIONS: The following issues were addressed: Saving Squeeze value in Cart Recorder {4941} Old-style Hook button graphic {5513} Problems with creating announcers in LB {5184} 51122 (5.1.1.) ------------------------------------------------------------------------------ CORRECTED: The "no sound" bug was not actually corrected in 51117, but in 51122 instead. {5537} FEATURE ADDED: Ability to play Dolby AC2. {????} 51117 (5.1.1.) ------------------------------------------------------------------------------ CORRECTED: Minor corrections made the the text of the EULA. {5916} CHANGES TO EMBEDDED: Live Copy behavior, 'Go' button, No Sound. {5388/5555/5537} 51109 (5.1.1.) ------------------------------------------------------------------------------ BEHAVIOR CHANGED: If Netcatch-A and Netcatch-B are set to the same input device on the Devices page (and Multi-Netcatch is enabled) and a netcatch for input 'B' is scheduled, it will fail to run and issue a red error message to the message area on the screen and write an error the AIR log (even if the 'A' netcatch is not running). This prevents an improperly configured second netcatch from disrupting netcatches scheduled on the first input. (This also allows Netcatch-B to be intentionally set to the same input as Netcatch-A, if necessary, in those situations where Multi-netcatching is activated but not used.) {5998} REPAIRED: If a new Multi-netcatch style DTMF recording was "armed" early in the SKD file and SS32 loaded after that time, the DTMF recording would be successful. However, if a DTMF recording was armed or re-defined after SS32 was running, the DTMF recording would not have input information ('A' or 'B') and would crash to desktop. As of this version, input information is correctly transfered to the recording mechanism. {6017} 51108 (5.1.1.) ------------------------------------------------------------------------------ REPAIRED: DTMF recording has been restored to the Multi-netcatch feature. Two DTMF recording can occur at the same time; however two DTMF recordings of the same type (that is, "NA" thru "NZ") cannot be armed at the same time since the pin numbers would be the same. The DTMF button in the Definitions section of the Real-Time Event page now also lists which recording input ('A' or 'B') each active DTMF event is currently armed on. COSMETIC CHANGE: In the interests of consistancy, references to netcatches are being standardized to the term "netcatch", using that spelling. Eliminated are references to "netcapture", "net-capture", "net-catch" and other variations. 51029 (5.1.1.) ------------------------------------------------------------------------------ REPAIRED: Crosstalk between Netcatch-A and Netcatch-B when both were recording would occasionally cause a garbled message on the status screen. REPAIRED: The "Title" field was tucked underneath the VU meters on the Cart record screen. 51028 (5.1.0.) ------------------------------------------------------------------------------ REPAIRED: The "Title" field was tucked underneath the VU meters on the Cart record screen. 51027 (5.1.1.) ------------------------------------------------------------------------------ REPAIRED: The serial numbers on the "Profile" configuration page were not properly wrapping with in the display area when more than 12 devices were shown. BEHAVIOR CHANGED: On the "Sys Info" configuration page, if ASI adapters of different models are found, more than one model number will be listed instead of listing the model number of just first adapter encountered. REPAIRED: In the multi-netcatch feature, when doing a segment netcatch by closure, the pin numbers in the "end" column were not were not being stored correctly. Also, the number of segments recorded sometimes did not match the number requested. 51025 (5.1.1.) [do not use] ------------------------------------------------------------------------------ BEHAVIOR CHANGED: The End User License Agreement that appears whenever a new version of SS32 is installed has been updated and a scroll bar added to scan though it. {5444} FEATURE ADDED: On the "Consoles" configuration page, on the "Wheatstone" tab, a button ("Sync Time w/SS32") has been added that will send the current SS32 time to the console display. BEHAVIOR CHANGED: When using the standard graphic style, the optional satellite-liner indicator (satellite configuration page) now has a more integrated design. (This feature is documented at build 20606.) NEW FEATURE: It is now possible to record two netcatches at the same time. (This is an extra-cost option and must be activated by Scott Studios; if not properly authorized, the "Devices" page will not show a device for "Netcatch-B" and the "Profile" page will not show "Cap" on the "Authorized Features" list. When "Netcatch-B" is not authorized, the current single netcatch is called 'A'.) The procedure is only slightly different than the current system: o The Netcatches are named "Netcatch-A" and Netcatch-B" regardless of the actual input (recording) device used. On the "Devices" page is where each name is associated with an actual input number. Of course, 'A' and 'B' must be assigned to different inputs. This association allows the underlying recording device number to change, if it needs to, without changing SKD file entries. o When scheduling a netcatch in the SKD file, the desired netcatch name ("A" or "B") is designated in the "Ending" field. If neither an 'A' nor a 'B' is found there, 'A' is assumed so that this feature is backward compatible with the single catch version. As previously, running netcatches can be monitored on the "Real Time Event Table" option page. {4784} 51016 (5.1.0.) ------------------------------------------------------------------------------ REPAIRED: Starting with build 50322, if a revised SKD file for the current day was reloaded and it contained a greater number of events than the SKD file it replaced, the new one would be truncated by that number of events (that is, the events would be missing from the 11pm to 12 mid hour). SS32 was not updating its internal record of how big the SDK file was. A workaround for versions between 50322 and this one is to use Jump and Recue to regain the missing events. As of this version this behavior has been corrected. {5843} 51015 (5.1.1.) ------------------------------------------------------------------------------ REPAIRED: Starting with build 50322, if a revised SKD file for the current day was reloaded and it contained a greater number of events than the SKD file it replaced, the new one would be truncated by that number of events (that is, the events would be missing from the 11pm to 12 mid hour). SS32 was not updating its internal record of how big the SDK file was. A workaround for versions between 50322 and this one is to use Jump and Recue to regain the missing events. As of this version this behavior has been corrected. {5843} 51014 (5.1.1.) ------------------------------------------------------------------------------ EMBEDDED APPLICATIONS brought up to date. {3939} 51013 (5.1.1.) ------------------------------------------------------------------------------ BEHAVIOR CHANGED: Since SS_EVERYWHERE no longer relies on what was known as the "key" value to connect, this number has been removed from the Everywhere page. CORRECTED: The AIR log no longer lists the SEGUE EDITOR as being closed every time the LOG window is closed. {5313} BEHAVIOR CHANGED: On the "Console" page, each console maker has its own tab. Support for the serial port version of Wheatstone has been moved to a "Legacy" tab and has been disabled. (Contact dMarc/Scott Studios Tech Support if it is necessary to use this feature.) On the "Switcher" page, the "Wheatstone" entry has been renamed "WhStone/serial" to differentiate it from the TCP/IP version of Wheatstone support (see below). NEW FEATURE: Support for using a TCP/IP connection to a Wheatstone console has been added. This is activated on the "Wheatstone" tab of the "Console" configuration page by either using "Auto Connect" or "Connect Now". SS32 will treat the console as a switcher. In the "Map Devices to Surface" section, Wheatstone channels can be assocated with SS32 audio devices such that when an ON or OFF switcher command is executed, it will also operate the corresponding Wheatstone channel (Click on the SS32 Device to cycle devices then click on "change" to associate a channel). In the case of a "Preview" or "Listen" ON or OFF command, the channel on the Wheatstone surface that is associated with the SS32 Preview device will go into and out of "Cue" mode. The Wheatstone "Consoles" configuration tab contains these other controls: WHEATSTONE IP ADDRESS: Enter the address of the Wheatstone Surface. Consult the WheatStone documentation on how to change the address of the console, if necessary. The port/socket is hard-coded to 55777 and so does not need to be entered. AUTO CONNECT: Check this box to cause SS32 to attempt a connect upon loading. PROFILE: Once connected, the Profile section will be populated with specifics of the host. HEARTBEAT: This merely increments every 50 seconds or so to comfirm that the "heartbeat" fucntion is working and keeping the connection alive. CONNECT NOW: At any time (even if already connected), this button can be used to attempt a connection. Use this button to manually connect if "Auto Connect" is not used. PROGRAMMABLE BUTTONS: In this section, various tasks can be assigned to the set of "Programmable Buttons" on the Wheatstone surface (they are numbered top row first, then bottom row) including "start next" and Auto/Man button. (Click on the Surface Button to cycle through the button numbers and use "Change Task" to cycle through tasks to assign to that button. Be sure to consult Wheatstone documentation on setting up the Wheatstone options file to use these programmable buttons. VIEW MSGS: For diagnostic purposes, this checkbox can be used to monitor all messages from the host. They will appear at the top of the display area and scroll downward (newest on top). Since there are many "" messages in the stream, these are not displayed but merely increment the counter when they arrive. Note that not all messages are generated by the console--some are generated by SS32 to indicate the status of the connection. It is intentional that the View Msgs checkbox does not stay checked when configuation is exited. SEND BUTTON: For technicians who know the commands the surface responses to and want to troubleshoot, a "Send" button has been provided. Type the command to send in the input box provifed and click send. The "view msgs" checkbox must be checked to see reponses. This is NOT for general use and will probably be removed in future versions. {5455} CHANGED: In anticpation of having additional Netcatches, the existing single netcatch is now referred to as Netcatch 'A' in the configuration pages. In all other respects, the netcatch mechanism operates exactly as it always has. 50xxx (5.1.0.) ------------------------------------------------------------------------------ CHANGED: New icon to replace "highway" theme icon. 50725 (5.1.0.) ------------------------------------------------------------------------------ CORRECTED IN EMBEDDED VT: "Unable to Record" error. {5185} 50722 (5.1.0.) ------------------------------------------------------------------------------ CORRECTED: Distorted (new-style) buttons in embedded LB and VT. {5142}{5144} 50717 (5.1.0.) ------------------------------------------------------------------------------ CORRECTED: When using Named Schedules, if the pin designated to Resume from Rain delay was activated when no actual Rain Delay was in progress, it would cause SS32 to behave as if no Named Schedule was running and no longer react to any inputs related to it. As of this version, Resume-pin activations are ignored if no rain delay is in progress and a message is written to the AIR log instead. {4959} BEHAVIOR CHANGED: When squeezing an audio file that is over 60 seconds (for example), the internal math does not always fall exactly on 60.000 seconds. It may caculate to 59.997 or 60.002 (for example). The "cart label" on the SS32 display truncates (rather than rounding) the length value to whole seconds and thus audio files that were being squeezed to 59.997 would thus appear to be only :59 seconds long (even though they would play for 59.9 seconds). As if this version, a special case for stretched or squeezed files has been made so that files that are 59.500 seconds through 60.499 will show as ":60" (and similar with :30). Non-squeezed files are not changed but, if desired this rounding could be applied to all files or made a config choice so as not to break any previous behaviors. {4943} CORRECTED: SS32 no longer issues "Invalid object" warnings when using the ASI 5111 audio adpaters. {4335} CORRECTED: Grpahics in Cart Recorder and Configuration "setup-1" page. {5023} CORRECTED: Wild Card support in Cart Recorder. {3888} CORRECTED: Slider bar synchronization. {4940} CORRECTED: Rotator Creation Error. {3939} 50707 (5.1.0.) ----------------------------------------------------------------------------- BEHAVIOR CHANGED: The SS32/dmarc splash screen has been updated. It now does not take up the entire desktop while SS32 loads. {5063} 50622 (5.1.0.) ----------------------------------------------------------------------------- FEATURE ADDED: When a file was uploaded via the "inbox" mechanism for a category that had alias names which in turn appeared in the SKD file, those events with the alias names were not being recognized and therefore were not being recued. As of this version of SS32, the original category name plus all known alias names are compared against the twelve-event SKD file buffer. The AIR log lists all alias names that were attempted and how many total matches were found. 50615 (5.1.0.) ----------------------------------------------------------------------------- MAINTENANCE BUILD: Changes to Embedded applications. 50520 (5.1.0.) ----------------------------------------------------------------------------- MAINTENANCE BUILD: Cart Record screen editing. {4836} 50513 (5.1.0.) ----------------------------------------------------------------------------- DIAGNOSTIC ADDED: On the "Demo/Diagnostic" configuration page, a new checkbox called "Log All Inbox Activty" can be activated to do the following: All debug messages generated by the process that promotes audio files out of the Inbox and into the category folder are logged to the AIR file. If SS32 receives a "recue" message, the catcode is listed and the number of catcode matches found in the 12 event on-air buffer is noted in the AIR log. The title and trivia text of each event that is marked for recue is written to the AIR log before that event is recued. After recue, the Title and Trivia are again listed (for all recues, not just those done for the inbox). If a NowPlaying message was successfully sent via TCP/IP, the first 40 characters of that actual NowPlaying message is written to the AIR log [Note: any characters in this raw NowPlay message that are out of printable ascii range are replace by a dot '.']. 50407 (5.1.0.) ----------------------------------------------------------------------------- CORRECTED: Due to a complication in attempting to make the "standard" graphics the default, it was not possible to upgrade directly from versions older than build 50525 (without upgrading to a build between). With this build, SS32 can now upgrade directly from older versions. 50404 (5.1.0.) ----------------------------------------------------------------------------- NEW CONFIGURATION: On the "Database" page, it now possible to configure the event listings to utilize the color of the category it is in. If, for some reason, its category is not listed in the category table, the color will default to the standard fallback color: The color of the second entry. NEW FEATURE: The keystroke combination CTRL-SHIFT-J has been added to the set of keyboard equivalents (when they are active on the System page, Misc section). When pressed, this combination will cause SS32 to execute a "Jump-to-Now and Recue" operation. This is not supported in the Live Mode. NEW FEATURE: On the "Remote" configuration page, it is now possible to assign an input pin (closure) to "Jump+Recue" which will cause SS32 to execute a "Jump-to-Now and Recue" operation, followed by a "Startnext" to put the SKD file on-air (if not already on-air). This is not supported in the Live Mode. BEHAVIOR CHANGED: When using two monitors and the "Disable Touch Screen" option, the second screen displays the same message as appears on the primary monitor. 50329 (5.1.0.) ----------------------------------------------------------------------------- FEATURE ADDED: The ability to use the extra inputs on the 43xx family of ASI adapter cards (see 21017) has been extended to using a hot buttons to turn them on and off. This is done by allowing the toggle type ([T]) hot buttons to use AX event names that have been assocated with the extra inputs on these adapters. Here is how to accomplish the link between hot buttons and the extra inputs: 1. If not already done, establish a unique, four character AX name for each of the inputs that is to be attached to a hot button (as if creating an AX event) in the list of AUX names on the "AUX events" configuration page. 2. If not already done, in the "ASI 4300 Family Additional Inputs" section of the "Misc-2" configureation page, associate the new AX names with each input to be hot-button controlled. (An audio gain level can also be associated with each input in this section). 3. If not already done, establish an entry in the Audio Routing table on the "Audio Routing" configuration page for each AUX name in use. (No other columns need be entered--the AUX name just needs at minimum to be in the Audio Routing Table to 'register' it with the system.) 4. Just like any other "toggle" type hot button, use the special category "[T]" with the desired aux name (e.g. [T]ASI2 ) to form a CATCODE when editing hot buttons for this feature. Note: Only one 43xx adapter (adpater #1) is currently supported in multi-adapter installations. 50325 (5.1.0.) ----------------------------------------------------------------------------- CORRECTED: When returning from a Named Schedule by closure, SS32 uses the time of the closure determine the event that would have been playing had the schedule not been interrupted and then loads and prepares that event for playback. Since syncs are ignored while a Named Schedule is being executed, if a hard sync occurs after the closure but before the original schedule is properly loaded, it will also be ignored. However, this results in a schedule-resume-point that is prior to the hard sync marker instead of being after it, where it should be. As of this version, the last hard sync to occur (and be ignored) during a Named Schedule is re-examined and allowed to execute after the original schedule resumes. In most cases, this hard sync will be too old, not find a proper jump target and thus fail--but sometimes, it will have the effect of "auto correcting" the schedule. IMPROVED: In Live Mode, Standard Graphics, those events that are not playable "carts" are now signified by redesigned (in a more compatible style) blue and black up arrows. NEW CONFIGURATION: In the "Auto Mode" section of the "Misc-1" page, users can now select "red" as the color of the (optional) markings on the six Start buttons that signify that the system is in "man" instead of "Auto". SS32 must be reloaded for this setting to take effect. 50323 (4.9.0.) ----------------------------------------------------------------------------- CORRECTED: In Livemode, Standard graphics, switching to the insert/database screen was causing the non-deck events (up arrows) to disappear. IMPROVED: In LiveMode, Standard graphics, the background of UpArrrow buttons was changed to black. In order to avoid confusion as to which events are "carts" and which are not, the "cover art" feature can no longer be demonstrated in the livemode. 50322 (4.9.0.) ----------------------------------------------------------------------------- CORRECTED: If a schedule-rejoin happened to attach right after an event had gone on-air from a position other than next (the second position) due to, for instance, an event not cued or a link event canceled, it was possible that nearby event would be missing (that is, the re-join process would miscalculate and attach one too soon).. This would usually appeared in the AIR log as "Rejoin(>jmp<<<<)" instead of listing a valid time. (In rarer situations, it was possible to create a extra, duplicated event caused by the same sort of one-off calculation.) As of this version, re-attachments are done using a completely different method. CORRECTED: In the "Standard" graphics mode, when opening any of the embedded applications, the yellow countdown graphic was not properly covering the green "utility" button. CHANGED: The Scottbtn.dll now contains replacement buttons for Play, Stop, Next and Prev in the Segue Editor to have hem look smoother. CHANGED: In "Standard Graphics", live mode, the button that holds open the deck to be filled (red square on grey button) was using the bitmap from the "classic" mode. 50320 (4.9.0.) ----------------------------------------------------------------------------- STANDARD GRAPHICS IMPROVED: Reverse the Sort selection button colors so the selected is gold and non-slected is blue. Plus other misc button cosmetic changes. 50318 (4.9.0.) ----------------------------------------------------------------------------- IMPROVED: Using "standard" graphics, the MoreEvents window was showing a partial "brushed steel" background on the second monitor. BEHAVIOR CHANGED: New Buttons added to Scottbtn.dll. 50316 (4.9.0.) ----------------------------------------------------------------------------- GRAPHIC CHANGES: In the "standard" version of the graphics, the "brushed steel" background has been placed behind the Options Page and the Option selection rectangles have been replaced with bitmap buttons. The brushed steel background as alo been added to the following screens: Named Schedules Jump and Recue page More Events/log Everywhere page Real Time page Hot Page Select This change requires a new Scottbtn.DLL (included in the zip package) and SS32 will display and log an error if the proper version cannot be found (but will still run). 50315 (4.9.0.) ----------------------------------------------------------------------------- IN-HOUSE CHANGES 50312 (4.9.0.) ----------------------------------------------------------------------------- BEHAVIOR CHANGED: It is not longer necessary to select a font style on the "System" page to match the style of screen graphics. It is now done automatically. The correct font for the "Standard" style screen is now located in the lastest version of the Scottbtn.DLL and if this font cannot be found, the most closely-matching Windows font will be chosen and a message will appear in the AIR file. (As a diagnostic tool only, an "UnLoad" button has been provided to remove this font from Windows.) 50225 (4.9.0.) ----------------------------------------------------------------------------- NEW FEATURE: SS32 now has new screen graphics (known as "standard"). Users who prefer the "Classic" style can switch back on the "System" page, if desired. NEW FEATURE: SS32 now has a new version-number system. Current versions of SS32 are in the form "5.1.0.[build]" where [build] indicates a particular variation of that release. BEHAVIOR CHANGED: The inital "splash" screen (and the "Disabled TouchScreen" panel) has been redesigned to incorporate the new version format. 50207 ----------------------------------------------------------------------------- NEW FEATURE: Support for the 6044 AudsioScience Audio Adapter, allowing the use of four inputs on each card. 50204 ----------------------------------------------------------------------------- CHANGES MADE TO EMBEDDED APPLICATIONS 50201 ----------------------------------------------------------------------------- CHANGES MADE TO EMBEDDED APPLICATIONS 50131 ----------------------------------------------------------------------------- BEHAVIOR CHANGED: The first time SS32 accessed a drive that was located on a network (i.e. non-local drive), it triggered a routine that drove CPU usage up to 90-100% continuously. This can be observed in versions somewhere after 40917. As of this version, CPU usage is back to normal. BEHAVIOR CHANGED: A recent change caused (legacy) 4501 adapters to generate a "101 Invalid Object Type" error that had to be cleared when SS32 was loaded. CORRECTED: When the checkbox to activate the DoubleDisk feature was recently moved from the "Setup" page to the "System" page, it reappeared (in some versions) back on the "Setup" page as well. In those rare versions where the checkbox appears on both pages, the one on "Setup" does not do anything. As of this version, the DoubleDisk checkbox is only on the "System" page. 50120 ----------------------------------------------------------------------------- FEATURE ADDED: This version supplies the support for SS_EVERYWHERE to use the "Menu"-type buttons added in version 41208. (Be sure this version is paired with an SS_EVERYWHERE that also supports "menu" buttons to use the feature.) BEHAVIOR CHANGED: The ability of the "Jump and Recue" screen to parse very short "title" and "code" fields that are encountered in the SKD file has been improved. CORRECTED: The duplicate checkbox for "Double Disk" on the Setup page have been removed. ENCHANCED: Named Schedules (.ALT files) that had as the last event an AX or AT event would return to the main schedule at the departure point rather than jumping to the current time of day. (Named Schedules with digital audio events last would behave as expected--as would the "end on pin" option.) As of this version, Named Schedules ending in audio events, AX events or AT events perform the jump to the current time of day. (The workaround for SS32 versions previous to this is to ensure that Named Schedules that are expected to play through to the end have as the last event a digital audio event.) *** this file has been truncated to show only changes made from 2005 on ***