JP2000348158A - Method and system for folder monitor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize an OPI(open prepress interface) system which performs monitor processing of picture folders in real time without being affected by other processings. SOLUTION: In an OPI daemon, a folder and picture monitor process and a picture conversion monitor process are independently processed as independent processes. The generation processing of a low-resolution picture which takes a long time is executed by starting a picture conversion process as an independent process from the picture conversion monitor process. That is, the folder and picture monitor process, the picture conversion monitor process, and the picture conversion process are independently processed in parallel. Thus, various monitor processings are performed in real time without waiting for the end of the generation processing of the low-resolution picture 20. Plural picture conversion processes may be simultaneously started to simultaneously execute generation processings of plural low-resolution pictures.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a folder monitoring method and a folder monitoring system, and more particularly, to an OPI system for performing an editing operation on low-resolution image data and replacing it with high-resolution image data at the time of output to perform a printing process. The present invention relates to a folder monitoring method and a folder monitoring system used for a folder.

[0002]

2. Description of the Related Art In the printing industry, DTP (DeskTop Publis), which edits and prints documents using a personal computer or the like, has conventionally been used.
hing) is widely used. In DTP, editing work is performed on an editing workstation to determine the layout of images, texts, line drawings, and the like, using editing software, and the result is generally converted to PS data (PostScript data).
Output in the page description language called ipt). Output PS
The data is transferred via RIP (Raster Image P
rocessor) sent to the workstation. In the RIP, the PS data is analyzed to generate page-based image data. By transmitting this image data to the output device, an output (printed matter) is obtained.

Usually, in order to obtain a high-quality printed matter, tens to hundreds of MB of image data (original image data) is used. When this original image data with a large amount of data is used when editing with the editing software, the burden on the editing computer is large, the processing capacity is reduced just by laying out, and the editing work cannot be performed comfortably. there were.

[0004] Also, from the editing workstation, the PS
It takes a very long time to output data, and depending on the type of workstation, there is a case where other operations cannot be performed during PS data output, resulting in poor work efficiency. Furthermore, this PS data is transferred from the editing workstation to the R
When transmitting PS data to the IP workstation, the data transmission amount (communication traffic amount) on the network may increase, and the data transmission processing efficiency of the entire network system may be reduced.

For this reason, the original image data (hereinafter, referred to as
The display image data (hereinafter, referred to as a “low-resolution image”) is generated by thinning out the “high-resolution image”, and editing is performed using the low-resolution image, and is switched to a high-resolution image at the stage of the PS data. OPI to output to RIP
(Open Prepress Interface) system has been widely introduced.

FIG. 19 shows a general OPI (so-called “Aldu
s-OPI ") system.

As shown in FIG. 19, an editing workstation (W / S) 300 has a high resolution image 302 (TIF).
Low-resolution image 3 generated by thinning out F format)
The editing operation is performed by using editing software (so-called DTP software) using the 04 (TIFF format). When the user issues a print instruction and outputs the PS data 306, the editing workstation 30
0 is the low-resolution image 3 instead of the low-resolution image 304
Information (file name, size, etc.) relating to the high-resolution image 302 corresponding to 04 is embedded in the PS data 306 as a comment sentence 308 and output.

[0008] The outputted PS data 306 is transmitted to the OPI server 310 via a network. OPI
In the server 310, the comment sentence 3 in the PS data 306
08 is analyzed to generate PS data 312 into which the high-resolution image 302 is inserted. This PS data 312 is transferred to RIP3
By transmitting the image data to the printer 14, it is possible to output (print) a high-resolution image.

As described above, in the OPI system, an editing operation is performed using a low-resolution image having a small amount of data (usually about 1 MB), so that the user can perform the editing operation comfortably and can perform the editing operation from the editing workstation. Since no image data is output when the PS data is output, the waiting time can be reduced.

Generally, in the OPI system, when a high-resolution image is stored in a predetermined folder (hereinafter, referred to as an "image folder"), a low-resolution image for display used for editing work is automatically generated. It has become. More specifically, as shown in FIG. 20, the inside of the image folder is monitored (step 320), and it is determined whether there is a high-resolution image for which a low-resolution image needs to be generated (step 322). If it is necessary to generate a resolution image (Yes at Step 322), a low-resolution image generation process is executed (Step 324).
The process is repeatedly performed until the I system is terminated (Yes in step 326).

[0011]

However, in the prior art, since the folder monitoring process and the low-resolution image generation process are performed successively (in series), once the low-resolution image generation process is started, Until this processing is completed, it is not possible to proceed to the monitoring processing of the image folder.

For example, even if an attempt is made to generate a new low-resolution image (new low-resolution image) during the generation of a low-resolution image, the processing for generating the new low-resolution image is not performed. It does not start until the process ends.

In general, the generation of a low-resolution image takes a long processing time, and during this time, it appears to the user that nothing has been processed.
In some cases, the OPI system is misunderstood, such as when the system is in an unprocessable state (so-called freeze).

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and a folder monitoring method and a folder monitoring method for realizing an OPI system for monitoring an image folder in real time without being affected by other processes. The purpose is to provide a system.

[0015]

In order to achieve the above object, according to the present invention, low resolution image data for editing is generated from high resolution image data, and the high resolution image data and the high resolution image data are generated. A folder monitoring method used in an OPI system for storing low-resolution image data in a predetermined folder, performing editing work using the low-resolution image data at the time of editing, and switching to high-resolution image data at the time of output, A monitoring process of monitoring a predetermined folder, grasping the correspondence between the high-resolution image data and the low-resolution image data, and determining whether or not it is necessary to execute a low-resolution image data generation process, The method is characterized in that the low-resolution image data generation processing is continuously executed irrespective of the execution.

According to the first aspect of the present invention, the folder monitoring process is continuously executed regardless of whether or not the low-resolution image data generation process is being executed. Thus, even when the low-resolution image generation processing is started, the folder monitoring processing can be executed without waiting for the end of the low-resolution image data generation processing.

The method of executing the folder monitoring process independently of the low-resolution image data generation process is not particularly limited in the present invention. For example, the folder monitoring processing and the low-resolution image data generation processing are alternately switched and executed at predetermined time intervals (so-called parallel processing) by the same arithmetic unit such as a CPU, so that the folder monitoring processing is performed on the low-resolution image. It may be independent of the data generation processing. Further, an arithmetic unit for executing the folder monitoring process is provided separately from the arithmetic unit for executing the low-resolution image data generating process, and the folder monitoring process and the low-resolution image data generating process are simultaneously executed in parallel (so-called parallel processing). Process), the folder monitoring process may be made independent of the low-resolution image data generation process.

According to a second aspect of the present invention, in the first aspect of the present invention, during the execution of the low-resolution image data generation processing, the low-resolution image data and the monitoring processing are executed in a time-division manner. It is characterized by:

According to the second aspect of the present invention, during execution of the low-resolution image data generation process, the monitoring process and the low-resolution image data generation process are performed in a time-division manner, that is, alternately at predetermined time intervals. It is switched and executed. This allows
Even in a general (general-purpose) computer having only one mounted CPU, the monitoring process and the low-resolution image data generation process are performed by sharing the CPU, and the low-resolution image data generation process is being executed. The monitoring process can be continuously executed regardless of the monitoring process.

