QNX^® Aviage Multimedia Suite 1.2.0 Alpha 20.12.0 Release Notes

Date of this edition: January 19, 2009

Target OS: This software is compatible with target systems running QNX^® Neutrino^® 6.4.0.

Host OS: You must have already installed the QNX^® Momentics^® development suite  6.4.0 as a self-hosted QNX Neutrino system, or on one of the following hosts:

---

For information on installing this package, see the Installation Note.

---

Contents

• What's in this package?
  • Notices
  • Documentation
  • What's new in this release
  • QNX Aviage Multimedia Core 1.2.0 binaries
  • Headers and libraries
  • Sample applications
  • Binaries for packages requiring special licenses
  • Binaries for other packages
• Known issues

Throughout this document, you may see reference numbers associated with particular issues, changes, etc. When corresponding with our Technical Support staff about a given issue, please quote the relevant reference number. You might also find the reference numbers useful for tracking issues as they become fixed.

---

The QNX Aviage Multimedia Suite: is compatible with generic filesystems, such as FAT32, ISO9660, and others provided with the QNX Neutrino operating system or with a QNX board support package. Media-specific filesystems, such as for Apple iPod devices and Microsoft PlaysForSure devices, are provided in the relevant QNX Aviage Multimedia Suite packages. uses QDB, QNX's embeddable SQL database server that is based on the SQLite project (http://www.sqlite.org) and supports most SQL-92 syntax. For more information about what SQL-92 syntax SQLite doesn't support, see “SQL Features That SQLite Does Not Implement” on the SQLite web site.

---

What's in this package?

This package contains libraries, binaries, and source code for sample applications for the Multimedia Engine running on QNX Neutrino.

The main archive, mme_build20.12.0_jan16_09.zip, contains the following:

patch-630SP2-0315-mmedia-01-15-1650.tar

MME core product binaries.

patch-630SP2-0999-extra-aac-01-15-1650.tar

MME software codec for AAC files.

patch-630SP2-0315-extra-drm-01-15-1650.tar

MME binaries for DRM support.

patch-630SP2-0315-extra-mp3-01-15-1650.tar

MME binaries for MP3 support.

patch-630SP2-0315-extra-ipod-01-15-1650.tar

MME binaries for iPod support.

patch-630SP2-0999-extra-ipp-01-15-1650.tar

MME software codec for H.264 files.

patch-630SP2-0315-extra-pfs-01-15-1650.tar

MME binaries for PFS device support.

patch-630SP2-0315-extra-wma9-01-15-1650.tar

MME software codec for WMA files.

patch-630SP2-0999-extra-mp3-01-15-1650.tar

MME software codec for MP3 files.

---

You should replace existing .sql and configuration files with the files included in this release. Benchmarks for this release are available on request. This alpha release has not been tested on Jacinto platforms.

---

Notices

• MME requires Neutrino 6.4
• Imcompatibility with older MME releases

MME requires Neutrino 6.4

As of this release the Aviage MME releases require a Neutrino 6.4 system.

Imcompatibility with older MME releases

This release includes changes and upgrades that make it incompatible with older releases, as follows:

• SQLite has been upgraded to SQLite 3.6.3, and the MME and QDB now use SQLite 3.6.3:
  • This SQLite release uses less malloc() and free() calls than did releases prior to 3.6.1. Use of this SQLite release has resulted in performance improvements for MME synchronization operations.
  • The QNX file libz.so is now required on the target system for all applications that use libsqlite3.so. This file is required by the SQLite addon “CEROD”, which handles encrypted or compressed databases.

  Any applications that link against the SQLite library directly must be recompiled.

• This release implements a new client library, which renders it incompatible with releases older than the Aviage MME alpha 20.4 releases.

  You must recompile and relink all client applications to use this release.

• MDSs (metadata synchronizers) have been replaced by MDPs (metadata plugins).

  You must change the <MDS> element in your configuration file to <MDP>. See Metadata plugins replace metadata synchronizers below.

---

A client application compiled against QNX Aviage Multimedia Suite (MME) 1.0.n must be recompiled in order to work with QNX Aviage Multimedia Suite (MME) 1.2.0. You must update all system components to QNX Aviage Multimedia Suite 1.2.0. Alpha 20.12.0. Your environment must not contain both 1.0.n and 1.2.0 multimedia components.

---

Documentation

This release includes the following preliminary MME 1.2 documentation:

mme_patch_build20.12.0_inst.html

The installation note. Please read it before installing.

mme_patch_build20.12.0_rel.html

The release notes (this file).

ReleaseNotesMMF.20.x-7.mht

Release notes for the Margi component.

mme_intro.pdf

The Introduction to the MME, which includes:

• MME Architecture
• MME Quickstart Guide
• MME Frequently Asked Questions

mme_dev_guide.pdf

The MME Developer's Guide.

mme_api_ref.pdf

The MME API Library Reference.

mme_utils_ref.pdf

The MME Utilities Reference.

mme_config_guide.pdf

The MME Configuration Guide.

mme_tn_ref.pdf

MME Technotes.

qdb_dev_guide.pdf

The QDB Developer's Guide.

What's new in this release

This release introduces many new features and improvements, and deprecates some features available in older releases:

• New features
• Deprecated and removed features

New features

The table below lists the most significant new features and updates that were implemented in this release. For more complete information about these and other features in this release, please refer to the MME documentation.

Upcoming changes to the <interface> element

In this release the <interface> element returned with the device configuration by mme_device_get_config() uses sub-elements for the different device and connection types. For example, for a an iPod connected through a USB transport, the <interface> element and sub-elements might look as follows:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<device api_version="1">
	<interface>
		<usb path="1" devno="14" vendorid="0x5ac" productid="0x5ac"/>
	</interface>
	...

In the next release:

• The various <interface> sub-elements will be replaced by the <interface> attribute type.
• The <interface> now supports the attributes that were previously sub-element attributes (devno, vendorid, etc.).

Thus, the information in the example above will be presented as follows:

<interface type="usb" path="/dev/usb1" devno="14" vendorid="0x5ac"  productid="0x5ac"/>

An iPod connected through a serial transport will have an <interface> element with the type attribute set to “serial”:

<interface type="serial" path="/dev/ser1" />

A Bluetooth device will have an <interface> element with the type attribute set to “bluetooth”:

<interface type="bluetooth" path="/dev/wms/player1" />

---

The MME Developer's Guide describes the <interface> element as it will be in the next release.

---

Changes to synchronization behavior

This release implements some changes to synchronizations:

• CDDA synchronizations no longer combine passes
• Directed synchronizations remove missing folders from MME database

CDDA synchronizations no longer combine passes

In previous releases, CDDA mediastore synchronization passes 1 and 2 were combined in a single pass.

Starting with this release, CDDA synchronizations no longer combine these two passes. The MME now perform the files synchronization pass and the metadata synchronization pass separately for CDDA mediastores, just as it does for other mediastore types.

This change allows configurable fallback through multiple CDDA metadata synchronizers, such as Gracenotes, Musicbrainz, CDTEXT, and none.

Directed synchronizations remove missing folders from MME database

In earlier releases, if a directed synchronization was pointed to a folder that no longer existed, but was in the MME's database, the synchronization would fail.

With this release, a directed synchronization does not fail when it is unable to find a folder that is in its database. Instead, it deletes the folder and its contents from the MME database.

This change means that the client application can remove a folder from a mediastore, then use directed synchronization to remove this folder from the MME database.

Metadata plugins replace metadata synchronizers

As part of the MME's improved metadata handling, in this release (with one exception) metadata plugins replace the metadata synchronizers of previous releases. This change means that you must change the <MDS> element in mme.conf into an <MDP> element. For example:

<MDP>
    ...
    <dvdifo skipdurationzero="true">
        <dvdaudio>
            <devicefid create="true"/>
            <chapterfids create="true"/>
        </dvdaudio>
    ...
    <cdtext rating="80"/>
    ...
</MDP>

---

The Gracenote client mdp-gracenote_client.so replaces mds-gracenote_client.so.

---

io-media DLLs

Starting with this release io-media-generic no longer links statically to filters. It therefore now requires more DLLs to be present that it did when it linked statically to filters. The following filters and streamers are now required by the io-media default configuration:

• audio_writer.so
• cdda_parser.so
• cdda_streamer.so
• fildes_streamer.so
• mpega_parser.so
• queue_filter.so
• stream_reader.so

The default io-media configuration loads some filters and streamers permanently into memory; other filters are loaded and unloaded dynamically when necessary. Some filters are loaded permanently because they are needed by the majority of graphs; if any of these required filters are missing, there is a high probability that io-media will not be able to play any media. These filters are, therefore, specified as required by the default configuration; if any of these filters is missing, io-media will exit at startup.

Some other filters are loaded permanently because they might be used for potentially high-bandwidth operations that could be significantly slowed down by having to load and unload filters. These filters typically support a particular operation or media type; if they're missing, io-media will not be able to play some media but will have no problems playing other media. Some of these filters are shipped in a separate, optional package, and may not be present on some targets. These filters are flagged as optional in the default configuration; if they are missing, io-media logs a warning to the system log, but does not treat the situation as a fatal error.

Configuring the set of required filters and streamers

You can change the minimum DLL set that io-media maintains in memory in order to make optimal use for your environment of the system resources you have available. Generally, the more DLLs in memory, the better the performance but the greater the memory required.

The io-media configuration file includes multiple keepdll elements under the mmf module's module-options element. Each keepdll element determines if the named filter or streamer is in the set or is optional.

The default setting is required: if it the DLL is missing, log an error and exit. Thus, in the example below:

• tmpfile_streamer is optional (because it is only used for playback during ripping) — it is not kept in memory, and io-media starts even if this streamer is missing
• stream_reader is required — it is kept in memory, and io-media will not start if this streamer is missing

module-options {
    ...
    keepdll {
        name = "tmpfile_streamer"
        optional = yes
    }
    keepdll {
        name = "stream_reader"
    }
    ...
}

Default io-media configuration shipped with the release

Starting with this release, to facilitate updating io-media default configuration files are included as a reference in the release package under etc/.

These files have the format io-media-version.cfg. For example, io-media-generic.cfg is the configuration file for io-media-generic.

Deprecated and removed features

The table below lists the features and capabilities that have be deprecated or removed from this release.

library_extra table

MME performance has been improved by the integration of the library_extra table columns into the library table. These columns are:

• copied_fid
• duration
• fid
• fullplay_count
• last_played
• permanent
• playable

If the removal of the library_extra will cause problems with your projects, as a temporary measure until you have removed all references to the library_extra from your applications, you can uncomment the following “CREATE VIEW” line in mme_library.sql to create an SQL view that mimics the library_extra table:

-- CREATE VIEW library_extra AS select fid, last_played, fullplay_count, duration, copied_fid, playable, permanent FROM library;

---

In order to benefit from the performance improvements gained by the integration of the library_extra table's columns into the library table, you should remove references to the removed table from your applications as soon as possible.

---

QNX Aviage Multimedia Core 1.2.0 binaries

The standard QNX Aviage Multimedia Suite binaries are delivered in the patch-630SP2-0315-mmedia-mm-dd-hhmm.tar pathc. They include the binaries, DLLs, and SQL configuration files required to run the QNX Aviage Multimedia Core 1.2.0 and support binaries. Binaries for features requiring special licenses are listed under “Binaries requiring special licenses” below.

These files are installed under target/qnx6/, under the subdirectories for the supported target platform:

• lib/dll/mmedia/aac_parser.so — AAC parser filter DLL for io-media.
• lib/dll/mmedia/ade3_writer.so — (ARMLE targets only) Audio Decode Engine support.
• lib/dll/mmedia/audio_streamer.so — a streamer for reading audio from a sound card.
• lib/dll/mmedia/audio_writer.so — a filter for standard audio output to a PCM device.
• lib/dll/mmedia/cdda_parser.so — the CD-ROM parser filter for io-media.
• lib/dll/mmedia/cdda_streamer.so — the CD-ROM streamer filter for io-media.
• lib/dll/mmedia/damping_audio_writer.so — a filter for fading a PCM stream in or out.
• lib/dll/mmedia/fildes_streamer.so — the file streamer for io-media.
• lib/dll/mmedia/http_streamer.so — internet stream writer for io-media.
• lib/dll/mmedia/media_streamer.so — media streamer filter for io-media.
• lib/dll/mmedia/mp4_parser.so — MPEG-4 video parser for io-media.
• lib/dll/mmedia/mpega_parser.so — MPEG audio parser for io-media.
• lib/dll/mmedia/ogg_decoder.so — (PPCBE, SHLE and x86 targets only) Ogg Vorbis decoder for io-media.
• lib/dll/mmedia/ogg_encoder.so — (PPCBE, SHLE and x86 targets only) Ogg Vorbis encoder for io-media.
• lib/dll/mmedia/queue_filter.so — buffer queue filter for io-media.
• lib/dll/mmedia/rawfile_writer.so — raw file writer filter for io-media.
• lib/dll/mmedia/stream_reader.so (PPCBE, SHLE and x86 targets only) — stream reader filter for io-media.
• lib/dll/mmedia/tmpfile_streamer.so (PPCBE, SHLE and x86 targets only) — temp file streamer filter, used to support concurrent reading and writing of a file for io-media.
• lib/dll/mmedia/wav_parser.so — WAV file parser filter for io-media
• lib/dll/mmedia/wavfile_writer.so — WAV file encoder/writer filter for io-media.
• sbin/io-fs-media — a version of io-fs with built-in modules for PFS, iPod, and tmpfs (requires appopriate licenses).
• sbin/io-media-generic — generic version of io-media.
• sbin/mme-generic — generic version of mme.
• usr/bin/qdbc — a utility for executing statements on a qdb database.
• usr/lib/libaoi.so — the addon interface library, required by io-media
• usr/lib/libaoi.so.1
• usr/lib/libmme.so
• usr/lib/libmme.so.1
• usr/lib/libmmedia.so — multimedia library, required by the MME and io-media.
• usr/lib/libmmedia.so.1
• usr/lib/libmmfilter.so — filter support library, required by the MME and io-media
• usr/lib/libmmfilter.so.1
• usr/lib/libogg.so (PPCBE, SHLE and x86 targets only) — Ogg Vorbis support
• usr/lib/libogg.so.1 (PPCBE, SHLE and x86 targets only)
• usr/lib/libqdb.so — required for dynamic linking to libraries
• usr/lib/libqdb.so.1 — required for dynamic linking to libraries
• usr/lib/libsqlite3.so — SQLite 3 library, used by qdb.
• usr/lib/libsqlite3.so.1
• usr/lib/libvorbis.so (PPCBE, SHLE and x86 targets only) — library for Ogg Vorbis.
• usr/lib/libvorbis.so.1 (PPCBE, SHLE and x86 targets only)
• usr/lib/libxml2.so — libxml2 support.
• usr/lib/libxml2.so.1 — libxml2 support.
• usr/sbin/qdb — the QDB database binary.

These SQL support files are installed under target/qnx6/sql/:

• mme.sql — the MME configuration schema.
• mme_connect.sql — connection schema.
• mme_custom.sql — the configuration schema for a custom table.
• mme_data.sql — the customer configurable default data.
• mme_library.sql — the MME library schema.
• mme_temp.sql — the in-memory MME schema.
• mmgui.sql — the mmegui schema.
• qdb.cfg — the qdb configuration file.

These configuration files are installed under target/qnx6/etc/:

• iofs.fsd — io-fs configuration file.
• iofs.fsf — io-fs configuration file.
• iofs.fsm — io-fs configuration file.
• io-media-generic.cfg — io-media configuration file.
• mme.conf — MME configuration file.

Headers and libraries

The following files are included under target/qnx6/[target]/:

• bin/mme-cdripper
• bin/mmecli
• bin/mme-player-multisource
• bin/mme-player-simple
• bin/mme-shuffle
• bin/mmexplore
• bin/testapp-cmdline
• usr/lib/libiomedia.a
• usr/lib/libmme.a
• usr/lib/libmmeS.a
• usr/lib/libqdb.a
• usr/lib/libqdbS.a
• usr/lib/libxml2.a
• usr/lib/libxml2S.a

The following files are included under target/qnx6/usr/include/:

• cipher.h
• iomedia/api.h
• iomedia/events.h
• iomedia/types.h
• mm/charconvert.h
• mm/types.h
• mme/config.h
• mme/event.h
• mme/explore.h
• mme/interface.h
• mme/metadata.h
• mme/mme.h
• mme/types.h
• mmedia/media_error.h
• mmedia/media_event.h
• mmedia/media_interfaces.h
• mmedia/mediafilter_defs.h
• mmedia/medialib_defs.h
• mmedia/mmedia.h
• qdb/qdb.h
• sqlite3.h
• sys/dcmd_dio.h
• sys/dcmd_fsys.h
• sys/dcmd_io-media.h
• sys/dcmd_media.h
• sys/scsi_cmds.h
• sys/uuid.h

In addition to the files listed above, target/qnx6/usr/include/ includes the libxml directory with third-party header files for libxml2.

Sample applications

Sample applications with their source code and required headers and libraries are delivered in the QNX Aviage Multimedia Core 1.2.0 patch patch-630SP2-0315-mmedia-mm-dd-hhmm.tar.

Sample source code

