Skip to main content
Inspiring
February 13, 2025
Answered

FrameMaker hangs regularly

  • February 13, 2025
  • 5 replies
  • 2995 views

Hi,

With FrameMaker 2022 (v17), when editing a 750 pages document converted from a previous release, I have 2 problems:

 

1) At start, it says "At least one original filter used for graphics is not available......"

How can I find what graphic is missing or bad?

 

2) Regularly, Frame hangs for 30s. It's very disruptive, how can I find why and remedy to it?

I use an Intel 24 core, a GEN4 NVME SSD and 128GB  memory, so resources are not the problem.

 

Thanks in advance for any help.

Correct answer léandro_0776

léandro: I am using Gimp to read my .rast files, and convert to .jpg.

If they are all contone images (e.g. photos, color or B&W), that's fine. JPG uses curve-matching compression, which works for scan lines that describe curves through colorspace.
If any are line art, (2-tone) B&W, or have regions of flat (monotone) colors or shades, JPG is going to introduce "ringing" artifacts at edges. Something that uses repeat-count compression would be more suitable, such as PNG.


Well, I was wrong about the anchored frames.

After spending much time redoing them, that did not help.

So I took the advice gievn here to do a binary search.

I ended up with a completyl blank document that was still hanging.

I then (finally!) created a brand new document, imported all the settings of the old one, and than made a cut & paste of the content.

I ended up with the same document, but no more hang ups.

Just a corruped or too badly imported a long time ago file.

5 replies

frameexpert
Community Expert
Community Expert
February 13, 2025

Here is a utility script that may help you solve the "original filter" message. When you run it on an active document (File > Script > Run), it will write 3 pieces of information to the Console window (View > Panels > Console) for each imported-by-reference graphic:

 

  1. The file name of the image.
  2. The import filter base name.
  3. The import filter full name.

 

In general, the graphic's file extension should match the import filter base name. If it doesn't, that may reveal the problem. Here is how it can occur: You import a graphic and FrameMaker figures out the filter to use. You later create another graphic with a different format but with the same name as the original graphic. That will usually trigger the message you are seeing. Anyway, this script may help you figure out if there any mismatches like this.

 

All that said, you probably have images that were imported with an earlier version of FrameMaker and that import filter is no longer available in your current version.

 

main ();

function main () {

    var doc;
    
    doc = app.ActiveDoc;
    if (doc.ObjectValid () === 1) {
        processDoc (doc);            
    }
}

function processDoc (doc) {
    
    var graphic, file, importHint;
    
    graphic = doc.FirstGraphicInDoc;
    while (graphic.ObjectValid () === 1) {
        if (graphic.constructor.name === "Inset") {
            if (graphic.InsetFile !== "") {
                file = new File (graphic.InsetFile);
                importHint = graphic.ImportHint;
                Console (File.decode (file.name) + "\t" + 
                    importHint.substring (8, 12) + "\t" + 
                    importHint);
            }
        }
        graphic = graphic.NextGraphicInDoc;
    }
}
Inspiring
February 13, 2025

Thanks, that's interesting although I would have to look into it to know how to use it.

But as posed above, I figured out that (you are 100% right) that it's caused by old .rast files.

The display and print fine, so I'll forget about the warning: these are not causing the slow down, as posted above.

Inspiring
February 13, 2025

I finally got over being lazy, and used this script to change all the .rast files with JPEG ones converted with GIMP.

The error message does not happen anymore.

Thanks!

frameexpert
Community Expert
Community Expert
February 13, 2025

Are you working across a network? That can cause slow scrolling. One thing to try: choose View > Options and uncheck Graphics. This will hide the graphics in the document. See if that solves the scrolling problem.

Inspiring
February 13, 2025

No network problem. 

As I posted above:
I found the problem: some anchore frames created with an old FrameMaker version should show a box around the text inside, but do not. Removing these frames and reformatting solved it, but it's a lot of work, it hangs at every action.

Community Expert
February 13, 2025

"1) At start, it says "At least one original filter used for graphics is not available......"

How can I find what graphic is missing or bad?"

Try going to the folder where you store your graphics. Sort the folder by file type. If you have files of the type *.tif, *.tiff, *.bmp - they may be likely culprits, and you can try converting these file to *.png and relink them.

Regarding the document and the hanging problem... Is it ONE big fm file or is it a book with multiple chapters?

 

 

Bjørn Smalbro - FrameMaker.dk
Inspiring
February 13, 2025

I think it's because this doc was created a long time ago on Unix with .rast files. They do show, but trigger this warning.

I could convert them, but it's not worth the time just to supress this warning.

Dave Creamer of IDEAS
Community Expert
Community Expert
February 13, 2025

I had to look up what a .rast file was! Did FrameMaker ever import that file format? 

 

David Creamer: Community Expert (ACI and ACE 1995-2023)
Jeff_Coatsworth
Community Expert
Community Expert
February 13, 2025

#2 - is this happening with just one doc or all your docs? Is this a new install of FM 2022 (what point version are you on?)?

Inspiring
February 13, 2025

Just one doc, but I found the problem: some anchore frames created with an old FrameMaker version should show a box around the text inside, but do not. Removing these frames and reformatting solved it, but it's a lot of work, it hangs at every action.

Community Expert
February 13, 2025

Hi,

1 Does the message say which filter is affected?

When an image cannot be imported, FrameMaker will show a grey box instead.

You can create a PDF and flip through it manually to detect the grey boxes.

Or you could open the Inset pod (View | Panels | Inset) and check the type. There are "Image" and "Unresolved Image" and probably more. You can sort or filter the items in this list to find problem graphics.

 

2 What do you do, when FrameMaker hangs? Do you flip through the pages? Then I would guess that graphics are involved. What happens, when you do not display graphics (View | Options)? Does this happen as well?

Do you have the latest update installed? Can you check your update in Help | About?

Best regards, Winfried

Inspiring
February 13, 2025

1 - No, it just say there is one . I opened the Inset panel, it's very convenient, thanks for pointing it out.
The is no Unresolved. and going through each of them (it's really fast) displays an image every time.

The exact message is:

At least one original filter used for graphics imported by reference is not available, or the imported file's format has changed. An alternative filter may be used if the file is recognized as a graphic FrameMaker can import.

 

2 - Anything actually. For example for (View | Panels | Inset) just clicking on View did it.

I'll try without displaying graphics and get back to you. I don't have a specific way to trigger it, I'll just have to work a while and see if it happens or not.

 

Thanks.

Inspiring
February 13, 2025

That did not take long: PageDown triggered it.