Sizzle scratch

[bigjuggler]

Does anyone know where sizle 0.5 stores it's scratch files. I had to force quit an image export and now it seems that a big chunk of my boot drive is full.

I would like to find the the files and delete them manually.

Thanks.

[galactica]

sorry, i do not. You would think it would be in preferences, but then mine are all greyed out.

id try emailing the author of the app, for sure he/she knows

talus25@speakeasy.net

[BDMTHRFKR]

If you don't get any email response from the author, do a search from the finder, add the criteria "size" and input a number a little bit smaller than what you think the file size is and it should come up. Alternately, if you open up your hard drive and tell the finder to "calculate all sizes" (Toolbar at the top/view/show view options) and sort the window by size that should also give you a good idea where that large file is. Hope this helps!

[WiseWeasel]

My guess is he made it an invisible file (by making it start with a "."), and so you might have to add the visibility criterium of 'invisible items' to that search. It's also possible that Sizzle splits the cache into several pieces for wide filesystem compatibility, and so I'd search for items over 900 MB for the size criterium.

[bullitB]

The files are stored in a folder in /private/tmp.

/private/tmp is emptied on reboots, so you might want to just do that. 8)

[bigjuggler]

Wow, thanks for all the replies. I have rebooted and searched for visible and invisible file sizes over 90 MB.

Found /private/tmp folder (empty)

It seem some other app is the culprit (I have some very large library files).

Thanks again...I guess I got a bit paranoid when i read in the sizzle manual that force quitting the app is a bad idea.

BTW Sizzle is a wonderful app for those of us who can't use iDVD (external burner) and can't afford DVDSP.

[Riot Nrrrd]

Wow, thanks for all the replies. I have rebooted and searched for visible and invisible file sizes over 90 MB.

Found /private/tmp folder (empty).

[13:23] panther:/<4>Contents/MacOS % strings - Sizzle | grep tmp
/private/tmp/sizzle_tmp-%d
/private/tmp/tmpscript-%d.sub

Incredibly poor programming practice, IMHO.

If Sizzle needs separate per-session temporary storage for scratch space during disc image creation or whatnot, Henry either needs to implement Preferences with a Preference for specifying a scratch space directory to use, or else if he needs to leave it hard-coded then it should be changed to /private/tmp/sizzle/sizzle_tmp-%d and /private/tmp/sizzle/mpscript-%d.sub - that way, if you didn't have enough space on your root boot Volume for Sizzle to use for its scratch space, you could create a symbolic link (alias) called /tmp/sizzle to point to another larger Volume, and Sizzle would use that and be blissfully unaware.

If you have the Sizzle 0.5b1 source, you can change the path in the file classes/SZLDisc.m and rebuild it with Project Builder, if you have the Developer Tools installed. (Or Xcode from the Panther 7B85 Xcode CD installed, if you're running Panther 7B85.) You'll also need to edit the project file itself (Sizzle.pbproj/project.pbxproj) in a text editor to change the references to /Users/hmason/Projects to match your own path to the source directory.

(That said, I feel the need to mention this - I just used Sizzle 0.5b1 and did a Save as Disc Image. I then mounted the disc image and DVD Player didn't recognize it as a valid DVD. I pointed it at the VIDEO_TS folder on the mounted Volume and it still complained about not finding valid stuff in it, even though I saw the usual .IFO and .VOB files in it. Caveat emptor.)