That is, even if the low-resolution image generation processing is started, the folder monitoring processing can be executed without waiting for the end of the low-resolution image data generation processing.
The system can be realized by a general (general-purpose) computer without using a special computer.

According to a third aspect of the present invention, in the first or the second aspect of the present invention, the low-resolution image data generation processing is performed while limiting the simultaneous execution of the low-resolution image data generation processing for a predetermined number or more. A start management process for starting the generation process is continuously performed regardless of whether the monitoring process and the low-resolution image data generation process are being performed.

According to the third aspect of the present invention, the low-resolution image data generation processing is started by the start management processing while managing not to execute a predetermined number or more of low-resolution data generation processing simultaneously. . The start management process is continuously executed regardless of whether the folder monitoring process or the low-resolution image data generation process is being executed. Accordingly, it is possible to prevent the load due to the execution of the plurality of low-resolution image generation processes from becoming excessive and affecting other processes (processing stagnation or the like) beforehand, and to always perform the monitoring process in real time.

The method of executing the start management process independently of the folder monitoring process and the low-resolution image data generation process or the means therefor is not particularly limited in the present invention as in the first aspect.

According to a fourth aspect of the present invention, in the third aspect of the invention, it is determined that the start management process needs to execute the low-resolution image data generation process in the monitoring process. When a new low-resolution image data generation process is started, if a predetermined number of the low-resolution image data generation processes are being executed, the process waits for the start of the new low-resolution image data generation process. It is characterized by:

According to the fourth aspect of the present invention, when a predetermined number of low-resolution image data generation processes are already being executed, the start of a new low-resolution image data generation process is waited for, and the start is started. After the state becomes possible (after the number of low-resolution image data generation processes being executed becomes less than a predetermined number)
The process of generating new low-resolution image data is started. Thus, the monitoring process can always be performed in real time, and when it becomes possible to start the process, the waiting low-resolution image data generation process can be started immediately.

According to a fifth aspect of the present invention, in the third or fourth aspect of the present invention, the monitoring process is repeatedly executed at a shorter time interval than the start management process.
It is characterized by:

According to the fifth aspect of the present invention, the monitoring process and the start management process are each repeatedly executed, and the monitoring process is executed at shorter time intervals than the start management process. Thereby, for example, even when the monitoring processing and the start management processing are performed in parallel by sharing one arithmetic unit, the monitoring processing can be performed frequently, and it is possible to prevent the OPI system from being misunderstood as a malfunction. it can.

According to a sixth aspect of the present invention, low-resolution image data for editing is generated from high-resolution image data, and the high-resolution image data and the low-resolution image data are stored in a predetermined folder. A folder monitoring system used in an OPI system for performing an editing operation by using the low-resolution image data at the time and replacing the high-resolution image data with the high-resolution image data at the time of output. A monitoring process of grasping the correspondence between the low-resolution image data and determining whether it is necessary to execute the low-resolution image data generation process, regardless of whether the low-resolution image data generation process is being performed. It is characterized by having monitoring means for continuously executing.

According to the sixth aspect of the present invention, the monitoring means continuously executes the folder monitoring processing irrespective of whether or not the low-resolution image data generation processing is being executed. Thus, even when the low-resolution image generation processing is started, the folder monitoring processing can be executed without waiting for the end of the low-resolution image data generation processing.

The means for executing the folder monitoring process independently of the low-resolution image data generation process is not particularly limited in the present invention. Similarly to the first aspect, for example, the same CPU or other arithmetic means alternately performs folder monitoring processing and low-resolution image data generation processing at predetermined time intervals (so-called parallel processing).
The folder monitoring process may be independent of the low-resolution image data generation process. Further, an arithmetic unit for executing the folder monitoring process is provided separately from the arithmetic unit for executing the low-resolution image data generating process, and the folder monitoring process and the low-resolution image data generating process are simultaneously executed in parallel (so-called parallel processing). Process), the folder monitoring process may be made independent of the low-resolution image data generation process.

According to a seventh aspect of the present invention, in the invention according to the sixth aspect, the low-resolution image data generation process is started while limiting a predetermined number or more of the low-resolution image data generation processes simultaneously. Further comprising a start management unit that continuously executes the start management process, regardless of whether the monitoring process and the low-resolution image data generation process are being performed.
It is characterized by:

According to the seventh aspect of the present invention, the start management unit continuously executes the start management process irrespective of whether or not the folder monitoring process and the low-resolution image data generation process are being performed. You. In the start management process, the generation process of the low-resolution image data is started while the generation process of the predetermined number or more of the low-resolution data is managed so as not to be simultaneously executed. Accordingly, it is possible to prevent the load due to the execution of the plurality of low-resolution image generation processes from becoming excessive and affecting other processes (processing stagnation or the like) beforehand, and to always perform the monitoring process in real time.

The method or means for executing the start management process independently of the folder monitoring process and the low-resolution image data generation process is not particularly limited in the present invention as in claim 6.

[0034]

Next, an example of an embodiment according to the present invention will be described in detail with reference to the drawings.

(Schematic Configuration of Entire System) FIG. 1 shows a schematic configuration of a system in this embodiment. As shown in FIG. 1, an editing workstation 10 as a client device and a server 12 as a server device include:
They are mutually connected via a network 16 and constitute a client server system 18. Further, a printer 14 is also connected to the network 16 as an output device. The editing workstation 10, the server 1
2. The number of printers 14 is not particularly limited (in the present embodiment, three, one, and one, respectively), and may be any number.

The editing workstation 10 performs an editing operation for determining the layout of images, texts, line drawings, etc., and can transmit PS data to the server.

The server 12 automatically converts high-resolution image data (hereinafter simply referred to as “high-resolution image”) to low-resolution image data in EPS (AliasEPS) format (hereinafter simply referred to as “low-resolution image”). It can be generated. This low-resolution image (AliasEPS) can be used for editing work in the editing workstation 10.

The server 12 generates PS data including a high-resolution image based on the PS data from the editing workstation 10, and generates a P-data including the high-resolution image.
Image data in page units is generated based on the S data and transmitted to the printer 14. The printer 14 executes printing based on the image data and outputs a printed matter.

(Summary of low-resolution image in AliasEPS format) Next, a low-resolution image in EPS format generated by thinning out high-resolution images in the server 12 and used for editing will be described.

The low-resolution image 20 of this EPS format
As shown in FIG. 2, information on the high-resolution image of the source is added as a comment 24 together with low-resolution image data (hereinafter, referred to as “thinned-out image”) 22 generated by thinning out the high-resolution image. (The EPS format to which the comment 24 regarding this high-resolution image is added is defined as “AliasEPS”).

