Microsoft has already acknowledged that some of the legacy‑API issues stem from timing differences between the old and new stacks. Their own statement puts it this way:

“Some apps are relying on the slow speed of the old API and are allocating SysEx buffers after they are needed. This worked in the slower API, but not in the new one. We have some retry logic in place in an upcoming update to help work around this problematic code.”

More details are in their official write‑up:
https://devblogs.microsoft.com/windows- … rkarounds/

To rule out device‑side problems, I tested the Behringer BCF in every configuration I could:

• USB‑MIDI with the Behringer driver

• USB‑MIDI using the standard Windows class‑compliant driver

• Traditional DIN‑5 MIDI, connected to the UCX II MIDI ports

In every single case, the behavior is identical.

I do miss the old scale option with key control 'z' to switch between 100% and 200%.
Also scale levels 150%, 250% and 300% can be usefull for 4k and 8k screens.
It would be great to have those options.

I would guess that the TM FX scaling is related to the current screen resolution.

This could be either the "native" resolution of the monitor or the current scale used for the Windows Desktop.

If you scale your Windows Desktop to lets say 130% this is your new "100%" in terms of TM FX scaling.

I could be wrong on that; I never thought about it, but I think this is the way it works.

The new installer is great; it saves a lot of time for switching between the two versions.
Also, many thanks for porting a few things back to 1.99.

EDIT: I only had a little issue that appears to be local on my system.
I couldn't find my workspaces in "Quick Workspace Select".
After some testing, it turns out that this could be solved by a restart of TotalMix FX.

More layout presets would literally change my, and many fellow engineers lives for the better. Please and thank you.

RC 2_2 includes a minor fix for the updated but older version 1.991: the three new Preferences options were not saved - now they are. Link in first post.

You can zoom in but the names go bigger as well it stays the same. If your snapshot name is too long for visibility, zooming in will not help you out.
I'm on Mac but I expect the same behavior on windows.

Just install.

Under Windows, this has been possible for a very long time; I would say since the first 2.x release.

You need to move the mouse to the right area, hold the control key and scroll with the mouse wheel to zoom in/out.
Same as with the left part of TM FX with the channels.

Regarding the scaling, it would be nice to have the ctrl+scroll function active in the RoomEQ window as well. Some recent change made the REQ window very small and unable to scale up when simply making the window larger, on the biggest size the font size and knob size isnt consistent with what I have in the main window:

also, when I move the REQ window onto a screen that has different system scaling (window spawned on 150% scaling monitor, moved it to 100% scaling monitor), it suddenly looks quite aliased:

Thanks for the reply.  It's my understanding that Microsoft has already 'fixed' the sysex issues.  No other applications I use stops receiving midi input after a sysex is sent.  I will post an issue on their GitHub page.

I posted a bug report here.
https://github.com/microsoft/MIDI/issue … 4159209440

Others? I see just one user further up that reported BCF2000 one way working - something RC 2 definitely fixed. That is the same as what you describe - are you sure you are using TM FX 2.0 RC 2?

I have just tested 2.0 RC2 and the change from bitmap is not that great for my display situation. I have 2048x1152 resolution, 100% in Windows 10. In TM with 100% the text like "stereo" or "phase" is hard to read and looks not great either. Even with TM in maximized Window, the text looks too small for my eyes. When I reduce the size of the TM Window the text gets so tiny that it looks even blurred. In general all text / labels are not large enough to create a pleasant look. Switching to old mode for the time being. Hope it can be addressed in some way. There is plenty of space in my option to increase the (vector) fonts/text labels.

Thank-you for taking the effort to try an resolved the issue. Something is still not right.  Things lock up after my device sends 5 sysex messages (each of which is 15 bytes long). In my testing, I was sending them one at a time with 1 second in between. You are pre-allocating beffers? After you receive a sysex, you are recycling your buffer and pushing it back to the input?

lpMidiHdr->dwBytesRecorded = 0;
midiInAddBuffer(hmi, lpMidiHdr, sizeof(MIDIHDR));

As always, the locked state can be fixed by toggling the "Enable MIDI Control", which I assume closes and reopens the port. I would be happy to send you a device to test with.

That's your poragative. I will make sure that my users are aware of the compatibility issue with TotalMix FX.

Sure.

Which one mackie protocol do you use in the BFC2000 ?
Did you try change them ?
I would go thru and check out every one of them, 4.

Also make sure the firmware of the BFC is up-to-date.

My #1 request for TotalMix is: add a manual and / or automatic check for TotalMix updates. Most programs have the ability to update themselves. This would be a useful enhancement for all TotalMix users.

The beta has large letter "C" shown prominantly as a button for each channel strip. These widgets take a lot of space, but it seems their only purpose is to show panning. That is when I realized there are no tooltips to help the user understand what widgets are for. Tooltips would be helpful.

To show panning, a widget that does not resemble a button should be used, and it should have a landscape orientation (wide but short). The channel strips would be shorter if the panning indicator was shorter.

One problem I had with the previous TotalMixes (non-beta): no icon for launching the program was provided in Windows Start. I would have to burrow into C:\Windows\System32 to find it. After updating to the beta, that version is now gone, but "C:\Windows\System32\TotalMixFX.chm" remains. The beta now lives in "C:\Program Files\RME\MADIface\TotalMixFX_x64.exe". It does not appear in the Start menu, althought right-clicking on the program said that it should be. After toggling that, the icon appears on the Start menu. However, the next time I opened the Start menu it was gone. I tried again, and moved it to a group in the start menu, and it remained visible. So there is a problem with the start menu.

Overtall, the beta is a big improvement, which would be even better with additional polishing.

My quick tests shows that the  issue is fixed. Thank-you so much.  On the weekend no less.  Thank-you again.  I know it's probably unlikely for this version and I'm not sure of the status MIDI port notifications for the MIDI API, but this is what I use and it still works.

#include <dbt.h>

static const GUID GUID_AUDIO_DEVIFACE = {0x6994AD04L, 0x93EF, 0x11D0, {0xA3, 0xCC, 0x00, 0xA0, 0xC9, 0x22, 0x31, 0x96}};

BOOL DoRegisterDeviceInterfaceToHwnd(IN GUID InterfaceClassGuid, IN HWND hWnd, OUT HDEVNOTIFY* hDeviceNotify) {
    DEV_BROADCAST_DEVICEINTERFACE NotificationFilter;

    ZeroMemory(&NotificationFilter, sizeof(NotificationFilter));
    NotificationFilter.dbcc_size = sizeof(DEV_BROADCAST_DEVICEINTERFACE);
    NotificationFilter.dbcc_devicetype = DBT_DEVTYP_DEVICEINTERFACE;
    NotificationFilter.dbcc_classguid = InterfaceClassGuid;

    *hDeviceNotify = RegisterDeviceNotification(hWnd, &NotificationFilter,DEVICE_NOTIFY_WINDOW_HANDLE);

    if (NULL == *hDeviceNotify)
        return FALSE;
    
    return TRUE;
}
void addInterfaceConnectedNotification(HWND hWnd) {

    static HDEVNOTIFY hDeviceNotify;
    DoRegisterDeviceInterfaceToHwnd(GUID_AUDIO_DEVIFACE, hWnd, &hDeviceNotify);
}

This will give you WM_DEVICECHANGE notifcations.....

A ON / OFF button for the tooltips would be good, as sometimes tooltips can get annoying.

Here, it works.

EDIT:

Update and Good News.

Following mslinn’s report, I decided to try TM Remote again after a few months, and suddenly it wasn’t working for me either.

After some extensive troubleshooting, I’m pleased to confirm that this is not related to TotalMix FX 2.0 (or any driver versions). It was a local problem of my Windows installation.

EDIT2: Issue identified and solved.

A couple of months ago I decided to use Jumbo Frames (MTU of 9000) for making my network backup more efficient, and this caused the issue. After setting the MTU of my 10 Gbit network adapter back to the default value - MTU of 1500 - everything works perfectly.

I have deleted my subsequent posts containing troubleshooting information, as they are no longer relevant to this thread on TM FX 2.0.

Many thanks to Martin and RME for troubleshooting and finding this out using my sniffer traces.

Greetings to everyone
I can't install version 2 rc4, I currently have 1.99 x64 installed but when I start 2 at the end it tells me totalmix not found for update.
1.99 is just a desktop executable and it works fine
can you help me
thank you very much

Update: TM FX 2.0 has been released as installer, also including version 1.991. The above posts are an archive of the beta phase.

Download: https://www.rme-audio.de/downloads/tmfx … 91_win.zip

Please note that we have a big list of upcoming features and wishes for TotalMix FX 2.0, and of course we will continue working on it. One already available update is the global OSC control, which will be released as v 2.1, see here:

https://forum.rme-audio.de/viewtopic.php?id=43075

A big thanks to everyone that helped us bringing TotalMix FX 2.0 into the current state!