similar to: Support for METADATA_BLOCK_PICTURE in any players?

Displaying 20 results from an estimated 500 matches similar to: "Support for METADATA_BLOCK_PICTURE in any players?"

2012 Mar 24
1
icy-metaint in header and in stream data
Normally icy-metaint is a line in the http header, but some stream only sends it in the response data is self. Where can I find such a stream? Is that compliant to the standard? Implementation that also parses the response data http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadata-in-android-2-2 Thank Stig -- Best Regards / Mvh Stig Christensen stig
2007 Jan 07
1
METADATA_BLOCK_PICTURE question
Hi everybody, I have a question about the following part of the METADATA_BLOCK_PICTURE specification. The components: Width, Height, Color Depth, and Colors Used don't provide an "unknown" value and seem to assume that the program encoding the METADATA_BLOCK will be aware of these components of the file. As these fields seem to just provide "extra" information (I'm
2010 Sep 04
9
I think vorbis codec group have a new target
I compared quicktime aac and vorbis,i think quicktime aac is better than vorbis at 80Kbps. please tell me if i'm wrong. using command: qtaacenc.exe --tvbr 31 --highest --samplerate keep test.wav qt.m4a oggenc2.exe --raw -q 1.6 test.wav -o vorbis.ogg the version: qtaacenc version 20100725 with QuickTime 7.6.7 OggEnc v2.87 (libvorbis 1.3.1) links:
2012 Apr 17
1
command line perl tool to create ogg/Vorbis picture comments
On 14 April 2012 23:40, Ian Malone <ibmalone at gmail.com> wrote: > On 14 April 2012 23:34, Ian Malone <ibmalone at gmail.com> wrote: > >> http://pastebin.com/xXhPyZuQ > >> ./jpegtoblock.pl ?-i DSCN7376.JPG -o flacblock > >> You'll need to add the "METADATA_BLOCK_PICTURE=" which makes it into a >> comment file yourself. >> >
2019 Jun 21
3
support free WEBP images in Opus files
WebP (imagepart of VP9) is better then JPG AVIF (imagepart of VPX/AV1) is better then HEIF please support in OPUS file for album arts more then JPG and PNG... WebP and AVIF are free imageformats can store multiple images thats good for the problem with METADATA_BLOCK_PICTURE only can store one file. i try to push some devs of player and converter to support this too. wbr from berlin
2011 Jan 20
1
Flac] Where Cover Art?
"Santiago Jimeno" wrote: > Flac files, as us knows, follows the Vorbis Tags system included in block 4 > Recently Vorbis has established the possibility to include picture files by > means of 2 Tags: COVERARTMIME AND COVERART. > To work therewith is quite easy. No. this in incorrect. The VorbisComment "COVERART" was only ever unofficial, and has been deprecated
2013 Nov 28
3
pictures
Hello, I have problems with encoding FLAC-Files with embedded pictures. Currently i use opus-tools 0.1.7 with libopus 1.1-rc2. After encoding opusinfo shows WARNING: Unknown picture type in METADATA_BLOCK_PICTURE comment 12 (stream 1): 1768776039 WARNING: Invalid mime type length in METADATA_BLOCK_PICTURE comment 12 (stream 1): 1697607790 bytes when 5562 are available When i play the files with
2014 Feb 12
2
[user] coverart and other tags
On Wed, 2014-02-12 at 14:29 +0000, Ian Malone wrote: > On 12 February 2014 13:02, Alice Wonder <alicewonder at shastaherps.org> wrote: > > Hello, > > > > I am new to using opus but so far I really am loving it. At 16kbps > > spoken content sounds fabulous. > > > > I am using opusenc on 64-bit linux - mostly with flac input. > > > > The one
2014 Jun 20
2
Lets work towards a new version
On Fri, Jun 20, 2014 at 1:05 AM, lvqcl <lvqcl.mail at gmail.com> wrote: > I cannot find anything about the size of METADATA_BLOCK_PICTURE block > in <http://xiph.org/flac/format.html>. Where did you read this? > METADATA_BLOCK_HEADER has a 24-bit field to encode the length of METADATA_BLOCK_DATA ; hence the limitation (which not only applies to METADATA_BLOCK_PICTURE but all
2019 Jun 21
1
support free WEBP images in Opus files
Oops, meant to add, there's absolutely no restrictions on the format of any picture block, either, and opusenc will already just add whatever gets passed in without even trying to verify anything about the file format. That's up to tagging and playback software to support; foobar2000, for instance, only supports formats that are part of Windows' GDIplus library. On Fri, Jun 21, 2019
2014 Jun 19
2
Lets work towards a new version
On Thu, 19 Jun 2014 05:00:39 +0400 lvqcl <lvqcl.mail at gmail.com> wrote: >Erik de Castro Lopo wrote: > >> It sees that the most serious bug in the flac bug tracker: >> >> https://sourceforge.net/p/flac/bugs/413/ >> >> has been fixed in git. This fix alone is worth a new release so its >> time to work towards one. >> >> Things I need
2014 Feb 12
3
[user] coverart and other tags
Hello, I am new to using opus but so far I really am loving it. At 16kbps spoken content sounds fabulous. I am using opusenc on 64-bit linux - mostly with flac input. The one thing I can't figure out how to do is add album art. I tried passing the vorbis way of adding a metadata_block_picture comment field to opusenc but it complained about the length. I can't seem to find any
2009 Jul 23
1
Fixing ogg vorbis corruption caused by bad metadata
> However, there is a general point. ?Xiph policy > now encourages cover art in VorbisComments > using the METADATA_BLOCK_PICTURE tag, > visit: > http://wiki.xiph.org/VorbisComment#Cover_art > > This means that VorbisComments can be > huge, and so memory for them now needs to > be allocated from the heap, not the stack. Huge is relative. Are people really sticking
2008 Apr 12
1
base64 ALBUMART vorbiscomment
" Ivo Emanuel Gon?alves " <justivo at gmail.com> wrote: ... > To be fair, only the Vorbis users requested albumart. FLAC users > should in theory be able to use the tag too if they want, but this > wouldn't be something we'd see in other codecs like Speex and Theora. This is a minor point, but FLAC users can already do this using METADATA_BLOCK_PICTURE (which
2015 Oct 12
2
Use of alloca in vorbis_comment_add_tag
Dear Vorbis devs, I'm Robert Kausch, author of fre:ac - free audio converter. Please consider using _ogg_malloc/_ogg_free in place of alloca in vorbis_comment_add_tag. alloca will cause undefined behaviour/crashing when it causes a stack overflow which can easily happen when adding cover art in a METADATA_BLOCK_PICTURE comment. I had a user trying to convert a FLAC file with a 2 MB
2008 Oct 18
1
Album art - requirements
>> So, a possible way to encode album art would be: >> >> - a Skeleton stream with appropriate header messages >> - one Kate stream per image, carrying a PNG image >> (alternatively, use Ogg/MNG, if someone brings it from the dead) >> [...] Silvia wrote: >Interesting proposal. Not sure it won't over-complicate album art though... Well yes, of course
2011 Jan 23
0
Flac] Where Cover Art?
OK Martin. Thank you for the explanations and for your time. I am writing a program that reads and writes all existent Tags types. It lacks only to end the edition (rewriting) of "Native" Flac and Matroska. Both cases for the same problem: the separation of Tags and Picture in different blocks. In Flac I resolved it, but now I have to add METADATA_BLOCK_PICTURE. Reading Vorbis
2011 Jan 22
0
Flac] Where Cover Art?
You said "With the exception of where to put a picture file, VorbisComments in a Vorbis stream are the same as VorbisComments in a FLAC stream." In METADATA_BLOCK_PICTURE case they would not be the same. Up to now we could exchange the complete block of VorbisComments. But with the addiction of METADATA_BLOCK_PICTURE doesn't happen this way. In Ogg files the METADATA_BLOCK_PICTURE
2007 Aug 09
1
odfWeave processing error, file specific
Hello, I hope there is a simple explanation for this. I have been using odfWeave with great satisfaction in R 2.5.0. Unfortunately, I cannot get beyond the following error message with a particular file. I have copied and pasted into new files and the same error pops up. It looks like the error is occurring before any of the R code is run (?). Any suggestions on how to track this down and fix
2009 Aug 01
1
odfWeave : sudden and unexplained error
Dear list, dear Max, I a currently working on a report. I'm writing it with OpenOffice.org and odfWeave. I'm working increentally : I write a bit, test (interactively) some ideas, cutting-and-pasting code to the Ooo report when satisfied with it. I the process, I tend to recompile the .odt source a *lot*. Suddenly, odfWeave started to give me an incomprehensible error even before