eulores Posted February 9, 2010 Share Posted February 9, 2010 Hallo liebe Leute, ich habe ein Konvertierungstool in Python geschrieben, welches Kanäle einfach umsortieren kann. Das Tool wird veröffentlicht, sobald die letzten "gröberen" Fehler ausgemerzt sind ;-) Auch das einlesen und exportieren in Formate .INI, .CSV und .DAT klappt beinahe perfekt! Leider merke ich, dass DVBViewer manche "Reserved" Felder benutzt und auswertet, diese aber nicht dokumentiert sind! (Habe aich in der Wiki danach gesucht!) Kann mir bitte ein Entwickler sagen, was in den Feldern Reserved5, Reserved7 und Reserved8 abgespeichert wird? Wenn diese Felder auf Null gesetzt werden, dann funktionieren bei mir alle DVB-S Kanäle, nicht aber die DVB-S2. Wenn die Felder via Transedit (scan selected...) bestimmte Werte aufweisen, klappt der Empfang. Kann ich den Inhalt dieser Reserved Felder von denen in entsprechenden .INI oder .CSV Dateien ableiten? z.B. bei ARTE HD scheint Reserved5 der Satelliet-Orbiter Wert zu sein (192 in meinem Fall); Reserved7 ist 67h (103 dez.); Reserved8 ist 7265h (29285 dez.). Sind diese Werte gleich Null, klappt der Empfang von ARTE HD nicht mehr :-( Viele Gruesse, eulores ps. die Support.zip habe ich absichtlich nicht beigefügt, da mein Problem Hardware- / Konfigurations-unabhängig ist. Bitte keine Hate-Mails falls ich mich geirrt haben sollte, und support.zip trotzdem mit dabei sein sollte :-) Quote Link to comment
Lars_MQ Posted February 9, 2010 Share Posted February 9, 2010 TTuner = record TunerType: TTunerType; //byte Group: TChannelGroup; //byte Unused1: Byte; Flags: Byte; Frequency: DWord; SymbolRate: DWord; LOF: Word; //LNB LOF PMT: Word; Volume: Byte; Unused: Byte; SatModulation: Byte; AVFormat: Byte; FEC: Byte; Audiochannel: Byte; Unused3: Word; //CAID_0 Polarity: Byte; //or Modulation or BandWidth Unused4: Byte; OrbitalPos: Word; Tone: Byte; //22 khz off/on EPGFlag: Byte; DiSEqCValue: Word; // OrbitPos, or other value: Positoner, GotoAngular, Command String DiSEqC: Byte; //None,SimpleA, SimpleB, PosA/OptA, PosB/OptA, PosA/OptB, PosB/OptB Language: TTunerLanguage; //array [0..2] of char (byte) AudioPID: Word; Unused5: Byte; unused6: Byte; VideoPID: Word; TransportStreamID: Word; TelePID: Word; NetworkID: Word; SID: Word; PCRPID: Word; end; Quote Link to comment
eulores Posted February 11, 2010 Author Share Posted February 11, 2010 (edited) Thanks a lot for your previous fast answer. It already helped me a lot When channel data is exported in .INI format, the following fields are defined. I tried to correlate them with the fields documented in ChannelFormat.txt: .INI ChannelFormat.txt ==== ================= TunerType TunerType Frequency Frequency Polarity Polarity Symbolrate Smbolrate FEC FEC APID Audio_PID VPID Video_PID PMTPID PMT_PID PCRPID PCR_PID AC3 AVFormat TelePID Teletext_PID SID Service_ID StreamID TransportStream_ID NetworkID OriginalNetwork_ID LNB-Selection Tone LNB LNB_LOF DiseqC DiSEqC DiSEqCValue DiSEqCExt Root Root Name ChannelName Category Category Encrypted Flags SatModulation SatModulation Group ChannelGroup Language not yet in ChannelFormat.txt, but equivalent to Reserved7+Reserved8 (3 bytes) EPGFlag not yet in ChannelFormat.txt, but equivalent to Reserved6 (1 byte) Volume not yet in ChannelFormat.txt, but equivalent to Reserved1 (1 byte) Audiochannel not yet in ChannelFormat.txt, but equivalent to Reserved2 (1 byte) OrbitalPos not yet in ChannelFormat.txt, but equivalent to Reserved5 (2 bytes) Questions Can you please check if I got the correlation right? Some fields were obvious, but some other were based on guesswork. Polarity: What is the correlation between numbers and characters? From my own samples I only got as far as 0=h, 1=v. But what about the other numbers or the other modulation systems? Audiochannel: There seems to be a casing mistake: In .ini it is written in title-case, in .csv it is written in camel-case (AudioChannel). Which one is the correct spelling, or are both accepted? Right now it is impossible to check on my own, as this field seems to be always zero. SatModulationSystem: This field appears only in .csv files. Is this equivalent to bit 2 of SatModulation (modulation system)? DiSEqCValue: Is this equivalent to DiSEqCExt? On my system, it is always zero. What does it contain? The documentation mentions, amongst others, OrbitPos, but now there is a separate field for it. Do you mind if I create an entry in the wiki based on the contents of this post and your answers? I guess this information could be also of value to other people. Best regards, eulores Edited February 11, 2010 by eulores Quote Link to comment
eulores Posted February 18, 2010 Author Share Posted February 18, 2010 Also FEC ist nicht gleich FEC! FEC as known within the context of .INI and .CSV files is one less than the value stored in the FEC field of channels.dat files. So, nach langem Suchen habe ich nun endlich entdeckt, warum bei mir mit der FloppyDTV die HDTV Kanäle nicht so richtig laufen wollten. Anscheinend spielen falsche FEC Angaben bei DVB-S keine Rolle, nicht so bei S2 Transpondern. Grüsse, eulores ps. Ich würde mich freuen falls jemand die Fragen in meinem letzten Post etwas näher betrachtet ;-) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.