jpc.zonder wrote:[UP] Well great, it's one month to the day since a message was sent to RME support, and no response. I must admit that I didn't expect this. Hello, RME? I have to work.
It can always happen that something accidentally goes wrong. We're all human. There are better possibilities than complaining after a month in the public. You could have resent your mail after a few days and kindly asked what happened to your request etc.
By the way, I asked you a month ago for details and repeatable steps to better understand the problem, see post #4. Until now you haven't provided more detailed information to describe your problem in an understandable way to be able to support you further.
Simply referencing a very short subject line or a youtube video is not sufficient as it does not explain exactly WHAT the problem is. There was already confusion whether you mean the recall function of TM FX.
So a clear description of the problem is needed, it should include the following things:
what you do exactly, bring it down to the least amount of simple, repeatable steps that reliably trigger the issue and leave out everything which is not required to bring it to the point
the result obtained and why you are not satisfied with it
the expected result
TM FX can be regarded as very mature and stable: after over 20 years of development, a clear concept and because all RME recording interfaces use exactly this software. I recall snapshots every day using TM FX buttons and ARC USB, I restore my entire workspace using "Workspace Quick Selects" by mouse click or using function keys. Everything works as expected.
Since storing and retrieving snapshots and workspaces is a very important feature of TM FX, if there was a problem in this area, more customers would report problems, but that is not the case. So it sounds more like an operational problem to me.
In order to clarify this, please provide the needed information, thanks.
BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14