 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
CFM nous apporta ses lumieres ainsi en ce 2004/05/12 19:10... :
>>Where are the ""?
>>
>>
>>
>>>SceneFile=billiards
>>>IniOutputFile=
>>><snip>
>>>Is Notepad supposed to be in the same directory as POV-ray for Windows v3.5?
>>>
>>>
>>>
>>>
>>>
>>>
>>No. Notepad need to be in it's normal, default, location, or somewhere
>>where windows can find it: ie.:it's in the system path.
>>
>>Alain
>>
>>
>
>I don't understand your question. Also, I'm just trying to access the Edit
>Master POVRAY.ini in the tools menu with no luck. I have notepad on the
>desktop, but the POV program comes up with an error every time I try to
>click on Edit Master POVRAY.ini.
>
>
>
I don't see any backslashs in the paths, and could'nt see any in the
source view.
Do you have notepad.exe on the desktop, or a shortcut to it?
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen McAvoy <mca### [at] aol com> wrote:
> On Thu, 13 May 2004 16:13:37 EDT, "CFM" <nomail@nomail> wrote:
>
> >Still, I don't
> >know if TMPGE nc-2.5.
>
> Hi, CFM
> TMPGEnc will create a MPEG which is a common movie format and save it
> to the directory you want. It will not play them back. You will need
> to use Windows Media Player or something else. It is easy to use, when
> you browse for the files just double click in the first one of the
> series and it will select them all. You can change the compression
> settings if you want. Like most programmes it takes some time to get
> experience but you can just accept the default settings till you want
> to experiment.
> You could use VideoMach to create your movie
> http://gromada.com/download.html
> When VideoMach creates the movie it automatically plays it in Windows
> Media Player. One thing to point out VideoMach is when you select the
> files you must select them from the last to the first. E.g. 100 to
> 001.
>
>
> Regards
> Stephen
OK, so I don't need POVTICK and those other applications?
From my experience, only certain movie players such as Windows Media Player,
RealOne, and QuickTime are specific to certain movies. Are the MPEGs that
TMPGEnc generate specific to any one of these movie players, or is it
general to all of them?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Oh, I forgot to ask the most pertinent question: How do I use or activate
TMPGEnc?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40a525af27c58a6aff0268740@news.povray.org>, nomail@nomail
says...
> Oh, I forgot to ask the most pertinent question: How do I use or activate
> TMPGEnc?
>
>
You just run the program and it will give you a list of options to encode
to. I don't know enough about what each does to say exactly, but some are
MPEG-2 for DVD, etc. I think you also pick the specific encoder to use
too. Most people are probably using DivX or one of the other popular
ones. Some are oddballs that work in some players but not others, etc,
mainly do to bugs in the way the players deal with the codec. Some codecs
like AngelPotion are just junk to begin with, crash and produce
intentionally bad files (popular with the truly cheap pron sites..)
In general, once you install a version of the DivX or other codec, then
'all' players on your system, from Windows Media Player, to WinAmp 5, to
DivX Player, etc. will all recognize the movie and play it without a
problem, which should answer your other question about which players can
play the movies.
If you plan to use PNG files to save space, but still have all the color
and quality (Where jpg loses quality and gif loses color), then you may
need to get the reader for TMPGEnc for PNG. Someone said that the
original file in these news groups was corrupted (or at least their
download was), so try getting it from my web site at:
http://www.geocities.com/shadowfyr2/cg/vfpng.zip
I tested the archive of mine and it is OK. It also should now be easier
for me to point people to as well. lol
The instructions for how to install these are someplace in the TMPGEnc
docs I think..
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 14 May 2004 15:48:32 EDT, "CFM" <nomail@nomail> wrote:
>OK, so I don't need POVTICK and those other applications?
Correct.
>
>From my experience, only certain movie players such as Windows Media Player,
>RealOne, and QuickTime are specific to certain movies. Are the MPEGs that
>TMPGEnc generate specific to any one of these movie players, or is it
>general to all of them?
What happens is that Windows associates certain file types with
particular applications. So when you double click a file, that is not
an executable one, Windows uses the executable (EXE) to run it.
Depending upon which version of windows you are using try right
clicking on an image or animation and select "open with". You can then
pick which application you want to run the file with.
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> You just run the program and it will give you a list of options to encode
> to. I don't know enough about what each does to say exactly, but some are
> MPEG-2 for DVD, etc. I think you also pick the specific encoder to use
> too. Most people are probably using DivX or one of the other popular
> ones. Some are oddballs that work in some players but not others, etc,
> mainly do to bugs in the way the players deal with the codec. Some codecs
> like AngelPotion are just junk to begin with, crash and produce
> intentionally bad files (popular with the truly cheap pron sites..)
>
> In general, once you install a version of the DivX or other codec, then
> 'all' players on your system, from Windows Media Player, to WinAmp 5, to
> DivX Player, etc. will all recognize the movie and play it without a
> problem, which should answer your other question about which players can
> play the movies.
>
> If you plan to use PNG files to save space, but still have all the color
> and quality (Where jpg loses quality and gif loses color), then you may
> need to get the reader for TMPGEnc for PNG. Someone said that the
> original file in these news groups was corrupted (or at least their
> download was), so try getting it from my web site at:
>
> http://www.geocities.com/shadowfyr2/cg/vfpng.zip
>
> I tested the archive of mine and it is OK. It also should now be easier
> for me to point people to as well. lol
>
> The instructions for how to install these are someplace in the TMPGEnc
> docs I think..
OK, I clicked onto the TMPGEnc program, and came up with a window that asked
me what format I wanted. I clicked on NTSC under Video-CD. I then was
brought to a page that said to select the source file. There was a video
file box and an audio file box. I clicked the browse button next to the
video file box. Another window then opened with an empty file name box. I
guess I was supposed to enter the name of the file I want converted into a
video. That would be clockdemo.pov, however it was not listed, and not
recognized, either. I set the program to retrieve the file out of the
correct directory, too. Still, nothing worked. What's wrong?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40a9109927c58a6a5af6886c0@news.povray.org>, nomail@nomail
says...
> > You just run the program and it will give you a list of options to encode
> > to. I don't know enough about what each does to say exactly, but some are
> > MPEG-2 for DVD, etc. I think you also pick the specific encoder to use
> > too. Most people are probably using DivX or one of the other popular
> > ones. Some are oddballs that work in some players but not others, etc,
> > mainly do to bugs in the way the players deal with the codec. Some codecs
> > like AngelPotion are just junk to begin with, crash and produce
> > intentionally bad files (popular with the truly cheap pron sites..)
> >
> > In general, once you install a version of the DivX or other codec, then
> > 'all' players on your system, from Windows Media Player, to WinAmp 5, to
> > DivX Player, etc. will all recognize the movie and play it without a
> > problem, which should answer your other question about which players can
> > play the movies.
> >
> > If you plan to use PNG files to save space, but still have all the color
> > and quality (Where jpg loses quality and gif loses color), then you may
> > need to get the reader for TMPGEnc for PNG. Someone said that the
> > original file in these news groups was corrupted (or at least their
> > download was), so try getting it from my web site at:
> >
> > http://www.geocities.com/shadowfyr2/cg/vfpng.zip
> >
> > I tested the archive of mine and it is OK. It also should now be easier
> > for me to point people to as well. lol
> >
> > The instructions for how to install these are someplace in the TMPGEnc
> > docs I think..
>
> OK, I clicked onto the TMPGEnc program, and came up with a window that asked
> me what format I wanted. I clicked on NTSC under Video-CD. I then was
> brought to a page that said to select the source file. There was a video
> file box and an audio file box. I clicked the browse button next to the
> video file box. Another window then opened with an empty file name box. I
> guess I was supposed to enter the name of the file I want converted into a
> video. That would be clockdemo.pov, however it was not listed, and not
> recognized, either. I set the program to retrieve the file out of the
> correct directory, too. Still, nothing worked. What's wrong?
>
>
Ok.. First off, it can't 'run' POV files. It can only take images and
compress them into a video stream. So, what you need to do is run the
clockdemo.ini file inside POVRay. The ini file includes the information
needed to tell POVRay how many frames to create, etc. These frames will
probably be called something like clockdemo1.bmp, clockdemo2.bmp, etc.
You need to select the clockdemo1.bmp file in TMPGEnc, since that is the
'first' image in the sequence you want to make into a movie. TMPGEnc will
then run you through a series of screens for various settings, unless you
know what you are doing, ignore these. Finally it will reach a screen
with the 'output file'. This will likely be something like clockdemo.mpg,
so unless you want to name it something else, you can also leave that
alone. TMPGEnc should then read in each file one at a time, until it
reaches that last bmp file with clockdemo in its name, followed by a
number. Really simple. ;)
Now, as for the .ini files in povray. Most do not include a line
specifying the 'type' to produce. This means that unless you have done
what I did and edited povray.ini to change the default to png (I did this
because I don't have the space for the 100+ images some animations
generate), it will default to the 'system' type, which in windows is
.bmp. If you change this default in povray.ini or in the clockdemo.ini,
then of course the file you tell TMPGEnc to start with will be a .png
file instead. However, if you use this type, you 'must' install the vfpng
files I mentioned first, since TMPGEnc doesn't know how to read them
without it. If you have lots of drive space (like an 80GB drive or
something), then this is going to be a lot less of an issue than for me.
lol In that case, you can probably stick with .bmp and be OK. At least as
long as you eventually delete all the original images after you have a
mpg video you like. ;) lol
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Ok.. First off, it can't 'run' POV files. It can only take images and
> compress them into a video stream. So, what you need to do is run the
> clockdemo.ini file inside POVRay. The ini file includes the information
> needed to tell POVRay how many frames to create, etc. These frames will
> probably be called something like clockdemo1.bmp, clockdemo2.bmp, etc.
> You need to select the clockdemo1.bmp file in TMPGEnc, since that is the
> 'first' image in the sequence you want to make into a movie. TMPGEnc will
> then run you through a series of screens for various settings, unless you
> know what you are doing, ignore these. Finally it will reach a screen
> with the 'output file'. This will likely be something like clockdemo.mpg,
> so unless you want to name it something else, you can also leave that
> alone. TMPGEnc should then read in each file one at a time, until it
> reaches that last bmp file with clockdemo in its name, followed by a
> number. Really simple. ;)
>
> Now, as for the .ini files in povray. Most do not include a line
> specifying the 'type' to produce. This means that unless you have done
> what I did and edited povray.ini to change the default to png (I did this
> because I don't have the space for the 100+ images some animations
> generate), it will default to the 'system' type, which in windows is
> .bmp. If you change this default in povray.ini or in the clockdemo.ini,
> then of course the file you tell TMPGEnc to start with will be a .png
> file instead. However, if you use this type, you 'must' install the vfpng
> files I mentioned first, since TMPGEnc doesn't know how to read them
> without it. If you have lots of drive space (like an 80GB drive or
> something), then this is going to be a lot less of an issue than for me.
> lol In that case, you can probably stick with .bmp and be OK. At least as
> long as you eventually delete all the original images after you have a
> mpg video you like. ;) lol
That's odd. I'm using POV-ray version 3.5. The tutorial that came with
version 3.5 said that the older versions required the manual creation of
separate frames in a sequence, each frame with its own name. The tutorial
said that the new version I'm NOW using doesn't require that, anymore. The
tutorial said that I do not need a separate batch script and no external
sequencing programs. Apparently, the command line can be used to activate
an internal animation sequence that causes POV-ray to automatically handle
the animation loop details for me. All I'd need to put into the ini file
are "Initial_Frame=1 Final_Frame=20" if I wanted to generate 20 frames for
the animation. I could also have the option of putting "Initial_Clock=0.0
Final_Clock=2.0" if I wanted the clock to cycle through values other than
the default of just 0.0-1.0. Then, I also have a third option of adding
"Subset_Start_Frame=7 Subset_End_Frame=12" if I wanted to view just frames
7-12 in an animation of about 20 frames. After that, I just render the
whole animation at once. I don't think your explanation coincides with the
version of POV-ray I'm using. Do you recognize any of the stuff I put up
above?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40aa75bc27c58a6a6b9afb860@news.povray.org>, nomail@nomail
says...
> > Ok.. First off, it can't 'run' POV files. It can only take images and
> > compress them into a video stream. So, what you need to do is run the
> > clockdemo.ini file inside POVRay. The ini file includes the information
> > needed to tell POVRay how many frames to create, etc. These frames will
> > probably be called something like clockdemo1.bmp, clockdemo2.bmp, etc.
> > You need to select the clockdemo1.bmp file in TMPGEnc, since that is the
> > 'first' image in the sequence you want to make into a movie. TMPGEnc will
> > then run you through a series of screens for various settings, unless you
> > know what you are doing, ignore these. Finally it will reach a screen
> > with the 'output file'. This will likely be something like clockdemo.mpg,
> > so unless you want to name it something else, you can also leave that
> > alone. TMPGEnc should then read in each file one at a time, until it
> > reaches that last bmp file with clockdemo in its name, followed by a
> > number. Really simple. ;)
> >
> > Now, as for the .ini files in povray. Most do not include a line
> > specifying the 'type' to produce. This means that unless you have done
> > what I did and edited povray.ini to change the default to png (I did this
> > because I don't have the space for the 100+ images some animations
> > generate), it will default to the 'system' type, which in windows is
> > .bmp. If you change this default in povray.ini or in the clockdemo.ini,
> > then of course the file you tell TMPGEnc to start with will be a .png
> > file instead. However, if you use this type, you 'must' install the vfpng
> > files I mentioned first, since TMPGEnc doesn't know how to read them
> > without it. If you have lots of drive space (like an 80GB drive or
> > something), then this is going to be a lot less of an issue than for me.
> > lol In that case, you can probably stick with .bmp and be OK. At least as
> > long as you eventually delete all the original images after you have a
> > mpg video you like. ;) lol
>
> That's odd. I'm using POV-ray version 3.5. The tutorial that came with
> version 3.5 said that the older versions required the manual creation of
> separate frames in a sequence, each frame with its own name. The tutorial
> said that the new version I'm NOW using doesn't require that, anymore. The
> tutorial said that I do not need a separate batch script and no external
> sequencing programs. Apparently, the command line can be used to activate
> an internal animation sequence that causes POV-ray to automatically handle
> the animation loop details for me. All I'd need to put into the ini file
> are "Initial_Frame=1 Final_Frame=20" if I wanted to generate 20 frames for
> the animation. I could also have the option of putting "Initial_Clock=0.0
> Final_Clock=2.0" if I wanted the clock to cycle through values other than
> the default of just 0.0-1.0. Then, I also have a third option of adding
> "Subset_Start_Frame=7 Subset_End_Frame=12" if I wanted to view just frames
> 7-12 in an animation of about 20 frames. After that, I just render the
> whole animation at once. I don't think your explanation coincides with the
> version of POV-ray I'm using. Do you recognize any of the stuff I put up
> above?
>
>
Ok, yes, you can use the command line parameters to specify both file
type, the number of frames, etc. I am used to using the GUI and frankly
never saw any real point to running it from the command line, so
basically using the command line in this case is just like using the INI
file. All the INI file really does is provide POVRay with the command
line options in a file you can run from the GUI. The results are exactly
the same.
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott nous apporta ses lumieres ainsi en ce 2004/05/18 17:10... :
>In article <web.40aa75bc27c58a6a6b9afb860@news.povray.org>, nomail@nomail
>says...
>
>
>>>Ok.. First off, it can't 'run' POV files. It can only take images and
>>>compress them into a video stream. So, what you need to do is run the
>>>clockdemo.ini file inside POVRay. The ini file includes the information
>>>needed to tell POVRay how many frames to create, etc. These frames will
>>>probably be called something like clockdemo1.bmp, clockdemo2.bmp, etc.
>>>You need to select the clockdemo1.bmp file in TMPGEnc, since that is the
>>>'first' image in the sequence you want to make into a movie. TMPGEnc will
>>>then run you through a series of screens for various settings, unless you
>>>know what you are doing, ignore these. Finally it will reach a screen
>>>with the 'output file'. This will likely be something like clockdemo.mpg,
>>>so unless you want to name it something else, you can also leave that
>>>alone. TMPGEnc should then read in each file one at a time, until it
>>>reaches that last bmp file with clockdemo in its name, followed by a
>>>number. Really simple. ;)
>>>
>>>Now, as for the .ini files in povray. Most do not include a line
>>>specifying the 'type' to produce. This means that unless you have done
>>>what I did and edited povray.ini to change the default to png (I did this
>>>because I don't have the space for the 100+ images some animations
>>>generate), it will default to the 'system' type, which in windows is
>>>.bmp. If you change this default in povray.ini or in the clockdemo.ini,
>>>then of course the file you tell TMPGEnc to start with will be a .png
>>>file instead. However, if you use this type, you 'must' install the vfpng
>>>files I mentioned first, since TMPGEnc doesn't know how to read them
>>>without it. If you have lots of drive space (like an 80GB drive or
>>>something), then this is going to be a lot less of an issue than for me.
>>>lol In that case, you can probably stick with .bmp and be OK. At least as
>>>long as you eventually delete all the original images after you have a
>>>mpg video you like. ;) lol
>>>
>>>
>>That's odd. I'm using POV-ray version 3.5. The tutorial that came with
>>version 3.5 said that the older versions required the manual creation of
>>separate frames in a sequence, each frame with its own name. The tutorial
>>said that the new version I'm NOW using doesn't require that, anymore. The
>>tutorial said that I do not need a separate batch script and no external
>>sequencing programs. Apparently, the command line can be used to activate
>>an internal animation sequence that causes POV-ray to automatically handle
>>the animation loop details for me. All I'd need to put into the ini file
>>are "Initial_Frame=1 Final_Frame=20" if I wanted to generate 20 frames for
>>the animation. I could also have the option of putting "Initial_Clock=0.0
>>Final_Clock=2.0" if I wanted the clock to cycle through values other than
>>the default of just 0.0-1.0. Then, I also have a third option of adding
>>"Subset_Start_Frame=7 Subset_End_Frame=12" if I wanted to view just frames
>>7-12 in an animation of about 20 frames. After that, I just render the
>>whole animation at once. I don't think your explanation coincides with the
>>version of POV-ray I'm using. Do you recognize any of the stuff I put up
>>above?
>>
>>
>>
>>
>
>Ok, yes, you can use the command line parameters to specify both file
>type, the number of frames, etc. I am used to using the GUI and frankly
>never saw any real point to running it from the command line, so
>basically using the command line in this case is just like using the INI
>file. All the INI file really does is provide POVRay with the command
>line options in a file you can run from the GUI. The results are exactly
>the same.
>
>
In the windows version, there is a "command line" box nexe to the quick
res drop-list. For a 20 frame animation you just put +kff20 there, start
the render, sit back, and you get your 20 frames animation.
You can input parameters far longer than what you can see in the box,
separate each parameters by a space.
Look section 5.2.1 (Animation Options) in the documentation.
+kfi<val> = initial frame
+kff<val> = final frame
+ki<float> = initial clock
+kf<float> = final clock
+sf<val> = start subset frame (+sf0.<val> for % position)
+ef<val> = end subset frame
+kc = cyclic animation
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
