Jamcast 1.8 Released

by Scott Saturday, April 28, 2012

It’s here! We’re happy to announce the availability of Jamcast 1.8. This release marks a major milestone in ongoing efforts to prepare the Jamcast platform for an improved wide-release API. Announcements regarding the Jamcast API and availability of plugins are coming next.

Introduced in Jamcast 1.8 is an improved software update system. Although a basic updater actually does exist now (it will push 1.8 out to the install base), the new system includes the ability for us to push notes along with the update. There is also a new notification present in Jamcast Server Manager.

New Logging SystemAlso notable in this release is an overhauled logging system. The three legacy logfiles (medialog, importlog, and upnplog) have all been moved to a new \logfiles subdirectory and consolidated to a single logfile that rolls over daily. The logfiles are also now formatted in accordance to log4J/log4net layout specifications which allows you to view the logfiles using a compatible viewer/tailing program if desired. Additionally, users can control the level of logging detail and number of days logfiles are kept via Jamcast Server Manager.

There’s a bunch more, too. Check out the change log:

- FIX: removed unnecessary service status notification in UI
- FIX: fixed value decoding for PluginDataProvider selects
- FIX: invalid UPnP BrowseMetadata response on Virtual Soundcard
- FIX: Performing Artists container returning incorrect metadata
- FIX: Folders container returning incorrect metadata
- FIX: remote track type in iTunes library not handled (will skip
  until iCloud streaming support is available)
- ADD: new logging system, log management features
- ADD: new software update system
- ADD: API - added method to request server restart from plugin
  configuration panel
- ADD: API some obsolete / redundant code removed / refactored
- ADD: API version upped to 3.0
- ADD: improved logging for failed UPnP actions	
- ADD: better handling of invalid UPnP search criteria
- ADD: UI performance enhancements
- ADD: link to plugin download page
- ADD: visual indication that plugin is installed but fail to load
- ADD: updated license.txt


Categories: Release

Apple’s iCloud Unsupported For Now

by Scott Saturday, April 14, 2012

iCloudAs users begin to migrate their iTunes libraries to the cloud, we’re sad to announce that iCloud-hosted media is not currently supported by Jamcast. For Jamcast version 1.7.6 and prior, remote iTunes tracks will actually cause import of the entire iTunes library to abrupt abnormally. While this defect has been fixed for Jamcast 1.8, moving forward remote tracks will be skipped. To continue serving up your iTunes-managed library, tracks must be stored locally.

Of course we’d love to bring iCloud support to Jamcast and will be looking into the possibilities as time goes on. Or perhaps someone will beat us to it and build an iCloud plugin for Jamcast? Stay tuned on that.

Tags: , ,


Jamcast 1.7.6 Released

by Scott Monday, April 02, 2012

First post in the new blog software! It’s been a week or two, but I’d like to take the time to formally announce the release and availability of Jamcast 1.7.6. This and the previous few releases have been building upon the 1.7 overhaul of the media and content directory services to support the new API and plugin infrastructure. The platform is solid -- this is the final release before Jamcast 1.8. Head on over to the downloads page to get your copy today.

Here’s the change log:

- FIX: API - better error reporting when plugin load fails
- FIX: Server Manager crashes when setting capture device dropdown list 
  to invalid selection
- FIX: bitrate wrong in metadata for 44.1kHz tracks
- FIX: Virtual Soundcard reporting wrong bitrate when hardware mode
  is forced by user	  
- FIX: byte order issue with WinMM capture samples	
- FIX: audioscrobbler submits tracks multiple times
- ADD: reduced request timeout on device description HTTP GET's
- ADD: better logging for device description timeouts

Hope you enjoy this release! If you run into any trouble, please let us know via the Technical Support forum.


Categories: Release