How do I convert ms/line to ppm

I'm looking at buying a scanner with a document feeder. The feeder can feed in 30 ppm, but the scanner can only can at 12 ms/line. So how fast is the scanner scanning? Is having such a fast document feeder useless?

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

asked Apr 24 '10 at 17:15

user4941

5272914

i imagine "12 ms per line" means the scanning speed depends on what resolutions you scan at (and what resolutions the scanner is capable of). lower resolutions mean fewer lines per page mean faster scanning. higher resolutions mean more lines per page mean slower scanning.

– quack quixote
Apr 24 '10 at 17:21

Absolutely. What I need are some solid numbers. If it depends on dpi, then I need @dpi x, y pages per minute will be achieved.

– user4941
Apr 24 '10 at 18:15

add a comment |

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

asked Apr 24 '10 at 17:15

user4941

5272914

i imagine "12 ms per line" means the scanning speed depends on what resolutions you scan at (and what resolutions the scanner is capable of). lower resolutions mean fewer lines per page mean faster scanning. higher resolutions mean more lines per page mean slower scanning.

– quack quixote
Apr 24 '10 at 17:21

Absolutely. What I need are some solid numbers. If it depends on dpi, then I need @dpi x, y pages per minute will be achieved.

– user4941
Apr 24 '10 at 18:15

add a comment |

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

asked Apr 24 '10 at 17:15

user4941

5272914

speed scanner scanning

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

asked Apr 24 '10 at 17:15

user4941

5272914

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

asked Apr 24 '10 at 17:15

user4941

5272914

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

edited Apr 24 '10 at 17:19

quack quixote

35.3k1087119

asked Apr 24 '10 at 17:15

user4941

5272914

asked Apr 24 '10 at 17:15

user4941

5272914

asked Apr 24 '10 at 17:15

user4941

5272914

i imagine "12 ms per line" means the scanning speed depends on what resolutions you scan at (and what resolutions the scanner is capable of). lower resolutions mean fewer lines per page mean faster scanning. higher resolutions mean more lines per page mean slower scanning.

– quack quixote
Apr 24 '10 at 17:21

Absolutely. What I need are some solid numbers. If it depends on dpi, then I need @dpi x, y pages per minute will be achieved.

– user4941
Apr 24 '10 at 18:15

add a comment |

i imagine "12 ms per line" means the scanning speed depends on what resolutions you scan at (and what resolutions the scanner is capable of). lower resolutions mean fewer lines per page mean faster scanning. higher resolutions mean more lines per page mean slower scanning.

– quack quixote
Apr 24 '10 at 17:21

Absolutely. What I need are some solid numbers. If it depends on dpi, then I need @dpi x, y pages per minute will be achieved.

– user4941
Apr 24 '10 at 18:15

i imagine "12 ms per line" means the scanning speed depends on what resolutions you scan at (and what resolutions the scanner is capable of). lower resolutions mean fewer lines per page mean faster scanning. higher resolutions mean more lines per page mean slower scanning.

– quack quixote
Apr 24 '10 at 17:21

Absolutely. What I need are some solid numbers. If it depends on dpi, then I need @dpi x, y pages per minute will be achieved.

– user4941
Apr 24 '10 at 18:15

add a comment |

3 Answers
3

active

oldest

votes

Well an A4 page (I live in the UK) has about 50 lines of text on it, so to do an A4 page it would take 12 x 50msec = 600msec or a little more than half a second. A 30 ppm sheet feeder would feed one every two seconds leaving you with a reasonable margin for error.

I would suggest you only use the numbers as a guideline, see if you can find a review or some real world tests. Find out what people actually think about it, Amazon.com is quite good for user reviews of consumer products.

answered Apr 24 '10 at 17:20

Richard Slater

4961817

add a comment |

I believe the way to calculate the time (in seconds) a scanner takes to scan a page is as follows:

(Scanner DPI) x (Length of page in inches) x (scanner speed in msec/line) / 1000 =

eg: For a scanner which scans at a speed of 12 msec/line at 1200 DPI (dots per inch) to scan a Letter size page (8.5 x 11 inches) it would take:

1200 (DPI) x 11 (inches) x 12 (msec/line) / 1000 = 158.4 seconds



So approximately = 160 seconds

Notes and assumptions:

I believe "line" in msec/line refers to a line of pixels so at 12msec/line the scanner's sensor array can acquire 1 line of pixels in 12 milliseconds where the length of the line is the length of the scanner's sensor array, which is typically the width of the largest page that can be scanned (see next point).

It is assumed that the scanner's sensor array move along the length of the page (this is typical for most commercial flat-bed scanners). If it move along the width then use the width in the calculation above instead.

It is assumed that the warm up time, time for data transfer to the PC and any other time associated with the process of scanning is negligible when compared to the time taken by the sensor array to acquire the picture of the physical medium. Thus time calculated is approximate at best and likely slightly less then the total time required to scan the page.

Scanner may have different scan speeds at different DPIs and the scaling may not be linear. eg: Scanner which scans at 10 msec/line at 600 DPI may not be able to scan at 5 msec/line at 300 DPI.

edited Jan 7 '17 at 19:04

answered Jan 7 '17 at 18:57

moo

74557

add a comment |

-1

A4 = 5833 pixel line

scan speed 12msec/line

so time = 12msec/line * 5833 line = 69996msec or about 70seconds.

edited Jun 13 '16 at 14:50

techraf

4,079111729

answered Jun 13 '16 at 14:22

mbpower

Where do you get that A4 = 5833 pixel line?

– TheKB
Jun 13 '16 at 15:51

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f134322%2fhow-do-i-convert-ms-line-to-ppm%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

answered Apr 24 '10 at 17:20

Richard Slater

4961817

add a comment |

answered Apr 24 '10 at 17:20

Richard Slater

4961817

add a comment |

answered Apr 24 '10 at 17:20

Richard Slater

4961817

answered Apr 24 '10 at 17:20

Richard Slater

4961817

answered Apr 24 '10 at 17:20

Richard Slater

4961817

answered Apr 24 '10 at 17:20

Richard Slater

4961817

answered Apr 24 '10 at 17:20

Richard Slater

4961817

add a comment |

I believe the way to calculate the time (in seconds) a scanner takes to scan a page is as follows:

(Scanner DPI) x (Length of page in inches) x (scanner speed in msec/line) / 1000 =

eg: For a scanner which scans at a speed of 12 msec/line at 1200 DPI (dots per inch) to scan a Letter size page (8.5 x 11 inches) it would take:

1200 (DPI) x 11 (inches) x 12 (msec/line) / 1000 = 158.4 seconds



So approximately = 160 seconds

Notes and assumptions:

I believe "line" in msec/line refers to a line of pixels so at 12msec/line the scanner's sensor array can acquire 1 line of pixels in 12 milliseconds where the length of the line is the length of the scanner's sensor array, which is typically the width of the largest page that can be scanned (see next point).

It is assumed that the scanner's sensor array move along the length of the page (this is typical for most commercial flat-bed scanners). If it move along the width then use the width in the calculation above instead.

It is assumed that the warm up time, time for data transfer to the PC and any other time associated with the process of scanning is negligible when compared to the time taken by the sensor array to acquire the picture of the physical medium. Thus time calculated is approximate at best and likely slightly less then the total time required to scan the page.

Scanner may have different scan speeds at different DPIs and the scaling may not be linear. eg: Scanner which scans at 10 msec/line at 600 DPI may not be able to scan at 5 msec/line at 300 DPI.

edited Jan 7 '17 at 19:04

answered Jan 7 '17 at 18:57

moo

74557

add a comment |

I believe the way to calculate the time (in seconds) a scanner takes to scan a page is as follows:

(Scanner DPI) x (Length of page in inches) x (scanner speed in msec/line) / 1000 =

eg: For a scanner which scans at a speed of 12 msec/line at 1200 DPI (dots per inch) to scan a Letter size page (8.5 x 11 inches) it would take:

1200 (DPI) x 11 (inches) x 12 (msec/line) / 1000 = 158.4 seconds



So approximately = 160 seconds

Notes and assumptions:

I believe "line" in msec/line refers to a line of pixels so at 12msec/line the scanner's sensor array can acquire 1 line of pixels in 12 milliseconds where the length of the line is the length of the scanner's sensor array, which is typically the width of the largest page that can be scanned (see next point).

It is assumed that the scanner's sensor array move along the length of the page (this is typical for most commercial flat-bed scanners). If it move along the width then use the width in the calculation above instead.

It is assumed that the warm up time, time for data transfer to the PC and any other time associated with the process of scanning is negligible when compared to the time taken by the sensor array to acquire the picture of the physical medium. Thus time calculated is approximate at best and likely slightly less then the total time required to scan the page.

Scanner may have different scan speeds at different DPIs and the scaling may not be linear. eg: Scanner which scans at 10 msec/line at 600 DPI may not be able to scan at 5 msec/line at 300 DPI.

edited Jan 7 '17 at 19:04

answered Jan 7 '17 at 18:57

moo

74557

add a comment |

I believe the way to calculate the time (in seconds) a scanner takes to scan a page is as follows:

(Scanner DPI) x (Length of page in inches) x (scanner speed in msec/line) / 1000 =

eg: For a scanner which scans at a speed of 12 msec/line at 1200 DPI (dots per inch) to scan a Letter size page (8.5 x 11 inches) it would take:

1200 (DPI) x 11 (inches) x 12 (msec/line) / 1000 = 158.4 seconds



So approximately = 160 seconds

Notes and assumptions:

I believe "line" in msec/line refers to a line of pixels so at 12msec/line the scanner's sensor array can acquire 1 line of pixels in 12 milliseconds where the length of the line is the length of the scanner's sensor array, which is typically the width of the largest page that can be scanned (see next point).

It is assumed that the scanner's sensor array move along the length of the page (this is typical for most commercial flat-bed scanners). If it move along the width then use the width in the calculation above instead.

It is assumed that the warm up time, time for data transfer to the PC and any other time associated with the process of scanning is negligible when compared to the time taken by the sensor array to acquire the picture of the physical medium. Thus time calculated is approximate at best and likely slightly less then the total time required to scan the page.

Scanner may have different scan speeds at different DPIs and the scaling may not be linear. eg: Scanner which scans at 10 msec/line at 600 DPI may not be able to scan at 5 msec/line at 300 DPI.

edited Jan 7 '17 at 19:04

answered Jan 7 '17 at 18:57

moo

74557

I believe the way to calculate the time (in seconds) a scanner takes to scan a page is as follows:

(Scanner DPI) x (Length of page in inches) x (scanner speed in msec/line) / 1000 =

eg: For a scanner which scans at a speed of 12 msec/line at 1200 DPI (dots per inch) to scan a Letter size page (8.5 x 11 inches) it would take:

1200 (DPI) x 11 (inches) x 12 (msec/line) / 1000 = 158.4 seconds



So approximately = 160 seconds

Notes and assumptions:

I believe "line" in msec/line refers to a line of pixels so at 12msec/line the scanner's sensor array can acquire 1 line of pixels in 12 milliseconds where the length of the line is the length of the scanner's sensor array, which is typically the width of the largest page that can be scanned (see next point).

It is assumed that the scanner's sensor array move along the length of the page (this is typical for most commercial flat-bed scanners). If it move along the width then use the width in the calculation above instead.

It is assumed that the warm up time, time for data transfer to the PC and any other time associated with the process of scanning is negligible when compared to the time taken by the sensor array to acquire the picture of the physical medium. Thus time calculated is approximate at best and likely slightly less then the total time required to scan the page.

Scanner may have different scan speeds at different DPIs and the scaling may not be linear. eg: Scanner which scans at 10 msec/line at 600 DPI may not be able to scan at 5 msec/line at 300 DPI.

edited Jan 7 '17 at 19:04

answered Jan 7 '17 at 18:57

moo

74557

edited Jan 7 '17 at 19:04

answered Jan 7 '17 at 18:57

moo

74557

answered Jan 7 '17 at 18:57

moo

74557

answered Jan 7 '17 at 18:57

moo

74557

add a comment |

-1

A4 = 5833 pixel line

scan speed 12msec/line

so time = 12msec/line * 5833 line = 69996msec or about 70seconds.

edited Jun 13 '16 at 14:50

techraf

4,079111729

answered Jun 13 '16 at 14:22

mbpower

Where do you get that A4 = 5833 pixel line?

– TheKB
Jun 13 '16 at 15:51

add a comment |

-1

A4 = 5833 pixel line

scan speed 12msec/line

so time = 12msec/line * 5833 line = 69996msec or about 70seconds.

edited Jun 13 '16 at 14:50

techraf

4,079111729

answered Jun 13 '16 at 14:22

mbpower

Where do you get that A4 = 5833 pixel line?

– TheKB
Jun 13 '16 at 15:51

add a comment |

-1

A4 = 5833 pixel line

scan speed 12msec/line

so time = 12msec/line * 5833 line = 69996msec or about 70seconds.

edited Jun 13 '16 at 14:50

techraf

4,079111729

answered Jun 13 '16 at 14:22

mbpower

A4 = 5833 pixel line

scan speed 12msec/line

so time = 12msec/line * 5833 line = 69996msec or about 70seconds.

edited Jun 13 '16 at 14:50

techraf

4,079111729

answered Jun 13 '16 at 14:22

mbpower

edited Jun 13 '16 at 14:50

techraf

4,079111729

edited Jun 13 '16 at 14:50

techraf

4,079111729

edited Jun 13 '16 at 14:50

techraf

4,079111729

answered Jun 13 '16 at 14:22

mbpower

answered Jun 13 '16 at 14:22

mbpower

answered Jun 13 '16 at 14:22

mbpower

Where do you get that A4 = 5833 pixel line?

– TheKB
Jun 13 '16 at 15:51

add a comment |

Where do you get that A4 = 5833 pixel line?

– TheKB
Jun 13 '16 at 15:51

Where do you get that A4 = 5833 pixel line?

– TheKB
Jun 13 '16 at 15:51

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Gfrktyl