Re: [RDD] Glasscoder HLS encoding

[Frank Schultze]

Hi Fred and All,

Apologies for resurrecting an old thread. I thought I had this sorted, but
on a test installation I dont get any joy.

1. I've installed a test version of Rivendell 4 on an Ubuntu AWS instance
and I can successfully use Glasscoder to send audio to an IceCast server.
2. I'm now trying to get Glasscoder to serve a HLS stream locally on the
same machine with:
*glasscoder --server-type=hls --server-url=file:///var/www/html/hls_1/
--verbose --audio-format=aacp --audio-samplerate=48000 --audio-channels=2
--audio-bitrate=48 --audio-device=jack --jack-server-name="default"
--jack-client-name=hls_1 --jack-gain=0*
3. I can connect the jack clients and all looks fine. Audio assignments in
rdadmin are fine - I've tested with other streams. The m3u8 manifest and
payload files are writing fine. I'm running these jack clients from
rdadmin->Host Settings->Jack.
4. When I try stream from the box I just get a constant stereo tone,
instead of what rdairplay is playing. I'm connecting to the machine with
Safari & VLC at:
*http:///hls_1/hls_1.m3u8*

I was hoping someone had possibly run into this problem, and could share
ideas?

Thanks,
Frank

On Sat, 12 Feb 2022 at 09:20, Frank Schultze 
wrote:

>
> On Tue, 8 Feb 2022 at 15:07, Fred Gleason 
> wrote:
>
>> On Feb 7, 2022, at 08:39, Frank Schultze 
>> wrote:
>>
>> I would like to set up an HLS stream directly from a Rivendell machine
>> already running Glasscoder to an Icecast2 server - all working fine.
>> Setting up another instance of Glasscoder for HLS I'm able to get the PUT
>> requests at an nginx web server (manifest and data files) but the server
>> won't save and therefore deliver them.
>>
>> According to my readings nginx is able to process these requests directly
>> using WebDAV and write these (maybe even cache them) for availability on
>> the web server as http://sample.com/sample.m3u8?
>>
>> Could anyone please point me in the right direction without having to
>> write a RESTful API?
>>
>>
>> You have several options. First though, a bit a clarification: Icecast2
>> has nothing to do with HLS streaming. Those two streaming systems are
>> completely orthogonal.
>>
>> GlassCoder can publish HLS in three different methods: FILE, HTTP[S] and
>> SFTP. The FILE method is simple to set up but requires that GlassCoder be
>> running on the same system that is serving the streams. HTTP uses basic
>> ‘garden variety’ PUT and DELETE transactions; WebDAV is not necessary and
>> would be massive overkill. I’ve no experience with nginx, but GlassCoder is
>> known to work well with Apache httpd; see the ‘docs/‘ directory in the
>> installation package for a sample Apache configuration. Really, any web
>> server that supports standard PUT and DELETE should work just fine though.
>>
>> In many ways however, the third method, SFTP, is the easiest and most
>> flexible. SFTP uses the widely deployed Secure Shell protocol, and is
>> basically just another name for the scp(1) functionality that ships as part
>> of Secure Shell.
>>
>> Thanks Fred,
>
> Looks like the SFTP method will do what I need. This system will
> eventually send out three streams 1) To Icecast2 2) To HLS server and 3) To
> a DAB+ trial mux using odr-mmbtools.
>
> Thanks again,
> Frank
>

-- 
The information contained in this communication is legally privileged, 
confidential and may
contain proprietary and/or personal information. It is 
intended solely for use by the individual
or entity to whom it is 
addressed, and those authorized to receive it. If you are not the
intended 
recipient, you are hereby notified that any disclosure, copying, 
distribution or any
action taken or omitted on this basis is prohibited and 
may be unlawful. AME Ltd respects
your privacy and we acknowledge that this 
email may contain personal information. By
sending this communication you 
expressly give AME Ltd, consent to process the personal
information in this 
email which will be done in accordance with the Protection of Personal
Information Act 4 of 13. AME is not liable for the proper, complete 
transmission of the
information contained in this communication and/or any 
delay in its receipt.
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Glasscoder HLS encoding

[Frank Schultze]

On Tue, 8 Feb 2022 at 15:07, Fred Gleason  wrote:

