Slow text rendering in KDE.

Hi there,
I recently starting getting quite fed up with how I felt that writing stuff in kate (or kile, or kdevelop etc) was very slow and unresponsive. The effect I was getting is that there was a big delay (of up to a second or two sometimes) between hitting the key and the character appearing on the screen. It's especially noticeable if you type a whole bunch of stuff very quickly - wait for the screen to catch up!
I did a few experiments, and managed to rule out any kate plugins etc, though I wasn't experiencing the same thing in konsole / yakuake. Also, I noticed that if I made the kate window smaller, so not so much of the text I was editing was visible, it would speed up. In fact, the size of the lag seems proportional to the amount of text visible and being rendered while typing (even if that text is not being changed).
I fiddled with a few settings and noticed that I could fix the lag (i.e. completely get rid of it) by disabling "sub-pixel rendering" in KDE's font settings (and restarting the relevant program). Incidentally, it's not enough to have the the "sub-pixel rendering" box enabled and select "none" - that still creates the lag.
Therefore, I can work around this for now by unchecking the box, but it got me interested in this. I'm thinking that it's something to do with the way Qt is rendering the fonts, possibly to do with my intel graphics driver, but possibly not.
So this post is twofold really; firstly to let others know of the workaround in case they're also experiencing this, but also to ask around to see if other people are noticing this, with a view to filing a bug / feeding back to developers / deciding that I need newer hardware.
My specs:
- KDE from kdemod 4.2.2
- intel 945GM graphics card onboard
- xorg intel driver (currently version 2.3.2, but I've experienced the same with earlier and later versions, up to the current git version)
- XServer 1.6, though again, I've experienced this with 1.5 too.
- Using EXA for rendering, though again I've had the same experience with XAA. Haven't tried UXA yet.
So... anyone any contribution?
Cheers,
Pete.

I experience sever slowdown in scrolling in Kate with my Intel 965. However, I do not experience any problems in other applications (Kontact, Konsole, etc.). I did not experience the problem (at least noticably) when I was using Xorg 1.4 and XAA. Hopefully, 4.5.1 resolves this issue for me as well... It's harder to deal with large code files now.

Similar Messages

Adobe Photoshop CS6 Very Slow On Rendering Type

I have a notebook with specification as mentioned below :
Lenovo Ideapad Y470P
2nd generation Intel Core i7-2670QM Processor( 2.2GHz 1333MHz 6MB)
Windows 7 Ultimate x64
AMD Radeon HD 7690 2GB
8.0GB PC3-10600 DDR3 SDRAM 1333 MHz
750GB 5400
I'm using Adobe Photoshop CS6 (64 Bit) for doing my job.
Right now, i have a task to create a banner with dimension 800 x 900 Centimeters with Resolution 300 DPI and Color Mode RGB 16 Bit.
The file size when blank is about 56.1 GB.
The problem is, when i add some text with Horizontal Type Tool and click on the Move Tool, the Rendering Type screen show up and take a very very long time to finished.
I have made some configurations to my Photoshop that i found on Adobe Forum, but the problem still persisted.
Some configurations that i've made is :
- Turn off the Automatically Save Recovery Information
- Set Maximize PSD and PSB File Compatibility to Ask
- Set the Memory Usage to 95%
- Set the Cache Levels to 8 and Cache Tile Size to 1024K
- Set the Graphics Advanced Settings to Drawing Mode Advanced, and Check the option Use Graphics Processor To Accelerate Computation, and Uncheck the option Anti-Alias and 30 Bit Display
- Set the Scratch Disk to another partition ( C:System D:PageFile E:Data F:Scratch Disk)
And after all of that configuration, my Photoshop still slow when Rendering Type.
Could you give me some tips to solve my problem?
Thanks

300 ppi for a banner that size is categorically not normal. Guaranteed.
Get specific instructions from the shop that is going to print it.
You keep confusing ppi with dpi. The resolution of an image file really is expressed in ppi, pixels per inch, not "dpi" which is dots per inch. The precise terminology is as follows:
DPI = Dots per inch = units used to measure the resolution of a printer
LPI = Lines per inch = The offset printing 'lines' or dots per inch in a halftone or line screen.
PPI = Pixels per inch = the number of pixels per inch in screen/scanner file terms.
Here's a link to a discussion that may interest you:
http://graphicdesign.stackexchange.com/questions/487/what-ppi-should-a-large-format-artwor k-for-print-be-done-at
It includes the following chart and subsequent comments :
"The rule of thumb is that we need 1.5 to 2 times the LPI in PPI to get acceptable results.
"Viewing Distance   Present Study
20 feet    greater than 10 LPI
18 feet    18.75 LPI or greater
16 feet    18.75 LPI or greater
14 feet    37.5 LPI or greater
12 feet    37.5 LPI or greater
10 feet    50 LPI or greater
8 feet     65 LPI or greater
6 feet     85 LPI or greater
4 feet     100 LPI or greater
2 feet     133 LPI or greater
1 foot     150 LPI or greater
6 inches   150 LPI or greater
"Presumably, for a banner 3m x 5m, you'd be standing at a minimum of, say, 10 feet. (Just eyeballing the wall here.) So, by this table, you'll need 50 LPI minimum. That would mean your raster graphics should be about 100 PPI, or 75 PPI at 12-14 feet. Considering that and the fact that 2x LPI is pretty conservative for reproducing fidelity (often 1.5xLPI is "enough"), this agrees with [the given] advice of 75 PPI being acceptable."
Talk to your printer. I suspect they will want a file at under 75 ppi, or even much less. Follow the printer's advice/request.

Adobe Premier pro running very slow when rendering a file

Adobe Premier pro running very slow when rendering a file

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Text rendering on MacBook Pro differs from PowerBook.

It appears that various applications use a different text rendering technique on the MacBook Pro than on the Powerbook. Camino for instance uses sub-pixel rendering on the PowerBook but standard anti-aliasing on the MacBook Pro. So do Word and MSN and others.
At first I thought it had something to do with the app being universal or not. But Camino is supposed to be a universal binary.
Anyone has a clue about why this difference?
(You can easily see if sub-pixel or standard rendering is used by zooming in with option-cmd-8. Standard rendering has only shades of gray. Sub-pixel rendering uses colors. More on OS X text rendering can be found here: http://daringfireball.net/2003/11/panthertextrendering.)

First, I wonder - does it look good or bad? Or, is this simply a comment that it is different?
Second, and I'll bet this is your answer, is that the difference is most likely due to the type of video card being used. I notice that nothing effects rendering of fonts like the type of video card.
I am interested because I will be doing lots of text work on my MBP, and would like to know if there is an issue with this. I had a notebook (Toshiba) about three years ago that the text was soft and nothing I could do would make it sharper. I ended up dumping the notebook and getting something else. MS Cleartype seems to work to some degree in Windows machines, but I don't see anything like that on my PB. However, the PB is fine as it...
Bob

IOS8 iPad Air (A7) Safari Auto-fill slows text entry down

iPad Air (A7)
iOS8
64GB
I am entering text into the following site (renew a subscription): http://oracle-sub.halldata.com/site/ORA000401OCrenew/init.do?{removed http query params}
Safari auto text is severely slowing text entry (the suggested text at the bottom of the screen is cool, but seems to cause a drag)
Aside from turning this nifty feature off, iOS8 safari seems it needs to be tuned to work properly.
Suggestions?
Thanks

iPad Air (A7)
iOS8
64GB
I am entering text into the following site (renew a subscription): http://oracle-sub.halldata.com/site/ORA000401OCrenew/init.do?{removed http query params}
Safari auto text is severely slowing text entry (the suggested text at the bottom of the screen is cool, but seems to cause a drag)
Aside from turning this nifty feature off, iOS8 safari seems it needs to be tuned to work properly.
Suggestions?
Thanks

Font or text rendering problem :(

Hello!
I have a problem in Numbers with text rendering or something like that.
Some characters have wrong representation right in cells. And when I export document to PDF all characters which cross the cell border have white lines.
I already tried to rebuild font cache without luck.
Can anyone help to figure this out?
Thank you!
P.S.
Numbers 2.1, Mac OS X 10.7.2, here is a snapshot:

You already know that but it may be interesting for others.
(1) the OP's document behave the odd way on my machine.
(2) When I insert similar characters in a complementary table in the original document, it behave flawlessly.
Now are new informations.
(3) I copied the content of your tables and pasted values in tables of a blank new document.
With the font set to Helvetica everything was OK.
I tried several fonts.
Avant Garde --> OK
Baskerville --> OK
Calibri --> OK
Arno Pro --> OK
Cochin --> OK
Garamond Premier Pro --> OK
Minion Pro --> OK
Warnock Pro --> OK
Arial --> Odd behavior
This odd behavior doesn't strike in TextEdit or Pages.
So there is clearly a problem between Numbers and Arial
Yvan KOENIG (VALLAURIS, France) lundi 30 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My Box account is : http://www.box.com/s/00qnssoyeq2xvc22ra4k

Slower pdf rendering since v26?

I noticed a slower PDF rendering (iOS) on v26 compared to earlier versions. Did anyone have same behaviors?

I would suspect you have not tried reading a .PDF file on your Windows 10 TP system because there is in fact a WindowsApp called Reader as noted by MakeMeLaugh that does indeed read .PDF files.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Dynamic text rendering in Cp4

I'm having an issue with an embedded AS2 SWF that spawns a MovieClip containing a dynamic text field populated with ActionScript. When I publish/preview the Captivate movie with externalized animations, the dynamic text renders fine. However, when I do NOT externalize animations, the dynamic text appears garbled.
I'd go ahead and externalize animations in this project, but there are other embedded SWFs in the project that work correctly only when they are not externalized.
Anyone have experience with this or a similar issue?

I just had a similar problem and fixed it by embedding the font into the Flash SWF and also embedding uppercase and lower case characters.
Not sure why this was needed since I never had to do that with Captivate 3, but that was the only thing that corrected the problem.
/Michael
Click here to visit the www.captivate4.com blog

Slow page rendering due to a LOV!

I was trying to figure out what the cause of my slow page rendering was and looking at the debug results I figured for one of my page items which is a LOV I get:
0.18800 13.98400 ...Session State: Save "P2_CATEGORY" - saving same value: "4"consistantly taking around 14 seconds.
I have even simplified the LOV to type static, and it only has 6 values. There is only one computation for this item which is static assignment only when the value of item is null.
I'm wondering if it's the item being saved in session really which is taking all this time or something else could be causing it to run slow. I mean, can the debug results be misleading me?
I'm using Apex 4.1 and Oracle 11g. I have 40 Shared_servers set.
I would appreciate any hints.

Hi,
set partialSubmit=true on the button
Frank

Dreamweaver CS6 and CC both very slow page rendering under Mavericks

Dreamweaver CS6 and CC both very slow page rendering under Mavericks compared to 10.8.5
Any ideas?

One other thing I am seeing:
When I open any document (html, javascript) inside DWCC now, then close it without any changes, DW asks if I want to save changes.
I just tested this under 10.8.5 and there is no lag there, nor are documents mysteriously modified when opened.
Note: I have tested this both with and without other Apps or extensions running in Mavericks and 10.8.5

Text rendering property

Firefox 3 supported the text-rendering property.
Does ff8 also support the above property?
From what i have come to understand it does not that is why i am asking, to be certain.
Besides it does not make sense an older version supporting it and and a newer one not.

So, as i understand, firefox 8 '''does not''' support it.

{text-rendering : optimizeLegibility} turns off google webfont in DW CS6 live preview (suddenly)

I'm currently working on two websites for the UN, based on Wordpress, child themes based on twentytwelve and twentythirteen.
I started to work a certain time ago on the child theme for 2012 which uses "Open Sans" fonts.
I don't remember having any problem with this site: everything was working ok, I made a few changes but nothing important.
I turned to the nd website based on 2013-theme, it works perfectly and DW CS6 is a real time saver for creating a child-theme, nonetheless...
This morning I turned back to the 2012-based wordpress site: every text was simply not displayed anymore... only in live preview in DW...
Even with the parent theme, the text was siply not displayed (so don't suggest my css code is bugged or what...)
After a while, I figured out it was not really a problem regarding the font itself, but with the CSS property "text-rendering" with value set "optimizeLegibility".
Commenting out this declaration solved the problem. Nonetheless...
1 month ago there was no problem. Then suddenly...
Is there a problem with the live preview mode and this CSS property? (indeed there is a problem)
Can we have a fix for this? I mean, an update for DW CS6 (not for DW CC) ?
TIA

Hello Nancy!
Normally, according to https://developer.mozilla.org/en-US/docs/Web/CSS/text-rendering Gecko could take it in charge too, but seems to override this setting (a thing I can understand, Gecko is using a fast rendering engine). So you're right: at this time, it can impact only webkit/chromium engines. Which, as far as I know is the underlying engine(s) behind "Live Preview". And it does impact readibility in DW CC (it improves it).
Personnally I'ls better stick to the real CSS properties for kerning, alternative uppercases and ligatures, BUT the wordpress team seemed to think it was a good idea to use it (along with many other strange ideas such as using rem unit for the layout).
The real thing here is: some weeks ago, when I started to tune the 2012-based theme I use for this site, I'm pretty sure I was able to read the text in Live Preview in DW CS6. I wouldn't have chosen to use this theme with such an annoyance, else. So basically, it's really strange that suddenly this property has such an impact on the "live preview" mode of DW CS6. What I would really appreciate here is a small update/bugfix to DW CS6: I don't need this property to be taken in charge in DW CS6 as it is done in DW CC, I'ld just want this property not to impact the live preview.
Last : I mentionned an update of DWCC being possibly a culprit for this. How relevant could be this statement ? Are "live preview" modes shared by DW CC and DW CS6 ? (Even if, of course, this "bug" is not happening with DWCC).
PS: Thanks a lot Nancy to pay attention to my posts as I often yell a lot here.

Difference in text rendering between PDF and Mars?

I was doing some testing with Mars and stumbled upon what
seemed like suboptimal text rendering. Because it was quite subtle
and I wanted to make sure there was an actual difference, I did a
little comparison between PDF and Mars rendering.
See this image. Can
you see a difference?
I'm still not sure whether there is an actual difference, but
I still somehow got the impression that the upper example (PDF) is
a little more polished then the lower one (Mars). Are different
rendering paths actually used? Will it remain that way?
My SVG for Mars was very simple:
<text font-size="10pt" x="20" y="20" fill="rgb(0,0,0)"
font-family="F0">aex</text>
The PDF was produced with MS Office 2007 and Microsofts Save
as PDF plugin (also at 10pts). The font is Gentium.

The difference *IS* subtle, but you're right -- there does
appear to be a perceptible difference between the two samples.
Without making an in-depth study, it's hard to say whether we
can do anything about this. Even though they're both opened in
Acrobat, the rendering path for a Mars document is *VERY* different
from the path for a PDF document, and many of the events along the
chain are out of the control of those of us writing the Mars
plugin. There are some text-quality issues that I'd like to take
care of in time for our next release, however; perhaps I'll be able
to address this particular issue at the same time.

Ugly text rendering in Safari 5.03 for windows

Text renders really ugly and some times unreadable in Safari.
Not all text but always the text in RSS feeds and the text in this forum.
It's too bold and looks like it is small text that has been scaled up without adding pixels.
Anyone else with same problem or anyone with a solution?

here's what it looks like:
http://dl.dropbox.com/u/2459424/safari.JPG

Java2D text rendering quality

Dear all,
I am currently trying to get high quality rendering for monochrome text, targeting epaper viewers. I draw strings into a BufferedImage, and display it on my LCD monitor in order to quickly check the rendering quality, before transferring it to epaper. I am encountering some disappointing surprises using Java2D, and cannot get a good output quality:
- TextAttribute.WEIGHT produces only 2 different renderings, regular or bold.
- Fonts appear very very light for sizes up to 17pt, and suddenly appear bold at 18pt+ sizes
I am working under Windows XP SP 2, with JDK 1.6.0. Here follows a small piece of code illustrating the second problem. When comparing output with Photoshop or Fireworks outputs, the results are really disapointing, and I am sure that I am missing something...
Thanks in advance for any help/tip.
Sincerely,
Jean-Marie
import javax.swing.*;
import java.awt.*;
import java.awt.font.FontRenderContext;
import java.awt.font.TextLayout;
import java.awt.font.TextAttribute;
import java.awt.image.BufferedImage;
import java.text.AttributedString;
public class TextRendering extends JPanel {
    private static final int WIDTH = 2000;
    private static final int HEIGHT = 8000;
    private static final int MIN_SIZE = 13;
    private static final int MAX_SIZE = 72;
    private static final int STEP = 1;
    private BufferedImage buf;
    public TextRendering() {
        setMinimumSize(new Dimension(WIDTH, HEIGHT));
        setPreferredSize(new Dimension(WIDTH, HEIGHT));
        buf = new BufferedImage(WIDTH, HEIGHT, BufferedImage.TYPE_BYTE_GRAY);
        Graphics2D g2d = (Graphics2D) buf.getGraphics();
        g2d.setColor(Color.WHITE);
        g2d.fillRect(0, 0, WIDTH, HEIGHT);
        g2d.setColor(Color.BLACK);
        g2d.setRenderingHint(RenderingHints.KEY_ANTIALIASING, RenderingHints.VALUE_ANTIALIAS_ON);
        g2d.setRenderingHint(RenderingHints.KEY_TEXT_ANTIALIASING, RenderingHints.VALUE_TEXT_ANTIALIAS_LCD_HRGB);
        g2d.setRenderingHint(RenderingHints.KEY_RENDERING, RenderingHints.VALUE_RENDER_QUALITY);
        g2d.setRenderingHint(RenderingHints.KEY_FRACTIONALMETRICS, RenderingHints.VALUE_FRACTIONALMETRICS_ON);
        // g2d.setRenderingHint(RenderingHints.KEY_TEXT_LCD_CONTRAST, 250);
        FontRenderContext frc = g2d.getFontRenderContext();
        Font f = new Font("Arial", Font.PLAIN, 24);
        int y = 20;
        for (int i = MIN_SIZE; i <= MAX_SIZE; i += STEP) {
            String s = new String(i + "pt- I would like to get a better rendering ! ");
            AttributedString attText = new AttributedString(s);
            attText.addAttribute(TextAttribute.FOREGROUND, Color.black);
            attText.addAttribute(TextAttribute.FONT, f.deriveFont((float)i));
            TextLayout textlayout = new TextLayout(attText.getIterator(), frc);
            textlayout.draw(g2d, 10, y);
            y += i + 10;
    public void paint(Graphics g) {
        Graphics2D g2d = (Graphics2D) g;
        g2d.drawImage(buf, 0, 0, null);
    public static void main(String[] args) {
        JFrame f = new JFrame("Text rendering demo");
        f.getContentPane().add(new JScrollPane(new TextRendering()), BorderLayout.CENTER);
        f.setSize (600, 800);
        f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        f.setVisible(true);
}

Of course, the same rendering problem can be observed with the more sophisticated "Font2DTest" example which can be found in the JDK samples: with the Arial font, the text becomes "semi-bold" starting from 18pt size, whereas it is very light for sizes up to 17pt.
Thanks again for any help.
Jean-Marie

Slow text rendering in KDE.

Similar Messages

Maybe you are looking for