Elsewhere there was a report:
Just got my second service call and third Aspen dropped off at my house, last two have been swapped out due to issue where some recordings get only a minute long recording of a black screen and the info of the recording says words to the effect " Recording was interrupted, some data may have been lost" No other shows where recording at this time and no one has been home, hard drive is more then 50 % free.. Tech was going to bring a Whistler out but told me that they don't have them in Victoria yet, grr
I too just had a spate of these over a two day period. My Pace Aspen (my second) also, later that day. lost the video on HDMI (I tried two different cables) and on the coax output had the audio from one channel and a shaky still image from a different channel. I have had Shaw reset the Aspen and we'll see if the problems repeat.

I too just had a spate of these over a two day period. My Pace Aspen (my second) also, later that day. lost the video on HDMI (I tried two different cables) and on the coax output had the audio from one channel and a shaky still image from a different channel. I have had Shaw reset the Aspen and we'll see if the problems repeat.Now, even after the unit had been reset yesterday, I have had recurrences of the lost program problem, i.e. programs that won't play and that have the progress bar to the far right, including one tonight that shows as a 60 minute recording in the list of recorded programs, with no indication of any recording problem, and with MPEG file size of 0 {0} and Trick file size of 0 {0}.

Edit: This last program resulted from a series recording set up for "all channels" and results from the PVR's attempting to record the program on a channel to which we don't subscribe. Some of the other problem recordings are also from channels to which we don't subscribe. The PVR should ignore such channels for series recordings and warn us for non-series recordings. Other occurrences of these problems occurred on channels to which we do subscribe. In one case my daughter saw the recent War of the Worlds (old version) recording taking place, successfully, at the 45 minute mark. It showed up that way in the recorded program list too. When we went to watch it later it too started out in pause mode with the screen showing the progress bar at the far right. The recorded program listing now showed only 1 min and displayed the dreaded " Recording was interrupted, some data may have been lost" message. Not all problem programs have this message associated with them.

My first Pace Aspen started failing at about the two month mark and it is now two months since I got this one. I actually bought it about a month ago and I am not a happy camper. Since Shaw seems no longer to be offering the Aspen, in favour of the newer units, the odds of getting a problem-free replacement, if I have this unit swapped out too, are decreasing rapidly.

Twice now, in the last week, while watching TV, my Pace Aspen has lost all Video on its outputs. The HDMI output just loses the video completely. The first time I also checked the coaxial output. It was locked on a still image of one channel with audio from a different channel. I didn't check the component output. The second time I checked the component output and it was at best a very grainy image and at worst it was almost completely blank, but it did match the selected channel. I didn't check the coaxial output this time. I had Shaw do a reset after the first occurrence, which cleared the problem and I disconnected the power to the unit myself the second time and that cleared the problem also.

"Series Recording" does not work properly on this Aspen. Trying to do a series recording of Bones on all channels (new episodes and repeats) has littered my hard disk with attempted "recordings" from channels to which we don't subscribe (e.g., Canadian time shift channels).

As well there is a sprinkling of other unsuccessful, unplayable, "recordings" from channels to which we do subscribe, many of them, but not all, Bones episodes too. The problems occur on a handful of channels, Space (subscribe), Diva (free preview?) and a couple of others. A very few occurrences of this problem also occurred with regular recordings, e.g., a recent "War of the Worlds" broadcast.

The two resets for my video problems also didn't help with this problem.

I have had this unit for about two months now, having bought it a month ago. My first unit started failing at about the two months mark also, having rendered unwatchable previously watchable recorded programs.

Edit (26 Oct 2009):
Shaw tech has just told me that he'll replace it with a Motorola tomorrow. Now I have to try and see whether I'll lose any features or not.

Thanks to all, especially Lindend, for help with my Aspen.

Edit: (29 Oct 2009)
After a couple of days with a Motorola 3416 I am going to take my chances with a third, alas refurbished (Shaw seems to have no new ones left), Pace Aspen. The viewing experience was, for me, far better with the Aspen. The advantages are:

