Evaluating Fasoft for Podcast applicatio
I will be doing one to two hour recordings of lectures and presentations to be used as podcasts. I saw that Fasoft software has built in compression and equalization, and it appeared to be easy to use. I have not found that to be true with the Bias LE that came with my Tascam US-122 A to D converter for my specific use.
Question: Can I just set Fasoft to “record,” and have it continue to record until I press “stop?” With Bias LE, you have to set how long the recording will be, and I can not predict recording length with the lectures I am recording.
2.) Is there any limit or technical issues with long recordings using Fasoft, or digital recording for that matter (provided that I have enough hard drive storage?
3.) I see that Fasoft works with the Tascam US-122. Are there any problems or considerations with using this device with Fasoft?
I appreciate your time and opinions in getting me started. I come from autiotape background, and I need a simple and reliable means of making these recordings in conference halls.
Eyup!
Welcome to the forum!
I use NTrack for home recordings, so I do not have direct experience of the type of application you describe.
However, several users do use NTrack in “live” situations and, as far as I am aware, do not suffer problems caused by NTrack.
In previous builds, the file size limit was 2GB, but this no longer applies. File size is now limited by the resources of your computer.
So, provided you have an already stable and robust system, NTrack will certainly do what you require.
I have no experience with the Tascam unit, but I see no reason why it should not work.
Potential problems may be drivers, you would be wise to test the system thoroughly.
Steve
<!–QuoteBegin>
| Quote |
| Question: Can I just set Fasoft to “record,” and have it continue to record until I press "stop?" |
Yep. The longest I’ve done would be about an hour and a half, of 8 tracks at once. Be prepared for a bit of a wait when you press stop though, as ntrack has to draw the wavs afterwards. It takes a while, and you’ll think it’s crashed, but just sit on it for a bit.
I have not run into any limits (I think I’ve recorded in excess of 2 hours) but I do suggest stopping and restarting at every opportunity. I occassionally (ver. 3.3) have cases where the .wav files get messed up or some other error happens. It is better to find this right away and confine the problems to a section of the total session. Usually just restarting the program clears the problem (it may be related to disk fragmentation, I am unlikely to have it on a freshly formatted disk).
Jim