search

JvanKatwijk / eti-stuff

experimental software for creating and interpreting eti frames
GNU General Public License v2.0
21 stars 12 forks source link

eti-cmdline: not able to generate DAB+ ETI file #40

Closed aleena57 closed 5 years ago

aleena57 commented 5 years ago

I could generate DAB file but am unable to generate DAB+ file. While playing the audio through dablin_gtk, audio is not clear. SDLOutput: silence started... SDLOutput: silence ended (115200 bytes) SDLOutput: silence started... SDLOutput: silence ended (117760 bytes) SDLOutput: silence started... SDLOutput: silence ended (199680 bytes) SDLOutput: silence started... SDLOutput: silence ended (101376 bytes) SDLOutput: silence started...

getting errors like (5+) or (AU #2), before the silence start/end messages

andimik commented 5 years ago

Could you please upload this file and post all messages?

What source do you use? How is the reception?

aleena57 commented 5 years ago

ETIPlayer: playing sub-channel 0 (DAB+) ETISource: reading from 'dabplustest2.ETI' FICDecoder: SubChId 0: start 0 CUs, size 96 CUs, PL EEP 3-A = 128 kBit/s FICDecoder: SId 0xE001: audio service (SubChId 0, DAB+, primary) FICDecoder: SId 0xE001, SCIdS 0: MSC service component (SubChId 0) FICDecoder: EId 0xE000: ensemble label 'REDWOOD' FICDecoder: SId 0xE001: programme service label 'REDWOOD SRV00' (0+) SuperframeFilter: Superframe sync started... (0+) SuperframeFilter: Superframe sync succeeded after 1 frame(s) ETIPlayer: format: HE-AAC v2, 48 kHz Stereo @ 128 kBit/s AACDecoder: using decoder 'FAAD2' SDLOutput: using audio buffer of 192000 bytes SDLOutput: audio opened; driver name: pulseaudio, freq: 48000, channels: 2, size: 9216, samples: 1152, silence: 0x00, output: 32bit float (AU #2) (5+) (AU #2) (0+) (AU #2) (0+) (AU #2) (0+) (AU #2) SDLOutput: silence started... (5+) (AU #1) (AU #2) SDLOutput: silence ended (9216 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (30720 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (15360 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (15360 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (15360 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (15360 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (15360 bytes) SDLOutput: silence started... (0+) (AU #2) SDLOutput: silence ended (6144 bytes) SDLOutput: silence started...

aleena57 commented 5 years ago

source is REDWOOD streamer.

andimik commented 5 years ago

Ok, then the file should be error-free of course.

aleena57 commented 5 years ago

Ok, then the file should be error-free of course.

Then what would be the issue?

basicmaster commented 5 years ago

This is difficult to say without having the actual ETI file. I tend to assume that the file content is not 100% correct for some reason. Is it this device with which you created the mux?

And with which hardward/software did you get the signal to DABlin? This cannot be seen in the posted logs, as you just play the file dabplustest2.ETI here.

Could you upload the ETI file somewhere? A minute or so would be enough, if it is too large.

BTW did you also open JvanKatwijk/eti-stuff#39 some days ago?

aleena57 commented 5 years ago

Is it this device with which you created the mux? Yes And with which hardward/software did you get the signal to DABlin? dabstick https://drive.google.com/open?id=1DFGApCGd-1esjQ3SQyay9nzCPyJceM4u

JvanKatwijk commented 5 years ago

we can see that the eti file does not give the good results, but can we get a recording of the input? with an input file I can do some checking and see where things go wrong

Op ma 21 jan. 2019 om 14:24 schreef aleena57 notifications@github.com:

Is it this device with which you created the mux? Yes And with which hardward/software did you get the signal to DABlin? dabstick https://drive.google.com/open?id=1DFGApCGd-1esjQ3SQyay9nzCPyJceM4u

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/40#issuecomment-456072977, or mute the thread https://github.com/notifications/unsubscribe-auth/AITzwOT8ZFeoj9AkWibslph0R5ogp-_jks5vFb-WgaJpZM4aKC2Y .

-- Jan van Katwijk

+31 (0)15 3698980 +31 (0) 628260355

aleena57 commented 5 years ago

I don't have recording of input. I only have the eti file.

andimik commented 5 years ago

You wrote you made the recording with a dabstick. So you can write the input file (raw or sdr file).

JvanKatwijk commented 5 years ago

I ran a quick test and I noticed that the reed-solomon decoding for DAB+ frames consistently give more errors than can be repaired. Are we sure that the incoming data is correct?

Op di 22 jan. 2019 om 06:59 schreef andimik notifications@github.com:

You wrote you made the recording with a dabstick. So you can write the input file (raw or sdr file).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/40#issuecomment-456280746, or mute the thread https://github.com/notifications/unsubscribe-auth/AITzwLvXMbYGMR2HiEYsEKWmsVlv6MNXks5vFqjcgaJpZM4aKC2Y .

-- Jan van Katwijk

JvanKatwijk commented 5 years ago

I ran some further tests and it shows that the data in the MSC is corrupted, the data in the FIC is apparently not. Looking at the et-cmdline sources (which I did not do for quite a while) shows that handling the MSC is unaware of the kind of service carried in the MSC, it handles "subchannels", so DAB, DAB+ and data channels are all handled the same.

So it is really necessary to get the incoming data. Until then I cannot be certain that the incoming data is correct

Op di 22 jan. 2019 om 11:51 schreef jan van katwijk <j.vankatwijk@gmail.com

:

I ran a quick test and I noticed that the reed-solomon decoding for DAB+ frames consistently give more errors than can be repaired. Are we sure that the incoming data is correct?

Op di 22 jan. 2019 om 06:59 schreef andimik notifications@github.com:

You wrote you made the recording with a dabstick. So you can write the input file (raw or sdr file).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/40#issuecomment-456280746, or mute the thread https://github.com/notifications/unsubscribe-auth/AITzwLvXMbYGMR2HiEYsEKWmsVlv6MNXks5vFqjcgaJpZM4aKC2Y .

-- Jan van Katwijk

-- Jan van Katwijk

basicmaster commented 5 years ago

So my current assumption is that the generator already outputs faulty DAB+. At least the PAD is affected...

andimik commented 5 years ago

So let's wait until we get a rawfile

JvanKatwijk commented 5 years ago

Agree Op 22 jan. 2019 21:09 schreef "andimik" notifications@github.com het volgende:

So let's wait until we get a rawfile

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/40#issuecomment-456544917, or mute the thread https://github.com/notifications/unsubscribe-auth/AITzwJa4AqJyYAg_FnzVBMHCq9jcEAh4ks5vF3AHgaJpZM4aKC2Y .

aleena57 commented 5 years ago

Thank you all. I got it sorted by changing bitrate in streamer.

andimik commented 5 years ago

You mean the sampling rate?

basicmaster commented 5 years ago

@aleena57: While your issue is solved now, it would be really helpful if you could provide the raw dump anyway, so that we can investigate if there is an issue on our side. I don't think so, but I would like to be sure ;-)

JvanKatwijk commented 5 years ago

It seems @aleena57 does not react anymore on the question to make the input available, so I suggest to close the issue. However, it seems not quite in line with the net-etiquette to not answer, since we all spent time addressing his/hers question. The question whether or not he/she also was responsible for issue #39 was also not answered. Sad

basicmaster commented 5 years ago

Yes, it's indeed annoying when people take, but don't give back....this would be the least...