Aspen's "zoom" feature (which coupled with my TV's aspect ratio control), gave me the ability to stretch/zoom more effectively (the controls on my TV weren't sufficient with the Motorola),
much more rapid, and smoother, HDMI handshaking between the PVR and my TV,
the availability of an RF "pass through" when the Aspen was turned off.
a host of little things

I am now hoping that I won't, in the end, be sorry.

FYI,

We recently introduced our Home Content Sharing product. Its a client/server (NAS) based solution that lets you network multiple clients (via Ethernet or MoCA) and share content between clients in the same home. If you're interested in using this type of technology in your existing Pace STB, please drop by the Home Content Sharing thread (http://www.avsforum.com/avs-vb/showthread.php?t=1191788).

I'm getting that audio cutout on mine too. At least I hope thats what the issue is.

After having had my third Aspen (refurbished) for only a few days it has started exhibiting the same problem that my first (brand new) Aspen did after two and one half months, namely programs that record, are initially watchable and then become unwatchable with MPEG and Trick file sizes of some-size {0} (reported in post #194 in this thread). Shaw is coming tomorrow to bring me Aspen #4.

Edit:
It seems my three problems are each somewhat different from each other:

Based on recordings that worked, the file sizes should be:

MPEG File Size size1 {size1}
Trick File Size size2 {size2}

but were (for the problem recordings)

1st unit:
MPEG File Size size1 {size1}
Trick File Size 0 {0}

2nd unit:
MPEG File Size size1 {0}
Trick File Size size2 {size2}

3rd unit:
MPEG File Size size1 {0}
Trick File Size size2 {0}

My second unit also occasionally lost video on the HDMI output and, at those times, had garbled video on the composite and RF outputs.

The serial numbers of the defective units are:
PAZP00005678
PAZP00021035
PAZP00028548
Has anyone else had any of these units? Do they just keep recirculating, i.e., being returned, "refurbished", placed with a customer, returned, ...?

Edit: Just received my fourth Aspen. Its label says it was made in March 2009 but its serial number is lower than my (third) unit's which was labeled as being made in February 2009. ???? Oh well, as long as it proves to be reliable (Its hard drive appears to have been reformatted twice already so what are the chances?).

It would be very useful to see all three pages of the content listing for that recording if/when the problem occurs again.Lindend: Roginator and I have provided (posts 245 (http://www.avsforum.com/avs-vb/showthread.php?p=17333755#post17333755), 246 (http://www.avsforum.com/avs-vb/showthread.php?p=17334935#post17334935)) some screen shots relating to our problems. What do they tell you about what could be going on?

Given the semi-systematic, somewhat consistent, corruption of the file system data that seems to be happening, I'd put my money on a software bug (non-robust exception handling?). I could be wrong though. It wouldn't be the first time, nor the last. ;)

I am also quite puzzled. Why are some of us afflicted with these problems on Aspen after Aspen - some people have reported trying 6 or 7. Considering the hundreds (thousands?) that must be in use, why aren't there more reports of these problems? Are people just living with these problems? I really don't understand and am getting quite frustrated.

What do they tell you about what could be going on?

Sorry. Somehow I missed those screen shots. The diags listing reveals two separate issues.


QOS. Looks like it recorded OK, but the MPEG file is no longer on the filesystem. What firmware revision do you have? Depending on the firmware release, there may be a hidden screen to monitor filesystem activities at boot.
Private Practice. This never recorded properly. Unclear why/how that happened.



Given the semi-systematic, somewhat consistent, corruption of the file system data that seems to be happening, I'd put my money on a software bug (non-robust exception handling?).

Your initial thoughts are right. It definitely is a software bug(s) so replacing h/w isn't going to help. I've seen very sporadic reports of issue #2 but we've not isolated the scenario down. For issue #1, we've added a number of fixes in our maintenance releases to address these issues and added the hidden screens to monitor filesystem activity to track why the file was removed by the filesystem. So really, firmware release #s may shed some light on why some see the problem and others don't.

... What firmware revision do you have? Depending on the firmware release, there may be a hidden screen to monitor file system activities at boot.My earliest problems (the recordings that disappeared) were with firmware 12.09, The QOS and Private Practice etc. problems occurred with 13.56 and that is the firmware my current Aspen is running. I have only had it for a couple of days now and so far it is behaving. (But it is a refurb unit that has already been reformatted twice, so I surmise some previous owner(s) has/have had problems and returned the unit. Time will tell.)Your initial thoughts are right. It definitely is a software bug(s) so replacing h/w isn't going to help.I wish I had know this before I gave up my brand new, pristine Aspen for the grungy, scratched, in-one-case-dented, refurbished units I have had since then.
So really, firmware release #s may shed some light on why some see the problem and others don't.Hmm, I'm not sure that I understand this. I have had some of these problems with both firmware releases. Many others must be running these firmware releases too. If the problems aren't also related to some hardware malfunction why aren't they more widespread?

I am still wondering why I (and those few others reporting them in forums such as this) should see so many of these problems over two firmware releases and three Aspens?

Or are these problems well-known and widespread?

... Depending on the firmware release, there may be a hidden screen to monitor files ystem activities at boot...
How would I access that? Also somewhere, someone mentioned checking to see if the defragmenter was running? Is this checked on the processes diagnostics page or where? Thanks.

How would I access that? Also somewhere, someone mentioned checking to see if the defragmenter was running? Is this checked on the processes diagnostics page or where? Thanks.

From the diags main menu (not the dashboard), press 8 then 2 (i.e. 82) and hit enter. If it shows something, please do some screen caps.

Didn't work for me. Pressing 8 then 2 then OK/SELECT just took me into the screen for whatever main menu item had been highlighted. Pace Aspen running 13.56. I have had the "refurbished" machine (manufactured March 2009 - 2 reformats already) only a few days and it hasn't yet failed for me. I was trying to get a "normal" baseline.

Edit: Works on a Summit, though.

Here is a baseline of an 82 HDD Drive Statistics screen for a new Pace Summit with Shaw Expander, with no recordings. Sorry, I cannot get the spacing quite right. I think we'll be needing this because I am reading reports that the problems afflicting the Aspen may also be afflicting the Summit.

Question Linden: Does invoking this screen just provide reports or does it effect repairs too?
--
HDD Drive Statistics

internal HDD is none
external HDD is/dev/sda
df.
Filesystem 1k-blocks Used Available Use%
/dev/ram0 4608 4608 0 100%
tmpfs 1408 88 1320 6%
none 16384 0 16384 0%
/dev/mtdblock4 1964 112 1852 6%
/dev/sda3 9733120 888 9732232 0%
===========================================
mount
/dev/ram0 on / type squashfs (ro)
tmpfs on /var type tmpfs (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /mnt/memory type tmpfs (rw)
/dev/mtdblock4 on /mnt/nvram type jffs2 (rw)
/dev/sda3 on /mnt/hd_ext type xfs (rw,noexec,rtdev=/dev/sda4
============================================================ =====
head -1 /dev/sda PACE-2-1
head -1 /dev/sda5 hd_extSuccessfulMount
============================================================ =====
fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 1 8001 83 Linux
/dev/sda2 2 2 8032+ 5 Extended
/dev/sda3 3 1215 9743422+ 83 Linux
/dev/sda4 1216 121601 967000545 83 Linux
/dev/sda5 2 2 8001 83 Linux
cd /mnt/hd_ext; du | tail -1
32?.
============================================================ =====
gathering external recording statistics
external mpg count 0 (0 zero length)
external nav count 0 (0 zero length)
external xml count 0 (0 zero length)
============================================================ =====
ls -Rail .mnt/hd_ext/lost+found
/mnt/hd_ext/lost+found:
133 drwxr-xr-x 2 0 0 6 Jan 1 2000 .
128 drwxr-xr-x 6 0 0 106 Nov 8 19:57 ..
examining defragger files
cat /mnt/gpfs/shutdown_Log
============================================================ =====
cat /mnt/gpfs/missing_files
============================================================ =====
cat /mnt/gpfs/internal_format_info
============================================================ =====
cat /mnt/hd_ext/shutdown_log
============================================================ =====
cat /mnt/hd_ext/missing_files
============================================================ =====
cat /mnt/hd_ext/external_format_info

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Unformatted external disk
/var/tmp/external-disk-status: bad
Unable to retrieve external_format_info prior to reboot!
/etc/real_prepare_disk called for /dev/sda at Sun Nov 8 19:55:28
============================================================ =====
cat /mnt/system/shutdown_log
============================================================ =====
cat /var/tmp/internal_boot_info
============================================================ =====
cat /var/tmp/internal_format_info
============================================================ =====
cat /var/tmp/external_boot_info

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes


Device Boot Start End Blocks Id System
/dev/sda1 1 1 8001 83 Linux
/dev/sda2 2 2 8032+ 5 Extended
/dev/sda3 3 1215 9743422+ 83 Linux
/dev/sda4 1216 121601 967000545 83 Linux
/dev/sda5 2 2 8001 83 Linux
Last known boot status of /dev/sda3 was: FormatComplete
mounting /dev/sda3 to replay log
Wrote hd_extMount to /dev/sda5

Wrote hd_extRepair to /dev/sda5
Repairing /dev/sda3
/usr/sbin/xfs_repair -r /dev/sda4 /dev/sda3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem free space and inode maps...
- found root inode chunk
Phase 3 - for eac AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- process newly discovered inodes///
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost_found (if it exists) ...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
Phase 5 - rebuild AG header and trees...
- generate realtime summary info and bitmap...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- ensuring existence of lost+found directory
- traversing filesystem starting at / ...
- traversal finished ...
- travesrsing all unattended subtrees .
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verufy and correct link counts...
done
Wrote hd_extMount to /dev/sda5

/dev/sda3 mounted successfully
/dev/sda3 /mnt/hd_ext xfs rtdev=/dev/sda4 1 1 added to /var/tmp/fstab
Wrote hd_extSuccessfulMount to /dev/sda5
/mnt/hd_ext mounted successfully.

Mounted external disk
/var/tmp/external_disk_status: pass
============================================================ =====
cat /var/tmp/external_format_info
============================================================ =====
cat /var/tmp/disk_drv1
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_UnMount:2350 unmounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
impl_DISK_Mount:2303 mounting /mnt/hd_ext
============================================================ =====
cat /var/tmp/disk_drv2
============================================================ =====

From the diags main menu (not the dashboard), press 8 then 2 (i.e. 82) and hit enter. If it shows something, please do some screen caps.My Summit with Shaw Expander had a problem recording last night, long before the drive filled up even once. This one got the error message about an "interrupted recording" and had OK MPEG File Sizes but had Trick File Sizes 0f 0 {0}.Screen shots and more info are coming later today. Unfortunately I have already looked at the HDD Drive Statistics once without capturing the screen shots. I hope that hasn't its compromised the second time I look at it, when I will take screen shots. If we're "lucky" another instance of the problem will manifest itself. I have developed the feeling, but don't yet have any evidence for it, that shutting down (and subsequently restarting) the Summit may have something to do with the problem(s). I noticed no problems with any of my test recordings until after I had turned the Summit off and turned it on again, but I cannot be sure I didn't just miss noticing the problem.

Linden, what information from the screen shots do you wish to see. Any other procedure I should, or should not, be following, e.g., shut down, or not, re-enter diagnostic,s or not, reboot, or not?

Linden, I have sent you a PM with a link to the screen shots for the two problems I have just had with my Summit PVR and attached Shaw (Western Digital) Expander. Providing them here is just too awkward. Both recordings were attempted recordings from channels to which we subscribe and, this time, both show as 1 minute recordings with the error message "This recording was interrupted while in progress. Some of the program may have been lost.". In both cases the programs recorded, properly, from the same channels, at the same time, on my 4th Aspen, which, after my having had it for about a week, hasn't failed yet.

The House recording problem from yesterday:
MPEG File Size 196608 {196608}
Trick File Size 0 {0}

and a new Bones recording problem from today:
MPEG File Size 0{0}
Trick File Size 0 {0}

This one got the error message about an "interrupted recording" and had OK MPEG File Sizes but had Trick File Sizes 0f 0 {0}.

Did your box crash and reboot during the recording? Normally, that's the only way to get an interrupted recording. If the box reboots during the recording, the file size info in the content listing most likely won't be valid.

Did your box crash and reboot during the recording? Normally, that's the only way to get an interrupted recording. If the box reboots during the recording, the file size info in the content listing most likely won't be valid.Nope - no crash or anything that I noticed. The uptimes for my Summit seem to be consistent with my controlled reboots - that is power disconnects and reconnects. I'll double check to make sure.

It's too bad that the 82 key sequence doesn't work with the 13.56 Aspen firmware.
- - - - - - - - - - - - - - - - - - - - - -
Edit:
I have checked the various screen shots and according to those the Summit did not crash during the failed recordings, if the up times on screen 25 are to be believed.

2009/11/09 00:11:14: System rebooted

2009/11/09 19:00:15: House started recording from channel 208 WUHFD,
2009/11/09 19:00:15: House ended recording from channel 208 WUHFD,
- according to screen 22 Content Listing as per 2009/11/10 08:50

2009/11/10 01:00:14: Bones started recording from channel 217 SHOWD
2009/11/10 01:00:15: Bones ended recording from channel 217 SHOWD,
- according to screen 22 Content Listing as per 2009/11/10 08:47

2009/11/10 08:56:36: screen 25 shows up time 1 days, 18:45:33, i.e., 32:45:22, i.e. back to 2009/11/09 00:11:14

Nope - no crash or anything that I noticed. The uptimes for my Summit seem to be consistent with my controlled reboots - that is power disconnects and reconnects. I'll double check to make sure.

The other way to get an interrupted recording would be an EAS. Do you know if an EAS happened in that time frame?

Linden, I have sent you a PM with a link to the screen shots for the two problems I have just had with my Summit PVR and attached Shaw (Western Digital) Expander.

I looked at the screen shots from your PM. The diags indicated that this is not a data corruption or loss scenario. From the firmware perspective, the recording completely cleanly (i.e. the guide just aborted the recording early).

Unfortunately, this version of TV Guide has a known bug that can cause this to happen (although it is reported to be relatively rare, I know of several people who have run into it). I can't definitely say its the EPG bug, but it seems like it might be.

What is an EAS?
I have to wonder if this EPG problem is being reported only for Pace, or also for Motorola implementations, of the EPG? Am I correct that each company does its own implementation? Or do all the boxes run s/w provided by the EPG vendor/supplier (whatever the correct term is)?
I'll post again if I get any of the other problems.
Thanks, Linden.

What is an EAS?

Emergency Alert System.

I have to wonder if this EPG problem is being reported only for Pace, or also for Motorola implementations

This particular issue has been reported on both.

Or do all the boxes run s/w provided by the EPG vendor/supplier (whatever the correct term is)?

Depends on who your cable provider is. TV Guide is used by a significant number of North American Cable providers and is the guide your currently running. The same version of guide is used by both Pace and Motorola and is written by Rovi.

Does the Pace gear support I-Guide A28 with web based DVR programming?

I looked at the screen shots from your PM. The diags indicated that this is not a data corruption or loss scenario. ...
Is there any significance to the fact that the 82 HDD Drive Statistics screen (for cat /var/tmp/disk_drv2?) had entries around the time of my failed Bones recording

2009/11/10 01:00:14: Bones started recording from channel 217 SHOWD
2009/11/10 01:00:15: Bones ended recording from channel 217 SHOWD,
- according to screen 22 Content Listing as per 2009/11/10 08:47
HDD Drive Statistics listing:
Tue Nov 10 01:00:16 2009
: Unsol Sess: CRD_RECORD_TERMINATED
Tue Nov 10 01:00:16 2009
: Unsol Sys: CRD_SYSTEM_NORMAL

but not for the failed House recording?

2009/11/09 19:00:15: House started recording from channel 208 WUHFD,
2009/11/09 19:00:15: House ended recording from channel 208 WUHFD,
- according to screen 22 Content Listing as per 2009/11/10 08:50
HDD Drive Statistics listing: none

In fact the listings jumped straight from the 8th (23:08:17) to the 10th (01:00:16) of November.

Linden, obviously there are recording failures about which Pace can do little or nothing. The best example of these are the problems due to the Guide's scheduling series recordings on unsubscribed channels.

For those other problems that might be Pace's responsibility, what information can people who experience them usefully post from the 22 Content Listing and the 82 HDD Drive Statistics listings (and other sources?) to help in tracking these difficulties down?

I prefer the viewing experience of the Pace products, Aspen and Summit, over the Motorola 3416 but people seem to be reporting that the 3416s do not exhibit these recording problems to the same extent as the Pace units. One person is reporting failures on a Pace box that were concurrently successfuly recorded on a Motorola box, for example.

We appreciate your help so far and would like to know how we can help to debug these problems. Surely with the number of people reading and contributing to this forum, the number of people experiencing these problems and with the addition of the 82 HDD Drive Statistics listing we should be able to help track something that would be of use to the Pace folks.

Kritiker,


I prefer the viewing experience of the Pace products, Aspen and Summit, over the Motorola 3416 but people seem to be reporting that the 3416s do not exhibit these recording problems to the same extent as the Pace units. One person is reporting failures on a Pace box that were concurrently successfuly recorded on a Motorola box, for example.

I've done some more digging around for you. We do have a Pace specific bug in this area (this explains why some are seeing it more on Pace boxes). I thought the bug was fixed in your Shaw firmware build, but it won't be available until the next maintenance release. The symptoms you describe appear to match what was fixed in the bug but I can't say with 100% certainty that the issues are the same.

Will update the forum when the maintenance build is released.

Great news!
Aspen, Summit, others?
Thanks again.

Linden, FWIW, I have noticed a discrepancy, on my Summit, between the ordering of programs in the list of recorded programs and in the 24 Content Listing. It does appear that all 64 programs appear on both lists but in a different order. Is this significant?

[snip - I am told that the different order is not significant. To avoid unduly cluttering this thread I have deleted the table showing this discrepancy.]

Also, again FWIW, after a power failure, irrespective of how long the successful recording was, only the first two minutes seem to be playable. As well, the file sizes seem to be
MPEG File Size size1 {size1}
Trick File Size 0 {size2}

I have just received this confirmation of problems from Pace Technical Support about my Aspen. It is most disturbing.

We do have an issue with black/ blank recordings and have some improvements to the firmware that we will be supplying to Shaw in the near future. However the scale of the problem as I understand it is at around 3% of recordings are potentially affected, ie failing to black.:mad:

At least, to Pace's credit, they have acknowledged the problem and are working on it.

Furthermore, Tech Support suggests leaving the Aspen on full-time,
This has been demonstrated to reduce the number of recordings that fail to black.

Edit: Summits too!

I picked up a new 787x tonight and the CCard Health is only showing Fair. Is that normal for this model? All the premium channels, and DVR seem to be functioning normally. VOD menus work, but VOD show play back produces a error screen.

Cable Card Status
Connection= Present
Validation State= Unknown (7)
Object Name= MCblCard
Software Version= 02.65 (0x09010007)
Manufacture ID= Motorola
Hardware Version= p=MCPOD v=01.00 r=07
Card Ready= Yes
Operating Mode= NPH

VOD play back error screen:
In order to start cable service for this device, please contact your cable provider
Cablecard ID and Unit Address are listed.

UPDATE: after 4 calls to Mediacom and lots of frustration and being hung up on, my Cable Card now has a VALID state (who trains these people???).

My 787x DVR is showing the following input name on my TV display ("Reference Sw"). The 779x DVR shows the following name "Dual HD/PVR STB". These names are sent over HDMI from the source device.

Also the TVGUIDE Cablebox setup/Configuration screen shows Firmware "99.99" where as the 779x DVR shows "12.56" on that same screen. The Dashboard shows "12.61" on the 779x. Did a marco get left to a default value when the 12.61 FW version was compiled?

The 787x still has the same bug as the 779x series in that the current HD program you are watching shudders for 20-30 secs when a back ground HD show starts recording.

Anyone else noticed this?

PS - At least it doesn't seem to shudders the current show when a background HD recording ends.

My 787x DVR is showing the following input name on my TV display ("Reference Sw"). The 779x DVR shows the following name "Dual HD/PVR STB". These names are sent over HDMI from the source device.

Also the TVGUIDE Cablebox setup/Configuration screen shows Firmware "99.99" where as the 779x DVR shows "12.56" on that same screen. The Dashboard shows "12.61" on the 779x. Did a marco get left to a default value when the 12.61 FW version was compiled?
My 787 was just updated with 15.66 firmware. I had no problems with the 14.07 version it replaced, although 30-second skip and replay do seem a little faster now. I believe the box is running i-Guide v. 75.73.

You must not have Mediacom. I don't think they believe in using new FW.

I see the 14.xx FW release notes fixed this that could be the cause "Frozen/stuttering video after a channel change."

Toadtaste, When will Mediacom customer's see an update to the 787x FW?

Lindend,

This 12.61 FW has the same HDD spindown issue the 779x had. This FW is supposed to disable that feature, but the HDD optimization routine puts the HDD to sleep it appears when it completes. (The display shows the "-" animation when the power on is pressed.)

With the HDD spindown enabled I got the TVGOS HDD full message and it didn't record the show just like the 779x would do. Since I have disabled HDD spindown, I have not gotten the TVGOS HDD is full error.

Also, thie 787x is starting the HDD optimization every evening about midnight (I am assuming that is what it is, the HDD keeps making a racket when the DVR is shut off) and it takes forever to complete. I am still watching TV at this time and the external HDD noise is annoying. Why is this version doing so much HDD optimization? If it would wait these new shows would get viewed and erased.

I purchased an extrernal drive that can use ESATA connection, 1TB in size. The PACE 787x that I have does not seem to recognize it. My cable company tech support said it was too big, and to try splitting. The 787x still doesn't see it. They then recommended that I consult with this thread to solve the problem. Any help would be greatly appreciated.

I purchased an extrernal drive that can use ESATA connection, 1TB in size. The PACE 787x that I have does not seem to recognize it. My cable company tech support said it was too big, and to try splitting. The 787x still doesn't see it. They then recommended that I consult with this thread to solve the problem. Any help would be greatly appreciated.

I hope you didn't purchase a USB/eSata combo HDD. (They have interface issues that cause eSata errors.) The WD external combo drives don't even get recognized.

The fist post lists the verified by PACE HDDs that will work.

Yes, it is a combo unit, Sans Digital MS1UT with a Seagate drive inside.

rbrand, there are only very few combo drive enclosures (among them some Vantec enclosures) reported to work, at least initially. The problem is that combo drive enclosures have firmware to control the various interfaces (USB, FIrewire , eSATA). This firmware may interfere with the Pace unit's ability to control the external HDD correctly, or at all.

eSATA-only drive enclosures (generally) have no such firmware. The enclosure just provides power to the drive and a direct cable connection between the SATA connector on the drive and the eSATA connector on the enclosure. There is no processing of the signal done. An eSATA connector is simply a more rugged form of SATA connector designed for more frequent plugging and unplugging.

Also remember that external drives are not hot-swappable when used with Pace PVRs. The Pace PVR must be turned off before connecting or disconnecting the external drive.

Do an Internet search on "Adding a SATA Drive To Pace HDPVRs" (include the quotes) for further information. I'd hve PMed you the link but you don't have PMing enabled. I don't think I'm allowed to post the link here.

My original motive to add an external drive was to be able to keep recorded programs rather than lose them when the DVR crashes, which btw has been happening about every 6 mos. However all the research seems to indicate that may not be possible since the external gets formatted each time it is hooked up to another box.

Is it possible to get the data from an external HD to a computer then to a DVD so I can have a backup?

rbrand, the files are encrypted (and tied to a particular PVR) so that even if you can get at them (by hooking the drive up to a Linux PC), you can't do anything with them.

Can anyone please tell me which colorspace these units output over hdmi? YpbCbR, or whatever it is, or RGB, it would be a huge help.

Can anyone please tell me which colorspace these units output over hdmi?

Its RGB.

on 19 November 2009: ... Will update the forum when the maintenance build is released.We have been waiting quite some time already for a Summit (and others) firmware update. For me the problems started in June of 2009 with my Aspen. It now seems that Pace's testing of the Summit update is still several more weeks away and deployment (Shaw for me) will take even longer.

I have found, in other contexts, that such delays often represent a disregard for the end customer, a focus on other issues/problems deemed more important (Home Content Sharing???) and/or a company in financial disarray. Do any of these apply here? If not, then why is it taking so long?

I am extremely disappointed at the length of time that Pace is taking to solve the problems that we have reported here and elsewhere, problems that are an ongoing source of irritation. I had expected better from Pace. :(

With build 12.61, the PACE box flakes out about every 15 days and needs to be rebooted to work correctly again.

Symptoms, the video will freeze on live tv or trying to playback a recording. The sound will continue to play. FF a recorded program will show the video, but pressing play will result in a frozen still image (but sound continues). Changing channel on live TV will result in a still image of the new channel or the video may play a few seconds then freeze for over 20seconds then might play 1-2 seconds and freeze again (sound continues).

I am connected via HDMI through a AVR and HDMI switch. The only anomaly in the diag screen I noticed was that the HDMI repeater status was false. Unplugging HDMI cable and waiting a few seconds then replugging it fixes the repeater status to true. But the problem persists.

All the Dashboard statuses are Green.

This has happened three times and at about the same interval each time (15 days).
I was wondering if my box has the wrong SW loaded on it. The lead tech said that the box should do some long load with the display counting when it was first connected, but my unit never did this and was ready to go. With the issues I reported here: http://www.avsforum.com/avs-vb/showthread.php?p=17646579#post17646579, I wonder if my unit still has PACE engineering build on it or something.

WhatHappened, which Pace box do you have? Your cable provider can do a full reset that might help. Generally your box will have downloaded, and be running, the latest firmware build that your cable operator has deployed - perhaps not necessarily the absolute latest. Linden has posted, in the first post of this thread (http://www.avsforum.com/avs-vb/showthread.php?t=1053440), links to the firmware pages for a number of Pace boxes.

You might also, if you haven't already done so, try running the box directly into the TV for a while (I know, that defeats the purpose of your setup) and/or try a different set of HDMI cables or even use them for different connection in your system.

I did a little further checking and are you still talking about your TDC787X (aka Aspen)? If so, firmware version 12.61, according to Pace TDC787X (aka Aspen) Release Notes Thread (http://www.avsforum.com/avs-vb/showthread.php?p=14384853#post14384853), seems a bit old. The current version seems to be 14.06-14.14,14.27.

WhatHappened, which Pace box do you have? Your cable provider can do a full reset that might help. Generally your box will have downloaded, and be running, the latest firmware build that your cable operator has deployed - perhaps not necessarily the absolute latest. Linden has posted, in the first post of this thread (http://www.avsforum.com/avs-vb/showthread.php?t=1053440), links to the firmware pages for a number of Pace boxes.

You might also, if you haven't already done so, try running the box directly into the TV for a while (I know, that defeats the purpose of your setup) and/or try a different set of HDMI cables or even use them for different connection in your system.

I did a little further checking and are you still talking about your TDC787X (aka Aspen)? If so, firmware version 12.61, according to Pace TDC787X (aka Aspen) Release Notes Thread (http://www.avsforum.com/avs-vb/showthread.php?p=14384853#post14384853), seems a bit old. The current version seems to be 14.06-14.14,14.27.

Kritiker,
Thanks for your effort (I know my version is old, but there is nothing for me to do except post here). I am very familiar with these PACE boxes and am posting for Lindend to hopefully answer or acknowledge that behavior is already fixed. I hope that Mediacom employee in charge of these DVRs and their FW version deployed would also respond (he use to frequent these PACE boards.).

WhatHappend, Does calling Mediacom and having them do a full reload (not just a reset - not sure of the precise terminology) not update the firmware? The list of resolved problems for the later firmware versions seems extensive.

Can someone else who is a Mediacom customer in Southern Minnesota confirm the firmware version they are running for the TDC787X (aka Aspen)? Will Mediacom confirm this for you? Good luck!

Recently my 787 has been showing random and intermittent video and audio glitches. To eliminate the cable signal as the problem, I tuned clear QAM channels on my TV and found no evidence of glitching or transmission errors (error counts = 0). I noticed that the signal level recently has gone up to +10dBmV (also confirmed by TV and cable modem), so I inserted an 8dB attenuator, and bingo - problem solved, no more glitching. Any cable box worth its salt should be able to handle signal levels in the range of +/-15dBmV, but the 787 -at least my particular unit - cannot.

I've also recently had some other issues. Several times over the past few weeks, video has gone blank (menus and guide still displayed normally though), and a cold reboot was needed to restore normal operation. I've also had several erroneous 1-minute recordings, although that could be a firmware/software issue (currently running 15.66 firmware; 75.73 i-Guide software). Finally, in the process of troubleshooting the glitch problem, I attempted a scan disk but gave up and cold rebooted after the box stuck at 10% for several hours.

WhatHappend, Does calling Mediacom and having them do a full reload (not just a reset - not sure of the precise terminology) not update the firmware? The list of resolved problems for the later firmware versions seems extensive.

Can someone else who is a Mediacom customer in Southern Minnesota confirm the firmware version they are running for the TDC787X (aka Aspen)? Will Mediacom confirm this for you? Good luck!

You don't understand Mediacom. The software they use in their PACE 779x is about 2 years old. Mediacom says it is Pace that has not provided any new updates, but the PACE release thread shows newer versions for the 779x.

I expect that my version in the 787x is the latest Mediacom has rolled out. I had every reboot/reset that Mediacom CSR could send done when I got the box to get the cable card error status and VOD to work.

The reason for the old versions on Mediacom networks is probably because they are running a very old iGuide version and PACE will not build that old iGuide in the newer builds due to all the bugs. I think Mediacom is about 4 version back on iGuide 74.64 - 3337 (I've see Comcast is running 78.44 - A28p0-2.09).

((I wonder if it cost money to update the Head-ends to the latest iGudie versions and Mediacom being in constant financial trouble can't afford it?))

My sympathies, WhatHappened!

Does the MacG Client for GuideWorks run on this box? It's to allow for EBIF applications such as Caller ID on TV.

Is Version 34.1 compatable? What about I-Guide A28, or is it still stuck on 25.2, or 27.1?

I have a Western Digital DVR Expander, model WD5000F032. I have used it for a couple of years with the TDC778x, but that DVR went bad and my cable company swapped it out with the TDC787X. My external drive won't work with this new DVR.

When I hook it up to the DVR and plug it in, the DVR doesn't work. In diagnostics the DVR is listed as not existing or not enabled, I don't remember and no hard drive, internal or external is found. If I remove the external drive after powering down, everthing works like normal.

I checked to make sure that the SATA port is enabled on the 787x.

Any ideas?

I have been very patient, waiting for oft-promised firmware updates for my Pace Summits. In the meantime I have been put to considerable inconvenience over the continuing firmware problems, which for me started last June with an Aspen and have continued, unabated, on my current Summits with Shaw (WD) Expanders (external HDDS).

I have written to both Shaw and Pace Technical Support telling them that I hope these firmware updates will actually be in place by the end of March or I will have no choice but to move to a competitor, which I am very reluctant to do, but what choice am I being given? Repeated assurances that corrective firmware updates are coming soon have been nothing but empty promises. (I have no illusions that my stated intention to switch to a competitor will have any actual impact. It would just get me out of this ongoing situation.)

After 8 months I think I am entitled to consider the Pace PVRs to be lemons.

Does anyone have any positive light to shed on this situation?

I have been very patient, waiting for oft-promised firmware updates for my Pace Summits. In the meantime I have been put to considerable inconvenience over the continuing firmware problems, which for me started last June with an Aspen and have continued, unabated, on my current Summits with Shaw (WD) Expanders (external HDDS).

I have written to both Shaw and Pace Technical Support telling them that I hope these firmware updates will actually be in place by the end of March or I will have no choice but to move to a competitor, which I am very reluctant to do, but what choice am I being given? Repeated assurances that corrective firmware updates are coming soon have been nothing but empty promises. (I have no illusions that my stated intention to switch to a competitor will have any actual impact. It would just get me out of this ongoing situation.)

After 8 months I think I am entitled to consider the Pace PVRs to be lemons.

Does anyone have any positive light to shed on this situation?
I've had a 787 for the better part of a year, and it's been mostly reliable, although not perfect. I've used it both with and without a WD My DVR Expander with few problems. It always records the programs I schedule without issues. A few months ago, the 787 got DVR amnesia and forgot it was a DVR, requiring a reboot. A few days ago, the annoying DVR full message popped up, but that's a known i-Guide software issue, not the 787 firmware (currently running firmware v. 15.66; i-Guide v. 75.73).

I've had a 787 for the better part of a year, and it's been mostly reliable, although not perfect. ...787 firmware (currently running firmware v. 15.66; i-Guide v. 75.73).I should, of course, have been more specific. The Aspens I had were TDC776D (aka Aspen Embedded) running, when I got rid of the last one, firmware 13.56 (last updated approx. May 2009) not the TDC787X (aka Aspen) running firmware 15.66 (updated more frequently and more recently. 15.66 doesn't even appear in the Release Notes thread yet) you have. My Summit's firmware is still in its initial release, 14.34 (from about Sept 2009).

Your comments are actually somewhat encouraging. Thanks.

I just got a 787x from my cable provider, Insight. So far, I'm not completely sold on it. It's been a bit too unstable for my liking. I've had it for less than a week and it's already crashed (or in one instance, completely bugged out) twice.

The first time was Sunday night (a day after I got it). I was recording the Academy Awards in HD while simultaneously recording a movie (not HD, digital). I had intended to watch the Oscars later, but ended up watching live instead. When the ceremony ended, I went to the DVR listing page, while the program was still recording (I had set it to go an hour beyond the reported end time), and deleted the program. Big, huge, mistake. On the my previous Motorola box, this would simply stop the recording and delete the program. On the Pace, the whole box just hung. Every once in a while, I would get window of a few seconds to perform some actions before the box would hang again. I eventually selected the DVR program list and noticed that the movie that was recording on the other tuner now had about 8 entries, each for one minute, in addition to the first 2 hours. Every time the box hung, it created another 1 minute entry for the movie. I eventually gave up and was forced to unplug the box. Once the box reprogrammed itself, I checked out the DVR program list. The Academy Awards program listing was still there, as was about 12 listings for the movie I had been trying to record. I deleted all of them and surveyed what was left on the DVR. I had three other HD recordings, each an hour long. Though the listing was there for each program, when I tried to play them, I just got a blank screen, fast forwarding immediately took me to the end of the program and rewinding immediately took me to the beginning of the program. Deleting them had no effect on the "% Full" measurement. All of the HD recordings were gone. All of my other non HD recordings appear to be fine.

Just now I had a second incident. I got home and turned on the tv. There was an HD movie recording on the second tuner, and the primary tuner was on channel 1 (essentially the home page). I typed in the channel for ESPNHD. Immediately, the box hung. It stayed that way for over a minute and then reset itself. It's very disturbing when you can't perform an action as simple as watching one channel while recording on another without the cable box completely losing it.

My firmware revision is 13.53. Is this version anywhere close to recent? Are these known issues? Have they been fixed already?

If anyone has any info, I'd appreciate it.

Thanks.

While the Pace TDC787X (aka Aspen) Release Notes Thread (http://www.avsforum.com/avs-vb/showthread.php?p=14384853#post14384853) lists versions 13.33-13.42 as the most recent, techweb's version, a few posts back, is apparently 15.66 for the 787X.

With build 12.61, the PACE box flakes out about every 15 days and needs to be rebooted to work correctly again.


I have found the issue why the box needs to be rebooted periodically to keep using it. It appears that there is a major memory leak. The box ran too low on memory this time in only 6 days of use (normally been 15days). I had the box on more for the last 6 days.

System Free memory is 118196KB after a reboot (DVR fully works).
System Free memory is 6584KB when the DVR becomes unable to play video (sound still works.)

Based on the Memory config screen, it is the SDRAM that is all used up.

PACE, Has this issue been resolved in newer FW builds? The release notes don't talk about a memory leak.

I have found the issue why the box needs to be rebooted periodically to keep using it. It appears that there is a major memory leak. The box ran too low on memory this time in only 6 days of use (normally been 15days). I had the box on more for the last 6 days.

System Free memory is 118196KB after a reboot (DVR fully works).
System Free memory is 6584KB when the DVR becomes unable to play video (sound still works.)

Based on the Memory config screen, it is the SDRAM that is all used up.

PACE, Has this issue been resolved in newer FW builds? The release notes don't talk about a memory leak.

There are actually two issues going on. I just had the issue where just certain channels won't show video (audio is fine). The free memory was around 110,000KB. The channels that won't play video live also will not play video from previous recording recorded on those non-working channels.

Rebooting returns the box to a working condition.

This issues happened less then 24 hours after the previous reboot.

I have Mediacom aswell so i feel the other peoples pain... But one problem I am having is on HD channels and issues on like MTV channels is the sound will cut out for 1/2-1 second and sometimes the picture will pixel/block while the sound cuts out. This only started when i got a Vizio 55" VF550M Tv. On my 32" Emerson LCD TV i had i didnt have this problem. Only thing chaged was the TV and now showing this problem. Have restarted. Checked all connections ect and all is fine. The connection is through HDMI. I'm not sure if this is a Box issue or a TV setting issue. I have messed with some of the sound settings on the tv but still having issues.

Also those with mediacom i have emailed a few times asking for Firmware upgrades and they said they only have the firmware that comes with the box from the factory and they dont get anything from pace to do updates. I contacted Pace and they said they send upgrades to Mediacom and they are the only ones that can upgrade the box.

I have Mediacom aswell so i feel the other peoples pain... But one problem I am having is on HD channels and issues on like MTV channels is the sound will cut out for 1/2-1 second and sometimes the picture will pixel/block while the sound cuts out. This only started when i got a Vizio 55" VF550M Tv. On my 32" Emerson LCD TV i had i didnt have this problem. Only thing chaged was the TV and now showing this problem. Have restarted. Checked all connections ect and all is fine. The connection is through HDMI. I'm not sure if this is a Box issue or a TV setting issue. I have messed with some of the sound settings on the tv but still having issues.

Also those with mediacom i have emailed a few times asking for Firmware upgrades and they said they only have the firmware that comes with the box from the factory and they dont get anything from pace to do updates. I contacted Pace and they said they send upgrades to Mediacom and they are the only ones that can upgrade the box.

The person that does the Mediacom updates for these boxes contacted me and said we should have a new update in 1-2months (that was about 1/2 a month ago.)

I don't understand why Mediacom is so far behind the other cable companies on their DVR software versions. If I had to guess, it would be not allocating enough resources to check each version prior to releasing them on the system.

The issue with this is that we don't know what version that will be and PACE is probably ignoring issues reported on FW version as old as 12.61. If the version Mediacom release still has the same issues then it could be another 18months before we would ever see the fixes for these issue deployed. Seems like a bad way to do business.

The person that does the Mediacom updates for these boxes contacted me and said we should have a new update in 1-2months (that was about 1/2 a month ago.)

I don't understand why Mediacom is so far behind the other cable companies on their DVR software versions. If I had to guess, it would be not allocating enough resources to check each version prior to releasing them on the system.

The issue with this is that we don't know what version that will be and PACE is probably ignoring issues reported on FW version as old as 12.61. If the version Mediacom release still has the same issues then it could be another 18months before we would ever see the fixes for these issue deployed. Seems like a bad way to do business.

Yeah, being in an apartment i'm limited to Mediacom or Rabbit ears so they got me over the barrel. For some of the problems i have been having i will be calling mediacom here tomorrow and throwing a few more complaints in the hat about the service.


EDIT: I went into the Diagnostics Dashboard and just sat here and watched it for abit and every so often the IB1 TUNER SNR and IB1 TUNER ERRORS goes to Fair... Is there any numbers anywhere in the diagnostics anyone wants me to post up to help determine any issues. Now they went to poor and my Short Term Errors are 25851. What would cause this. How can i fix it.

Thanks,
Randy

I would just like to point out that the latest version could have worse software issues than the one currently running. This is a good example of that. One of the issues in the latest version is that the DVR will randomly go 100% full when it is obviously not full.

I would just like to point out that the latest version could have worse software issues than the one currently running. This is a good example of that. One of the issues in the latest version is that the DVR will randomly go 100% full when it is obviously not full.


That is interesting... Every-time that issue comes up Lindend always says it is a TVGOS issue and not a PACE bug. Does that mean all the DVRs (Motorola included) sharing that TVGOS version have the same issue?

Does it have that issue more than the PACE 779x DVR did? What kind of frequency have you seen that issue on the later software version?

I have seen that issue 1-2 in the last 4 months on the 12.61 version on the PACE 787x. (That was less than the 779x).

That is interesting... Every-time that issue comes up Lindend always says it is a TVGOS issue and not a PACE bug. Does that mean all the DVRs (Motorola included) sharing that TVGOS version have the same issue?

Does it have that issue more than the PACE 779x DVR did? What kind of frequency have you seen that issue on the later software version?

I have seen that issue 1-2 in the last 4 months on the 12.61 version on the PACE 787x. (That was less than the 779x).
I remember getting erroneous DVR full messages on a Moto 6412 I had several years ago, so it is an i-Guide bug that Rovi seem to be unwilling or enable to exorcise. It seems to happen less often with newer guide software versions, but it still pops up occasionally.

The issue was that it would not go away without a format of the drive if i remember correctly. Suffice to say we are waiting for the next release.

The issue was that it would not go away without a format of the drive if i remember correctly. Suffice to say we are waiting for the next release.

Well that can happen to any i-Guide DVR. To clear the issue, you have to delete some recording. If you just hit the DVR full message with a DVR that has no recordings, you will have to take extra steps to resync the iGuide to the real OS file system. Format is one way, but I would think that Erasing GPFS Partition would also work (I haven't tried it).

I just had the issue last night with the 12.61 FW with the full DVR message that started over-night. So I have a recording that is 10hours long on HDD that doesn't show up in the i-Guide DVR list (you have to use diag menu to see it). If it was a weekday and I wasn't there to stop the background recording the next morning that gets started by the iGuide when the full happens, that recording could have filled an entire standard PACE DVR without external HDD. When you reboot the DVR the background file (with no name) gets erased.

If the frequency of the DVR full messages is not greater than before, I think you should release the new FW.

Is Mediacom putting pressure on Rovi/Macrovision/Gemstar/Comcast or who ever makes the i-Guide SW about fixing the false full DVR issue?

Well had mediacom come out and check everything. Says everything looks good. They switched out a splitter to get more power to the DVR and nothing really has changed. Still have audio dropouts... Havent noticed the video drop out yet like i use to. So its alittle better i guess.

That is interesting... Every-time that issue comes up Lindend always says it is a TVGOS issue and not a PACE bug. Does that mean all the DVRs (Motorola included) sharing that TVGOS version have the same issue?

You are correct in that TV Guide will report that the disk is full when in fact it really isn't full. This behavior exists on all hardware platforms (Pace and non-Pace) and TVG software versions. That being said, this is where it gets complicated. TVG will get into this state when an unanticipated error happens.

So really, the false disk full is masking an underlying error. The underlying error may or may not be a Pace bug depending on the scenario in question.

We are investigating the error scenario that Toadtaste reported but I can't comment further on that in a public forum.

I'm discovering more and more issues with my new Pace box (787X). I've now had 3 recordings in the past week and a half where out of nowhere the recorded program will suddenly speed up during playback for about 1 second. When the program resumes normal speed, the audio and video are completely out of sync and the video is shaky for the rest of the program (like it's skipping frames). Performing some sort of action (fast forward, rewind, skip, stop and play) seems to fix things, syncing the audio and correcting the fps issues. Unfortunately, it's really screwed things up for me, as I like to dub programs off of the DVR unmonitored when I need to make space for new recordings and have been creating worthless coasters because of this. While this seems to happen to random recordings, once a recording is afflicted, it exhibits the same behavior every single time, at the exact same spot on the program. I've skimmed through the entries in this thread and not seen a reference to such a similar happening.

Lindend? Do you have any suggestions?

This is a 787X operating firmware 13.53 on Insight Cable.

Thanks.

I have been very patient, waiting for oft-promised firmware updates for my Pace Summits. In the meantime I have been put to considerable inconvenience over the continuing firmware problems, which for me started last June with an Aspen and have continued, unabated, on my current Summits with Shaw (WD) Expanders (external HDDS).

I have written to both Shaw and Pace Technical Support telling them that I hope these firmware updates will actually be in place by the end of March or I will have no choice but to move to a competitor, which I am very reluctant to do, but what choice am I being given? Repeated assurances that corrective firmware updates are coming soon have been nothing but empty promises. (I have no illusions that my stated intention to switch to a competitor will have any actual impact. It would just get me out of this ongoing situation.)

After 8 months I think I am entitled to consider the Pace PVRs to be lemons.

Does anyone have any positive light to shed on this situation?LindenD, any insights? We are now being told that mid-April is the best guess for Shaw firmware updates (Summit et al). My most charitable interpretation is that the bugs are so severe that much, if not all, of the underlying code is being rewritten. Regrettably, I don't think Linden will be able to say much. Certainly Pace Technical Support is no longer talking to me. [To Pace's credit, it was Pace Technical Support's willingness to enter into a dialogue about symptoms that prevented me from jumping ship much sooner.] I am in the last stages of talking to Shaw about options, including having Shaw buy back my Summits and Expanders. Wish me luck! I'll need it.

Well Harmony added the CC command to my account - but it doesn't appear to be working completely. It seems to only send an "off" command for CC to my Pace box - if I manually turn CC on on the box - that code will turn it back off - but it will not turn CC on. Any ideas?

Just an update for you Linden.

It does appear that the code for both CC and Resolution change are working.

I think the issue with the CC command in particular - is that after sending it - I have to turn my cable box off - then back on to complete it - after the on/off - CC is indeed back on.

It will turn the CC off at anytime - however - after pressing my assigned CC button to turn CC on - it's almost as if the cable box can't process the command until it's turned off then on again and then after that - CC is on.

I'm not sure why but I don't think it has anything to do with the code Jason at Remote Central came up with - I think it's a shortcoming of the box.

Regardless - even in this state - it's a LOT better than the old way we had to turn CC on and off - which was press power on the box - hit menu - use the arrow pad to scroll to CC - hit enter - scroll to CC on/off menu - hit menu - press power. Obviously at 5am when my wife wants to run on her treadmill and watch tv with the sound off - she doesn't appreciate having to go through all that fuss. This will be a much better solution even with the power cycle needing to be done.

Thank you again and let me know if there's anything you'd like me to test or whatnot.

Let me look into this and I'll update you on what I find.

I've discovered you don't actually *have* to turn the box off to have the captions come on. If you use any of the timeshifting features, when you return to live tv, the captions will be working.

I have a Western Digital DVR Expander, model WD5000F032. I have used it for a couple of years with the TDC778x, but that DVR went bad and my cable company swapped it out with the TDC787X. My external drive won't work with this new DVR.

When I hook it up to the DVR and plug it in, the DVR doesn't work. In diagnostics the DVR is listed as not existing or not enabled, I don't remember and no hard drive, internal or external is found. If I remove the external drive after powering down, everthing works like normal.

I checked to make sure that the SATA port is enabled on the 787x.

It was suggested that I try reformatting it from a computer, but I don't think I have any computer with an external SATA port, unless I'm missing something.

Any ideas?

I have a Western Digital DVR Expander, model WD5000F032. I have used it for a couple of years with the TDC778x, but that DVR went bad and my cable company swapped it out with the TDC787X. My external drive won't work with this new DVR.

When I hook it up to the DVR and plug it in, the DVR doesn't work. In diagnostics the DVR is listed as not existing or not enabled, I don't remember and no hard drive, internal or external is found. If I remove the external drive after powering down, everthing works like normal.

I checked to make sure that the SATA port is enabled on the 787x.

It was suggested that I try reformatting it from a computer, but I don't think I have any computer with an external SATA port, unless I'm missing something.

Any ideas?

You can buy a USB to eSata adapter for your PC for about $8.
http://www.amazon.com/USB-to-eSATA-SATA-Adapter/dp/B002BC32OG/ref=pd_cp_e_1

>>You can buy a USB to eSata adapter for your PC for about $8.

Thanks. I didn't know that. I'll get one and try reformatting it from my computer.

After being forced, by a low-level tech support representative, to jump through a few more hoops (having a senior, thankfully, technician come out to check my levels and set-up), I was able to get loaner Motorola 3416s until the Pace Summit firmware issues are resolved plus I received a modest bill credit, thanks to the senior technician, who understood the problems completely, didn't try to claim that they were somehow my fault & said so, and to a pair of excellent level-2 technical support specialists who tried, within the limits imposed by Shaw, to make things right. Such people do exist at Shaw. One just has to find them, somehow. This solution isn't perfect but it helps make an intolerable situation tolerable.

Now I don't care how long it takes to fix the firmware.

The issue was that it would not go away without a format of the drive if i remember correctly. Suffice to say we are waiting for the next release.

Mediacom updates the FW to 13.36 last night (from 12.61).

I hope this fixes the massive memory leak that has been shutting down my box in 5-15days of usage. I think the memory leak was caused by the defrag task.

PS - Toadtaste, was it the 14.xx versions that had the false full messages you were taking about?

The 787x still has the same bug as the 779x series in that the current HD program you are watching shudders for 20-30 secs when a back ground HD show starts recording.

Anyone else noticed this?

PS - At least it doesn't seem to shudders the current show when a background HD recording ends.

Version 13.36 fixed the "99.99" Firmware version on the TVGUIDE Cablebox setup/Configuration screen, it now shows 13.36.

The HDMI display info is still sent out as "Reference Sw".

Lindend, is the "Reference Sw" HDMI display tag fixed on later FW builds?

The iGuide version is still the old 74.64 -3337 version that 12.61 had.

The 14.xx version was the one experiencing that problem. That also included guide A25, so it will have to wait until a revision is released that addresses the current issues that we can deploy with A25.

A41A code appeared on the 787x display. No power outage or other anomily occurred that I'm aware of (I also have a Motorola box on same TV and that was okay). Power down & up cycle still ends up with the 787x hanging when it gets to the A41A code.

Cable company (Armstrong) said the box was unresponsive and the help desk didn't seem to know what the A41A code indicated. I have a WD Caviar Blue 500GB drive connected via e-sata which has been working well (had it as high as 87% full during the Olympics - it was at approx 25%/26hrs when this happened). After pulling the e-sata and re-powering, the 787x returned to full functionality -- but of course with only a listing of the recordings and no content (at least I know exactly what I may have lost).

The WD drive appears to be healthy/functional. I can view the partitions as well as the hex/ascii content. I imaged the WD drive (using DiskImage from Dubaron) so that I might possibly be able to re-image a replacement drive. Armstong dispatched a tech and offered to replace the 787x box, but I'm seeking other options which may preserve the 26hrs of recently recorded content.

Any insight with regard to the A41A code and a possible resolution will be appreciated.

More regarding the A41A hang up:

I wiped the WD 500GB drive by creating a MSWindows partition on it and then re-attached it to 787x. The 787x then formatted the drive and it shows up as "Good" in the 787x diagnostics. Appears to be funtioning well and I have already recorded 20+hrs of HD programming as well as played back a few hrs. I think that pretty well verifies the problem was not drive related.

btw, the 787x is at rev 15.66.

Looking at the drive hex/ascii dump from when the problem occurred, I see the following:
byte 000h= PACE-2-1
byte 120h= Invalid partition.Error loading operating system.Missing operating system
byte 7E000h offset 8257536= hd extBadDisk
This may be a clue. (I have screen shots of the dump.)

I have been using a SATA to eSATA enclosure to house the WD 500GB drive but I also tried a Thermaltake BlackX SATA to USB/eSATA docking station which appeared to work equally well. The BlackX allows you to drop in either 3-1/2 or 2-1/2 inch drives. I'm thinking of going back to the BlackX and seeing whether it may be possible to periodically swap in multiple small capacity drives in order to circumvent loosing "all" recorded content as happens with a 1 drive scenario.

I can't get the SAP audio stream of CNBC HD to work on a PACE DVR. I had the same issue on the PACE 779x DVR.

CNBC HD broadcasts two English audio streams, a DD 5.1 stream for the main window and a DD 2.0 stream for special programs in a PIP windows.

I have tried to go to Audio setup menu and choosing each language one at a time and nothing brings up the DD2.0 audio stream. I have tried power cycling after each language selection or changing channel after each selection.

Anybody able to get the SAP audio on CNBC HD?

On my SONY Cablecard DVR, I just select the current audio track I want to hear English track 1 or English track2.

Is there any way via the remote control to toggle closed captioning on and off?

Has anyone had any success connecting a Pace box with an external HDD using a 15' eSATA cable? I tried, with two different cables (from the same manufacturer - the only ones I could find) to connect my Summit to an Expander (WD) and neither worked. Both worked just fine with my computer and a different eSATA HDD.

Hmmm, it appears that, despite the availability of longer cables and despite the fact that some equipment works with the longer cables, the eSATA spec allows for a maximum length of 2 metres, with so-called active adapters. With passive adapters the maximum cable length is reduced to 1 metre. I haven't yet tried a 2 metere cable. It isn't long enough to be useful to me. I want to position the Expander in another room (through the intervening wall)

Has anyone had any success connecting a Pace box with an external HDD using a 15' eSATA cable? I tried, with two different cables (from the same manufacturer - the only ones I could find) to connect my Summit to an Expander (WD) and neither worked. Both worked just fine with my computer and a different eSATA HDD.

Hmmm, it appears that, despite the availability of longer cables and despite the fact that some equipment works with the longer cables, the eSATA spec allows for a maximum length of 2 metres, with so-called active adapters. With passive adapters the maximum cable length is reduced to 1 metre. I haven't yet tried a 2 metere cable. It isn't long enough to be useful to me. I want to position the Expander in another room (through the intervening wall)

You are trying to use a cable that is 2x over the eSata spec of 6.6ft. I would never try that on a DVR that can't handle HDD errors.

The PACE 779x DVR used a passive Sata to eSata so that would reduce the max length to 3.3ft (I haven't looked inside a 787X).

Quote from wiki:With passive adapters the maximum cable length is reduced to 1 metre (3.3 ft) due to the absence of compliant eSATA signal-levels.

Thanks, WhatHappend. That also explains why I had so much trouble finding a 15' eSATA cable. I wish I'd thought to check this out before I bought the cable.

Nonetheless, the cable worked with a Vantec enclosed HDD and my desktop computer's (passive- connected directly to an internal SATA port) eSATA adapter (retrofitted). Of course, I only checked that the drive was detected and readable. Who's to say how well or for how long or how reliably it would have functioned with a cable that much longer than the spec permits. At least I can get a store credit when I return the cable.

Got my refund for the cable. I will try to put the Summit & Expander, together, in the other room and use the IR extension receiver to control them from the first room. Wish me better luck than the first time I tried to use the IR extension receiver, when I had the "runaway" menu problem. This time, though, the Summit (with its built-in IR receiver) and the extension IR receiver will be in separate rooms. Maybe that'll eliminate any interference between the two IR receivers????

Addendum: Well it seems that turning off the IR receiver in the Summit user settings only turns off the one integrated into the box and leaves the extension IR receiver fully functional. Very useful.

Cable provider: Buckeye CableSystem.
Remote: Atlas OCAP 5-Device.
Television: Phillips 32" LCD.

Problem: Occasionally, and now happening more often now, the signal from the remote to the box will be lost. Sometimes this happens directly after turning on the box with the remote, and sometimes it can take up to 3 or 4 hours before the signal is lost.
Scenario: After about 2 hours of using the remote for changing channels, all of a sudden the remote will not work for changing the channels. No amount of rebooting the box will fix the issue. Cycling the power doesn't help. Having the remote inches away from the box doesn't work. Swearing at the box doesn't work. Changing the batteries doesn't help.

I chatted with a technician with Buckeye and he suggested that 'something may be intercepting the remote signal.' While this seems like a logical proposition, we never had a problem controlling the cable box before we upgraded to this DVR. We've not added any new devices since the upgrade. Also, if a device is intercepting the signal, would it not continue to intercept the signal? As mentioned, the problem doesn't always happen. We do have two laptops in the room that are wifi enabled. The issue happens weather or not the laptops are turned on.
Of course, Buckeye suggested swapping the DVR box with another one, however I'm really interested in this situation. Does anyone know what could be causing this issue, or have a working solution?

Thanks.

I have given up waiting for a corrective firmware update for the ongoing "blank recording problems".

I have just had my two Summits replaced, in my case by a pair of Motorola DCX3400s.

After over a year of dealing with missed recordings first on my Aspen and then on my Summits it was time.

I will miss the full width guide and especially the hardware zoom of the Pace units but I look forward (hopefully) to reliable recording.

Good luck to those of you who are still hanging in there. I hope a corrective firmware update comes soon.

I have given up waiting for a corrective firmware update for the ongoing "blank recording problems".

I have just had my two Summits replaced, in my case by a pair of Motorola DCX3400s.

After over a year of dealing with missed recordings first on my Aspen and then on my Summits it was time.

I will miss the full width guide and especially the hardware zoom of the Pace units but I look forward (hopefully) to reliable recording.

Good luck to those of you who are still hanging in there. I hope a corrective firmware update comes soon.
Don't know if this would solve your problem, but my 787 was updated to 18.42 firmware a few days ago. I've never had the blank recording issue, but the erroneous DVR full message that happens every once in awhile popped up again a few weeks ago.

I have no way to tell now whether I would have received the update to 18.32 or whether it would have helped. My Summits were (Shaw) DC758Ds. My last firmware revision was 17.88.

The Summits were nice machines in many ways and a fix had to happen at some point but I had been promised imminent fixes since June of 2009 (initially for an Aspen) and just reached the stage where I needed to put those blank recording behind me.

I didn't give up easily, having tried numerous replacement PVRs, numerous firmware updates and having corresponded extensively with Pace Technical Supporet - who were very good but obviously at the mercy of their programmers/engineers.

Thanks also to all the help that I got from the members of this forum and from Linden.

Sorry if this has been answered, but I don't have time to read all of the pages. Can I have hdmi, and component running at the same time?

got got this to replace the old motorola 64XX...why does this thing take forever switching channels....going from a 1080i signal to 480i or 480p. The old box never did this. I switch channels and the screen goes black...a couple greens line will show and then the picture pops up...very annoying!!

I am connected via HDMI

got got this to replace the old motorola 64XX...why does this thing take forever switching channels....going from a 1080i signal to 480i or 480p. The old box never did this. I switch channels and the screen goes black...a couple greens line will show and then the picture pops up...very annoying!!

I am connected via HDMI

It is your TV that takes that long to change resolution. The PACE box supports sending the video through at its native resolution for best image quality. Some TV change much faster than other. The resolution changes causes a HDMI handshake.

The Motorola box converted everything to one resolution. To make the Pace box do that, go to user setup menu (power off then press menu button) and only select one resolution 1080i or 720p then all video will be converted to that selected resolution and the channel changes will be faster.

It is your TV that takes that long to change resolution. The PACE box supports sending the video through at its native resolution for best image quality. Some TV change much faster than other. The resolution changes causes a HDMI handshake.

The Motorola box converted everything to one resolution. To make the Pace box do that, go to user setup menu (power off then press menu button) and only select one resolution 1080i or 720p then all video will be converted to that selected resolution and the channel changes will be faster.

Thanks....I selected 1080i only and it seems to be working great...amazes me how these techs just plug em in and go...

I just recieved this box from Mediacom in Mobile Al. The problem is anytime you fast forward a show on the DVR it overuns when you go back to play, then I am forced to rewind again. My last Pace box would stop right when I hit play, this is very annoying. Has anyone had this problem and is there a fix for this?

If ever I pause the DVR, the gaphical bar showing pause position / time bar is displayed by the DVR. This is quite big and takes up about a quarter of the viewable display. Often this actually blocks out parts of the screen you wish to see paused especially sports.

Could this be made to perhaps time-out to vanish after a few seconds or even a variable added to the CP to set the time it displays for by the user?

Cheers.

Anyone have an answer to this? I find it extremely annoying and would love to disable it. I have a 787x.

Anyone have an answer to this? I find it extremely annoying and would love to disable it. I have a 787x.
This is a function of the guide/DVR software used by your cable provider and not of the DVR firmware. If you have i-Guide, there's unfortunately no way to disable the progress bar.

If ever I pause the DVR, the gaphical bar showing pause position / time bar is displayed by the DVR. This is quite big and takes up about a quarter of the viewable display. Often this actually blocks out parts of the screen you wish to see paused especially sports.

Could this be made to perhaps time-out to vanish after a few seconds or even a variable added to the CP to set the time it displays for by the user?

Cheers.

Press the EXIT button once.

This is a function of the guide/DVR software used by your cable provider and not of the DVR firmware. If you have i-Guide, there's unfortunately no way to disable the progress bar.

Correct. Nice summary.

With the DC700X using an external harddrive, has there been any discussion on transferring recordings to a computer and either saving them on the harddrive for keeping or transferring those recordings to DVD?

I added another DVR to my account with Buckeye Cablesystem in Toledo OH and got the TDC-787X. I have read the first post about the external hard drive capabilities and it makes reference to later firmwares being able to handle 750G plus (of course eSATA only). What firmware should I be looking for, or should I just stick with the 500G My DVR Expander model that I have used with pretty good success with a couple of my other DVRs? I would like to go larger if possible. My wife eats up these external drives with recordings like there's an endless supply of recording space.
I guess the other question, is the limitation of using a drive that is only eSATA versus both eSATA and USB 2.0 capabable still valid? It's tough finding eSATA only drives now. The firmware this model is using by Buckeye Cable in Toledo OH is 11.90. Many updates behind so I imagine it would be stretching it to go 750GB but trying to find any of the three that are listed in the Pace 787X thread, it looks like they are out of production.
Thanks in advance.

The support for 1TB drives was added in the 13.xx builds. You can still use that size drive, you just will only be able to use the first 500GBs of it.

The support for 1TB drives was added in the 13.xx builds. You can still use that size drive, you just will only be able to use the first 500GBs of it.

Thanks for the reply. From the postings I've seen here from Linden, I got the impression that if you have the older firmware it will only, in his words, recognize ~700GB of the drive.
I was contacted by tier 2 support at Buckeye last night and the told me they are working ona new Guide and with that will more than likely be implementing newer firmware but in the meantime he was going to contact the engineers and see if there was something they could do that would allow customers to mount the larger drives. I'm not holding my breathe but in the meantime ordered the 1 terabyte My DVR Expander drive from western digital so we'll find out one way or the other.
Thanks again.
Bob

Has anyone done a successful drive upgrade on a TCD776D or similar? If so, is there anything special involved or is it straightforward?

Hi. I've seen some people have 30 second skip on this DVR, but my remote doesn't have that button. I do have a Harmony 880, but it's not available there. Does this device in fact have a skip feature?

Hi. I've seen some people have 30 second skip on this DVR, but my remote doesn't have that button. I do have a Harmony 880, but it's not available there. Does this device in fact have a skip feature?
Yes the 787 supports 30-second skip, but some cable operators may disable this feature. You might find a direct method of adding 30-second skip to Harmony remotes by searching the Comcast Motorola DVR thread. My method is more convoluted since I had already been using a Comcast DVR remote that I bought on eBay when I got my Harmony remote. The Comcast DVR remote doesn't come programmed with 30-skip, but it's button-by-button programmable, and instructions for adding 30-second skip can be found on the web. After I got the Harmony remote, I simply used its learning function to create a SkipForward command.

Hello,

Recently I bought the Onkyo 9300THX home theater system, hooked it up to the Pace 787 HD DVR box, and have had audio hiccups (or drop outs if you prefer) ever since. :(

What happens is the audio will drop out for 1/2-1 second and will come back right away. Happens sometimes every five minutes, more on some channels than on others, but from what I can deduce, it happens on all of them.

Blu-ray play and Xbox are fine, it's the Pace 787. I've been reading that firmware upgrades can fix this issue for this model HD DVR. Unfortunately, talking to a tech on the phone for about and hour, and a visit from an install guy, and two weeks later I am in the same position I was before. Neither of them new what to do about updating the firmware.

So, please...for the love of Pete, can someone tell me how to get Mediacom LLC cable to update the firmware on their boxes. To what lengths have other people with the same issue gone to get the firmware update successfully accomplished through their cable provider?

Any insight would be GREEEAAATTTLYY appreciated.

By the way, when I called the tech and she pinged my box to do a routine check, I lost about half the free channels I had been getting since I picked up the box 3 months ago. :eek:

Sux to be me.

Tom

I just recieved this box from Mediacom in Mobile Al. The problem is anytime you fast forward a show on the DVR it overuns when you go back to play, then I am forced to rewind again. My last Pace box would stop right when I hit play, this is very annoying. Has anyone had this problem and is there a fix for this?

Same here. On my Pace DC700x, the slowest fast forward (two arrows) is very slow, about 2x or drop every other frame -- 28 seconds to play 60 seconds of material by my extremely inaccurate measurement :) . The next fastest speed, (three arrows) is almost 20x -- 3.5 seconds to play 60 seconds of material -- overruns the progress bar display and my visual cortex.

Surely providing 4x and 8x as middle speeds would be an easy fix to streamline into the next distro -- adding an option to jump forward or backward 15 minutes using the >>| and |<< keys or other keys would be nice as well.

I have a 787x and would like to know if it's possible to change a setting somewhere so the unit will always go to the last channel used on power up?

Thanks for the reply. From the postings I've seen here from Linden, I got the impression that if you have the older firmware it will only, in his words, recognize ~700GB of the drive.
I was contacted by tier 2 support at Buckeye last night and the told me they are working ona new Guide and with that will more than likely be implementing newer firmware but in the meantime he was going to contact the engineers and see if there was something they could do that would allow customers to mount the larger drives. I'm not holding my breathe but in the meantime ordered the 1 terabyte My DVR Expander drive from western digital so we'll find out one way or the other.
Thanks again.
Bob

How did this work out for you Bob? I ordered that same drive. Does the Aspen recognize the entire volume?

Thanks, Dan.

We have a TDC787x
-video quality sometimes changes to cartoon like colors
-seems to solve if turned off for a while and back on

It would be ideal to either know the cause and solution

Or to replace the unit - Is it possible to backup the recorded shows (either to an external hard drive or possibly a linux connection, or perhaps a usb linux boot?)

I understand the files are recorded with encrypted headers which are explicitly associated with the hardware. So I may only be able to view them on a pc if at all.

So it seems ideal to solve the color problem. Or find a way to back up the videos and make usable on an working 787x.
ideas?
Thanks

This is somewhat off-topic but not sure where to ask this. I have retired one of my WD MY DVR Expanders (500 GB) and replaced it with a 1 TB. Is there a way to get my computer running WinXP to be able to reformat the drive? My computer has an external eSATA port and it was recognized as a new hardware device but wasn't given a drive letter. I'd like to reformat it as NTFS so I can use it as an additional external drive. Anyone know how I can do this?

This is somewhat off-topic but not sure where to ask this. I have retired one of my WD MY DVR Expanders (500 GB) and replaced it with a 1 TB. Is there a way to get my computer running WinXP to be able to reformat the drive? My computer has an external eSATA port and it was recognized as a new hardware device but wasn't given a drive letter. I'd like to reformat it as NTFS so I can use it as an additional external drive. Anyone know how I can do this?

Nevermind. I figured it out. :)

Does anyone know how to reset the TDC787X?
To clear the memory might be another way to say it.

Does anyone know how to reset the TDC787X?
To clear the memory might be another way to say it.

You can format the internal or external HDD to reset it.

Directions contained in the first post

Is there a way to enable the sata port without the cable company's help?
If not, are the sata settings linked to the usb or the IR blaster port settings? Thinking of asking the cable company to enable those and hope the sata gets enabled at the same time.

Greetings,

I have a Pace Aspen DVR and am in Toledo OH Buckeye Cablesystem area. I just purchased a WD My Book AV DVR Expander (1 TB). I turned off and then unplugged my DVR, plugged the external drive (USB/eSATA) into the Aspen with the supplied eSATA cable. I then plugged power cable into the external drive, and finally, plugged the DVR back in. After booting up, I tried the LIST button (some remotes call it "my DVR") and received the message of no DVR available and to call my provider. The tech support guy walked me through the Dashboard and Diagnostics where I found under HDD info that neither the external or the internal were being recognized. I unplugged the DVR and unplugged the external from the DVR and then plugged in the DVR. Once rebooted, it once again recognized its own internal drive.

I even tried the whole procedure a second time in case I did something wrong but had the exact same results.

I would sure appreciate any help or suggestions. I have read that sometimes a combo USB/SATA drive can be a problem. It was the only SATA drive I could find in person though. Thanks much in advance.

Steve

Hmm, no help from anyone 'eh.

Well, I returned the external drive.

My guess would be that the included eSata cable was not making good connection on the DVR and causing the issue. I have had to trim the plastic on eSata cables to get them to work properly in some computers. Buying a more expensive cable also helps.

The first post has external drives that have been tested to work with the unit.

That same Western digital worked great for me. Pretty much plug and play. I can't remember if I did anything differently and I'm not home at the moment. I hope it works out for you because the amount of high definition content on mine at 12% capacity is awesome.

Lindend,
Are you going to update the release notes for 21.xx updates?

Version 13.36 fixed the "99.99" Firmware version on the TVGUIDE Cablebox setup/Configuration screen, it now shows 13.36.

The HDMI display info is still sent out as "Reference Sw".

Lindend, is the "Reference Sw" HDMI display tag fixed on later FW builds?

The iGuide version is still the old 74.64 -3337 version that 12.61 had.

With the new version 21.87 loaded by Mediacom tonight.

I see that the HDMI display tag is now fixed as it shows "TDC787x".
The iGuide version is updated to: 75.73 a25p2-3.S2.r-3
That seems like a pretty old iGuide version (wasn't a28 released in 2009?)

A25 is an older version, but A28 isn't going to be rolled out for a while yet.

I can't believe how slow the 30 sec skip fwd and back are in the new 21.xx update. In the 13.xx version the skip speed was good. The whole UI can pause and take 3-7 second pauses before processing actions from the remote. (this is when recording 2 HD channels and watching a HD recording from the HDD.) How could this update cause this slow down???

Also the 21.xx update has lost the option to put the HDD to sleep in the user settings menu.

I am surprised Mediacom would approve this update????

The S/W ver on mine is 75.73-a25p2-3.S2.r-3

This doesn't look like any of the numbers I've seen mentioned here, what am I misunderstanding?

Another question, I just noticed I was watching a movie that should be in Dolby 5.1 but I'm only getting 2 channel PCM using HDMI. I switched HDMI cables and no change, hooked up my old AVR it also says its only getting 2 channel PCM.

I then hooked the DVR to my current pre/pro with toslink and I'm getting Dolby 5.1 now.

I've checked all the audio settings in the set up menu also so I'm not sure if I'm missing something or if something is wrong with my DVR. Any suggestions?

With the new version 21.87 loaded by Mediacom tonight.

I see that the HDMI display tag is now fixed as it shows "TDC787x".
The iGuide version is updated to: 75.73 a25p2-3.S2.r-3
That seems like a pretty old iGuide version (wasn't a28 released in 2009?)

The S/W ver on mine is 75.73-a25p2-3.S2.r-3

This doesn't look like any of the numbers I've seen mentioned here, what am I misunderstanding?

That is the guide version on the box. The box runs PACE FW (like a OS) and the iGuide software run on top of that. That is the same version of IGuide I reported in the quoted post above. You can look in the PACE diag menu to see the PACE version loaded. First post should tell you how to access the menu.

Another question, I just noticed I was watching a movie that should be in Dolby 5.1 but I'm only getting 2 channel PCM using HDMI. I switched HDMI cables and no change, hooked up my old AVR it also says its only getting 2 channel PCM.

I then hooked the DVR to my current pre/pro with toslink and I'm getting Dolby 5.1 now.

I've checked all the audio settings in the set up menu also so I'm not sure if I'm missing something or if something is wrong with my DVR. Any suggestions?

First question is does the HDMI cable go from the PACE to the AVR or TV?

First question is does the HDMI cable go from the PACE to the AVR or TV?

The HDMI cable goes from the Pace to my pre/pro and then HDMI from the pre/pro to TV.

I used my old AVR to make sure the problem isn't with my pre/pro and both of them were only receiving 2 channel PCM. In the past I would get the appropriate Dolby signal displayed on the scree on my pre/pro. I just did a firmware update to the pre/pro last night so I assumed something was wrong with it after the update so I put my old AVR back in the mix and it also wasn't getting Dolby. I've read on here talk of firmware upgrades on the Pace so I thought I'd check to see if anyone else has the problem.

I called my cable provider and that tech must have been new. Had no idea what I was talking about. She sent a signal to reset the box and it didn't' fix the problem.

I've got to go scoop snow after the storm last night and then I'll come back in and play with the Pace a little more checking the menu you mentioned in the post above.

Thanks for both responses!

I've checked all the audio settings in the set up menu also so I'm not sure if I'm missing something or if something is wrong with my DVR. Any suggestions?

The HDMI cable goes from the Pace to my pre/pro and then HDMI from the pre/pro to TV.

I used my old AVR to make sure the problem isn't with my pre/pro and both of them were only receiving 2 channel PCM. In the past I would get the appropriate Dolby signal displayed on the scree on my pre/pro. I just did a firmware update to the pre/pro last night so I assumed something was wrong with it after the update so I put my old AVR back in the mix and it also wasn't getting Dolby. I've read on here talk of firmware upgrades on the Pace so I thought I'd check to see if anyone else has the problem.


When you say "checked all the audio settings in the set up menu", do you mean the (power off - menu key) setup menu or the iGuide menu audio setup menu?

You should set the (power off - menu) option for HDMI audio pass through (HDMI Settings -> Audio Output mode -> "PASS THROUGH"). You can also disable "Auto Detect" so it stays on pass-through no matter what the HDMI handshake with your AVR or TV reports. Also on the Yamaha Rx-V663, you need to make sure Option Menu -> HDMI Set -> S.Audio is set to "RX-V663".

Sounds like you still have your Yamaha Rx663 for a backup (I thought you were selling it when you asked the question about over-riding YPAO EQ settings?) Don't worry the 787x will output DD5.1 to that Rx663 just fine as that is my setup.

When you say "checked all the audio settings in the set up menu", do you mean the (power off - menu key) setup menu or the iGuide menu audio setup menu?

You should set the (power off - menu) option for HDMI audio pass through (I don't remember the exact wording of the menu).

Sounds like you still have your Yamaha Rx663 for a backup (I thought you were selling it when you asked the question about over-riding YPAO EQ settings?) Don't worry the 787x will output DD5.1 to that Rx663 just fine as that is my setup.

I checked out both menus and all is set as it should be. Something must be wrong with it is my only guess.

Yeah I still have my 663. I thought I had it sold. The guy came and I set it back up in my system and he demo'd it. I have the original box, remote, manual, etc... everything. Tape the box back up and it would be like new in the box. After its all said and done he says he only has $100 to spend and since its a few years old... I couldn't get him out of my house fast enough! Got to love Craiglist!!!

So I've tried different HDMI cables, swapped between my pre/pro and AVR so the only thing left is the box. For now I'll just use toslink since I'm considering changing providers so no point in fixing the problem by exchanging the box and change providers in a month.

Lindend,
Are you going to update the release notes for 21.xx updates?

Sorry guys. I'm a little backed up but I'll update the release notes thread as soon as I get a chance.

That seems like a pretty old iGuide version (wasn't a28 released in 2009?)

Not all MSOs have upgraded to A28. Some have, some haven't.

Anyone had any luck adding the 30 second skip to this box?

Anyone had any luck adding the 30 second skip to this box?

Yes, it works fine. Same code as the Motorola boxes...