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

"cannot unify two nested clocks" error #771

Closed
gammaw opened this issue May 9, 2019 · 3 comments
Closed

"cannot unify two nested clocks" error #771

gammaw opened this issue May 9, 2019 · 3 comments
Labels

Comments

@gammaw
Copy link

gammaw commented May 9, 2019

Hi,

I have a Liquidsoap configuration which throws the error in the title.

The background is this: AzuraCast/AzuraCast#1513

In theory I know a fix (which would be to define and use the live source at later point in the configuration) but it cannot be done given how the configuration is generated. Other ideas given the constraints? I thought of somehow removing the live source and redefining and adding it to the final source.

Thanks!

@gammaw
Copy link
Author

gammaw commented May 9, 2019

Did some reading, removed crossfade (somewhere earlier in the config) and now Liquidsoap starts. Fading now doesn't work as expected though, maybe I'm using an older release. I saw that you were fixing some bugs related to transitions. Btw, do you have fresh documentation (or release > 1.3.6? I had an issue the other day which drove me crazy thinking that ! stands for logical NOT and didn't find it in the documentation (in fact, ! stands for dereferencing).

@toots
Copy link
Member

toots commented May 19, 2019

Hi,

We're working on a serious rewrite of the documentation with @smimram.

As for your original issue, the problem most likely comes from having two sources that have different clocks, for instance input.alsa and input.gstreamer and trying to unify them, which mean having them under the sam operator, for instance a switch.

Sharing mode code example would make this easier to explain.

@toots toots added the usage label May 19, 2019
@smimram smimram added bug and removed usage labels May 27, 2019
@smimram
Copy link
Member

smimram commented Jul 26, 2021

We cannot do much more without code extracts and clocks are not documented in details in the book. Closing, feel free to reopen if needed.

@smimram smimram closed this as completed Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants