|
2004-12-16 22:18
|
Screenshot-ardour: editor.png (29,461 bytes) |
|
|
it is related to your configuration. you are missing the font that ardour uses to draw this text. which version of X are you running? |
|
|
Same "bug" with the gentoo 2004.3 with same Gdk-Critical message I have the xorg version 6.8.0-r3 with type1 and freetype fonts loaded |
|
|
I'm having the same problem with Ardour on Fedora Core 3. I posted a message about it just a while ago on Planet CCRMA list and another user reported that he also had the problem on FC 3. I was able to solve this problem by changing Gnome keyboard setting from 'Finnish (Latin 1)' to 'Finnish'. After that I run Ardour again and the track names displayed properly. However the problem came back after I rebooted and now I can't get it to display the track names even if I change the keyboard setting. I think this "bug" is preventing me from using Ardour. I'm getting '[ERROR]: state could not be saved' -errors constantly. Once I saw the track names properly displayed (after that keyboard setting change), I did not get any of these error messages. This is what I get to std.err when 'state could not be saved' -error messages appear: Loading session /projects/ardour/testing using snapshot testing error : xmlEncodeEntitiesReentrant : input not UTF-8 output conversion failed due to conv error Bytes: 0xB7 0x31 0x22 0x20 I/O error : encoder error Ardour version : 0.9beta23 |
|
|
ppkarppi - I don't believe that these problems are related. I could be wrong. Your encoding problem is because libxml uses UTF-8 by default, not Latin-1. It can be told to switch encodings, but I do not see any way to do this automatically. The key to the problem reported in this bug is the GdkDrawable message, which indicates a missing font. Using the XFree86 server rather than the X.org server (shipped with FC3) gets rid of the problem. So I believe that the core of the issue is missing fonts or incorrect font configuration setup. We need to find a set of fonts that are known to be present for XFree86, X.org and XDarwin. |
|
|
FYI... I too am running ardour under Slackware 10.0 and see the rectangles where the track name should be. I run under fvwm2, not gnome. However, I am running (for various reasons unrelated to ardour) the XFree86 4.3 xserver (libraries, binaries etc are still from xorg 6.7.0). In other words, the generic solution to the problem is not to run XFree86's Xserver. Obviously in some cases (FC3) this works, but in others it doesn't. During ardour startup I get many of the Gdk-CRITICAL messages as noted in the original post (so many that they exceed the size of my very large termina scrollback buffer). I have not noticed any mention of missing fonts yet but I will check in more detail soon. Note also that whereas I am seeing the rectangles in the track names, I am NOT getting any of the other problems noted by ppkarppi (problems saving state, etc). |
|
|
I am using X.org 6.8.1 Exactly what font is Ardour trying to use? |
|
|
the fonts are all specified in ardour_ui.rc. the location that this file is loaded from is displayed in the terminal at startup. look for "fontset" to see all of them. |
|
|
For me (Slackware 10.0 running XFree86 4.3 server as described earlier) the offending fonts are those in the Lucinda family. The "track_name_display" style entry references the font *-lucinda-medium-r-*-*-*-100-*-*-*-*-*-*-*. If I replace "lucinda" with (for example) "courier", then the track names are displayed correctly (albeit slightly too big). What's interesting is that this might be due to some locale/encoding issue. Under xfontsel, the above lucinda specification matches 20 fonts. The font which is displayed does correctly render A-Z, a-z, 0-9 and punctuation characters. It is the extended characters which are rendered as rectangles. I'm no expert on X fonts, but it seems to me that something funny is going on here. At least on my system I have the lucinda fonts and the fonts definitely render the standard ascii character set fine (at least in xfontsel and xterm). For some reason, when this font is used by ardour, the rectangles are displayed instead, as if the wrong glyphs in the font are being called up. Either that or ardour is getting one of the other 20 matching fonts and one of these can't display the standard characters. BTW, I'm pretty convinced the Gdk-CRITICAL messages aren't related to this font problem. For me I still got the messages when using "courier" which worked as previously outlined. The Gdk-CRITICAL messages probably need to be looked at but to me they don't appear to be related to the font problem being discussed here. |
|
|
Same here. Using CCRMA on Fedora 3. Im also having starnge characters everywhere Like in places where it must says "estéreo" (stereo) it reads "est�eo" |
|
|
one more thing that may help... today Firefox spat the following to the console regarding the Lucida font: Warning: Cannot convert string "-b&h-lucida-medium-r-normal-sans-*-140-*-*-p-*-iso8859-1" to type FontStruct |
|
|
I went back to Fedora Core 1 because I thought I was able to use Ardour on it without the problems I encountered with FC3 - I was right. Ardour works very nicely on Fedora Core 1 default workstation installation + Planet CCRMA software. Fonts render without any problems and I'm not getting any error messages. I have the same localisation setting on this FC1 installation that I had with FC3 (System language - English (USA), Keyboard - Finnish). |
|
|
I tried 0.9beta24 over the weekend on my Slackware 10.0 box (configuration unchanged from tests with previous ardour versions detailed earlier). With version 0.9beta24, the font used for the track names displays with no problem now; it works out of the box without having to change anything. From my point of view this issue seems to be solved. |
|
|
this appears fixed. if any of the reporters/commentators have other experiences, please reopen the report. |
- Anonymous
