similar to: comment header specification

Displaying 20 results from an estimated 9000 matches similar to: "comment header specification"

2005 Sep 07
2
AACPlus Shoutcast v1.90
If you have access to a Windows box, Winamp v5.1 can rip CD's to AAC+. I can't imagine why you would want to do that normally, but it would be useful for comparisons. Ross. ----- Original Message ----- From: "Karl Heyes" <karl@xiph.org> To: "Ross Levis" <ross@stationplaylist.com> Cc: "icecast" <icecast@xiph.org> Sent: Thursday, September
2001 Sep 03
2
lowpass option (Was: RE: channel coupling in rc2)
I would very much like a lowpass option because for FM radio broadcasting I don't want to encode frequencies above 15khz. I'm waiting for this option before switching to ogg from mp3(lame). Ross. > -----Original Message----- > From: owner-vorbis@xiph.org [mailto:owner-vorbis@xiph.org]On Behalf Of > Gian-Carlo Pascutto > Sent: Tuesday, 4 September 2001 01:46 > To:
2006 Feb 03
1
padding in comment header
Having looked through the archives I've come to the conclusion that to do padding for comments (in a file tagging context) the simplest solution is to zero pad the comment header packet to fixed length[1] and regenerate pages from #2 up to the first one containing the setup header. Is this correct? Not very closely related: should doing ogg_stream_pagein followed by
2009 Jun 28
6
Tidy up of XiphWiki VorbisComment page
I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the
2002 Mar 05
3
UTF-8 & Hebrew
Sorry if this is offtopic. My Win32 comment editor uses a routine of my own to read comments directly from OGG files but uses vorbiscomment.exe to write comments. I've implemented a UTF-8 function which I found on the internet to decode UTF-8. It appears to be working fine for most European characters, however, I have a Russian user using WinXP who is entering Hebrew characters such as
2009 Jul 17
2
Decoding setup header
On Fri, Jul 17, 2009 at 12:48:27PM -0700, Ralph Giles wrote: > > In my ongoing quest to restore corrupted ogg files, I'm trying to find > > an easy way to identify the setup header without having to actually > > decode it. I understand that it starts with [packet_type] = 5 and then > > the string 'vorbis', but is there some way to figure out where it > >
2002 Feb 27
3
WinVorbis 1.1 released (UTF-8 support, final notice)
This will be the last announcement of WinVorbis releases on this list. Visit the website to keep up to date. WinVorbis is now UTF-8 compliant! For some reason VorbisComment doesn't support UTF-8 characters in tag names, only in tag data. Added a case conversion routine which uppercases the first letter of every word and lowercases the rest. It is implemented in the templates by using
2003 Feb 12
2
Comment fields don't like accents!
Anyone know, under Linux, how to get accents (hoping for u with an umlaut, for example) into a comment field? They're happily in the comment file I'm using as a source (or on the command line), but they get translated into # either when I do vorbiscomment -a or vorbiscomment -l (not sure which, but XMMS also sees # instead of the right char, which implies the first). title=Die Sch#ne
2004 Apr 21
2
Changing comment-tags
Hello, i use libvorbis to develop some small applications for a radio station. I wonder, why there are no functions in the library to add/modify the comment tags in ogg-files. The only way I found is to make use of vorbiscomment binary, but this way is not that good. Are there api calls to do this?? thanks, Daniel. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project
2008 Dec 18
2
Updated comment padding patches
I've attached updated patches (against vorbis-tools 1.3.0b3.5) to support comment padding. No changes to libvorbis are necessary. The padding is added in the same way as oggenc2 (null bytes within the packet, at the end) and shouldn't cause problems with any reasonable decoder or comment editor implementations. Padding is enabled by default, except for small files (less than 30 s for
2007 Nov 05
2
edit comment
How i can edit the comments of a vorbis file? _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL:
2004 Sep 10
2
[Flac-users] Can I use Vorbis comment on ogg - flac?
Hello flac-users, I'm storing my ripped CDs on FLAC until Vorbis 1.0 gets out (supposedly RSN). But I want to enter the vorbis comment just once. Since I'll use ogg bitstream for both files, I was wondering if I could use vorbiscomment or tOGGer on ogg-flac files? Is there any tool (besides de pipe) to convert ogg-flac to ogg-vorbis? Best regards, Alejandro Belluscio
2004 Sep 10
2
[Flac-users] Can I use Vorbis comment on ogg - flac?
Hello flac-users, I'm storing my ripped CDs on FLAC until Vorbis 1.0 gets out (supposedly RSN). But I want to enter the vorbis comment just once. Since I'll use ogg bitstream for both files, I was wondering if I could use vorbiscomment or tOGGer on ogg-flac files? Is there any tool (besides de pipe) to convert ogg-flac to ogg-vorbis? Best regards, Alejandro Belluscio
2016 Dec 31
2
comment writing in opus / liboggz
It seems there still isn't a tool (at least not a Xiph one) for modifying Opus comments from the command line. I've had a go at adding support in liboggz (which is fairly trivial, since it just means adding recognition for the Opus stream). That certainly works for comment editing, but I'm not sure if it's is good enough to commit back, because timing gets reported back slightly
2016 Dec 31
2
comment writing in opus / liboggz
It seems there still isn't a tool (at least not a Xiph one) for modifying Opus comments from the command line. I've had a go at adding support in liboggz (which is fairly trivial, since it just means adding recognition for the Opus stream). That certainly works for comment editing, but I'm not sure if it's is good enough to commit back, because timing gets reported back slightly
2007 Mar 17
5
2nd attempt - Repairing vorbis files
Hello, No public anwer came to my previous post, and my problem is urgent, so I'm trying again. I'm using Ogg Vorbis since 2000 and some of my files appear to be damaged - at least some players reject some of them (WinAmp, Quintessential Media Player beta 116). Is there a repair tool for Windows which could rebuild vorbis files so that they all could be played in WinAmp, which is very
2009 Jun 11
3
SIP hacked connection?
Hi Running 1.2.26 BRI stuffed. Calls made via PSTN via ISDN interface (Junghanns). SIP ports mapped through firewall as we often connect from outside, but all SIP accounts have good passwords. However our telecoms provider picked up a few suspicious calls to places we do not normally call at times we do not often call. Looking at Asterisk logs it shows SIP session from the internet connected
2008 Sep 22
2
Can Vorbis comment tags be empty ?
Hi, I've written some code to validate comments passed to libkate, which happens to use the Vorbis comments format (apart from the framing bit, which I dumped rather early). While coding this, I wondered if I should allow empty tags (eg, '=foo'). I had a look at liboggz and vorbiscomment, and they both allow it (I didn't test vorbiscomment, just looked at the source). However,
2004 Sep 26
1
Samba 2.2.11 upgrade funkyness !!!
Hi all. Am experiancing strange issues with Samba 2.2.11 after upgrading from 2.2.7a. Running it as a Domain Member server to an NT4 PDC the ./config/make/make install was fine, no issues, compiled with same options needed to edit the smb rc file at /etc/rc/d/init.d/smb and make these chamges daemon /usr/local/samba/bin/smbd -D -s /etc/samba/smb.conf daemon /usr/local/samba/bin/nmbd -D -s
2016 Dec 31
3
[ogg-dev] comment writing in opus / liboggz
On 31 December 2016 at 14:03, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Ian Malone wrote: >> >> out, due to the Opus pre-seek, I think. Fixing that probably requires >> adding an Opus-specific metric to liboggz, since the current default >> linear one doesn't deal with first granule position being set. Thought >> I'd check before getting