Jump to content

TransEdit Discussion


Recommended Posts

There are no service names in the PAT, only Service ID -> PMT PID assignments.

 

Well, I can't test it, so it's hard to make it work. Here in Europe I don't get a single service name on four satellite positions with SDTO activated, so it does something... please test it with some other satellite position, like Bell 91, that provide service names in the usual way - you should get no service names at all after correctly inserting SDTO=1 in the [sATTYPE] section of the according transponder list.

 

I already have the SDT other XML file from karimir, that should be enough. I'll check the code again...

 

 

I tried it again, still does not bring out the names. I am attaching the XML from the PAT PID = 0 which after 10 seconds pickups the names correctly.

Echostar_7_12282_V_08.xml

Link to comment
I am attaching the XML from the PAT PID = 0 which after 10 seconds pickups the names correctly.

From the TransEdit Manual:

The right side of the tree node's captions – after the hyphen – is not part of the original SI Table entries, but added by the Analyzer to make them comprehensible. Partly the descriptions originate from Analyzer tables, that translate values into names, partly from a special name-giver instance, that collects all IDs and names from the SI Tables (e.g. from Service Descriptors) and assigns them to each other.

ATM my family keeps me busy, but I will look after it...

Link to comment

I've just noticed that the EchoStar SDT other contains several subtables, and TransEdit 3.1.2 only examines the first one, which is not the correct one. So the approach must be a bit more sophisticated. Let's have another try - TransEdit 3.1.2.1 EchoStar Test version in the members area, beta section. Maybe not the last one... that's the result of coding blindly :jawdrop:

 

The SDTO=1 entry in the transponder list file is still necessary, of course.

Link to comment
I've just noticed that the EchoStar SDT other contains several subtables, and TransEdit 3.1.2 only examines the first one, which is not the correct one. So the approach must be a bit more sophisticated. Let's have another try - TransEdit 3.1.2.1 EchoStar Test version in the members area, beta section. Maybe not the last one... that's the result of coding blindly :jawdrop:

 

The SDTO=1 entry in the transponder list file is still necessary, of course.

 

Was able to get some names, but not consistant.

Link to comment
Increase Settings -> Scanner 2 -> SDT timeout. It may take longer to read all the subtables.

 

 

I have raised the SDT timeout to 32000, now I get half the channel with name and the other half without. If you can raise the SDT timeout more I think all the names should come through.

Link to comment
I've just noticed that the EchoStar SDT other contains several subtables, and TransEdit 3.1.2 only examines the first one, which is not the correct one. So the approach must be a bit more sophisticated. Let's have another try - TransEdit 3.1.2.1 EchoStar Test version in the members area, beta section. Maybe not the last one... that's the result of coding blindly :)

 

The SDTO=1 entry in the transponder list file is still necessary, of course.

 

 

Great work… :jawdrop: (EchoStar 6,8 110W) it’s now working at 95% with TE3.1.2.1

 

You can see the result in the 2500.ini attached files.

 

Now some explanation:

 

In the TE.ini I have increased the SDT to 32,000 ms

 

In the 2500.ini you can see some empty transponders and after a second or third rescan I have received the info after increased SDT to 45,000 ms.

 

Finally I have just one empty transponder (32=12661,V,20000,56,0,0) and this is due to a poor quality signal on this one.

 

So I can conclude that you have found the solution in the TransEdit 3.1.2.1.

 

 

This afternoon I will conduct the same test on (EchoSar 7 119W) and I come back with the result.

 

 

Observation:

Some time when I modify the SDT in the ini file, TransEdit.exe don’t show the same value in the Settings/ Scanner2.

 

 

Tank you very much for your help and your work. :)

2500.ini

Link to comment
This afternoon I will conduct the same test on (EchoSar 7 119W) and I come back with the result.

 

Test result on (EchoSar 7 119W) with SDT at 32,000 ms in the include 2410.ini.

 

Some observation:

I can populate some empty transponders in increasing the SDT.

On some other empty transponders I have a poor quality signal.

On the 12428,V,20000,56,0,0 I have no lock.

 

Finally I have reconduct all my test with my other software (MT) AND I got the same result.

 

So, my conclusion : TransEdit 3.2.1.1 can now do the job.

 

My next step will be to fine tune my dish and scan again all transponder individually.

 

Hope this help and again Tank You.

2410.ini

Edited by lgRich
Link to comment

Can somebody elaborate on the new transponder list format?

 

74=12692,H,22000,56,129,0,|ORF Digital

Seems to be:

frequency,polarity,symbolrate, fec,?,dvb-s2-flag

 

What's behind the '?'? Is it a bit field as integer representation? If yes which bits indicate what? Must be about additional S2 parameters like pilot-symbols and roll-off...

 

 

What about the common TT format?

 

30=11895,V,27500,34
31=11914,H,27500,910,S2

Guess it is not supported any longer, even for non-Conexant-demodulator cards which do not require the additional S2 parameters?

Link to comment
What's behind the '?'? Is it a bit field as integer representation?

Yes. It combines several properties of DVB-S/S2 transponders:

 

Bit 0-1: Modulation (0 = Auto, 1 = QPSK, 2 = 8PSK, 3 = 16QAM)

Bit 2: Modulation System (0 = DVB-S, 1 = DVB-S2)

Bit 3-4: Roll-Off (0 = 0.35, 1 = 0.25, 2 = 0.20, 3 = reserved)

Bit 5-6: Spectral Inversion (0 = undefined, 1 = auto, 2 = normal, 3 = inverted)

Bit 7: Pilot Symbols (0 = off, 1 = on).

 

Bit 0-4 conform with a series of bits in the satellite delivery system descriptor (part of the NIT), as defined by ETSI. The next value (what you call DVB-S2 flag) is just there for compatibility reasons. Future DVBViewer/TransEdit versions will only use bit 2 of the bit field, as described above.

 

The spectral inversion values conform with the BDA specifications. We don't know exactly what they do and how they are used by different devices/drivers, so they are there for experimental reasons. In TransEdit spectral inversion can be set for a transponder by inserting the two characters %x in the description, where x is one of the spectral inversion values 0...3, e.g. %3 for inverted.

 

Modulation System had to be introduced for DVB-S2 cards in general, and Modulation, Roll-Off and Pilot Symbols particularly for Conexant based DVB-S2 devices (Hauppauge / FireDTV), because tuning S2 transponders doesn't work without specifying them.

Link to comment
What about the common TT format?

30=11895,V,27500,34

31=11914,H,27500,910,S2

TransEdit reads "S2", if present, and converts it to the DVBViewer/TransEdit system of storing DVB-S2 parameters in transponder lists.

Link to comment

First off, thanks a lot for the detailed explanation.

 

So a transponder list is not supposed to be read or updated by human beings? It is just a matter of NIT scan? At least the ETSI thing explains the bit field (resp. the value), however, it is not well readable and editable for human beings.

 

So TT format should still work for non-Conexant cards incl. S2 tuning. That's fine for me. I will go for these files then since there are some well administered sources out there with up-to-date lists.

Link to comment
however, it is not well readable and editable for human beings

Of course it is. That's what TransEdit has been made for - a GUI for reading, editing and updating transponder lists.

Link to comment
  • 4 weeks later...

OK, found the files now. Always waited for some dialog to appear. Did not know that the files are named dynamically and saved to the output directory...

Link to comment
  • 1 month later...
just try SkyStar 2 rev 2.3 and BlindScan and then made something identical...

Do it yourself. :)

 

SkyStar2 rev 2.3 is the only known card that it able to perform automatic symbolrate detection (rev. 2.6 isn't!). Simply set the Symbolrates field in the Blind Scan Window to 0. But please don't try this with other cards (e.g. FireDTV S2. It crashes).

Link to comment
  • 2 weeks later...
Do it yourself. :bye:

 

SkyStar2 rev 2.3 is the only known card that it able to perform automatic symbolrate detection (rev. 2.6 isn't!). Simply set the Symbolrates field in the Blind Scan Window to 0. But please don't try this with other cards (e.g. FireDTV S2. It crashes).

Griga I`m not a programmer :D

AVerTV DVB-S card can also perform automatic symbolrate detection....I try just like you saj but this work very slow....SS 2 rev 2,3 with Blind Scan softver work very fast and for each satellite you can made file with blind scan options just like this

07E_11_5000-7500.bsp

 

[settings]

LOF_Lo=9750

LOF_Sw=11700

LOF_Hi=10600

SrMask=080

Freq_B=10950

Freq_E=11200

PolarV=1

PolarH=1

IncStep=2

IncJump=0,8

Time_C=90

Time_Q=2000

Time_V=2000

PllIndx=0

Link to comment
and for each satellite you can made file with blind scan options

http://www.DVBViewer.com/griga/TransEdit%2....html#BlindScan

Apply stores the parameter ranges in the transponder list, so that you don't have to enter them again next time. Additionally TransEdit recalculates the number of parameter variations, for each parameter separately and the resulting total number (the product of all single variations), which helps to estimate how much time the complete blind scan will take.
Link to comment
  • 8 months later...

Latest TransEdit (3.2.1) crashes when using Analyze on a Transponder. Scan (All) works.

Edited by Klaus_1250
Link to comment
Latest TransEdit (3.2.1) crashes when using Analyze on a Transponder.

Which network? Which transponder? How does it crash? I've tested it with many DVB-S/T-transponders, no crash.

Link to comment

DVB-C, Ziggo (previously @home) in the Netherlands. QAM64/6875. It crashes within 1 second after starting to analyze the given transponder and displaying the results. E.g. I can see what I normally see, but within a second it gives an "instruction at 0x004dcaab referenced memory at 0x00000009 The Memory could not be read." and it stops.

 

Strangely enough, I have some old raw transponder captures lying around and they work fine. Will grab some more tomorrow if I have some time to see if it is something in the stream or it is hardware related (hardware is a Twinhan Cab-CI 2033 with the 1.1.0.200-drivers).

Edited by Klaus_1250
Link to comment

Haven't tested all transponders, but it certainly is not the only one. Other transponders crash Transedit as well, though the error message is a bit different. E.g. instruction at 0x706d6953 referenced memory at 0x706d6953 (kind of peculiar that one). I should point out that the error message always stays the same (e.g. instruction/memory address), but is different for some transponders. I've tested about a dozen transponders, but I only see those two errors ( 0x706d6953/ 0x706d6953 and 0x004dcaab/0x00000009).

Edited by Klaus_1250
Link to comment

TransEdit 3.2.0 (still available in the members area -> old versions) doesn't crash?

 

I've completely reworked the part of the Analyzer that reads the SI tables. So it may be just one particular descriptor that is not handled correctly. Would be good to know which one.

 

Untick Settings -> Analyzer -> Read Event Information Table (EIT). Still crashing? If not, the problem is caused by the EPG data (EIT) evaluation. If yes, by something else.

 

Please use TransEdit 3.2.0 (if possible) to save the transponder with disabled EIT (or the EIT without the other tables, according to the test above) as XML and attach it here (zipped, of course).

Link to comment
TransEdit 3.2.0 (still available in the members area -> old versions) doesn't crash?

Nope. Works fine and dandy.

 

Untick Settings -> Analyzer -> Read Event Information Table (EIT). Still crashing? If not, the problem is caused by the EPG data (EIT) evaluation. If yes, by something else.

Still crashing, but no longer within 1 sec. Sometimes very fast, sometimes it takes a while (up to 10 sec).

 

Please use TransEdit 3.2.0 (if possible) to save the transponder with disabled EIT (or the EIT without the other tables, according to the test above) as XML and attach it here (zipped, of course).

Done. Even managed to do one with 3.2.1. It crashed when I hit save as xml, but it did save the xml.

 

Ziggo Brabant Limburg (1111) 380000_02 is with 3.2.0

Ziggo Brabant Limburg (1111) 380000_03 is with 3.2.1

 

[edit]Did a 1GB raw transponder capture and fed it to 3.2.1. It does not crash Transedit like a live analysis, but the analysis of the file is not completed. At some point (not the same point every time) the analysis just stops. Fed the same capture in 3.2.0 and it completes the analysis.[/edit]

Ziggo_Brabant_Limburg__1111__380000.zip

Edited by Klaus_1250
Link to comment

this does sound more like are access (threading) problem than like a problem with the incoming data...

referenced memory at 0x00000009

This is an access to non initialized (or already freed) instances...

Link to comment

Interesting. Started up 3.2.1, Task Manager, Set CPU affinity to CPU 0, ... no crash. CPU is a P4 3.2 HT. Can't run without HT I'm afraid, locked by HP :-(

Link to comment

I hate these threading issues :biggrin:

 

@Klaus_1250: Please try TransEdit 3.2.1.2 (members area, beta section).

 

@Lars: IsMultiThread := true was missing. However, it was also missing in 3.2.0... and I've changed nothing concerning thread interaction.

Link to comment

It doesn't crash the app, but it does not complete the analysis either (same as 3.2.1). It just stops at some point. Hitting restart doesn't work either. It works in the sense that it cleans the previous results, but it doesn't start scanning the file again. Only way to make everything work is to make sure Transedit only runs on one Hyperthreading "CPU".

 

Not sure if it will help, but this rolls out of Dr. Watson:

 

*----> State Dump for Thread Id 0xe98 <----*

eax=0237a8e8 ebx=00bdafe8 ecx=02a44060 edx=004d36ec esi=00bdafe8 edi=00abac94
eip=706d6953 esp=020dfdd0 ebp=020dfe18 iopl=0		 nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000			 efl=00000246

function: <nosymbols>
No prior disassembly possible
	706d6953 ??			   ???
	706d6955 ??			   ???
	706d6957 ??			   ???
	706d6959 ??			   ???
	706d695b ??			   ???
	706d695d ??			   ???
	706d695f ??			   ???
	706d6961 ??			   ???
	706d6963 ??			   ???
FAULT ->706d6953 ??			   ???
Error 0x00000001
	706d6955 ??			   ???
	706d6957 ??			   ???
	706d6959 ??			   ???
	706d695b ??			   ???
	706d695d ??			   ???
	706d695f ??			   ???
	706d6961 ??			   ???
	706d6963 ??			   ???
	706d6965 ??			   ???
	706d6967 ??			   ???

*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
ChildEBP RetAddr  Args to Child			  
020dfdcc 004dce8a 00bdaf00 0041c7c2 00bdafe8 0x706d6953
020dfe18 004e4eea 020dfe44 00ab7794 00000000 TransEdit+0xdce8a
020dfe44 004e69f0 00009ea0 00000000 00000001 TransEdit+0xe4eea
020dfe60 004996d1 00ab7794 000000bc 020dfea8 TransEdit+0xe69f0
020dfe8c 0048ecc4 020dfec8 00000000 00ec4288 TransEdit+0x996d1
01f66a68 9ba78ed7 2b173e5c 75d215c1 a27c168f TransEdit+0x8ecc4
95840047 00000000 00000000 00000000 00000000 0x9ba78ed7

*----> Raw Stack Dump <----*
00000000020dfdd0  8a ce 4d 00 00 af bd 00 - c2 c7 41 00 e8 af bd 00  ..M.......A.....
00000000020dfde0  01 af bd 00 67 ce 4d 00 - 68 28 bc 00 a0 02 bd 00  ....g.M.h(......
00000000020dfdf0  8b 41 40 00 f1 09 41 00 - 8f 52 4e 00 03 00 00 00  .A@...A..RN.....
00000000020dfe00  00 55 b7 00 cf 03 00 00 - 40 fe 0d 02 4b 4b 4e 00  .U......@...KKN.
00000000020dfe10  98 7f 21 02 00 00 00 00 - 44 fe 0d 02 ea 4e 4e 00  ..!.....D....NN.
00000000020dfe20  44 fe 0d 02 94 77 ab 00 - 00 00 00 00 02 00 00 00  D....w..........
00000000020dfe30  00 61 10 00 c0 7e 21 02 - 04 00 00 00 94 77 ab 00  .a...~!......w..
00000000020dfe40  90 ac ab 00 60 fe 0d 02 - f0 69 4e 00 a0 9e 00 00  ....`....iN.....
00000000020dfe50  00 00 00 00 01 00 00 00 - f0 61 4e 00 01 00 00 00  .........aN.....
00000000020dfe60  8c fe 0d 02 d1 96 49 00 - 94 77 ab 00 bc 00 00 00  ......I..w......
00000000020dfe70  a8 fe 0d 02 ef 96 49 00 - 8c fe 0d 02 00 5a ab 00  ......I......Z..
00000000020dfe80  a4 1c 00 00 60 ea b2 00 - 94 77 ab 00 68 6a f6 01  ....`....w..hj..
00000000020dfe90  c4 ec 48 00 c8 fe 0d 02 - 00 00 00 00 88 42 ec 00  ..H..........B..
00000000020dfea0  40 ba eb 00 81 ed 48 00 - b4 fe 0d 02 9d ed 48 00  @.....H.......H.
00000000020dfeb0  c8 fe 0d 02 dc ff 0d 02 - ba ed 48 00 c8 fe 0d 02  ..........H.....
00000000020dfec0  68 a4 f1 01 00 00 00 00 - e4 fe 0d 02 3d bc 03 5e  h...........=..^
00000000020dfed0  00 5a ab 00 40 ba eb 00 - 88 42 ec 00 98 43 ec 00  .Z..@....B...C..
00000000020dfee0  40 ba eb 00 fc fe 0d 02 - ba bb 03 5e 40 ba eb 00  @..........^@...
00000000020dfef0  a0 ae 34 00 18 36 ec 00 - 90 ae 34 00 78 ff 0d 02  ..4..6....4.x...
00000000020dff00  da ba 04 5e 98 43 ec 00 - 40 ba eb 00 00 00 00 00  ...^.C..@.......

 

On other thing I noticed. Sometimes, TransEdit is able to analyze a transponder for quite a while (30s), but as soon as I would hit "Save as xml", it will crash.

Edited by Klaus_1250
Link to comment

Thanks for your efforts. ATM it's still a mystery to me, and it will take a bit of time to check the code. So please stay tuned - as soon as I have a clue what's going I'll upload another test version.

Link to comment

A couple of transedit questions I hope you can help with

 

1) How can I find the correct roll-off values for a DVB-S2 transponder using Blind Scan? I can succesfully find the transponders using 0-2 in the roll-off blind scan window but I can't find a way to see which roll-off value is optimum. Roll-off is not listed in the scanner window.

 

2) When I close a preview window I get "Ungultige Gleitkommaoperation." message. When I try to do another preview afterwards I get "Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000" or "Zugriffsverletzung bei Adresse 0047BA4D in Modul "Transedit.exe". Lesen von Adresse 00000004"

 

The transponders I am scanning are 30000 SR 8PSK DVB-S2 transponders.

 

I am using transedit 3.2.1.2 on Vista 32.

 

Thanks.

Link to comment

1. just don't care if reception is quasi error free. If you want, you can read the value from the NIT (sat delivery system) if provided (Astra 0.35).

 

2. dunno. External cards with usb2 can't handle the high rate dvbs2 transponders.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...