Moodmixer » Allgemein

NRK ordert neue Kanäle

admin — Thu, 03 Nov 2011 13:32:07 +0000

NRK ordert neue Kanäle. Der norwegische Rundfunk hat wieder einmal ein paar neue Lizenzen für die Playlistautomation seiner Internetradiokanäle gekauft

Partnerschaft mit accenta music GmbH

admin — Sun, 14 Aug 2011 13:33:48 +0000

Die Moodmixer Gmbh hat den Spezialisten für Gemafreie Musik accenta music gmnh als Partner gewonnen. “Für accenta music fungieren wir zukünftig als technischer Dienstleister im Bereich Streaming und instore-Radio

slidertest

admin — Tue, 22 Jun 2010 14:30:23 +0000

Thank you

admin — Tue, 11 Aug 2009 06:34:09 +0000

Thank you for sending us your message

Moodmixer 80’s New Wave and Love Radio

admin — Fri, 27 Mar 2009 10:00:39 +0000

If your nicest teenage time was in the 80#s and you love 80’s music and new wave- then here’s your radio to listen to:

If you want to add this radio to your website you need this bit of code:

Have fun

Yin-Yang Riddle

admin — Thu, 26 Mar 2009 15:44:46 +0000

If you really haven’t got anything else to do then try and solve this little riddle: Simply play around with the buttons and see what you can learn about this. By the way: consecutive clicking onto the “Start” button slows down the rotation tempo.

tell us

Checklist background music

admin — Mon, 16 Mar 2009 13:01:39 +0000

Your company checklist : In which areas is there a need for action? Where is your current situation satisfactory, what have you always wanted to change?

Please contact us if you need support in finding the perfect music system

or call us right away

CLICK HERE TO PRINT THE PAGE !

	OK?	NEED OF ACTION ?
1.We don’t use CD-players anymore because CDs can only be looped and scratch easiliy
2. We don’t play radio because we don’t want to bother our guests with disturbing interruptions for news and weatherforecasts
3. Our music concept has been individually set up for our needs, customer- and target group structure and matches our brand
4. We play the music at a constant volume
5. Our music system doesn’t produce listening gaps when played at low volume
6) If ncessary, we have planned conmmercial interruptions very thoroughly
7) The selected music is liked by our customers
We try not to play extravagant music ( other than in lifestyle bars or cafés)
9) alternatively: for our mainly young customers we play the hottest stuff in town
10) We play different musicin different areas, matching the product range which is displayed
11) We play faster music to get our customers movingt (Example: Fast food chain)
12)We play classical or slower/smooth music because this makes our guests slow down, stay longer and thus consume more
13) Our background music is controlled centrally, no more hands on for our employees
14) Our employees cannot play whatever they like
15) Our employees can play guest request (bars)
16) Neither does our music make customers and employees nervous nor bores them or makes them fall asleep
17) We don’t play loops but a constantly changing music playlist
18) tracks, that our customers like, can be played on a higher frequency
19) tracks will not be repeated too often
20)In elevators, and on floors we play more background music
21) If we have installed digital signage(video) systems, our background music is synchronized accordingly
22) Loudspeakers are postioned properly, not directly above our guests heads
23) The Loudspeaker system provides the same volume/sound of the music throughout the room

CLICK HERE TO PRINT THE PAGE !

Studies about background music

admin — Mon, 16 Mar 2009 12:52:54 +0000

Will music increase your revenue ? What can music do for my business?

Before you dig into the subject of background music or foreground music for your business, the first question will be the one of cost-benefit ratio: Will music increase the revenue of my business?

Music is used in many businesses either in the background ( Muzak, elevator music, piped music) or in the foreground (like in modern fashion stores).

Music is supposed to make your customer and guests feel comfortable, possibly stay longer and consume more. Music wants to help you build up customer relations and create an athmosphere which complements the style, interior and brand of your business environments.

There are many providers of so called business audio, instore radio, background music suggesting that music is utterly important to the success of your company.

Here is a collection of links to articles and studies about the use of background music and their effects on consumer behaviour, which you might find interesting:

PLAY THAT ONE AGAIN: THE EFFECT OF MUSIC TEMPO ON CONSUMER BEHAVIOUR IN A RESTAURANT
The Effect of Music on Perceived Atmosphere and Purchase Intentions in a Restaurant
Background music at work;Work & Well-Being
The Arbitron Retail Media Study: Impact of audio broadcasting in retail
In many scientific research articles you will find pro’s and con’s to background or foreground music – still there have been no final results found that music in a commercial environment increases revenue. But it seems, that it has many positive effects if applied sensitively and can have many negative effects if applied without enough knowledge.

In some cases NO music is better than bad or wrongly assembled or looped music. So it might be interesting for you to go through our little online checklist on background music for your business:

if you would like us to develop a perfect concept for your background music or instore radio, in terms of appropriate music down to technical means, then contact us or call us right away:

Your sixth sense in future

admin — Thu, 12 Mar 2009 13:04:23 +0000

Exciting how today’s technology can support us in future:

Full article at http://www.ted.com/talks/view/id/481

Moodmixer SDK for developers

admin — Mon, 09 Feb 2009 13:14:48 +0000

This document will describe the functionality and purpose of the UniversalMixMachine web service, provided by Moodmixer GmbH.

The UniversalMixMachine web service provides users with an online tool that delivers a calculated and in length defined list based on almost arbitrary data and a history of previously delivered items. Typical use cases are musical play lists, dynamic product presentations or recommendations for web visitors. Since the UniversalMixMachine calculates the returned list by a complete analysis of base data and logs the result will always be different from previous lists and absolutely up to date at the same time. The process can be fully automated, what makes it possible to deliver user related content dynamically without any further interaction.

The selection of items is conducted on the basis of threee possible algorithms. These can be combined and put into a weighed order. Each algorithm can be used for different metadata.

Ranking: The principle of all Moodmixer™-Systems is a rating system. The higher a track is being rated, the “relatively“( in relation to the title pool used) more often it will be used in a playlist.

Ranking columns can also be used for temporary archiving of tracks (value 0 equals “not in use” if activated). Ranking can be used on any kind of data that can be converted into a ranking, such as product age, price, editorial oder user-rating, click rates, sales charts, results from filters or semantic analysis, resuilts from collaborative filtering and many more.

Group distribution (optional): The group algorithm will take care of a homogeneous distribution of values that occur more often in a data library- i.e. if you have an artist in the library that owns many more songs than others you might want to distribute all of his titles evenly across the playlist- without a bulk of songs at one point- then you set “Group” to the Artist column. This is also a good way to control the distribution of i.e. voice type or of product groups and their homogenious distribution. Group algorithms are “non-destructive”- if a title pool doesn’t allow for this distribution it will carefully soften the rule.

Smoothing (optional): This control can be set for values such as BPM, Tempo/ felt tempo, Rhythm-description etc. it aims to prevent too large differences in value change from one item to the next. If the title pool allows it then changes will be made in waves, slowly increasing and decreasing. This control is also non-destructive.

Overview:

UniversalMixMachine web service has one core function called UMMRun

The used parameters:

You need at least a PrimaryID for each planned item.

With this PrimaryID the user should be able to get additional information from his own database if necessary. The second entry will contain the calculated start time of the item, it will only be present if ScheduledStartTime is valid. The third entry will contain the URL of the calculated item if the column type is present. The length of the returned array depends of either the value in ItemsReturn or the amount of items used to fill the time given by ScheduleStartTime and ScheduleEndTime.

In any case the last two entries of the returned array will contain first the parameters passed to the function except MixData and LogData for control purposes and second a string that will be “No Errors!”, if everything worked fine. So, if an error occurred and the function was able to return the object array, it will be just two entries long. One can say for a rule that, if the returned array length is lower or equal two, something went wrong.

The parameters:

All UMMRun function parameters are of type string to avoid any type mismatch. But there are some crucial aspects that should have special attention:

All four parameters ColTypes, ActiveColumns, ColumnRestrictions and ColRanks must exactly reflect the amount of columns in . I.e. if has 4 columns ColTypes must also contain 4 numbers separated by a ‘;’: “0;2;9;11″

MixData , LogData must be separated by the same ColumnSeparator and RowSeparator and these separators should be safe, means, neither MixData nor LogData entries should contain them.

