almost 3 years ago

20220330 - Release Notes

by Blane Zemunik

Doohly Player Version 3.0 is now available for download.

Playback Performance Efficiencies/Updates
- Backend updates have increased media player performance and efficiency for users, resulting in better performance for devices.

The Doohly Player would rarely not show content at restart.
When the Doohly Player app started, content would sometimes render in the top left corner of the display.

almost 3 years ago

20220310 - Release Notes

by Blane Zemunik

Users can now set individual creatives' playback scaling type. There are three different options available:

Scale To Fit: Keep the creatives aspect ratio and resize to fit the frame.
Stretch To Fill: Ignore the creatives aspect ratio and stretch it to fill the entire frame.
Scale To Fill: Keep the aspect ratio of the creative and resize to fill the frame, overflow will be cropped and not displayed.

Users can now select and delete multiple folders within the “Creative Library”.
Within the device details screen, the brightness and volume options have been removed.
There are some other slight UI changes you may notice.

When content finished playing and no more content was scheduled to a player, it would not clear the last creative.
When using HTML content and skipping the last creative, the player would stop on the current creative.
Player v2.1.1 wouldn’t play content immediately after registration.

almost 3 years ago

by Blane Zemunik

Programmatic HTML Packages
- HTML Packages can now instruct the Doohly player to “skip” to the next creative, allowing programmatic HTML Packages to skip when there are no ads available.
- These “skips” are tracked and Doohly can exclude skipped plays from reported plays.
Device Address
- Users can now assign a specific address to a device. This can either be pulled directly from the map pin or specified as a different location. We’ve added this feature to allow locations such as shopping centres and hospitals to specify exact device locations whilst using a common descriptor.
- As part of this updated feature, existing devices will automatically have their location updated.
- This is also an important requirement for future feature updates.

When editing a device and changing the orientation to portrait, the frames on the device would display incorrectly.
Users were unable to delete bookings when making use of the public Doohly API due to a mapping error.
When renaming a device, the associated reference image would be removed and disappear.
The UI would allow "Completed" and "Archived" bookings to have frames removed and added. (This had no effect on reporting)
Devices that have been unregistered were still calling the playlist/settings endpoint, causing API errors.
When attempting to move multiple folders in the creative library via drag and drop the folders would not move
When selecting multiple folders in the creative library and right-clicking to move, there would be an error pop up and the folders would not move.

almost 3 years ago

by Blane Zemunik

Users can now see which frame a booking is booked for within “Device Details”.
In the “bookings” list, users can now see what campaign each booking is associated with. This enables users to now filter and sort bookings by campaign name.
The order in which ‘x',‘y’ and ‘width’, 'height’ inputs have been reversed in both Canvas and Frame setup to be more consistent with other software products.

When shrinking the internet browser window with the navigation menu expanded, the Name column in the list of bookings in the Campaign Details screen would disappear.
When viewing the bookings for a device, if the same booking is booked against multiple frames on that device and a booking is removed from any of the frames, the booking would actually be removed from all frames on that device.
When viewing the bookings page when empty, it would display the following incorrect error message “There are no bookings for this frame”. This has been removed to avoid confusion.

almost 3 years ago

by Blane Zemunik

When assigning a video to a booking a video could have a duration of `6.45s` however the duration stored & used by the players was rounded down to the value of `6s`. This means that videos didn't always play for their full duration as intended.
When a device was deregistered while the device did not have a socket connection to the server the player will get stuck in a state where it thought it was still registered but the socket authorisation would prevent it from connecting again. The only way to get the player out of this state was to restart the player which would require physical access to the player
When a device had an active booking assigned to it that had a play method of "Individual Creatives Per Loop" and without any creatives assigned, the player stopped playing even if there are other bookings that should play.