[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #AOT-741707]: creating a movie with an isl script

Hi Bill-

> I just started the IDV interactively and followed your instructions. I
> did this with 3
> different memory sizes: 512m (default), 768m, and 1024m. With the first
> two the
> renderer is OpenGL and with the last it is Directx. The latter is what
> I used before
> the support request. There were no messages in the command prompt window
> in any of the three.

Thanks for taking the time to sleuth this.
 
> So, when I specified 1024m I'm thrown into Directx. Does it have
> something to do
> with my pc having only 1.5m or ram and the graphics memory is shared,
> 96m max ?

I would guess so.  We've had other users report that they can't even start the 
IDV when the put the memory up to a certain point.  Remember, Windows 
automatically eats up 500Mb just on principal. ;-)

> After the support request, I thought that memory might be the culprit,
> so I tried
> 768m. And that let the bundle complete as intended.
> 
> Does it make sense that the images are 'blank' with Directx (1024m
> case) ?

Not sure why they'd be blank.  You could try running with the -Dj3d.rend=d3d 
option with 768m memory and see if they are still blank.  I'm guessing they 
will be okay and that it's a memory/texture size issue.

You just need a bigger machine. ;-)  

Any frost up there yet?

Don

> Unidata IDV Support wrote:
> 
> Bill-
> 
> This is Don.
> 
> 
> 
> The info from Don was interesting. However, I have the latest graphics
> driver
> (according to Intel) and my opengl version is 1.3, which is the minimum
> required
> for j3d 1.5.2 (according to the link from Don). (And my directx is
> version 9.0).
> 
> 
> 
> When you run the IDV interactively, use the Help->About menu and look 
> under the System tab.  I think your's will show that your Java 3D Renderer is 
> Direct-X.  On your first report, that's what the information indicates.
> 
> When you run the IDV, look in the command prompt window that runIDV.bat is 
> running in and see if there is a message that says it
> is running in Direct-X mode.  If it has to switch, it usually prints out a 
> message saying that it has to do this.
> 
> recheck your runIDV.bat script or whatever you are using to run the isl from 
> the command line to make sure that Direct-X isn't
> being called.
> 
> otherwise, I'm stumped.
> 
> Don
> 
> 
> 
> So, I believe I am running opengl with my onscreen IDV; but when the
> movie tag
> in the isl file tried to save images directx was invoked. Perhaps the
> large width
> and height triggered this, or low graphics memory, or something else ?
> 
> If the IDV was using directx (onscreen) I would be concerned, but I
> don't
> think this is the case. So, I'm okay with the situation. If you can
> find out anything
> else I am interested, but not concerned.
> 
> Thanks again, Bill
> 
> Unidata IDV Support wrote:
> 
> Hi again Bill
> 
> Here is more information I did not know earlier (passed to me via Don):
> 
> If the version of OpenGL on the graphics card is not what Java3D expects, it 
> will automatically go into Direct-X mode.  So, that would explain how he 
> could be running Direct-X without changing runIDV.bat.  See:
> 
> https://j3d-core.dev.java.net/j3d1_5_2/RELEASE-NOTES.html
> 
> (last sentence in the Windows section)
> 
> -Julien
> 
> 
> 
> Hi, Bill
> 
> 
> 
> I did generate the images and movie, just not as large as I wanted.
> However, this is okay
> because I am developing the code to run on another pc where I have more
> resources.
> I was able to debug the isl script.
> 
> Yes, the movie is as I expect. Thanks for looking at it and finding it
> interesting. I will
> tweak the bundle later.
> 
> I thought that the IDV used opengl by default, however, my error
> message suggested
> that it was using directx.
> 
> 
> If you are running the IDV (out of the box) via the IDV.bat command, I would 
> agree with this statement. You must explicitly choose to run the IDV with 
> Direct3D, and OpenGL is by default. I also agree you are running the IDV with 
> Direct3D. If you did not change the IDV.bat script to explicitly use Direct3D 
> there is a bit of a mystery here for me. I would be curious to know what 
> would happen if you were to start the IDV with the "-Dj3d.rend=ogl" command 
> line option to explicitly choose OpenGL (jre\bin\java -Xmx512m -Dj3d.rend=ogl 
> -jar idv.jar).
> 
> My problem seems to be a lack of ram (and my
> 
> 
> graphics
> memory is shared), but I would update opengl and/or directx if it might
> help.
> 
> 
> Since you are currently running the IDV with Direct3D, an update may be worth 
> a shot.
> 
> -Julien
> 
> Do you
> 
> 
> have any comments ?
> 
> Bill
> 
> Unidata IDV Support wrote:
> 
> Hi again, Bill
> 
> Sorry the movie generation is giving you trouble.
> 
> In the meantime, I have put your movie on motherlode:
> 
> http://motherlode.ucar.edu/repository/entry/get/a.mov?entryid=990734ec-6b4f-4524-92e7-435bfd126049
> 
> Is this the movie you expect to see? (Interesting movie, BTW.)
> 
> Also, here is my ISL script (for what it is worth)
> 
> <isl>
> <bundle file="/tmp/WoMercV1d.xidv" width="1620" 
> height="810"/>
> <pause/>
> <movie file="/tmp/a.mov" imagedir="/tmp" 
> imagetemplate="WoMercV1dy_%count%" imagesuffix="jpg">
> </movie>
> </isl>
> 
> Thanks,
> 
> -Julien
> 
> 
> 
> 
> Julien,
> 
> The documentation is in section 7.1.5, in the description of the movie
> tag:
> "If no file attribute is specified then this just generates the
> images, not the movie.
> For example, you can not specify the file name but do specify the imagedir
> and
> this will generate the images and place them in the imagedir for later
> processing."
> 
> Prior to the error reported previously, I had a java heap error; so, I
> increased memory for the JVM
> to 1024m. Then, the d3d error occurred. However, I was able to complete
> the bundle file and
> determine whether it was functioning correctly.
> 
> After reading your email, I noted that I only needed 586m (not 1024);
> so I changed the memory
> value to 768m. When I opened/ran the isl file, it did create the images
> and a qt movie !
> 
> I guess this is not an IDV problem, and is related to graphics memory.
> 
> Then, I attempted to run the process noninteractive, without opening
> the IDV. It bombed,
> and showed an error message; but it wasn't visible long enough for me
> to read. I guessed that
> the width was too large in the bundle tag. I decreased it from 1620 to
> 620. And that worked.
> 
> I tried adding a path to the movie file name: ${islpath}a.mov ; I don't
> believe a movie file
> was created, but the images were.
> 
> If you have further suggestions, please let me know. Thanks for the
> direction,
> 
> Bill
> 
> Unidata IDV Support wrote:
> 
> Hi, Bill
> 
> This may be a video card issue. I was digging around and found an old post on 
> something similar.
> 
> http://www.unidata.ucar.edu/support/help/MailArchives/idv/msg02416.html
> 
> I would start there and the suggestion pertaining to increasing the memory 
> with the -Xmx1024m JVM option (or something appropriate to the memory 
> capacity of your machine.)
> 
> Let us know if this works.
> 
> Also, about the mistake in the documentation, could you point us to its 
> location so that we may correct the error?
> 
> Many Thanks,
> 
> -Julien
> 
> 
> 
> Full Name: bill fingerhut
> Email Address: address@hidden
> Organization: lyndon state college retired
> Package Version: 2.9 build date:2010-08-07 07:06 UTC
> Operating System: Windows XP
> Hardware: Java: home: C:\Program Files\IDV_2.9\jre version: 1.6.0_20 
> j3d:1.5.2 fcs (build4)
> Description of problem:
> 
> When trying to save images from an animation (movie), using an isl script,
> the images are blank as is the movie.  I see the following errors:
> 
> Fail to lock surface: D3DERR_DRIVERINTERNALERROR
> Fail to lock surface: D3DERR_DRIVERINTERNALERROR
> Fail to lock surface: D3DERR_DRIVERINTERNALERROR
> 
> Here is more detail in case it is needed.
> 
> I'm starting the IDV and reading in my isl script so I can debug
> this. Here is the isl:
> 
> <isl>
> <bundle file="${islpath}\WoMercV1d.xidv" width="1620" 
> height="810"/>
> <pause/>
> <movie file="a.mov" imagedir="${islpath}" 
> imagetemplate="WoMercV1dy_%count%" imagesuffix="jpg">
> </movie>
> </isl>
> 
> The bundle loads correctly and the display is ok. The movie file and
> the image files are created, but are solid black - blank.
> 
> BTW, the user's manual states that the file attribute can be omitted
> if the movie is not wanted and the images are. Omitting file leads to
> an error.
> 
> 
> 
> 
> 
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: AOT-741707
> Department: Support IDV
> Priority: Normal
> Status: Open
> 
> 
> 
> 
> 
> 
> --
> The Fingerhuts
> Saint Johnsbury, Vt, 05819
> 
> email: address@hidden
> 
> 
> 
> 
> 
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: AOT-741707
> Department: Support IDV
> Priority: Normal
> Status: Open
> 
> 
> 
> 
> 
> 
> --
> The Fingerhuts
> Saint Johnsbury, Vt, 05819
> 
> email: address@hidden
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: AOT-741707
> Department: Support IDV
> Priority: Normal
> Status: Open
> 
> 
> 
> 
> 
> 
> --
> The Fingerhuts
> Saint Johnsbury, Vt, 05819
> 
> email: address@hidden
> 
> 
> 
> 
> 
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: AOT-741707
> Department: Support IDV
> Priority: Normal
> Status: Open
> 
> 
> 
> 
> 
> 
> --
> The Fingerhuts
> Saint Johnsbury, Vt, 05819
> 
> email: address@hidden
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: AOT-741707
Department: Support IDV
Priority: Normal
Status: Open