Online Services team Ircam

1
Online Services team Ircam
2
Content of this presentation

• Presentation of the team
• Members and skills
• former realizations
• Foreseen role in Semantic HiFi
• Technical coordination and system architecture
  (WP1.2)
• Development of the online music metadata server
  (WP7)

3
The teammembers

• Jérôme Barthélémy, Pascal Mullon
• Head(s)
• Technical coordination and architecture
• (development)
• Guillaume Boutard
• Conception and development of the applicative
  layers
• web technologies and middleware
• Max Jacob
• database technologies
• audio data and metadata management

4
Former realizationsCuidado - the Online Sound
Palette

• Centralized database of audio samples (35 000) of
  different kinds (instruments, sound effects,
  etc.)
• Dynamic database users are identified, can add
  personal samples and describe them
• Online access to the audio (audio conversions,
  download, upload, streaming)
• Browse and search, automatic classification,
  based on complementary descriptions (keywords,
  text, numerical descriptors)
• Relies on a set of independent software
  components

5
Former realizationsAudio data database

• Extensible file storage solution
• Audio formats on-the-fly conversion
• On-the-fly, segment-based streaming and download

6
Former realizationsAudio metadata database

• Dedicated to audio samples description
• Structured, textual descriptions
• Numerical descriptions
• Mpeg7-based
• Support of segments ? evolution towards music
  material
• Linux/PostGreSQL

7
Former realizationsApplicative layer

• Built on top of preceding components (all
  components can be distributed on different
  hardware)
• Acts as a controller supervising exchanges
  between them
• Provides high-level services accessible online
• Java API (intranet)
• Over the web (Java serialized objects, servlets
  producing html pages)

8
Roles of the team in Semantic HiFiCritical points

• Integration of components developed by partners
  on the three targeted applications
• Interoperability
• Modularity (reusability of the developments)
• Independency of the different functional groups
  of data audio data, metadata, authoring data
• Independency towards DRM solutions

9
Roles of the team in Semantic HiFi

• WP1.2 Technical coordination and definition of
  the architecture (what runs on which component?)
• Data exchanges taking place between these
  components
• Definition of their APIs, and of data exchanges
  between them
• ? participation to the functional conception
  (technical feasibility)
• WP7 Online server of musical metadata
• Definition and modelling of data (musical
  metadata) and set up of related database
• Identification of the other data (authoring or
  playing lists parameters, etc.)
• All aspects dedicated to web communication with
  the other agents of the system

10
WP1.2Technical coordination architecture
USER Y - HiFi system
USER Y - Metadata authoring application
HiFi
PC
USER X - Metadata authoring application
USER X - HiFi system
How? (peer to peer? Local home connexion? Web?)
PC
HiFi
Centralized metadata server
Web servers
11
WP1.2Technical coordination architecture

• Three main directions to start with
• What?
• Identification of the main software components of
  the system scientific modules, databases,
  conversion modules, etc
• Identification of the main types of data (audio,
  metadata, authoring parameters/scripts)
• Specification of their technical requirements
  (disk, processing power, external libraries, )
• Where?
• How can these software components be distributed
  on the 3 hardware platforms, regarding
  compatibility between the technical
  characteristics of these 3 platforms and the
  requirements of the software components
• (especially what are the technical
  characteristics of the Hifi system, and what can
  be hosted on it?)
• How?
• Data and metadata formats (especially for data
  shared or exchanged between different components)
• What will be the interactions between these
  components (classical web client/server protocol,
  P2P, USB connexion between Hifi and PC)

12
WP1.2Technical coordination architecture

• Answers to these questions should provide
• bottom up functional elements (what we can hope
  to achieve scientifically and technically) to
  consider along with users feedbacks ? D1.2.1
• A first specification of technical
  characteristics of hardware and software
  elements, providing guarantee of compatibility
  between components interacting one with the other
• A basis for detailed conception (especially
  interfaces/APIs of software components)
• A basis for planning refinement

13
WP7Sharing system

• Is one of the components of this architecture ?
  will be specified by the D1.2.1
• Centralized databases of audio data, audio
  metadata and other sharable data (authoring
  parameters, etc.) accessible online
• Reusability of our former realizations