Live 360° Stream to VR Headset

[goamberg 0]

Hi all

I hope I am in the right corner of this forum for this question:
and I know it may not the optimal way to do this and will be happy to go a different route ;-). I am quite new to this...

I am using Emby server as a Mediaserver for Live Streaming to VR Headsets. We produce the 360° content ourselfs and use a strong WIFI setup provided by the client.
The setup is as following:
Xsplit produces an RTMP Stream. I made a *.strm file for the emby libary pointing to that RTMP stream. The VR App can see the Media Server without any problem and can start the stream from the libary.
Meanwhile on the PC with the libary on it, it starts to produce a .ts video file. So far all good.

Now to my problem with being live.
On the 2nd (or 3rd or 10th) headset it also can access the stream with no problem - but it starts playing the .ts file from the beginning and not really live.
So when I start the first headset, all player started later, have always a delay from that time the first stream started.

Is there any way to access the stream dirctly? Bandwith is no problem at all

Cheers
Goam

[Luke 42080]

Hi, can we look at the server log from an example?

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

[goamberg 0]

Hi
Of course Here is the embyserver file with starting and accesing the live stream via a Oculus Go Headset over WIFI from a fresh start ob emby A .ts file is saved to transcoding.tmp and the next headset accessing the stream will start from the beginning of the file saved in temp and not a the acutal time where the livestream is.

Cheers
Goam

embyserver-63670386232.txt

ffmpeg-directstream-f3ffb552-1199-4746-b075-3dd71f4882b3.txt

[Luke 42080]

Is the ffmpeg log supposed to have deviceid=test, or did you edit that?

[goamberg 0]

dont know what the deviceid=test means.
Its just the file that was created besides the embyserver log file. No editing from my side.
 

[Luke 42080]

Ok, I assume you redacted them because you didn't want them to be seen publicly. If your devices are actually both reporting a device id of test, then that explains the problem because the server will think they're the same device.

[goamberg 0]

ah ok. understood. when the device id would be different, a new .ts file and so on would be started for each device...am I understanding this correctly?

what is the device id in this context? The headsets were 5 Oculus Go Headsets and they all were reading the same .ts file ( but it was the same app - Samsung VR)

[Luke 42080]

That's correct. Well it looks like you're using dlna, so the device id just comes from the reported uuid.

[Luke 42080]

Nevermind, I can add a workaround for the next release. Thanks.

[goamberg 0]

thanks!, awesome support!

But now I ran into another problem.
For no reason, at least to me, it starts to transcode now instead of direct play. As far as I remember I didn´t change any settings that would activate this.
DLNA direct play is set to all video all audio as in the default profile.

Goam

ffmpeg-transcode-3a75b8b6-386b-45e3-a566-e4c78b80d635.txt

embyserver-63670628677.txt

[Luke 42080]

We don't have media info so it transcodes in order to ensure that it will just work.

[goamberg 0]

ok, understood.

What I dont understand is what is the difference from Monday (and all last month) to today.
Earlier it worked fine with directplay and now it starts transcoding.
Same xsplit local stream as always.
Any idea how I can add this information for the input, that the transcode does not start?

(tested now with several windows and emby restarts)

Goam

ps.
attached the 2 logs with transcode and directplay from Monday and today.

ffmpeg-directstream-f3ffb552-1199-4746-b075-3dd71f4882b3.txt

ffmpeg-transcode-3a75b8b6-386b-45e3-a566-e4c78b80d635.txt