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

[IDV #YLI-186553]: comedy of errors saving a 77 frame movie capture

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDV #YLI-186553]: comedy of errors saving a 77 frame movie capture
  • Date: Fri, 01 Mar 2013 10:00:19 -0700
> It's an 18 frame Ruc bundle. But the specific displays aren't the point.
> 
> The point is that I made a 77 frame movie, rotating and zooming and turning 
> on more displays and repeating the loop, and accumulating the frames. With a 
> pretty big window. Then it was impossible to write the frames into a movie, 
> despite the preview looking good.
> 
> You could test large movie capture with any bundle.
> 

Brian,
    I tested the WRF model with 144 frames and saved as animation GIF,  no 
problem at all.


Yuan
> 
> Sent from my iPad
> 
> On Feb 28, 2013, at 4:17 PM, "Unidata IDV Support" <address@hidden> wrote:
> 
> >> I got no error messages, just unreadabale movies of every format I tried .
> >> And no individual images written to the folder where I tried to put them .
> >
> > Brian,
> >    If you can create a bundle, I would like to test it locally.
> >
> >
> > Yuan
> >>>> * in .gif, the later frames are all this
> >>>> [cid:4b2cd80e-0a1a-4b9e-85d5-d95c7f8fae24@amazon.rsmas.miami.edu]
> >>>
> >>> Brian,
> >>>   If each frame was created correctly, I suspect that there is some 
> >>> memory issue when creating the movie. Did you get any error message?
> >>> Yuan
> >>
> >> Hope you could see the image I attached about .gif. It looked like a 
> >> scanline length problem.
> >>
> >> But the individual frames seem OK. Everything was fine in the preview.
> >> And those frames that were bad in the .gif were the OK ones in the .mov 
> >> output. (and vice versa).
> >>>
> >>>
> >>> Ticket Details
> >>> ===================
> >>> Ticket ID: YLI-186553
> >>> Department: Support IDV
> >>> Priority: Normal
> >>> Status: Open
> >>
> >> Brian Mapes
> >> address@hidden or address@hidden
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: YLI-186553
> > Department: Support IDV
> > Priority: Normal
> > Status: Closed
> >
> 
> 


Ticket Details
===================
Ticket ID: YLI-186553
Department: Support IDV
Priority: Normal
Status: Open