similar to: OPUS/FLAC Metadata

Displaying 20 results from an estimated 3000 matches similar to: "OPUS/FLAC Metadata"

2017 Jun 12
3
OPUS/FLAC Metadata
Marvin, That is the current version being used and it still has no meta data. server_id Icecast 2.4.99.1 Testing the metadata from the admin page “Update Metadata” results in the response: Message: Mountpoint will not accept URL updates Return Code: 1 So I would guess it isn’t functioning yet. > On Jun 12, 2017, at 12:34 PM, Marvin Scholz <epirat07 at gmail.com>
2017 Jun 12
2
OPUS/FLAC Metadata
Thanks Phiipp, I've attempted to download this previously but somehow ended up with v2.4.99 on Windows. Is there a specific path to your suggested version? This is on a Windows machine (since that might be an issue here). Rick Keniuk On 6/11/2017 9:36 AM, Philipp Schafft wrote: > Good evening, > > On Sun, 2017-06-11 at 09:24 -0500, Rick Keniuk wrote: >> Anyone know any
2017 Jun 15
2
OPUS/FLAC Metadata
Hi all, 2017-06-13 9:33 GMT-05:00 Philipp Schafft <phschafft at de.loewenfelsen.net>: > > Good afternoon, > > > On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote: > > Marvin, > > > > That is the current version being used and it still has no meta data. > > server_id Icecast 2.4.99.1 > > Icecast2 2.5 beta releases use 2.4.99.x as version
2019 May 10
2
OPUS Metadata in IceCast v2.4.4
Hello all, I may have asked this previously, but I am still on a mission to get metadata on my OPUS streams (FLAC if possible also). I am using IceCast v2.4.4 (on Windows 8.1) and RadioCaster as an encoder for OPUS streams and I know that sending the streams directly to IceCast will not pass metadata for song title and artist. I have tried using a built-in server in RadioCaster and I can see
2017 Jun 13
0
OPUS/FLAC Metadata
Good afternoon, On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote: > Marvin, > > That is the current version being used and it still has no meta data. > server_id Icecast 2.4.99.1 Icecast2 2.5 beta releases use 2.4.99.x as version number. So that is correct. > Testing the metadata from the admin page “Update Metadata” results in the response: > > Message:
2019 May 04
2
Source client with HTTP PUT
Good afternoon, On Sat, 2019-05-04 at 10:19 -0400, Fred Gleason wrote: > On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote: > > > Don't use PUT at all. Instead, open a TCP socket connection to the > port > > that the server is running on, write all of your headers to that > > (terminating each one with a CR/LF), send a naked CR/LF to tell > Icecast >
2017 Jun 12
0
OPUS/FLAC Metadata
On 12 Jun 2017, at 19:10, Rick Keniuk wrote: > Thanks Phiipp, > > I've attempted to download this previously but somehow ended up with > v2.4.99 on Windows. Is there a specific path to your suggested > version? This is on a Windows machine (since that might be an issue > here). Thats correct, that is the 2.5 beta version. > > Rick Keniuk > > On 6/11/2017
2017 Jul 31
2
Icecast 2.4.99.1 Opus Metadata. status.xsl and playlist.log
Hello, I'm currently testing Icecast 2.4.99.1 in regards to Opus metadata support. I have a Ogg Opus stream located here: http://50.31.159.156/64.opus When I playback the stream in VLC I see the expected metadata displayed in the client. ffprobe and mediainfo also return the expected metadata. # mediainfo http://50.31.159.156/64.opus General Complete name :
2019 May 04
4
Source client with HTTP PUT
Good afternoon, On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote: > On Fri, 2019-05-03 at 13:19 +0000, Jürgen Bund wrote: > > I’m writting a source client in c#, in which I’m sending chunks of a > > mp3 file with http Put to IceCast. > > My problem is, that it is not a continues stream. Each http PUT > > request is an extra track. > > How can I generate an
2017 Jun 16
3
OPUS/FLAC Metadata
On 16 Jun 2017, at 5:41, Rick Keniuk wrote: > Is this the HTTP call for injecting the “song” metadata? > This is a capture (using RawCap in conjunction with Wireshark) of my > AAC+ stream metadata input to IceCast that works fine. > > GET > /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley > HTTP/1.0
2019 May 13
2
OPUS Metadata in IceCast v2.4.4
Good morning, On Fri, 2019-05-10 at 17:59 +0100, Paul Martin wrote: > On Fri, May 10, 2019 at 10:35:39AM -0500, Rick Keniuk wrote: > > > I may have asked this previously, but I am still on a mission to get > > metadata on my OPUS streams (FLAC if possible also). > > https://tools.ietf.org/html/rfc7845.html (Section 5.2) > > ...which is similar to Ogg Vorbis
2019 Dec 08
5
How to make the playlist repeat
Good afternoon, I have two playlists going, on separate mount points, and they both exhibit this behavior. It appears that ices is shutting down when it reaches the end of the playlist. I'm getting these same four lines at the end of the logs of both playlists: [2019-12-08  00:00:53] INFO playlist-builtin/write_ogg_data module shutdown requested [2019-12-08  00:00:53] INFO input/input_loop
2019 Mar 28
3
YP Directory Listing Concern
Good afternoon, On Thu, 2019-03-28 at 21:15 +0800, Prince Naryk wrote: > can u please check my config file and see if there is something wrong with > it, You define the same listen port 3 times. Also your hostname is not set to a hostname but an IP. You also set max clients to 5000. Which is fine for Icecast. However your OS may add additional restrictions. Why do you define a
2017 Apr 11
4
Server Side Spot Replacement?
Hi guys, Can anyone share some (deep technical) light on how «Server Side Spot Replacement" on live radio streaming with Icecast can be done? Thanks, BR Rune -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20170411/e322cb01/attachment.html>
2018 Nov 09
3
Custom Hooks
Couldn't you also just have a client stream locally from icecast that can do things on metadata change? I mean it's a bit icky but it'd work. ---- Philipp Schafft wrote ---- >Good morning, > >On Thu, 2018-11-08 at 12:45 -0500, Alex Hackney wrote: >> I actually got this to work this morning finally. The problem was on my >> auth server. > >Perfect. :) >
2019 Aug 13
2
MetaData Update for FLAC and OPUS
It seems, that with FLAC and OPUS streams (not individual files) the song title (meta data) updates do not work. Also the ICEcast admin web interface isn’t working for FLAC and OPUS; while it is working for MP3, AAC as well as OGG streams. I.e. when sending a continuous FLAC or OPUS stream to an ICEcast server, it seems impossible to update the meta data mid-stream (like it works for MP3, AAC
2018 Nov 15
4
How to concatenate Ogg in the browser JS?
Thank you, ogginfo returned: ----- Note: Stream 1 has serial number 0, which is legal but may cause problems with some tools. New logical stream (#1, serial: 00000000): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: ffmpeg Channels: 1 Rate: 22050 Nominal bitrate: 35.333000 kb/s Upper bitrate not set Lower bitrate not set Vorbis stream 1: Total data
2019 May 14
2
OPUS Metadata in IceCast v2.4.4
Good afternoon, On Mon, 2019-05-13 at 17:55 +0100, Paul Martin wrote: > On Mon, May 13, 2019 at 08:45:40AM +0000, Philipp Schafft wrote: > > Support for metadata in Opus is a feature of Icecast 2.5.x. It has first > > been included in v2.5.0-beta.2. But please note that this is only about > > displaying. > > I can see support for reading it from incoming Ogg/Opus
2016 Dec 27
1
dir.xiph.org : OPUS stream wrongly identified as Vorbis
Yes, Le 27/12/2016 à 16:09, Philipp Schafft a écrit : > -kh is not a branch but a private fork. The Foundation has no control > over it nor do any updates on the official Icecast automatically go into > that fork. (Also: the code is generally considered incompatible) I'm only using the -kh fork because it supports the X-Forwarded-For header. Hoggins! -------------- next part
2017 Jan 25
2
Icecast 2.4.0 max-listener-duration
I'm using the KH edition of Icecast 2.4.0 but it may also related to the standard release. I added the following to my config xml file but the file cannot be parsed is the error... <mount type="default"> <max-listener-duration>28800</max-listener-duration> </mount> Any ideas of the problem? Thanks. -------------- next part --------------