> On Feb 7, 2022, at 08:39, Frank Schultze 
> wrote:
>
> I would like to set up an HLS stream directly from a Rivendell machine
> already running Glasscoder to an Icecast2 server - all working fine.
> Setting up another instance of Glasscoder for HLS I'm able to get the PUT
> requests at an nginx web server (manifest and data files) but the server
> won't save and therefore deliver them.
>
> According to my readings nginx is able to process these requests directly
> using WebDAV and write these (maybe even cache them) for availability on
> the web server as http://sample.com/sample.m3u8?
>
> Could anyone please point me in the right direction without having to
> write a RESTful API?
>
>
> You have several options. First though, a bit a clarification: Icecast2
> has nothing to do with HLS streaming. Those two streaming systems are
> completely orthogonal.
>
> GlassCoder can publish HLS in three different methods: FILE, HTTP[S] and
> SFTP. The FILE method is simple to set up but requires that GlassCoder be
> running on the same system that is serving the streams. HTTP uses basic
> ‘garden variety’ PUT and DELETE transactions; WebDAV is not necessary and
> would be massive overkill. I’ve no experience with nginx, but GlassCoder is
> known to work well with Apache httpd; see the ‘docs/‘ directory in the
> installation package for a sample Apache configuration. Really, any web
> server that supports standard PUT and DELETE should work just fine though.
>
> In many ways however, the third method, SFTP, is the easiest and most
> flexible. SFTP uses the widely deployed Secure Shell protocol, and is
> basically just another name for the scp(1) functionality that ships as part
> of Secure Shell.
>
> Thanks Fred,

Looks like the SFTP method will do what I need. This system will eventually
send out three streams 1) To Icecast2 2) To HLS server and 3) To a DAB+
trial mux using odr-mmbtools.

Thanks again,
Frank

-- 
The information contained in this communication is legally privileged, 
confidential and may
contain proprietary and/or personal information. It is 
intended solely for use by the individual
or entity to whom it is 
addressed, and those authorized to receive it. If you are not the
intended 
recipient, you are hereby notified that any disclosure, copying, 
distribution or any
action taken or omitted on this basis is prohibited and 
may be unlawful. AME Ltd respects
your privacy and we acknowledge that this 
email may contain personal information. By
sending this communication you 
expressly give AME Ltd, consent to process the personal
information in this 
email which will be done in accordance with the Protection of Personal
Information Act 4 of 13. AME is not liable for the proper, complete 
transmission of the
information contained in this communication and/or any 
delay in its receipt.
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Glasscoder HLS encoding

[Fred Gleason]

On Feb 7, 2022, at 08:39, Frank Schultze  wrote:

> I would like to set up an HLS stream directly from a Rivendell machine 
> already running Glasscoder to an Icecast2 server - all working fine. Setting 
> up another instance of Glasscoder for HLS I'm able to get the PUT requests at 
> an nginx web server (manifest and data files) but the server won't save and 
> therefore deliver them.
> 
> According to my readings nginx is able to process these requests directly 
> using WebDAV and write these (maybe even cache them) for availability on the 
> web server as http://sample.com/sample.m3u8 ?
> 
> Could anyone please point me in the right direction without having to write a 
> RESTful API?

You have several options. First though, a bit a clarification: Icecast2 has 
nothing to do with HLS streaming. Those two streaming systems are completely 
orthogonal.

GlassCoder can publish HLS in three different methods: FILE, HTTP[S] and SFTP. 
The FILE method is simple to set up but requires that GlassCoder be running on 
the same system that is serving the streams. HTTP uses basic ‘garden variety’ 
PUT and DELETE transactions; WebDAV is not necessary and would be massive 
overkill. I’ve no experience with nginx, but GlassCoder is known to work well 
with Apache httpd; see the ‘docs/‘ directory in the installation package for a 
sample Apache configuration. Really, any web server that supports standard PUT 
and DELETE should work just fine though.

In many ways however, the third method, SFTP, is the easiest and most flexible. 
SFTP uses the widely deployed Secure Shell protocol, and is basically just 
another name for the scp(1) functionality that ships as part of Secure Shell.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Glasscoder HLS encoding

[Frank Schultze]

Hi All,

Apologies upfront for this being an off-topic request. It would seem this
request is more to do with HTTP PUT and DELETE methods than Rivendell, but
I've nowhere else to turn.

I would like to set up an HLS stream directly from a Rivendell machine
already running Glasscoder to an Icecast2 server - all working fine.
Setting up another instance of Glasscoder for HLS I'm able to get the PUT
requests at an nginx web server (manifest and data files) but the server
won't save and therefore deliver them.

According to my readings nginx is able to process these requests directly
using WebDAV and write these (maybe even cache them) for availability on
the web server as http://sample.com/sample.m3u8?

Could anyone please point me in the right direction without having to write
a RESTful API?

Thanks in advance,
Frank

-- 
The information contained in this communication is legally privileged, 
confidential and may
contain proprietary and/or personal information. It is 
intended solely for use by the individual
or entity to whom it is 
addressed, and those authorized to receive it. If you are not the
intended 
recipient, you are hereby notified that any disclosure, copying, 
distribution or any
action taken or omitted on this basis is prohibited and 
may be unlawful. AME Ltd respects
your privacy and we acknowledge that this 
email may contain personal information. By
sending this communication you 
expressly give AME Ltd, consent to process the personal
information in this 
email which will be done in accordance with the Protection of Personal
Information Act 4 of 13. AME is not liable for the proper, complete 
transmission of the
information contained in this communication and/or any 
delay in its receipt.
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev