Channel 5 HD

Last night I wanted to record "Hercules" on Channel 5 HD, when I set it to record it also started to record on Channel 5 SD at the same time ( a channel which I had hidden) when I tried to delete the Channel 5 SD recording it also deleted the Channel 5 HD recording.
0
Comments
I have learned to my cost, albeit in different circumstances, to watch anything I want to watch before deleting anything else, related or not :-(
As johnnyshank suggests the issue (that I noticed on a different non Youview box) is that the (single) program request appears to occupy both the tuners and thereby limiting what else can be viewed or recorded.
Further speculation - one possible scenario
As the program Crid is probably the same identity for both the C5 and C5HD program the viewer selects a channel from the EPG say C5HD to record thye film. The program CRID identifies that the film comprises more than one segment so looks on ther EPG for a match but finds 2 matches (on C5 and C5HD). Both matches are stored for subsequent recording.
The UK DTT SI rules of operation specifically state that under these circumstances a different IMI should be used for the different channels. Channel5 don't do this.
The programme CRID should be the same (and correctly is) but unfortunately the IMI suffix to the CRID is also being set as the same for both channels i.e. #1.
The UK DTT SI rules of operation (part of the d-book) state that if part of a programme with an IMI is being recorded then any programme that starts within 3 hours of the end of the part being recorded should also be recorded. Thus both broadcasts of the second part are recorded.
For series CRIDs across the channels channel5 insert a '5' for channel 105 (at the second character shuffling the position of the remaining channels along by 1 character). Split single programmes don't have a series CRID but do have a spit suffix (IMI) and the channal5 CRID/IMI allocation strategy so far hasn't covered this. To correct this Channel5 would need to update their CRID/IMI allocation process.
Thanks for highlighting this to us. We've had a look into it and this is (as Zulu suggested) a problem with the split instance identifier not being set correctly. We'll feed this back to Channel 5.