522 Comprehensive Bug List and Feature Wish List

[Pepper]

OK, updated the lists once again, is that better?

I need some feedback: are any of the following fixed yet?

Audio dropouts
Occasionally incorrectly named recordings
Unsubscribed channels in search results

 

[Witschey]

You know, Witschey, you can make your own list. Wouldn't that be easier than crying that you can't give orders to other people? .

I think the answer to this is redundant. It makes no sense to have everybody have a separe bug list. This is SO OBVIOUS that I am starting to think that you have a mental problem of so sort which is preventing you from following the most basic logical principles. I am so sorry for you!

I haven't read past the first paragrap[h of your posts in a long time.

So don't read them! And do us all a favour, if the only thing you have to contribute is complaining about what other people post (without giving ANY arguments at to why the bugs I have reported are not being included into a Comprehensive list), then just don't post anything. The only thing you do is deviate the conversations of threads such as this one into a personal fight.

My post wasn't only a critique on the fact that the 'comprehensive list' is NOT comprehensive (even after Pepper said he has just updated it), but it highlighted some of the things that were previously documented and which were not included in the list. A logical person (from your behaviour it doesn't include you) would see the value of somebody bringing to the attention of readers that the list is NOT comprehensive and that issues are being ignored. Otherwise people like myself would go on reading this thread thinking that it is in fact a comprehensive list.

To the contrary of that, your posts are only personal critiques without giving ANY arguments AT ALL as to why you are in dissagreement with my issue. Yes I will continue raising the issues that I know are bugs over and over and over again until they are taken into account or solved and NOTHING you say will deter me from that. So either live with it, or close your eyes when you come accross one of my posts.

the whining never stops, and the same thing gets said over and over again. .

Again, it is obvious that you have a problem following basic logical principles. I am so sorry for you......
Since you don't seem to understand let me explain you (maybe this will help your brain get blood circulation again). I continue to mention the same things over and over again, because some people in this bulletin board seem to want to ignore them. Sometimes I think that some of you provably work with Dish Network....which would explain why you want to put the issue underground and not let them be out in the open! The 44 hour issue was discussed EXTENSIVELY in satelliteguys.us..but despite of that Pepper did not include it in what he calls a comprehensive bug list. How can you call a list comprehensive when a thread that discusses a particular bug on the 522 and which gets more than 1000 views gets completely ignored? The issue is so 'hot' that the Dish Network e-mail server crashed due to the amount of emails that they received asking them to solve the 44 hour issue. To prevent further crashing of the Dish Network e-mail server the names of the Dish Network personnel mentioned in my message were removed, so that they would stop receiving as many complaints on the 44 hour issue. So since you are provably unaffected by the 44 hour you want to simply put it aside, but the proof that it is an important issue is the amount of e-mails Dish Network received and the amount of views that the 44 hour issue thread received. So YOU can ignore it, but try to get the rest of the audience to ignore it and don't you dare try to get me to stop mentioning the issue to others.

Pepper is making the list publicly available and claiming that it is comphrehensive. It is not comphrehensive and that is the point I am trying to make. Now if you can't follow this logic, please do us a favour and go see a doctor; because your lack of ability to follow and your immediate critiques (in an agressive way) towards everything that I say are starting to get me very very upset.

Keeping your posts to your own comprehensive bug list thread would be nice from my perspective.

Look up the word "comphrehensive"...read the objective that Pepper had when creating this tread.....If you can't follow than, then maybe its time you go see a head specialist.

If you want to avoid a reaction like this one, the next time you critique something that I say, you should backup your statements with logical arguments. I don't mind critique, but I will NOT tolerate critiques without any logical arguments, which only aim to create personal one to one fights on public bulletin boards like this one and that only help to deviate the subject being dealt in the board.

You either contribute to my statements or stay away from me.

 

[Witschey]

OK, updated the lists once again, is that better?

Thank you for updating the list once again. It is certainly nice to see that the two most serious issues I am facing with the 522 (which were not there before) are now part of the list. However just from reading the thread last week I know that quite a few bugs and wish list items that were contributed to your thread during the past two weeks are NOT included in the list yet. I can image that those people who took the time to read all your tread and later took the time to contribute reports on bugs not found on your list or wish list items would like to know why their items didn't make it to the 'comprehensive bug list'.

To avoid people feeling that their issues are being left out or ignored, I would like to recommend that you revisit the posts people have made during the past week or two and that you either mention why you are ignoring an item (you could do that on the tread itself), or that you include it in the list.

You mentioned previously that you updated the list. That gives readers like myself the idea that you have read all new posts and either included them in the bug list or decided not to include them for a reason. Later you said that you had only included some things due to time.

I understand that you may not have time to update the list at all times whenever we post something; but I think that the next time you say you have updated the list, that should mean that you have read all posts, and either included them in the list or posted a reply to the tread saying why you are not including them. That is the only way to make this a 'fair' bug list that takes everybody's feedback into account; as opposed to making it your own personal bug list.

 

[maximum]

Witschey
Dude, take a chill pill. Your posts make it sound like you have some kind of anger management problem. Rather than rant and rave about Pepper's list not including your (or other people's) suggestions just write a simple and polite post asking him to add your issues when he gets a chance.

Example:
"Pepper, I noticed that my issue with the receiver not working with the 44 hour program guide is not on the list. Could you please add it."
"Thanks"

Short, simple, polite and to the point. Give it a try.

 

[maximum]

Here is another one for the bug list that's new with the 2.36 update.
If you press the up arrow on the remote when the power is off, the system info. screen comes up. If viewing the RF output this screen does not display and it appears that the receiver is not responding.

Thanks for voluntarily maintaining the list. Hope Dish technicians are reading it.

 

[Witschey]

Witschey
Dude, take a chill pill.

Every action brings a reaction. If I am personally attacked I will defend myself. Don't attack me and I wont attack you. If Pepper has anything to complaint about my posts let HIM tell me about it, but having the rest of the people act as his 'bodyguard' will bring with it some reaction from my part. That is to be expected.

Talking about Pepper's list, perhaps this would be a good time to acknowledge the good idea and initiative of Pepper to start a comphrehensive bug list that would serve as 1 repository for all the open issues out there. I think that the principle is great, and that is why I am investing some of my time contributing to it. Perhaps I was a bit too direct (for the taste of most people) when expressing my dissapointment at the fact that the issues posted on the bulletin board where not being included in the list. So if I hurt Pepper's feelings I would like to appologize for that. It was not my intention. However my basic arguments still holds. If this is to be called a 'comprehensive bug list' for SatelliteGuys.us bugs on the 522 I think that every effort should be made to make sure that bugs reported on the tread are included in the list (or an explanation posted on the tread as to why they are not beign taken into consideration).

The idea and initiative of Pepper is FANTASTIC, but some effort needs to be put into updating the list to make sure that contributions to the tread are not lost, forgotten or discarted without a reason.

Thanks Pepper for your initiative and for making sure that the list continues to include all the issues reported on the thread.

 

[Pepper]

Well the items are definitely in the thread, if not yet in either the bug list or wish list at the very top. If something's not there that means that any of the following is true:

- I'm stupid, I could not understand what was being said. Example: you asked for the ability to set the default start and end pad times, then went on to say where it's already there. Are you asking for something different?
- I'm busy, I haven't had time to try to duplicate or do further research. This includes testing things that were reported before, to see if they are still there, after getting a new software release.
- It's unrelated or out of the scope of the list. Example: Assigning functions to unused buttons on the remote would require redesigning the ROM in the remote, not the receiver.

If I add something to the bug list that means either I personally have experienced it more than once (duplicatable) or there are more than one person out there stating it to be so (verifiable).

I'm not taking anything personally. This is MY list as somebody said, I humbly thank all who have contributed to it but since it has my name on it I'm not going to just throw everything and anything on there without serious thought.

 

[Sapient]

Witschey,

I see you wrote yet another mile long post, no doubt lettig your rage force you to use twenty paragraphs were a couple sentences would do. Sorry to say I didn't read it.

 

[Sapient]

I am sorry to report that I had two audio drops while watching a one hour recording today. I can't say if the program was recorded before or after the update, however.

 

[Witschey]

- I'm stupid, I could not understand what was being said. Example: you asked for the ability to set the default start and end pad times, then went on to say where it's already there. Are you asking for something different?.

Not understanding something is DEFINATELY not stupid. It may in fact be the fault of the person stating the issue...(not being clear enough).

Regarding the start end pad times, what I meant to say it that there should be the option for the owner of a 522 receiver to setup default start and end pad times, as opposed to having to live with the Dish Network selected defaults of 1 and 3 minutes. In another words, let the USER choose what he wants the default pad times to be.

Currently, it is NOT possible to setup a user default for the pad times on the 522 receiver. Every single time that a 522 user sets up a new recording event one needs to edit the default pad times if one doesn't agree with them. I am requesting to have as a wish list item to be able to setup a user default start and end pad times.

I'm not going to just throw everything and anything on there without serious thought.

I definately agree. Throwing all types of issues (without checking first whether they are in fact a bug) would cause the list to contain a lot of items which may not be bugs, but rather problems that a particular user is having due to not knowing how to operate the receiver or a unique problem particular to that receiver and not to all receivers. So please DO verify that they are trully bugs. That is part of the value of the list; and Dish Network will take the list more seriously if it has been validated.

 

[Witschey]

Witschey,

I see you wrote yet another mile long post, no doubt lettig your rage force you to use twenty paragraphs were a couple sentences would do. Sorry to say I didn't read it.

Am I supposed to feel sorry that you didn't read my post? Man! You give to much credit to yourself. Your contribution to my posts is negative (iow you not only not contribute anything positive, but your contributions are of such nature that they are negative), so I don't give a damn if you read my posts or not. In fact I think everybody would be better off if you didn't read them and therefore didn't reply to them either.

 

[Pepper]

Currently, it is NOT possible to setup a user default for the pad times on the 522 receiver. Every single time that a 522 user sets up a new recording event one needs to edit the default pad times if one doesn't agree with them.

Ah, now that makes sense. I coulda' sworn that I had seen in there that it could be modified but I did not notice it was an "every time" thing. I agree, either there should be somewhere to change the default, or have it remember what you changed it to till you change it to something else.

I think what I was seeing is that I changed the settings for a recurring timer, then every time it recorded it followed that behavior BUT sure enough the next timer I setup was default 1 and 3 again.

 

[mrschwarz]

Ah, now that makes sense. I coulda' sworn that I had seen in there that it could be modified but I did not notice it was an "every time" thing. I agree, either there should be somewhere to change the default, or have it remember what you changed it to till you change it to something else.

I think what I was seeing is that I changed the settings for a recurring timer, then every time it recorded it followed that behavior BUT sure enough the next timer I setup was default 1 and 3 again.

Are you sure that's a bug or is it a programmed behavior that most of us don't like?

 

[Witschey]

Are you sure that's a bug or is it a programmed behavior that most of us don't like?

I think this would have to be consdiered a "Wish List" type of item because it is not like something is malfunctioning. Changing the pad times works just fine....but I (and I think other people too) would like to ability to decide what we want as default pad times so that we don't have to edit the pad times manually every time we want to record an event. For example in my case I am perfectly happy with NO pad times at all. IOW 0 minutes before and 0 minutes after; but since Dish is putting 1 and 3 minutes pad time I have to edit that EVERY single time I setup a recording event. I understand that some poeple are provably happy with 1 and 3 minutes and others may want something else; so why not allow everybody to choose their defaults and make every user happy.

I used to have a 508 receiver before I bought the 522, and I think remembering that on the 508 software it WAS possible to change the default pad times. However I am not 100% sure of it. Anyway with a 508 receiver who can check that?

 

[BobaBird]

The only pad on the 50x line is a check box (default=off) to start 1 minute early. Any other variation has to be done by editing the start and/or end times.

 

[CygnusTM]

Another bug I've noticed: The Schedule page doesn't show all skipped events. It shows some, but not all. I especially notice this on Wednesday nights. I had both West Wing and Alias recording from 9-10 and Good Eats from 10-10:30. The problem is that Alias usually runs past its scheduled time. If that is the tuner used for Good Eats, Alias gets cut off. My solution is to skip GE at 10 and record it when it re-runs at 2AM. However, the 2AM showing doesn't show up in the list so I have to hunt it down in the guide and restore it from there.

This appears to be fixed in L2.36.

Edit: Nevermind. I just noticed you never added this to the page. [insert whiny temper-tantrum here]

 

[cellness]

Bug: Edit Time doesn't stick

Let's say a certain program has several episodes being run back-to-back (I'll call it a marathon). I would like to record the marathon as one recording, not several individual recordings. So I create the timer for the first episode, then go back and edit the time to cover the whole marathon. For example the original time was 4:00 PM to 5:00 PM and I change it to 4:00 PM to 8:00 PM. All seems well, as the info about the event shows 4:00 PM to 8:00 PM and the guide shows the record icon on all the episodes.

However, when looking at the event info at a later time , the event has reverted back to the original time (i.e. 4:00 PM to 5:00 PM). The record icon is also only showing on the first episode. I've reproduced this problem several times, after first being "bit" by this bug and only getting the first episode of a marathon

I've noticed that this problem will show itself when checking the event info first thing in the morning, so it appears to happen when the program guide is updated overnight. It *may* occur at other times as well, I've not yet determined this, but I suspect it has something to do with the program guide update, especially after noting a few similar bugs while reading this thread.

Also, the problem does NOT occur if I create a manual timer that covers the course of a marathon. All episodes do get recorded properly under one recording. So it's almost as if an edit to a timer simply does not "stick".

Note that this problem never exhibited itself with my older 510 DVR.

Has anyone else noticed this problem?