Subject:Reopening files in SF

Posted by: Russell

Date:9/4/2000 9:27:00 PM

We record a file in SF, then save then open the same file in
Wavelab to make some changes that arent as good in SF. Make
the Wavelab changes, save then open again in SF....ughh big
problems....the file opens REAL slow. If we open direct then
on screen its says "0%" until the file has been completely
processed (this can take a very very long time - it opens
roughly in real time i.e 4 minute track takes 4 minutes to
open). Or we open "normal" and on screen it says "100%" but
nothing happens for the same long long time e.g 4 minutes.
Initially we thought the system had hung but its just
opening the file and not telling us.
If we open the file, close it and then reopen - the file is
still really slow to open - in fact nothing comes up on
screen and the system is effectively unusable until the file
has been opened up - then it suddenly appears on screen.

Have we missed a setting or something? Surely SF can cope
with files going to another program and then back in again?

Subject:Re: Reopening files in SF

Reply by: ATP

Date:9/5/2000 5:37:00 PM

i'm guessing here, but could it be that you've set Wavelab to work in
32 bit mode, whereas Sound Forge only supports 16 bits?

or try opening the file in Direct Mode in SF. it'll open much faster
now, but since it reads and edits directly on the HD a system crash
could severely damage your file. if you have a reasonable stable
system you needn't worry....much. ;)

Russell wrote:
>>We record a file in SF, then save then open the same file in
>>Wavelab to make some changes that arent as good in SF. Make
>>the Wavelab changes, save then open again in SF....ughh big
>>problems....the file opens REAL slow. If we open direct then
>>on screen its says "0%" until the file has been completely
>>processed (this can take a very very long time - it opens
>>roughly in real time i.e 4 minute track takes 4 minutes to
>>open). Or we open "normal" and on screen it says "100%" but
>>nothing happens for the same long long time e.g 4 minutes.
>>Initially we thought the system had hung but its just
>>opening the file and not telling us.
>>If we open the file, close it and then reopen - the file is
>>still really slow to open - in fact nothing comes up on
>>screen and the system is effectively unusable until the file
>>has been opened up - then it suddenly appears on screen.
>>
>>Have we missed a setting or something? Surely SF can cope
>>with files going to another program and then back in again?
>>
>>

Subject:Re: Reopening files in SF

Reply by: Russell

Date:9/6/2000 5:31:00 PM

ATP wrote:
>>i'm guessing here, but could it be that you've set Wavelab to work
in
>>32 bit mode, whereas Sound Forge only supports 16 bits?

Thanks for that hint, we will have a look at that and see if it helps

>>or try opening the file in Direct Mode in SF. it'll open much faster
This doesnt help at all - opening in direct mode makes no difference,
it is still VERY slow to load. Only when another change is made in SF
AND subsequently saved (updating peak file?) does direct work
properly.
>>now, but since it reads and edits directly on the HD a system crash
>>could severely damage your file.
Yeah - not good but sometimes worth the risk -

Subject:Re: Reopening files in SF

Reply by: ATP

Date:9/8/2000 8:40:00 PM

What are your system specs? Maybe your computer's too slow (though I
think you'd have noticed that. :)

Is this particular file the only one taking so long to load, or do
you have problems with every wave file?


Russell wrote:
>>
>>
>>ATP wrote:
>>>>i'm guessing here, but could it be that you've set Wavelab to
work
>>in
>>>>32 bit mode, whereas Sound Forge only supports 16 bits?
>>
>>Thanks for that hint, we will have a look at that and see if it
helps
>>
>>>>or try opening the file in Direct Mode in SF. it'll open much
faster
>>This doesnt help at all - opening in direct mode makes no
difference,
>>it is still VERY slow to load. Only when another change is made in
SF
>>AND subsequently saved (updating peak file?) does direct work
>>properly.
>>>>now, but since it reads and edits directly on the HD a system
crash
>>>>could severely damage your file.
>>Yeah - not good but sometimes worth the risk -
>>

Subject:Re: Reopening files in SF

Reply by: MJim

Date:9/10/2000 12:57:00 AM

Yes, use the direct mode, SF has a recovery feature to protect your
files in crashes. It works, I've been there and use direct mode
exclusively for the great time savings & reliability. Also check your
default Temporary Storage Folder under Options/Preferenced/Perform.
This MUST be on the same hard drive that you are saving your files to
or it is very slow to open files as they have to be copied to the
default hdd before opening. Not important which directory you use so
long as it is on the same hard drive that your files are on.

Russell wrote:
>>We record a file in SF, then save then open the same file in
>>Wavelab to make some changes that arent as good in SF. Make
>>the Wavelab changes, save then open again in SF....ughh big
>>problems....the file opens REAL slow. If we open direct then
>>on screen its says "0%" until the file has been completely
>>processed (this can take a very very long time - it opens
>>roughly in real time i.e 4 minute track takes 4 minutes to
>>open). Or we open "normal" and on screen it says "100%" but
>>nothing happens for the same long long time e.g 4 minutes.
>>Initially we thought the system had hung but its just
>>opening the file and not telling us.
>>If we open the file, close it and then reopen - the file is
>>still really slow to open - in fact nothing comes up on
>>screen and the system is effectively unusable until the file
>>has been opened up - then it suddenly appears on screen.
>>
>>Have we missed a setting or something? Surely SF can cope
>>with files going to another program and then back in again?
>>
>>