In the comment 24, specifically, the file name of the high-resolution image and the path of the high-resolution image
The folder names of the PI directory 90 and the OPI folder 70, and the upper and lower hierarchical relations), the folder ID of the folder storing the high-resolution image (the OPI folder 70 described later), and the format of the high-resolution image (EPS, TIF
F, JPEG, GIF, PICT, etc.) are described. In addition, the comment 24 also describes the start / end position of the low-resolution image and identification information indicating that the image is data in the AliasEPS format.

The comment 24 is used in the OPI filter 106 to be described later.
Anything other than 06 is ignored. Therefore, the low resolution image 20 in the AliasEPS format can be handled as normal EPS format data by the application software. For example, when the low-resolution image 20 is displayed by the editing software, only the thinned image 22 is visualized and displayed. Also, even if the low-resolution image 20 (or PS data including the low-resolution image 20) is converted into image data by RIP and output to the printer 14, only the thinned image is printed without printing the comment 24. You.

(Detailed Configuration of Editing Workstation)
FIG. 3 shows a detailed configuration of the editing workstation 10.

As shown in FIG. 3, the editing workstation 10 has a CPU 30, a ROM 32, a RAM 3
4, HDD (Hard Disk Drive) 36, I / O port 4
0. The CPU 30 and the ROM
32, RAM 34, HDD 36, and I / O port 40
They are interconnected via a system bus 42.

The ROM 32 and the HDD 36 store various programs 44 such as an OS, editing software, and image processing software. The OS includes a kernel section for executing tasks and managing resources, and a network OS for controlling systems between networks (for example, AppleShare for Macintosh and Netware386 for Windows).
Or a shell that controls the basic operation and appearance of the OS (for example, M
acintosh Finder, Windows Explorer) and GU
A user interface such as I (Graphical User Interface) is included.

That is, the editing workstation 10
For example, even if the file system differs from that of the server 12, the user can mount and use the disk (HDD or the like) of the server 12 as a remote file system without being aware of the difference by the network OS. Under the network OS, a client-server system is realized between the editing workstation 10 (client) and the server 12, so that processing requests and data transmission / reception can be performed with each other.

Further, the file system on the server 12 side can be displayed in a shell, and the editing workstation 10 can associate the hierarchical structure of folders and files on the server 12, the names of folders and files, and the folders and files. Icon, etc., which are displayed. The display 10 on which the shell is displayed
By operating the mouse or keyboard (icon click, drag, drop, etc.) in the GUI environment while referring to D (see FIG. 1), the file system on the server 12 side is operated (copying and deleting folders and files). , Move, rename, create new, etc.).

The HDD 36 also stores original image data 46 for printing (hereinafter referred to as “high resolution image”) input by a scanner or the like (not shown) and a low resolution image 20 (AliasEPS) for editing. Is available. This low-resolution image 20 is usually used for editing work in the editing workstation 10. When the user issues a print instruction for the edited page, the PS data A including the low-resolution image 20 is output (see FIG. 7).

More specifically, the editing workstation 10
The user operates the mouse or keyboard (not shown) using the editing software in the program 44 and in the GUI environment while referring to the display 10D, thereby determining the layout of images, texts, line drawings, etc. Do the work.

The user of the editing workstation 10 can use the image processing software or the like in the program 44 to edit the high-resolution image 46 if necessary.
Various types of image processing such as enhancement processing and conversion processing can also be performed. Also, as described above, the server 12 can be mounted on the disk, and the high-resolution image 46 can be copied or moved to a folder in the disk on which the server 12 is mounted.
The low-resolution image 20 can be copied from the disk on the side and stored in the HDD 36.

(Detailed Configuration of Server) FIG.
2 shows a detailed configuration.

The server 12, as shown in FIG.
PU50, ROM52, RAM54, HDD56, I /
An O port 60 is provided. In addition, these CPU5
0, ROM 52, RAM 54, HDD 56, and I / O port 60 are mutually connected via a system bus 62.

Various programs 64 are stored in the ROM 52 and the HDD 56. The program 64 includes an OS (including a network OS and a user interface in addition to the kernel, similarly to the editing workstation 10 described above), and an O described later.
A program for causing the PI 100 and the RIP 102 to function is included. Also included is an image conversion program 114 (see FIG. 8) for generating low-resolution image data 20 (AliasEPS) by thinning out high-resolution image data.
The image conversion program 114 is, for each high-resolution image data format (EPS, TIFF, JPEG, DCS, PICT, etc.), an executable format (generally “* .exe ”Indicates a file, and“ * ”indicates an arbitrary character or character string.)
It is prepared in.

The HDD 10 stores an image database 6 for organizing and storing high-resolution images and low-resolution images.
6. The OPI database 68 is stored.

(Summary of Image Database and OPI Database) FIG.
As shown in FIG. 6, a plurality of OPI folders 70 can be provided. Each OPI folder 70 includes a high-resolution image folder 72, a low-resolution image folder 74, and a status folder 76.

The high-resolution image folder 72 stores the high-resolution image 78 as the original image data, and the low-resolution image folder 72 stores the low-resolution image 20 generated by thinning out the high-resolution image 78. It has become. In the status folder 76, a log file 80 indicating the generation status of the low resolution image 20 is stored.

More specifically, in the log file 80, messages (start, processing, successful completion, failed completion, error information) issued from the system in the low-resolution image generation processing are described. . The log file 80 is generated corresponding to each of the high-resolution images 78 in the high-resolution image folder 72.

If necessary, sub-folders 82 and 84 are located in the lower hierarchy of the high-resolution image folder 72, the low-resolution image folder 74, and the status folder 76, respectively.
A high resolution image 78, a low resolution image 20, and a log file 80 can be stored in these folders, respectively.

Each OPI folder also stores an ID file 110 in which a folder ID described later is described. By this folder ID, each O
The PI folder can be uniquely identified.

In the upper hierarchy of the OPI folder 70, the OP
An OPI directory 90 is provided as a folder for managing the I folder 70. The user
An arbitrary folder can be set in the OPI directory 90 by using a setting tool (prepared as a tool of the OPI 100 described later) prepared in advance on the server 12 side. OPI described later
100 operates in a file system under the OPI directory 90. In the OPI database 66, the folder set in the OPI directory 90 is created as if the OPI root directory 88
It will be treated as if it were provided below.

When the file system of the server 12 is mounted from the editing workstation 10 to use the function of the OPI 100, the root directory 88 is referred to as a top directory. The user can newly create, delete, rename, copy, move, etc. the OPI folder 70 from the editing workstation 10 side.

The OPI database 68 contains the OPI 10
The location path of the folder set in the OPI directory 90 is stored as a management target folder (OPI config folder) by 0. That is, when the OPI directory 90 is set by the user using the setting tool, the path of the folder is registered.

The OPI database 68 stores each O
OPI folder 7 provided under PI directory 90
A folder name of 0 and a folder ID are also stored. Therefore, from the OPI database 68,
The location paths, folder names, and folder IDs of all the OPI folders 70 can be checked.

The OPI database 68 stores a table that associates each image format (EPS, TIFF, JPEG, DCS, PICT, etc.) with the image conversion program 114 (executable format). Table 1 shows an example of this table.

[0065]

[Table 1]

An image conversion program for a plurality of resolutions (72 dpi, 144 dpi, etc.) is prepared so that a low-resolution image 20 of a desired resolution (thinning-out) can be obtained as a desired low-resolution image. The table may correspond to the image format, the resolution, and the image conversion program 114.

The OPI database 68 also stores search conditions (search with priority on folder ID / search with priority on folder path / search only with file name) which will be described later. The user can use a setting tool (OPI 10 described later) prepared in advance on the server 12 side.
0 is provided as a tool for the search).

(Server Function) As shown in FIGS. 6 and 7, the server 12 converts the PS data A generated by editing using the low resolution image into the PS data including the high resolution image, as shown in FIGS. OPI100 to switch to B
And RIP1 for converting PS data B into image data
02 is to function. Thus, O
By providing both the PI 100 and the RIP 102 in the server 12, the editing workstation 10
In the process of transmitting the PS data to the IP 102, there is no network transfer load due to the high-resolution image.

The OPI 100 can operate the OPI database 68 and the image database 66 by using a GUI environment (hereinafter simply referred to as “GUI”) 120. For example, the user of the server 12 can perform various settings of the OPI database 68 by operating a keyboard and a mouse (not shown) under the GUI 120. When the file system of the server 12 is mounted from the editing workstation 10, various settings of the OPI database 68 can be made from the editing workstation 10.

The OPI 100 includes an OPI daemon 104 which automatically operates in the background while the OPI is running, and an OPI filter 106 which operates when the PS data A is received from the editing workstation 10. ing. Hereinafter, the function of the OPI daemon 104 and the OPI filter 106 will be described in detail.

(OPI daemon) OPI daemon 104
Are connected to an image database 66 and an OPI database 68.

The image database 66 can also be connected from the editing workstation 10 side. More specifically, for example, the high-resolution image 46 stored on the editing workstation 10 side by the user.
To the high-resolution image folder 72 in the image database 66 (a high-resolution image 78 is generated in the high-resolution image folder 72), and conversely, the low-resolution image in the low-resolution image folder 72 in the image database 66. 20 can be copied to the editing workstation 10 side.

FIG. 8 shows an outline of the processing performed by the OPI daemon 104. The OPI daemon 104 is located in the image database 66,
The inside of the I directory 90 is always monitored (hereinafter, this process is referred to as “folder & image monitoring process”).

In the folder and image monitoring process, if there is a folder requested to be managed by the OPI 100, the OPI daemon 104 registers the folder in the OPI database 68. (Hereinafter, this process is referred to as “folder monitoring process”).

More specifically, as shown in FIG. 9, when a user copies a predetermined file (hereinafter, referred to as an “authentication file”) 108 into a newly created folder 70A, a folder management request is issued. Is being done. In the OPI daemon 104,
Monitoring under the OPI directory 90, the authentication file 1
08 is checked to determine that the folder 70A in which the authentication file 108 is stored is a folder for which management is requested. The path of the folder 70A in which the authentication file 108 is stored and a unique folder ID for identifying the folder 70A are registered in the OPI database 68. An ID file 110 describing the folder ID is generated in the folder 70A in which the authentication file 108 is stored, and the authentication file 108 is deleted.

In the OPI 100, the folder 70A registered in the OPI database 68 and assigned with the ID file 110 is managed as the OPI folder 70. Further, the user can arbitrarily create the OPI folder 70 by creating a new folder under the OPI directory 90 and copying the authentication file.

The OPI daemon 104 generates a high-resolution image folder 72, a low-resolution image folder 74, and a status folder 76 in the OPI folder 70. In the OPI 100, only the contents in the high-resolution image folder 72, the low-resolution image folder 74, and the status folder 76 are used for processing, and the OPI folder 7
The other areas in 0 are not used. That is, other areas of the OPI folder are:
The user can use it freely. For example, the OPI folder 70
, Or under the OPI folder 70, and data (document files, etc.) used for editing work can be stored.

Thus, for example, the OPI folder 70 is created for each project or each month, and the high-resolution image 78, the low-resolution image 20, and other related files (document files, etc.) are collected together for each project or each month. Can be managed.

The OPI daemon 104 executes the OPI database 68 in the folder and image monitoring process.
If there is an unnecessary image in the OPI folder 70 registered in the
When it is necessary to generate 0, a low-resolution image generation job is created and registered in the low-resolution image generation job queue 112 (hereinafter, this processing is referred to as “image monitoring processing”). .

More specifically, as shown in FIG.
High-resolution image folder 72 in the same OPI folder 70
And the high-resolution image 78 stored in the low-resolution image folder 74 and the low-resolution image 20, respectively, and create a low-resolution image generation job for the high-resolution image 78 in which the corresponding low-resolution image 20 does not exist. It is supposed to.

Further, even when the generation date and time of the corresponding low resolution image 20 is older than the generation date and time of the high resolution image 78, a low resolution image generation job for the high resolution image 78 is created. . That is, when some change is made to the high-resolution image 78 after the low-resolution image is generated, even if the low-resolution image 20 exists, the high-resolution image 78 is thinned out again to obtain the low-resolution image 2.
A low-resolution image generation job is generated so as to generate 0.

Further, for the low resolution image 20 in which the corresponding high resolution image 78 does not exist, the low resolution image 20 is deleted.

The OPI daemon 104 refers to the low-resolution image generation job queue 112 at predetermined time intervals (hereinafter, this process is referred to as an “image conversion monitoring process”). In the image conversion monitoring process, if there is a low-resolution image generation job waiting to be executed in the low-resolution image generation job queue 112, the low-resolution image generation job is extracted from the low-resolution image generation job queue 112, and the low-resolution image generation job The image conversion process corresponding to the job is started. At this time, in order to prevent an excessive load on the server 12 and stagnation of other processes, the number of activated image conversion processes is also managed so that a predetermined number or more of image conversion processes are not activated.

In the image conversion process, the format (EPS, TIFF, JPEG, DCS, P) of the high-resolution image 78 is referred to by referring to the correspondence table (see Table 1) in the OPI database 68.
An image conversion program 114 corresponding to (ICT or the like) can be selected and activated. When the image conversion program 114 is started, the low-resolution image 20 in the AliasEPS format is generated from the high-resolution image 78.

Although the present invention does not limit the file name of the generated low-resolution image 20 in particular, in the present embodiment, as an example, the generated low-resolution image 2
0 is automatically given a file name obtained by adding "s.eps" to "the file name excluding the extension part of the high-resolution image 78". For example, a high-resolution image 78
Is "imageA.eps", the generated low-resolution image 20 is given a file name of "imageAs.eps". The generated low-resolution image 20 is stored in a high-resolution image folder 72 in which a high-resolution image 78 is stored.
Low-resolution image folder 7 in the OPI folder 70
4 is stored. Note that the generation date and time of the corresponding low resolution image 20 is older than the generation date and time of the high resolution image 78, and if the low resolution image 20 is generated again, the newly generated low resolution image 20 is older. Since the same file name as that of the low resolution image 20 is given, the file is automatically updated (overwritten) with the newly generated low resolution image 20.

The OPI daemon 104 generates a log file 80 at the same time that the generation of the low-resolution image is started. Also, the OPI daemon 104
The file name of the log file 80 is changed according to the generation state of the low-resolution image 20, and a comment indicating the processing state (start, processing, successful completion, failure end, error information) is included in the log file 80. It is written.

Although the present invention does not particularly limit the file name of the log file 80, in the present embodiment, as an example, during generation of a low-resolution image (during processing), “XX” is used.
X.continue "," XXX.complete "when the generation of the low-resolution image is completed (successful termination), and" XXX.complete "when the generation of the low-resolution image fails due to some abnormality (failed termination).
"failed", the file name of the log file 80 is changed.

Note that "XXX" indicates an arbitrary character or character string, and the same character string as the character string excluding the extension in the file name of the high-resolution image 78 is automatically added. I have. For example, if the file name of the high-resolution image 78 is “imageA.eps”, the log file 80 is “imageA.continue” during low-resolution generation, “imageA.complete” when low-resolution image generation is completed, If the generation of the low-resolution image fails, the file name is "imageA.failed".

In the GUI 120, the extension of the log file 80 (“continue”, “complete”, “fail”
ed "), the icons 122 having different designs
(See icons 122A, 122B, and 122C in FIG. 11) are associated in advance. Therefore, when the log file 80 is displayed on the shell, the appearance of the icon 122 is changed according to the change in the file name, that is, according to the generation status of the low-resolution image 20 (processing / successful end / failure end). It is changing. The extension of the log file 80 (“continue”, “complete”, “faile
d)), the icon 12 which changed the color instead of the design
2 according to the state of generation of the low-resolution image 20,
The color of the icon 122 of the log file 80 may be changed.

When the file system of the server 12 is mounted from the editing workstation 10, the user displays the shell of the server 12 on the display 10D of the editing workstation 10, and displays the icon of the log file 80. 122 can also be confirmed.

The generated low-resolution image 20 is stored in a low-resolution image folder 74 under the OPI folder 70 in which the high-resolution image 78 of the generation source is stored. The log file 80 is stored in the status folder 76 under the OPI folder 70 in which the high-resolution image 78 of the generation source is stored.

For example, when performing a layout operation of a newly generated high-resolution image 78 by reading with a scanner or the like, or performing image conversion processing, the user must input the high-resolution image 78 as shown in FIG. OPI daemon 104 is simply copied to high-resolution image folder 72.
Thus, the low-resolution image 20 can be automatically obtained. For details, see the OPI daemon 104
The high resolution image 78 without the corresponding low resolution image is recognized in the image monitoring process according to the first embodiment, a low resolution image generation job for the high resolution image 78 is generated, and the low resolution image is generated in the image conversion monitoring process. The generation job is executed, and the low-resolution image folder 7
4, a low resolution image 20 is generated. At this time, a log file corresponding to the high-resolution image is also generated, and its file name and icon 1 are set according to the generation state of the low-resolution image.
22 changes, so that the user can confirm the generation status.

(OPI Filter) On the other hand, the OPI filter 106 is connected to the image database 66 (see FIGS. 6 and 7). The OPI filter 106 includes:
The PS data A from the editing workstation 10 is input.

The OPI filter 106 analyzes the PS data A from the editing workstation 10 and
When the low resolution image 20 (AliasEPS) is included in the data A, the image database 66 is searched for a high resolution image 78 corresponding to the low resolution image 20. Note that this search is selectively performed according to search conditions set by the user stored in the OPI database 68 (search with priority on folder ID / search with priority on folder path / search only with file name). The ID of the folder storing the high-resolution image 78 described in the comment 24 and the location path (OPI directory 90)
And the name of the OPI folder 70 and the relationship between the upper and lower layers) or the file name of the high-resolution image 78. Note that the search may be performed using the folder name of the OPI folder 70 instead of the location path.

The OPI filter 106 replaces the low-resolution image 20 (AliasEPS) in the PS data with the searched high-resolution image 78, and generates PS data B including the high-resolution image. (Hereafter, like this
The OPI method for replacing image data in the AliasEPS format is called “AliasEPS-OPI method”). At this time, if the high-resolution image 78 in the image database 66 corresponding to the low-resolution image 20 is in the EPS (DCS is acceptable) format, the low-resolution image 20 and the high-resolution image 78 in the PS data are simply replaced. It has become. The high-resolution image 78 in the image database 66 corresponding to the low-resolution image 20 has a format other than the EPS format (TIFF, JPEG, PIC
T), the high-resolution image 78 is converted into the EPS format to generate a high-resolution image 78A, and the high-resolution image 78A is replaced with the low-resolution image 20 in the PS data.

Here, since the EPS format data is self-contained PS data, the exchange of the EPS format data in the PS data can be performed without affecting other parts of the PS data. .
Therefore, switching between the low-resolution image 20 and the high-resolution image in the PS data can be performed simply by changing the low-resolution image 20 (AliasEPS) without changing the description of the other parts of the PS data.
And high-resolution image (EPS format high-resolution image 78
Alternatively, it can be performed simply by replacing the high-resolution image 78A).

The OPI filter 106 is not the low-resolution image 20 from the editing workstation 10,
P containing comment 308 about high resolution image
When the S data is received (that is, PS data of the Aldus-OPI system, see FIG. 19), the comment 308 is analyzed, a corresponding high-resolution image is searched, and the PS data is converted so that the high-resolution image is included. It can be rewritten. That is, the OPI filter 106
It can support both the dus-OPI system and the AliasEPS-OPI system. Further, the OPI filter 106 transmits the P instructed to not execute the image replacement processing.
When the S data A is received, the received PS data A can be output as it is without performing the switching process.

The PS data B including the high-resolution image 78 (or 78A) generated by the OPI filter 106 is sent to the RIP 102. RI
In P102, image data in page units is generated based on the PS data B. This image data is transmitted to the printer 14 and the printer 14
Printed by. Accordingly, printing is performed with a desired layout and based on the high-resolution image 78 in the image portion.

(Operation) Next, as an operation of the present embodiment, various formats (EPS, TIFF, JPEG, DCS, PICT,
Etc.) from the high-resolution image of the AliasEPS format, and prints by performing editing work using the generated low-resolution image (that is, AliasEPS).
-OPI method) will be described with reference to FIG.

First, the user inputs an OP on the server 12 side.
In the I database, specifically, the root directory 88
The high-resolution image 78 is copied to the high-resolution image folder 72 of the OPI folder 70 in the lower hierarchy.

In the server 12, the high resolution image 78 is automatically thinned out by the OPI daemon 104 and the AliasE
A low-resolution image 20 in the PS format is generated. The low-resolution image generation processing by the OPI daemon 104 will be described later in detail.

The user operates the editing workstation 10
On the side, the editing work is performed using the editing software. At this time, the low-resolution image 20 (AliasEPS) generated by the server 12 is used instead of the high-resolution image 78 to determine the layout of the image. When the editing operation is completed and the user issues a print instruction for the edited page, the editing workstation 10 displays the low-resolution image 20 (Alia).
sEPS) is output to the server 12.

