TT Recast 1.5 Beta
Installed TT Recast Beta 1.5:
Recevied error '91' right after registering - registration responded successfully so I am not sure if this was error that was waiting in the background for the registration window to close or if it was due to the registration itself. TT was purchased for me as a gift a while back.
Still see CPU Spike and LONG delay in getting the Timer Schedule to open. This might be due to hitting the REGISTRY for this information (which I beleive is a complete MISTAKE - but thats just me) however - on a dual core Athlon, 2.2GHz, 2GB RAM, with a Raptor 74GB 10k RPM drive. This delay is just insane.
In order to READ this graph, the FIRST SPIKE on BOTH CPU windows is from the TaskManager just Loading (this happens to everyone). The Time Trax Scheduler Spike happens in the SECOND CPU window and is that the ENTIRE second spike. The Spike goes away when the Scheduler finally opens.
For comparison, Here is what TaskManager Looks like when you load Adobe Image Ready CS-2 (9)
2 Spikes, 2 CPUs, both SHORTER than loading the SCHEDULER from Time Trax.
My Peanut Gallery Recomendations:
1. After the FIRST LOAD, cache location of the XM PCR / Direct unit on which port and check there first, the length in time it takes to scan seems to be FOREVER.
2. Remove the Schedule from the REGISTRY. Not only does it NOT belong there, but it would be MUCH easier to use a comma or TAB seperated file, in which, users could at least use to import and export the scheduler to another machine for upgrades and computer swaps.
3. I am not sure if RECAST set this or I accidentally set this in the OLDER version I jus tupgraded from - but recast should not be by default set to the
HIGH PRIORITY task level, this could cause people with less powerful machines to be stuck.
4. Drop Down boxes for the Presets got 'sticky'. Clicking and holding on the slider to drag down to the BPM channel became a huge chore. The slider locked on something else and did not scroll. Then, when it was high-lighted, I just tried to use the UP/DOWN arrows to change it, and it bounced out of being 'selected' and then NOTHING was selected. Forcing me back to clicking the box again and try to scroll the channels.
5. When changing the recording the AREA to another DRIVE, Time Trax wanted to restart. Why is this? Why not just use the portion of code that changes and makes new directories to force this shift/change to the new drive. For example, if you are running to record on C, and choose D, you stop timeshifting, change location, start time timeshifting, pop-up message box that reminds the user to clean up the old directories. Just bothersome that the application needed a restart - you change folders before and after recordings a drive is extremely similiar.
6. When a scheduled recording is taking place, it is almost impossible to stop it. YOU should be able to OVER RIDE this without going into the Scheduler to turn it off, then waiting for the Time Trax Recast APP to react to the change and stop recording.
Its gonna run over the weekend and we will see what happens.
Currently, its running on a:
Athlon x2 64 2.2Ghz
2GB Ram
ASUS A8N-Premium Mobo
OnBoard Sound by RealTek
Nvidia 7800GT (BFG)
(1) 74GB Raptor 10K RPM SATA drive (OS - Programs)
(1) 250GB Hitachi 7200 RPM SATA Drive (TT recording area and other Media)
(1) Sony DVDR
(1) NEC DVDR
The Process Thread Priority is set to ABOVE NORMAL.