Burli Newsroom Release Notes

Please contact support@burli.com for the latest version and upgrade instructions

Burli Web Server RSS links fix

In Burli 234q, we have fixed an issue with the RSS links in the Burli Web Server. They are now showing correct XML content.

Dispatching to Burli ‘NewsHub’ now supported

Starting in 234o user can dispatch text+plus audio stories to Burli NewsHub. Please contact support@burli.com for more information.

FEATURE: Date/Time stamp in the Display Name of RCS.INI Cart Chunks

Starting in version 234n, we have added the ability to include Date/Time stamps to the Friendly names in the Cart Chunk of RCS.INI (Genesys). This feature is only available if you are using CartChunk=Genesys in your RCS.INI. This lets the users in the control room easily see when the audio was sent from Burli to the automation system,

 

Example setting:

 

[Group1]

HideTitle=Yes

DefaultParams=channels=mono&CartChunk=Genesys

Cart1=News Bully for TEST FM [Time/Date Variables],12345, minlength=59&maxlength=61&Expiry=12&Next=57

 

For example:

Cart1=News Bully for TEST FM %I:%M%p,12345, minlength=59&maxlength=61&Expiry=12&Next=57

 

The output of for the Friendly Name in this example will be “News Bully for TEST FM 4:20pm”

Syntax for the Date/Time time variables:

https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/strftime-wcsftime-strftime-l-wcsftime-l?view=vs-2017

 

Edited Podcasts now show the correct duration

Starting in version 234m, we have fixed an issue that would give the incorrect duration to any Podcasts where the audio was edited in the Work folder before being sent. This is now working correctly.

Improvements made to prevent web server crash from consecutive searches

Changes applied in in build 234L

Audio ingest setting changes

Starting in Burli 234k, we have changed the default settings for ingesting from multiple audio sources (AUDIPT 1-8). Previous to this version, if you wanted to have each of your AUDIPT newswires to go into their own Filters, you would need to turn on the following setting in MAIN.INI:

 

[Startup]

NewAudioFilterMethod=Yes

 

This is now Yes by default

 

You can still add that setting and to turn that setting to No if you have more than one AUDIPT and require all of them to go into one Filter.

FEATURE: Multi select/delete in the Archive

Starting in Burli 234j, we have not made it possible to select more than one Archive story at a time. Previous to this version, it was only possible to select one story at a time from the Archive.

Burli crash after changing a Logger Session sample rate

Starting in Burli 234i, we have fixed an issue when changing an existing recording session sample rate, the changes were saved to the database but would cause Burli to crash. This is now working correctly.

Apple QuickTime support has ended

As Apple no longer supports QuickTime in Windows platforms, we have now deprecated this support in 264h . FFMpeg is being used instead for conversion of all media files.

FEATURE: Hourly backups of the local Work Folder

Starting in version 234g, we have added a backup mechanism for the local Work folder.

Burli will now automatically backup the local Work folder index file every hour to the local C:\Burli\Logs folder and named "_workB_YYYYmmdd_HHMM.zip".

To restore the Work folder from a backup, open the appropriate Zip file and go to  Burli -> Local. Rename or delete the corrupt _workB.rdf file in C:\Burli\Local and copy the one from the backup to the folder.

After restarting Burli, you should see all of the content in the Work folder again.

Open External Audio files removes all Upper Case letters

Starting in version 234f we have fixed an issue where the titles of media files imported via Open > External Files would all be in lower case. This is now working correctly. Upper and lower case titles are already imported correctly with drag and drop to the Work folder.

FEATURE: Emailed video attachments audio extraction

Starting in Burli 234e, we now will keep all emails video clips as attachments as well as convert them to audio. The attachments can be accessed by clicking on the paperclip icon in the top left of each email. Please make sure that you have all video extensions listed in the [NonAudioEmailAttachments] section of MAIN.INI.

FTP Path and Port information is not saved for an Anonymous user

Starting in Burli 234e, we have fixed an issue when using an Anonymous user in a Newswire configuration. From version 228a – 234d, when settings the Anonymous user for the FTP ingest, the File Path and Port was not saved. This is now working correctly.

Fix VN port warning when it is disabled

Starting in Burli 234e, we have fixed a warning message about conflicting ports when the feature is not enabled. This is now working correctly.

High CPU Usage for Burli

Starting in Burli 234d, we have fixed an issue that would cause Burli to use more than the normal amount of CPU; sometimes over 50%. In this version, the CPU usage should rest below 10% when it is not ingesting new stories or doing any file cleanup.

FEATURE: Secure HTTPS support for the Burli Web Server

Starting in Burli 234c, we now support SSL (https) for the Burli Web Server. Please contact support@burli.com for more information.  

FEATURE: EOM setting for OMT (iMedia Touch) Dispatch

Starting in Burli 234a, you can now set an EOM on all carts being set to iMediaTouch (OMT). This is also called the “SEG” in some applications. The setting applies to all carts being sent to iMediaTouch and the new setting is as follows:

 

In OMT.INI, you will create a new section near the top of your OMT.INI with the following:

 

[General]

EOM=####

 

Where #### is a value in milliseconds from the end of the cart.

 

Example:

 

[General]

EOM=300

 

This would place an EOM marker 300 milliseconds from the end of each cart. Burli will write this information to the Cart Chunk to be read by iMediaTouch.

Script/Prompter formatting issues with Chinese characters

Starting in Burli Unicode 233z, we have fixed an issue when displaying Chinese characters in the Prompter which includes spaces and tabs. In previous versions, extra spaces were being shown in Prompter mode. This is now working correctly.

Archive display improvement

Starting in Burli 233y, we have improved the Archive window and now display the full Month/Day/Year. In previous versions, the year may be cut off depending on the font being used.

Support https for Update via Internet

Starting in build build 233y-HL/233y-U we now support https for Update via Internet

Sluggishness when switching tabs in Burli Unicode

Starting in Burli 233x, we have fixed an issue seen with Burli Unicode when switching between Script tabs and the Work folder. This was due to logs being turned on and saving the files in Unicode format. We now save the files in UTF-8 and performance is very good.

FEATURE: Support https for Update via Internet

Starting in Burli 233x, we now support HTTPS for Burli HASP license updates.

Drag and Drop audio links to a Work folder from HTTPS websites

Starting in Burli 233u, we have fixed an issue introduced with Burli 233s which added the ability to Drag and Drop web audio links into the local Work folder from HTTPS websites. Previous to this version, only audio links from HTTP websites could be dragged and dropped.

Plain Text emails missing text

Starting in Burli 233t, we have fixed a bug where Plain Text emails were missing text. This would only be seen when Plain Text emails which include a line with a single dot. This is now working correctly.

POP3 email server connections

Starting in Burli 233s, we have fixed connection issues with POP3 email servers. Previous to this version, you would have to add “pop3://” to the server configuration. This is no longer required for POP3.

Drag and Drop audio links to a Work folder from HTTPS websites

Starting in Burli 233s, we have added the ability to Drag and Drop web audio links into the local Work folder from HTTPS websites. Previous to this version, only audio links from HTTP websites could be dragged and dropped.

FEATURE: Mark all emails from one or more email accounts as Urgent on the ticker

Starting in Burli 233r, we have added the ability to mark all emails from one or more email accounts as Urgent on the ticker. In the email account setting field(s), the appended "?urgent" which indicates "Urgent" flag is turned on for that account.

 

For example:

abc@gmail.com@pop3s://pop.gmail.com?urgent

FEATURE: Support for QGoLive mobile uploads

Starting in Burli 233q, we support the QGoLive mobile uploads application. Burli 233q and Newswires 2.65 is required for this feature. You will see the QGoLive Newswire in the Newswires2 tab. When creating a Filter for this, please use the one called “Wire:QGoLive”.

Fix for the Twitter window

We have fixed an small issue with the accounts displayed when sending a Tweet and you have more than one account. This is now showing the accounts correctly starting in 233m

Dragging a Stereo file form a Remote Location does not respect the KeepStereoImport setting

We have fixed an issue when dragging Stereo files from a Remote location not respecting the KeepStereoImport=Yes setting and converts the file to Mono if that is the local audio format. Starting in Burli 233k, the file stereo file can be dragged to the local Work Folder and the user will be asked it they want to keep the file in Stereo.

FEATURE: Ability to ingest audio from .MXF files

Starting in Burli 233k, we have added the ability to ingest .MXF (Material Exchange Format) and rip the audio from them. Libmedia 3.9 is also required for this feature.

Dispatched stories to remote sites do not retain Category and Priority information

Starting in Burli 233h, we have fixed an issue when sending stories to remote VN locations where the category and priority information was not included. This is now working correctly.

Enable the CdArchiveAudio (SQL) feature for Optimized Archives

Starting in Burli 233f, we now allow users with Optimized Archived to send audio to offline storage. (CTRL-F6 -> cdarchiveaudio) Previous to this version, this feature only worked non-Optimized archives.

FEATURE: Scheduled Tweets

Starting in Burli 233f, you can now schedule Tweets from any workstation. It lets the users create a Tweet and then schedule a date and time for it to be sent out. There is also a management screen to allow users to see which Tweets are being sent out and when. Tweets that are no longer valid can also be removed. Once a Tweet has been sent, the user will be notified via a popup on any workstation that they log into.

 

This feature requires a valid Twitter account registered in Burli and a MySQL or MSSQL Burli database. The following MAIN.INI setting is also required:

 

[Twitter]

ScheduleServer=[computer hostname]

 

By default, it's blank, which means the feature is turned off.

 

Every Burli workstation can create/view/delete the scheduled Tweets but only the server machine can send the scheduled Tweet to twitter.com. Once it's sent out, the user that sent the Tweet will receive a notice. The interval time for checking the status of scheduled tweet is 10 seconds for both server machine and client machine.

 

To send a Scheduled Tweet, open a new Tweet (CTRL+Shift+T or Right-Click on some text in the Work Folder) and click on the Schedule button.

 

You will then be asked to enter the Time and Date that you want the Tweet to be sent.

 

Click on Confirm when you have set the correct Time and Date.

 

You will be shown a confirmation widow showing the Tweet will be sent and when.

 

When the Tweet has been sent, you will see a popup message to confirm. Once you click OK, the Scheduled Tweet will be removed from your schedule.

 

If you would like to see all scheduled Tweets, simply open a new Tweet (CTRL+Shift+T or Right-Click on some text in the Work Folder) and click on the Manage button.

 

You will then be shown all scheduled Tweets. On this screen you can see who sent the Tweet, the contents of the Tweet and when the Tweet is scheduled to be sent.

 

If you choose to Delete a Scheduled Tweet, you will be shown a confirmation window.

Files sent via Burli Web Server cut off

Starting in Burli 233f, we have added a new setting to MAIN.INI which will allow Burli to compensate for poorly formed audio files which would otherwise get chopped off prematurely when submitted via the Web Server or even Drag and Drop or Open External.

 

The new setting is as follows:

 

[Startup]

FFmpegMp3DurationExtra={n}

 

Where n should be an integer ranging from -100 to 100. The default is 5, which means 5% more audio duration than what libFFMpeg APIs detect. This flexibility gives our users a solution in some extreme cases where their original mp3 file contains wrong/incorrect/corrupted file header information.

 

CAP and CEP Newswires are not working in Burli Unicode

Starting in Burli 233d, we have corrected an issue with added blank spaces when ingesting the CAP Newswire in Newswires 1. This fix also requires Newswires-2-61.zip.

 

Unable to send items to the Archive

We have fixed an issue with being able to send items to the Archive with Burli Unicode. This was due to the user setting for “Language for non-Unicode programs” set to anything else but English. This is now working with MSSQL Driver version 4.4.

FEATURE: Support for a second Report-IT newswire

Starting in Burli 233b, we have added an additional TieLine Report-IT newswire for customers that need to monitor more than one source. This feature also requires Newswires 2.60 minimum. You will find the second Report-IT newswire in the Newswires 2 tab listed as “Report-IT-2”. When creating a filter for this newswire, be sure to pick “Report-IT 2” as the Source.

Fix for the Twitter Home Timeline retrieval

Starting in Burli 233a, we have fixed an issue with ingesting the Twitter Home Timeline (https://api.twitter.com/1.1/statuses/home_timeline.json). This is now working correctly.

Fix for capturing CAP and CEP Newswires

Starting in Burli Unicode 232z, we have fixed an issue with capturing CAP and CEP Newswires. This is now working correctly with this latest version.

Slow insert into Archive DB with a large table

Starting in Burli 232x, we have fixed an issue with slowness experienced when dispatching to the Archive once it has reached a large size. This issue was seen with large a 1.3 GB Optimized Archive. With this new version, the new items will be saved to the Archive in under a second.

When dispatching to the Internal Newswire, the categories do not show up in the correct order

Starting in Burli 232w, we have fixed a display issue when dispatching Internal Newswire stories. Before this version, the categories would be sorted alphabetically. Starting with this version, the categories will be displayed in the order that they are set up in POST.INI.

FEATURE: Hide Security tab in set up screen

Starting in Burli 232v, we have added the ability to give users access to the Config -> Program Setup area without showing the Security tab. To do this, we have added an additional setting to MAIN.INI where you can specify one password for Administrators and one without the Security tab for Users. The setting is:

 

[Passwords]

setup=[AdministratorPassword],[UserPassword]

 

where,

if AdministratorPassword is "*NOPASSWORD*", then any input password is treated as admin password.

 

if AdministratorPassword is blank, then admin password is "radio".

 

if the user input matches the [UserPassword], the Security tab window is hidden.

 

[UserPassword] is case insensitive.

[AdministratorPassword] should be lower case, except "*NOPASSWORD*".

 

Note, if you roll back to previous Burli.exe, make sure you delete the [UserPassword] and preceding comma.

FEATURE: Ability to show all Network/Aliased folders when there are too many to show on one screen

Starting in Burli 232u, we have added the ability to show and open Network, Aliased or Local Folders if there are too many folders to show on one screen. When you go to Open a Folder in Burli, you will now be shown the option to Show all.. which will open a popup displaying every folder in a scrollable list.

 

There are MAIN.INI settings to control how this window appears and how many folders to show before the Show all.. option.

 

[Startup]

FolderListMenu=XX,YY

 

XX is the number of items to show in the Open > Network > Aliased > Local Folders before the Show All..  option is shown. The default is 100 Folders.

YY is the number of Columns to display. The default is 4 Columns.

 

When you go to Open a Folder, the last item in the list is Show all…

 

Click on this and you will be shown a new window with every folder displayed. There will be side and bottom scroll bars if the list is longer or wider than the window.

 

You then just need to click on the Folder that you want to open.

FEATURE: Ability to Drag and Drop text to existing stories

Staring in Burli 232s, you are now able to drag and drop text into existing stories. Simply highlight any text from the top edit window or from another application and drag and drop it into the story location in the Work Area. The Undo and CTRL-Z function will undo any changes that you have made.

Fix for tab Text Import loop

Starting in Burli 232q, we have fixed an issue where stories from a Text Import (TXTIPT in Newswires 2) repeats the stories. This issue affected Burli 232o and 232p. This is now working properly.

Fix for tab focus when right-clicking

Starting in Burli 232p, we have fixed an issue when a user right-clicks on a tab to close it or any other action but the focus is still on the last used tab. Burli will now switch focus to the tab that is being right-clicked.

Fix for moving Script Tabs

Starting in Burli 232o, we have fixed an issue with Script tabs jumping out of order. This was seen when so many tabs were loaded that they went off to the right where some were hidden. This issue is now fixed.

Network folder recycle bin `Error renaming file' error

Starting in Burli 232n, we have fixed an issue when trying to delete an item from a Network Folder.

FEATURE: Podcast Duration tag

Starting in Burli 232n, we now populate the Duration field for Podcasts. This is done automatically so no user input is required. This requires Version 3.5 of the PHP scripts.

FEATURE: Allow for special characters in Author, Title and Description fields

Starting in Burli 232m, we now allow for special characters to be used in the Author, Title and Description Podcast fields.

Fix for MSSQL converted data and Podcasting

Starting in Burli 232L and PHP Scripts 3.2, we have fixed an issue when using MySQL to MSSQL converted data and Podcasts. You would see and error when submitting a new Podcast. FTPUPLOAD.PHP would also show an error which is fixed in PHP 3.2 Scripts.

Fix for Capture of FTP based newswires stopping

We have made a change in Burli 232k to store all temporary data in the local C:\Burli\Temp folder which will be cleaned up once Burli has finished using them. Previous to this version, we would use the Windows Temp folder where Burli did not always have sufficient rights to delete the old files.

Fix for AP PrimeCuts

Starting in Burli 232j, we have resolved an issue with AP PrimeCuts where stories arrive with no audio attachments. This fix also requires Newswires 2.56.zip.

Fix for Web Server when using [ and ] as the characters for TimingExcludeStart and TimingExcludeStop

Starting in Burli 232i, we have fixed an issue when using [ and ] as the characters for TimingExcludeStart and TimingExcludeStop in MAIN.INI. The Burli Web Server would crash when a user was viewing Scripts via the Burli Web Server. This affected versions 231p-232h and is now working correctly.

FEATURE: HTML5 for audio links in Burli Web Server

Starting in Burli 232h, we have added HTML5 audio links in the Burli Web Server. This allows for the Web Browser to play the audio links without the need to install plugins or download the file first. User will now see a play and pause button with level controls for each audio clip included in a story:

 

Depending on the Browser being used, the display will look slightly different. To download one of the clips, you just need to Right-Click on the audio control panel and select “Save as”.

 

We have made it possible to disable the HTML5 audio links. This will revert all audio links to the older HTML audio links which still work the same way that they did in the past. To disable the HTML5 Audio Links, the following MAIN.INI setting is required:

 

[Startup]

HTML5AudioControl=[Yes/No]

 

Default is Yes

FEATURE: Support for 280-character Tweets

Starting in Burli 232f, we now display all 280-character Tweets. No changes are required in configuration for this. You will see all of the Twitter feeds download again when you first launch this new version.

FEATURE: Support for AFP English and French NewsML 1.2 newswire

Starting in Burli 232f, we now support the AFP French (ID#99) and English (ID#184) News ML 1.2 formatted newswire. Newswires 2.55 is also required for this support. The newswires can be found in the Newswires2 tab as “AFP-EN” and AFP-FR”. When creating Filters for these newswires, the Source field should be “Wire: AFP(English NewsML1.2)” and “Wire:AFP(French NewsML1.2)”. There is a required SchemeLookup for these newswires in MAIN.INI:

 

[Newswires]

SchemeLookup##=184,15

SchemeLookup##=99,15

 

Where ## is the next number in the list.

Unicode compatibility for MSSQL database users

Starting in Burli 232c, we have added compatibility for Unicode characters in the MSSQL database. This version also requires Version 4 of the MSSQL driver only if the database is using the "nvarchar" string type rather "varchar". If the database does not use the "nvarchar" string type, the older version of MSSQL drivers (Version 3) are required.

FEATURE: Support for MetroSource Newswire

Starting in Burli 232b, we use libmedia.dll to determine the audio clip properties for clips included with MetroSource newswire stories. This has been done to prevent any issues if any mislabelled clips arrive with a story.

Windows permissions sometimes prevents libmysql.dll from being copied to the workstation

Starting in Burli 232a, Burli will now copy the required MySQL DLLs to the local C:\Burli\Drivers\Database folder on launch. Previous to this version, Burli would try to copy libmysql.dll to the C:\Windows\System32 or C:\Windows\SysWOW64 folder. This location is sometimes restricted from users so the file would not get copied and then see a failure loading the MySQL drivers.

 

FEATURE: HTML5 for audio links in Burli Web Server

Starting in Burli 232a, we have added HTML5 audio links in the Burli Web Server. This allows for the Web Browser to play the audio links without the need to install plugins or download the file first. User will now see a play and pause button with level controls for each audio clip included in a story:

 

Depending on the Browser being used, the display will look slightly different. To download one of the clips, you just need to Right-Click on the audio control panel and select “Save as”.

Backup Newswire Server cannot be selected with ExportAlways=No (default)

Starting in Burli 231z, we have fixed an issue which would not allow you to select your backup Newswire Server if you do not have the ExportAlways=Yes option turned on. This is now worked as it should.

Fix for crash when closing Scripts

Starting in Burli 231z, we have improved the process when closing multiple Scripts. In some cases, Burli would crash when closing one large Script or multiple Scripts. This is now working correctly.

Added new Ctrl+F6 command to show the loaded version of MySQL DLL

Starting in Burli 231y, we have added a new CTRL-F6 command which will show the version of MySQL which is currently loaded. The new CTRL-F6 command is “libmysql” (no quotes) which will display the current version.

Fix for returning from CTRL-E  Edit/Prompter Mode

Starting in Burli 231x, we have fixed an issue when using CTRL-E to go to half screen Prompter mode. Now CTRL-E will again return you to Edit mode from Prompter. Versions 231s-231w were affected.

Improvement for MySQL driver handling

Starting in Burli 231w, we have changed the location for storing MySQL drivers on workstations to prevent issues with user rights. Previous to this version, on first launch, Burli would try to copy libmysql.dll to C:\Windows\System32 or C:\Windows\SysWOW64 which would not always be allowed. As all users do not always have rights to copy files to the C:\Windows folder, Burli will now copy libmysql.dll to the C:\Burli\Drivers\Database folder (or Local Root Path\Drivers\Database\). All users should have sufficient rights to this location and so the file should be copied successfully from now on.

Fix for Sending Tweets

Starting in Burli 231v, we have fixed an issue that would not allow you to send a Tweet with less that 140 characters. This is now working correctly.

FEATURE: Support for the AP PrimeCuts ATOM feed

Burli will retain the category code from the source; if it matches the any of the Internal Newswire category codes it will use that instead of respecting the DEFAULT Internal Newswire category code. This is fixed in 231u. This requires a new main.ini setting for turning on/off this behavior. [Startup] IgnoreOriginalCatPriPostBIN=Yes Where the default is No. This setting affects both "Export as Internal Newswire..." and "Export to BIN with attachment ..."

LocalFolderTiming=Yes | Total time not updating

We found a bug since version 230t which is related to the main.ini setting "VideoTiming" and this feature. If that is Yes, any story text enclosed by ".{" and "}" is not saved to the RDF file. This is fixed in 231t.

Web browser retains old URL when navigating to the Home page

When browsing any site other than the Home site specified in the Web browser, clicking the Home button does indeed take you home, but leaves the URL of the site you had been previously looking at.  This is fixed in 231t.

BUG: Certain MP3 files can crash Burli

Starting in Burli 231s, we fixed an issue where certain MP3 files can cause Burli to crash.

FEATURE: Manual or automatic refresh of an FTP Folder improved

Starting in Burli 231r, we have improved on the FTP refresh feature. With the new version, the FTP tab will not be automatically refreshed unless the user has selected the FTP tab.

We have also improved the refresh behaviour to keep the current sort order.

 

FEATURE: Ability for users to sort tabs by sliding left or right

Starting in Burli 231q, users are now able to slide tabs left or right in the Work Area for easier organization. Simply left-click on a tab and slide it left or right.

The Work tab cannot be moved.

 

FEATURE: Manual or automatic refresh of an FTP Folder

Starting in Burli 231p, you can now either manually or automatically refresh the contents of an FTP Folder. To manually refresh a folder, simply Right-Click on the folder and choose “Refresh”.

To enable automatic refresh, a MAIN.INI setting is required: [FTP] ftpTabRefresh=##

Where ## is a value in Seconds.

By default, this value is 0 which means manual refresh Example: [FTP] ftpTabRefresh=60 This will automatically refresh the FTP folder every 60 seconds.

 

FEATURE: Support for the AP PrimeCuts ATOM feed

Starting in Burli 231o, we now support the Associated Press PrimeCuts service via their ATOM feed delivery method since the AP PrimeServer service will be discontinued around the end of 2017. Newswires.zip version 2.52 is also required for this new method. The following account settings should be added into MAIN.INI:

 

[Newswires]

RSSAuthentication#=207,1~Username~Password

 

Where # is the next number in the list and Username and Password are your Associated Press Username and Password.

 

Once you have added this setting, restart Burli and go to Config -> Program Setup -> Newswires2 and scroll down to “AP PrimeCuts Atom Feed”. Click Install and enter AP PrimeCuts in the name field, set the Refresh Rate to 5 minutes (or less) and then enter the following URL in the URL field:

 

http://syndication.ap.org/AP.Distro.Feed/GetFeed.aspx?idList=38325&idListType=products

 

Click Add and then OK.

 

The first check may take up to one minute before stories start to enter the InQueue. Your existing AP PrimeCuts Filters will work with this new delivery method.

 

Story Slugs being cut off

Starting in Burli 231o, we are now keeping story slugs intact u to 250 characters. Previous to this version, if you had a small read window when you are editing a story and the Slug needs to wrap, Burli was creating the story with only the first line of the Slug. This is now working correctly.

 

Audio upload fails if there is a UNC path above the FTP site that you are sending to

Starting in Burli 231o, we have resolved an issue with AudioUpload.ini. previous to this version, if you had a UNC path location preceding an FTP location, the FTP destination would fail. This is now working correctly.

 

FEATURE: Twitter now allows for 280 characters per Tweet

Starting in Burli 231n, we now allow for 280 characters per Tweet up from the previous 140 character limit.

 

Script timing not updated on other Burli clients when Story removed

Starting in Burli 231m, we have fixed an issue with Script Timing not updating. If you have a Section Break at the top of a newscast and second user removes the last story from the newscast, the first user will not see the timing updated. This is now working as expected.

 

FEATURE: Publish to WordPress

Starting in Burli 231L, you are now able to publish to WordPress. This is for Text only at this point. The user can simply Right-Click on the Slug of a story and select Send to WordPress. The user can then choose the account that they want to publish to. You will then be shown the content in a window which can be edited before sending. To enable this feature, you will need to add the following settings to MAIN.INI:

 

[Wordpress]

Account=wp~Wordpress user account

 

or

 

[Wordpress]

Account1=wp1~Wordpress user account1

Account2=wp2~Wordpress user account2

 

At this point, only text is supported. Supporting other media will be done in the near future.

 

For Self-Hosted WordPress websites, please use the following syntax:

 

[Wordpress]

Account=Friendly name~user name[optional]~password[optional]~selected[optional]~http(s)://your.self.hosted.url:port[optional]

 

The default value of the web site is public-api.wordpress.com

 

FEATURE: Drag and Drop audio to insert

Starting in Burli 231k, you are now able to drag and a drop segment of audio from the top window and insert it into the bottom Single Track editor. You will however, lose the Undo chain from your project on the bottom and Burli will confirm that you want to do so.

FEATURE: Full Screen Prompter button

Starting in Burli 231k, users can now enter Full Screen Prompter with a larger Prompter Font by simply hold the CTRL key when they click the On-Air Button. To exit the Full Screen Prompter, simply press the ESC key. This will return you to Edit Mode with the Default Font.

Full Screen Prompter mode can also be entered with CTRL-F12 and back to Edit mode with CTRL-F11 as before.

 

FEATURE: Menu item to Save Pane Positions

Starting in Burli 231j, users can now save their Burli pane positions with FEATURE: Menu item to save the pane positions Config -> Save current window layout. This will store the current window layout to the local registry so Burli will always show the current layout when it is started.

FEATURE: Increase window size for Dispatch

Starting with Burli 231j, we have increased the size of the Dispatch window to allow for longer dispatch destination names.

 

MP3 files being cut off with FFMPEG=Yes

Starting in Burli 231j, we have fixed an issue with some MP3 files which have the last second or two being cut off. This was due to incorrect length information being stored in the MP3 file. We have made allowances to our ingest to estimate the file as slightly longer when Burli sees this kind of file.

 

Slug characters are cut off if it is too long

Starting in Burli 231i, we have increased the maximum length of Slugs which are submitted via the Burli Web Server. This would result in cut off characters if the Slug was too long. In the case of Chinese characters, the limit would be around 25 characters due to “double Byte” encoding. The previous length was 50 characters which has now been increased to 300.

 

FEATURE: Full Screen Prompter button

Starting in Burli 231i, we have made it easier for users to go to Full Screen Prompter and added a default Prompter font. When a user goes to Full Screen Prompter mode, the Prompter Font will automatically be selected. All Burli workstations will now have the “Default Font CTRL-F11” and “Prompter Font CTRL-F12”.

 

These can be edited on each workstation in Config -> Program Setup -> Fonts. Normally, only the Edit font needs to be adjusted if required.

 

Once a user has opened a Script and is ready to go On-Air, they simply hold CTRL and press the “On-Air Mode” button.

 

This puts Burli into Full Screen Prompter mode with the Prompter Font selected

 

A user can also go to this Full Screen Prompter mode by pressing CTRL-F12

 

Once the user has finished reading the Script, to return to regular Edit mode, they simply press the ESC key. This will return Burli to the editing mode and the Default Font will automatically be selected. A user can also get beck to Edit Mode by pressing CTRL-F11.

 

The regular half screen Prompter is still available by clicking the “On-Air Mode” button as per usual.

 

Web Server search with “Include Body” causes Burli Web Server to crash

Starting with Burli 231h, we have fixed an issue when in some cases, searching with the option to “include body” would cause Burli on the Web Server to crash. This was due to a built in timeout of 15 seconds so if your InQueue buffer was very large or the PC which hosts the Web Server was not so fast, the 15 seconds time out was reached and Burli would crash. To prevent this, we have added a MAIN.INI setting to allow you to increase the timeout.

 

The setting is as follows:

 

[Startup]

WebSearchTimeout=##

 

Where ## is in seconds. The default without this setting is 15 seconds. In a slow network environment, this value should be increased to 30 seconds or more.

Urgent story appears as a regular story in the InQueue

Starting with Burli 231h, we have fixed an issue where an urgent story which is posted to the InQueue would flash in the ticker but look like a regular story in the InQueue. The correct Urgent icon is now posted to the InQueue.

 

Improved contacts import functions from CSV files

Starting with Burli 231g, we have increased the number of columns and buffer size when importing contacts from a CSV file. The new limit is now 100 columns and 10,000 characters per record.

Fixed crash caused by pressing Ctrl+Enter

Starting with Burli 231e, we fixed a crash when pressing the Ctrl+Enter keyboard combination.

Client application crash when Sending story to a Remote Site via the Dispatch menu

Starting with Burli 231d, we fixed a client application crash when sending a story to a Remote Site via the Dispatch menu.

Sending story to a Remote Site via the Dispatch menu caused Burli Web Server crash

Starting with Burli 231c, we have fixed an issue when sending a story to a Remote Site via the Dispatch menu would crash the Burli Web server at the Remote Site. This issue affected versions 230n-231b only although the Drag and Drop method would still work fine. This issue is now resolved.

Support for ADPCM audio files

Starting with LibMedia 3.8, we now support ADPCM encoded files. This file should be renamed to “libmedia.dll” and copied to your Burli Server in ~\Burli\Settings\Media folder.

Crash on audio import

Starting with Burli 231a, we have fixed an issue when importing Stereo audio files to a newsroom that uses Mono as their default audio setting. This fix requires libMedia.dll to be used and should be on the Burli file server in ~\Burli\Settings\Media and should be called “libMedia.dll”.

Improvement to the Prepend/Append option when dragging items

Starting in Burli 230y, we have improved the Prepend/Append option when dragging multiple items to a Script. Burli will now place all items correctly depending on your workstation setting. Previous to this version, dragging and dropping a single story would be correct but multiple stories would not always go to the correct position.

Feature: Display the Story Count for Scripts

Starting in Burli 230x, we now show the Story Count of any Script by Right-Clicking on the Script’s tab. This Story Count does not include any Section Breaks.

Multi-track playback issue

Starting in Burli 230x, we have fixed an issue with Multi-track playback which would result in choppy audio. This affected versions 230v-230w only.

Use the local Time zone information and time in Internal Newswire XML file headers

Starting in Burli 230t, we now use the local time and time zone information when creating the XML header for Internal Newswire stories. Previous to this version, we always wrote GMT time and the GMT time zone in the XML headers.

FEATURE: DropOnInHouseFilter option for VN

Starting in Burli 230t, you are now able to drag and drop a story to a Remote VN In-House category and Burli will select the correct Category based on the Filter or Sub-Filter where the story was dropped. Pervious to this version, the user would have to manually choose the Category.

Fix for LocalStoryTIming

Starting in Burli 230t, when you mix down a multi-track project and then import an audio clip, the time of the imported clip is correct. Previous to this version, after you do a mix down and import an audio clip, the audio clip would show as the same length as the mixed down project. To show the length of stories and clips in the Work Folder, you must have LocalFolderTiming=Yes in the [Startup] section of Main.ini.

Web Server crashes when user plays an audio clip

Starting in Burli 230s, we have fixed an issue with the Burli Web Server. When a user would click to play a piece of audio via the Burli Web interface, the Burli Web Server would crash. This issue affected versions 230n-230r.

Fix for section break timing display

Starting in Burli 230s, we have fixed a display issue with Section Breaks not showing the time correctly if you had a font size or character set that would not fit. We have expanded the size of the columns for the Time so it will now show correctly.

Export To menu not displaying correctly

Starting in Burli 230r, we have fixed an issue with the “Export to” menu which was not showing all of the correct export locations. This is now working correctly.

FEATURE: Support for the DPA Newswire

Starting in Burli 230q, we now support the DPA newswire. This also requires a minimum of Newswires 2.51 to be installed. The newswire is called “DPA” in the Newswire2 tab and can be configured for either UNC or FTP folder ingest.

To add a Filter for this newswire, add a new Filter in the Filters tab and select Wire: DPA as the Source.

Export To menu not displaying correctly

Starting in Burli 230r, we have fixed an issue with the “Export to” menu which was not showing all of the correct export locations. This is now working correctly.

Web Server crashes when user plays an audio clip

Starting in Burli 230s, we have fixed an issue with the Burli Web Server. When a user would click to play a piece of audio via the Burli Web interface, the Burli Web Server would crash. This issue affected versions 230n-230r.

Fix for section break timing display

Starting in Burli 230s, we have fixed a display issue with Section Breaks not showing the time correctly if you had a font size or character set that would not fit. We have expanded the size of the columns for the Time so it will now show correctly.

FEATURE: Support for the DPA Newswire

Starting in Burli 230q, we now support the DPA newswire. This also requires a minimum of Newswires 2.51 to be installed. The newswire is called “DPA” in the Newswire2 tab and can be configured for either UNC or FTP folder ingest.

To add a Filter for this newswire, add a new Filter in the Filters tab and select Wire: DPA as the Source.

 

Audio Logger does not clean up old folders when purging old recordings

Starting in Burli 230o, Burli will delete the Folders as well as the files according to the Session's Purge Settings. Previous to this version, only the audio files would be deleted and the empty folders would be left on disk. You will have to manually delete any Folders that are older than your Purge settings to begin with but Burli clean up any new empty folders and files from now on.

FEATURE: Open Web Burli Web Links In New Tab

Starting in Burli 230o, when a user in logged into the Burli Web Server and clicks on a Web Link on the left hand side on the Burli Web Server, that website will open in a new tab, rather than the frame. The following MAIN.INI setting is required to enable this feature:

[WebLinks]

OpenWebBurliWebLinksInNewTab=Yes

FEATURE: Advanced Audio processing filters

Starting in Burli 230m, you are now able to add custom audio processing filters to the Single Track Editor. Simple Right-Click on the audio in the Work Folder and Select “Filter his audio” and then the required filter.

To enable the audio filters, you must have a copy of libMedia.dll in the Burli Server in ~\Burli\Settings\Media as well as the following MAIN.INI  settings:

[Audio]

Filter1=Low band pass~lowpass=f=3000

Filter2=High band pass~highpass=f=200

Filter3=Loudness Normalise (single pass)~loudnorm=I=-16:LRA=20.0

Filter4=Loudness Normalise (dual pass)~loudnorm=I=-16:LRA=20.0:dualpass=1

Filter5=50% Volume~volume=volume=0.5

Filter6=150% Volume~volume=volume=1.5

These are a few examples which work well however some of the other available filters are experimental and not all will work as expected. The “Loudness Normalise” in this the EBU r128 standard.

These audio filters use the libFFmpeg library so you can modify or add the required filters to MAIN.INI making them available on all workstations. (https://ffmpeg.org/ffmpeg-filters.html)

FEATURE: Ability to drag and drop a story to any In-House category via Virtual Newsroom

Starting in Burli 230m, you can now drag and drop a story on any remote In-House Category and Burli will automatically pick the correct category for it.

Previous to this version, a drag and drop would always show the Default category and the user had to click on the Category drop down menu to select the correct Category. To enable this VN feature, DropOnInHouseFilter=Yes (on by default) and RemoteFilters=Yes must be turned on in the [Startup] section of MAIN.INI.

Fixed crash with FTP client

Starting in Burli 230L, we fixed an issue with the Burli FTP client when using initial file paths which included subfilters. (Eg. /News/Sports) This is not working correctly.

FEATURE: Local Work Folder story timing

Starting in Burli 230k, we can now display the story timing in the local Work folder. This way you can see the total length of your story before you post it to the In-Queue or drop it into a Script. To enable this feature, you must have libMedia.dll in the Burli Server in ~\Burli\Settings\Media and have the following setting in MAIN.IN:

[Startup]

LocalFolderTiming=Yes

The default is No

Removed dependence for MYSQL or MySQL DLLs when a database is not being used

Starting in Burli 230k, we removed the dependance for MSSQL or MySQL DLLs when a database is not being used. Some users would see errors when launching Burli even if they were not using a MySQL or MSSQL Database server. This would appear if you have SQLFeatures=## and ## was any value. Now, Burli will not request any DLLs as long as SQLFeatures=0 or does not exist in MAIN.INI.

Fixed MAIN.INI [Newswire Server] section

Starting in Burli 230j, we have fixed an issue when you have multiple lines in a row which are comments in the [Newswire Server] section of MAIN.INI. Having multiple lines in a row which begin with ; would disable any of the following entries. This is now working correctly.

Renamed “libFFmpeg.dll” to “libMedia.dll”

Starting in Burli 230j, we have renamed the libFFmpeg.dll file to libMedia.dll for easier reference. All future media DLLs will be called libMedia.dll and will be copied automatically from your Burli server to each workstation as they launch. There should always be a copy of libMedia.dll on your Burli Server in ~\Burli\Settings\Media. To see which version of libMedia.dll you have installed on any machine you can do the following in Burli:

CTRL-F6 -> libmedia -> OK

You will then see the version of libMedia.dll installed on the Burli workstation

Fix for Twitter feeds via VN

Starting in Burli 230j, we have fixed an issue when viewing Twitter feeds which included multiple carriage returns via VN. Previous to this version, Burli would not display all stories. This is now working correctly.

Fix for Tab windows when changing fonts

Starting in Burli 230k, we have fixed an when choosing or switching Fonts and the titles in the Tab windows would look strange. You can now switch or edit Fonts without affecting the Tab windows.

Burli fails to read [Startup] section of MAIN.INI if encoded in utf-8

Starting in Burli 230i, we have fixed an issue with the [Startup] section of MAIN.INI not being read if it is encoded in UTF-8. This is now working as expected.

Future support for Unicode for database access

Starting in Burli 230h and the latest database DLLs (MySQL=v8 MSSQL=v3) we can use the same DLL for both ANSI and Unicode versions of Burli. Simply replace the DLLs depending on your SQL version (MySQL or MMSSQL) on the Burli Server in ~\Burli\Settings\Database with the new DLLs.

FEATURE: Refresh VN Filter tree

Starting in Burli 230g, we now refresh Sub-Filters when looking at a VN filter. Previous to this version, only parent filters would be refreshed. The refresh setting RemoteVNInQueueRefresh=## where ## is minutes is required.

Removed Burli warning message on exit

Starting in Burli 230g, we no longer warn users on exit that the machine has newswire capture responsibilities when only the Background recorder feature has been turned on.

FEATURE: Show Twitter links as clickable

Starting in Burli 230f, all Twitter feeds which include URLs in the Tweet are now clickable.

Web browser improvement

Starting with Burli 230e, when you go to a web page, the URL in the address bar will just show the address of the page that you are on. Previous to this, the address bar would change to show each link and page content link as it was being loaded.

Internal Newswire stories being overwritten with a previous story

Starting with Burli 230d, we have resolved an issue when multiple Internal Newswire stories are posted at the same time. The filenames stored on the server use the timestamp including the seconds so if multiple stories were posted within the same seconds, they would all get overwritten by the last one posted. We now include milliseconds in the filenames which will assure that each story gets a unique filename.

 

Corrupt waveform after recording in MP2 format

Starting in Burli 230c, we have fixed an issue where after recording in MP2 format, the waveform that is created does not represent the sound correctly. This issue was seen only when the user has both MP2 as the default format and the MAIN.INI setting of RMSNormalizeOnStop=Yes is enabled. This has now been resolved.

 

FEATURE: Ability to close multiple tabs

Starting in Burli 230a, you are now able to close multiple tabs in the bottom work area. You can choose from closing the current tab, close all tabs or close all tabs but the current one.

 

Re Enable Active FTP Mode

Starting in Burli 229z, we have added the Active FTP mode back to Burli. This feature was removed in Burli 227d so the “Passive Mode” button on any newswire was disabled as we were always defaulting to Extended Passive or Passive Mode automatically. Some users still require Active FTP Mode so this option was added back to Burli 229z. If you are having problems with Newswire FTP connections after this upgrade, you may need to check the “Passive Mode” option for the affected newswire service in Burli.

 

FTP Client sub directories fix

Starting in Burli 229x, we have fixed an issue with the FTP client. Previously, if a client was logged into an FTP site with multiple subfolders, the user was not able to navigate up the folder tree to the parent folders. This affected versions starting with version 227d.

 

Inconsistent Stereo file import

Starting in Burli 229w, we have fixed an issue when importing stereo audio files that are not MP3, WAV or MP2 where the audio would end up being in summed mono format. This also requires the latest libFFmpeg_2.2.dll to be copied to the Burli server. Burli will now import Stereo files correctly when ingested.

 

Keep the Story Creation time when copying stories to Network Folders

Starting in Burli 229v, Burli will not keep the Story Creation Time when copying stories and audio to Network and Aliased folder. Previous to this version, Burli would write the current time to all items being copied to Network Folders.

 

Fix for M4A files

We have fixed an issue with some M4A files which were being clipped at the end of the audio and silence added to the beginning due to bad header. This fix requires libFFmpeg.dll  (Ver 2.1) to be copied to the Burli Root Path in ~\Burli\Settings\Media. All workstations will copy and use this new DLL locally when they launch Burli.

 

New Logo for Burli Newsroom and StartApp

Starting in Burli 229s and StartApp 7.3.0.0.1, we are introducing our new Desktop icon of everyone’s favourite cockatiel, the Burli Bird!

Please let everyone know that their icons have been updated.

To update StartApp.exe, the local workstations will require StartApp7.3.0.1.exe to be manually copied to each local Burli directory (C:\Burli by default) and a new shortcut placed on their desktop. If you just rename StartApp7.3.0.1.exe to StartApp.exe (like the old version), no new shortcuts should be required.

FEATURE: Support for all audio and video files types for audio ingest

Starting in Burli 229r, you are now able to ingest all audio and the audio from all video file types. This works with Drag and Drop, Open External File, and Newswire or Email ingest. Previously, Burli could ingest most audio files with the addition of Apple QuickTime and a DLL. Since Apple no longer supports QuickTime for Windows, we are using FFMPEG to decode all audio and video files and convert the audio into the default audio format being used in the newsroom. To enable this feature, simply copy the file "libFFmpeg.dll" to the Burli Server in the ~\Burli\Settings\Media folder. Please create this folder if it does not already exist. As each workstation is launched, it will check the server for any drivers and updates in this folder and copy it locally to ~\Burli\Drivers\Media. No additional installation files are required. Burli now supports the following file types: Audio Files (*.aac;*.aif;*.aifc;*.aiff;*.amr;*.bwf;*.flac;*.m4a;*.mp2;*.mp3;*.mpg;*.ogg;*.pcm;*.s48;*.snd;*.wav;*.wma) Video Files (*.3gp;*.avc;*.avi;*.divx;*.mkv;*.mov;*.mp4;*.mpg;*.wmv) In addition, this new engine can be used for decoding MP3 files as they are ingested instead of using the older audio ingest method.

Faxes unable to be displayed because source .tif file missing from server

Starting in Burli 229r, we have fixed an issue when both fax capture and auto dispatch are configured. In that case, the user would see “TIFFOpen error” when clicking on a fax that has been received. This is now working as expected. Users who do not have both fax capture and auto dispatch configured will not see this issue.

Advanced right-click menu options | Cut, Copy and Paste

In 229q, the pop up menu item "Convert selected text" is hidden if no text is selected. It was always shown in earlier versions.

Fix for invalid commands in the Upper Work pane and add Tool Tips

Starting in Burli 229p, we have enabled the Copy/Cut/Paste buttons in the “Multitrack” window when using it for text or Single Track audio.

Fix for POP3S, FTPS and SFTP support in Burli

Starting in Burli 229o, we have fixed an issue where Burli was not always successful connecting to an FTPS/SFTP server if it is using a nonstandard port (21). Burli will instead try port 46321.

Drag and Drop audio fix

Starting in Burli 229o, we have fixed an issue with drag and drop audio which would create a story with a broken link. This affected version 228o to 229q.

Fix for missing audio when restarting Audio Logger sessions

Staring in Burli 229o, we have fixed an issue with the Audio Logger when starting and stopping a session or opening and closing Burli on a machine which has Audio Logger duties. Previous to this version, if a session was stopped and started, the audio for the rest of that hour would not be available to the users.

Fix for usernames which start or end with a space

Starting in Burli 229n, we will automatically strip any leading or trailing spaces which have been entered when creating new users. Previously, the user would be required to includes those spaces.

FEATURE: Radiomation Archive data import

Starting in Burli 229m, we have added the function to import a Radiomation Archive into a Burli Archive database. The Radiomation Archive should be saved as a .CSV file and placed in the same folder as the Text which are being imported. All audio files should be in subfolders of this location. The following function assumes that you have a functioning MSSQL or MySQL Burli database created.

FEATURE: Alternate Single Track Play Speed

Starting In Burli 229L, we have removed the option of changing the Alternate Single Track Play Speed of 1 as this is the normal playback speed. The option is found in Config -> Alt Single Track Play Speed and initiated by pressing CTRL+Play.

FEATURE: Option to disable Burli Newswire client-side/gateway purging

Starting in Burli 229L, we have added the ability to disable client side purging of Internal Newswire/Uploaded file with Attachment files. Previous to this version, uploaded files will always be checked for expiry and deleted unless the user sets a very high value for “PurgeHold” in the [Newswire Server] section of MAIN.INI.

You can now disable the purging function by setting the PurgeInterval to 0 or a negative value. With this value, the purging thread will not be launched and the information of the uploaded files will not be saved in the XML file used for purging. Example: [Newswire Server] PurgeInterval=0 or PurgeInterval=-1 Turns the purging function off.

FEATURE: Support for the Radio New Zealand (NEWSML RNZ) newswire

Starting in Burli 229j, we now support the Radio New Zealand (NEWSML RNZ) newswire. This also requires a minimum of Newswires 2.49 to be installed. The newswire is called “NewsML (RNZ)” in the Newswires2 tab and can be configured for either UNC folder or FTP folder ingest. When configuring the newswire, the File Filters field should have *.nsml and the Audio File Extension should have mp2 or whichever audio file format you are expecting with the stories. This newswire can only handle one audio file extension. To add a Filter for this newswire, add a new Filter in the Filters tab and select Wire: NewsML-RNZ as the Source.

FEATURE: Shortcut keys to launch Quickplay decks

Starting in Burli 229i, you are now able to launch a Quickplay deck with your keyboard. Previous to this version, only a mouse click or GPIO device. To start a Quickplay deck, press CTRL+SHIFT+[DECK#]. You can use CTRL+SHIFT+1 –> 8 to start decks 1 to 8.

Upload to web with attachment or to Burli Internal Newswire ca sometimes overwrite existing files

Starting in Burli 229g, we have added an option to change the naming convention for files uploaded to web with attachment or to the Burli Internal Newswire. This new setting uses the current time including seconds to the file name of the XML and the attachments to prevent any duplication of file names.

FEATURE: Dispatch attachment with Burli Internal Newswire

Starting in Burli 229f, we have fixed an issue with cancelling the attachment step and Burli showing an error on the ticker. You can now cancel the attachment and your Burli Server will dispatch the file with no additional attachments. A success or failure will show properly along the ticker.

 

FEATURE: POP3S, FTPS and SFTP support in Burli

Starting in Burli 229f, we have corrected an error which may have resulted in duplicate emails arriving. This seems to affect POP3s when pulling from an Exchange email server.

Added ToolTips to Single Track editor

Starting in Burli 229e, we have added all of the Tool Tips for when you hover your mouse over the action buttons.

FEATURE: Support for the new Marketwired newswire format

Starting in Burli 229d, we have added support for the Marketwired newswire format. This also requires a minimum of Newswires-2-48.zip

 

Drag/drop Story audio from Script Browser into Clip placeholder broken

In Burli 229c, we have fixed an issue where dragging a story with audio from the script explorer to a Script clip holder on the bottom was broken. This is now working as expected.

Displays the unedited run time in Quickplay deck, until playing

Starting in Burli 229c, we have fixed a display issue where an edited piece of audio which is dragged into a Quickplay deck would show the unedited time until the user started the audio. This is now showing the correct length.

Script Explorer refresh issue

Starting in Burli 229b, we have fixed a script explorer refresh issue. Previous to this version, it would take some seconds after expanding a day to show the + sign beside all scripts which contained stories. This now happens instantly.

FEATURE: Support for Luci audio Newswire

Starting in Burli 228z, we have added support for Luci .BWF files. Burli will read the data from the file header and use it for the header and body of the story. If the “Description” field contains a # character, everything before it will be the Slug and everything after the # will be the Body. The sender’s name will also be included in the header. This feature also requires Newswires-2-27.zip and above. When creating a Filter, there is a new Source called “Wire:Luci” to filter this newswire.

FEATURE: Dispatch audio to Network Folder without any popup

Starting in Burli 228y, we have added the ability to drag and drop or Dispatch Audio to a Network Folder with the default of “Display the dropped audio as a wave graph”. With the following setting turned on, the file will be sent as an Audio only file.[Startup] NoNetworkFolderDropPrompt=[Yes/No] No is the default, which means always show the prompt window.

FEATURE: WebServer and VN | Sort Network folder stories in Modified Date order

Starting in Burli 228x, we have added the ability to show Network foldeer contents via Web Server or VN with the most recent itmes at the top. This requires a new main.ini setting  [Startup] DisplayWebNetworkFoldersDescending=[Yes/No] Yes will show the most recent at the top of the list. The Default is No and will show the oldest on the top.

This setting also requires the following MAIN.INI setting to turn this feature on:

DisplayWebNetworkFoldersByDate=Yes

Please note, the above setting affects the behavior of:"DisplayWebNetworkFoldersAlphabetically" If the setting "DisplayWebNetworkFoldersAlphabetically" is on, the new/old setting is ignored. This applies to both displaying web network folders in the Burli Web Server and displaying VN network folders inside Burli.

FEATURE: Export user list to text

Starting in Burli 228x, we have added the ability to use the "Phone Hybrid" file in Burli Security for free text information like station name, location or full name. This information can then be exported using the CTRL-F6 -> userlist2. When adding the information into the Phone Hybrid field in Burli Security, you must check the "Allow hybrid access" to store the information.

FEATURE: Send to SoundCloud

Starting in Burli 228w, we have moved the “Upload to SoundCloud” option up the list. This is to keep the “Build Text and Audio” option as the last item on the list which may people are used to.

FEATURE: Ability to choose a category and priority when sending a story to the web

Starting in Burli 228w, we have added the ability to choose a category and priority when using the Send to Web feature. The categories and priorities are configured in the POST.INI file in the [NewswireCategoryMap] and  [NewswirePriorityMap] sections.

FEATURE: Send to Soundcloud

Starting in Burli 228v, we have improved the method used for sending to Soundcloud.

Fixed File deletion from FTP

Starting in Burli 228u, we have fixed an issue with file deletion from FTP sites when using the “Auto Purging Files” option in one of the Newswires. This is now working as expected..

Fixed anonymous FTP site access

Starting in Burli 228t, we have fixed an issue where anonymous FTP access was no longer working. This affected versions 228a-228s. This is now working as it should.

Fixed drag and drop to Work Folder for audio files

Starting in Burli 228s, we have fixed an issue where the drag and drop of an audio file or link function would result in a story with the link to file instead of the audio file. This affected versions 228n-228r and is now working as it should.

Script refresh issue

Starting in Burli 228r, we have improved the Script refresh so that all scripts and stories in the upper Script Explorer window show immediately. Previous to this version, users would have to wait for up to 30 seconds for the stories to appear. This is now working as expected.

Grey out invalid buttons

Starting in Burli 228q, we now grey out any invalid buttons along the toolbars if the operation does not apply to the current item. We have also added Tool Tips to the buttons in the Text Editor and Single Track Editor.

Remove all TABs from the IAR newswire

Starting in Burli 228p, we now remove all TABs from the IAR Newswire when a story is pulled down to the Work folder.

Following an empty Twitter account stops Twitter capture

We have fixed an issue in Burli 228n where Burli would stop ingesting Twitter if one of the accounts had no Tweets. Burli will now just ignore the empty Twitter account and move on to the next one.

Improved FTP/UNC audio ingest

Starting in Burli 228m, we have improved the FTP and UNC Audio file ingest by limiting Burli to converting 5 files at a time to reduce CPU usage and speed up conversions.

New MSSQL Driver version

Starting in Burli 228L we have improved the MSSQL DLLs to minimize memory usage. Version 2 of the drivers will be automatically copied to every workstation when they launch. For all users that have a MSSQL database, please put all of the Version 2 drivers to the Burli Root Path in ~\Burli\Settings\Database and overwrite or rename the existing versions.

FTP Timeout

Starting in Burli 228k, we have added a time for all FTP operations. This is now set to 5 minutes

Fixed Clip holder information when going to Prompter mode (CTRL-F12)

We have fixed an issue in Burli 228h where the Clip holder in Prompter mode would not show the word Clip if you went to the full screen Prompter with CTRL-F12. This is now working as expected.

 

FEATURE: Variable playback speed in Single track editor

Starting in Burli 228c, we have made a small change to the menu item to select the alternate playback speed option. We now show in the Config menu “Alt Single track speed” to make your selection.

FEATURE: FTPS and SFTP Support in Burli Newswires2 ingest

Starting in Burli 228a, we have added the ability to ingest newswires and audio from SFTP and FTPS servers. When entering the FTP Server field information, you should explicitly add the prefix of "ftps://" or "sftp://" before the server IP address or server name. The default prefix is "ftp" if you do not enter one. As for the "Port" information, leave it blank and Burli will use the default port of that FTP protocol be used. This feature does not yet work for uploading to an Internal Newswire.

Prompter Mouse auto scroll function does not keep focus

Starting in Burli 228a, we have improved the behaviour of the Scroll function when in Prompter mode. Previous to this version, when you have a half screen prompter and decide to click on and scroll through a story in the upper window, the prompter would start scrolling again. This is now working as it should.

Audio Scroll Bar disappears after zoom/waveform selection

Starting in Burli 228a, we have fixed an issue where if the user selects some audio waveform and zooms into some audio waveform, if you moved the scroll position (drag or scroll wheel), the entire scroll bar temporarily disappeared. This is now working as it should.

Local Script editing behaviour fix

In Burli 227z, we have fixed an issue in 227y where the Script Story contents could not be seeing tine the upper preview window. This is now working correctly and stories can be previewed in the upper window again.

Remote Section Breaks converted to Stories

We have fixed an issue where remote script Section Breaks were being changed to Stories when dragged to a local Script or Folder. Starting in Burli 227y, we retain the properties of the remote Section Break.

Local Script editing behaviour fix

In Burli 227x, we added multiple Remote Script selection which had an negative effect with selecting Local Scripts for editing. In Burli 227y, we have fixed that behaviour so that a simple drag and drop to your Work folder is working as expected.

FEATURE: Copy multiple Remote or Local Script stories

Starting in Burli 227x, we have added the ability to select and drag multiple stories from a Remote or Local Script in the top window to a local Script or Folder on the bottom work area. Users can Shift-click to select a range of stories or Ctrl-click to select individual stories. The stories that have been selected will be shown in bold font.

FEATURE: Widen Category drop down menu window for Internal Newswire

Starting in Burli 227x, we have widened the Category drop down picker window to allow for longer category names. This change only affects sending to the Internal Newswire.

FEATURE: Support for POP3s in Email Capture

Starting in Burli 227w, we have added native POP3s support to allow connections to email providers like Gmail, Yahoo and Office365. Previous to this version, those types of connections could only be made using a third party proxy to add TSL encryption like stunnel.

 

The format of POP3 accounts remains the same which is:

 

emailaccount@POP3Server

 

For example:

 

abc@def.com, if the mail server is def.com and using pop3, not pop3s.

 

The new format which includes both POP3 and POP3s is:

 

emailaccount@[protocol://]server[:port]

 

[protocol] is optional. The value can be "pop3" or "pop3s". Default is "pop3".

[port] is optional. The default is 110 for pop3 and 995 for pop3s.

 

for example, in case of Gmail.com which uses pop3s, the setting is:

 

abc@gmail.com@pop3s://pop.gmail.com or

abc@gmail.com@pop3s://pop.gmail.com:995

FEATURE: Dispatch to Zetta Automation

Starting in Burli 227v, we have added support to dispatch to Zetta automation systems. A configuration file called zetta.ini must be configured and saved in ~\Burli\Settings to add this feature. Please contact Burli Support for details.

Sample zetta.ini

Audition metadata/marker audio causes audio click | drag/drop import

Starting in Burli 227u, we have fixed an issue where any metadata added to an audio file which is the same format as your default audio format would include some clicks in the file when the file was dragged and dropped into the Work folder. We have now resolved this issue and all files should all import cleanly.

FEATURE: Dispatch to DJB Radio Automation

Starting in Burli 227u, we have added support to dispatch to DJB Radio automation systems. A configuration file called djbradio.ini must be edited and saved in ~\Burli\Settings to add this feature. Please contact Burli Support for details.

FEATURE: WINS Downloader newswire

Starting in Burli 227t, we now use the 1010 WINS logo for the WIND Downloader newswire. A minimum of Newswires 2.44 is also required for this change.

Starting in Burli 227s, we have added a “WINS Downloader” newswire to the Newswires2 tab. This requires a minimum of Newswires 2.43. The Filter Source for this new newswire is called “Wire: WINS DNLD”.

 

FEATURE: Flash Burli task bar icon when a chat message arrives

Starting in Burli 227r, we will flash the Burli icon on the Windows task bar if a chat message arrives but the user has minimized or switched focus to another application.

 

Dispatch to WideOrbit improved

Starting in Burli 227p, we have removed the hard coded timeout value to avoid showing a false error message during manual dispatch to WideOrbit automation systems. Any Auto Dispatch or if you have the “UseThreadToCopy=Yes” in WideOrbit.ini will only show the progress in the ticker tape. The default behaviour or without that setting, (or set to No) it will always show progress in a popup window.

FTP Client crash when expanding site node

Starting in Burli 227o, we have fixed an issue of Burli crashing when the user clicks on the + of an FTP site without clicking on the name first. This is now resolved.

 

Dispatch error

Starting in Burli 227m, we have changed a timeout value which would erroneously show an error when manually dispatching a file to an automation system. The timeout has been changed from 10 seconds to 60 seconds

Suppress pop up messages for automatic dispatch

Starting in Burli 227L, we suppress the popup dialogue box when using an auto dispatch to any automation system. The status will be shown on the ticker tape for Scott and WideOrbit automation. The status for other automations systems will be added in upcoming versions. For manual dispatch to automation, we will continue to show the popup except in the case of Scott automation when using “UseThreadCopy=Yes. In that case, we will still show the status in the ticker.

Expanded diagnostic logging of Chat messages

Starting in Burli 227k, we have added extra information in the Chat logs for Burli Workstations. To enable these logs, you must turn them on in the Event Logs button in Config > Program Setup. You should also have the logs turned on for the Burli TCP Server so that comparisons can be made.

FEATURE: Sort in the FTP Client Window

Starting in Burli 227j, you are not able to sort the items in the FTP Client window by clicking on the Filename, Size or Date/Time columns.

Wrong stories archived when using Ctrl+D to Archive

Starting in Burli 227j, when using Ctrl+D (dispatch window) to Archive In-queue files, only the story(s) focussed in the lower Work folder is archived. Using Right-Click > Dispatch > Archive works as expected. While fixing this issue, we also made some improvements to the Dispatch UI, see next.

Improved user interface when dispatching to the Archive

Starting in Burli 227j, we now show the Slug of each item that has been sent to the Archive when using CTRL-D to Dispatch.

FEATURE: Side Scrolling in the Single Track Editor when zoomed in

Starting in Burli 227h, when a user has zoomed in on a portion of the Single Track Editor, they are now able to scroll right or left using the new scroll bar along the bottom.

Force Newswire Engine use to use QuickTime for MP3

Starting in Burli 227g, we have added a new setting to use the QuickTime audio converter instead of the default engine for ingesting from Newswires. There is a new MAIN.INI setting required:

[Startup]

QuickTimeMp3=[Yes/No]

If the setting is Yes, then Burli uses QuickTime library instead of lame mp3 engine to convert all mp3 files. The default is No.

To use this feature, you also have to install Apple QuickTime and the Burli QuickTime DLL.

FEATURE: FTPS and SFTP support in Burli

Starting in Burli 227e, Burli can support FTPS or SFTP connections when using the FTP Client window. The MAIN.INI settings are as follows:

[FTP]

Client1=FTP name~Server IP~user~password~initial path

This now supports ftp, ftps, and sftp.

For example,

[FTP]

Client1=Burli FTP1~ftps://8.8.8.8~user~password~initial path

Client2=Burli FTP2~sftp://8.8.8.8~user~password~initial path

Client3=Burli FTP3~ftp://8.8.8.8~user~password~initial path

Client4=Burli FTP3~8.8.8.8~user~password~initial path

The protocol string must be followed by "://" To allow a special ftp port, add ":port#" after server IP, like this sftp://8.8.8.8:997 The global passive mode setting in MAIN.INI has no effect to the FTP tab window. Burli can now handle passive and active mode automatically.

FEATURE: Auto-logout at specific clock time or after X minutes

Starting in Burli 227c, we have added the option for workstations to automatically log out after a period of inactivity or at a specific time of the day. This is very useful for NetHASP users where a production room is used for a short time but the user forgets to logout of the workstations which ties up a NetHASP license. You are now able to specify that workstations are logged out after X minutes of inactivity or at a specific time every day.

The MAIN.INI Setting is:

AutoLogoutTime=####

Where #### is how many Minutes of inactivity

For Example:

AutoLogoutTime=330

This means 330 minutes of idle or 5 1/2 hours

OR

If you use a COLON in the value, then it is considered a specific TIME of day.

AutoLogoutTime=##:##

Where ##:## is the time of day for the time of day in 24hour clock format.

For example:

AutoLogoutTime=3:30

This means 3:30 AM

AutoLogoutTime=23:30

This means 11:30pm or 23:30

There are TWO other MAIN.INI settings which are prerequisites for this function to work:

[Startup]

AutoLogoutEnabled=Yes

AutoLogoutLevel=2

The AutoLogoutLevel=2 is for any NetHASP workstations. AutoLogoutLevel=1 will log out any workstation whether it has a NetHASP or local USB HASP

BE CAREFUL: If you have any Capture or On-Air machines which are using a NetHASP license but you do not want them to be affected but this setting, you can EXCLUDE those machines by using the following format:

[Startup]

AutoLogoutEnabled=Yes!EXCLUDED HASP ID,EXCLUDED HASP ID,EXCLUDED HASP ID

Every HASP ID following the ! will be excluded.

In addition to the settings above, you can also optionally have Burli close when the logout happens this can be done with the following MAIN.INI setting:

[Startup]

AutoCloseOnAutoLogout=Yes

The default is No.

Improved MP3 AUDIPT ingest

Starting in Burli 226y, we have improved the logic for ingesting MP3 audio files. Previous to this version, MP3 files which contained the ID3 tag at the very end could end up being skipped by Burli.

SQL Ctrl+F6 command ‘SQLINITDATABASE’ does not create Archive tables.

Starting in Burli 226x, the Ctrl+F6 command ‘SQLINITDATABASE’ now populates all required tables. Previously, the archive tables were not always created and a separate Ctrl+F6 command was required for a fully functional database.

*This command is required only for newly configured databases. While it should not cause any problem, it is recommended you do not run this command on a previously initialized database unless the archive tables are missing.

Failed Archiving confirmed as “Successful Dispatch’ (missing archive database tables)

Starting in Burli 226w, we now warn the user if Archiving a story fails. In some cases, we found that Archiving stories reported successful when the archive database was not setup correctly.

Burli will now produce the error “Error Dispatching Item” if archiving fails.

*Please make sure the Archive tables exist in your SQL database. If you require assistance, please contact Burli Support.

Improved compatibility when creating MP3 files

Starting in Burli 226v, we have changed the MP3 padding to use “Adjust” rather than On or Off. The MAIN.INI setting, if included, will force padding to On or Off which can have varying results depending on the length of the file being created (MP3Padding=Yes/No). We recommend that the setting is left remmed out or removed so that Burli uses the Adjust mode.

FEATURE: 4 channel PCM files supported

Starting in Burli 226u, we now support 4 (or more) channel PCM audio files for AUDIPT and drag and drop. This is a common format for some television production tools and those files can now be dropped to a shared network folder for use in the newsroom. The channels will all be bounced down to your default audio format. Apple QuickTime and the Burli QuickTime DLL must be installed on each machine that requires this feature.

 

FEATURE: MP3 for the Internal Newswire | AudioFileSizeLimit setting

Starting in Burli 226u, we now support audio file size limits for the Internal Newswire. When a user at a workstation sends a story with one or more audio clips, each one will be checked to see if one or more exceed the limitation set by the Administrator based on the MP3 format used for the Internal Newswire. If one or more of the story clips exceeds that limit, the user will be shown a warning to let them know that the story cannot be exported. The MAIN.INI setting is:

 

[Newswires Server]

AudioFileSizeLimit=####

 Where #### is the value in kilobytes.

 MP3 file causes Burli email ingest to crash

Starting in Burli 226s, we have added extra tolerance for poorly formed MP3 files. Previous to this version, some MP3 files which contain bad or inconsistent header information that came via email, would stop email from ingesting afterwards. This function is now much tolerant to these types of files.

FEATURE: FTP transfer for Wideorbit dispatch

Starting in Burli 226q, Burli can send WideOrbit Automation audio carts to FTP sites in addition to UNC paths. Multiple sites/paths can be set up for each group of carts if required. The format for wideorbit.ini is as follows:

[Group[n]]

Path=Server IP or name,port,passive/active mode,user name,password,initial path

 

Example:

 

[Group4]

Path=ftp.distribution.com,21,0,Newsroom,Passw0rd123,/Import/News

 

port: if omitted, Burli will use the FTP protocol default port which is 21.

passive mode: "0"/"1" means active mode/passive mode. If not set, Burli will use the global "PassiveFTPMode" setting in main.ini.

 

You can add multiple locations by using the | between each location however you cannot exceed 256 characters total in one Path statement.

In the case of FTP transfer, Burli will create a temporary “.part” file on the FTP server until the transfer is complete and then rename the file to “.WAV”.  Success or failure of a dispatch will be shown in the Burli ticker. All log events relating to FTP will be in the MISC log file.

Auto Dispatch (audio) fails when audio missing

Starting in Burli 226p, we have fixed an issue when using the Auto Dispatch feature to an Automation system.

The issue occurred when Auto Dispatch file which should include audio arrives in the Burli InQueue without the audio. Burli would try to dispatch it but it would fail and all subsequent Auto Dispatch files would fail. Burli now checks to see if the Dispatch location requires an audio file and if none is included, we will skip the file and log the error in the Dispatch log file if logging is enabled.

AUDIPT capture from an FTP site adds a forward slash (/) prefix to audio file name

Fixed in 226o

CP Audio capture fails after a few days

We have added extra logging to the Miscellaneous log files to help pinpoint an issue where the audio from the CP audio feed no longer arrives after a few days of running.

Archive Search String using "and" "or" operators fail

The archive search dialogue box has some changes in the UI in 226o. WE have added a combo box which allows users to select the search types/methods among three choices.1. Classic - which is simply a "LIKE" search 2. Boolean - full text search, with boolean method on, so that "and", "or" etc can be mixed with searching text 3. Free text - full text search, with boolean method off, so that it is more like nature language search. * If main.ini setting "FullTextSearch” is No, the UI won't be displayed. At this time, only archive search is affected.

 [AudioSelFiles] feature is not available when stereo is default audio format

Fixed in 226o

Sub filters can lose their Source information

Fixed in 226K. We have found that if you create a Sub filter and check box the Source and restart Burli and uncheck the source, the Sub filter loses its source information and you need to manually select the Source information even though it is a Sub filter.

Body search via Web Browser causes application crash

Fixed in 226L. The main reason of crash was corrupt stories in the In-queue. We have improved the error handling for these stories. In one case this crash still occurs under very specific circumstances.

Sub filters can lose their Source information

Fixed in 226K.

Sub Filter not respecting parent filter

We have found that if you create for example a Parent Filter of RSS with RSS as the Source and then create a sub filter with not extra criteria like Body or Category, on restart, Burli will show the entire InQueue when selecting that Filter even though the parent is using RSS as the Source.

FEATURE: Export User List from Security

Starting in Burli 226j, we have added the ability to Export the list of Users in Burli Security to a text file. In Burli press CTRL-F6 and enter “userlist” (no quotes) and Burli will export  list of usernames to a text file by default called “UserList.txt” There will be one user per line followed by a comma. This feature respects the main.ini  setting "SaveAsFilePath" for initial file path.

FEATURE: Receive IPAWS alerts from FEMA (multiple States or Counties)

DOWNLOAD: IPAWS_Filter.dta 

Starting in Burli version 226i, we have improved features of the IPAWS national alerts from FEMA to include multiple States and Counties. Newswires 2-41.zip is also required to be installed for this new feature. Please be sure to follow the steps below exactly or your Burli workstation may be flooded with every alert from across the country. Burli will determine your location for FEMA alert messages based in County or State codes using the 2 digit State codes or the 5 digit County  codes. These codes can be found on the following URL.

State Codes: http://www.epa.gov/envirofw/html/codes/state.html

By clicking on your state in the link above, you will be taken to another page which shows all of County/Borough/Parish FIPS codes.

You can use just the State Code or you can narrow down the alert area to the county by adding the three digits of the County to the State. For example Colorado is FIPS code 08. If you optionally want to narrow the alert area down to the county, Denver for example is FIPS Code 031 so the entire FIPS code for Denver, Colorado is 08031.

The MAIN.INI setting to add this location information is :

[Newswires]

IPAWSSettings=[FIPS Code 1],[FIPS Code 2],[FIPS Code 3],etc.~[Local Severity Level]~[Non Local Severity Level]

Example:

IPAWSSettings=22,40017,13275,46117~1~4

In this example, the entire state of Louisiana is the Local Alert area as well as Canadian County, Oklahoma, Thomas County, Georgia and Stanley County, South Dakota where everything starting from Minor alerts are marked as Urgent and any alerts marked as Urgent from outside of your area are marked as Urgent.

The Local FIPS code is your local Alert area(s). This can be either the entire State (2 digits) or narrowed down to the County/Borough/Parish (5 digits)

The Local Severity Level determines what level of alerts are marked as Urgent and shown in Red on the ticker. Optionally they can pop up a message in Burli when an Urgent message arrives.

Each alert has a "Severity" attribute. Here is the mapping:

Extreme = 4

Severe = 3

Moderate = 2

Minor = 1

Unknown = 0

For example, if level value is set to 3, alerts with "Severe" or "Extreme" are marked as urgent story in Burli. If this setting is absent, all alerts are marked as regular.

The Non Local Severity Level is the threshold value of Urgent alerts of everything outside of your Local Alert area. This value is optional but if added will mark certain alerts above a specific level to also be marked as Urgent and in Red on the Ticker. See above comments for "local severity level". This may be valuable as some Extreme alerts in another part of the country could be considered news worthy.

In addition to the MAIN.INI settings above, you can optionally have Burli pop up a message each time an Urgent IPAWS message arrives. This is done by adding  the following two MAIN.INI settings:

[Startup]

PopupOnUrgentStories=Yes

UrgentStoryPopupWireID=222

Once you have added the MAIN.INI settings, you should import the supplied IPAWS_Filter.dta file.

This is done by going to Config > Program Setup > Filters.

Right-Click on the In-Queue and select Import.

Browse to the supplied IPAWS_Filter.dta file and press OK.

You will now see the IPAWS Filters have been added to your Filter tree and can be moved up or down in the list.

You should now restart Burli on your Capture machine so that it will read your Local FIPS code on launch.

All of the steps above are very important. Please be sure that you have completed all preceding steps before continuing.

The last step is to add a specific URL to your Burli Capture machine to start ingesting the alert messages.

Go to Config > Program Setup > Newswires2

Scroll down to IPAWS and press Install

In the Name field enter IPAWS

Change the Refresh Rate to every 5 minutes (or 1 minute)

In the URL field, enter (or Copy and Paste) the following:

https://apps.fema.gov/IPAWSOPEN_EAS_SERVICE/rest/public/recent/2012-08-21T11:40:43Z?pin=NERnYWYyZ1kxZzg

Press the OK button.

You are now receiving FEMA IPAWS Alerts in Burli!

Improved Archive searching when using FullTextSearch=No option

Staring in Burli 226h, we have improved the search results of the Archive when using FullTextSearch=No option  with multiple words which include the words and|or|not. With this version, you can now enter a string like “food and drug” and see all stories which include those words.

FEATURE: Receive IPAWS alerts from FEMA

Starting in Burli version 226g, we are now able to receive the IPAWS national alerts from FEMA. Newswires 2-41.zip is also required to be installed for this new feature. Please be sure to follow the steps below exactly or your Burli workstation may be flooded with every alert from across the country.

Improved error handling for PostRecActions which include FTP upload

Starting in Burli 226f, we have improved the error handling of PostRecAction command which include and FTP upload. Previous to this version, if the FTP site went offline or unresponsive, Burli could crash. We now handle this issue and log events were added to help diagnose the connection issues.

FEATURE: PAP NewsML1.2 newswire

Starting in Burli 226e and Newswires 2.40, we have changed the formatting of the PAP NewsML1.2 newswire. We now include the Sub Headline in the Body of each story instead of the Header.

 

FEATURE: Bay City News newswire

Starting in Burli 226e, we now support the Bay City News newswire. The newswire is called “BCN” in Newswires2 and requires Newswires 2.40 to be installed. The Filter Source for this newswire is called “Wire: Bay City News”.

 

FEATURE: NewsML 1.0 version of Reuters

Starting in Burli 226e, we now support the NewsML 1.0 version of Reuters. The newswire is called “RTML_1” in Newswires2 and requires Newswires 2.40 to be installed. The Filter Source for this newswire is called “Wire: NewsML 1.0 – Reuters”.

 

Twitter capture stops if the Twitter server returns an error message

Starting in Burli 226d, we have made Burli more fault tolerant if the Twitter Server returns an error message. These could be simple messages being returned like a Server busy or Server unavailable. Before this version, Burli could stop ingesting Twitter feeds but with the new version, Burli will simply try again the next time.

Audio Logger incorrect Start Stop times when recording multiple sessions

Starting in Burli 226c, we have changed the way we request a value from the database to fix an issue with an incorrect value being written when recording multiple concurrent Audio Logger sessions.

 

Auto Dispatch fails if a file is less than one second and loops an error

Starting in Burli 226c, we have fixed an issue when an audio file shorter than one second is auto dispatched to an automation system. Previous to this version, Burli would pop up an error message which once cleared would pop up again. Now Burli will just log the error and skip the file.

 

Improved functionality for the PAP NewsML newswire

Starting in Burli 226b, we have improved the functionality of the PAP NewsML newswire. Now when you drag a story down to the work area, the Summary information is included in the body of the story.

Twitter ingest now uses an improved engine

Starting in Burli 226a, we have started to use the new JSON library which will improve speed.

FEATURE: Force Multi-Track sessions to Stereo

Starting in Burli 225z, you are able to pre-set the Multi-track recorder sessions to always be in Stereo even if your default audio format is Mono. There is a MAIN.INI setting required to enable this feature:

[Startup]

MultitrackAlwaysStereo=Yes

The default is No

New logo for the Press Association  Newswire

Starting in Burli 225y and Newswires 2.39, Burli includes the updated Press Association newswire.

FEATURE: Improved Logging for iMediaTouch (omt.ini)

Starting in Burli 225y, Burli has improved logging and also includes extra log events to show all successful dispatches with sending to multiple dispatch paths with iMediaTouch automation systems. In order to see the log events, you must have the Dispatch log events turned on at each workstation that is dispatching to automation. The successful log events will include the Time, Path, File name, Length and Duration taken to send the file.

A typical log entry will look something like this:

2015-05-14 09:12:54.785                    225z-HL T320           'Walter Cronkite' Successfully copied "C:\Burli\Temp\15901.wav" to "\\OMTAutomation\Import\N201.WAV" in 4 second(s) (Audio length is 1:29.494)

Global Connect Newswire failed

We have changed the logic in the Global Connect Newswire which was recently added. Burli will now read the Header information regardless of your Purge settings. Starting in Burli 225x, Burli now reads all header information correctly.

Mouse gets "Stuck" in the Single Track editor

Starting in Burli 225x, we have resolved an issue where the mouse pointer could get “stuck” in the Single Track editor under specific conditions.

FEATURE: Display Sub Heading from PAP NewsML

We now support displaying the Sub Heading of all PAP NewsML stories. Starting with Newswires 2.37, there is a MAIN.INI setting required to display this field:

[Newswires]

SchemeLookup[n]=223,24

Where [n] is the next number in your list of SchemeLookup entries

FEATURE: Global Connect Newswire supported

Starting in Burli 225w, Burli now supports the Global Connect newswire which also requires Newswires-2-36.zip to be installed. You will find the newswire in the Newswires 2 tab.

 

Once you have set up your capture settings, you should also add a Filter using “Wire: Global connect” as the Source.

 

 

Fix for SoundCloud Uploading in Non-HL versions

Starting in Burli 225v, we have fixed an issue in Uploading to SoundCloud with Non-HL versions of Burli.

FEATURE: Upload to SoundCloud

Starting in Burli 225u, we now support uploading audio clips to SoundCloud. This is the first release of this feature so some improvements may be made based on your feedback. You will have to create a SoundCloud Account prior to configuring Burli in addition to adding a new section in MAIN.INI.

 

[SoundCloud]

Account=Friendly Account Name~email@address.com

 

Example:

 

[SoundCloud]

Account=Burli Software~burlisoftware@burli.com

 

Once you have added this section to MAIN.INI, you will have to restart Burli.

 

To upload any Audio Clip to your SoundCloud Account, simply Right Click on an Audio Only file and select “Upload to SoundCloud”:

 

 

The very first time that you upload a file, a popup window will ask you to log into your SoundCloud account with the email address and password. Once this has been done, Burli will save a certificate file on the Burli Root Path so it will not have to be done again.

 

You will then be shown the following window which will allow you to choose the Title, Tags and what kind of License as well as the ability to attach a photo:

 

 

Once you press the Upload button, you will see a progress bar and finally “[Title]” has been uploaded successfully. Press the Done button to continue.

 

FEATURE: Option to force all Network Folder items to the Recycle Bin

Starting in Burli 225u, we have added the ability to always send Network Folder items to the Network Recycle Bin to prevent any accidental deletions. There is a MAIN.INI setting required to be added to turn this behaviour On:

 

[NetworkFolderRecycleBin]

ForceRecycle=Yes

 

The Default is No

 

With the option turned on, you will see the Delete option has been greyed out when deleting a file from a Network Folder.

 

FEATURE: OMT Automation | Dispatch to multiple UNC paths

Starting in Burli 225u, Burli can now Dispatch to multiple UNC paths for OMT Automation systems. This allows for the same OMT Dispatch cart to go to separate OMT automation systems at one time. The | (pipe) is used as the separator between each UNC path. For example:

 

[Group1]

Name=Monday Radio News

Format=WAV

Path=\\10.13.104.4\Import|\\10.12.208.4\import|\\10.13.222.4\import

FEATURE: Archive audio in MP2 format

Starting in Burli 225t, you can now specify an alternative audio format for your Archived audio. If your default format in your newsroom is PCM Linear audio, you are now able to set your Archived audio to be MP2 format. Previous to this version, you were only able to Archive in your default format. There is a new Archive.ini setting to enable this feature:

 

[data]

AudioFormat= [LINEAR|MP2],[STEREO|MONO],[SAMPLE-RATE],[BITRATE]

 

Example:

 

[data]

AudioFormat=MP2,MONO,44100,128

 

Currently MP2 and Linear audio formats are supported.

 

If you have any Auto Dispatch set up to send stories to your Archive in a specific audio format, please remove the audio settings for that instance in your Dispatch.ini file or all files will be converted twice.

 

FEATURE: Rearrange audio clip order in a story

We have fixed an issue with the audio clip swap function when using Quickplay decks. Previous to this version, if you had ShowDeckRightClickMenu=Yes in Quickplay.ini, the feature would be disabled. This is now working correctly in Burli 225t.

Audioupload.ini Auto Dispatch audio only        

Starting in Burli 225s, if an Auto Dispatch has been set up using Audioupload.ini, Burli will only send the Audio clip even if there is Text included in the story. Previous to this version, Burli would show an error that text is included in the story and not upload the file.

 

FEATURE: .S48 file format supported for import

Starting in Burli 225s, Burli is able to open .s48 files which are a proprietary MP2 file used in certain automations systems. You are now able to Open > External File or Drag and Drop these files to your Work Folder. AUDIPT engines in Newswires 2 tab will also work with these files.


Improved Logging for the Internal Newswire dispatch

Starting in Burli 225s, we now add a log event when uploading to Internal Newswire fails via UNC method. Previous to this version, we only logged failures when using the FTP method when uploading stories.

FEATURE: Microsoft SQL Database supported

Assignments, Archive, Contacts and Audio Logger supported. MySQL to MSSQL data migration options available.

Please contact Burli Software for more information..

Auto Dispatch (audio) freezes for text only stories

Starting in Burli 225r, we have added error checking logic to the Auto Dispatch function. Previous to this version, if an item arrives which meets the Auto Dispatch Filter criteria, Burli would try to send the item regardless of the content. This would cause issues if trying to send and audio cart to an automation system but the story did not contain any audio. We now check if the item is going to an audio file to make sure that it contains audio or reject it if no audio is included. Any Auto Dispatch locations which do not require audio are not affected by this change.

 

Display "Events and Hours" by default when opening the Audio Logger

Starting in Burli 225q, when a user opens the Audio Logger, the default is to show "Events and Hours". Previous to this version, Burli would show "Events Only".

 

WideOrbit dispatch displays incorrect message on the ticker

Starting in Burli 225m, we have fixed a ticker message that is shown when dispatching to WideOrbit automation. We have fixed the ticker message “Burli>Scott-sent ok” to “Burli>WideOrbit- Sent ok”. This is only seen when using the wideorbit.ini setting: UseThreadToCopy=Yes

FEATURE: Dispatch attachments using Burli Internal Newswire

Starting in Burli 225L, it is now possible to send XML stories with an attachment (i.e.photos, pdf, video) to one or more locations. This mechanism uses the Newswire Server configuration where each location can be set up. For each Web location, the name of the  each web location must begin with an * (asterisk):

 

 

This way, the Internal Newswire can also be used.  If an attachment is added to an Internal Newswire story, it will not be see inside of Burli.

 

There is a new setting to enable this function in MAIN.INI:

 

[Newswire Server]

InternalNewswireAttachment=[Yes|No]~[Right Click Menu Name]~[Default Attachment file path]~[Dispatch Server]

 

"Yes" to turn on this new feature. No by default.

 

The next three settings are optional:

 

[Right Click Menu Name] = The name of the dispatch in the menu. Default setting is “Exporting as Internal Newswire with Attachment”.

[Default Attachment file path] = The default location for attachments. This could be a local or network location.

[Dispatch Server] = The server which will send the data. The default is the same DefaultServer specified in your [Newswire Server] section.

 

Example:

InternalNewswireAttachment=Yes~Export to Web with Attachment~\\Media Server\Pictures~Server1

 

Once this has been enabled, users can Right Click on a story and select “Export to Web with Attachment”

 

 

The next window will open to the Default Attachment file path where the user can select one attachment and press OK.

 

The next window will allow the user to select one or more of the Web Locations:

 

 

Once the user clicks on OK, the story with its attachment will first be copied to the Burli Server before they are then uploaded to the destination(s).

 

All files will have unique file names and will be purged according to the Purge settings in [Newswires Server].

 

Westwood One capture supports multiple categories

Starting in Newswires.zip version 2.34, Burli can support the Westwood One news stories which include multiple categories.

The category information is now being stored in the XML files as <itunes:keywords> data where multiple categories are allowed. In Burli a single story which is both “US News” and “Sports”, the same story will  now show up in both filters. These filtering changes may not be seen for stories which were ingested before you upgrade to the new newswires.zip version. A Westwood One filters file  is available from Burli Support for importing into your system. If you already have a previous version of Westwood One filters, you should delete those before importing the new filter file.

DOWNLOAD: newswires2-34.zip and WestwoodOneNewsFilters-2.dta

Urgent story flag for PAP NewsML

Starting in Newswires 2.33, we are now showing the PAP NewsML Priority 1 & 2 stories as Urgent by flashing the stories in the ticker when they arrive. They can also be filtered with the letter “u” in the Priority field.

DOWNLOAD: newswires2-33.zip

Quickplay progress bar for timed events

Starting in Burli 225h, we have fixed an issue where timed events in the Quickplay decks were playing fine but the progress bar was not displayed. This is now working correctly and the progress bar shows for all events.

FEATURE: Westwood One News feed

Starting in Burli 225g and Newswires2-32.zip, we support the Westwood One News feed. You will find the Westwood One news on the Newswires2 tab.

DOWNLOAD: Newswires2-32.zip and WWOneNewsFilters.dta

 

You will have to add the URL by clicking Install and then adding their URL

:

 Be sure to change the Refresh Rate to your desired frequency and Press Add

If you have been given a Filter file for this newswire (WWOneNewsFilters.dta), you just need to go to the Filters tab in Config –> Program Setup and right click on the In-Queue and select Import.

 You will then have the following Filters in your In-Queue.

 

You will have received a Username and Password for this newswire. That information goes into MAIN.INI in your [Newswires] section:

[Newswires]

RSSAuthentication##=228,1~username~password

 

Where ## is the next RSSAuthentication number in the list. For example:

 

RSSAuthentication3=228,1~username~password

 

You should also add a SchemeLookup for this newswire for it to be displayed correctly:

 

SchemeLookup##=228,7

 

Where ## is the next available number in your list of SchemeLookup entries. For example:

 

SchemeLookup12=228,7

 

Burli should be restarted after all of these changes.

 

FEATURE: CNN Wire feed

Starting in Burli 225g and Newswires2-32.zip, we support the CNN wire feed. You will find the CNN Wire news on the Newswires2 tab.

DOWNLOAD: Newswires2-32.zip  and CNNWireFilters.dta

 You will have to add the URL by clicking Install and then adding their URL:

Be sure to change the Refresh Rate to your desired frequency and Press Add.

You will have received a Username and Password for this newswire. That information goes into MAIN.INI in your [Newswires] section:

 

[Newswires]

RSSAuthentication##=227,1~username~password

 

Where ## is the next RSSAuthentication number in the list. For example:

 

RSSAuthentication3=227,1~username~password

 

You should also add a SchemeLookup for this newswire for it to be displayed correctly:

 

SchemeLookup##=227,7

 

Where ## is the next available number in your list of SchemeLookup entries. For example:

 

SchemeLookup12=227,7

 

To add a Filter for this newswire, go to the Filters tab and add a New Filter with the Source as: “CNN WIRE RSS”

 

 

Burli should be restarted after all of these changes.

Display issue with the original file audio file after RMS or TimeStretch

Starting in Burli 225f, we have fixed a display issue with the original audio file in the Single Track Editor after editing it and then either RMS normalizing or TimeStretching. Previous to this version, the original audio clip would appear to lose its edits and return to its original length. This issue is now fixed and the original audio clip retains all edit points.

Default RMS value changed to -20db

Starting in build 225e

 

Story Search (Finder) dialogue displays Filters in same order as InQueue

Starting in Burli 225d, we have improved the Filter dropdown window in the Finder. Now all Filters are shown in the order in which they appear in the InQueue and all sub filters will be indented from the parent filters.

Auto Dispatch with body search Filters issue

Starting in Burli 225c, we have fixed an issue when using the Auto Dispatch function with Filters that use a body search to filter the stories. This is now working correctly.

Unedited version of audio sent to Internal Newswire

We have fixed an issue starting in Burli 225b where audio that has been edited in the Single Track editor and then directly dispatched to the Internal Newswire would not include the edits and instead send the original audio. This is now working correctly.

TCPServer (Chat) Purge log files

Starting in TCPServer 7.2, we now support the ability to purge old log files. Purging can be configured in the Settings.ini file as shown below:

[Logging]

Enabled=Yes

Filepath=C:\LogTest\Event

ServiceFilepath=C:\LogTest\Event\ServiceLog

PurgeLogDays={m}

Improved TimeStretch audio quality

Starting in Burli 225a, we have updated the code used for the TimeStretch feature which has resulted in much better sounding audio files. This feature requires the MAIN.INI setting:

 

[Startup]

TimeStretch=Yes

FEATURE: Secondary IRN XML Newswire

Starting in Burli 224z and Newswires 2.30, Burli can support TWO IRN XML feeds. The new one is called “IRNXMNL2” which functions exactly like the IRNXML newswire does. To Filter this newswire, be sure to use “Wire:IRN-XML2 (UK)” as the Source.

 

FEATURE: Improve the BuildAudioTextStory feature with Append

We have improved the Build Text + Audio feature starting in Burli 224x. Previous to this version, once you had added one or more clips to a story, it was not very easy to add additional clips. Now it is just a matter of clicking on the audio clips (s) that you want to add plus the Text + Audio story, then right-click and select “Build Text + Audio Story” and the clips will be appended to a new copy of the story.

FIXED: Story order changed unexpectedly when dragging between Scripts

We have fixed an issue when dragging and dropping a list of items from one folder or script/rundown to another. Previous to this version, the order of the items was not always kept. Starting in Burli 224x, we now keep the original order after copying.

Flatline audio waveform when editing long audio files

In Burli version 224w, we have fixed an issue when editing audio longer than 71:34. Previously, when a user cut audio from a long clip which left over 71:34 remaining, the waveform would show a flat line after the edit point even if there was audio there. This is now working as expected with any length audio file.

Logger sessions created with blank names (missing validation)

Starting in Burli 224v, we now ensure all Audio Logger Sessions are named.

Previously, a user could click on New in the Recording Sessions window and then press OK which would create blank session.

FEATURE: Rearrange audio clip order in a story

Starting in Burli 224v, we have added the ability to swap the order of clips in a story. The story must be either in your Work folder, a Network Folder or in a Script and contain at least two clips. The function is called when you right-click on a Clip holder where you will then be given the choice to swap positions with the other clip(s) position.

legacy.jpg

FEATURE: Internal Newswire dispatch window | Display category value in 'category display name' field

Starting in Burli 224v, we now display the Category and Urgency in both the picker window and the window to the right. This makes it much easier to tell which category you are sending to if the name is longer than the allowed space in the picker window.

legacy.jpg

FEATURE: Support for the La Presse Canadienne newswire

We have added support for the “La Presse Canadienne” newswire starting in Burli 224u and Newswires 2.27. The newswire can be found in the Newswires2 tab as “LPC”.

 

legacy.jpg

Filters can also be added for this newswire by adding “La Presse Canadienne” as the Source.

 

In addition, you will need to add the following MAIN.INI settings:

 

[Newswires]

RemoveHtmlTagsFromWire=225

SchemeLookup##=225,8

 

Where ## is the next available number in your list of SchemeLookups.

FEATURE: Canadian Press (Audio) Internet Delivery via FTP

(doc version 4)

Starting in Burli 224t, we fully support the Canadian Press Audio feed. The new Canadian Press XML format includes both Text + Audio. In Burli, both items will arrive as a single Story.

Minimum requirement is Burli 224t and Newswires 2.26.

This feed will require the FTP site information and Username and Password provided by the Canadian Press. Please contact them if you do not already have this information.

DOWNLOAD CanadianPressAudioFiltersV2.dta filters template

DOWNLOAD: LaPressCanadienneFilters.dta filters template

 

This document will show you how to switch the BN newswire to the FTP capture method as well as adding the new Canadian Press Audio Feed. Prerequisites are the following:

 

 

Setting up the BN Text feed

You will require the FTP site and Username and Password information from the Canadian Press for this which will be supplied to you. Please contact the Canadian Press if you do not receive this information.

To switch your existing BN serial feed to the FTP feed, follow these steps:

  1. If you are currently receiving the BN Newswire on the Newswires1 tab, please remove it.
  2. Go to Config > Program Setup > Newswires 2 tab and double-click the BN Newswire

  1. Change the method from COM Port to Files. Select FTP folder and then enter your FTP Server address, Username and Password.
  2. The files are sitting on a Canadian Press FTP Server and holds 24 hours of stories. To prevent a flood of old stories, you should check the “Files newer than” and specify 1 hour. Customers in Atlantic Canada should specify 2 hours. Customers in in the prairies or BC should leave the box unchecked. You do not have to check any of the other checkboxes or enter anything into the “File Filters:” field.
  3. Your existing BN Filters will work just as they did in the past. You should see the new stories coming in within a few seconds which should look exactly the same as before. If you want to improve the look of the feed, you can add the following SchemeLookup setting to your MAIN.INI file:

[Newswires]

SchemeLookup##=2,23

Where ## is the next available number in your list of SchemeLookups.

*If you are having issues with no stories or only a couple of stories being received, try turning on the “Passive mode” checkbox.

Setting up the CP Audio feed  

The new Canadian Press Audio newswire includes both Text + Audio. In Burli, both items will arrive as a single story with the audio in a Clip holder of each story. The minimum requirement for this is Burli 224t and Newswires 2.28.

This feed will require your unique Audio RSS URL from the Canadian Press. The Canadian Press will send this information out to you.

Replace your Username and Password in the following:

The URL for CP Audio in French and English is:

http://USERNAME:PASSWORD@audio.cp.org/productionaudio/rss/all.xml

The URL for English ONLY Audio is:

http://USERNAME:PASSWORD@audio.cp.org/productionaudio/rss/english.xml

The URL for French ONLY Audio is:

http://USERNAME:PASSWORD@audio.cp.org/productionaudio/rss/french.xml

  1. To add this new feed, you should go to the Newswires2 tab and scroll down to the CP XML newswire and press the Install button.

  1. Enter a friendly name that identifies this feed to System Administrators and your unique URL using the Username and Password provided to you by Canadian Press.

  1. Change the Refresh rate to every 1 minute
  2. Be sure to press the Add button before clicking OK, otherwise your new settings will not be remembered.
  3. You will need to add Filters for this feed to the Burli filter tree. If you have a supplied Filter file from Burli or CP, please go to the Filter tab and right-click on the InQueue node at the top of the tree and select Import and browse to the *.dta file. (CanadianPressAudioFiltersV2.dta and LaPressCanadienneFilters.dta)

If you do not have a filter file, you can add a new Filter simply by using “Wire: CP XML” as the Source.

What about the old audio feed? You should now be able to turn off the Background Audio Capture on the Burli Audio tab if CP is delivering all of the feeds you expect on the CP Audio newswire. You can just uncheck both Left and Right channels to disable the old feed recordings.

Network Folder orphans cleanup

Starting in Burli 224p, we have added the option of removing Network Folders even if they contain some orphaned files.

 

recycle bin and purge.jpg

 

*Supported for systems using the ‘NetworkFolderRecycleBin’ feature in build 224q or higher.

To enable this feature, a MAIN.INI setting is required as follows:

 

[Startup]

FolderOrphansCleanOption=Yes

 

The default value is No.

FEATURE: Cartchunk next marker | Master Control (RCS.INI)

We have improved the cart chunk header for the SEC1 (next marker) with RCS.INI dispatched carts. Starting in Burli 224o, if for example a cart has been specified to be 90 seconds long with allowance between 89-91 seconds and the cart is only 89.2 seconds long, the SEC1 marker will be set at 89.2 seconds.

FEATURE: Option to rename the “Export to Internal Newswire” dialogue

Staring in Burli 224n, you now have the ability to rename the “Export in Internal Newswire” dialogue to anything that you want.  For example, you could have it instead say something like, “Publish to all stations”

The setting is:

[Newswires]

InternalNewswireMenuName=[Enter custom menu name here]

Example

InternalNewswireMenuName=Publish to all stations

Without this setting in MAIN.INI, it will default to “Export to Internal Newswire”.

FEATURE: Support for the PAP NewsML newswire

Starting in Burli 224L and Newswires 2.25, Burli can support the PAP NewsML newswire.

FEATURE: Do not add the Time and Date to the Slug on Mix down

Starting in version 224m, we have added the option of not appending the Time and Date to the slug of a mixed down audio project. There is a MAIN.INI setting required for this:

[Startup]

MixdownSimpleSlug=Yes

The default value is No. This will remove the time stamp appended to a Multi-Track Mix-down in the work folder.

TV Prompter +/- keys not working

We have fixed an issue with stopped the +/- keys in TV Prompter mode. In Burli 224k, we have enabled the keys again.

TV Prompter F7/F8 keys not working

We have fixed an issue which disable the F7/F8 (Previous/Next story) buttons. In Burli 224j we have enabled the buttons again.

FEATURE: Option to rename the Audio Upload dispatch

Starting in version 224i, you can change the standard “Audio Upload:” dispatch to anything you like. The audioupload.ini file has one or more [Group#] where you can change the name of the dispatch.

[Group1]

Name=[group name]~[group name prefix]

Example:

[Group1]

Name=Traffic Reports~Send to Web

Where "~[group name prefix]" is where you need to put the name you want to see in the Dispatch window. The value of "group name prefix" overwrites the previous fixed string "Audio upload:". If it's omitted, Burli behaves exactly as previously showing "Audio upload: “ in the Dispatch window.

Search Filters not available via the Burli Web Server

We have fixed an issue which would hide all Search filters via the Web Browser. Starting in Burli 224g, all Search Filters are visible again.

Filter arrangement (up/down) NOT saved

Starting in Burli version 224f, you can arrange the Filters into any order that you wish whether they are single Filters or Parent/Child Filters. Previous to this version, single Filters were always placed on the bottom of the Filter tree and Parent/Child Filters were always on the top. This new arrangement requires a MAIN.INI setting to be added:

[Startup]

InQueueFilterSort=No

This is Yes by default.  If it is Yes, Burli behaves the same as before. With this set to No, you can arrange the Filters into any order that you wish.

FEATURE: Support for the Twitter Search API

Starting in Burli 224f, Burli now supports the Twitter Search API which is useful for following hash tags (e.g. #burlisoftware) or any mentions of specific words, #hashtags or accounts. Previous to this version, Burli could only support the Timeline API. The following is an example of a Twitter Search URL:

This link will pull in all Tweets which contain the #hashtag “#vancouver”

https://api.twitter.com/1.1/search/tweets.json?q=#vancouver

If you wanted to search for two (or more) words (“vancouver traffic” in this case) , you need to separate each word with %20 as in the following:

https://api.twitter.com/1.1/search/tweets.json?q=vancouver%20traffic

Here are the details of all possible arguments which can be included in a Search API request:

https://dev.twitter.com/docs/api/1.1/get/search/tweets

The following is the limitation as stated on Twitter’s web site:

Twitter's search is optimized to serve relevant tweets to end-users in response to direct, non-recurring queries such as #hashtags, URLs, domains, and keywords. The Search API (which also powers Twitter's search widget) is an interface to this search engine. Our search service is not meant to be an exhaustive archive of public tweets and not all tweets are indexed or returned. Some results are refined to better combat spam and increase relevance. Due to capacity constraints, the index currently only covers about a week's worth of tweets.

FEATURE: WebServer | View Network folder stories in Modified Date order

Starting in Burli 224e, Burli Web Server users can see the items contained in Network Folders by their modified dates. This is handy for users who need to see the latest items at the bottom of the list of items. The following MAIN.INI setting is required to enable this FEATURE:

[Startup]

DisplayWebNetworkFoldersByDate=Yes/No

The default value is No. If the setting "DisplayWebNetworkFoldersAlphabetically" is on as well, this setting is ignored.

FEATURE: Popup alerts for Urgent stories based on their newswire ID

Starting in Burli 224d, Burli is able to show a popup alert message box when an urgent story arrives in the InQueue depending on their newswire ID. This is useful for any urgent Internal Newswire or InHouse items that you want to have all workstations display a popup message but suppress any urgent story popup messages from any other of your newswire sources. To make this feature work, you will need to add the following MAIN.INI settings:

[Startup]

PopupOnUrgentStories=Yes          (required)

UrgentStoryPopupWireID=[wireID#1],[wireID#2],etc

For example:

[Startup]

PopupOnUrgentStories=Yes

UrgentStoryPopupWireID=5,214

This example will show a popup message box for only InHouse (5) and NAAD Emergency Alerts (214) only.

cid:image005.jpg@01CF9F7B.25CEB010

You can find each of the  Wire ID#s on the Newswire 2 tab as you click on each Newswire.

Audio Logger PostRecAction confuses sessions that stop at the same time

Starting in version 224d, we have improved the logic with PostRecActions and the clock based Audio Logger sessions. In some very specific instances where sessions stop and start at the same time and included a Port Record Action, some sessions failed to record because the STOP command was issued to BOTH the session that just started and the one that is supposed to stop. The logic has been improved to stop the correct session before starting the next one.

FEATURE: "Exclude" Boolean Filter/Search function

We have changed the logic slightly for boolean Filtering and Searching. Previous to Burli 224a, Burli was inserting a leading space if it followed a !(not) argument which is not being added anymore. This would cause issues if the search work began a sentence for example. Because of this, the user may have to add a space after their word. For example, “michelle !obama” will display all stories which contain “michelle” but not “michelle obama”.

FEATURE: Script Template Audio immune to purging

Starting in Burli 223z, you can now add audio elements (Intros, Sounders, etc) to Script Templates. All Scripts that are generated afterwards will also contain those audio elements. It is just a matter of dragging and dropping the audio items into your Script Templates from either the InQueue or a Local or Network Folder as you would any other item. Any of the referenced audio files will not be purged until there are no more references to the files in the Script Templates or the Templates themselves are deleted.

Burli crashes after dropping a Faded out track to Quickplay deck

We have fixed an issue when a Fade Out is applied to the end of an audio clip in the Work folder and it then pushed to a QuickPlay deck and played, Burli would crash. This is now fixed and working properly.

FEATURE: Base64 encoded Email do not display correctly

Starting in Burli 223v, we have added the ability or Burli to display Base64 encoded HTML emails. Burli will now convert the email to the default code page of the operating system.

FEATURE: Shortcut key to Start and Stop the Background Recorder

Starting in Burli 223u, there is now a shortcut key to Start (CTRL+K) and Stop (CTRL+SHIFT+K) the Background recorder. This is useful is you want to record a newscast where you can play a sounder underneath the newscast and also playback and hear all clips included in the stories in real time. The minimum requirement for this feature is that you have the Background audio capture recorder setup as the same Audio format and Sample rate as your default settings and the LEFT Channel set for “User” for the Capture method. Of course you will also need to set the Mode to “Background audio capture” and the correct sound card input for recording.

cid:image001.png@01CF9B54.AFE5E0F0

Once this is setup correctly, the shortcut keys will do the following:

CTRL+K will start the recording

cid:image002.png@01CF9B54.AFE5E0F0

CTRL+SHIFT+K will stop the recording

cid:image003.png@01CF9B54.AFE5E0F0

…and then Burli will take you to the finished recording in the Single Track Editor.

FEATURE: Refresh VN Filter tree

Starting in Burli 223t, there is now the ability to auto refresh any VN connection that you are currently connected to. If you are looking at a Filter at another location using the VN connection, the Filter will refresh at the rate set in MAIN.INI. Your upper window tab will always have the newest item at the top of the list and your focus will be taken to that item as the window is refreshed. To enable this feature, the following MAIN.INI setting needs to be added:

[Startup]

RemoteVNInQueueRefresh=##

Where ## is an integer, in minutes. The default value is 0. If the value is 0, this feature is disabled.

FEATURE: WideOrbit Automation Dispatch

Starting in Burli 223s, there is now a WideOrbit Dispatch feature. All WideOrbit dispatch locations that you have configured in Burli will be shown as “WideOrbit:…”. The dispatch function is configured with a wideorbit.ini file which should be located on the Burli Root Path in the ~\Burli\Settings folder.  It uses many of the Scott Automation system settings so if you are currently using scott.ini to dispatch to WideOrbit, you can either copy and paste all of the [Group] settings into a new WideOrbit file or simply rename your current “scott.ini” file to “wideorbit.ini”. WideOrbit will by default not include the “SP preceding the cart numbers which is the default for Scott Automation carts. There is a built in function code in Burli to edit your WideOrbit configuration file from any Burli workstation with CTRL-F6 > wideorbit > <Enter>. This should bring up your default text editor with your current wideorbit.ini file. Previous versions of Burli would not dispatch to all locations. Please update to version 223s if you are using this Dispatch feature.

If you are using auto dispatch to wide orbit, please do not use the ‘AutoDispatchAudioFormat’ setting in the dispatch.ini as this will corrupt the audio file headers.

Background Audio capture | wrong playback length in third party software

We have fixed an issue where background audio recordings in MP2 format were given the incorrect file header information. This would result in external audio players reporting the wrong time and audio cut off. This is now fixed in version 223r.

FEATURE: Support for the RadioVoodoo Service

Starting in Burli 223q, Burli can ingest the RadioVoodoo service directly into the InQueue. The newswire is found in the Newswires2 tab and can use either UNC or FTP location. This also requires Newswire2.22.

HTML Emails showing with a Subject but no Body

In Burli 223p, we have fixed an issue where HTML formatted emails would show up in Burli with the Subject line but no Body. This was being caused by an unusually formed email header which Burli will now parse correctly.

FEATURE: Open default Web Browser when clicking on links

Starting in version 223o, we have added the option of opening a link using the default Web Browser on the workstation instead of using the built in Internet Explorer engine used by Burli. With this option turned on, when a user clicks on a web link in a story or the [full story] link in RSS or Twitter feeds, the contents will be opened using the default Web Browser. The option is turned on in MAIN.INI with the following setting:

 

[Startup]

UrlOpenInDefaultBrowser=Yes

FEATURE: Disable F2 key in QuickPlay

When using Quickplay, the F2 key will play the currently queued Quickplay deck and queue the next deck. If the user has a Script open in Prompter mode, the prompter will start scrolling instead. With the following QuickPlay.ini setting, the F2 key can be disabled in QuickPlay:

[QuickPlay]

PreventF2KeyPlay=Yes

The default is no

FEATURE: Improved audio quality of low sample rate PCM audio files

Starting in Burli 223m, we have added the ability to use the QuickTime audio engine to import PCM audio files below a specific sample rate. By default Burli will send all PCM audio files to its codec to be automatically converted into the workstation/station’s default audio format. Some users have found that with some 8kbs PCM files, the audio quality sometimes sounds a bit scratchy once it has been imported into Burli when using the default codec. We have added a setting which will allow the QuickTime codec to do the conversion instead for all PCM files which have a sample rate below a set threshold. This feature requires QuickTime and the Burli QuickTime DLL to be installed on the machine which is ingesting the files. There is also a new MAIN.INI setting where you can specify the sample rate threshold:

[Startup]

QtMaxPCMSampleRate={n}

n is an integer number in Hz. The default is 0 which effectively turns the feature off.

Example:

[Startup]

QtMaxPCMSampleRate=8000

This example will send all PCM audio files with the sample rate of 8kbs (8000) or below to the QuickTime codec.

FEATURE: WideOrbit Automation Dispatch

Starting in Burli 223L, there is now a WideOrbit Dispatch feature. All WideOrbit dispatch locations that you have configured in Burli will be shown as “WideOrbit:”. The dispatch function is configured with a wideorbit.ini file which should be located on the Burli Root Path in the ~\Burli\Settings folder.  It uses many of the Scott Automation system settings so if you are currently using scott.ini to dispatch to WideOrbit, you can either copy and paste the settings into a new WideOrbit file or simply rename your current “scott.ini” file to “wideorbit.ini”. There is a built in function code in Burli to edit your WideOrbit configuration file from any Burli workstation with CTRL-F6 > wideorbit > <Enter>. This should bring up your default text editor with your current wideorbit.ini file.

Deleting users from Burli security causes freeze/crash

In Burli 223j, we have fixed an issue where Burli would freeze or crash when deleting users. This was caused by resources such as network folders were removed before the user(s) who reference that material are removed.

Burli crashes if entire audio in the Single Track editor is highlighted and deleted

We have fixed a an issue in the Single Track editor which would cause Burli to crash if the user highlighted the entire waveform and pressed Delete or Cut. Starting in Burli 223i, Burli will now send the entire cut to the recycle bin if the entire waveform as been highlighted and deleted.

Support for the AFP (EAA) newswire

The AFP newswire has changed their format and Burli 223h and Newswires 2.20 now supports this new format. Users may notice that the correct blue logo is now shown in the InQueue and Filter.

FEATURE: HTTPS support for Twitter

Starting in early 2014, Twitter will no longer support plain text HTTP connections and will instead support HTTPS connections only. Starting in Burli 223b, Burli has added a command to convert all of your existing HTTP Twitter URLs in Newswires2 to the required HTTPS format.

The following command will convert your URLs: CTRL-F6 > update_twitter_url

You will then be shown a dialogue box with the number of Twitter URLs that have been changed. A Twitter URL should then look like this :

https://api.twitter.com/1.1/statuses/user_timeline.json?user_id=screenname

FEATURE: Rotation items in QuickPlay

Starting in Burli 223c, Burli supports a rotation of clips much like a playlist. Burli can play clip one after the other and stop or continue to rotate clips depending on the settings. In Quickplay.ini, existing settings could be like this

[QuickPlay]

File20=RotationTest-title~RotationTestSection

[RotationTestSection]

File1=solobell.wav~solobell

File2=\\vsburdc01\office\Miscellaneous\QuickPlayTest\4min.wav

File3=topid.wav

The new settings look like:

[RotationTestSection]

NewRotationMethod=Yes

File1=solobell.wav~solo bell~Yes

File2=\\Server01\QuickPlayTest\4min.wav~4 min~Yes

File3=topid.wav~~yes

File4=D:\Burli\QuickplayDrop\playlist2.ini~~yes

1.           "NewRotationMethod" is required for auto rotation play. No by default to keep backward compatibility.

2.           File[n]=[FileName]~[Display name]~[Yes to auto play next] or  File[n]=[playlist.ini]~[Display name here overwrite the name defined in playlist.ini]~[Yes to play next]

3.           The syntax of [FileName] or [playlist.ini] is same as before, which supports both absolute path and relative path.

4.           Each playlist.ini contains only one audio file. i.e. only "File1" in [playlist.ini] is used.

To restart the Rotation list from the beginning,  go “Offline” and then back “Online” with a QuickPlay deck. This is useful for auditioning the rotation elements or in case of misfiring a cart.

FEATURE: Boolean InQueue Searches and Filters

Starting with version 222x, Burli can now perform Boolean InQueue Searches and also add Boolean arguments to Filters. This feature supports Boolean "OR","AND" and “NOT" operations by using "|", "&", "!" respectively. Any white spaces in the search text are valid. For example, "do" hits would include the story containing a string "download", while "do " would not.

An example search could be, “NHL &canucks” … to match all stories which include both “NHL” and “canucks”

OR:

“Tom|Dick&Harry|Joe!Blough” … to match all stories containing “Tom” or containing both “Dick AND Harry”, or containing “Joe but NOT Blough”.

This feature requires a new main.ini setting as follows,

[Startup]

NewInQueueSearch=Yes

The default value is No.

If the number of stories in the InQueue is very large, it will slow down Burli's launch speed if any Filter’s search criteria includes any Boolean arguments; "&", "|", "!". A plain string as a Filter’s search criteria will have no such effect. The launch speed of Workstations which are Fastload clients will remain the same.

As the name of new setting indicates, this feature only affects InQueue Filter configuration and InQueue search. Other searches like Scripts, Archive and Contacts are not affected.

FEATURE: Show success of failure when sending an Internal Newswire story

Starting in Burli 222p, we now show success or failure when sending an Internal Newswire story along the ticker of the workstation.

cid:image004.png@01CF9B54.AFE5E0F0

Audio quality improvements for the TimeStretch feature

We have improved the quality of the audio when performing a Time Stretch to a stereo audio file.

Adding an audio clip to a New MultiTrack project freezing

We have fixed an issue with Burli where if the user creates a new Audio Project and drops items into the project, Burli would freeze.  This was seen in only on Windows XP workstations using the HL versions of Burli 222r – 222d. This issue is now resolved.

FEATURE: Support for any character set in Twitter and RSS

Starting in Burli 223d, we have added support for Twitter feeds in any character set. Twitter sends Unicode characters using a special string which is then converted to the actual letter. Burli can now

support English plus one non-English language Twitter feeds/RSS.

The new MAIN.INI setting is:

[Newswires]

UTF8to=[character set name in HTML],[Code page - optional]

For Example:

[Newswires]

UTF8to=big5,950

[Character set name in HTML] information can be found on the following webpage:

http://msdn.microsoft.com/EN-US/library/windows/desktop/dd317756%28v=vs.85%29.aspx

You must use the name exactly as it appears on this webpage

[Code page] is optional. By default, Windows OS' default code page is used if this setting is omitted. We recommend leaving this blank and using the system's default code page first. If Burli's not displaying Twitter feeds correctly, then add the [Code page] information.

An example of some languages are:

Latin 1

UTF8to=iso-8859-1

Big 5

UTF8to=big5,950

Eastern European

UTF8to=iso-8859-2,28592

Please note, this setting "UTF8to" will overwrite the following existing MAIN.INI settings:

[Newswires]

UTF8toISO88591=YES/No - default Yes

UTF8toISO88592=YES/No - default no

UTF8toBig5=YES/No - default No

If "UTF8to" and any one of the above three settings exist, "UTF8to" is used instead. This will affect all RSS/XML feeds.

Burli crashes if entire audio in the Single Track editor is highlighted and deleted

We have fixed a an issue in the Single Track editor which would cause Burli to crash if the user highlighted the entire waveform and pressed Delete or Cut. Starting in Burli 223i, Burli will now send the entire cut to the recycle bin.

FEATURE: Support for many Email audio attachments

Starting in Burli 223h, Burli Email capture can handle many audio attachments. Previous to this version, Burli was only able to handle the number of Clip Holders set in Burli. By default, this is 3 so if someone would email 5 clips, the last two would be lost. In version 223h and above, Burli will break the email into multiple parts in the InQueue to handle every audio attachment and will show in the title which part of a multi part email the item is from. If you receive 9 clips but are only showing 3 clip holders, the email will be broken into 3 separate emails.

cid:image005.png@01CF9B54.AFE5E0F0

Deleting users from Burli security causes freeze/crash

In Burli 223j, we have fixed an issue where Burli would freeze or crash when deleting users. This was caused by resources such as network folders were removed before the user(s) who reference that material are removed.

Improved Focus using the keyboard

We have improved the focus when using the keyboard when navigating the InQueue Tree.

FEATURE: Sending Tweets using https

In Burli 221r, we have changed the method from http to https for posting Tweets to the Twitter website to resolve an issue that some customers were seeing when sending Tweets.

FEATURE: Compress files to MP3 on Internal Newswire

We have reduced the number of messages that are displayed during sending from 5 to 3. We now show "Start", "50%", "Done." along the ticker when a file is being sent to the Internal Newswire.

FEATURE: Shorten URLs in Tweets

Starting in Burli 221p, Burli has the ability to send shortened URLs in Tweets. As the user inputs a valid URL, when they type either “http://” or “https://”,  Burli will reserve 22 or 23 characters regardless of the length of the URL. Once the Tweet has been sent to Twitter, it will automatically be converted to a shortened URL. (e.g. http://news.nationalgeographic.com/news/2013/06/130621-summer-solstice-2013-longest-day-sun-earth-space-science/ will be shortened to http://t.co/Mt0uWpcHaM) Burli is not verifying the URLs as they are input so be sure to verify the URLs before sending.

Twitter no longer shows the Sender in the Ticker or InQueue

Burli is now showing the Twitter account of the sender in the Slug and on the ticker correctly. This information was not showing correctly after the switch to the latest Twitter API 1.1.

FEATURE: Support for Report-IT mobile apps from TieLine

In Burli 221t, we have added the ability to ingest stories submitted from the Report-IT application from TieLine. The "Report-IT" Newswire is found under the Newswires2 tab. In the File Extension field, use a | to separate each file type. For example: wav|m4a|aac.

You can add the “Report-IT” newswire in Newswires2 by clicking “Install”.

cid:image006.jpg@01CF9B54.AFE5E0F0

Set the UNC Folder or FTP settings to the location where the users will upload their stories.

cid:image007.jpg@01CF9B54.AFE5E0F0

In the File Filters, make sure it is set to: *.xml

For the Audio File Extension field, enter the file extension you will be ingesting or to ingest both WAV and M4A formats, enter: wav|m4a

You should then add a Filter in the InQueue for the Report-IT newswire:

cid:image008.jpg@01CF9B54.AFE5E0F0

Make sure to set the Source as: Wire: Report-IT

You will also have to set up your TieServer with the TieServer Console and turn on the Burli settings. If you are going to use Apple audio formats (AAC, M4A, etc) you will need to add QuickTime and the Burli QuickTime DLL to your capture machine.

FEATURE: Added metadata to Tieline stories

Burli now displays extra metadata in the Report-IT stories. The location name and a link to a Google map location are now included. Newswires 2.19 and Burli 222f is required for this feature.

cid:image009.jpg@01CF9B54.AFE5E0F0

Multi-track leaves orphan folders after audio files deleted

Burli is now properly removing old files and cleaning up Multi-track folders when they are deleted.

Multi track waveform not drawing correctly with live Audio Logger sessions

We have fixed an issue in 221u where previously, if the user drags a live Audio Logger session into the Multi track recorder, they would see a flat line waveform for one of the previous segments. This is now fixed and working as expected.

Burli crash on Right Click of a folder

Burli would crash when clicking on a blank space in a Folder but not on an item. This issue affects versions 221k – 221w.

Pressing F2 with only one QuickPlay deck causes an error

We have fixed an issue when a user has only one QuickPlay deck configured. If the user he presses F2 to play the deck for the first time only, an error, "An invalid argument was encountered." is shown. Any subsequent F2 presses will just play as per normal. This is now working correctly.

Long MP3s are sometimes cut off before the end of the file

We have found an issue with MP3 files being created either with Save As or Podcasts. If the files had long durations (30 minutes or more) and high compression ratios, the audio could sometimes be cut off a few seconds before the end. To prevent this issue, we have added an MP3 Padding option. The MAIN.INI setting is:

[Startup]

MP3Padding=Yes

FEATURE: Script and InQueue search improvements

We have improved the Search function for both Scripts and InQueue starting in version 222e. The interface no longer “freezes” and the user can now cancel the search at any time.

FEATURE: TimeStretch/Shrink

We have added an on/off switch for the Time Stretch/Shrink feature which is by default off. Starting in version 222h, if you wish you add this option to the workstations, use the following setting:

[Startup]

TimeStretch=Yes

No by default.

In Burli 221w, we have added the ability to Time Stretch or Shrink audio in the Single Track editor.  To perform the Time Stretch/Shrink function, the user needs to Right-Click on an audio file in the Work Folder and then choose, "Time stretch this audio...".

cid:image010.jpg@01CF9B54.AFE5E0F0

You will then be shown a window with the original file length in seconds. The user can then input the new length in seconds. The pitch of the audio will be kept and the limitation of the final audio is between 50% and 150% of the original file length.

cid:image011.jpg@01CF9B54.AFE5E0F0

cid:image012.jpg@01CF9B54.AFE5E0F0

The pitch of the audio will be kept and the limitation of the final audio is between 50% and 150% of the original file length.

cid:image013.jpg@01CF9B54.AFE5E0F0

The new file will be added into the Work Folder. The original audio file will be kept and the Time Stretched/Shrink audio will have the letters "-TS" added to the modified file name.

cid:image014.png@01CF9B54.AFE5E0F0

FTP PostRecAction issues

We have fixed an issue which caused an error in Burli when using an FTP location as a PostRecAction in the Burli Audio Logger. This is now working correctly.

Phantom Scrolling | AllowScrollDragging feature

We have fixed an issue where the Script story list appears to move by itself after an audio item is dropped into a Script clip holder. This is now working correctly.

FEATURE: Auto dispatch to OMT

We have added the ability to automatically dispatch to an OMT automation system cart based on the In-House filter that the audio is dropped into. Please contact Burli support for more details.

FEATURE: Ability to select the TIMER format in QuickPlay decks

We have added the option of displaying 12hour or 24 hour format in the QuickPlay decks. In addition, if you use more than one TIMER, each deck can display it own format. The new Quickplay.ini setting is:

[QuickPlay]

DeviceDeck#=TIMER|TIMER12|TIMER24

Where,

TIMER, same as current behaviour which uses the MAIN.INI setting

TIMER12, shows the timer in AM/PM format

TIMER24, shows the timer in 24 hour format

Hiding the Filter Tree loses focus on a Script Story in the Top window

We have fixed an issue when the user is looking at a Script story and then hides the Filter Tree. Previously, Burli would lose focus of the story but starting in 222i, the story focus is kept.

Drag Story into folder drops top bottom of Story list

We have fixed an issue introduced in 222g when a story dropped in a Script or Work Folder would always end up at the bottom of the list. In version 222i, this issue has been resolved.

Dispatching an MP3 file to OMT creates the wrong file extension

We have fixed an issue when dispatching an OMT cart in MP3 format where Burli would incorrectly add a .wav extension regardless of the audio format. Burli is now respecting the audio format chosen and creating OMT carts in MP3 format with the correct .mp3 file extension.

Telnet to a Burli Newswire Server causes a crash

We have fixed an issue of Burli crashing when a user opens a Telnet session to the same port that Burli uses for Internal Newswire Server (5658). Burli will now reject the connection.

FEATURE: Enhanced Auto Script generation

We have added the ability to specify one Burli machine which is responsible to auto generate the Scripts each day. This is done by adding the HASP ID of the machine that you wish to do this task. Without adding a HASP ID, every machine will try to create the Scripts at the specified time.

The new setting is:

[Scripts]

DaysFuture=4,Yes[HaspID]~HH:MM

Example:

DaysFuture=4,Yes1350539511~14:30

If the "HaspID" is present, only the computer with that particular hasp can run this feature. If "HaspID" is omitted, all machines are eligible.

cid:image009.jpg@01CF9B54.AFE5E0F0

FEATURE: Burli Mail link available in via the Burli Web Server

We have added the ability to read Burli Mail via the Burli Web Server. The user who logs into the Web Server will see a “Burli Mail” link at the top of the web page where they are able to read their Burli Mail. All stories are displayed and sorted by their modified time with the newest items at the top.

[Twitter]

This section controls the way that Burli functions with Twitter.

Function:

Starting in build 210w, this MAIN.INI [Section] and its settings adds “Send to Twitter” functionality to Burli. A Twitter message can be sent directly from Burli by highlighting text and either CTRL-Shift-T or Right-Click “Send to Twitter” on highlighted text or a story. The Twitter entry box will pop up with the highlighted characters auto filled or the contents of the story entered. The user can alternatively simply CTRL-Shift-T or Right-Click “Send to Twitter” and freely enter text into the pop up box. As the user types into the entry box, a “Remaining” counter is displayed which indicates the number of characters remaining for the Twitter message. The maximum number of characters in a Twitter message is 140. When you want to send the Tweet, press the “Send” button and a progress bar will be shown. If the user exceeds the 140 character limit, a negative number is displayed in the “Remaining” counter indicating the number of characters over the limit and the Send button will also be disabled. If no accounts are selected, the Send button will also be disabled. There is also the ability to send to multiple Twitter accounts at the same time by selecting the checkbox next to each name. You make the account checkbox(s) selected by default by adding the “Selected” field at the end of each entry. The current unauthorized connection limit is 350 requests or Tweets per IP Address per hour. The current OAuth connection limit is 450 per Twitter account per hour.

Syntax:

[Twitter]

Enabled=Yes

AccountManagement=[Yes/No]

Account1=[display name1]~[TwitterUser1]~[Password1]~[Selected/blank]

Account2=[display name2]~[TwitterUser2]~[Password2]~[Selected/blank]

Account3=[display name3]~[TwitterUser3]~[Password3]~[Selected/blank]

Account4=[display name4]~[TwitterUser4]~[Password4]~[Selected/blank]

Group1=[TwitterUserGroup1]~[Twitter account#(s)]

"Enabled=Yes" is the power-on switch for this feature. The default setting is "No".

AccountManagement=Yes/No (optional) is enables Twitter User rights based on the Burli Security group. If this is set to No or is not added, Burli will allow all users to send Tweets to any account listed. This feature is available starting in version 217z.

Account# must be in numerical order.

[display name#] is what the user will see to describe each account. They should not contain any of the following characters

< (less than)

> (greater than)

: (colon)

" (double quote)

/ (forward slash)

\ (backslash)

| (vertical bar or pipe)

? (question mark)

* (asterisk)

. (Period)

Group[n],[Security Group name] (optional) must be in numerical order. This links the predefined User Group in the Security tab to one or more Twitter accounts. Every member in a Group is allowed to send Tweets to specific Twitter accounts. The Security Group name must match the name of the Group in Burli Security exactly. Adding users to specific groups will allow them to send Tweets to specific accounts.

TwitterUser# is the Twitter account name.

Password# is an Twitter account password

“Selected” to select the account checkbox(s) by default is optional. No entry or a blank will not select the checkbox by default. Burli will remember the last selection at a workstation as long as Burli is not restarted.

Example:

[Twitter]

Enabled=Yes

AccountManagement=Yes

Account1=CBRD~CBRD123~CBRDpassword~Selected

Account2=CHAZ~ChazFan~Chazpassword~Selected

Account3=All Sport Radio~Allsportradio~sportpassword

Account4=All Talk Radio~AllTalkradio~talkpassword

Group1=NewsTeam~1

Group2=SportsTeam~2

Group3=OnAirTeam~3,4

Group4=Editors~1,2,3,4

Once you have added the Twitter section to MAIN.INI, you will need to Authorize Burli for each Twitter account to receive an OAUTH certificate for each account. Please restart Burli after adding the [Twitter] section before continuing onto the next steps.

Because there are a few steps involved, you first need to retrieve each OAuth certificate from Twitter. Once all of the tokens are all saved into Burli, you will not need to manually authenticate again.

In Burli, press CTRL-F6 > oauth and you will be presented with the following dialogue box.

cid:image015.png@01CF9B54.AFE5E0F0

You will also find that Burli has opened an Internet Explorer window with the following information:

cid:image016.jpg@01CF9B54.AFE5E0F0

“Twitter Username Here” will be your Twitter account name. Once you press “Allow” the following page will be shown:

cid:image017.jpg@01CF9B54.AFE5E0F0

Enter the Username and Password for the account and press “Allow”. The following page will be shown:

cid:image018.jpg@01CF9B54.AFE5E0F0

Type or Copy and Paste the PIN number given to you into the Burli dialogue box and then press OK.

The Twitter certificate will be saved for this account and will not require any further authentication.

If you have more than one Twitter account, do the same procedure above with each account. Burli will create a text file with the Access Token for each account and it will be saved to the Burli Root Path at (~\Burli\twitter). Each accounts’ file will be named as [display name].txt. example: All Sports Radio.txt. When you have completed the above authentication procedure with each account, you will not need to do it again.

Note:

If there are any errors during sending the Twitter message, it will be displayed in the progress bar. The error messages can be referenced on the Twitter website. (www.twitter.com)

Twitter has introduced a new “OAuth” method for sending Tweets directly from other applications. OAuth is an authentication protocol that allows users to approve applications to act on their behalf without sharing their password. Because of this new authentication method, we have had to change the way that Burli sends Tweets. There is an “Access Token” that is now saved to Burli which is responsible for all future authentications.

Because there are a few steps involved, the very first time that you send a Tweet from one of your Twitter accounts, it is recommended that you only send to one account at a time for the first send. Once all of the tokens are all saved into Burli, you will not need to manually authenticate again. The OAuth tokens can also be retrieved with CTRL-F6 “oauth” (without quotes).

Burli will create a text file with the Access Token for each account and it will be saved to the Burli Root Path at (~\Burli\twitter). Each accounts’ file will be named as [display name].txt. Example: All Sports Radio.txt.

FEATURE: Twitter API 1.1 improved support | Home Timeline

We have improved the support in Burli for the new Twitter 1.1 API which is being used starting on March 5th, 2013. Twitter’s support for the older API 1.0 will be slowly shut down after this date. Starting with Burli 220j and Newswires 2.12, Burli can take advantage of the newer limits allowed when checking for Twitter feeds with this new method. The new limit is 180 checks every 15 minute window per Twitter OAuth account. This means that you can now check 12 Twitter accounts once per minute in Burli. In addition, Burli also supports your Home Timeline as a Twitter feed. Please see the details below.

 

*For anyone who already has Twitter feeds coming into Burli, the URLs of each feed needs to comply with the new format.

 

*If you are already ingesting Twitter into Burli, to make the conversion easier, we have added a function to convert your Twitter feeds in Burli to the new format.***

 

The function is called with:

 

CTRL-F6 > update_twitter_url > OK.

 

Burli will then convert all existing Twitter links to JSON API 1.1 format and will show a confirmation box when it is done. A restart of Burli is recommended once the links have been converted. Once you have converted the URLs, you can expect to see all Tweets from all URLs to be ingested again since this is actually a new source of data in a slightly different format.

 

 

*The new format also requires a new SchemeLookup which needs to be added/modified in your MAIN.INI file.

 

[Newswires]

SchemeLookup##=188,22

 

Where  ## is the next available number in the list of SchemeLookup entries.

 

 

Twitter API 1.1 URLs:

The format of the Twitter URLs looks like this:

 

https://api.twitter.com/1.1/statuses/user_timeline.rss?screen_name=XXXXXXX

 

Replace XXXXXXX with the twitter account's “screen_name”.

 

For example:

 

https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=ladygaga

 

or

 

https://api.twitter.com/1.1/statuses/user_timeline.rss?user_id=###

 

For example:

 

https://api.twitter.com/1.1/statuses/user_timeline.json?user_id=16409683

 

All you need to do is to add the Twitter URL using one of  the formats detailed above into the Twitter newswire on the Newswires-2 tab:

 

 

You can add as many Twitter accounts as you wish as long as you do not exceed the Twitter limits (180 checks in a 15 minute window):

 

 

Once you have added all of the Twitter accounts that you want, go to the Filters tab and add a filter for each Twitter account.

 

Each Twitter feed starts with “username” or “Twitter / username”. Use this string in the Body field like the following example:

 

 cid:image021.png@01CF9B54.AFE5E0F0

 

Add as many Sub-Filters (Right-Click > New Sub-filter) as you wish so that you can see each feed individually.

 

 

This will make the Tweets appear properly in Burli and show the (full story) link which the users can then click on.

 

Adding more than one OAuth Account in Burli will allow for even more checking as Burli will switch over to the next account once the limit for the first account has been reached. This will affect the check on a Home Timeline as it will show whichever account is currently checking

 

FEATURE: Twitter Home Timeline

As well as or instead of following other Twitter accounts, it is also possible to add your own Timeline as a Twitter feed in Burli. The format for the URL looks like this:

 

https://api.twitter.com/1.1/statuses/home_timeline.json

 

This will show you all of the Twitter accounts that you are “Following” with your Twitter account as well as all Tweets that you send or receive. The allowance from Twitter is to check your own timeline once per minute and will deliver everything new since the last check. This allowance is in addition to the 180 checks per 15 minute window of other Twitter accounts. Some users may find that by simply following all of the Twitter accounts they wish to see in Burli in their Twitter account, they only need to check their Home Timeline instead adding each individual Twitter account as an individual feed.

 

To create a Filter for the Home Timeline, enter home_timeline into the Body field of the Filter:

 

cid:image023.jpg@01CF9B54.AFE5E0F0

 

You can also see items filtered by the individual accounts if you set up filters for those accounts.

FEATURE: Fix for BN/CP newswire line feeds

Starting with Newswires 2.17, Burli can now strip any extra line feeds being sent from the BN/CP newswire. Previously, Burli would display all content from BN/CP in their native 80 character long lines and in Courier font. This meant that users would have to manually strip any extra formatting  when they drag an item into a Script or Work area. To enable this new feature the following SchemeLookup must be added to MAIN.INI:

[Newswires]
SchemeLookup##=2,23

Where ## is the next consecutive number in the list.

FEATURE: Shorten URLs in Tweets

Starting in Burli 221p, Burli has the ability to send shortened URLs in Tweets. As the user inputs a valid URL, when they type either “http://” or “https://”,  Burli will reserve 22 or 23 characters regardless of the length of the URL. Once the Tweet has been sent to Twitter, it will automatically be converted to a shortened URL. (e.g. http://news.nationalgeographic.com/news/2013/06/130621-summer-solstice-2013-longest-day-sun-earth-space-science/ will be shortened to http://t.co/Mt0uWpcHaM). Please note that Burli is not verifying the URLs as they are input so be sure to verify the URLs before sending.

Twitter no longer shows the Sender in the Ticker or InQueue

Burli is now showing the Twitter account of the sender in the Slug and on the ticker correctly. This information was not showing correctly after the switch to the latest Twitter API 1.1.

Fixed an instability issue with the Burli Web Server

We have found and fixed an instability issue in the Burli Web Server. When a Web Server user posted a story which was over a certain length, it would cause the Burli Web Server to crash. Versions 219p to 220a were affected.

FEATURE: Save as File naming

We have added a MAIN.INI setting to turn this feature off which may be required in countries that do not use Western character sets. We recommend this to any users who are seeing errors saving files which have been automatically given the Slug for the File Name. The new MAIN.ININ setting:

[Startup]

SlugFileName=No

The default is Yes

 

Webserver slug search error | An invalid argument was encountered

We have fixed an issue which affects users with non-western character sets who do either a Slug search in Burli or a Search with the Burli Web Server in Internet Explorer. These two features are now working as they should.

FEATURE: Toggle audio play counter between count up and count down

The counter in the bottom right can now be toggled to count Up or Down. The counter will always default to counting down when you click play on any audio.

Counting down shows a GREEN flashing arrow:

cid:image001.png@01CDD4F0.D91E17C0

Clicking on the Timer window will toggle the counter to count UP and will show a BLUE flashing arrow:

Another click on the counter will toggle it to count Down again.

FEATURE: Body Search via the Burli Web Server

Starting in Burli 219s, Burli Web Server user now have the ability to search the Body of all stories. This feature requires the “VN Advanced” checkbox enabled on the Burli Web Server’s HASP licenses.

Previously, Burli Web Server users only had the ability to search the Slug of all stories.

The user simply needs to check in the “Include Body” checkbox in the Burli Web Server search.

cid:image004.png@01CDD4F0.D91E17C0

Remote Scripts in the wrong order

Starting with version 219q, Burli now shows the Remote Scripts in the order they were meant to be shown. Previously, the Remote Scripts were being showing in alphabetical order.

Extra logging added to the Quick Record (CTRL-Q) function

We have added more log details in the Audio Recording log file which will help find the cause of the final recording not being created properly during Quick Record. Please be sure to have the “Audio Recording” Event Log turned on for all affected workstations.

FEATURE: Optionally turn logs ON at all workstations

We have added a feature to turn on specific log files for all workstations using a MAIN.INI setting. This make it easy to turn on specific logs without having to configure each workstation. The MAIN.INI setting is:

[Startup]

ForceLogEventsOn=n1,n2,n3,...

Where n# is the ID of the specific log files.

For example:

ForceLogEventsOn=18,0

This will force SCRIPTS and STARTUP log events on for all workstations, in addition to what each local workstation already has turned on.

Here are the Log IDs:

 

0                         Startup

1                         Fax Capture and Viewing

2                         Email Capture

3                         Web Server

4                         Password updates

5                         Audio Playback

6                         Replication

7                         Phone Dock

8                         Network bandwidth

9                         Critical events

10                     Miscellaneous

11                     Newswires1

12                     Audio Recording

13                     Audio Capture

14                     Database

15                     Chat client

16                     Auto audio trim

17                     Newswires2

18                     Script

19                     Dispatch

Extra diagnostic logging added to the Script log file

We have added extra diagnostic details to the Script log file. In the event that a Script file is locked, the log file will now show how long it took to try to open a file and also how many remaining attempts it will make. This will help to better identify the cause of any Script errors seen on workstations.

 

FEATURE:   Template for default text in new stories

We have added the ability to have default text appear every time someone creates a new story in the Work Folder. This is done by having a template file which must be called “NewStoryTemplate.txt” and located on the Burli Root Path in the ~\Burli\Settings directory. The first line of the text file will end up being the Story Slug and everything afterwards will be the Body. A variable of %USERNAME will insert the Burli Username of the author into each story. Here is an example of a template:

Burli NEWS - STORY SLUG - 1 - %USERNAME

EXTRO:

SOURCE:

 The story can then be easily modified by the editor and will keep a standardized format for all stories. If a “NewStoryTemplate.txt” file does not exist in the Root Path in the ~\Burli\Settings directory, Burli will behave as it did previously when creating a new story.

FEATURE: Allow for negative logic momentary closure for GPIO in Quickplay

Some customers require "negative logic" for contact closures from Quickplay. This means that they require a HIGH signal when there is no audio and a LOW signal (off) while audio is playing. QuickPlay now allows the use of a NEGATIVE value in the [Duration] field to tell Quickplay to trigger the GPIO device to LOW for the specified duration.

For example:

OpenAction1=IO,SeaI/O,1,3,-150

This will send a LOW signal for 150 ms on playback of a specific Quickplay deck.

FEATURE: Twitter API 1.1 support

Starting with Burli 219v, Burli supports the latest Twitter 1.1 API. It is expected that Twitter will discontinue support for the current version 1.0 API on March 5th, 2012 when they will turn off their RSS and XML functions. All users who have Twitter ingest or sending in Burli should upgrade to the latest version on or before this date.

To make the conversion easier, we have added a function to convert your Twitter feeds in Burli to the new format.

The function is called with:

CTRL-F6 > update_twitter_url > OK.

Burli will then convert all existing RSS links to JSON format and will show a confirmation box when it is done. A restart of Burli is recommended once the links have been converted.

FEATURE: Remote Folders via Virtual Newsroom

Burli now allows for access to remote Network Folders via the Virtual newsroom feature. This requires a minimum of Burli 219x on both the workstation(s) and the remote server(s). The remote Network Folders are Read Only and provide the users with all of the Network Folder material available at the remote VN locations. Audio clips are automatically converted to the local audio format when dragged to a workstation.

Clicking on the Folder tab will show you the remote locations available:

cid:image001.png@01CDF576.154DD1E0

Clicking on one of the remote locations will show you the folders that are available:

cid:image002.png@01CDF576.154DD1E0

Clicking on a Folder will show you the stories where content is shown to the right:

cid:image016.jpg@01CDF8BC.3DACFE60

When dragging a story down to any folder on the workstation, if there are any audio clips included in a story, they will be automatically converted to the local default audio format:

Right-Clicking on any remote location will allow you to refresh the folder and story listing:

cid:image018.jpg@01CDF8BC.3DACFE60

FEATURE: Remote Network Folders via VN | Automatic Refresh

We have added the ability to automatically refresh Remote Network Folders. With this feature enabled, the user will see all Remote Network Folders that they have opened refreshed at regular intervals. If the user needs to see an immediate update, they can always Right-Click to refresh. This feature is configured by adding the following setting to MAIN.INI:

RemoteNetworkFoldersRefresh=#

Where # is in minutes with a minimum of 1 minute. The default without this setting is not to refresh automatically.

Error icon in remote Scripts and Folder not displayed properly

We have fixed an issue when a connection error has occurred when connecting to a VN location for remote Script or Network Folders.

FEATURE: Aliased Folder listing method (NetFolderSplit)

We have introduced the ability to split the menu into additional columns after the specified number of folder names. This is controlled by the same setting as is used for Network Folders:

[Startup]

NetFolderSplit=[n]

Where [n] is the number of network/aliased folder names to display in a continuous column in the Open|Network Folders or Open|Aliased Folders menu option before starting a new column.

QuickPlay Deck cannot display the & (ampersand) character

We have fixed an issue where the & (ampersand) character was not being displayed properly in the Quickplay decks. This is being displayed properly.

FEATURE: GPO triggers during Burli recordings

Burli now has the ability to trigger a GPO during foreground recording. Either by the user clicking on the Red button, CTRL-R or CTRL-Q in Script mode (Quick Record) will trigger the GPO. This can be either a momentary or continuous type of closure and is specific to each workstation. To configure this, there is a file called LOCAL.INI which specifies the GPO device and channel as well as its duration. It should be located in the same directory as Burli.exe on the local hard drive.

The LOCAL.INI format is as follows:

[ForegroundRecording]

OpenAction=IO,[DeviceName],[DeviceIndex],[OutputIndex],[LengthinMS]

CloseAction=IO,[DeviceName],[DeviceIndex],[OutputIndex],[LengthinMS]

Where [DeviceName] identifies the I/O device. Burli supports several; for example: “SeaI/O”.

Where [DeviceIndex] is a one-based index for the specified device, in case there are more than one in a given machine. In most cases, the value here will be 1

Where [OutputIndex] is a one-based index for the output relay that should be pulsed

Where [LengthinMS] is the length of the pulse relays in milliseconds. For Negative Logic, use a – in front of the value. For example, -250 will trigger negative logic for 250ms. For continuous closures, using a value of 1 means a Continuous closure On and a value of 0 means a Continuous closure Off.

For example:

[ForegroundRecording]

OpenAction=IO,SeaDacLite,1,1,1

CloseAction=IO,SeaDacLite,1,1,0

This will trigger SeaDacLite device #1, channel #1 On until the user presses Stop when the channel will be turned Off.

Or

[ForegroundRecording]

OpenAction=IO,Axia,1,4,150

CloseAction=IO,Axia,1,4,150

This will trigger Axia device #1, channel #4 On for 150ms at the start of recording and then the same device and channel Off for 150ms when the user presses stop.

FEATURE: Lock (disable) Deck Drag and Drop

We have added to the feature of locking Quickplay decks drop down menu to also prevent the user from Dragging and Dropping items to a locked Quickplay Deck. This feature is enabled with the following Quickplay.ini setting:

DeckLockDrop=Yes/No

Where the default is Yes. This setting also requires the "DeckLock=" setting enabled on specific decks.

FEATURE: Body search via VN

We have added the ability to perform a Body Search on a Virtual Newsroom node. Previously, the user was only able to do Slug Searches. There is a new pop-up command window labelled "Search body...". The previous "Search..." has been renamed to "Search slug...". This functionality requires the VN Advanced feature enabled on the VN Server. If the VN server doesn't have its "VN advanced" feature turned on, the search result will return an empty list.

cid:image001.png@01CE0487.CC9388C0

FEATURE: NAAD Alert Support in Burli

Burli now supports the National Alert Aggregation & Dissemination (NAAD) System in Newswires2. A minimum of Burli 218z and Newswires 2.07 is required. Alerts will be shown in RED on the Burli Ticker based on your location.

 

 

All other alerts which are Non-Local or are Test messages will be hidden unless you click on the “Non-Local Alerts” or Test Messages Filters in the InQueue.

 

To enable this feed, you will first need to add the coordinates of your Local Alert Area which can be any region that forms a triangle or Polygon (3 or more points). The coordinates must be in the form of Latitude and Longitude in Degrees and minutes with Decimal format for the minutes and a negative value for points West and South E.G. 49.2734,-123.1321

 

There are various tools available online to help you find your Latitude and Longitude values. Here is one example:

 

http://gmaps-samples.googlecode.com/svn/trunk/poly/mymapstoolbar.html

 

 

Find all of the points for your Alert area and put them MAIN.INI in the [Newswires] section.

 

The setting is:

 

CAPCPSettings=lat1,long1,lat2,long2,lat3,long3,…

 

Example:

 

CAPCPSettings=50.02,-97.7,49.53,-97.8,49.34,-97.15,49.48,-96.57,49.97,-96.56,50.18,-97.1

 

You should also add a Scheme setting for NAAD:

 

SchemeLookup##=214,21

 

Where ## is the next available number in the list.

 

The last Latitude and Longitude pair will link to the first Latitude and Longitude pair to close the shape. You may have as many Latitude and Longitude pairs as you wish as long as you do not exceed 1000 characters in this setting.

 

The NAAD Filters have been created for you. They are currently setup to show all Local alerts on both the Ticker and InQueue but all other alerts which are outside of your region and also Test messages will be Hidden from Ticker and InQueue. You can always see those alerts by clicking on the Non-Local Alerts filter and sub filters.

 

 

To import these filters, go to Config -> Program Setup -> Filter Tab. Right-click on the “In-Queue” and select “Import” and then browse to the supplied “NAADFilters.dta” file. If you already have existing CAPCP Filters in your system, please remove them before importing the new filters file.

 

You should then Exit and Restart Burli.

 

Now you will need to add the NAAD Newswire in the Newswires2 tab:

 

 

Click Install on the NAAD newswire.

 

 

Add a Friendly Name: NAAD

Change the Refresh rate minutes to your preferred rate.

Enter the following URL: http://rss.naad-adna.pelmorex.com/

Click on the ADD button to add the settings.

 

You will start to see the NAAD messages coming into Burli.

 

Please note that it is important to follow this order exactly when adding the NAAD feed or you may end up with hundreds of items in the InQueue which do not apply to your area.

New Default settings in Burli

***The following MAIN.INI [Startup] settings have now been made YES by default and changes the behaviour of Burli. If any of these new default settings are not desirable, please add the setting to MAIN.INI and set it to No.***

CutDelete=No This is now YES by default

This setting allows user to change the Delete key to perform a "cut" in the editor rather than delete text from title. This is actually a key remapping. The focus remains in the Slug title field however when pressing the Delete key. The function will be mapped to delete a selection of audio waveform.

ReclaimFocusFromWebBrowser=No This is now YES by default

This setting fixes a very minor issue when navigating between Burli‘s Web Browser and RSS stories.

PrompterCheckFocus=No This is now YES by default

This setting will use a slightly different method to judge the currently active item when in Prompter mode. This solves the prompter jumping problem reported by some Burli customers of an item that can be in “focus” but is not “selected”. Previously, the default action (when the PrompterCheckFocus setting is set to No) is to look for the item that is selected. By checking for a “focus” item (not “selected”) the prompter does not jump.

FilterSort=No This is now YES by default

This setting allows users to alphabetically sort items listed in the filter tabs. The list is sorted when the [S] keyboard button is pressed. By default, these items are displayed in chronological order. A user may be creating a special report on a high number of recent assaults using related stories from the past week. By default, all stories are in displayed in chronological making it a time consuming task to find all stories (slugs) that begin with “Assault‘ as they are scattered amongst all the other stories. By pressing the [S] key, all stories (slugs) that begin with the letter “A”, “B”, “C” etc. will be grouped together. To reset the order of Filter Tab items back to the default chronological order, the user must re-open the Filter tab.

VNAllowCancel=No This is now YES by default

This setting will enable the Cancel button in the progress dialogue box when users drag the slug of a remote VN story. Without this setting set to No, the Cancel button is greyed out and the red 'X' has no effect.

The following MAIN.INI settings are also Yes by default:

Automatically create new Burli users

There is a new feature to automatically create new Burli users with predefined user rights. A new MAIN.INI setting is required which specifies the default user who’s rights will be assigned to the newly created users when they login.

[Startup]

GlobalDefaultUser=BurliDefaultUser

Where “BurliDefaultUser” is the name of the user from which the rights will be copied.

There are four prerequisites that need to be in place for this function to work:

The new Burli users will be created based on their Windows Login name. The Burli ticker tape will confirm that the user has been logged in (and created) at launch. If the user already exists in Burli security, the rights will not be changed. Starting in Burli 219e, the user rights include group membership but do include an optional predefined user password. This is to prevent users from logging in as someone else with no password or to give users rights to the Burli Web Server.

EMAIL Urgency

With this  version of Burli, we have added the ability to disable “High Priority” email from flashing on the ticker. The new MAIN.INI setting for this is:

[Startup]

EmailPriority=No

The default setting is Yes

Strip all HTML coding

For this new version you will need to add the specific newswire IDs of the Newswire feeds in MAIN.INI that you DO want the HTML tags to be stripped from. CNW-XML is one that you may want to add. The new entry looks like this:

[Newswires]

RemoveHtmlTagsFromWire=###,###,###,###

Where ### are the Newswire ID numbers that you want HTML tags to be stripped. For CNW XML, you would want to add 147. For example:

[Newswires]

RemoveHtmlTagsFromWire=147

Author’s names can now posted via VN and Web Server

Burli will now post the username to the slug for stories posted via the Virtual Newsroom or via the Burli Web Server. It uses the same setting which turns this feature on for a newsroom:

[Startup]

PostUserName=Yes

Required additional settings:

[Startup]

NewLoginMethod=Yes

TV Prompter mode can now scroll much more quickly

There is a new setting which will enable a much faster TV Script scrolling speed. The new setting for MAIN.INI is:

[Prompter]

DefaultScrollPixel=X

where X is the number of pixels Burli will move the text which is 1 by default.

Example:

[Prompter]

DefaultScrollPixel=2

We found 2 or 3 to be a good number of pixels for speed without making the text look too jerky. The higher the number of pixels you set this to, the faster and jerkier the text will become.

Corrected Audition link via Web Server when “RMSNormalizeForInQueue” is turned on

Previous to this version, Burli would not display the "Audition quality" audio link via Web Server if the user had the Automatic RMS feature turned on. This has now been corrected. The Audition Quality link is not available when the default setting is MP2 audio.

Normalize Audio Logger items to InQueue (MySQL required)

With this version of Burli, we have added a new MAIN.INI switch so that PostRecAction items can now be RMS normalized. The new switch has been added to the end of the current syntax and is only applicable to PostRecAction to InQueue items.

For example:

[AudioRecorderSession1]

PostRecAction1=IN-QUEUE:%SESSIONTITLE[] (%CLOCKTITLE[]) @%START[%Y%m%d]-%START[%H%M] RMS=Yes or (YES)

The default is No

If "RMS=Yes" is present, Burli will RMS normalize the audio according to the global RMS setting value in main.ini.

RMS Normalization on Dispatch

With this version of Burli, you can now to apply a different normalization setting to individual audio files exported via the AudioUpload.ini method.

The syntax of "File{m}Settings" in “audioupload.ini" has some changes. Currently the setting looks like this:

[Group{n}]

File{m}Settings=[AUDIOFORMAT]~[FTP|UNC]~[CONNECTION DETAILS]

where: AUDIOFORMAT is made up of:

 [LINEAR|MP2|MP2RAW|MP3],[STEREO|MONO],[SAMPLERATE],[BITRATE],[BWFHEADER YES|NO]

For example:

[Group1]

Name=Weather Upload to Web

File1=Weather (short),burlitest_wxshort

File1Settings=MP3,STEREO,44100,128,No~FTP~123.456.789.12,un,pw,

The new syntax change is related to "AUDIOFORMAT", it was:

[LINEAR|MP2|MP2RAW|MP3],[STEREO|MONO],[SAMPLERATE],[BITRATE],[BWFHEADER YES|NO]

Now it is:

[LINEAR|MP2|MP2RAW|MP3],[STEREO|MONO],[SAMPLERATE],[BITRATE],[BWFHEADER YES|NO], [RMS;[DbValuesTRUE|FALSE];[RMS DB | RMS RATIO]]

The TRUE means RMS DB and FALSE means RMS Ratio.

For example:

File1Settings=MP3,STEREO,44100,128,No,RMS;TRUE;-40.0~FTP~123.454.321.12,un,pw,

File2Settings=MP3,STEREO,44100,128,No,RMS;FALSE;0.01~UNC~\\BurliExport\AudioForExport

Story view via Burli Web Server

If a user has the 24HourClock=Yes (or MilitaryTime=Yes) in MAIN.INI, viewing stories via the Burli Web Browser now respects this setting and shows the 24 hour clock method for the time received. Previously, Burli only showed the time in 12 hour clock format (AM/PM).

FEATURE: New CTRL-F6 for the HASP tab

We have also added a new CTRL-F6 command to get to the HASP tab of Burli without having to navigate through all of the menus. This is valuable for situations where finding the Program Setup password is not available or not allow by the end user.

The new function is:

CTRL-F6 > hasp (lower case)

After pressing OK:

cid:image002.png@01CCEFCE.573F2800

You can then Update via Internet, Update from file or Update manually or simply check the Min date and Max date.

FEATURE: Send multiple audio-only stories in a single e-mail

We have added the ability to select multiple audio only stories from the Work folder and send them as a attachments to an email. The user will be prompted once for the audio format settings which will be applied to all of the attachments.

Right-most Web Browser frame does not wrap correctly in Safari Browser

We have added new logic in the Burli Web Server to check the client browser type. If it is Safari (used in iPhone, iPad and iPod Touch) Burli will show a maximum of 20 characters for each story slug in the middle panel. If the story slug is longer, it will be reduced to 20 and show … so the content in right-most panel won't be cut off. i.e. “President Obama spok...”

FEATURE: Show the Wire ID # for each Newswire

We have added the ability to show the Wire ID # for each Newswire. This number can then be used in MAIN.INI when adding SchemeLookup settings. The option is turned on in the [Newswires] section by default but can be turned off with the following setting:

[Newswires]

ShowID=No

This is Yes by Default

You will see each Newswire includes its ID#. In the following example, ABC RSS has the ID number of 205.

cid:image003.png@01CCD501.DA7AB460

Scripts Browser text editor (upper half) should be read-only

Since the Script Explorer in the top window is read only, we have added an option to show the area in grey which indicates Read Only. The user will also be unable to type any text into the area. To enable this feature, we have added a new main.ini setting as follows:

[Startup]

ScriptExplorerReadOnlyTextEditor=Yes

Default is No.

FEATURE: Apple file format ingest via FTP

Burli can now ingest Apple audio file types via FTP in Newswires2. Previously, those file types were not supported. QuickTime must be installed on the Burli capture machine as well as the BurliQuicktimeDLLInstaller_2.2.0.0a.exe to support this feature.

FEATURE: Prevent double-click for Script stories (Author pop-up window)

We have added a setting to disable the “Author” popup window when a user double clicks on a story in a Burli Script. Some users have found this popup undesirable.

The new setting is:

[Startup]

ScriptStoryAuthorFeature=No

Default is Yes.

Crash during RSS capture

We have fixed an issue where Burli would run out of memory or crash if a poorly formed RSS link was being ingested in Burli. Previously, Burli would fill a memory buffer with the bad data but never release it. This has now been resolved.

FEATURE: Hide sender's email address from the Burli ticker and InQueue

We have added the option of hiding the Sender's name and email address from the ticker and InQueue. A new main.ini setting has been added to turn this feature on and off:

[Startup]

EmailHideSender=Yes

Default is No.

Email capture crashes when email server connection is lost

We have resolved an issue where Burli would continue to run but the Email function was stopped due to a network interruption. An error message would be shown in Burli but when the user pressed OK, Burli would close. We have now changed the error handling behaviour in case of a network interruption during Email capture. Burli will now continue to run and the Email capture function will continue to run even in case of a network interruption. If Burli is unsuccessful connecting or disconnected during a connection, it will simply try again later.

Added more log events in MISCELLANEOUS for Network folder story locking/unlocking

We have added more log events in the Burli Miscellaneous log file for all Network Folder story locking and unlocking. This was done to help to diagnose reports of missing stories in Network Folders.

FEATURE: Compile multiple audio cuts into one

We have added a new feature in Burli to enable the user to open a Cast and highlight one or all  stories and then Right-Click and “Compile Audio”. The compiled audio will be assembled to the local Work folder as a new Audio file with the name of the particular Cast. This audio file can then be edited and sent to an automation system.

A new MAIN.INI setting is required to enable this new FEATURE:

[Startup]

CompileAudio=Yes

The default value is No.

  1. Select multiple stories from a Cast using the Mouse or Arrow button + Shift or CTRL then Right-Click.

cid:image003.jpg@01CCBE64.A7689DC0

  1. The Compiled Audio will be saved in the local Work folder with the Title of the News Cast that it was created from. In this case, “10am (News Talk)”.

  1. The audio file can then be Dispatched, Edit, etc.

You cannot mix audio formats when selecting files for Compiling Audio. For example Stereo and Mono files cannot be mixed. All audio must be in the same format or the following warning will be shown:

cid:image007.png@01CCBE37.04B8A430

FEATURE: 'Combine as a single Story' right-click option

We have added a new feature to Burli which allows the user to combine Audio cut(s) that you have highlighted in a Local or Network folder to a new Text + Audio item. The original Audio cut(s) will be left as they are and the new story’s Slug will say “Replace this first line with the story Slug” just as you would if you were creating a new text story. When the user Right Clicks on one or more Audio only items or Text only + Audio Only items the menu command is "Build Text + Audio Story". If all selected are audio cuts, right clicking any  of the selected will bring up the command.

Alternatively, you can highlight a Text Only story and also one or more Audio Only items and those selected Audio cuts will be then added into the Text story. In this case, Right-Clicking on the Text Only story will bring up this command. The audio cut(s) will then be added into the Text item instead of creating a new item.


There is a new main.ini setting to enable this FEATURE:

[Startup]

BuildAudioTextStory=Yes

The default value is No.

cid:image003.png@01CCBE3D.0091F630

Network folder items

We have improved the Network story file locking function. In the past it was possible for two or more workstations to be editing the same story at the same time. This would sometimes cause some text to be lost. Burli will now show a popup whenever someone else is editing the same network story. Once the other user has stopped typing, the file is able to be edited once more.

FEATURE: Send multiple audio-only stories in a single e-mail

We have added the ability to select multiple audio only stories from the Work folder and send them as a attachments to an email. The user will be prompted once for the audio format settings which will be applied to all of the attachments.

FEATURE: Burli Play Counter

Burli now has the ability to display how many times an audio cut has been played On-Air.  Now when a user right clicks on an audio clip, the menu will show “Played: XX time(s)” followed by a list showing each time that the particular audio cut was played in chronological order.

cid:image002.jpg@01CBB0DB.4CEC1DA0

To register as a valid “Play”, the following must be true:

  1. The user has the Script in Prompter mode in Burli
  2. The cut plays to the end

The Play Counter feature requires the following main.ini setting:

[Startup]

PlayCounter=Yes

The default value is No.

If you want to turn the Play Counter off at a specific workstation, you can use the following syntax:

PlayCounter=Yes![HASP ID#]

Example:

PlayCounter=Yes!8374632924

This would turn the play counter on for all workstations except for the one with HASP ID 8374632924.

When an audio file, for example, "1234.wav" is fully played On-Air in Prompter mode, a count file "1234.ctr" is created in the folder where the audio file is located. This will typically be on the Burli Root Path in the ~\Burli\Audio\In-House directory. For each new play, a line is appended to each file to register the playback information. This counter file will be purged when its original wav file has also been deleted. A “Play” will be counted for a clip even if a portion of that clip has been highlighted and added to a Script and played On-Air. If for some reason the On-Air workstation has lost its network connection and is running a mirrored copy of the audio files in a Script, the plays will not be registered for those stories.

Incorrect path for remote log file deletion

We have fixed an issue where remote Script log files were not being deleted from the Root Path if the File Server hosting the Root Path was not also running Burli. The Script files are named “YYYYMMDD-SCRIPT_R.log” and are located in the ~\Burli\Log\ folder. The log files will now be properly purged after one week by any Burli workstation which is using the Root Path and is running Burli.

Audio file length calculation

We have improved the Burli audio file length calculation to ensure more accurate millisecond resolution when displaying the audio file length.

Orphaned audio entry in Orphaned audio entries in UploadedFiles.XML when posting the same audio for two different Internal Newswire stories

We have fixed an issue when two Internal Newswire stories both had the same audio included. When the purge arrived and purged the first story entry including the audio entry in UploadedFiles.XML, the second story audio could not be deleted since the audio cut was already removed. We have changed the way that the included audio files are named. If the xml file name is something like "Sta201106020169.xml" for example, then the attached audio clips will be "Sta201106020169-1.wav", "Sta201106020169-2.wav", etc. This guarantees that the audio file name on the server is unique for each export.

This change requires the following new main.ini setting:

[Newswire Server]

NewAudioFileName=Yes

The default value is No.

PostRecAction sometimes confuses items

We have fixed an issue when multiple Audio Logger sessions stopped at the same time and where then being sent to the InQueue using the PostRecAction MAIN.INI setting. Occasionally two items would share the same audio when Burli assigned a cut number to both PostRecActions. We now process one PostRecAction at a time so that this cross assignment cannot happen.

AudioLogger error message when choosing the last hour of the day and modifying the TO: time

We have fixed an issue when using the Audio Logger interface to find a recording from the 23:00 hour. If the user clicked on the last hour and then edited the TO: time to something like “23:15” and dragged the time to the Multitrack recorder, they would see an error about choosing more than 10 hours. This has now been fixed.

cid:image001.jpg@01CC24F1.D4D18180

FEATURE: Right Click menu Post to InQueue

Burli now has a “Post to InQueue” option as in the screenshot below.

cid:image002.png@01CC24F1.D4D18180

Mix down and Recording audio Slugs do not respect the 24HourClock setting

We have fixed an issue when the user has the 24hour clock format set in Burli (24HourClock=Yes or MilitaryTime=Yes) and does a Single track Recording or a Mix down from the Multitrack recorder. Previously we would always add a time stamp in 12 hour format to the slug of the item in the Work folder. Burli now respects the 24HourClock setting and correctly stamps the slug in 24 hour format.

FEATURE: Use Slug title for Folder Drop audio file name

Burli has added the option to use the Slug Title for the filename when using the [FolderDrop] feature. To allow for this new feature, there is a small change in MAIN.INI.. There should now be an * (asterisk) in the place of the filename.

For example

[FolderDrop]

Folder1=Dalet Automation Server~\\daletserver01\fromburli\*.wav

If Burli does not see “*.wav” in the place of the filename in MAIN.INI, the new feature will not work. Because the Slug name will be used for a filename, only valid Windows filename characters are accepted. However, if Burli finds any invalid characters in the Slug, they will be stripped out before they are added to the filename but the slug itself will always remain untouched.

Respect the YEAR information from FTP files if they are older than one year

We have changed the behaviour of Burli when ingesting stories from and FTP folder and there are  stories that are over one year. Previously, Burli did not read the YEAR information of the FTP files so stories that were over one year old would be ingested again. The year information of FTP files are now being respected.

Purging of Backup InQueue RDF files

We have changed the way that the backup InQueue RDF files are being purged to solve an issue with File Serves. Backup RDF files are being created every hour starting in Burli 212m and are being saved to the Root Path in the \TEMP directory. If the Root Path machine also has Burli running, the \TEMP folder is purged every 130 hours (7.5 days) by default or whatever the user has set for the optional MAIN.INI CleanupTempFiles=[n] setting. If however, the File Server is not also running Burli, the backup InQueue RDF files will accumulate and never be purged. To solve this issue, we have created a new version of Burli which will use the machine responsible for Purging to clean up those files. The workstation that has "This workstation purges data files" turned on will do the Purge of those old RDF files. The default will be 180 hours (7.5 days) or however many hours the user has set in MAIN.INI for CleanupTempFiles=[n]. The first purge event of those backup InQueue RDF files will happen 2 minutes after first starting Burli and will from then on be on a two minute cycle to check for old files. This update should be implemented for all users that have a dedicated File Share which is not running Burli.

cid:image001.jpg@01CC60AC.9B0FFF20Twitter.com

OAuth authentication method for Twitter

Burli now uses the OAuth authentication method for capturing Twitter feeds. This increases the permitted checks per hour from 150 to 350 times for each OAuth account  configured and no longer limits you per IP address. Once one OAuth account has used its hourly quota of 350 checks, Burli will automatically use the next OAuth account. In this way, if you have only one Twitter account, you can safely check Twitter for 5 different Twitter feeds every minute. By adding another local Twitter account,  this number is doubled to 10 Twitter accounts and so on.

The new OAuth method for Twitter requires a minimum of Burli 214f and Newswires 1.76. Both files must be updated for this new method to work properly. Also, at least one Twitter account needs to be activated in Burli to use this new method. (Please see the [Twitter] section below for instructions on how to add Twitter accounts to Burli.) Burli creates a text file with the Access Token for each account and is saved to the Burli Root Path at (~\Burli\Twitter). Each accounts‘ file will be named as [display name].txt. Example: All Sports Radio.txt.

The format of the Twitter feed URL format has change from the previous non-authenticated capture method. The new format is now:

http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=[sc]

Replace [sc] with the twitter account's screen_name.

Example:

http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=ladygaga

Alternatively, you can use the User ID# of the feed that you wish to follow like this:

http://api.twitter.com/1/statuses/user_timeline.rss?user_id=###

Replace the ### with the User ID of the feed

Example:

http://api.twitter.com/1/statuses/user_timeline.rss?user_id=813286

A typical Twitter feed has a URL which looks something like this:

cid:image003.png@01CC60AC.9B0FFF20

All you need to do is to add the Twitter URL using one of  the formats detailed above into the Twitter newswire on the Newswires-2 tab:

You can add as many Twitter accounts as you wish in the dialog box which is just like setting up RSS feeds:

cid:image005.png@01CC60AC.9B0FFF20

Once you have added all of the Twitter accounts that you want, go to the Filters tab and add a filter for each Twitter account.

Each Twitter feed start with “username:”. Use this information in the Body field like the following example:

 cid:image009.jpg@01CAB702.767AFE30

Add as many Sub-Filters (Right-Click > New Sub-filter) as you wish so that you can see each feed individually.

***For the best appearance of your Twitter feeds, we recommend the following Scheme setting to be added in the [Newswires] section of MAIN.INI. ***

SchemeLookup5=188,7

Format:

SchemeLookupX= 188,7

CTRL-F6 function to convert the Twitter feed URLs

Burli now includes a Ctrl-F6 command to automatically convert the Twitter feed URLs in Newswires2 from the old RSS method (pre Burli 214f) to the new OAuth method introduced in Burli 214f.

To perform the function on the Burli Twitter feed Capture machine, press CTRL-F6 and type "update_twitter_url" (no quotes).

It will do the following,

  1. Reads the existing Twitter URLs stored in the windows registry
  2. If the URL contains "/user_timeline/" string, then it will be replaced with the new URL.
  3. If the new string doesn't contain "/user_timeline/", it won't be modified.
  4. The number of replaced URLs is shown on the pop-up window

Twitter.com

 [Twitter]

This section controls the way that Burli functions with sending Twitter messages.

Function:

Starting in build 210w, this [Section] and its settings adds “Send to Twitter” functionality to Burli. A Twitter message can be sent directly from Burli by highlighting text and either CTRL-Shift-T or Right-Click “Send to Twitter” on highlighted text or a story. The Twitter entry box will pop up with the highlighted characters auto filled or the contents of the story entered. The user can alternatively simply CTRL-Shift-T or Right-Click “Send to Twitter” and freely enter text into the pop up box. As the user types into the entry box, a “Remaining” counter is displayed which indicates the number of characters remaining for the Twitter message. The maximum number of characters in a Twitter message is 140. When you want to send the Tweet, press the “Send” button and a progress bar will be shown. If the user exceeds the 140 character limit, a negative number is displayed in the “Remaining” counter indicating the number of characters over the limit and the Send button will also be disabled. If no account are selected, the Send button will also be disabled. There is also the ability to send to multiple Twitter accounts at the same time by selecting the checkbox next to each name. You make the account checkbox(s) selected by default by adding the “Selected” field at the end of each entry. The current sending limit is 350 Tweets per hour per account.


Syntax:

[Twitter]

Enabled=Yes

Account1=[display name1]~[TwitterUser1(optional)]~[Password1(optional)]~[Selected/blank]

Account2=[display name2]~[TwitterUser2(optional)]~[Password2(optional)]~[Selected/blank]

Account3=[display name3]~[TwitterUser3(optional)]~[Password3(optional)]~[Selected/blank]

Account4=[display name4]~[TwitterUser4(optional)]~[Password4(optional)]~[Selected/blank]

"Enabled=Yes" is the power-on switch for this feature. The default setting is "No".

Account# must be in numerical order.

[display name#] is what the user will see to describe each account. They should not contain any of the following characters

TwitterUser (optional) is an optional field since Twitter is now using an authentication method that does not require this information to be stored

Password (optional) is an optional field since Twitter is now using an authentication method that does not require this information to be stored

“Selected” to select the account checkbox(s) by default is optional. No entry or blank will not select the checkbox by default. Burli will remember the last selection at a workstation as long as Burli is not restarted.

Example:

[Twitter]

Enabled=Yes

Account1=CBRD~CBRD123~CBRDpassword~Selected

Account2=CHAZ~ChazFan~Chazpassword~Selected

Account3=All Sport Radio~Allsportradio~sportpassword

Account4=All Talk Radio~AllTalkradio~talkpassword

cid:image003.jpg@01CAAB1E.87804720


Note:

All three fields (Enabled, and each account’s Username and Password) in the [Twitter] section must be entered in Main.ini for the Twitter function to send properly. If there are any errors during sending the Twitter message, it will be displayed in the progress bar. The error messages can be referenced on the Twitter website. (www.twitter.com)

Twitter has introduced a new “OAuth” method for sending Tweets directly from other applications. OAuth is an authentication protocol that allows users to approve applications to act on their behalf without sharing their password. Because of this new authentication method, we have had to change the way that Burli sends Tweets. There is an “Access Token” that is now saved to Burli which is responsible for all future authentications.

Because there are a few steps involved, the very first time that you send a Tweet from one of your Twitter accounts, it is recommended that you only send to one account at a time for the first send. Once all of the tokens are all saved into Burli, you will not need to manually authenticate again.

The first time that you send a Tweet from Burli, you will be presented with the following dialogue box.

cid:image002.png@01CB5B21.49093660

You will also find that Burli has opened an Internet Explorer window with the following information:

cid:image012.jpg@01CB5E5A.61CC5600

“Twitter Username Here” will be your Twitter account name. Once you press “Allow” the following page will be shown:

cid:image013.jpg@01CB5E5A.61CC5600

Enter the Username and Password for the account and press “Allow”. The following page will be shown:

cid:image004.png@01CB5B20.62BAC700

Type or Copy and Paste the PIN number given to you into the Burli dialogue box and then press OK.

The Twitter message will be sent and all following Tweets from this account will not require any further authentication.

If you have more than one Twitter account, do the same procedure above with each account. Burli will create a text file with the Access Token for each account and it will be saved to the Burli Root Path at (~\Burli\twitter). Each accounts’ file will be named as [display name].txt. example: All Sports Radio.txt. When you have completed the above authentication procedure with each account, you will not need to do it again.

Corrupt MP3 email attachment fix

We have resolved an issue in Burli when receiving an email which included a corrupted MP3 file attachment would hang the email capture function. Burli will now check to see if there is a bad header or if the file contains partially or totally corrupted audio information. We will now ingest the files even with the invalid information and the email capture function will continue properly. This makes the email capture function much more robust.

Intermittent mismatch error report when combining stories

We have made some changes to Burli to fix an issue when combining multiple audio clips within a Script and it falsely reports an audio format mismatch error. We fixed this in Burli 217e and above and have also added more MISCELLANIOUS log events to trap any exceptions.

FEATURE: Custom Icons for Virtual Newsroom Nodes and Script Explorer

We have added the option to allow for customized icons for each VN node and remote Script locations in Burli. All images need to be stored in the Burli Root Path in the following directory: ~\Burli\Settings\Icons\ and the images need to be in BMP format and 16x16 pixels in size. Larger files are OK as they will be resized by Burli.

The new settings that are required for this new feature is the logo file at the end of each Remote Hosts entry:

[Remote hosts]

Remote[n]=[Descriptive name],[IP address or host name],[proxy server IP],[username],[password],[Stationlogo.bmp]

Example:

[Remote hosts]

Remote1=London Bureau,11.22.33.44.55:5678, ,vn_london,vn_password,LondonLogo.bmp

Remote2=Paris Bureau,22.33.44.55.66:5678, ,vn_paris,vn_password,ParisLogo.bmp

Etc…

cid:image002.png@01CD0137.39FE2B40

FEATURE: Web Burli view the network folder stories in alphabetical order

We have added the ability to sort the items in Network Folders via the Burli Web Server sorted Alphabetically. To enable this feature, a new MAIN.INI setting is required:

[Startup]

DisplayWebNetworkFoldersAlphabetically=Yes

The default value is No. Without this setting, all Network Folder items will be shown by their modified dates.

FEATURE: HASP license auto update | Update via internet

We have added the ability for Burli to automatically update the HASP licences from the Burli server eliminating the need for anyone to do this manually. This setting is highly recommended for customers who have a large number of users on multiple Root Paths. This is also very good for remote users with local Root Paths where giving out the Program Setup password is not desirable. With this setting, Burli will automatically check for licence updates 31 days before licence expiry. If it is successful, the message “Hasp update” will show in the InQueue and Ticker. Which particular machine(s) that does this check can be controlled by the setting otherwise all machines will do this check.

There is a MAIN.INI setting to enable this new function:

[Startup]

AutoHaspUpdateViaInternet=Yes

The default for this setting is No. Alternatively, you can use the following syntax so that only one machine does the check for the entire station:

[Startup]

AutoHaspUpdateViaInternet=No!987654321

With the example above, only the machine with HASP ID# 987654321 will do the update for all workstations.

FEATURE: New CTRL-F6 for the HASP tab

We have also added a new CTRL-F6 command to get to the HASP tab of Burli without having to navigate through all of the menus. This is valuable for situations where finding the Program Setup password is not available or not allow by the end user.

The new function is:

CTRL-F6 > hasp (lower case)

After pressing OK:

Description: Description: cid:image002.png@01CCEFCE.573F2800

You can then Update via Internet, Update from file or Update manually or simply check the Min date and Max date.

FEATURE: Adjustable HEIGHT for Button Bar | Advanced Quickplay Prompter Buttons

We have added the option of adjusting the Quickplay Button HEIGHT for the Button Bar in Prompter mode. This has been done to better accommodate Touch Screen users.

Description: Description: cid:image004.jpg@01CCF2E4.F5C2EE80

A new QUICKPLAY.INI setting has been added to support this FEATURE:

[QuickPlay]

PrompterButtonHeight=n

Where n is the number of pixels is the default setting and the minimum is 30.

FEATURE: 'Combine as a single Story' right-click option

We have added a new feature to Burli which allows the user to combine Audio cut(s) that you have highlighted in a Local or Network folder to a new Text + Audio item. The original Audio cut(s) will be left as they are and the new story’s Slug will say “Replace this first line with the story Slug” just as you would if you were creating a new text story. When the user Right Clicks on one or more Audio only items or Text only + Audio Only items the menu command is "Build Text + Audio Story". If all selected are audio cuts, right clicking any  of the selected will bring up the command.

Alternatively, you can highlight a Text Only story and also one or more Audio Only items and those selected Audio cuts will be then added into the Text story. In this case, Right-Clicking on the Text Only story will bring up this command. The audio cut(s) will then be added into the Text item instead of creating a new item.


There is a new main.ini setting to enable this FEATURE:

[Startup]

BuildAudioTextStory=Yes

The default value is No.

cid:image003.png@01CCBE3D.0091F630

FEATURE: AP PrimeCuts Server Audio files - Automatically create text + audio story

We have added tighter integration with the AP PrimeCuts service. Burli will now merge an audio file from the AP PrimeServer application to its story text information from the AP PrimeCuts website to form a single story in the Burli InQueue.

 

To enable this, you need to have the AP PrimeServer application installed and configured and add the AP PrimeCuts newswire in the Newswires2 tab:

 legacy.jpg

 

You will also need to add a PrimeCuts Filter for the InQueue by selecting “Wire: AP PrimeCuts” as the Source:

 

legacy.jpg

 

 

There is also a new MAIN.INI setting required to authenticate for downloading the XML data from the PrimeCuts Website. The setting looks like this:

[Newswires]

APPrimeCutsAuthentication=UserName~Password

 

Where the "UserName" and "Password" is separated by "~".

 

Updated AP Logo

legacy.jpg

You will notice that in the latest version of Burli and Newswires.zip, we have updated to the new logo from Associated Press.

FEATURE: AP PrimeCuts now supports Sub Categories and File Types

We have now added Sub Category and File Type information to the AP PrimeCuts newswire. This makes for easier searching and sorting stories from AP. For Audio Type, Actuality, Voicer and other types can be searched and/or filtered. I have built a fairly complete Filter list for you (APPrimeCutsFilters.dta) Which you can import after you remove your existing AP PrimeCuts filters. We have created a fairly complete Filter list which can be imported by Right-Clicking on “In-queue” filter and select “Import…” and then select the “APPrimeCutsFilters.dta” file. If you already have some AP PrimeCuts Filters, please remove the existing ones first before importing.

Web tab shows last RSS feed page and does not remember the last web page visited

We have fixed an issue where the user selects a web bookmark and then reads an RSS feed. When the user clicks back on the Web tab, instead of the last webpage visited being shown, the RSS feed is shown instead. This is now working as it should so clicking on the Web tab shows the last page visited as expected.

FEATURE: NewsML G2 formatted newswire support

Burli now supports the NewsML G2 format which is now being used by a number of newsfeeds including Reuters. Newswires 1.98 is also required to support this new format.

FEATURE: Automatic backup of Settings directory to the local root

We have introduced a new feature where every Burli workstation will now have its settings (Server Settings directory) saved as a ZIP file on launch to its local ~\Burli\Logs directory. This was done to enable quick recovery in case of a Burli Server Failure. The files

Are named “ServerSettings_YYYYMMDD-HHMMSS.zip” for example “ServerSettings_20120625-145904.zip” and only a maximum of 7 will be kept on any machine before they are purged.

Text contents disappear from stories in Network Folders

We have resolved an issue where the text contents of stories went missing when multiple users were working on the same Network folder. This was seen when someone edited the slug of a story when another story was being added to the folder at the same time. This caused the folder index to be offset and changes were then applied to another story in the folder. We now refresh the index/offset of the story being edited before the new slug is overwritten.

Stability issue with Twitter RSS feed downloading

We have fixed an issue where Burli would crash if there was a delay in getting the XML data downloaded and the Event Log files were turned on. This fix also effects basic HTTP authentication and RSS downloading.

FEATURE: Automatic backup of Settings directory to the local root

We have introduced a new feature where every Burli workstation will now have its settings (Server Settings directory) saved as a ZIP file on launch to its local ~\Burli\Logs directory. This was done to enable quick recovery in case of a Burli Server Failure. The files

Are named “ServerSettings_YYYYMMDD-HHMMSS.zip” for example “ServerSettings_20120625-145904.zip” and only a maximum of 7 will be kept on any machine before they are purged.

FEATURE: Automatically backup server Settings directory to the local root

We have now added the option to turn off this feature which automatically creates a copy of the Server settings to each workstation. The new main.ini setting is:

[Startup]

BackupServerSettingLocally=[Yes/No]

Yes by default.

Example:

[Startup]

BackupServerSettingLocally=No

FEATURE: Ingest Podcasts directly into Burli

We have added the ability to ingest Podcasts into Burli using the Newswires2 tab.

cid:image003.png@01CD643A.719C93A0

The RSS link for each channel needs to be added in the Podcast newswire in Newswires2:

cid:image001.png@01CD6439.C35910C0

Included in the Slug of each Podcast that is downloaded, we have the name of the each Podcast Channel so that you can set up Filters based on each Channel.

There is also a new MAIN.INI setting to specify how many days in the past to download in case a Podcast Channel has very many older podcasts available. The new setting is:

[Newswires]

PodcastRetroactiveDays=n

Where n is 30 by default.

Update Twitter logo cid:image006.png@01CD64CF.B2BCFBF0

We have updated the Twitter icon in Burli to the latest Twitter branding.

FEATURE: Support for MarketWire NewsML G2 format

Burli now supports the new MarketWire NewsML G2 formatted newswire in Newswire2. A minimum of Burli 218L and Newswires 2.02 is required. You will find the new “MarketWire NewsMLG2” in the Newswires2 tab.

cid:image004.png@01CD64CE.D7A46C10

For the “File Filters”, be sure to select *.newsml

In the Filters tab, create a new Filter with the Source as “Wire: MarketWire NewsML G2”.

cid:image005.png@01CD64CF.4C4BB410

FEATURE: Support for Plain Text Email in UTF-8, 8859-2 and all other Character sets

Burli now supports Plain Text emails which are sent in UTF-8, 8859-2 and all other character sets. The email will be displayed in Burli with the following MAIN.INI setting turned on:

[EmailCapture]

PlainTextToHTML=Yes

The default setting is no.

With this setting turned on, all Plain Text emails which are not 8859-1 encoded will be turned into an HTML email in Burli so that they can be displayed properly.

This setting also relies on the following default settings (Yes after 209d) to have also been left ON:

[Startup]

AllowBigHtml=Yes

ShowHtmlEmailIfAvailable=Yes

SupportHtmlEmail=Yes

If you are using a newer version than 209d, the three settings above are not required.

Email capture thread hangs until Burli is restarted

We have fixed an issue where the Email Capture function would get stuck if there was any interruption during the downloading of emails. Burli would need to be restarted in order to get the email capture function to work again. We have now made the entire email capture function much more robust starting in 218q. Burli now allows download resuming in the case of any network interruption during the download and also includes a timeout in case there is a loss of communication for 30 seconds or more during email capture.

User mode background record bug | Orphaned audio

We have fixed an issue where User initialed Background Recordings would disappear from the Work Folder if it was the last operation done before closing Burli. All background recordings now stays in the Work Folder until the user manually deletes them.

Text contents disappear from stories in Network Folders

We have fixed an issue where the story contents of Network Folder would not be saved properly. We found that this was due to an index offset which was being introduced when a new story was dropped onto a Network tab and the user continues to edit the original story without resetting focus to that story. This has now been resolved. Users will find that when they drop a story (Text or Text/Audio) into a folder tab, when they go back to the folder, they will see that focus has been set to the top story in the Network Folder which will be the newly added story.

Sealevel I/O | Channel 9 - 16 not available in Remote tab

We have fixed an issue where Quickplay decks over 9 were not accessible via the Remote tab in Burli so those carts could not be assigned. Starting in Burli 218w, any number of Quickplay decks can now be accessed.

Wave files downloaded from the Burli Web Server have incorrect header information

We have fixed an issue where audio files that are downloaded from the Burli Web Server were unplayable in certain audio applications. All versions of Burli before 219c are affected. This was caused by an incorrect RIFF header written to each WAV file which stated an incorrect length. All files are now being written with accurate header information and files should play now play properly in every audio application.

HTML Emails with an HTM attachment not displayed properly

We have resolved an issue in Burli when receiving HTML formatted email which included an HTML (or HTM) attachment. Previously, Burli would only show the HTML attachment. This has now been resolved and HTML emails will display properly.

FEATURE: Improved Podcast Ingest compatibility

We have improved the Podcast ingest by allowing for much larger ID3 tag image files (up to 1MB) and also ignore bad date stamps for Podcast channels that are not using proper RFC 822 format. Burli will ingest those feeds by ignoring the incorrect date format but the main.ini setting "PodcastRetroactiveDays" will have no effect on those feeds. Instead all Podcasts on that feed will be ingested.

Sending Tweets from Burli not working

We have fixed the method that Burli is using to send Tweets. Due to Twitter changing the allowed method for sending Tweets, we have had to change the way that Burli talks to the Twitter server. Ingesting Tweets is not effected as long as they use the following format: http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=XXXXXXX

Improved VBR MP3 ingest

We have improved the ingest method for VBR (Variable Bit Rate) MP3 files to allow for larger XING VBR headers.

FEATURE: Twitter API 1.1 improved support | Home Timeline

We have improved the support in Burli for the new Twitter 1.1 API which is being used starting on March 5th, 2013. Twitter’s support for the older API 1.0 will be slowly shut down after this date. Starting with Burli 220j and Newswires 2.12, Burli can take advantage of the newer limits allowed when checking for Twitter feeds with this new method. The new limit is 180 checks every 15 minute window per Twitter OAuth account. This means that you can now check 12 Twitter accounts once per minute in Burli. In addition, Burli also supports your Home Timeline as a Twitter feed. Please see the details below.

***For anyone who already has Twitter feeds coming into Burli, the URLs of each feed needs to comply with the new format.***

***If you are already ingesting Twitter into Burli, to make the conversion easier, we have added a function to convert your Twitter feeds in Burli to the new format.***

The function is called with:

 

CTRL-F6 > update_twitter_url > OK.

Burli will then convert all existing Twitter links to JSON API 1.1 format and will show a confirmation box when it is done. A restart of Burli is recommended once the links have been converted. Once you have converted the URLs, you can expect to see all Tweets from all URLs to be ingested again since this is actually a new source of data in a slightly different format.

***The new format also requires a new SchemeLookup which needs to be added/modified in your MAIN.INI file.***

[Newswires]

SchemeLookup##=188,22

Where  ## is the next available number in the list of SchemeLookup entries.

Twitter API 1.1 URLs:

The format of the Twitter URLs looks like this:

http://api.twitter.com/1.1/statuses/user_timeline.rss?screen_name=XXXXXXX

Replace XXXXXXX with the twitter account's “screen_name”.

For example:

http://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=ladygaga

or

http://api.twitter.com/1.1/statuses/user_timeline.rss?user_id=###

For example:

http://api.twitter.com/1.1/statuses/user_timeline.json?user_id=16409683

All you need to do is to add the Twitter URL using one of  the formats detailed above into the Twitter newswire on the Newswires-2 tab:

You can add as many Twitter accounts as you wish as long as you do not exceed the Twitter limits (180 checks in a 15 minute window):

cid:image002.png@01CE1671.9CD4F280

Once you have added all of the Twitter accounts that you want, go to the Filters tab and add a filter for each Twitter account.

Each Twitter feed starts with “username” or “Twitter / username”. Use this string in the Body field like the following example:

 cid:image005.png@01CE1673.20DDF3F0

Add as many Sub-Filters (Right-Click > New Sub-filter) as you wish so that you can see each feed individually.

This will make the Tweets appear properly in Burli and show the (full story) link which the users can then click on.

Adding more than one OAuth Account in Burli will allow for even more checking as Burli will switch over to the next account once the limit for the first account has been reached. This will affect the check on a Home Timeline as it will show whichever account is currently checking

FEATURE: Twitter Home Timeline

As well as or instead of following other Twitter accounts, it is also possible to add your own Timeline as a Twitter feed in Burli. The format for the URL looks like this:

http://api.twitter.com/1.1/statuses/home_timeline.json

This will show you all of the Twitter accounts that you are “Following” with your Twitter account as well as all Tweets that you send or receive. The allowance from Twitter is to check your own timeline once per minute and will deliver everything new since the last check. This allowance is in addition to the 180 checks per 15 minute window of other Twitter accounts. Some users may find that by simply following all of the Twitter accounts they wish to see in Burli in their Twitter account, they only need to check their Home Timeline instead adding each individual Twitter account as an individual feed.

To create a Filter for the Home Timeline, enter home_timeline into the Body field of the Filter:

cid:image006.jpg@01CE1690.5710BEE0

You can also see items filtered by the individual accounts if you set up filters for those accounts.

Bad XML (IRN) in Burli RSS feed via Webserver

Burli was stripping too many characters from the XML feed which removed the formatting in the Web Server. We are now excluding the characters required for formatting when stripping unused characters.

FEATURE: Expanded audio format support in Burli | AAC and AMR

This feature allows you to import many special audio file types (AIF, AIFF, AIFC, M4A, AAC, AMR and µ-law) using Newswires-2, Email capture and manually importing using the new QuickTime API.

 

-               On each machine intended for the new for Apple file ingest, first download and install the latest version of QuickTime.

 

Burli QuickTime DLL Installer:

-              Please run this DLL installer (BurliQuicktimeDLLInstaller_2.3.0.0a.exe) from a local path, not via network path. QuickTime must also be installed for this DLL to work properly.

 

Please note the following regarding the BurliQuicktimeDLLInstaller_2.3.0.0a.exe:

-              Burli must NOT be running during the installation.

-              Copies libQT.dll version 2.3.0.0 into [localroot]\Burli\Drivers\Media.

-              Inserts the required registry setting:

\HKLM\Software\Burli\AudioEditor\FilePlugIns\AT_QT with a string value “[localroot]\Burli\Drivers\Media\libQT.dll”

-              Supports Windows 32 and 64 bit.

-              Burli.exe requires, latest version of Apple QuickTime.

-              The installer assumes full read/write privileges to the local root, Windows temp directory and the registry.

-              Launch Burli afterwards.

FEATURE: Post to In-Queue via a Right Click Menu

We have added the ability to send Multiple stories to the InQueue with the Right-Click command "Post to InQueue". This function is different from the drag and drop function since it will not combine audio and text into single stories. Each item instead will be posted individually to the In-House filters with this Right-Click command.

Import problem with special char in filename (Drag/drop vs. Open External)

Previously, audio files that were dragged and dropped into Burli which contained special characters in their file names would not import properly. For example "song #3.mp3". This is now working with Drag and Drop. The Open External file function was not affected by these special characters.

FEATURE: Aliased Folder security setting

We have introduced a MAIN.INI setting to enable or disable the Aliased Folder security in Burli. The new MAIN.INI setting is:

[AliasedFolders]

CheckSecurity=Yes

By default the CheckSecurity settings are off.

FEATURE: Delete users from Burli security when they are no longer in Active Directory

We have added the ability to Delete users from Burli security when they are no longer in the Active Directory. The new feature uses ADSI (Active Directory Service Interface) to communicate with the Domain server to retrieve all of the Domain user names. It then compares the list with the Burli user list from the Security.dta file. If the Burli user doesn't exist in the domain user list and does not belong to the Burli "Administrator" (case insensitive) group, then the user will be removed from Burli. Before the actual deletion, a confirmation popup window is shown up, listing all the user names which will be deleted. If the OK button is pressed, the qualified user name will be removed but the user can also cancel if they see any errors.

The new Ctrl+F6 command is "OrphanUserData".

*** Please note that you need to run this command as administrator and you should back up the Security.dta file (in ~\Burli\Settings\) beforehand. ***

Blank subject line when receiving emails from Zetta (Powershell)

We have fixed an issue with blank Subject lines when an email is being received in Burli from Powershell. Some email header fields, like "From", "To", "Subject" can be encoded by two different methods. One is "Binary" encoding, another is "Quoted Printable" (QP) encoding. Previously, Burli could only handle "Binary" encoding for the above three fields. Starting in Burli 220n, we have added new code to handle the QP cases as well so they will now appear properly.

Syntax Error if a Script name has a space at the end

We have fixed an issue in the Burli Web Server when someone tries to view a Script which contains a <space> at the end of the filename. Previous to this fix, Burli would show a "Syntax Error" when trying to view one of these scripts. Starting in Burli 220n, it is possible to have a space anywhere in a Script Template's name and the Burli Web Server will display those scripts properly.

FEATURE: Permanent Web tabs

Burli now has permanent Web Tabs which will always take you to specific websites. These tabs are independent of each other and will allow you to click between news stories and web tabs returning to where you left off. The settings are newsroom wide so all workstations will see the same permanent Web Tabs each time and are in addition to the current Web tab.

The web tabs will be sorted alphabetically across the top and each website will load for the first time once you click on them.

cid:image001.png@01CE2F88.33E88FE0

To enable this feature, there is a new MAIN.INI section required:

[WebTab]

URL1=Twitter~www.twitter.com

URL2=Wikipedia~www.wikipedia.com

URL3=Weather~http://www.weatheroffice.gc.ca/city/pages/bc-74_metric_e.html

URL4=Google~www.google.com

The format is:

URL#=Friendly Name~Website URL

Where # is the next number in the list.

The navigation buttons can Refresh the page or reload the particular Web Tab’s fixed “Home” page.

FEATURE: Display original audio attachment name in email body

Starting in Burli 220p, Burli will show the filename for each audio file included in an Email. This will allow the newsroom to easily identify which clip is which and in what order. The list of filenames is included at the very end of the email under the heading “Original audio attachments”.

cid:image004.jpg@01CE3072.BEF62350

FEATURE: Rename Scott Dispatch to WOA

Burli Scott dispatch can now be renamed to “WOA” or “wide Orbit” or whatever the end user prefers. This was done because the file settings are the same but the user may not be aware that the two are compatible.

Instructions for Scott.ini

a.           Open Scott.ini

b.          Use the following syntax for the Name= setting:

Syntax

[Group<x>]

Name=[Group display name]~[“scott” replacement text]

Where <n> is a sequential number starting at 1

Example

[Group1]

Name=CBRD Traffic ~WOA

c.           Save Scott.ini

d.          Restart Burli

cid:image001.png@01CE375B.8AFFE1E0

Burli Email capture improvements

We have modified the email ingest to allow for various encoding lengths. Previously, Burli did not accept certain encoding formats for Base64 which could potential cause a crash.

FEATURE: Burli Text + Audio improvements

We have added to the functionality of the Build Text + Audio feature. Users can now use this feature in Network Folders as well as Work Folders. Also, when the user clicks on a Text story and an audio clip, the old items are now kept.

FEATURE: Additional Audio formats can be dragged from FTP sites

Burli now supports additional audio formats for Drag and Drop from an FTP site. Burli now supports *.wav,*.mp3,*.mp2,*.mpg,*.snd,*.wma,*.m4a,*.aif,*.aiff,*.aifc,*.aac,*.amr from FTP sites with the addition of QuickTime and the Burli QuickTime DLL being installed on the workstation.

FEATURE: Delete users from Burli security when they are no longer in Active Directory

We have improved the logic in requesting username from the Active Directory to compare user lists compared to previous versions. Burli will request the Login Names from the AD and then compare the list to the users in Burli Security and ignore UPPER and lower case in the usernames. Any users not in the AD will be removed from the Burli Security unless they are in the Admin group. Only 100 users per operation will be deleted. The Ctrl+F6 command is "OrphanUserData".

*** Please note that you need to run this command as administrator and you should back up the Security.dta file (in ~\Burli\Settings\) beforehand. ***

RMS Normalization issue fix

In Burli 220q, a new feature was added to keep the original audio file after RMS normalization. Unfortunately, if you did not add the new MAIN.INI setting to keep the original file, Burli would crash. This has now been resolved in Burli 220u.

FEATURE: Prevent Quickplay files from being overwritten during playback

Starting in Burli version 221k, we have added a feature to prevent a QuickPlay audio file from being overwritten during playback. There is a QUICKPLAY.INI setting required for this feature to be enabled:

[QuickPlay]

PreventPlayOverwrite=Yes

The default value is No.

QuickPlay Dropdown menu cannot display the & (ampersand) character

We have fixed an issue that would not allow the QuickPlay Drop down window from displaying the & (Ampersand) character. For example “Weather & Traffic Sounder” is now displaying as expected.

FEATURE: Support for RSS feeds with Traditional Chinese characters

Starting in Burli 221j, Burli supports RSS feeds which include Traditional Chinese Characters (Big5 encoding). This change will affect ALL RSS feeds being ingested into Burli. There is a new setting required in MAIN.INI for this new FEATURE:

[Newswires]

UTF8toBig5=YES

FEATURE: Check audio files that are submitted to the Web Server

Burli Web Server now has a feature to check the audio files that are posted with a new story regardless of the format. This way, Burli makes sure that the file is valid even if the format is the same as the station’s default format. If the file fails the error checking, the user will be shown the message, “Invalid audio detected. Item can’t be submitted.” The user can then retry sending the audio again or try again with different audio. The new MAIN.INI setting is:

[Startup]

AudioConversionAlways=Yes

The default value is No

This setting is not normally required. Please only use this feature on the advice of Burli Support.

FEATURE: Ability to Dispatch audio from any Clip holder

Starting in version 221f, users are able to Dispatch from any Clip Holder in Burli with a Right-Click. This will allow users to send Audio clips to their Automation systems or any other Dispatch locations that have been configured.

cid:image014.png@01CE531B.80090420

HTML Email is cut off before the end

We have fixed a limitation in the Burli Email capture which would limit any one email to 1000 lines. In Burli 221d, this limitation has been increased to 10000 lines.

Burli loads stories in the wrong order when using non Windows file servers

We have fixed a bug where stories would be loaded in the wrong order when using a Non-Windows file server. This effects version 216a-221b.

Burli cannot display European Unicode characters from Twitter feeds

Starting in Burli 221c, Burli can now display European Unicode characters included in Twitter messages correctly.

FEATURE: Folder Split for Aliased folders

Starting in Burli 221c, Burli now allows the users to display their Aliased folders in columns of specific length instead of a long scrolling list. The MAIN.INI setting to turn this feature on is:

[Startup]

AliasedFolderSplit=[n]

Where [n] is the number of network folder names to display in a continuous column in the Open|Network Folders menu option before starting a new column.

The value of 0 will turn this setting off and show a scrolling list instead. This is also the default setting without this entry.

FEATURE: Additional Audio formats can be dragged from FTP sites

Burli now supports additional audio formats for Drag and Drop from an FTP site. Burli supports *.wav,*.mp3,*.mp2,*.mpg,*.snd,*.wma,*.m4a,*.aif,*.aiff,*.aifc,*.aac,*.amr from FTP sites with the addition of QuickTime and the Burli QuickTime DLL.

FEATURE: Delete users from Burli security when they are no longer in Active Directory

We have improved the logic in requesting username from the Active Directory to compare user lists compared to previous versions. Burli will request the users list from the AD and then compare the Login names list to the users in Burli Security. Any users not in the AD will be removed from the Burli Security unless they are in the Admin group. Only 100 users per operation will be deleted. The Ctrl+F6 command is "OrphanUserData".

*** Please note that you need to run this command as administrator and you should back up the Security.dta file (in ~\Burli\Settings\) beforehand. ***


QUICKLIST OF FEATURES SINCE BUILD 195

(most recent on top)

FEATURE: Copy multiple Remote or Local Script stories
FEATURE: POP3s Email Capture
FEATURE: Dispatch to Zetta Automation
FEATURE: Dispatch to DJB Radio Automation

FEATURE: WINS Downloader newswire
FEATURE: Flash Burli task bar icon when a chat message arrives
FEATURE: Side Scrolling in the Single Track Editor when zoomed in
FEATURE: Sort in the FTP Client Window
FEATURE: Auto-logout at specific clock time or after X minutes
FEATURE: FTPS and SFTP support in Burli
FEATURE: 4 channel PCM files supported
FEATURE: MP3 for the Internal Newswire | AudioFileSizeLimit setting

FEATURE: FTP transfer for Wideorbit dispatch

FEATURE: Receive IPAWS alerts from FEMA (multiple States or Counties)

FEATURE: Display Sub Heading from PAP NewsML

FEATURE: Global Connect Newswire supported

FEATURE: Upload to SoundCloud

FEATURE: Option to force all Network Folder items to the Recycle Bin

FEATURE: OMT Automation | Dispatch to multiple UNC paths

FEATURE: Archive audio in MP2 format

FEATURE: .S48 file format supported for import

FEATURE: Microsoft SQL Database now supported

FEATURE: Dispatch attachments using Burli Internal Newswire

FEATURE: Westwood One News feed

FEATURE: CNN Wire feed

FEATURE: Finder Displays Filters in order of the InQueue

FEATURE: Second IRN XML Newswire

FEATURE: Improve the BuildAudioTextStory feature with Append

FIXED: Story order changed unexpectedly when dragging between folder/Scripts

FEATURE: Improve the BuildAudioTextStory feature with Append

FEATURE: Time of Day option for Quickplay sub-group

FEATURE: Support for the Canadian Press XML newswire

FEATURE: Internal Newswire dispatch window | Display ‘category’ value in 'category display name' field

FEATURE: Cartchunk next marker | Master Control (rcs.ini)

FEATURE: Option to rename Internal Newswire menu

FEATURE: Support for the PAP NewsML1.2 newswire

FEATURE: Faster scroll speed for TV mode Prompter

FEATURE: AudioUpload.ini | Rename "Audio Upload:" in the Dispatch dialogue

FEATURE: Twitter Search API

FEATURE: NAAD Alert Level Popups

FEATURE: "Exclude" Boolean Filter/Search function

FEATURE: Support for Report-IT mobile apps from Tieline

FEATURE: Support for Cantemo MAM

FEATURE: Refresh VN Filter tree

FEATURE: RadioVoodoo Service newswire

FEATURE: Open default External Web Browser when clicking on links

FEATURE: Improve imported low bitrate PCM audio quality

FEATURE: Wide Orbit automation dispatch

FEATURE: Quickplay rotation items | auto loop playback

FEATURE: Full HTTPS support for Twitter

FEATURE: Dispatch from the story Clip Holder

FEATURE: RCS.ini dispatch convert to specified format per Cart in a Group

FEATURE: Podcasting | no SQL database

FEATURE: Internal Newswire | Display upload confirmation (Success/Failure)

Fix audio quality of Time Stretch

FEATURE: Burli Internal Mail (B-Mail) access via web server

FEATURE: Single machine (hasp id) to generate Script templates

FEATURE: 12 hour or 24 hour format for the QuickPlay TIMER

FEATURE: Time Stretch/Shrink option in the Single Track Editor

FEATURE: Add metadata to Tieline stories

FEATURE: Compress files to MP3 on Internal Newswire

FEATURE: Auto generate daily script

FEATURE: Always convert audio files submitted via Web Server

FEATURE: Prevent Quickplay files from being overwritten during playback

FEATURE: Support for RSS feeds with Traditional Chinese characters

FEATURE: Delete Burli security users if not in Active Directory

FEATURE: Apple Audio formats Drag and Drop from FTP sites

FEATURE: CRN (Corus Radio Network) News feed

FEATURE: SDA xml newswire | newsml version 1.2

FEATURE: Scott.ini | Rename "Scott" in the Dispatch dialogue

FEATURE: Display original audio attachment name in email body

FEATURE: Permanent Web tabs

FEATURE: ATS newswire (NewsML-1.2)

FEATURE: Omnisport newswire

FEATURE: Security for Aliased Folders

FEATURE: Internal Newswire | User rights for sending

FEATURE: Twitter API 1.1

FEATURE: Post to In-Queue via a Right Click Menu | JAWS screen reading software

FEATURE: AAC and AMR format audio support

FEATURE: Remote Network Folders via VN

FEATURE: Aliased Network Folder Split

FEATURE: SkyNews FTP newswire

FEATURE: NAAD Emergency Alerts, Atom Feed

FEATURE: Body search via the Web Server & VN

FEATURE: GPO triggers when Burli record started

FEATURE: Quickplay Disable Drag and Drop

FEATURE: Negative logic GPIO closures in Quickplay

FEATURE: Multi select/delete in the Archive | Ctrl-F6 command

FEATURE: Toggle audio play counter between count up and count down

FEATURE: Optionally force Script logs ON at all workstations

FEATURE: RCS AutoDispatch | Multiple Carts / UNC paths

FEATURE: Template for default text in new Stories (Local Work folders ONLY)

FEATURE: Use the ORDER.TXT file in Burli | Script Template display order

FEATURE: Auto create users at launch | predefined set of user rights

FEATURE: Automatically backup server Settings directory to the local root

FEATURE: Update Twitter logo

FEATURE: search in remote VN In-queue nodes (not Script VN)

FEATURE: EAS Newsroom format support

FEATURE: Support Plain Text UTF-8 email and extended characters in UTF-8 and  iso-8859-2

FEATURE: MarketWire NewsML G2 format

FEATURE: AP PrimeCuts | Support Categories, Sub-categories and File Type

FEATURE: NewsML G2 formatted newswire support

FEATURE: Twitter user rights for sending

FEATURE: Clock time in Prompter | Display 12 or 24 hour time format

FEATURE: Dropbox newswire feeds (Audio, Text)

FEATURE: Receive OAuth certificate with Ctrl+F6 command

Prevent two instances of Burli from running on the same PC

FEATURE: AP PrimeServer Audio files | Automatically create text+audio story

FEATURE: Allow filtering <footageType> tag in CNN Newsource wire

FEATURE: NBC News Radio (aka Dial Global) newswire

FEATURE: Update AP logo

FEATURE: File based CNA newswires (CAP & CEP)

FEATURE: CNN FTP audio distribution

FEATURE: Custom Icons for Virtual Newsroom Nodes

FEATURE: Show progress bar during RCS Dispatch

FEATURE: HASP license auto update | Update via internet

FEATURE: Suppress HASP Warning messages

FEATURE: WebServer | View Network folder stories in alphabetical order

FEATURE: Send multiple audio-only stories in a single e-mail

FEATURE: Ctrl-F6 command | Dump Audio Device info (Name & ID#)

FEATURE: Vericorder ingest | Apple File Format (.m4a, aif, aifc etc..)

FEATURE: CBS Downloader | Support Multiple audio file types

FEATURE: MetroSource Newswire

FEATURE: ABC RSS Wire

FEATURE: Compile Field Mode Icons into executable (burli.exe)

FEATURE: Compile multiple Script Audio clips into one audio file

FEATURE: 'Combine as a single Story' right-click option

FEATURE: Convert Audio to Text  Story (with audio)

FEATURE: Hide sender's email address from the Burli ticker and InQueue

FEATURE: Display UTC (GMT) time story arrived in body of wire stories

FEATURE: Dispatch to NexGen

FEATURE: Prevent double-click for Script stories (Author pop-up window)

Scripts Browser text editor (upper half) should be read-only

FEATURE: Atom feeds in Newswires-2

FEATURE: Bypass Quickplay deck playback | Mouse click | Advanced Prompter Buttons

FEATURE: Adjustable width for Button Bar | Advanced Quickplay Prompter Buttons

FEATURE: Disable manual logout (Ctrl+L)

FEATURE: Hide the "Actions" tab in the Audio Logger

FEATURE: Twitter API for Ingesting Tweets

FEATURE: Continuous contact closure (GPO) from Quickplay

FEATURE: Story Separator lines in TV Prompter

FEATURE: Adjustable pane (frame) position for TV Scripts

FEATURE: Multiple Dispatch Paths | Maestro.ini

FEATURE: Apple file ingest (Quicktime API) in newswires-2 and e-mail and Manual Import

FEATURE: In-queue snapshot files | corrupt .RDF files

FEATURE: Edit Network folder stories via the Burli Web Server

FEATURE: Dispatch to Maestro automation

FEATURE: TV Prompter Mode | Reverse (not split, rotate or flip) Text display

FEATURE: Use Slug title for FolderDrop audio file name

FEATURE: Auto-dispatch to scripts

FEATURE: GPIO integration with Harris VM Quadra IP protocol

FEATURE: GPIO integration with Axia Livewire Protocol

FEATURE: Auto RMS normalize after recording

FEATURE: Additional support for Genesys playout system in Burli

FEATURE: SeaLevel 8111 (81XX series) device (Windows 32bit)

FEATURE: Add support for ANP XML wire

FEATURE: Access email attachments via Web Server

FEATURE: Button to play only last x3 seconds of audio for 'out' words

FEATURE: Play Counter | Count number of plays for Script audio

FEATURE: Multiple Dispatch Paths | Master Control (rcs.ini)

FEATURE: Support for ingesting U-LAW compressed WAV files as email attachments

FEATURE: Auto-Archive ANY Filter item in the In-Queue

FEATURE: RMS Normalize "postrecaction" items

FEATURE: Scripts Export over VN | Remote Hosts

FEATURE: Add Apple file extensions to the Open External File dialogue

FEATURE: automatically RMS normalize all audio entering In-Queue

FEATURE: Send to Twitter

FEATURE: Passive Mode FTP support

FEATURE: XML Export (newsML) | Edit newsML tags in Scripts body

FEATURE: Poddio iPhone data ingest

FEATURE: Scripts Access through VN | Remote Scripts

FEATURE: MP3 support in the web server

FEATURE: RMS Normalize a selection of audio | disable peak

FEATURE: Local Root diskspace advisory

FEATURE: Script timing | Calculate (SUM) timing for sections all breaks

FEATURE: Main.ini setting for In Queue buffer

FEATURE: Ctrl-F11 / Ctrl-F12 to include select font schemes

FEATURE: FTP destination(s) for RCS.ini

FEATURE: Chat scroll bar | Keep focus when new messages arrive

FEATURE: Add Script Templates to Burli Security

FEATURE: Master key commands for ON-AIR / EDIT mode

FEATURE: Pane/Frame | Save position settings in Windows Registry

FEATURE: Custom Newswire icons

FEATURE: Control of scroll direction in tickertape

FEATURE: GMG custom newswire server/capture

FEATURE: Auto Dispatch when posting items to specific In-queue filter

FEATURE: network folder recycle bin

FEATURE: Spell checker

FEATURE: Podcasting