Key	Status: mandatoryType: String Purpose: authenticates the web service call You can purchase a valid key from Moodmixer GmbH. The web service will only work with a valid key!
ColumnSeparator	Status: mandatoryType: String Purpose: Mix-Data You can use any printable character but it’s not recommended, because there is the risk, that MixData already contains those characters. Better use TAB or RETURN instead. ColumnSeparator must be different from RowSeparator!
RowSeparator	Status: mandatoryType: StringPurpose: the character or string to separate each row of Mix-Data You can use any printable character but it’s not recommended, because there is always the risk, that MixData already contains those characters. Better use TAB or RETURN instead. RowSeparator must be different from ColumnSeparator!
MixData	Status: mandatoryType: StringPurpose: the planning data as plain text, fields are seperated by ColumnSeparator, rows by RowSeparator
ColTypes	Status: mandatoryType: String consisting of integer numbers separated by a semicolon (;) Purpose: Defines the function of each column/field in MixData to be interpreted by the UniversalMixMachine There are currently 10 different types of columns. The PrimaryID column must always be present, it will be returned by the UniversalMixMachine to identify the data item. One of the three column types Ranking, Group or Smoothing must also be present and active. All other column types are optional but DurationInSeconds should be present, if exact timing is important, otherwise the <%UMM%> will assume a default duration value. PrimaryID=0 (mandatory) Ranking=1 (values in this column will be interpreted as preferences: higher values means relatively more ‘plays’) Group=2 (values in this column will be grouped if identical and distributed according to their amount) Smoothing=4 (values in this column will be interpreted as ’steps’ to avoid great ‘jumps’ from item to item) LinkedItem=6 CueIn=7 (values in this column will be interpreted as play mark relative to start of song in seconds and will be subtracted from DurationInSeconds) CueOut=8 (values in this column will be interpreted as end play mark relative to end of song in seconds and will be subtracted from DurationInSeconds) DurationInSeconds=9 (values in this column will be interpreted as total duration of item in seconds including existing cues) URL=10 (values in this column will be interpreted as path to physical media) Jingle=11 (values in this column will be interpreted as indicator that the item is a jingle and rotation restrictions will not be applied, values are 0=no jingle or <>0=jingle) Example: 0;1;9 says that there are three columns in MixData. First is of type PrimaryID, second of type Ranking and third of type DurationInSeconds
ItemsReturn	Status: optional Type: String Purpose: Sets the length of play list to return if this value is NULL or 0 and ScheduleStartTime and ScheduleEndTime are not valid the UniversalMixMachine will return an empty playlist. This value should not be bigger than 1000, especially when MixData are large, because the risk of timeout increases.
ActiveColumns	Status: mandatory Type: String consisting of ‘0′ or ‘1′ separated by a semicolon (;) Purpose: Defines the activity status of each column/field in MixData to be interpreted by the UniversalMixMachine Active columns must be of type Ranking, Group or Smoothing. There must be at least one active column, otherwise the UniversalMixMachine will return an empty play list. PrimaryID columns are automatically active and so must not be set. Example: 0;1;0 (column types: 0;1;9) says that there are three columns in MixData. Only the second column is active (and of type Ranking).
ColumnRestrictions	Status: mandatory Type: String consisting of ‘0′ or ‘1′ separated by a semicolon (;) Purpose: Defines the restriction status of each column/field in MixData to be interpreted by the UniversalMixMachine If a column has restriction enabled, the UniversalMixMachine will try to avoid an immediate repetition of an item with the identical value in the column field. 1;0;0 (column types says that there are three columns in MixData. Only the first column is restricted (and of type PrimaryID).
SmoothingValues	Status: obsolet Should be NULL or empty string.
ColRanks	Status: mandatory Type: String consisting of integer numbers separated by a semicolon (;) Purpose: Defines the priority of columns in MixData to be calculated by the UniversalMixMachine Lower values mean higher priority, negative values are not valid. Will only be evaluated for active columns except PrimaryID Example: 20;10;50 (column types: 0;1;9, active: 0;1;0) says that there are three columns in MixDataRanking), so only the value 10 will be evaluated.
LogData	Status: optionalPurpose: play history data as plain text consisting of two values for each row, PrimaryID and play date, fields are seperated by ColumnSeparator, rows by RowSeparator Sequence of the two values doesn’t matter but must be the same throughout the whole list. One must be a valid date the other one must NOT be a date. The UniversalMixMachine will calculate the play list based on log data if present. Otherwise it will give every item of MixData a virtual random play date. Example: ID1234 20081205T223417 ID0765 20081205T223705 ID8888 20081205T224123 IDxyz 20081205T224500 the date field can have any valid date format i.e. 11/30/08 7:14
LogScope	Status: obsolet Should be NULL or empty string.
LogStart	Status: obsolet Should be NULL or empty string.
PriorDay	Status: optionalType: String ‘0′ or ‘1′ Purpose: if set to any value different from ‘0′ the UniversalMixMachine will try to avoid planning of songs that has been played the day before inside the PriorDayScope
PriorDayScope	Status: optionalType: Integer number as string Purpose: if set to any value different from ‘0′ and the flag is set the UniversalMixMachine will try to avoid planning of songs that has been played the day before inside a scope of given minutes x2. Example: If the current planning time is 6:15 p.m. and the given PriorDayScope is 15 minutes, the UniversalMixMachine will not play songs that have been played the day before between 6:00 p.m. and 6:30 p.m. As long as there are no playable UniversalMixMachine will automatically narrow the scope until playable songs are found.
PWRA	Status: optionalType: String of value ‘0′ or ‘1′ Purpose: if set to any value different from ‘0′ the UniversalMixMachine MixData.
ScheduleStartTime	Status: optionalType: Date value as String Purpose: if set to any value different from NULL or empty string and ScheduleEndTime is a valid date value later than ScheduleStartTime the UniversalMixMachine will plan items either by DurationInSeconds or a fixed default value of 3 Minutes until the ScheduleEndTime is reached.
ScheduleEndTime	Status: optionalType: Date value as String Purpose: if set to any value different from NULL or empty string and ScheduleStartTime is a valid date value earlier than ScheduleEndTime the UniversalMixMachine will plan items either by DurationInSeconds or a fixed default value of 3 Minutes until the ScheduleEndTime is reached.