Long file sequences on OSX sux

[Keyser_Soze]

I’m using a dual 1GHz G4 with OSX 10.2.6
Working with long file sequences (as we often do in this business) is a real pain in the ****! Just to open a folder with lets say a couple of hundred frames of SD would leave me with that bloody spinning little dot for much too long… and this is just on the internal disk. If you would do the same on a mounted network drive you could take a trip to the moon and back and it would still sit there “thinking”.
Does my computer/system need an examination by the computer doctor or does it have something to do with Apple and really bad optimization of OSX? I suspect that cause doing the same stuff in the terminal (or in OS9) feels like flying compared to the “walking-through-mud” feeling you have in OSX.
Somebody with more computer skills than me please let me know what’s going on… I’m ready to smash the Cinema Display and kick my G4 with a steel toe Marten boot.

[John Montgomery]

Agreed 100%. I’ve mentioned to to anyone and everyone from Apple — it is really a shame. Must be all the metadata or something.

I always end up dealing with it using Terminal and access via unix. Not elegant or always practical, but at least there is a semi-workaround.

[spatspit]

i have the same problem accessing my sequence. it takes me doubly as long since im using a single 1 gig g4. I love to know how to access my sequence using the terminal?

thanx for your help.

[Keyser_Soze]

spatspit wrote:

i have the same problem accessing my sequence. it takes me doubly as long since im using a single 1 gig g4. I love to know how to access my sequence using the terminal?

thanx for your help.

There are loads of unix/terminal guides out there, just google. Try this site for some basic commands: http://hotwired.lycos.com/webmonkey/reference/unix_guide/
You can also acces a manual in the terminal. For example, if you wanted more information about the chmod command, you should type: “man chmod” and enter. The terminal can be very useful somtetimes. Good luck.

[Keyser_Soze]

johnmont wrote:

Agreed 100%. I’ve mentioned to to anyone and everyone from Apple — it is really a shame. Must be all the metadata or something.

I always end up dealing with it using Terminal and access via unix. Not elegant or always practical, but at least there is a semi-workaround.

Yeah, I guess we’ll have to use the terminal for now. But what do the Apple guys you talked to respond to this? Will they try to fix it or are they just doing like everybody else… putting their hope to better hardware instead of writing fast code. And I can tell you, faster computers doesn’t help much, I’ve tried a dual G5 and problem is still there. Let’s hope that Panther will do something about it.

[Author]

Posts