MusicCenter V9 manual

trivum can play web radio streams provided via the TuneIn catalog of web radio stations.

these are music files stored on a NAS (Network Attached Storage) in format .mp3, .flac and .m4a.

trivum can play music provided by streaming services like, for example, Deezer, Qobuz and TIDAL.

A music stream can be received and played in the local network via AirPlay from Apple devices.

Every zone supports two Alarms, on selectable week days.
An alarm may play a NAS playlist, web radio, FM radio or analogue input.
Alarms are configured directly in a visualization like the Web Visu or a Touchpad.

Alarm display

Alarm behaviour

1) if the zone is off, alarm will switch it on, play alarm content, then switch off.

2) if the zone is playing, the alarm may or may not play content, depending on current volume and pause status. but it is considered inactive, and it will not switch off the zone later.
This can be disabled by the global option:
System / Setup / Advanced / Force alarm (play and off) in active playing zones

3) if alarm is playing, but the user switches the zone off then on, or the user selects a different music content, the alarm is deactivated, and will not switch off the zone later. This behaviour cannot be deactivated, as such user interaction means the user has taken over control manually. If the "Force alarm" option mentioned above is used, it will kick in again on the next day, as soon as the alarm start time is reached again.

Whenever alarm behaves unexpected you may look for details under:
Support / Logs&Warnings / Show event log
Support / Logs&Warnings / Show warnings

Alarm extensions

If you strictly need an automated Zone Off every day, do not just rely on Alarm, as it can be deactivated by user interaction. Also configure a Night Quiet Time event as described below.

Every zone allows configuration of two special time ranges,

During these times music can be turned off, or the volume can be limited. AQT/NQT are set in the web configuration only.

For example, to force a Zone Off at 23:00, set NQT Starttime and Stoptime to 23:00, with action "turn off once".

With the SC344V2, the line-out outputs 1 to 4 have a trigger port. With this, external amplifiers, like our RA410 or P319, can be automatically turned on by selecting a source.

Trigger output technical details:

Here is an example how to connect output 1 triggering to an RA amplifier, in stereo mode.
Note that On A and On B on amplifier side are short-circuited, to tell the amplifier
it should run in stereo mode. This way only 2 control wires are needed from the SC to the amp.

With the SC044, the line-out outputs 1 to 4 have a trigger port. With this, external amplifiers, like our RA410 or P319, can be automatically turned on by selecting a source.

Trigger output technical details:

With an adapter cable RJ45 to Cinch + Trigger (Part No. 500034) a P319 amplifier can be connected to a SC044. In addition to the audio lines, the trigger connection (jack socket) must be connected to the trigger output of the SC044, either directly by removing the jack socket or with a cable with a jack plug. The tip of the jack plug is the switching input, the shield the ground.

The SC044 has two digital I/O ports, so it can be operated with simple buttons. For example, you can respond to the ringing at the front door by pausing the music playback. Or activate the paging feature to make an announcement.

Trigger input technical details:

For configuration see setupPlayer

This is described in the Quick Installation Guide, supplied with the amplifier. The connection scheme is also available here:

https://www.trivum-shop.de/support/docs/RP-RA410-connection.png

Important: after any jumper changes, restart the amplifier by disconnecting it from power,
otherwise it will not detect the changed configuration!

When done, also go into the web configuration of the RP actuator, into

and activate

(do not check "use control out" as this wire is not needed in this setup)

If the amp detects an active output (zone switched on with music playing) the green led at the amp will blink.

If it is passive the green led shows a permanent light.

This input allows to send external analogue sound into the RP341, by shielded Cat5 cable, using the original trivum Analog Input Adapter which is available here:

https://www.trivum.de/products/soundsystems/accessories/44/analog-input-adapter?c=422

Warning: please do not use Cat5 Adapters by any other manufacturer. The pins are not standartized, so they will not be compatible, and may even cause damage to external connected devices, due to 24V voltage on some pins supplied by the trivum SYM IN connector.

By default the RP311 is a single zone device, with the line output linked to the the speakers. The same sound is playing by loudspeakers and the line output.

This can be changed in the web configuration under:

If you select one of the "Independent lineout" options, you will get a second zone, whose audio is played by line out only.

Download the trivum trace tool, named trace.exe

Then open a Shell or Command Line Window (e.g. Windows: select Run then type CMD.exe) and go into the folder of the downloaded tools.

Use

→ Now you should see something like:

You may press: - i for information - t to toggle event tracing outputs

The WebConfig has a navigation bar at the top of the page.

In case of problems, trivum is able to support you using remote access technology. You can enable/disable this in the <basic setup>.

Please enter your contact information here to make support easier. trivum will then have the name and email to send you personalized messages.

trivum multiroom devices support static and dynamic IPv4 IP addresses (over DHCP router). For smooth interaction between all trivum devices in your network, we recommend the use of DHCP.

(3) Under Attention you will find some information about the network settings you have made.

(4) If you have made any changes to the network settings, you must reboot the system to enable the changes.

(5) If the network settings are correct, you can use Show trivum components found in network to list all trivum devices in your network.

This screen allows you to update your trivum multiroom devices, including all connected devices.

If a software update is available for a device, an Update available appears next to the device name.

Click on one of the devices to have more information and choices regarding a software update.

This screen displays information about the installed and the latest available software version (3) and allows you to trigger software updates.

Repeat this for all slave devices, then go back to the master’s web configuration, into: Hardware / Players.

The screen to configure the zones looks like this.

1 - QuickControl shows a special screen to quickly test basic playback in all zones.

2 - These are the zones of the master, or single, device.

3 - If additional slave devices were integrated, then their zones appear in such separate sections.

The screen to configure a zone looks like this.

(1) Click here to adjust basic settings of the zone such as name, default sources, volume handling etc.
See also Zone basic settings.

(2) Click here to adjust the basic sound settings (treble, bass, balance), the advanced sound settings (low/high pass, bass level, fixed volume) and the equalizer parameters of the different outputs.
See also Zone sound settings.

(3) Click here to define zone related actions for this zone. Zone related actions are shown in the TouchPads and WebVisus action area.

(4) Click here to adjust the paging settings for this zone.
See also Zone paging handling.

(5) Click here to adjust the KNX bindings to this zone.
See also setupKNXZones for more information.

(6) Click here to define up to eight sources for the "used next source" KNX command.

A ZonePlayer is a device with one or more outputs. One or more ZonePlayers are combined to a trivum multiroom system.

By selecting: Hardware / Players / SNR …​ you can configure a single ZonePlayer.

(1) A list of all zones that this player can play. Click on a ZoneOutput to go to the zone’s configuration screen setupZone

(2) With SC models the audio outputs can be freely configured (mapped) and used in pairs as stereo outputs as well as individually as mono outputs, for example for subwoofer or satellite speakers. Click here to map the outputs to the zones. Zone Mapping

(3) A list of all analog Line-In inputs. Click here to adjust basic settings of Line-In input such as name, icon, level-adjustment and auto sensing options.
See also Line-In setup.

(4+5) SC044 only: click here to define which KNX action should be executed when a digital HIGH respectively LOW signal has been detected at one of the digital IO ports.
See also Trigger input settings

Zone groups are predefined groupings of zones. With as simple KNX command you can enable or disable or even dissolve these groups.

Zones can be also grouped via the trivum TouchPads as well (see ???). However, with this type of grouping, there is no possibility to control the grouping by KNX.

The screen to manage the zone groups looks like this.

(1) All predefined zone groups can be activated simultaneously via a KNX command. Enter the KNX group address for this purpose.

(2) If this is checked, only the predefined zone groups can be selected on the Zone selection screen on TouchPads and WebVisus.If this is not checked, zones can be grouped/ungrouped at any time on the TouchPads/WebVisus.

(3) Click here to adjust the settings of a predefined zone group such as name, type, KNX group addresses to start/stop the group, included zones.
See also Zone group settings

(4) Click here to delete the predefined zone group.

(5) Click here to add a new predefined zone group.

The screen to manage the control units looks like this.

(1) Click here to add a new control unit.

(2) Whenever you connect to the trivum system with a Web Visu, e.g. by iPhone or a tablet, a new Control Unit is created dynamically. As long as you do not configure special actions for this unit it is considered "not configured". If your list fills with many unconfigured control units over time you may clean them up with this function.

(3) Click here to adjust the settings of a control unit such as name, assigned zone, assigned trivum actions and other specific settings.
See also setupControlUnit

The screen to configure a control unit looks like this.

1 - The zone that the control unit currently uses. This may be changed anytime by the zone selection menu within this unit.

2 - Commands that can be assigned for this control unit only. They will appear at the right side of the visualization.

3 - Normally, clicking on the power button at the right bottom in a control unit will activate mute, and a long press will switch the zone off. If this setting is active any (short) press on the power button will switch the zone off. This can be relevant for touch panel PC’s that do not support a long press.

The screen to configure TuneIn looks like this.

1 - this should be filled in only if "Local Radio" within the TuneIn Menu lists radio stations that belong to a wrong region. In this case, find out the latitude, longitude of your city, by googling: "Cityname latitude". Then enter them here. For example, for Zurich type here: 47.3,8.5

2 - if you use the TuneIn menu often and in every zone you may check this option. It will show an action "TuneIn" at the right side of every visualization.

3 - as soon as you marked TuneIn stations as favourites they will be listed here.

Longitude and latitude of some well-known cities Ort Breitengrad Längengrad Paris 48.8 2.3 Berlin 52.5 13.4 Barcelona 41.4 2.2 Chicago 41.9 -87.6 Tokyo 35.7 139.7 Istanbul 41.0 29.0 Rom 41.9 12.5 Sydney -33.9 151.2 New York 40.7 -74.0

The screen to configure AirPlay looks like this:

1 - enable or disable AirPlay in general.

2 - optional password to protect AirPlay inputs.

3 - check this to avoid instant massive volume changes, e.g. because your iPhone currently uses a volume 90 which is sent by AirPlay to trivum.

4 - by default, trivum AirPlay inputs look like "trivum #.100 name" with 100 being the last part of the trivum IP address. To show only zone names uncheck this option.

5 - if AirPlay stops sending audio, how long should trivum wait before a zone is switched off? Default is 30 seconds.

6 - in fully a transparent network, with no multicast filtering, this option is not required and should be "Do not send zone names repeatedly". Some networks, however, do not pass trough AirPlay name queries sent by an iPhone, with the result that trivum AirPlay input names are not visible at the iPhone. For this case select an active repeat of AirPlay names here, normally between 1 and 3 minutes. This option cannot be used with RP340, RP341, Actuator4 or any device that has just one streamer but multiple AirPlay inputs.

The trivum InStreamer adds another audio source to your trivum multiroom system. An external audio source, like a CD- or record player, can be connected via analog RCA or digital TOSLINK cable to the InStreamer. On the other hand, the InStreamer is connected via Cat-5 Ethernet cable to your LAN and will be automatically detected and integrated into your trivum system.

The screen to configure InStreamers looks like this.

The screen to configure an InStreamer looks like this.

1 - check this to make the instreamer available as an action in all zones, in the right side of every visualization.

2 - while an InStreamer is used to play music, select it’s icon here.

3 - if the sound is very silent select values above 100 (percent). If the sound is distorted select values below 100 percent.

4 - should not be checked as long as you use the InStreamer only in a single zone, or as a source for a group containing several zones. If, however, you want to play the InStreamer audio in different, ungrouped zones in parallel, especially with separate trivum devices, you have to enable multicast. Multicast however requires a proper configuration of your network switches, otherwise your network may fail. Read all details in article: https://www.trivum-shop.de/support/docs/en/trivum-troubleshooting.html#groupplay

The screen to add a new StreamingService looks like this.

NAS stands for Network-attached storage. Network-attached storages are special data storage, which can be connected directly to a network. Making your music library files accessible from all devices within the network, including trivum multiroom devices.

1 - click here to start another rescan of the NAS contents, if a NAS path was configured already.

2 - here you can configure a network path to access your music on a NAS.

3 - enable this to have an automatic NAS rescan done once per day.

4 - if you have mainly music from sampler albums, with many different artists, then trivum tries to detect such albums automatically, so you can still play them although artists are different. This however requires that the COMPILATION tag is set in all such music files. Read more below about this.
If tagging is not possible you may try the "Reduce compilation artists" option to replace all artist names by a text "Compilation". After changing the option a rescan is required.

5 - by default, trivum searches the NAS for .m3u files and includes these playlists in search results. You may not want to do so if all your playlists already taken automatically from an iTunes database file, as configured under (6).

6 - if you use iTunes and have your NAS folders well configured, as described under https://www.trivum-shop.de/support/docs/en/trivum-connect.html#nasitunes
then trivum will use playlists from this database automatically if this option is set.

7 - this is normally not used. Only if some very special web radio stations fail to play, because they expect a special user agent string, then this can be configured.

Start your favorite music thanks to trivum favorites in just three clicks. No more searching, no scrolling through long lists. And the best: adding a track to your trivum favorites is even faster. Any kind of music sources can be added to the trivum favorites - streams, fm stations and even audio inputs.

trivum multiroom devices with one or more built-in FM tuner have of course a classic station memory. With this, you can save up to 30 of your favorite radio stations, and select them easily by one touch.

The screen to configure the FM stations looks like this.

1 - the list of stations.

2 - buttons to delete stations.

3 - here you may add a station manually by entering it’s frequency.

Some trivum multiroom devices feature a built-in DSP for extensive sound optimizations. Thus, you can adjust the audio playback individually to your spatial conditions or to the music genre. Some DSP presets are already defined ex works.

The screen to change a DSP preset looks like this:

1 - individual EQ bands with frequency, Q factor and amount.

RTI is the link between your technical devices and provides you with a unified and comprehensive user interface. This surface is on hand-held remote controls, touch panels, tablets, smart phones and computers. trivum multiroom devices can be controlled from RTI systems and trivum can use RTI systems to control devices.

The screen to setup the RTI support looks like this:

1 - enable RTI support and show RTI specific settings.

2 - by default trivum decides automatically which configuration requires sending of RTI events. Check this to always send RTI events.

3 - if an RTI processor tries to access trivum, it is listed here automatically.

4 - the list of RTI command strings that map to trivum actions.

5 - here you can map self-defined command strings sent by and RTI to trivum actions. Whenever you click "add" another mapping is created under (6).

6 - overview of zones with their numeric ID’s, for identification within an RTI driver.

The paging function reduces the volume of the current music playback for a defined duration to play back the music, speech or sound from another audio source. The paging will be started and stopped via a KNX telegram to a defined group address. The volume of the paging event can be controlled via Knox too. With the paging function of the trivum Multiroom Systems and appropriate third-party hardware, you can make announcements, e.g. for offices, conference rooms and so on.

The screen to define the paging looks like this:

1 - click to create a new entry in the list (2)

2 - the currently defined pagings.

See also:

The screen to change a paging definition looks like this:

1 - to trigger the paging by KNX enter a group address here.

2 - remove the paging entry.

3 - run a quick test of the paging. As soon as started a stop button will appear.

4 - check this to have the paging enabled or disabled.

5 - how long should a paging play, in seconds, before it is stopped automatically.

6 - the playback volume which is used by zones, by default. it is also possible to change this individually per zone, under: Configuration / Zones / zone name / define zone paging handling.

Read more under: How to configure a ringtone paging

trivum supports KNX as an active KNX member for many years. We continuously work on the optimization of the KNX function, to make it better, more flexible and even easier for the installer.

All trivum devices support KNX ex works, that means KNX is "built-in". Prerequisite for an trivum KNX operation is a KNX/IP router, or interface (a router is recommended for an unlimited number of connections). trivum devices communicate via KNX/IP using this IP router.

trivum multiroom systems can be fully integrated into a KNX environment. So you can control third party devices via the trivum TouchPads for example. Or leave the multiroom system react on outside commands.

An KNX/IP router enables the communication between the KNX environment and the trivum multiroom system. See also KNX for more information.

To connect trivum devices useful with the KNX installation, the trivum devices must be parameterized.

Select KNX / Settings for the global KNX setup:

1 - enable receive and processing of KNX events from network, as well as sending of KNX status to the network, if configured.

2 - the multicast address where to listen or send to knx events. This is not the actual router device IP address (like 192.168.1.x) but always a multicast address starting with 224.

3 - if multiple KNX IP routers are detected in the network they can be listed here.

4 - link to the KNX trace where incoming messages with their time are listed.

5 - here you may upload lists of group addresses exported by ETS.

6 - here you may download the list of already used group addresses.

7 - an alternative tracing page to check live if defined group addresses receive something

8 - interactive view of all defined addresses, allowing to jump to the configuration pages where they are used.

9 - the physical device address that the trivum device should use on the KNX bus. It’s just important that no other KNX device uses this address.

10 - if you want to store the current trivum device state in a KNX scene, configure here the GA to program or recall the scene. read more details under "knx scenes" further below in the manual.

11 - for each zone a GA can be configured to control volume by 4-bit KNX messages. here you can configure the speed at which the volume changes. default is 2.

12 - to get a detailed log of incoming knx messages you have to enable this first. then go into: Information / Support / Logs&Warnings / Show KNX log

13 - select if the trivum device shall query configured group addresses for their status on startup

14 - normally, whenever knx data changes a message is sent immediately. but trivum may also re-send the current value inbetween, without any change, for example in case that a KNX display was taken off power temporarily. you may here configure an interval for such unrequested refreshs.

15 - NAS playlists with a special name starting like "P1 mylist" can be played directly, by configuring:
Configuration / Zones / zone name / KNX bindings / Play a NAS Index Playlist.
With "Show playlist entries" you get a list of all playlists, and the ones eligible for direct play being marked in green.

trivum KNX events link the KNX commands, send from KNX devices, with the trivum actions of your trivum multiroom system. They defines exactly in which zone a trivum action shall be executed, as soon as a KNX datagramm with the correct value is sent to a defined group address.

KNX events are actions bound to a group address.

1 - here you can create such a new event, or action.

2 - list of existing events

3 - click into the trash bin to delete an event. if you click anywhere else in the row you can edit the event.

You can have up to 700 KNX event objects.

The screen to change a KNX event definition looks like this:

KNX displays are hardware units displaying 1 to 4 lines of text.

The trivum MusicServer may not just receive KNX messages, but may also send a few simple commands to control KNX devices. these commands can be configured as actions in control units.

1 - switches may send a 1-bit message: toggle, or on, or off.

2 - dimmers may send

3 - shutters may send 1-bit messages: down, up, step down, step up.

The screen to edit a KNX actuator looks like this:

1 - given name

2 - on/off GA

3 - optional GA to read current status. relevant only if toggle actions are used.

the dimmer is a binary actuator extended by two fields to set or read brightness as a 1-byte value.

So far only the short and long action fields can be used in actions configured at control units.

Here many basic KNX settings can be configured per zone.

1 - enter a KNX group address (GA) here to switch the zone on or off by a 1-bit message with value 1 or 0. switching on means to play the most recent selected source again.

2 - GA to toggle mute of the zone or, if the zone is part of a group, of the whole group.

3 - GA to toggle mute only of this zone, no matter if grouped or not.

4 - control zone or group volume by a 4-bit KNX message. for example, receiving value 1 starts dimm down, which runs until volume 0 is reached, or value 0 is received.

5 - control zone or group volume by a 1-byte KNX message. KNX values 0 to 255 are converted internally to trivum volume values from 0 to 100.

6 and 7 - control zone volume only, no matter if grouped or not.

8 - step volume up or down by 1-bit messages.

1 - the KNX sources are a set of actions to start a specific source, and/or to select a content within a source. by configuring a GA here the user may toggle between these actions by a 1-bit message.

2 - start FM tuner by a 1-bit message

3 - start streamer. this will play the most recent selected content within that streamer, if any.

4 to 7 - select line inputs.

8 - if you have defined FM tuner presets, start them here with value 0 selecting the first preset.

9 - if you have NAS playlists with a name starting like "P1 mylist" or "P2 mylist" then a KNX 1-byte message value 0 will play "P1 mylist".

10 - if trivum favorites are defined play them directly here.

1 and 2 - to run a skip next or previous action by a 1-bit KNX message. e.g. while playing an album this will skip to the next track.

3 - send the zone status to the KNX bus: 0=off 1=on (including mute)

4 and 5 - tell to the KNX bus if the group or zone is muted

6 - send current zone volume as a KNX 1-byte message, with range 0 to 255

7 - use this to configure in detail what to send when the zone is switched on. may send a value "1" or "0".

8 - use this to configure in detail what to send when the zone is switched off. may send a value "1" or "0".

1 - tell if an alarm is configured as active

2 - tell if an alarm is currently playing

3 - send 1-bit value "1" if alarm starts playing

4 to 6 - same for the 2nd alarm of this zone

7 - GA to tell this zone if it’s part in a current scene. used in combination with: Automation / KNX / Setup KNX communication / Group address for scene save/restore. read details under: KNX scenes

8 - directly run a command in this zone through a 2-byte KNX value.
for the possible values see the list of zone commands in the trivum API documentation.

here is an excerpt of codes:

for example,

If pagings are defined then they can also be controlled by KNX. to do so select KNX / Paging to get this screen:

1 - select one of the paging entries to edit.

The screen to change the KNX paging definition looks like this:

1 - the paging can be started by a KNX 1-bit message to this GA.

2 - instead of using the predefined paging volume, a different volume can be set by KNX through this GA.

3 - while a paging is playing it’s volume can be modified by this GA. for example, sending a 1-bit message "0" will decrease the volume. the minimum volume for active paging is 5.

4 - normally, sending "1" to (1) starts the paging, but this behaviour can be changed here.

The trivum MusicSystems and the trivum TouchPads have KNX builtin. This means, that they can be controlled from other KNX devices or/and that they can control other KNX devices.

All you have to do is to

The trivum devices talk KNX/IP. This means, that a KNX IP Router or interface is neccessary to establish a communication with the KNX bus.

trivum devices are configured via web browsers, because they have a builtin web server. This means, that there is no need to use the ETS software.

But you should nevertheless take care of the following points:

See zoneKNX for all available datapoints per zone.

The trivum KNX event objects are a very flexible instrument. They can be used to trigger functions with KNX telegrams.

See editKNXEvent about event configuration.

The trivum MusicCenter software can even control some KNX actuators:

If you define e.g. a KNX shutter, then you can control this shutter in e.g. Macros (only C4 systems).
You can also map e.g. the long action of this KNX shutter to an action (button) on a TouchPad or a webTouch visualization.
You may also switch off a light when a zone starts.

See editKNXActuator for details.

See setupKNXDisplays about how to integrate KNX displays with trivum.

To run a paging controlled by KNX,

trivum KNX Datapoints have one of five sizes:

the same size can be used for many different purposes.
if you have to specify DPT types in your external KNX application select one of these:

In this example, a 6-fold KNX control element should control our trivum multiroom system. The controller should be able to operate some basic functions, such as

If you have a wall button that can only send 1 or 0 on the same group address it is still possible to achieve these two functions.

Then, if your wall button sends 7/1/0 1-bit value 1, it will toggle through web radio stations.
If it sends 7/1/0 1-bit value 0, it will switch the zone off.

Please make sure that you set the correct unicast and multicast IP addresses. Please refer to KNX/IP router settings.

These are limited to only a few parallel connections. Make sure that no other (or too many) devices are using the interface at the same time.

Please make sure that you set the correct filter and routing parameters. Please refer to Filter settings.

This is an iPhone App which is very helpful to check if your IP router works.

The communication is based on multicast communication. This has to be allowed by the switches - and routers/gateways which maybe are part of your network.
Please check the following areas:

If you have two or more network switches between the KNX IP router and the trivum device, then this may already cause a communication failure, that trivum does not get any KNX message.

Reduce the system. Connect both KNX IP router and the trivum device to the same network switch. Ideally use a simple, unmanaged network switch like TP-Link TL-SF 1008P or similar.

Read more details on that under Details of UDP Multicast Communication.

KNX messages are sent by UDP multicast, normally on group 224.0.23.12.

If you use filtering in your KNX/IP router, then really make sure that you use a dummy application or another tool to tell the KNX/IP router to not block the group addresses which are used by the trivum system.

Each bus device on the KNX bus has to have a unique device address. Make sure that you specified a valid KNX device address in the KNX setup of the trivum devices.

Scenes can be stored and recalled by objects

Up to 4 modes are available:

It is recommended to use Mode 4 by default, if your KNX actuators support it.

With modes 1 to 3, a trivum device stores up to 16 scenes.

If you want to store the current trivum device state in a KNX scene, perform these steps:

to program a scene:

use a programmed scene:

The following step by step example requires that you have the ETS software for Windows. In this software, you can open the group monitor, then send KNX messages by this group monitor for testing.

If you want to check if the trivum device can "see" KNX telegrams, you should

Gira X1 can be used as IP interface

The Gira X1 contains an IP interface, and can be connected with trivum through KNX interface mode. This requires trivum software V9.60 or higher.

Please note that the X1 is not an IP router, but just an interface. It can handle up to 3 ip interface connections in parallel, for example with one trivum MusicServer, and 2 trivum Touchpads.

If you have more devices that need to communicate with the X1, an extra IP router is required, like the Siemens N146, which sends UDP multicast messages on group addresses like 224.0.23.12.

Integration steps with Gira G1

In a project for the Gira G1, or the Gira Smart Home app, you create a web browser object in which you type an url like

containing the IP address of your trivum MusicServer system. Then you can use the full trivum music control within Gira.

Furthermore you can define in your Gira project some KNX switches to control trivum. They will send KNX messages which are sent via the X1 to the trivum device, for example to play a music favorite.

Gira HomeServer requires an extra IP router

The Gira HomeServer itself contains no IP router or interface, so it can not pass through KNX messages from the wire to LAN for trivum. So the Gira HomeServer requires an extra IP router for communication.

If your wall panels contains an integrated web browser you can test trivum integration, even without trivum hardware, by configuring the web visu URL from our online demo:

http://service.trivum.com:1080/

This will require hardware with one of these web browsers:

AirPlay has been introduced by Apple in June 2010. Many manufactures and Apple itself supports this technology to stream music to speakers. trivum supports AirPlay since many years and will continue to support AirPlay.

Apple supports AirPlay2 since 2018. The Apple HomePod speakers became the first Apple speakers which supports AirPlay2 in Q2 of 2018.

AirPlay2 is the multiroom extension of AirPlay and enables users to group AirPlay2 speakers. trivum Multiroom Systems do not support this AirPlay extension. They are compatible with AirPlay, but do not support the AirPlay2 grouping or other AirPlay2 extensions to AirPlay. This is because trivum itself is a multiroom system and we have a strong and reliable support for Multiroom and grouping. Control grouping via 2 different technologies would lead to unstable systems and inconsistent Multiroom installations because of the mixture of the two multiroom technologies.

On SC340, SC344, SC044 etc. .MP3 files can be uploaded directly in the paging setup menu. The files are converted internally to a raw PCM format, and synchronized to connected slave devices automatically. However this is done only if the device(s) have at least 350 mbytes of free internal disk space left. It is recommended not upload more than 100 files, as the internal storage is also needed for other things like cover art.

On C4, .MP3 files are played directly by a dedicated stream source card which is used for the paging. The ringtone files must be uploaded to the system’s internal flash disk.

This requires software V9.49 or higher.

This requires software V9.49 or higher.

Note: the LED flashing signal requires software V9.49 or higher.

Note: the LED flashing signal requires software V9.49 or higher.