The sample source code is installed under target/qnx6/examples/*. These applications illustrate various features and functionality provided by the MME. You can view command-line options for these applications by typing “use” then the application name. For example: use mmecli will list the command-line options for mmecli.

The sample applications are:

• avrcpexample — an io-fs-media module example for Bluetooth support.
• mme-cdripper — rip and play media.
• mmecli — a command-line interface to the MME.
• mme-player-multisource — enable selection of media from different sources.
• mme-player-simple — simple media player, with unlimited SQL requests.
• mme-shuffle — just play some tracks.
• mmexplore — an example of how to use the explorer API.
• priorityfolder — an example of how to set a specific folder as a priority folder.

If you have QNX Momentics PE, you can compile the sample applications using the IDE or the command-line tools; if you have SE, you have to use the command-line tools.

Binaries for packages requiring special licenses

Binaries for features requiring special licenses are delivered in individual patches.

QNX Aviage Multimedia Software Codec for AAC 1.2.0

The patch patch-630SP2-0999-extra-aac-mm-dd-hhmm.tar contains the binaries for AAC codec support:

• lib/dll/mmedia/qnx_raac_decoder.so — an AAC audio format decoder.
• lib/libqaacd.so — library for AAC codec support.
• lib/libqaacd.so.1 — library for AAC codec support.

QNX Aviage Multimedia Software Codec for MP3 1.2.0

The patch patch-630SP2-0315-extra-mp3-mm-dd-hhmm.tar contains the binaries for MP3 codec support. They include the following files:

• lib/dll/mmedia/fraunhofer_mp3_decoder.so — (ARMLE targets only) fixed-point decoder.
• lib/dll/mmedia/xing_mpega_decoder.so — (PPCBE, SHLE and x86 targets only) MP3 floating-point decoder.

QNX Aviage Multimedia Software Codec for WMA9 1.2.0

The patch patch-630SP2-0315-extra-wma9-mm-dd-hhmm.tar contains the binaries for WMA codec support. They include the following files:

• lib/dll/mmedia/wma9_decoder.so — Windows Media 9 decoder for io-media.
• lib/dll/mmedia/wma9_parser.so — Windows Media 9 parser filter for io-media.

QNX Aviage Multimedia Interface for iPod 1.2.0

The patch patch-630SP2-0315-extra-ipod-mm-dd-hhmm.tar contains the binaries for iPod support, and a sample application. They include the following files:

• examples/io-fs/drvr/media/ipod/acp/i2c — a generic i2c implementation example.
• lib/dll/iofs-i2c-ipod.so — a module for interfacing with the iPod authentication chip.
• lib/dll/iofs-ipod.so — a module for io-fs, for iPod device support.
• lib/dll/iofs-ser-ipod.so — a module for using iPod devices through a serial connection.
• lib/dll/iofs-usb-ipod.so — a module for using iPod devices through a USB connection.

---

This package is designed for use with the QNX Aviage Multimedia Core package. If you intend to use this package independently of the Multimedia Core, please contact your QNX sales support team.

---

QNX Aviage Multimedia Interface for PlaysForSure 1.2.0

The patch patch-630SP2-0999-extra-pfs-mm-dd-hhmm.tar contains the binaries for PFS device support. They include the following file:

• lib/dll/iofs-pfs.so — a module for io-fs, for Microsoft PlaysForSure (PFS) device support.

---

This package is designed for use with the QNX Aviage Multimedia Core package. If you intend to use this package independently of the Multimedia Core, please contact your QNX sales support team.

---

QNX Aviage Multimedia Interface for WMDRM10-ND 1.2.0

The patch patch-630SP2-0315-extra-wma9-mm-dd-hhmm.tar contain binaries for DRM support. They include the following files:

• lib/dll/cipher-aes.so — a library used by the PFS module to io-fs for supporting DRM on PFS devices.
• lib/dll/iofs-msdrm10.so — a library used by the PFS module to io-fs for supporting DRM on PFS devices.
• lib/libpfscrypto.so — a library used by the PFS module to io-fs for supporting DRM on PFS devices.
• lib/libpfscrypto.so.1 — a library used by the PFS module to io-fs for supporting DRM on PFS devices.

Binaries for other packages

Binaries for packages requiring distribution licenses acquired directly from a third party are delivered separately.

QNX Aviage Multimedia Software Codec for H.264 1.2.0

The patch with the binary for H.264 video codec support is patch-630SP2-0590-extra-ipp-632-mm-dd-hhmm.tar. This package contains:

• lib/dll/mmedia/ipp_h264_decoder.so — (x86 targets only) the H.264 codec decoder for io-media.

---

Commercial H.264 codec and IPP library distribution licenses are available directly from Intel at www.intel.com/cd/software/products/asmo-na/eng/219967.htm#vac. See the QNX License Guide at www.qnx.com/download/feature.html?programid=16860 for a full explanation of the licensing of and available support for this component.

---

Known issues

At time of release, the issues listed below were identified and under investigation. Check the QNX web site (www.qnx.com) for the latest information.

• Linux and Windows hosts with co-existing Neutrino 6.3.2 and 6.4 baselines: the MME 1.1.0 Core installer does not fail and request an uninstallation if you install the MME 1.1.0 on 6.3.2 and 6.4, then attempt a second installation on 6.3.2. (Ref. 62512)

  Workaround: When installing on co-existing baselines, before installing the MME, check for and remove any instances of the MME previously installed on the Neutrino baseline where you are performing the current installation.

• Linux hosts: the uninstaller incorrectly removes the execution permissions of libaoi.so.1. (Ref. 60088)

  Workaround: After uninstallation, manually reset the permissions for libaoi.so.1 to rwxrwxr-x.

• The iPod nano 2G refuses to connect if the upstream port reports full speed. This problem has been reported for this iPod only; other iPods do not indicate this problem. (Ref. 60634)

  Workaround: Use a high speed port for the iPod connection.

• iPods: quick track changes between different sampling rates on iPod Touch with older firmware (1.x) using digital audio results in silence. (Ref. 60652)

  Workaround: the client application should enforce a brief pause when requesting track changes on these devices.

• Incorrect configuration of the MME can cause it to fall into a loop while pruning a mediastore during synchronization. (Ref. 47264)

  Workaround: Always configure the MME so that the maximum memory permitted for synchronization operations is less than the maximum RAM size configured for tmpfs.

• If a mediastore changes, then the user requests playback of a fid from the removed mediastore, the MME attempts to play the track on the new mediastore.(Ref. 42329)

  Workaround: After a mediastore state change event, check the mediastore IDs (msid) for the tracks in a track session, and recreate the track session if needed.

• Accessing a second USB device during digital playback from an iPod device may compromise the quality and consistency of the playback. (Ref. 60593)

  During testing of playback from iPod devices, connection of a second device that takes a long time to access or scan files has occasionally produced audible gaps in the playback, or reports of buffer underuns. The cause of this behavior may be the test environment configuration, but this hypothesis has not been confirmed.

• If the io-fs iPod module (iofs-ipod.so) fails to launch because of authentication issues, the subsequently launched io-audio instance may also fault. (Ref. 61563)

• Samsung S3 MTP devices do not work with the QNX PFS driver (io-usb); the problem is under investigation. (Ref. 60631)

• The MME fails to correctly parse album art for some MP3 files. The current parser behavior is to “preparse” ID3 tags and remove from it any frames that are larger than four kilobytes. This behavior means that any images larger than four kilobytes found inside these tags are discarded. The problem will be resolved by the MME's new album art “Load on Demand” feature. (Ref. 60496)

• When playing tracks from a PFS device, the MME gets metadata from the PFS device instead of parsing the media file itself to extract the metadata (which would be a much slower process). If a PFS device doesn't provide metadata values, the MME fills in the values with its defaults. Note, however, that a PFS device's failure to provide metadata may indicate that there is a problem with the track, the device, or the way that the track was put on the device. (Ref. 44770)

• The MME has been observed to incorrectly report an error (errno=5) when setting repeat or random modes repeatedly and in rapid succession on an iPod. (Ref. 49402)

• Choppiness has been observed in parsing of MPEG4 files. (Ref. 54514)

• At startup, the MME restores the language to the setting in the MME configuration, rather than keeping the last language value set before shutdown. (Ref. 46642)

• An unexpected stopped playstate has been observed on some mediastores during a fast rewind. (Ref. 53104)

• Trick play (fast forward, fast reverse) doesn't work for very large files (over 1.5 gigabytes) on PFS devices. (Ref. 42847)

• Possible heap corruption during playback of .mp3 files with xing_mpega_decoder. (Ref. 54261)

• Testing has been able to make the MME fail under the following specific conditions (Ref. 47399):
  • Playback MPEG4 tracks from a USB stick.
  • Initiate some other process to consume a large portion of the system memory.
  • Change tracks, then immediately remove the USB stick.

• TI Jacinto: upon completion of a fast-forward or fast-reverse command for WMA files via the TI Jacinto DSP (ADE), playback will resume from the beginning of the file rather than the position where the trick play command was cancelled. (Ref. 46438)

• TI Jacinto: playback of WMA files after a pause is executed may result in a short burst of noise. (Ref. 46437)

• The QDB client (qdbc) may incorrectly parse code in a database column as a comment. For example, in the statement SELECT folder FROM folders WHERE basepath glob '/Coldplay/*';, qdbc interprets /* as a C comment, and not as part of the column data. (Ref. 46691)

• x86 platforms: qdb faults when attempting to handle statements with a large number of SELECTs. The SQLite #define that caps the number of SELECTs allowed at 500 does not appear to be respected. (Ref. 57293)

• If the destination file runs out of space while writing to the end storage position, QDB fails to perform a restore; QDB logs no errors or warnings before falling back to an older version. (Ref. 52012)

Technical support

If you have any questions, comments, or problems with a QNX product, please contact Technical Support. For more information, see the How to Get Help chapter of the Welcome to QNX Momentics guide or visit our website, www.qnx.com.