You might use normal font size, but you changed the font itself...

Okay I have found the font settings and all fonts seem to be set to their default setting of Segoe UI with a size of 9, which I believe is the Windows 7 default. Again I have check my DPI is at 100%, the Fireface box text appears to be larger than all other text within Windows. This is the only application where there seems to be an issue. This is very odd. Any other thoughts?

I am using Windows Aero default. All other dialogs appear correctly, Fireface settings seems to have larger text than any other dialog. Is there some registry settings for the fonts in the FF settings?

OK thanks for your help, I'll keep hunting and post back if I find anything incase anyone else comes across this issue. For information my system is a new Sony Vaio Z series, and I am using the preinstalled operating system without changing any display settings, so I suspect anyone else who has this notebook with a fireface will experience the same issue. Perhaps my only option is a fresh reinstall.

Hi all

I have the same problem with the settings dialog of FireFace UC. I tried it on two different notebooks (two different brands). I also tried with different screen resolutions and system font sizes.

It seems that the font and field sizes do not resize properly. I am a software programmer and such issues usually have its cause in some 'hard-wired' windows programming, where system context of the underlying os is not taken into consideration. In my opinion it is definitively not an issue of the pcs/notebooks/setups we are using but an issue of the software.

Update on 19.04.2010:
I changed in extended display settings the font size for dialogs to the smallest size possible (again on two completely different notebooks). After my setup change, all dialogs of other software showed smaller texts accordingly. The Settings Dialog didn't change at all, thus corroborating my theory that the system's context is not taken into consideration in this program. By the way: I have absolutely no display problems with TotalMix!

My comment above is still valid. We need to know what is different on your system than all the other multiple ten thousands users worldwide that have no problem.

Hi all

I knew that I was right but as usual in these days clients have to prove that they are right as vendors (in this case RME) more and more just state that ?multiple ten thousands of users worldwide do not have your problem? and as a conclusion ?the problem is your system? (or you) and not with the vendor's product!

Even though I stated that I made tests with different systems and that I am software developer the only (and very superficial) answer of MC is repeating all the time the same message.

As a consequence I analysed and in the end tweaked RME?s Settings Dialog program and here is the result:

First, the Settings Dialog program delivered by RME:

[img align=Settings Dialog by RME]http://i43.tinypic.com/2a8i4xl.png[/img]

Second, the same Settings Dialog program tweaked by me:

[img align=Settings Dialog by RME (tweaked)]http://i39.tinypic.com/2unvskg.png[/img]

So what was the reason? As many users already reported, changing any sort of settings didn't influence the behaviour of the Settings Dialog. Why? Because the Settings Dialog doesn't take the OS context into consideration. Up to Windows XP the "standard" dialog font was "MS Sans Serif". From Vista and Windows 7 on the standard dialog font changed to "Segoe UI" which has a significantly smaller footprint to accomodate higher resolutions of these days.

Every Windows programmer knows (except the one who programmed Settings Dialog) that it has to take OS context into consideration. In this case it would mean: If the program is running with Windows XP or earlier use ?MS Sans Serif?. If the program is running with Vista or later OS use ?Segoe UI?.

I edited the resources directly within the Settings Dialog Exe File in order to use ?Segoe UI? instead of ?MS Sans Serif?.

So, in the end, the client did the job of the vendor for free?

MC, you should be glad that I anticipated a problem RME will have when "multiple ten thousands of worldwide XP users" will upgrade to Windows 7.

MC

If I understand you correctly (citations of your answers):

- "Settings dialog uses a standard dialog form from MS (not so popular anymore)"
- "is an old-style dialogbox"
- "We have no time to reprogram the Settings dialog"

and consequently (my interpretation of your answers):

- Even though you are clients and have spent a lot of money for our products, you have to hack into your registry to solve our no more up-to-date program.

I will neither further comment on that nor follow anymore this thread. RME is not willing to do anything in this area? It is fine for me and I will base (as I always do) my future decisions on vendor's behavior and attitude.

Just a very last comment: It is very interesting to see that you made some investigation only after my work and not earlier?

Hi,

I found this link interesting and explaining here from Matthias above posting links

http://blogs.msdn.com/developingfordyna … cs-gp.aspx

I will check here with my Windows 7 Home Premium 32-bit to see what's written in the register.

regards S-EH

Hello Matthias,

it's not so a good idea to use the MS Sans Serif font in today's software. Just use the MS Shell Dlg font, which will use the font which is configured in Windows control panel (Tahoma typically on an XP system). The advantage is that the font is the same as in every standard Windows dialog and normally a true type font is used. All the hassle comes from MS Sans Serif being a bitmapped font.

And beleive me, this takes a bout 3 seconds in Visual Studio.

Cheers
Axel

I don't disagree with what you said, but have to correct this statement. These days everyone has a hi-resolution monitor. The point is that the error only shows up when your graphics card is natively supported to run in hi-resolution mode during Windows installation. And that seems to be a seldom case. Otherwise the forum would be full of complains about that. We really have lots of Windows 7 users already.

BTW, IF this turns out to be the problem (did it fix yours?) we could provide a simple (reg) file on our website. Double-click and one reboot and everything would be ok. Nobody is forced to edit the registry then.

Mathias,

You are a bully and a coward!

BULLY
A bully because you attempted to badger customers into trying to explain what was different in their systems from umpteen thousand others - something they could not possibly do, especially given the wide variation in DAW configurations.

You were right, it was something they did, but since it was an obscure Windows 'feature' that kicked in unbeknownst to them, they could be forgiven for thinking it was an RME issue, especially as the two dialog boxes behaved differently directly due to RME choosing to use different underlying technology for each.

That no-one at RME has had this issue just indicates you must all be using single small screens on your Win 7 systems - hardly covering the gamut of customer systems. So your dismissive comments about it not affecting your Win 7 systems - thus implying that there is therefore no problem with using Win 7 and RME dialogs - was rather premature, as you just haven't applied the configurations that customers will likely use.

When a customer (riiv) showed that it could be changed, only then did you actually start doing something about it, but not without first having a go at him as well. It was not hard to tell that he was frustrated with your fobbing off customers rather than taking control of the situation.

COWARD
A coward because you delete my post then make dismissive and derisive comments about it without allowing other readers of your comments to judge for themselves.

With RME and Steinberg, some really custmer-hostile elements seem to be taking over, where customers are treated with contempt and when they try to get some action on their concerns, are basically told to solve it themselves. Such arrogance.

BTW. The full reg file as per the first link did the trick.

I have a couple of slightly older nVidia cards and Dell monitors - something I would imagine is not so rare.

Poor MC, if you consider my replies in this thread as attacks.

My 'early attacks' must be very well hidden somewhere as I do not find them in my early replies.

If anything could be considered 'attacks' from my side, then this: I seriously questioned your behavior and attitude at a later stage in this thread as you only started to look seriously in this topic after I proved where the origin of this error was. To be clear: I made your job but obviously you still do not understand my standpoint. So for me it is like talking to a wall...

So please, if you are not able to manage such threads and discussions, you should do something else. Try to improve yourself and stop fingerpointing at others. You do not help yourself, nor do you contribute positively to yours or RMEs reputation.