similar to: HOgg Release 0.4.1

Displaying 20 results from an estimated 4000 matches similar to: "HOgg Release 0.4.1"

2008 Dec 23
0
HOgg Release 0.4.1
Here's some instructions for installing hogg on a current Ubuntu 8.10 (or Debian unstable? testing?) system, ie. if you don't already have haskell's cabal system installed: $ sudo apt-get install ghc6 $ wget http://hackage.haskell.org/packages/archive/cabal-install/0.6.0/cabal-install-0.6.0.tar.gz $ tar zxf cabal-install-0.6.0.tar.gz $ cd cabal-install-0.6.0 $ ./bootstrap.sh $ cabal
2011 Oct 07
0
HOgg 0.4.1.1 released
HOgg 0.4.1.1 Released --------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the fifth public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly
2008 Dec 23
1
HOgg Release 0.4.1
Conrad Parker wrote: > Here's some instructions for installing hogg on a current Ubuntu 8.10 > (or Debian unstable? testing?) system, ie. if you don't already have > haskell's cabal system installed: > > $ sudo apt-get install ghc6 > $ wget http://hackage.haskell.org/packages/archive/cabal-install/0.6.0/cabal-install-0.6.0.tar.gz > $ tar zxf
2007 Dec 07
0
HOgg 0.3.0 Released
HOgg 0.3.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the second public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on
2007 Dec 07
0
HOgg 0.3.0 Released
HOgg 0.3.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the second public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on
2008 Mar 24
0
HOgg 0.4.0 Release
HOgg 0.4.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the third public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on
2006 Dec 05
0
HOgg 0.2.0 Released
HOgg 0.2.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. http://snapper.kfish.org/~conrad/software/hogg/ This is the initial public release. The focus is on correctness of Ogg parsing and production. The capabilities of the hogg commandline tool are roughly on par with those of the oggz* tools[0],
2010 Jan 21
2
Oggs/ Speex check sum tool
Hi Is there a tool to verify and fix the checksum in a Speex file. I have seen somewhere a tool like "hoog.." Were can I get it Thanks for your time Saju -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20100120/79e209ad/attachment.htm
2007 Oct 02
1
tool to add skeleton (was Re: Re: Peer review draft for the new)
On 02/10/2007, Ian Malone <ibmalone@gmail.com> wrote: > Martin Leese wrote: > > 2. Following on from 1, a tool which inputs an > > Ogg containier with one or more streams, and > > outputs a new Ogg container with the same > > streams plus an Ogg Skeleton stream stuffed > > in front would be very helpful. The tool could > > also
2007 Oct 02
1
tool to add skeleton (was Re: Re: Peer review draft for the new)
On 02/10/2007, Ian Malone <ibmalone@gmail.com> wrote: > Martin Leese wrote: > > 2. Following on from 1, a tool which inputs an > > Ogg containier with one or more streams, and > > outputs a new Ogg container with the same > > streams plus an Ogg Skeleton stream stuffed > > in front would be very helpful. The tool could > > also
2012 Feb 15
0
[LLVMdev] LLVM GHC Backend: Tables Next To Code
On Feb 14, 2012, at 10:30 AM, David Terei wrote: > Hmm writing a blog post about TNTC is beyond the time I have right now. Sure, understandable. I'm surprised someone else hasn't already :) > Here is some high level documentation of the layout of Heap objects in GHC: > > http://hackage.haskell.org/trac/ghc/wiki/Commentary/Rts/Storage/HeapObjects#InfoTables > > With
2012 Feb 15
2
[LLVMdev] LLVM GHC Backend: Tables Next To Code
On Feb 15, 2012, at 12:16 PM, Chris Lattner <clattner at apple.com> wrote: > > On Feb 14, 2012, at 10:30 AM, David Terei wrote: > >> Hmm writing a blog post about TNTC is beyond the time I have right now. > > Sure, understandable. I'm surprised someone else hasn't already :) > >> Here is some high level documentation of the layout of Heap objects
2012 Feb 14
3
[LLVMdev] LLVM GHC Backend: Tables Next To Code
Hmm writing a blog post about TNTC is beyond the time I have right now. Here is some high level documentation of the layout of Heap objects in GHC: http://hackage.haskell.org/trac/ghc/wiki/Commentary/Rts/Storage/HeapObjects#InfoTables With TNTC enabled we generate code for closures of this form: .text .align 8 .long Main_main1_srt-(Main_main1_info)+0 .long 0 .quad 4294967299 .quad 0
2012 Feb 15
0
[LLVMdev] LLVM GHC Backend: Tables Next To Code
> This is starting to look very similar to how ARM constant islands work, without the extra ugliness from how small the ARM immediate displacements are. > > -Jim Would there be any reason that this couldn't be seen as an opportunity to move the constant islands pass out of the ARM backend and make the target-independent constant pools (which ARM bypasses completely) more generic?
2008 Feb 24
2
eos on continued page
Hi, I'm working on a new ogg file chopper (porting 'hogg chop' to C). These work pagewise, ie. they just copy the pages that are needed from the input to the output bitstream. I'm modifying the last page in the output bitstream so that it has the eos flag set. The last page is always one that has a granulepos set (that of the last packet finishing on that page). But let's say
2010 Mar 02
3
[LLVMdev] Embedding LLVM
Is there a guide anywhere to embedding LLVM into a program to compile and run a DSEL? Thanks, Sean
2009 Jun 30
2
Fixing ogg vorbis corruption caused by bad metadata
2009/6/30 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Monty Montgomery wrote, on 6/25/2009 2:16 PM: >>> Is there any way to understand exactly how it is invalid? I can replicate >>> this corruption simply by adding large album art to any ogg file with the >>> latest release of MediaMonkey. >> The second page is corrupt. ?The basic structure looks
2007 Mar 14
2
AW: packets and OGG pages
Thanks for your replys. >packets don't always begin at the >start of a page OK, since I only want to read / write the Vorbis comments, I can limit it to the Vorbis header packets. http://xiph.org/vorbis/doc/Vorbis_I_spec.html stats that the comment header always begins on the second ogg page. Since the length of the precedent identification header is fixed, this even is a fixed offset
2009 Jun 18
2
Fixing ogg vorbis corruption caused by bad metadata
I have over 1,000 ogg vorbis files that are no longer playable or editable. I believe the main cause was a MediaMonkey plugin that automatically fetched album art and added it to the header. The plugin itself just uses the generic MediaMonkey metadata facility, but something happened -- perhaps when the album art bitmap image was too large -- that caused the files to no longer work.
2012 Feb 13
3
[LLVMdev] LLVM GHC Backend: Tables Next To Code
Hello everyone, On behalf of GHC hackers, I would like to discuss the possibility of having a proper implementation of the tables-next-to-code optimisation in LLVM. Currently, the object code produced by all three GHC backends follows the convention that the table with the metadata of a closure is located immediately before the code of the closure. This makes it possible to get to both the code