Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synchronization loss #618

Closed
vdwjeremy opened this issue Jan 3, 2021 · 10 comments
Closed

Synchronization loss #618

vdwjeremy opened this issue Jan 3, 2021 · 10 comments

Comments

@vdwjeremy
Copy link

hello,
I loose frenquently synchronization with error "Lost coase sync" and "SyncOnPhase failed",
When that happens the frequency correction varies widely and the audio is lost for a few seconds.

synchronization.loss.mp4

SDR: Nooelec NESDR SMArt v4 (RTL2832U based)
Welle version: 2.3-dev build 2020-01-02
OS: Windows 10

Coarse corrector: CorrelatePRS (deactivated or others correctors are less effective)

The signal seems strong so I'm not sure what's happening here...
Any idea ?

@andimik
Copy link
Contributor

andimik commented Jan 4, 2021

Could you try if the same problems occur also when using rtl_sdr?

In my case it was helpful.

@vdwjeremy
Copy link
Author

How do you do that ?

@vdwjeremy
Copy link
Author

To rule out hardware or reception issues, i tried out https://www.ukwtv.de/cms/index.php?option=com_content&view=article&id=281&Itemid=550&jsmallfib=1&dir=JSROOT/dabplayer (after switching drivers) and it works fine.
This player uses Realtek driver RTKDAB.dll directly, so not open source unfortunately.

@beermad
Copy link

beermad commented Feb 12, 2021

A thought which may, or may not, be helpful.

Do the sync losses occur at regular times? The multiplex I mainly record (using welle-cli) has certain times when channels' bitrates change (usually because extra channels are added to or removed from the mux). This throws Welle off
welleErrors.log

, so I have to re-spawn the process to continue my recording. These changes happen at the same time each day (for example at 0900 and 0945, as there's an extra channel between those times).

It could be that the other player OP has tried handles bitrate changes more cleanly than Welle?

I've attached a segment of log showing the messages received when a mux reconfiguration occurs.

@andimik
Copy link
Contributor

andimik commented Feb 12, 2021

@beermad

Could you open a new issue?

According to your report this looks like a different story.

And please attach the full log as your file only shows the tail.

@beermad
Copy link

beermad commented Feb 12, 2021

@beermad

Could you open a new issue?

According to your report this looks like a different story.

And please attach the full log as your file only shows the tail.

Will do. I'll gather some comprehensive logging and post an issue in a couple of days when I've caught the right events.

@AlbrechtL
Copy link
Owner

@vdwjeremy Thanks for reporting. Which CPU your are using?

@beermad Is your issue the same like #587?

@beermad
Copy link

beermad commented Mar 27, 2021

@beermad Is your issue the same like #587?

Hi,
Looking at the log attached to that issue, it's showing the same messages I get when my muxes change config. So they're probably both the same.
Thanks.

@AlbrechtL
Copy link
Owner

OK. I marked it as duplicated.

@AlbrechtL
Copy link
Owner

I added a workaround in c0434be.

It is not a nice solution because it just restarts the decoder, which creates a short audio drop. But it is better than nothing :-).

Please test https://welle-io-nightlies.albrechtloh.de/20241009_c995c85b_Windows_welle-io-setup_x64.exe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants