I've been working hard on this and now it will show a volume indicator in the top left anytime the volume is changed via your keyboard or your RME hardware.  A tray icon will be next.

Here's an example of the volume indicator HUD:

Haha, appreciate the thumbs up reply!

Unfortunately doesn't do anything here. Questions:

- which of the three NET 5 versions needs to be installed? I downloaded the desktop version.

- the readme should be part of the program and available also when clicking on the symbol/icon, plus shown during installation. People will not find it on github.

- Remote Controller Address - IP or Host Name - stays empty?

> You'll need to have this set to 127.0.0.1 as TotalMixVC will attempt to communicate to the device over localhost.

I didn't see this crucial information anywhere before.

I downloaded 0.1.1, installed, added that adress and holy moses - it works! And looks phantastic! Congrats!

Really glad to hear you got it working.  Yeah, I honestly had forgotten to mention the IP that OSC should listen on because I forgot that I had actually changed it manually.

I have added this extra instruction in v0.1.1 which you are using to both to the README and the tooltip that pops up on the tray icon if the app can't communicate with your hardware.

I got it now working.

Looks nice, many thanks for your great work and running it as Open Source project.

A few comments / ideas:

1. Could you kindly add a comment to download the NET 5 Desktop (not the Console) runtime ? It was long ago for me that I had to install NET for an application and I was not aware of, that M$ does now this differentiation. I only looked for x64, to get the proper binary.

2. When TM FX OSC is not yet setup, then you get very nice guidance through a balloon tip when you hover the mouse over the icon of your app in the Windows notification area.
I wanted to make a screenshot of the instructions there, because I am new to OSC, but failed, because as soon as I press the hotkey for Greenshot (my screenshot tool) then the balloon tip window vanishes and you get nothing in your screenshot. Could you perhaps think about, to open a normal window that can stay open until you click an "OK" box ?
Then you can leave this window open for a while and open TM FX in parallel to make the necessary configuration.

3. Sadly I have no keyboard with volume controls. So I tried whether the normal arrow keys also trigger the TM FX volume control but they don't do. Is there perhaps a way, to use another key sequence, because not everybody has a Multimedia keyboard ?

4. What would you think about a mode to display the volume of "main out" permanently on the screen so that you have a permanent information about your volume ?! Either as smaller window with the option to run on top of all other windows (configurable option) or maybe even better, if you could provide this information directly in the Windows notification area like other tools (e.g. about computer metric) do to e.g. monitor CPU temperature and what not.

Good idea, thanks.

EDIT: but my idea was finally, that you do not need this extra step and move the instruction windows to a comfortably position, so that TM FX can be opened in parallel.

Thanks for the idea for another keyboard and the AutoHotKey script.
Nice idea, I am using it already on my own to open close TM FX and settings dialog

Don't worry, I was also working for open source for a very long time, I know this is simply work. It was just an idea, because we had in the last couple of month some people who had bad luck with volume mismatches with 0dB settings.

Although this is also not the final/proper solution to solve level mismatches in a recording environment it could at least support, to have volume information permanently visible on screen without filling the screen too much or blocking the view to the application.

For me personally this is no issue, I look to the left and see the volume on my ADI-2 Pro in my setup it has the additional task to act as kind of "monitor controller"

Yes, that would be an option if this appears to be easier to you.
But why you say for troublshooting ? I meant this for operation, so see the current value if you do not turn the faders.

I would really try to bring it into the Windows notification field, so that even with an application in fullscreen mode you could see it. Not sure where I saw this before, whether it was MSI afterurner or in rivatuner .. tried to find something for you as an exampled, but didn't find it.

After using the program for a few days now, I notice that it always loses connection after some time. It continues to run, but indicates that it has no connection. I do not know when and why it stops. The last time I noticed it was when I closed MusicBee and switched to Spotify, but it seems to appear randomly. I believe that previously the program would often work for about 1 hour and then at some point it would stop. When i quit and start the program again it works again for a while.

OSC support covers all faders/channels. Phones is nothing else than the assigned channel renamed, so it should be possible.

Thank you for the reply. FYI, since i updated TotalMix from 1.73 to 1.74 beta 3, i did not see this behaviour again. Maybe coincidence, i don´t know for sure, but i have no problems at the moment. If it happens again and if i find more information about possible triggers, i will write again.

Only for the record: i used 0.2.0 and yes, the mouseover indicated "not communicating".

