Wow cool.
Configuration from old tool, has been detected as you mentioned, very nice indeed.

I could add the 12Mic, which I am monitoring through MIDI over MADI, a 2nd time as an IP device.
But the device is not being shown as online, doesn't work.
Accessing the 12Mic through Internet browser works ...

2 issues:

1. After the installation of RME connector the old program MIDI Remote AVB is not working anymore, can't be started up.

I reinstalled my backup from 14.05.23, after that I could execute MIDI Remote AVB again.
Then I again installed RME Connector, started it up for a test and then quit the application.
Same issue again, MIDI Remote AVB can't be started.

When looking to
- the installation folder, then both programs are still visible
- Windows Programs and Features, then I see, that both applications are still installed

And I personally would welcome, that both applications can co-exist, as RME connector still has issues on my PC.

2. Problem is, after 2 minutes RME Connector stops working, then I can access 12Mic only via MIDI over MADI.
I can see on my Windows Gadget that the communication completely stops, after 2 min no network activity anymore.

Maybe misunderstanding regarding point 1. Once you install RME connector, then MIDI remote AVB is not working anymore, no matter whether RME connector is running or not.

Many thanks will try.

This has been fixed in Beta 14.

The level Meters for Phones out are not working
Beta 14

How about supporting MICSTASY?

There is no more option for selecting midi connections when using midi over Madi in beta 15.
Or did I overlook something?

Beta 15 introduces three bugs

1. MIDI input device is not being written to preferences file

2. after writing the proper config to the file it works, but not after startup

3. removing and re-adding of devices deletes the config of the devices: changes in preset names and I also think presets and snapshots. How to repeat: add devices, change preset name and change preset. Remove device, quit, re-add device, you see the default preset names, not your custom names.

A possibility to backup devices, presets, snapshots - comparable to a TM FX workspace file - seems to be missing.

+1

And also ADI8QS with full routing would be nice

Hi Vanceen,

if the LEDs at the network port of the 12Mic (with current firmware!) show activity, and within its menu STATE>Remote>HTTP Remote is toggled to "on", it is up to the operating system (and its network filters/firewall rules) to prevent RME Connector's automatic discovery of the attached device.

You could then check in the same menu of the 12Mic that an IP address has been assigned correctly and enter this address manually in your preferred browser to ensure that the connection is indeed working and the Web Remote can be accessed. If that is the case (communication via IP address works, but auto discovery of RME Connector does not work), please post your OS details (Windows or macOS version etc.).

-Max

It worked. Thanks.

Hi Vanceen,
this seems to be unrelated to RME Connector. Also, you do not have to change the DHCP setting - the 12Mic will use an address that starts with 169.254... if there is no DHCP server, and it is shown on the 12Mic after it was assigned. Have you tried disconnecting USB and using the device name in the browser's address bar (as described in the manual) to reach the device over network? If that does not work, please open a separate thread.
Max

Many thanks Max. Update installation went smoothly.

A question whether this is normal.

1. The display via IP also seems to react somewhat slower.

2. I see a difference in the display of the RMS level on the 12Mic, depending on whether you access the 12Mic via MADI or via network. The bar of the peak display is at the same level. However, there are differences in the display of the RMS level.

The difference at low volume:
- top row via MADI: you can see a green (I think this is a RMS bar), green filled up to the peak bar.
- bottom row: same peak level but no RMS bar.
The scale of the level meters looks the same. Can you explain the difference?

In the next posting you see the same at higher levels, there you see in the Peak Bar no level difference.
But the RMS bar via Network (bottom) is -10 dB lower.

Hi Ramses,

yes, that is normal.
TL;DR: only peak levels are received via MIDI.

You can observe a similar phenomenon when you use an Octamic XTC and compare the TotalMix value to the MIDI Remote value. TotalMix shows Peak and RMS values, but the MIDI Remote shows only the peak value. Users would guess that MIDI Remote shows peak levels from the fact that it is an A/D converter (avoid clipping under all circumstances) and that there is only one level bar. Peak metering is a useful default.

Here's an example of a single pulse:

The bandwidth in MIDI is not sufficient to transport both peak and RMS levels. It is not even sufficient to transport peak levels for the analog I/O with a fine granularity - the devices (including XTC) send 0 to -6 dBFS in 0.2 dB steps, -6 dBFS to -42 dBFS in 0.5 dB steps, and -43 dBFS to -64 dB in 1 dB steps. Also, since several devices in a MADI loop use the same MIDI port, the refresh rate for increasing levels will become slower when you add more devices controlled over the MIDI port. No peak hold levels over MIDI either.
Using network, there are no limits - RMS, Peak, and Peak Hold levels are received with 0.1 dB granularity and much more frequent (always faster than screen refresh rate).

So what does the MIDI level meter actually show? We decided to hold peak by default for a couple of seconds (the same behavior can be activated for network level meters if you adjust peak hold to 'auto' in the visual settings menu), and let the green/yellow gradient bar fall with a release time of about 10 dB/s without hold (so it begins decreasing first). You can configure a similar peak meter in DigiCheck (by default, it falls a bit faster and has a shorter peak hold).

Admittedly, this co-existence of Peak/RMS and PeakHold/Peak level meter can be confusing, especially if you control the same device via MADI and network at the same time. We could use different colors or add additional labels to show that it is a peak level meter, or not show the top peak bar at all. All of that seemed unsatisfactory in practical use. The overall aim was to have level meters well suited for adjusting the gain remotely via MIDI (as before), and then bring full TotalMix-style level meters for networked devices.

I hope this answers your question! By the way, this might also have lead to your previous impression that the level meters seemed 'slower' over network. They are not; actually they are faster, and they show RMS levels instead of a falling peak level.

Max

Tested controlling four Octamic XTCs over MIDI using RME Connector 2.0.0 on a MacBook Pro M1. I am continually impressed how your software releases improve the user experience, even with older devices. No other company does that. It worked fine, until...

Resizing the window triggers MIDI interference from within RME Connector?

We are familiar with MIDI interference between TotalMix FX and MIDI Remote; it's brutal, as the devices go crazy. We have a strict "No MIDI Remote" policy during live events and recording sessions. We noticed the RME Connector detects MIDI interference, which is an improvement over MIDI Remote. It worked fine running by itself, until we resized the window. Dragging the window corner triggered MIDI interference (seemingly from within RME Connector?), a warning displayed, and the OctaMics went crazy. It stops when you stop resizing the window?

Our Octamic XTC's are controlled via MIDI over MADI through a MADIface XT, which is connected to a MacBook Pro M1 via USB3.

No other applications were running, only RME Connecter 2.0.0. It's controls worked well, and the OctaMics responded perfectly. As soon as we start to resize the RME Connector window, there is a blast of MIDI traffic, the "MIDI Port busy" warning appears on RME Connecter, and the OctaMics to crazy. It stops when you stop resizing the window. Surprised us, since no other (potentially interfering) apps were running.

Octamics going crazy with other midi traffic:
I know this, but I found it to not affect the devices itself. It is only visible on the remote. Isn't this correct?
Georg

At georgob: when I connected XTC and ADI-8 QS (if I remember right) to one MADI bus of an HDSPe MADI FX and using
- remote control of XTC via TM FX (Auxdevice)
- remote control of ADI-8 QS using MIDI remote
then the XTC could not handle two different remote control protocols at the same time (via MIDI over MADI) well.
Randomly things / functions have been turned on or off on the XTC like Inst and PAD and you could hear the internal relays for such functions clicking which switching. So at least in this scenario, it issues real changes to the devices.
Not 100% sure whether also the ADI-8 QS settings were changed.

We were not running -any- other applications during our test, only RME Connector 2.0.0. We were using the DriverKit USB driver v4.09 rather than the kernel extension driver.

I posted <a href="https://littlemountainmusic.org/download/rme_connector_midi_interference.mp4">video</a> of the RME Connector window and a <a href="https://littlemountainmusic.org/download/rme_connector_midi_interference.txt">log</a> of the MIDI traffic during the "apparent" interference. The log shows regular status requests/responses, and as soon as you start to resize the window (at 09:55:16.563 in the log), the MADIface starts responding with malformed MIDI packets, even while RME Connector keeps sending its regular status requests.

I agree with georgeb that the OctaMics aren't actually misbehaving (since they're not receiving any crazy MIDI requests), only the UI is going crazy (since it receives malformed MIDI responses).

Thank you for the detailed analysis, we will have a look into this.

@max: Is this the cause for Octamic XTCs flickering on the Remote when other Midi messages are coming though?

Georg

Good to hear!

That might be a cause, yes. However, we expect the XTCs to not flicker (briefly display wrong settings/levels) in a daisy chain of SysEx-controlled devices without any other software attempting to use that MIDI bus.

Hopping the micstacy support too. I'm using one 12mic, one micstacy and two XTC at the same time. It has been furstrating when switching the control software.