[Galene] WHIP problems...

[Galene] WHIP problems...

[Tim Panton]

Hi, for ‘reasons’ I’d like to send a stream from an existing web page to galene via WHIP.
I’m running into permissions and CORS problems.

Has anyone been successful in sending WHIP to galene from a web page (i.e. not OBS) ?
If so could you please send me a bit of a cook-book ?

Thanks.

Tim.

[Galene] Re: WHIP problems...

[Juliusz Chroboczek]

> Hi, for ‘reasons’ I’d like to send a stream from an existing web page to
> galene via WHIP.  I’m running into permissions and CORS problems.

Have you set the `publicServer` flag in your `config.json`?

-- Juliusz

[Galene] Re: WHIP problems...

[Tim Panton]

> On 21 Feb 2024, at 10:12, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
>> Hi, for ‘reasons’ I’d like to send a stream from an existing web page to
>> galene via WHIP.  I’m running into permissions and CORS problems.
> 
> Have you set the `publicServer` flag in your `config.json`?

No, I’ll try that. 
Thanks.

T.


> 
> -- Juliusz
> 

[Galene] Re: WHIP problems...

[Dave Taht]

This is my test video for this: https://www.youtube.com/watch?v=j_QLzthSkfM

Less humorously I am really interested in video quality and responses
to latency and jitter in an application like this.


On Wed, Feb 21, 2024 at 4:21 AM Tim Panton <tim@pi.pe> wrote:
>
> Hi, for ‘reasons’ I’d like to send a stream from an existing web page to galene via WHIP.
> I’m running into permissions and CORS problems.
>
> Has anyone been successful in sending WHIP to galene from a web page (i.e. not OBS) ?
> If so could you please send me a bit of a cook-book ?
>
> Thanks.
>
> Tim.
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org



--
40 years of net history, a couple songs:
https://www.youtube.com/watch?v=D9RGX6QFm5E
Dave Täht CSO, LibreQos

[Galene] Latency and jitter [was: WHIP problems...]

[Juliusz Chroboczek]

> Less humorously I am really interested in video quality and responses
> to latency and jitter in an application like this.

Native Galene clients and WHIP clients use the same codepath for RTP, so
I'd expect latency and jitter to be exactly the same for WHIP and native.

I too would be interested in latency results for Galene, but such results
are better when put in context, so somebody would need to set up a lab
where they can also measure the latency of Zoom and Jitsi.  It should
preferably be somebody else than me, since I have an obvious bias, but I'd
be glad to assist the person doing the testing.

-- Juliusz

[Galene] Re: Latency and jitter [was: WHIP problems...]

[Tim Panton]

> On 21 Feb 2024, at 11:25, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
>> Less humorously I am really interested in video quality and responses
>> to latency and jitter in an application like this.
> 
> Native Galene clients and WHIP clients use the same codepath for RTP, so
> I'd expect latency and jitter to be exactly the same for WHIP and native.
> 
> I too would be interested in latency results for Galene, but such results
> are better when put in context, so somebody would need to set up a lab
> where they can also measure the latency of Zoom and Jitsi.  It should
> preferably be somebody else than me, since I have an obvious bias, but I'd
> be glad to assist the person doing the testing.

I’ve hacked together a glass-to-glass video latency measurement device.
I’ll be talking about it and publishing the how-to in April.

Happy to do a few tests on Galene and other platforms when I have a stable build.

(Currently it looks like safari is 1 frame faster than chrome ;-) )

T.
> 
> -- Juliusz
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org

[Galene] Re: WHIP problems...

[Tim Panton]

> On 21 Feb 2024, at 10:23, Tim Panton <tim@pi.pe> wrote:
> 
> 
> 
>> On 21 Feb 2024, at 10:12, Juliusz Chroboczek <jch@irif.fr> wrote:
>> 
>>> Hi, for ‘reasons’ I’d like to send a stream from an existing web page to
>>> galene via WHIP.  I’m running into permissions and CORS problems.
>> 
>> Have you set the `publicServer` flag in your `config.json`?
> 
> No, I’ll try that. 
> Thanks.
> 
> T.
> 

