I have been a long time TimeTrax user, but frankly lost interest as the Recast betas came out, So my XM and Timetrax were off for several months. I decided to jump back in over the holidays, specifically with the intent of capturing the 5,002 song DeepTrax marathon that started 1/1/2006.
I loaded the most current production Recast 1.4 (not the beta) with no difficulty and I though everyting was solid, but about 2 days into recording I noticed a large number of Not Recorded - Too short messages. Watching the display, it would be in a song and then after some time (I saw 15sec to 1:15min) it would act as if there was a song change when in fact it was still in the same song. This resulted in loosing a lot of songs (too short) and the few that did record were all bad (just the last part of the song).
A restart of Recast seemed to solve the problem. Now a few days later and it did it again. I've dropped back to 3.4.7 hoping it will be better.
Anybody ever seen this before?
I'm running on Windows Server 2003 Enterprise Edition (don't ask) and TimeTrax is the only thing running on this box, no other applications, no other users.
PS-already opened a support ticket with this info
I loaded the most current production Recast 1.4 (not the beta) with no difficulty and I though everyting was solid, but about 2 days into recording I noticed a large number of Not Recorded - Too short messages. Watching the display, it would be in a song and then after some time (I saw 15sec to 1:15min) it would act as if there was a song change when in fact it was still in the same song. This resulted in loosing a lot of songs (too short) and the few that did record were all bad (just the last part of the song).
A restart of Recast seemed to solve the problem. Now a few days later and it did it again. I've dropped back to 3.4.7 hoping it will be better.
Anybody ever seen this before?
I'm running on Windows Server 2003 Enterprise Edition (don't ask) and TimeTrax is the only thing running on this box, no other applications, no other users.
PS-already opened a support ticket with this info
Last edited: