Hopefully some Sound Forge (v.6.0) savy folks out there can explain something unexpected on one of my recent recordings...here's a recap of what happened:
I recorded a show as follows:
Sbd>R500 @16/48>RCA analog out>Oade dig mod UA5 @24/48>VX Pocket>SF 6.0
and everything worked fine...basically I was new to the UA5 and a bit distrustful that all would work out, so I put my R500 in front of it to make sure at least a 16/48 master got made. Anyway, all worked out fine and the next night I was at a different venue and didn't have the time or space to set up the UA5 as well, so I ran:
Sbd>R500 @16/48>coax out>VX Pocket>SF 6.0
Now, here's where it got funky - when I opened a new record window in SF for the first set, I noticed it was set up by default for 24/48 as that is what I had run the night before. So I changed the settings to 16/48 and ran the first set without problems. For the second set, I started it up again but this time failed to notice it again had defaulted to 24/48 and for unknown reasons SF still locked in on the 16/48 signal even though it was set for 24/48...I know in the past w/SF, if I try to send it a signal with a different sampling rate then it is set for, it gives me an error message and I have to change the settings to the correct value before I can record, but I had not dealt with this in regards to bit depth before - I just assume it would do the same and give me an error message but apparently not (??). Anyway, the recording ran at 24/48 with an incoming signal of 16/48 and it sounds fine when I listen to it.
So my questions are:
1) Why would SF lock in on a signal that is the wrong bit depth
2) What is the status of my recording - what did it do to covert the 16bit to 24? Is this recording flawed in some way?
Not a huge deal as I have the 16/48 DAT back-up but was perplexed by this when I went to edit the file and noticed it was 24/48...should I toss the 24/48 file and transfer the DAT? Does SF somehow convert the bit depth on the fly?
Thanks for any info ya'll can provide.