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:
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.