What version of TotalMix FX is that?

What OS do you have ?!
Whats the file name of the ZIP archive that you downloaded ?

TM v1.31 appears to me very old. I have doubts that you downloaded the latest FF800 driver.

For Windows: The latest FW driver for FF800 is "driver_fw_win_3125.zip"
(Windows 7 bis 10 PnP Treiber für Fireface 400, 800, 802, UCX, UFX, Version 3.125.)

The bug that you mentioned should be fixed for a long time. If you can't update the driver you can still try to update TM FX, for example here:

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

Link fixed.

Ok...the bug is still there...still the same behaviour.

^

I cannot find that on the website...under driver archive there is

Windows

win_fire_2999.zip    Windows XP/Vista/7 32/64 Bit PnP driver for Fireface 400/800, version 2.999, 11/27/2009. Last version with MME support.
w2fire_2631.zip    Windows 2000/XP PnP driver for Fireface 800, version 2.6.3.1, 02/20/2007.

Thanks ramses
First of all I apologise for any frustration...it has been a nightmare with UAD, Waves, Steinberg (elicenser does not recognise my dongle) etc etc...with so many bugs wasting days of my time when I could actually be making music :-)

I went to the archive section as that seemed logical.

I have been dealing with totalmix vs drivers as a separate entity...and MC provided a separate link to TMfx

BUT

1. I have downloaded the link to the latest; as stated
https://www.rme-usa.com/downloads.html? … n_3125.zip

2. Installed it (TMfx says its actually 1.6 not 1.63)

3. The bug is still absolutely and very much there; actually worse now because Fader Group 1, when recalled in different snapshots jumps to different fader assignments...I thought the manual said it was snapshot persistent.

4. Snapshots are of course used just for control room output; 1 = ATC with sub, 2 = NS + Sub, 3 = Mulitimedia, 4 = Auratone mono. It all began with a mono routing on snapshot 4 which breaks the routing of the others.

Either way, if someone would be so kind as to load the workspace and confirm that would be amazing

Cheers
M

Thats strange as I just tested and loaded fine. I have zipped it as a package protection and made the link click friendly

https://bit.ly/2q39BwN

I have double checked it and it downloads/opens fine this end...thanks for your help

Any news?

Hehe...ganz richtig. It's actually Sunday night in Sydney...just looking forward to resolution...and who can stop thinking about making music...I'm 54 and its in my mind more than ever!

Vielen Dank MC
I used total mix in much simpler way before and cubase did the work...now (using Live which has no such facility) I have moved the control room functionality for 4 references to TMix, it requires a bit of a hack. The prob is in my case, there was no user notification this would happen with fader groups...I would have thought the fader group memory structure would have allowed for phantom channels and reassigned its array index for each snapshot; as its a persistent facet of the UI.
More than that, rather than hacking it with a fader group, simply being able to assign concurrent multiple outputs the the main out would be much simpler...1 controller to rule them all! No different to managing eg 5.1. Essentially Im just doing 2.1 but no easy way for the snapshot to route those to a master fader and hence to fader grouping which is a hack I saw on the forum. I realise there is of course speaker B but its a mutually exclusive route.

Not sure if this is also a 'feature' :-) but now, with the fader groups working, I dim a snapshot, then select another, the dimmed position of the fader group remains even though the new snapshot was saved at 0db for the master level. Who has priority in the group and with the preference to use snapshot master level, shouldnt that take priority over a fader group?

EDIT: All the faders are saved at 0db on every snapshot...why do they not honour the saved setting?

Once again...thanks.