[HughH]

Hello,
Just used version 1.04 again on two large TV shows in DC, a week apart. Analog I/O, wc sync, tc chase, no DAW or file operations tested, just file acquisition and chase. Recorded several rehearsals, stop and start, along with the shows, with a different project folder/project file per day. No import/export tested either unfortunately.

First day had some issues with one drive misbehaving, think it was the drive. The operator could not reliably describe "what actually happened", so we're going with the drive scenario. We hope. All other drives were fine, and of high quality (G-Drive).

The gui is still fragile - the track overview indicates you're in a particular spot (little blue rectangle) but it's not always accurate. Unit still occasionally goes out of auto-scroll when you're changing window zooming. That should be a key command although not a toggle.

Takes a little too long to chase tc (I'm used to Nuendo's 1/4 to 1/2 second lock time) but it does the job. The VERY strange chase offset behavior I described earlier has been fixed.

The oddest behavior we've seen has to do with start/stop recordings. This happened during both weeks, with multiple shows, drives, dates, and locations. The track overview is open.
We'll record a bit locked to tc, then stop recording while continuing to chase tc. Sometime later we record again, then stop recording, continuing chase. Sometime later after several of these cycles we notice the first few tracks are contiguous the entire length of the recorded tracks. In other words, if most of the tracks have, for instance, 6 events recorded on them, tracks 1-4 will each be one long contiguous track from the beginning of event 1 to the end of event 6. As we go on with this pattern and record events 7, 8, 9, 10, the track overview will update at the end of each event with the correct tracks, then sometime arbitrarily the contiguous tracks will extend to the end of the new events. As time goes on, the number of contiguous tracks will increase, so that at the end of the day it may be as many as the first 12 or 14 contiguous tracks, or as few as 4. Also arbitrarily, the contiguous tracks may stop extending to new events, although that could have been caused by stopping tc chase at some point.
Looking in the File Manager, normal tracks have files of -
Track48_00
Track48_01
Track48_02
etc., while the contiguous tracks have ONE file of -
Track1_ren_00
with NO additional files.
The "ren" file's size reflects the additional size of when recording was not taking place, but when you play it back during those non-record times there's only silence, no audio. The machine was not recording during the non-record times, and the disk was not being accessed during the non-record times, but when you play them back the disk is being accessed.
Something in the file system is not playing nicely or the operator was accidentally doing something very weird!

I think something somewhere has changed in the Disk Management software - formerly you could plug in a firewire drive, enter Disk Management, right click on the firewire drive or the right section of the bar (usually Disk 1), and select Format. Now when you right click on anything having to do with the firewire drive the menu comes up but it's grayed out. Only by formatting it to "msdos" on a Mac, then mounting on the X-48, can you get the right-click menu to allow formatting. I'm sure it would also work formatting it externally on a PC.
We're using HFS+ drives and attempting to re-format them (to NTFS obviously) on the X-48. Does the X-48 prohibit formatting an HFS+ drive to NTFS? Or has something else changed? Don't know at this time.

Hugh