A question about saving

[shamann]

If I load a loop in the slicer, then hit the save button, it saves an Acidized version of the sample over top of the original file.

Is it possible to change settings somewhere so that the user can specify the save location and filename? If not, could that be added as a feature? I'd prefer not to save over my original loop files if at all possible.

[DarkStar]

no config settings, I'm afraid

What I do is:
copy the original file first and rename it, adding _orig to the file name,
or,
copy the orignal files into a new folder and work on them there.

[R.A.W.]

If not, could that be added as a feature?

that was already requested before and is on the list iirc

[shamann]

copy the orignal files into a new folder and work on them there.

I guess do this as a work-around. Bit fussy though. I've actually only just realized the save button was there, which will be handy for stuff recorded in Liveslice. It's rare that I'll use Acidized loops, but may be handy for some extra editing in Sound Forge.

If Jacob could add a new entry on the settings page for "Set default save directory," that would be the best solution for me. Anyone have any thoughts?

[shamann]

that was already requested before and is on the list iirc

Good news! I should pester Jacob for a view of the list, so that I don't request stuff already on it. I've been using Liveslice daily, so my FR rate has been increasing.

[R.A.W.]

If Jacob could add a new entry on the settings page for "Set default save directory," that would be the best solution for me. Anyone have any thoughts?

yeah, great idea!

that way we could save only the loops in acidized format for live-usage in that dedicated folder leaving the originals untouched. (though the additional acid-info doesn't do anything to the wavs besides changing the header afaik)

[shamann]

though the additional acid-info doesn't do anything to the wavs besides changing the header afaik

True. My thinking is that: 1) if I make changes to slice markers in an already acidized loop, I might want to save that version without changing the original; 2) when reloading a loop later, I might want it to just load with default markers to essentially start from scratch; and 3) I might want to make several versions of the same loop with different slicing options, just for ease of use when reloading them later (say 3 versions with different slice threshold settings).

For that last one, another feature would be to have the saved loops' filenames increment or get tagged/timestamped rather than save over an exisiting file (loop.wav, loop-ls01.wav, loop-ls02.wav, etc).

[DarkStar]

+1 (i.e. I'd like it too)

[R.A.W.]

2) when reloading a loop later, I might want it to just load with default markers to essentially start from scratch;

for that you can set the load-function to "audio only"

but nice FRs, so a +1 from me, too

[DarkStar]

I should have adeded the proviso:
- as long as I can still overwrite the original files when I want to (say, by setting the "default save directory" to blank or spaces)

R.A.W.,
I think that shamann wants to open an ACIDized file, change the slices, save it as a new ACIDIZED file.

Then, later on, open the first ACIDized file again. So, loading "audio only" would not help in this case.