Closed andimik closed 9 months ago
Yes, the log helps. I had a look at this file, and it shows tons of MOT packet errors, crc Errors etc. QIRX will never be able to decode such a stream.
An example from the log, as displayed by log4view:
I am not familiar with AbracaDABra. If you want to have the behavior in QIRX investigated, I need some raw file (a raw, not an ETI) of sufficient length. Otherwise, no chance.
Qirx has no problems with the audio, the signal is 100%, see screenshot.
See the last remark of my last posting.
It takes around 10 hours to send you the 2 GB raw file via wetransfer. Please be patient.
I really encourage you to install ODR-DabMod, as the 2 GB raw-file is just 58 MB in an eti (compressed).
https://get.hidrive.com/i/Zk6XJ8ZJ (58 MB eti, zipped)
In case the 150 MB raw is enough, it's here.
https://get.hidrive.com/i/VSxF9eyP
If not, I need to send you the 2 GB on a DVD probably per Post. I tried several times on various file hosters, I had no luck and it always ended in an error before EOF.
Thanks for the files. I try with the 150MB one. If it is too small, it will take some time, as I have currently no time to tinker around with the ODR tools.
To be honest, I have a problem understanding your reasoning, as the (popular!) Google Dropbox allows 2G. I used it very often for files above 1G. Are the 2G necessary? Does it really take almost 10 minutes to complete the EPG in your mux?
Yes of course, otherwise I would have not mentioned 2 GB.
I sent you a PM, with an alternative suggestion for Upload of your file.
@andimik ,
Thanks for uploading a raw file of about 10 minutes, Multiplex E4-9400 SLO DAB+ R2 W.
I analyzed your file, with the following result:
Also the relaxed "MOT Header Mode" for general MOT Objects requires a corresponding data Group type of "MOT Header"., which was not observed during the reception (and is not handled by QIRX).
To summarize, as QIRX works for SPI decoding only in Directory Mode, as required by the Standard, the SPI content in the file will not be decoded by QIRX.
Remark: The "Blinking Lamps" on the GUI, usually indicating an ongoing collection of SPI objects, cannot be omitted, because an object of data group type "MOT Directory" can arrive at any point in time, unknown by the software.
No new comments, I close it.
Well, my comment is, I have technically no idea here and need to trust you.
Good news, the broadcaster (RTV Slovenija) has fixed the issue. For a while there was no SPI transmitted at all, but now it works also in Qirx (at least for the Logos, the EPG does not work in Qirx, although there is a preview, which I can see in AbracaDABra).
The header in the old xml file was
<serviceInformation creationTime="2024-07-08 09:27:56" originator="AVT MAGIC DABMUX">
now it is
<serviceInformation creationTime="2024-10-28 08:32:11">
Probably they had a hardware upgrade recently, which finally seems to be compliant with the standard.
Mentioned in https://www.rundfunkforum.de/viewtopic.php?p=1747230#p1747230
Although two muxes in Slovenia (R2W and R2E) have introduced a real EPG within SPI, no files are stored in the SPI folder.
AbracaDABra has no problems with the data.
Maybe the following log helps?
qirx.logqirx.log-2024-02-01--00-13-31.txt.zip
Remark: As you can see, none of the services got a station logo