07-09-2021 12:28 PM
05-01-2025 08:35 PM
Back to the drawing board. Having worked perfectly from Sep-Dec, all recodings have failed since 29 Dec. Seems worse than the original problem. Shame on Samsung - not buying one from them anymore
06-01-2025 08:16 AM - last edited 06-01-2025 10:51 AM
Hey you guys! I had this problem too, as you see from my former posts. But finally I worked out the solution to fix it. Here is the way to fix it.
1. Go to Recordings, Recordings and Schedule Manager, Change tab from 'Recorded' to 'Scheduled'
2. Then click 'Scheduled Recordings' and if any source dialoges are listed hit 'X-Cancel' for each and every one.
3. Then click 'Scheduled Viewing' and if any are listed hit 'X-Cancel' as before.
4 Now go back to 'Recordings & Schedule Manager, and slowly scroll down all of your retained recordings one by one (that you may have scheduled in the past) . You will note as you scroll down each recoding changes to grey. This is normal. But you need to look at the recordings one by one looking for any that are grey before the become selected. Especially when you scroll off the top and bottom recording to see if they were grey, and likewise for all of the others.
5. If you see any recodings greyed before landing curson on them be sure to delete them. These are the "failed recordings" that have failed in the past for a variety of readings. Such as someone changed the channel whilst the recording was being made, or someone cancelled the 5 minute advance warning that a recording will be made. Easily done, but it clogs up the system with failed entries.
6 For all the recordings that were greyed out, hit the REMOVE button. JOB DONE !
It seems things like, kids, power cuts, switching between channels during recrdings or during notifications will cause failures and rogue entries in the Recorded, and Scheduled tabs.
If this works for you, be sure to like it so as others can find it easily.
07-01-2025 10:25 AM
Further to my last, I'd like to say, and apologise, that my latest failure (which dated precisely from 29 Dec) is NOT related to this thread. It is a different issue and I'm investigating whether it is the TV or the HDD.
For Midori47 - it looks to me like your problem and solution is also different to the subject of the thread, as detailed originally by Helen22. Not sure whether my new problem is the same as yours was, but I shall keep your solution to hand just in case! Thanks