IRIX and Software

Okay - installed and working under kubuntu 7.10. To answer your question, I use jpg when I don't care about quality and lossless tiff when I do.

The new framestore is great... thanks! Pretty much what I had in mind. I'll have to get used to it being manual, but I can see the value of that. I've worked with image playback tools in the past that always automatically kept the previous image in a buffer, so that you could toggle when you hit reload. With the manual approach, you have to *remember* to load the buffer when you reload, but I think I prefer that anyway.

Another issue: I typically save my files in 4-digit padded format (filename.%04d.tif), and I notice that djv_ls thinks there's a break between frame 999 and frame 1000. Likewise, if I have 'Automatically open file sequences' set in preferences, it only loads a sub-framerange (e.g., f0000-0999 if I give a frame between those numbers, even if there are more frames above 999).

For example, say I have 1500 frames in a directory:
clipper.0100-0999.jpg 33.1MB root Seq rwx Sat Dec 22 17:28:55 2007
clipper.1000-1599.jpg 21.68MB root Seq rwx Sat Dec 22 17:29:06 2007


If I force djv_view to load the full range (djv_view clipper.0100-1599.jpg), then it plays them all.


cheers
Mark

Hah! You beat me to it with that preference!

markwend wrote: Okay - installed and working under kubuntu 7.10.

Great, glad to hear it.

markwend wrote: To answer your question, I use jpg when I don't care about quality and lossless tiff when I do.

Ok, both of those file formats should be fine to over-write while viewing.

markwend wrote: Another issue: I typically save my files in 4-digit padded format (filename.%04d.tif), and I notice that djv_ls thinks there's a break between frame 999 and frame 1000.

I was wondering when someone would run into that.

Basically I got too clever with the file sequencing; the software tries to distinguish between sequences with leading zeroes and without, so what's happening is it thinks there are two sequences: 0001-0999 zero-padded, and 1000-1500 without. I should probably change this though, your case seems far more common than someone trying to mix frame padding in the same directory.


Thanks, Darby

Mark,

I just uploaded a new pre-release (djv-0.8.0-pre2) which has a number of fixes, including one for your file sequence problem. If you have a chance, try it out and let me know how it works.


Thanks, Darby

Hey Darby -

Got the new version and it works fine on gutsy. The issue you fixed with sequences over 1000 frames works fine now too. Thanks for that. A few new things...

a) Every time I install a new version, I have to go back and set my preferences all over from scratch. Any way to save preferences when a new version is installed?

b) When I set Mark In and Out points for playback, the Forward and Backward Playback modes obey these points. However, the jog shuttle (as well as right-button jogging) *doesn't* obey the mark in/out points. Is there a specific reason for that? If not, I'd prefer the shuttling to obey the marked points.

c) Here's a funny one. I'm in the habit of feeding a series of images to my own programs using wildcards (e.g., "myprogram file.*.jpg"). Of course, when I do this with djv_view, I get in trouble... it launches separate windows for EACH file that the wildcard expands to. I quickly need to killall in the shell before my machine swaps to death. Unless there's a compelling reason to open separate djv_view sessions with wildcards, it would be really nice to just load up all the files that a wildcard expands to in a *single* djv_view window. If I really want separate djv_view sessions, I launch them with separate commands.

Thanks again for a great and useful program!

cheers and happy holidays,
Mark

markwend wrote: The issue you fixed with sequences over 1000 frames works fine now too.

Cool. Thanks for testing it.

markwend wrote: a) Every time I install a new version, I have to go back and set my preferences all over from scratch. Any way to save preferences when a new version is installed?

Since I'm still making so many changes to the code, that's an unfortunate side-effect for now. But if you want you can try manually copying the previous preferences to the new ones; though that won't always work and could cause some odd behavior. The preferences are stored in your home directory, like:

~/.fltk/djv-0.8-1

So if your previous version was 0.7.4, you could try:

rm -r ~/.fltk/djv-0.8-1
cp -r ~/.fltk/djv-0.7.4 ~/.fltk/djv-0.8-1

markwend wrote: b) When I set Mark In and Out points for playback, the Forward and Backward Playback modes obey these points. However, the jog shuttle (as well as right-button jogging) *doesn't* obey the mark in/out points. Is there a specific reason for that? If not, I'd prefer the shuttling to obey the marked points.

The idea behind that was to allow adjustment of the in/out points after they are set, sort of for fine-tuning the marks. But you're right, it's probably better to keep all the controls consistent; do you think clicking and dragging the playback slider with the mouse should also obey the in/out points?

markwend wrote: c) Here's a funny one. I'm in the habit of feeding a series of images to my own programs using wildcards (e.g., "myprogram file.*.jpg"). Of course, when I do this with djv_view, I get in trouble... it launches separate windows for EACH file that the wildcard expands to. I quickly need to killall in the shell before my machine swaps to death. Unless there's a compelling reason to open separate djv_view sessions with wildcards, it would be really nice to just load up all the files that a wildcard expands to in a *single* djv_view window. If I really want separate djv_view sessions, I launch them with separate commands.

How about if I add a preferences option to combine all the command-line inputs into a single sequence, instead of sending each to a separate window? Note that all of the images need to be the same format though.

I also recently added a different sort of wild-card handling for someone else; sequences can now be specified like "render.#.tiff". Still have to add it to the documentation.

markwend wrote: Thanks again for a great and useful program!

Thanks for the feedback, it's very helpful.


Darby