In the server 12, the received PS data A is analyzed by the OPI filter 106.
The comment 24 of the low-resolution image 20 (AliasEPS) is analyzed, and the low-resolution image 20 (AliasEPS) in the PS data A is converted into a high-resolution image 78 (or 78A) in the EPS format corresponding to the low-resolution image 20 (AliasEPS). To generate PS data B.

The generated PS data B is passed to the RIP 102. In the RIP 102, the high-resolution image 78
(Or 78A), the page-based image data is generated based on the PS data B.

The server 12 transmits the image data generated by the RIP 102 to the printer 14. The printer 14 performs printing based on the received image data. As a result, a printed matter having a desired layout and an image portion printed based on the high-resolution image 78 is output.

By the way, during the start of the OPI, in the background, the OPI daemon 104 executes the “monitoring process” of the present invention so that the process of generating the OPI folder 70 and the process of generating the low-resolution image 20 are performed smoothly. The folder & image monitoring process and the image conversion monitoring process as the “start management process” of the present invention are independently executed as separate processes. Hereinafter, processing of the folder & image monitoring process and the image conversion monitoring process will be described.

(Folder & Image Monitoring Process) FIG. 12 shows a processing flow of the folder & image monitoring process.

As shown in FIG. 12, in the folder and image monitoring process, the folder monitoring process shown in FIG.
At 02, the image monitoring process shown in FIG. 14 is performed. Thereafter, in step 204, the end of the OPI 100 is determined. When the process of the OPI 100 is continued (negative determination), the process returns to the step 200. That is, the OPI daemon 104 repeatedly executes the folder monitoring process and the image monitoring process at all times until the OPI 100 is started up (Yes at Step 204).

In the folder monitoring process, as shown in FIG. 13 (see also FIG. 9), first, in step 210, the folder name of the monitoring target (OPI config {folder}) from the OPI database 68, that is, the OPI directory 90
Is obtained.

Next, in step 212, each folder to be monitored (O for which the folder name
When the folder in the PI directory 90 is searched and the authentication file 108 is confirmed (Yes in step 214), it is determined that a request is made to manage the folder (the folder 70A in which the authentication file has been confirmed). To step 216. If the authentication file 108 does not exist in the OPI directory 90, the process proceeds to step 224 described later.

In step 216, the authentication file 108
From the folder 70A where the
08 is deleted.

Next, in step 218, a unique folder ID for identifying the folder 70A in which the authentication file 108 has been confirmed, that is, a folder ID not registered in the OPI database 68 is issued. Further, the issued folder ID and the name of the folder 70A in which the authentication file 108 has been confirmed are set to OP.
It is additionally registered in the I database 68.

Next, in step 220, an ID file 110 in which the issued folder ID is described is created in the folder 70A in which the authentication file 108 has been confirmed.

Next, at step 222, the authentication file 1
08 in the folder 70A where the OPI 100 uses the high-resolution image folder 72,
A low-resolution image folder 74 and a status folder 76 are generated.

In this manner, the ID file is registered in the OPI database, the ID file is created, and the high-resolution image folder 7
2, low resolution image folder 74, status folder 7
6 is generated, the folder 70A is managed by the OPI 100 as an OPI folder 70 that can use the functions of the OPI 100.

Subsequently, in step 224, step 2
10. All monitoring target folders acquired in step 10, ie, all OPI
It is determined whether the search in step 212 has been performed for the directory 90, and the unsearched OPI directory 90 is determined.
If there is (NO), the process returns to step 212 to search the unsearched OPI directory 90.
When the search is completed for all the OPI directories 90 (Yes in step 224), the process returns to the folder & image monitoring process (see FIG. 12).

In the following image monitoring processing, FIG.
As shown in FIG. 4, first in step 230, O
The folder name of the OPI folder 70 from the PI database 68 (see step 218 in the folder monitoring process described above)
Is obtained.

Next, in step 232, the high-resolution image check processing shown in FIG. 15 is performed on each OPI folder 70, and then in step 234, the low-resolution image check processing shown in FIG. 16 is performed. It is. Thereafter, in step 236, it is determined whether the high-resolution image check processing and the low-resolution image check processing have been performed on all the OPI folders 70. If there is an unprocessed OPI folder 70 (no determination),
Return to step 230. That is, the high-resolution image check process and the low-resolution image check process are repeatedly performed on all the OPI folders 70.

In the high-resolution image checking process, as shown in FIG. 15 (see also FIG. 10), the OPI folder 70
In the high-resolution image folder 72 in the folder (step 2).
40), the high-resolution image 7 is stored in the high-resolution image folder 72;
If there is 8 (Yes in step 242), the process proceeds to step 244. If no high-resolution image 78 exists in the high-resolution image folder 72 (negative determination in step 242), the high-resolution image check process ends, and the process returns to the image monitoring process (see FIG. 14).

In step 244, it is determined whether or not there is a low-resolution image 20 corresponding to the high-resolution image 78 in the low-resolution image folder 74. If there is a low-resolution image 20, the process proceeds to step 246, where The generation date and time of the low-resolution image 20 corresponding to the image 78 are compared with the old and new dates.

If there is a low-resolution image 20 corresponding to the high-resolution image 78 (Yes at Step 244) and the date and time of generation of the low-resolution image 20 is newer than the high-resolution image 78 (No at Step 246) , Step 2
Go to 50.

When there is no low-resolution image 20 corresponding to the high-resolution image 78 (negative determination in step 244), or when the generation date and time of the low-resolution image 20 is older than the high-resolution image 78 (step 246). Affirmative decision)
After proceeding to step 248, proceed to step 250.

At step 248, a low-resolution image generation job for instructing to generate a low-resolution image 20 by thinning out the high-resolution image 78 is created and registered in the low-resolution image generation job queue 112.

In step 250, the OPI folder 70
It is determined whether the checking of the correspondence with the low-resolution image has been completed for all the high-resolution images 78 in the high-resolution image folder 72, and the unchecked high-resolution image 7
If there is 8 (negative determination), the process returns to step 244.

The check is completed for all the high resolution images 78 (Yes at step 250), and the generation date and time of the high resolution image 78 without the corresponding low resolution image 20 and the generation date of the corresponding low resolution image 20 are old. When a low-resolution image generation job is generated for the resolution image 78, the high-resolution image check process ends, and the process returns to the image monitoring process (see FIG. 14).

In the low-resolution image checking process performed after the high-resolution image checking process, as shown in FIG. 16 (see also FIG. 10), a search is made in the low-resolution image folder 74 in the OPI folder 70 (step). 260),
If there is a low-resolution image 20 in the low-resolution image folder 74 (Yes at Step 262), Step 264
Proceed to. If there is no low-resolution image 20 in the low-resolution image folder 74 (No in step 262), the low-resolution image check process ends, and the process returns to the image monitoring process (see FIG. 14).

In step 264, it is determined whether or not there is a high-resolution image 78 corresponding to the low-resolution image 20 in the high-resolution image folder 72.
When there is 8 (affirmative determination), the process proceeds to step 268.
If the corresponding high-resolution image 78 does not exist (negative determination), the process proceeds to step 266, and then proceeds to step 2
Go to 68.

In step 266, the low-resolution image 20 having no corresponding high-resolution image 78 is deleted.

In step 268, the OPI folder 70
It is determined whether the checking of the correspondence with the high-resolution image has been completed for all the low-resolution images 20 in the low-resolution image folder 74, and the unchecked low-resolution image 2
If there is 0 (negative determination), the process returns to step 264.

All low-resolution images 2 in the OPI folder
When the check for 0 is completed (Yes in step 268), the low-resolution image check processing is completed, and the low-resolution image 20 having no corresponding high-resolution image 78 is deleted, the image monitoring processing (see FIG. 14). Return to

(Image Conversion Monitoring Process) FIG. 17 shows a processing flow of the image conversion monitoring process.

As shown in FIG. 17, the image conversion monitoring process refers to the low resolution image generation job queue 112 in step 270, and if there is a low resolution image generation job waiting to be executed (affirmative determination), Step 2
At 72, it is confirmed that the number of currently activated image conversion processes is smaller than a predetermined number set in advance (Yes at Step 272), and the routine proceeds to Step 274.

If there is no low-resolution image generation job waiting to be executed (No at step 270), or even if there is a low-resolution image generation job waiting to be executed, a predetermined number of image conversion processes are set. Is running (negative determination in step 272), the process proceeds to step 278 described later.

The specific number of activations of the image conversion process used as a criterion in step 272 is as follows:
This is set according to the processing capacity of the server 12.

In step 274, a low-resolution image generation job waiting to be executed is extracted from the low-resolution image generation job queue 112. Based on this low-resolution image generation job, the image conversion process shown in FIG. It is started as a process different from the monitoring process and the image conversion monitoring process. Next, at step 276, the fact that the number of currently activated image conversion processes has increased by one is stored, and the routine proceeds to step 278.

Here, the image conversion process will be described.

As shown in FIG. 18, when the image conversion process is started, first, a log file 80 is generated, and this log file 80 is set to a “generating” state (step 290).

For example, the high-resolution image 78 “im” in the high-resolution image folder 72 in the OPI folder 70 “April”
When the image conversion process is started based on a low-resolution image generation job corresponding to “ageA.tif” (TIFF format), the log file 80 “imageA.continu” is stored in the status folder 76 in the OPI folder 70 “April”.
e "is generated. At this time, the log file 80 "im
When "ageA.continue" is displayed, the icon 122A is displayed. Note that "" indicates a specific file name.

Next, at step 292, referring to the correspondence table (see Table 1) of the OPI database 68,
Various formats of high-resolution images 78 (EPS, TIFF, J
PEG, DCS, PICT, etc.), the high-resolution image 78
The image conversion program 114 corresponding to the format is called and executed.

For example, in the case of a high-resolution image 78 “imageA.tif” in the TIFF format, the image conversion program 114 “imgtif.exe” corresponding to the TIFF format is called and executed. Thereby, the high-resolution image 78 "im
ageA.tif ”is thinned to generate a thinned image, a comment on the high-resolution image 78“ imageA.tif ”is generated, and the thinned image and the comment are combined to create a low-resolution image 20“ imageAs.eps ”in AliasEPS format. Generated. Also, the generated low-resolution image 20 “imageAs.ep
“s” is stored in the low-resolution image folder 74 in the OPI folder 70 “April”.

Next, at step 294, it is determined whether or not the generation of the low-resolution image 20 has succeeded. If the generation has succeeded (YES at step 296), the process proceeds to step 29.
Proceed to 8. If failed (No in step 296)
Goes to step 299.

At step 298, the log file 80 is set to the “completed” state. For example, the aforementioned OPI folder 7
0 In the case of the log file 80 “imageA.continue” in the status folder 76 in “April”, the file name is changed to “imageA.completed”. When the user displays the log file 80 “imageA.completed” in a shell from the editing workstation side, the icon 122B is displayed.

At step 299, the log file is set to the “failure” state. For example, the aforementioned OPI folder 70
In the case of the log file 80 “imageA.continue” in the status folder 76 in “April”, the file name is “i
mageA.failed ". When the user displays the log file 80 “imageA.failed” in a shell from the editing workstation, the icon 122
C is displayed.

The user operates the editing workstation 10.
When the log file 80 is displayed in a shell from the side and it is confirmed from the file name or the appearance of the icon 122 that a low-resolution image has been generated, an editing operation is performed using editing software.

In the image conversion monitoring process (FIG. 17), it is determined in step 278 whether there is an image conversion process that has been completed. If there is an image conversion process that has been completed (affirmative determination), , Step 2
At 80, it is stored that the number of currently active image conversion processes has decreased by one.

Subsequently, at step 282, the OPI
If the processing of the OPI 100 is continued and the processing of the OPI 100 is continued (negative determination), the process waits until a predetermined time is reached (a positive determination in step 284), and then returns to step 270.

That is, the OPI daemon 104 checks the OP
Until I100 is completed (Yes in step 282), the low-resolution image generation job queue 1
Referring to FIG. 12, the image conversion process for generating the low-resolution image 20 is started while managing the number of the image conversion processes to be started not to exceed the predetermined number.

As described above, in the present embodiment, the OPI
The daemon & 104 processes the folder & image monitoring process and the image conversion monitoring process as separate processes. Further, the process of generating a low-resolution image, which takes a long time, is executed by starting the image conversion process as a further process from the image conversion monitoring process.

That is, the folder & image monitoring process, the image conversion monitoring process, and the image conversion process
Each can be processed independently and in parallel. As a result, without waiting for the end of the low-resolution image generation processing,
The monitoring process can be performed in real time. In addition, a plurality of image conversion processes can be activated at the same time, and a plurality of low-resolution image generation processes can be executed simultaneously.

More specifically, for example, while the OPI is running,
The OPI daemon 104 constantly executes the folder & image monitoring process repeatedly, so that the user can store the authentication file 110 in the normal folder 70A.
By copying this folder 70A to the OPI
When a request is made to manage the folder 70A, the folder 70A can be managed as the OPI folder 70 by immediately registering it in the OPI database 68 or the like.

If the user has copied the high-resolution image 78 into the high-resolution image folder 72, a low-resolution image generation job instructing the high-resolution image 78 to generate the low-resolution image 20 is issued. Generated immediately. When any change is made to the high resolution image 78, an instruction is given to generate a new low resolution image 20 even if the low resolution image 20 has been generated in the past. Further, when the high-resolution image 78 is deleted, the corresponding low-resolution image 20 is immediately deleted from the low-resolution image folder 74.

When a low-resolution image generation job is generated by repeatedly executing the image conversion monitoring process by the OPI daemon 104,
The image conversion process is started immediately, and the low-resolution image 20 is displayed.
Can be generated. Further, even if the image conversion process has already been started, the image conversion process can be executed independently and in parallel. Therefore, it is necessary to start a new image conversion process and execute the generation processing of a plurality of low-resolution images 20 at the same time. Can also.

At this time, in order for the OPI daemon 104 not to activate more than a predetermined number of image conversion processes,
The number of startups is also managed. As a result, it is possible to prevent the number of times of starting the image conversion process from being too large, thereby preventing the load on the server 12 from becoming excessive and affecting other processes (processing stagnation or the like), and always perform the monitoring process in real time. be able to.

Table 2 shows a comparison between the prior art and the present embodiment.

[0155]

[Table 2]

In the present embodiment, the printer 14 is used as an output device of the image data generated by the server 12.
However, image data may be output to a processor that generates a printing plate.

In the present embodiment, the OPI system of the AliasEPS-OPI system has been described as an example.
The present invention may be applied to an OPI system of the s-OPI system or the like.

In the present embodiment, the folder and image monitoring process has been described as being executed repeatedly at all times. However, the folder and image monitoring process may be repeatedly executed at predetermined time intervals as in the image conversion monitoring process. .

At this time, the repetition time interval of the folder & image monitoring process and the image conversion monitoring process is not particularly limited in the present invention, but the repetition time interval of the folder & image monitoring process is determined by the waiting time of the user. In consideration of b, it is necessary to set such that it is not misunderstood as a malfunction of the system. The repetition time interval of the image conversion monitoring process may be set longer than the repetition time interval of the folder & image monitoring process.

In the present embodiment, the image conversion monitoring process has been described as being repeatedly executed at predetermined time intervals. However, the image conversion monitoring process may be repeatedly executed at all times as in the folder and image monitoring process.

Further, in the present embodiment, a configuration in which the server 12 has only one CPU 50 is described as an example of a general server. In such a case, the processing of the CPU 50 is performed at predetermined time intervals. By switching, a plurality of processes (folder & image monitoring process, image conversion monitoring process, image conversion process, etc.) are executed in parallel (so-called parallel processing).
That is, in the server 12, the folder & image monitoring process, the image conversion monitoring process, and the image conversion process are apparently processed in parallel at the same time, but the server 12 is provided with a plurality of CPUs, and the parallel processing is actually executed. You may make it.

[0162]

As described above, the present invention provides an OPI
There is an excellent effect that the monitoring process of the image folder in the system can be performed in real time without being affected by other processes.

[Brief description of the drawings]

FIG. 1 is a schematic configuration diagram of an entire system according to an embodiment.

FIG. 2 is a configuration diagram of a low-resolution image in AliasEPS format.

FIG. 3 is a configuration diagram of an editing workstation.

FIG. 4 is a configuration diagram of a server.

FIG. 5 is a diagram for explaining an OPI database.

FIG. 6 is a functional configuration diagram for explaining functions of a server.

FIG. 7 is a conceptual diagram for describing an outline of a process according to the present embodiment.

FIG. 8 is a conceptual diagram for describing an outline of processing by an OPI daemon.

FIG. 9 is a conceptual diagram illustrating a folder monitoring process.

FIG. 10 is a conceptual diagram illustrating an image monitoring process.

FIG. 11 is a conceptual diagram illustrating an image conversion process.

FIG. 12 is a flowchart illustrating a flow of a folder & image monitoring process.

FIG. 13 is a flowchart illustrating a flow of a folder monitoring process performed in the folder & image monitoring process.

FIG. 14 is a flowchart illustrating a flow of an image monitoring process performed in the folder & image monitoring process.

FIG. 15 is a flowchart illustrating a flow of a high-resolution image checking process performed in the image monitoring process.

FIG. 16 is a flowchart illustrating a flow of a low-resolution image checking process performed in the image monitoring process.

FIG. 17 is a flowchart illustrating a flow of an image conversion monitoring process.

FIG. 18 is a flowchart illustrating a flow of an image conversion process.

FIG. 19 is a conceptual diagram for explaining a conventional OPI method (Aldus-OPI).

FIG. 20 is a flowchart showing a flow of processing for monitoring a folder and generating a low-resolution image, which is performed in the conventional OPI.

[Explanation of symbols]

Reference Signs List 10 editing workstation 12 server 14 printer 16 network 18 client server system 20 low resolution image data (low resolution image data) 22 thinned image 24 comment 66 image database 68 OPI database 70 OPI folder (predetermined folder) 72 high resolution image folder 74 Low-resolution image folder 76 Status folder 78 High-resolution image (high-resolution image data) 80 Log file 88 OPI root directory 90 OPI directory 100 OPI 102 RIP 104 OPI daemon (monitoring means, start management means, control means) 106 OPI filter 108 Authentication file 110 ID file 112 Low resolution image generation job queue 114 Image conversion program 122 Icon PS data B PS data

Claims (7)

[Claims] 1. A low-resolution image data for editing is generated from high-resolution image data, the high-resolution image data and the low-resolution image data are stored in a predetermined folder, and the low-resolution image data is edited at the time of editing. OPI to perform editing work and switch to high-resolution image data at the time of output
A folder monitoring method used in a system, comprising: monitoring the inside of the predetermined folder, grasping a correspondence relationship between the high-resolution image data and the low-resolution image data, and executing a low-resolution image data generation process. A folder monitoring method for continuously determining whether or not there is a folder, regardless of whether the low-resolution image data generation processing is being performed. 2. The folder monitoring method according to claim 1, wherein while the low-resolution image data generation processing is being executed, the low-resolution image data and the monitoring processing are executed in a time-division manner. 3. A start management process for starting a low-resolution image data generation process while restricting a predetermined number or more of the low-resolution image data generation processes from being performed simultaneously, the monitoring process and the low-resolution image data generation process being performed. The folder monitoring method according to claim 1 or 2, wherein the folder monitoring method is continuously executed regardless of whether the generation processing is being executed. 4. When the start management process determines that it is necessary to execute the low-resolution image data generation process in the monitoring process and newly starts the low-resolution image data generation process, 4. The folder monitoring method according to claim 3, wherein when the number of the low-resolution image data generation processes is being executed, the start of the new low-resolution image data generation process is awaited. 5. 5. The folder monitoring method according to claim 3, wherein the monitoring process is repeatedly executed at a shorter time interval than the start management process. 6. A low-resolution image data for editing is generated from high-resolution image data, and the high-resolution image data and the low-resolution image data are stored in a predetermined folder. OPI to perform editing work and switch to high-resolution image data at the time of output
A folder monitoring system used in a system, wherein it is necessary to monitor the inside of the predetermined folder, grasp the correspondence between the high-resolution image data and the low-resolution image data, and execute low-resolution image data generation processing. A folder monitoring system, comprising: monitoring means for continuously executing a monitoring process for determining whether or not there is a file, regardless of whether the low-resolution image data generation process is being performed. 7. A start management process for starting a low-resolution image data generation process while restricting a predetermined number or more of the low-resolution image data generation processes from being executed simultaneously, the monitoring process and the low-resolution image data generation process The folder monitoring system according to claim 6, further comprising a start management unit that continuously executes the generation process regardless of the execution of the generation process.