Not working yet, 
Here’s what I see on the chrome console...

POST https://pipe.nu/group/hunt/.whip net::ERR_ABORTED 500 (Internal Server Error)
publish @ whip.js:78
await in publish (async)


Also how do I create the bearer token for whip to send? Can I use /invite for that ?

T.

[Galene] Re: WHIP problems...

[Juliusz Chroboczek]

> POST https://pipe.nu/group/hunt/.whip net::ERR_ABORTED 500 (Internal Server Error)
> publish @ whip.js:78
> await in publish (async)

Anything in the logs?

> Also how do I create the bearer token for whip to send?  Can I use /invite
> for that ?

Yes.

-- Juliusz

[Galene] Re: Latency and jitter [was: WHIP problems...]

[Juliusz Chroboczek]

> I’ve hacked together a glass-to-glass video latency measurement device.

That's almost unbearably cool.  Please send us a note when you do a presentation.

-- Juliusz

[Galene] Re: WHIP problems...

[Tim Panton]

> On 21 Feb 2024, at 12:09, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
>> POST https://pipe.nu/group/hunt/.whip net::ERR_ABORTED 500 (Internal Server Error)
>> publish @ whip.js:78
>> await in publish (async)
> 
> Anything in the logs?

Nothing I can see. 

[Galene] Re: WHIP problems...

[Tim Panton]

> On 21 Feb 2024, at 12:51, Tim Panton <tim@pi.pe> wrote:
> 
> 
> 
>> On 21 Feb 2024, at 12:09, Juliusz Chroboczek <jch@irif.fr> wrote:
>> 
>>> POST https://pipe.nu/group/hunt/.whip net::ERR_ABORTED 500 (Internal Server Error)
>>> publish @ whip.js:78
>>> await in publish (async)
>> 
>> Anything in the logs?
> 
> Nothing I can see. 

Which figures - I think it is a service worker issue on my side. 
I’ll investigate.

T.

[Galene] Re: WHIP problems...

[Juliusz Chroboczek]

>>>> POST https://pipe.nu/group/hunt/.whip net::ERR_ABORTED 500 (Internal Server Error)

> Which figures - I think it is a service worker issue on my side. 

It looks to me like you got a 500 error from the server.  Of which there
are quite a few in the WHIP code, not all of which log an error.

    $ grep -c InternalServerError webserver/whip.go
    7

So while it might be a violation of the protocol in your code, it
shouldn't result in a 500.

-- Juliusz

[Galene] Re: WHIP problems...

[Tim Panton]

I’ve narrowed it down to this:

        pth, kind, pthid := splitPath(r.URL.Path)
-       if kind != ".whip" || pthid != "/" {
+       if kind != ".whip” {

I _think_ the test for a url ending in “/“ is wrong for .whip

T.

> On 21 Feb 2024, at 16:02, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
>>>>> POST https://pipe.nu/group/hunt/.whip net::ERR_ABORTED 500 (Internal Server Error)
> 
>> Which figures - I think it is a service worker issue on my side.
> 
> It looks to me like you got a 500 error from the server.  Of which there
> are quite a few in the WHIP code, not all of which log an error.
> 
>    $ grep -c InternalServerError webserver/whip.go
>    7
> 
> So while it might be a violation of the protocol in your code, it
> shouldn't result in a 500.
> 
> -- Juliusz

[Galene] Re: WHIP problems...

[Juliusz Chroboczek]

> I’ve narrowed it down to this:
> 
>         pth, kind, pthid := splitPath(r.URL.Path)
> -       if kind != ".whip" || pthid != "/" {
> +       if kind != ".whip” {

commit 923d78eaa30becd0afed3943b75a5230e934037f (HEAD -> master, origin/master)
Author: Juliusz Chroboczek <jch@irif.fr>
Date:   Thu Feb 22 23:31:03 2024 +0100

    Fix handling of WHIP URLs.
    
    We broke WHIP when we introduced splitPath.  Thanks to Tim Panton.