 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm back for the search again. I really don't want to use the examples
people
have been discussing on using the text feature of POV to put my name in my
work.
I found ImageMagick, but it doesn't work nicely in DOS. The command for
annotation
is so long that DOS limits the amount of text at the prompt. So then I put
it in a
batch file, but since ImageMagick says to use image%03d.tga for a series of
files,
DOS interprets the %0 as a variable - basically it just doesn't work. So,
now I'm
searching again for something that will place text in a series of images.
Any other recommendations anyone??
Mike
--
All statements are of my opinion and concern. They do not reflect the views
of my employer.
Remove the x at the end of my address for replies.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Weber wrote:
>
> I'm back for the search again. I really don't want to use the examples
> people
> have been discussing on using the text feature of POV to put my name in my
> work.
> I found ImageMagick, but it doesn't work nicely in DOS. The command for
> annotation
> is so long that DOS limits the amount of text at the prompt. So then I put
> it in a
> batch file, but since ImageMagick says to use image%03d.tga for a series of
> files,
> DOS interprets the %0 as a variable - basically it just doesn't work. So,
> now I'm
> searching again for something that will place text in a series of images.
>
> Any other recommendations anyone??
>
> Mike
Well, I could I suppose code something in c. I guess. Been a while since
I've done DOS and all that segmentation [censored] though. :) far
pointers. huge pointers. yuck.
--
Lewis A. Sellers: writer and contract Multimedia Website Developer
mailto:lse### [at] usit net (The Fourth Millennium Foundation)
http://www.public.usit.net/lsellers/ & http://www.intrafoundation.com
http://brain-of-pooh.tech-soft.com/users/critters/bios/sellers_lewis.html
You can bug the living bejesus out of me live on ICQ @ 491461
(If I don't get back to you within a month, I'm out of prozac in some
dark corner somewhere screaming things quite unintelligable but -- most
curiously -- thick with a sumerian accent.)
"The comedy is over" -i pagliacci
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I thought about it myself. I think what I need to do is write a small
Windows program that I can specify the command line, name of the files to
annotate and indicating the start and stop numbers. I have image001.tga
image002.tga...image 360.tga and shell out to DOS to have it run.
Lewis Sellers wrote in message <3641F9EA.36C9F5C0@usit.net>...
>
>
>Mike Weber wrote:
>>
>> I'm back for the search again. I really don't want to use the examples
>> people
>> have been discussing on using the text feature of POV to put my name in
my
>> work.
>> I found ImageMagick, but it doesn't work nicely in DOS. The command for
>> annotation
>> is so long that DOS limits the amount of text at the prompt. So then I
put
>> it in a
>> batch file, but since ImageMagick says to use image%03d.tga for a series
of
>> files,
>> DOS interprets the %0 as a variable - basically it just doesn't work.
So,
>> now I'm
>> searching again for something that will place text in a series of images.
>>
>> Any other recommendations anyone??
>>
>> Mike
>
>Well, I could I suppose code something in c. I guess. Been a while since
>I've done DOS and all that segmentation [censored] though. :) far
>pointers. huge pointers. yuck.
>
>
>--
>Lewis A. Sellers: writer and contract Multimedia Website Developer
>mailto:lse### [at] usitnet (The Fourth Millennium Foundation)
>http://www.public.usit.net/lsellers/ & http://www.intrafoundation.com
>http://brain-of-pooh.tech-soft.com/users/critters/bios/sellers_lewis.html
>
>You can bug the living bejesus out of me live on ICQ @ 491461
>(If I don't get back to you within a month, I'm out of prozac in some
>dark corner somewhere screaming things quite unintelligable but -- most
>curiously -- thick with a sumerian accent.)
>
>"The comedy is over" -i pagliacci
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
There was a command-line program around some time ago that did exactly what you
want (more or less). It was written by Matthew Kaustinen. Can't recall what it
was called though.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Weber wrote:
>
> I thought about it myself. I think what I need to do is write a small
> Windows program that I can specify the command line, name of the files to
> annotate and indicating the start and stop numbers. I have image001.tga
> image002.tga...image 360.tga and shell out to DOS to have it run.
I sort of already wrote it a while ago. But having DOS pointer problems.
urggg.
A simple thing called imprint.exe. It takes a file called imprint.tga
and alphas it onto every other TGA file in your current directory that
has has the same width/height/uncompressed 24 bit format. If I have a
little more time tonight I'll see about finishing it. Or at least
posting it somewhere here to let other people more familiar with DOS
16-bit oddities have a go at debugging. :)
If it wasn't for 16-bit probs, I'd have already had her done.
This is the TGA file format btw:
/*
--------------------------------------------------------------------------------
DATA TYPE 2: Unmapped RGB
images. |
_______________________________________________________________________________|
| Offset | Length |
Description |
|--------|--------|------------------------------------------------------------|
|--------|--------|------------------------------------------------------------|
| 0 | 1 | Number of Characters in Identification
Field. |
| |
| |
| | | This field is a one-byte unsigned integer,
specifying |
| | | the length of the Image Identification Field. Its
value |
| | | is 0 to 255. A value of 0 means that no
Image |
| | | Identification Field is
included. |
| |
| |
|--------|--------|------------------------------------------------------------|
| 1 | 1 | Color Map
Type. |
| |
| |
| | | This field contains either 0 or 1. 0 means no
color map |
| | | is included. 1 means a color map is included, but
since |
| | | this is an unmapped image it is usually ignored.
TIPS |
| | | ( a Targa paint system ) will set the border
color |
| | | the first map color if it is
present. |
| |
| |
|--------|--------|------------------------------------------------------------|
| 2 | 1 | Image Type
Code. |
| |
| |
| | | This field will always contain a binary
2. |
| | | ( That's what makes it Data Type 2
). |
| |
| |
|--------|--------|------------------------------------------------------------|
| 3 | 5 | Color Map
Specification. |
| |
| |
| | | Ignored if Color Map Type is 0; otherwise,
interpreted |
| | | as
follows: |
| |
| |
| 3 | 2 | Color Map
Origin. |
| | | Integer ( lo-hi ) index of first color map
entry. |
| |
| |
| 5 | 2 | Color Map
Length. |
| | | Integer ( lo-hi ) count of color map
entries. |
| |
| |
| 7 | 1 | Color Map Entry
Size. |
| | | Number of bits in color map entry. 16 for the
Targa 16, |
| | | 24 for the Targa 24, 32 for the Targa
32. |
| |
| |
|--------|--------|------------------------------------------------------------|
| 8 | 10 | Image
Specification. |
| |
| |
| 8 | 2 | X Origin of
Image. |
| | | Integer ( lo-hi ) X coordinate of the lower left
corner |
| | | of the
image. |
| |
| |
| 10 | 2 | Y Origin of
Image. |
| | | Integer ( lo-hi ) Y coordinate of the lower left
corner |
| | | of the
image. |
| |
| |
| 12 | 2 | Width of
Image. |
| | | Integer ( lo-hi ) width of the image in
pixels. |
| |
| |
| 14 | 2 | Height of
Image. |
| | | Integer ( lo-hi ) height of the image in
pixels. |
| |
| |
| 16 | 1 | Image Pixel
Size. |
| | | Number of bits in a pixel. This is 16 for Targa
16, |
| | | 24 for Targa 24, and .... well, you get the
idea. |
| |
| |
| 17 | 1 | Image Descriptor
Byte. |
| | | Bits 3-0 - number of attribute bits associated with
each |
| | | pixel. For the Targa 16, this would be
0 or |
| | | 1. For the Targa 24, it should be 0.
For |
| | | Targa 32, it should be
8. |
| | | Bit 4 - reserved. Must be set to
0. |
| | | Bit 5 - screen origin
bit. |
| | | 0 = Origin in lower left-hand
corner. |
| | | 1 = Origin in upper left-hand
corner. |
| | | Must be 0 for Truevision
images. |
| | | Bits 7-6 - Data storage interleaving
flag. |
| | | 00 =
non-interleaved. |
| | | 01 = two-way (even/odd)
interleaving. |
| | | 10 = four way
interleaving. |
| | | 11 =
reserved. |
| |
| |
|--------|--------|------------------------------------------------------------|
| 18 | varies | Image Identification
Field. |
| | | Contains a free-form identification field of the
length |
| | | specified in byte 1 of the image record. It's
usually |
| | | omitted ( length in byte 1 = 0 ), but can be up to
255 |
| | | characters. If more identification information
is |
| | | required, it can be stored after the image
data. |
| |
| |
|--------|--------|------------------------------------------------------------|
| varies | varies | Color map
data. |
| |
| |
| | | If the Color Map Type is 0, this field doesn't
exist. |
| | | Otherwise, just read past it to get to the
image. |
| | | The Color Map Specification describes the size of
each |
| | | entry, and the number of entries you'll have to
skip. |
| | | Each color map entry is 2, 3, or 4
bytes. |
| |
| |
|--------|--------|------------------------------------------------------------|
| varies | varies | Image Data
Field. |
| |
| |
| | | This field specifies (width) x (height) pixels.
Each |
| | | pixel specifies an RGB color value, which is stored
as |
| | | an integral number of
bytes. |
| |
| |
| | | The 2 byte entry is broken down as
follows: |
| | | ARRRRRGG GGGBBBBB, where each letter represents a
bit. |
| | | But, because of the lo-hi storage order, the first
byte |
| | | coming from the file will actually be GGGBBBBB, and
the |
| | | second will be ARRRRRGG. "A" represents an
attribute bit. |
| |
| |
| | | The 3 byte entry contains 1 byte each of blue,
green, |
| | | and
red. |
| |
| |
| | | The 4 byte entry contains 1 byte each of blue,
green, |
| | | red, and attribute. For faster speed (because of
the |
| | | hardware of the Targa board itself), Targa 24
images are |
| | | sometimes stored as Targa 32
images. |
| |
| |
--------------------------------------------------------------------------------
*/
--
Lewis A. Sellers: writer and contract Multimedia Website Developer
mailto:lse### [at] usitnet (The Fourth Millennium Foundation)
http://www.public.usit.net/lsellers/ & http://www.intrafoundation.com
http://brain-of-pooh.tech-soft.com/users/critters/bios/sellers_lewis.html
You can bug the living bejesus out of me live on ICQ @ 491461
(If I don't get back to you within a month, I'm out of prozac in some
dark corner somewhere screaming things quite unintelligable but -- most
curiously -- thick with a sumerian accent.)
"The comedy is over" -i pagliacci
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lewis Sellers <lse### [at] usitnet> wrote:
: posting it somewhere here to let other people more familiar with DOS
: 16-bit oddities have a go at debugging. :)
: If it wasn't for 16-bit probs, I'd have already had her done.
16-bit problems? What 16-bit problems? There are no 16-bit problems in
DOS programs: just use the right compiler. Why you should get any problems
with 16-bit limits when you can just download a proper compiler with no
limitations and which makes programs in full 32-bit protected mode?
For an example, see my targa averager (http://iki.fi/warp/PovUtils/average/).
The source code is pure ANSI C, compilable in any system. It includes a DOS
compile which have no problems (it works in 32-bit pmode). I didn't have to
make any change to compile it on UNIX or DOS. And of course the program
(at least in some average modes) reads big images completely into memory
(if there is enough ram available; if not, it uses a slower
scanline-by-scanline algorithm).
I will probably add a feature to the program which allows to make the
thing requested in this thread... some day :)
If you don't have any proper compiler for dos, try:
http://www.delorie.com/djgpp/
--
- Warp. -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Weber <mwe### [at] racal-pelagoscom> wrote in message
3641be5b.0@news.povray.org...
<snip>
>Any other recommendations anyone??
Use POV. Use the rendered files as an image_map, put some text object in
front and use an orthographic camera.
>Mike
Peter
>All statements are of my opinion and concern. They do not reflect the
views
>of my employer.
>Remove the x at the end of my address for replies.
Neither do mine :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nieminen Mika wrote:
> 16-bit problems? What 16-bit problems? There are no 16-bit problems in
> DOS programs: just use the right compiler. Why you should get any problems
> with 16-bit limits when you can just download a proper compiler with no
> limitations and which makes programs in full 32-bit protected mode?
Because the big 10-pound Borland c++ 4.52 box was the most handy DOS
complier around at the time?
I've used watcom and djgpp before, but that was ages ago and they
weren't laying around my machine at the time.
If you're so pro-DPMI then feel free to go hack on the source. It's
posted in.... um, binary.utilities. imprint.c is the name. A quick dirty
hack from some .bmp/.pcx utilities I apparently make in '95. It almost
works. I started to convert it to 32-bit before x-files came on, but ran
into some struct align probs. Don't feel like downloading all the djgpp
docs to force it to comply. I'm tired. Have fun. :)
--min
--
Lewis A. Sellers: writer and contract Multimedia Website Developer
mailto:lse### [at] usitnet (The Fourth Millennium Foundation)
http://www.public.usit.net/lsellers/ & http://www.intrafoundation.com
http://brain-of-pooh.tech-soft.com/users/critters/bios/sellers_lewis.html
You can bug the living bejesus out of me live on ICQ @ 491461
(If I don't get back to you within a month, I'm out of prozac in some
dark corner somewhere screaming things quite unintelligable but -- most
curiously -- thick with a sumerian accent.)
"The comedy is over" -i pagliacci
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lewis Sellers <lse### [at] usitnet> wrote:
: If you're so pro-DPMI then feel free to go hack on the source.
If it compiles in UNIX with gcc, it should compile with djgpp as is. Unless
you have put some non-portable code in the source, which shouldn't be
necessary with this kind of utility. Making non-portable code with this
kind of programs is always a bad idea.
It's cool to receive a mail saying "I compiled your triangle mesh smoother
in my macintosh with no problems", specially because I have never used a
macintosh and have absolutely no idea about coding for it... :)
--
- Warp. -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
All right, Mika was starting to tick off the coder in me :) so to defend
my manhood I went and downloaded the bloody djgpp compiler and rewrote
the imprint proggie. I posted it in povray.binaries.utilities.
Try that for now. :)
--min
--
Lewis A. Sellers: writer and contract Multimedia Website Developer
mailto:lse### [at] usitnet (The Fourth Millennium Foundation)
http://www.public.usit.net/lsellers/ & http://www.intrafoundation.com
http://brain-of-pooh.tech-soft.com/users/critters/bios/sellers_lewis.html
You can bug the living bejesus out of me live on ICQ @ 491461
(If I don't get back to you within a month, I'm out of prozac in some
dark corner somewhere screaming things quite unintelligable but -- most
curiously -- thick with a sumerian accent.)
"The comedy is over" -i pagliacci
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
