Disabling .sfl Files
 

OK I realize these things store information about the videos that would otherwise go in file embedded metadata if my video types supported that, BUT I DON'T CARE. I constantly have to keep deleting the things after I render my projects. Sometimes when I'm trying to get a type of compression down I end up with 30 of these things scattered around.

I haven't experienced any issues with deleting the files, and I'm not concerned about any enhancements they may give my project media view. Can only find info on making new ones from Sony's help program but can't seem to delete using same procedure. Anyone gone through this problem as well?

And sorry if anyone dislikes the fact that I've made a lot of threads lately but I just have a lot to get off my chest at the moment. I've searched through the forums for similar topics before posting.

what version of Vegas ?

try : when you render - uncheck save project media marker in file

|
V

I have version 6. I actually tried that and it still saved the files. I guess project markers aren't the same thing.

Are you talking .sfl or .sfk?

The .sfk files are used to draw the audio waveform and are automatically created. You can delete them all you want and they will be re-created the next time you open the file in Vegas or DVD A. Just leave them until you delete the corresponding video or audio file.

.sfl mostly. I'd rather not have any accompanying files on my projects, files w/e. But yeah the main issue is the .sfl files that are saved with my rendered videos.

Got a reply back from Sony about the issue and they pretty much ignored me and told me that they are important so that projects can reference their files and so forth. So I guess I'm stuck with these little guys. Thanks for all your help anyway peoples.

OK, if Sony "ignored you" then how did you get an answer?
Bottom line is, you need these files. Delete them if you wish, they'll just come back. They're extremely small, so not sure why a mountain is being made of them? They've been part and parcel of how Vegas, Sound Forge, ACID, and all other Sony/Sonic Foundry tools have operated for the past 15 years. While some folks don't like them, I can honestly say that in 8 years of moderating forums related to the Sony/Sonic Foundry tools, no one has ever made quite this much fuss.
Accurate audio is important to most of us, these files give us sample accuracy. No other video tool is this accurate.

I'm really sorry :(

.sfl files ARE a problem
 

Hi Mathew, slightly immoderate and over-defensive answer from DSE I thought.

There are clearly workflow issues with the automatic creation of .sfl files when rendering - particularly when sending files to watch folders. Indeed cleaner 6 watch folders don't work when you render directly from Vegas 6 because they can't handle the sfl's. Vegas 5 had an option to turn these off I believe - why doesn't 6 - or does it?

Love Vegas, but this is my one gripe with the new version. And Mathew you and I are not the only ones (see link below) it is clearly a problem that needs sorting out, not denying.

http://www.sonymediasoftware.com/For...ssageID=399564

Joe

Joe, the original question pointed to .sfk files, which have always existed, and not .sfl files, until Edward asked about .sfl.
.sfl files used to be optional, but no longer are due in part to the way applications within Vegas share pointer information. The "Save Path" option in all of the Sony applications require these very small indicator files.
You may not be aware that at the time of this post, it had been posted multiple times elsewhere.
Either way, it's a trivial matter to delete the .sfk, .sfl, and sfap0 files generated by Vegas or other Sony applications if that's what you'd prefer to do. But the Sony software will always generate them each time you open or render the project.

The reason I originally asked for clarification was because the post title specifically mentioned .sfl files but the contents of the post seemed to relate more to .sfk files. Further clarification revealed he was really meaning the .sfl files but the same holds true for both - they're small, easy to find, easily deleted, and automatically rebuilt as needed.