Skip to main content
mandrill22
mandrill22
Inspiring
June 2, 2011
Question

FrameMaker Console data

  • June 2, 2011
  • 2 replies
  • 2823 views

What is the significance of the (8),(9) and (10) in the following console data? Do they relate to version numbers? What useful information, if any, can I get from this data?

MIF: "G:\ScannerDocuments\Framemaker\Robert\II6001520\II6001520h.mif" (8033): Value of Separation out of range (10).

MIF: "G:\ScannerDocuments\Framemaker\Robert\II6001520\II6001520h.mif" (16025): Value of Separation out of range (8)

MIF: "G:\ScannerDocuments\Framemaker\Robert\II6001520\II6001520h.mif" (6050): Value of Separation out of range (9)

I added some graphics in FM10, saved as a MIF and opened the file in FM8 (to save as a version 8 .fm file) but the graphics I added in FM10 won't display or distill (I get no warnings about missing graphics when I open the document in FM8, despite the gray boxes...object properties says the file is properly referenced.) Opening the same MIF file in 10 gives me the graphics back. What's happening here? Ihave tried both MIF7 and MIF10 with the same results.

    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    June 6, 2011

    mandrill22, just checking to clarify, you said:

    >> I added some graphics in FM10, saved as a MIF and opened the file in FM8<<

    >> I have tried both MIF7 and MIF10 with the same results.<<

    When you saved as MIF from FM10, I'm not 100% clear on whether your second comment quoted above means that you used the drop-down for the file type to specify what version #?

    And second, when you open the MIF again in FM10, do you get a dialog saying that the document is from a previous version?

    Also, are both your FM10 and any other FM version you're trying on the same O/S (and on the same service pack level of the O/S)? What O/S version(s) are you using?

    I'm asking these questions in order to help clarify whether FM10 is  correctly saving the MIF as an earlier version to start with, and/or whether there might be other platform-specific issues specifically with the graphics handling.

    Sheila

    mandrill22
    mandrill22Author
    Inspiring
    June 8, 2011

    Hello Shiela,

    I am using XP SP3 and both versions are on the same OS/machine, but other users get the same (plus more: numbering replaced by garbage etc.) translation errors.

    "When you saved as MIF from FM10, I'm not 100% clear on whether your second comment quoted above means that you used the drop-down for the file type to specify what version #?"

    I used the drop-down to specify MIF10 and when that didn't work I tried to save as MIF7. The file saves successfully in both instances and the MIF opens successfully in FM10. The problems start when opening either version MIF file in FM8. Some referenced graphics do not display and when i try to re-import them, I get the following error message.

    "The filter encountered an error and could not complete the translation"

    The only workaround is converting the JPEG graphic to to uncompressed format (BMP, TIFF etc.), and that is not really a good solution since we are talking about many graphics.

    Nadeem

    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    June 2, 2011

    I added some graphics in FM10 ...

    What graphics file format?

    Imported by reference, or copied into document?

    If color, RGB or CMYK model?

    mandrill22
    mandrill22Author
    Inspiring
    June 2, 2011

    rgb referenced, jpeg same as all the other 200 graphics

    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    June 3, 2011

    Not JPEG2000. Somehow that conversion (MIF to version 8) corrupts the image import filter. Once opened in FM8 it stops working properly.


    If there weren't quite so many of them, I'd suggest converting them all to EPS, which is probably the most stable FM import format.

    Should you decide to do it, also go back to the original PSDs (if saved) and re-save as EPS. We routinely keep the PSD masters at source resolution, with the final crop guides visible. We flatten, crop, re-size to 200 dpi, and save as EPS. It's then easy to [re]generate a modified image starting from maximum quality.

    JPEG is generally worth avoiding, both as an archival format, and as a Frame import format. If JPEG is all your camera emits, save a copy as something else right after camera download (PSD, DNG, TIFF or any other format that uses repeat-count, or no, compression), and use that as the edit and archival master.

    In addition to the version issues explored in this thread, JPEG always* has some level of lossy (curve-matching) compression in use. You get losses after editing the camera image even if saved at the full res. You get losses scaling (or just cropping and re-saving) it for import into frame. You can get more losses if print-to-PDF, Distiller or Acrobat Pro Optimize resamples it again.

    If your path is to critical color hardcopy, EPS also supports real CMYK that survives the GDI on all versions of Windows, including post-Vista editions with psuedo-CMYK support (that actually converts it to RGB and back).

    Plus, I really hate JPEG ringing-edge artifacts, but that's just me.

    ______

    * Some of the newer exotic JPEG variants may have less destructive/annoying compression, but they have the too-new versioning issue.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices