lsseq-2.4.1 v2.4

This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: James Rowell
A command-line utility for listing image sequences in a compact form.
13.1, 12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11.0, 10 or later
Linux, Mac, Windows
13 Jul 2021


The best such helper script for listing frame-sequences. It closely follows the look and feel of the standard 'ls' command, which means it's easy to switch back and forth between /bin/ls and lsseq in day-to-day use.

Please visit the github page and check out the visible there, it tells you everything you need to know, including how to install lsseq. It's easy!

Glad so many people and studios have used lsseq over the years, I personally find it indispensable when TD'ing jobs. I hope it has been equally useful for you.

Thanks so much and ENJOY lsseq!

Kind Regards,


v2.4.1 update, the package has been restructured and is SUPER easy to install now with python's 'pip'.

BSD 3-Clause License
Please login in order to download these files.


0 # Zach Lewis 2012-05-17 17:30
This is great - thanks for this.
I modified your script to have the nuke listing use a "-" instead of a "," in between the frame numbers, so I could copy the list from the terminal and paste directly into the nuke dag - works like a charm!
0 # James Rowell 2012-05-17 19:38
Thanks Zach - you know, I should make it '-' in the posted version too. Not sure why I have it being a "," although on the command line (nukev) a "," works. Anyway, I'll fix the source for everyone else too. Thanks again!
0 # James Rowell 2012-05-17 20:10
Hey everyone - I made the fix that Zach suggested, but Nukepedia's versioning numbering system here is too rough a granularity for how I've numbered my versions. So to get the latest here's a link:

When I get enough fixes and changes from people's suggestions/com ments/etc. to warrant going to v1.8 then I'll repost that version via Nukepedia's GUI on this site, in the mean time, I'll keep updates posted with links like I have here.

0 # Zach Lewis 2012-05-19 09:25
Thanks again, man. This has been super useful; already using it in production, and am loving it.
Here's another suggestion (unless it's already an option, and I just missed it): maybe make a "shell" format argument that doesn't print the frame range and replaces the frame number variable with an asterisk? So, we'd have something like...

lsseq -p -R -f shell


Would be friendlier for performing batch operations on image sequences in the terminal. Just a thought.
0 # James Rowell 2012-05-19 10:57
Great idea Zach - but I think I'll call the format "glob", since that's the unix term for filename expansion.
0 # James Rowell 2012-05-19 11:15
Afterthought: Note Zach, that globbing with a '*' may match filenames that you don't intend to match. It will match all your intended files, but could match more. Say (in your example) you have some files called : sc010_0010_beau ty_directDiffus e_v035.extraStu ff.*.exr in the same directory. Then the globbing pattern above in your example will also match this one.

If and only if the frame numbers are padded, then you can use this (for example):


And it will match only what you want. But, this doesn't work for non-padded frame numbers.

Tricky - I have to think about it.
0 # Zach Lewis 2012-05-19 12:39
oh, interesting. Good call.
Maybe aaa.[0-9]*.exr ?
0 # James Rowell 2012-05-19 12:58
Unfortunately globbing doesn't behave like a regular expression. Your expression above only means, match exactly one zero-through-ni ne character, followed by anything (or nothing). It doesn't mean zero or more characters of "zero-through-ni ne", as you might think.
0 # James Rowell 2012-06-16 10:14
I just posted a new version of lsseq. 1.8, which includes a glob format and also includes a command line argument to allow the interpretation of "_" as a separator between the filename and the frame number. The default is to be strict about "." - and there's a command line for that too to be explicit and allow for well behaved use of aliases. I believe my submission of 1.8 has to be reviewed before it shows up, but that should be coming shortly I'm guessing. Enjoy!! James.
0 # James Rowell 2012-06-24 05:15
I just posted an update with a bug fix. The bug was that when listing directories with an absolute pathname on the command line, the prepend path options weren't behaving properly - they are now. Since you can't post minor updates on nukepedia then please find the lastest version (1.801) here:

+1 # James Rowell 2021-04-22 00:12
Ha! Just posted 9 years worth of updates! (That is, v2.1.0 above.)

Please check out my github repo to follow future additions/impro vements etc. there!


You have no rights to post comments

We have 2008 guests and 85 members online