home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
No connection could be made because the target machine actively refused it
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1130871" data-attributes="member: 82144"><p>Please be reasonable. You know this generalisation is patently not true.</p><p></p><p>TV Server is not "my application" and therefore I do not take responsibility for it. I am only one person that works on it as a hobby. Like you, I have a real life. I don't have infinite time to fix all the bugs that are reported in such a huge code base (not even considering development of new features). Therefore, I have to choose what I will work on and what I won't.</p><p></p><p>You know that I've chosen to work on TVE 3.5. Attempting to fix this problem will block me from that work because debugging TVE 3 requires configuration that is incompatible with TVE 3.5 development. Further, I suspect the investigation could take most (if not all) of my available MP development time... and then at the end of the process I still doubt a problem will be found in TV Server... or if it is, it could easily be in a part that is irrelevant in TVE 3.5. Therefore I've decided I'm not willing to commit more time.</p><p></p><p></p><p>It is true that we don't want the TV service to crash. However not all TV Server crashes can be blamed on TV Server. Tuner drivers, M***I, DirectShow, BDA, 3rd party plugins... all can cause a crash in TV service, and yet they are not part of TV Server. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>So go ahead and fix it! I'm not stopping you. I'm simply saying I don't have time and inclination to fix it for you. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>That was just an example. Other possible causes are listed above (DirectShow etc.). That list is not an exhaustive list either.</p><p>To be very clear, my point is that I currently don't see definitive proof that this crash is caused by a bug in TV Server. There are alternative causes which you appear not to have considered.</p><p></p><p></p><p>Sure, and I appreciate this. I've also tried my best to help you by answering your questions, suggesting next steps etc.</p><p></p><p></p><p>Maybe... but then why haven't I seen such a problem before? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p></p><p>"No one" is a huuuuuge exaggeration. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p>Like I just said, I haven't seen such a report or problem before in any scenario, including with other 3rd party plugins.</p><p></p><p></p><p>Simple: because you want a solution. This is how open source works.</p><p></p><p></p><p>That's exactly my point: <strong>I do not have a running build environment</strong>, so it is not 1000 times easier. In fact it is quite an inconvenience for me.</p><p></p><p>Regards,</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1130871, member: 82144"] Please be reasonable. You know this generalisation is patently not true. TV Server is not "my application" and therefore I do not take responsibility for it. I am only one person that works on it as a hobby. Like you, I have a real life. I don't have infinite time to fix all the bugs that are reported in such a huge code base (not even considering development of new features). Therefore, I have to choose what I will work on and what I won't. You know that I've chosen to work on TVE 3.5. Attempting to fix this problem will block me from that work because debugging TVE 3 requires configuration that is incompatible with TVE 3.5 development. Further, I suspect the investigation could take most (if not all) of my available MP development time... and then at the end of the process I still doubt a problem will be found in TV Server... or if it is, it could easily be in a part that is irrelevant in TVE 3.5. Therefore I've decided I'm not willing to commit more time. It is true that we don't want the TV service to crash. However not all TV Server crashes can be blamed on TV Server. Tuner drivers, M***I, DirectShow, BDA, 3rd party plugins... all can cause a crash in TV service, and yet they are not part of TV Server. :) So go ahead and fix it! I'm not stopping you. I'm simply saying I don't have time and inclination to fix it for you. :) That was just an example. Other possible causes are listed above (DirectShow etc.). That list is not an exhaustive list either. To be very clear, my point is that I currently don't see definitive proof that this crash is caused by a bug in TV Server. There are alternative causes which you appear not to have considered. Sure, and I appreciate this. I've also tried my best to help you by answering your questions, suggesting next steps etc. Maybe... but then why haven't I seen such a problem before? ;) "No one" is a huuuuuge exaggeration. ;) Like I just said, I haven't seen such a report or problem before in any scenario, including with other 3rd party plugins. Simple: because you want a solution. This is how open source works. That's exactly my point: [B]I do not have a running build environment[/B], so it is not 1000 times easier. In fact it is quite an inconvenience for me. Regards, mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
No connection could be made because the target machine actively refused it
Contact us
RSS
Top
Bottom