Reply to thread

Message

<blockquote data-quote="rue" data-source="post: 1071682" data-attributes="member: 86567">Hi I additionally have to come back to this issue.Meanwhile I am using MP 1.7 RC since a while and I have this issue &quot;up and running&quot;.Today I had the chance to collect something - might be it helps to get for an answer or bugfix.As reported I currently use two different kind of adapters: TBS6928 (which is a PCIe one) and Pinnacle 460e (which is an USB one) together on the sam PC. The USB device will be powered off by Win 8.1 (measured it) completely to prevent from stick based side effects.For today I had 2 recording on different programs scheduled - one 1:15 pm (13:15) on &quot;Disney Channel/Pocahontas II&quot;, which is 576i/p@MPEG2|@ASTRA and the second one, which was &quot;Independence Day&quot; on SAT.1 (576i/p@MPEG2@ASTRA).Situation based Disney Channel has a different transponder than SAT.1 .. for this the first recording came up on TBS 6928 and was running fine up to the moment the second recording was started. For the second recording at 2:05pm (14:05) the Pinnacle 460e was used.So far ... everything fine ...&nbsp; just with the beginning of the second recording the continuity check errors on both streams came up. Before at the time only the TBS will be used - there was no problem.As a result the TSWriter is not able to write any significant (and snesefull) data to the disc. The number of discontiunations seems to be so high that now valid stream can be exist jumping over that time frame. In this case you will find on the disc for the first (good starting record) a perfect file up to the point &quot;on damage&quot; and after this only fragments. For &quot;ID4&quot; it results to a file of about 200 MB.I send you the logfiles as an attachment, please be gentle and verify it - just tell me where I am wrong, or give me an idea for a next step. TVService.log and TSWriter.log will have the appropriate informations.best regards and thanks in advanceRUE</blockquote>

[QUOTE="rue, post: 1071682, member: 86567"] Hi I additionally have to come back to this issue. Meanwhile I am using MP 1.7 RC since a while and I have this issue "up and running". Today I had the chance to collect something - might be it helps to get for an answer or bugfix. As reported I currently use two different kind of adapters: TBS6928 (which is a PCIe one) and Pinnacle 460e (which is an USB one) together on the sam PC. The USB device will be powered off by Win 8.1 (measured it) completely to prevent from stick based side effects. For today I had 2 recording on different programs scheduled - one 1:15 pm (13:15) on "Disney Channel/Pocahontas II", which is 576i/p@MPEG2|@ASTRA and the second one, which was "Independence Day" on SAT.1 (576i/p@MPEG2@ASTRA). Situation based Disney Channel has a different transponder than SAT.1 .. for this the first recording came up on TBS 6928 and was running fine up to the moment the second recording was started. For the second recording at 2:05pm (14:05) the Pinnacle 460e was used. So far ... everything fine ... just with the beginning of the second recording the continuity check errors on both streams came up. Before at the time only the TBS will be used - there was no problem. As a result the TSWriter is not able to write any significant (and snesefull) data to the disc. The number of discontiunations seems to be so high that now valid stream can be exist jumping over that time frame. In this case you will find on the disc for the first (good starting record) a perfect file up to the point "on damage" and after this only fragments. For "ID4" it results to a file of about 200 MB. I send you the logfiles as an attachment, please be gentle and verify it - just tell me where I am wrong, or give me an idea for a next step. TVService.log and TSWriter.log will have the appropriate informations. best regards and thanks in advance RUE [/QUOTE]

Verification