Thank you so much for making this! I've stuff around with AHK scripts and had a very basic version of this working (also using OSC) but this is so much better! Thank you, Thank you, Thank you!!!!

I did just revisit this and can't see any OSC messages coming through for Phones.  I have developed a little OSC monitor which listens on a chosen UDP port and displays everything that the device sends.

Here's what I did in TotalMix:

• Assign Phones 1 to PH 3/4

• Move the Phones 1 fader

I also tried to unassign Phones 1 and move the PH 3/4 output fader and again, no OSC messages were being sent.

Of course, the moment I touched the master fader or input faders, I saw data being sent.

As such, based on what I can see myself, OSC messages are not being sent for several faders in TotalMix:

• Software Playback Channels

• Output Faders (excluding Main)

I'm on TotalMix FX 1.73 with an RME Babyface Pro FS.  If I'm missing anything, please let me know.  I'm rather confident in my observations as this is exactly what I saw when I worked on the app several months ago too.

Cheers
Fotis

Thanks for the reply mate.  I simply can't get this to work regardless of whether I use the knob on the hardware or the mouse.

Just to clarify this as clearly as I can, this is what I'm doing:

1. Click on Assign in the bottom right of TotalMix FX, and assign Phones 1 to PH 3/4
2. Move the Phones 1 output fader with the mouse in TotalMix FX
3. Use the OUT selection button on the unit to switch to headphones (the 2nd option) and use the master knob to change the Phones 1 volume

The changes are reflected in TotalMix FX but no OSC messages are being sent at all.

However, doing this for the Main output works perfectly.

You can see a screenshot of the slider I'm referring to here:

Regarding OSC I think it would be better to use local networking instead of the loopback device.
So it would be flexible when it comes to integrating the volume control within your network.
For OSC with local networking you can configure your endpoint in TotalMix FX with the broadcast address of the local network, e.g. 192.168.1.255.
OSC messages will then be sent to all devices but you can use your volume control on different devices (simultaneously) if you want to do that.

So going to a self contained installer takes us from 2 MB to around 100 MB.  If I enable trimming, it's still close to 70 MB.  I will have to think about this as there are clearly pros and cons to both approaches.

I'm be tempted to make both versions available so users can choose which suits them, but that may just cause more confusion.

Yeah, you're absolutely right.

Hi, I posted this on the GS forum, but this one appears to be much more active, so apologies for the duplicate message. Cheers!

This is really fantastic and I appreciate your efforts. I have been using TotalMixKey for years, but find I need to reinstall the virtual midi drivers from time to time after windows updates and it's a pain. I'd just like to echo the comment on your GitHub page related to connecting the Mute key to TotalMix Dim. That's the only thing I miss from TotalMixKey. I see you replied with some code for that, but unfortunately, I haven't a clue how to implement that. Anyway, thanks again. I know you're doing this in your free time.

Very cool. I am no coder, but have gotten my hands dirty more than a few times with decent enough results when following a tutorial. I started poking around the json files and then quickly ran off to these forums because it was clear I was in over my head.

Anyway, I appreciate the reply. It's cool that you're doing this. This functionality (much like TotalKeyMix) is so very much welcome that I can't imagine working without it.

Okies, I have a build ready for everyone to try which you can download at https://artprodeau1.artifacts.visualstu … taller.exe.  This build also adds a plain tray tooltip text for Windows 11 which has broken the pretty widget functionality (due to a bug).

I'll be running this for a full day on my system before the officia release in case any issues pop up.

I'd like to thank everyone for this suggestion, it was a really great idea which I find myself using now too.

Glad to hear it's working well for you.  Yeah, you will need to restart TotalMix Volume Control as the installer won't do that automatically when upgrading at the moment.

Cool project! Just stumbled over it on google/github while doing some research on how to communicate with my RME UFX

@fgimian: Are you familiar with the microsoft surface dial? It's a standalone bluetooth volume controller. If i use my volume up/down keyboard hotkeys it triggers the TotalMixVC volume adjustment. But if I adjust the volume with the surface dial I only adjust windows volume. Strange.

Any suggestions on how to troubleshoot or get around it?

Thanks for the reply.
Have installed AutoHotkey and used the custom key binding options in the surface dial to increase/decreased the volume. Works like a charm!

Only thing I wished I could change was the amount of db/volume pr keystroke that was increased/decreased. Looks like per volume_up/volume_down totalmix vc? increases/decreased 1.2db. Is there any way in totalmix vc to change this to a lower number? 0.8 or something for example.