similar to: svn repository reorg

Displaying 20 results from an estimated 50000 matches similar to: "svn repository reorg"

2009 Jan 07
6
online service to host/share theora&vorbis encoded ogg files
hi, i am looking for a free hosting / file transfer service to share theora and vorbis encoded ogg videos. i have been making a series of contemporary art projects titled "a copyleft crowdsourcing free/open source project" with art students in gropus of 50-120. as a part of the project we want to share the video and audio content created for the project as copyleft and free/open
2010 Sep 23
2
Ptalarbvorm is now in trunk
We're about ready to do a 1.2 alpha release from the ptalarbvorm tree, and as such it's no longer experimental. I've replaced the theora svn trunk with a copy of derf's experimental tree; please do subsequent development toward the release there. The old 1.1.x trunk is available as http://svn.xiph.org/branches/theora-1.1 if you need it. -r
2004 Sep 15
1
building from svn
After downloading libogg-1.1.tar.gz, libvorbis-1.0.1.tar.gz, and libtheora-1.0alpha3.tar.gz; building and installing them in that order, and trying the alpha3 theora encoder, I decided to try to build theora from svn. Using svn to checkout theoratrunk worked ok. The first time I tried to execute ./autogen.sh, it complained that I didn't have automake. Mandrake 10.0 comes with automake
2010 Mar 21
1
Who's developing mwEmbed?
Recently I found out about mwEmbed[1] which seems to me to be a great tool to embed theora videos with a fallback mechanism in place and a really smooth user experience. Since I am testing the tool for use in my blog and other websites at the moment I would like to know who is actually developing that tool and where to report bugs. (e.g. it doesn't work yet in Opera 10.50 which is a
2004 Sep 12
3
libogg 1.1.1 release
Everyone, Pleased to announce the release of libogg version 1.1.1. This is a bugfix release on last year's 1.1 release. Source archives are available from our new download site: http://downloads.xiph.org/releases/ogg/libogg-1.1.1.tar.gz http://downloads.xiph.org/releases/ogg/libogg-1.1.1.zip Maintained from the /releases subtree on svn.xiph.org. This release is tagged in the
2004 Sep 12
3
libogg 1.1.1 release
Everyone, Pleased to announce the release of libogg version 1.1.1. This is a bugfix release on last year's 1.1 release. Source archives are available from our new download site: http://downloads.xiph.org/releases/ogg/libogg-1.1.1.tar.gz http://downloads.xiph.org/releases/ogg/libogg-1.1.1.zip Maintained from the /releases subtree on svn.xiph.org. This release is tagged in the
2006 Feb 01
2
Need clarification for Rails Engines SVN repository
Hi all ! Could someone tell me what''s what in the Rails Engines Subversion repository ? There are many folders where the Rails Engine is located, and from the folder names alone, I can''t really guess what''s what. For example, the rails engine plugin is situated at: plugins/engine engines/trunk branches/engines branches/edge_engines From the log, I gather
2009 Aug 05
2
libtheora 1.1beta1 release
All, After months of intensive development, we're finally coming to a stopping point in our rewrite of the libtheora reference implementation. All major features for the 1.1 are in, so it's down to bug fixing now. Please try this first beta and give us feedback. Most notable is that the encoder's rate control is much more configurable, and more capable in each configuration than
2009 Aug 05
2
libtheora 1.1beta1 release
All, After months of intensive development, we're finally coming to a stopping point in our rewrite of the libtheora reference implementation. All major features for the 1.1 are in, so it's down to bug fixing now. Please try this first beta and give us feedback. Most notable is that the encoder's rate control is much more configurable, and more capable in each configuration than
2008 Nov 03
2
Theora 1.0 final release
Theora is a video codec with a small CPU footprint that offers easy portability and requires no patent royalties. While the Theora bitstream format was standardized in 2004 and our beta releases have been used by millions, this 1.0 release is an important milestone reflecting the maturity and stability of the Theora codebase. A number of leading multimedia web groups already support Theora.
2008 Nov 03
2
Theora 1.0 final release
Theora is a video codec with a small CPU footprint that offers easy portability and requires no patent royalties. While the Theora bitstream format was standardized in 2004 and our beta releases have been used by millions, this 1.0 release is an important milestone reflecting the maturity and stability of the Theora codebase. A number of leading multimedia web groups already support Theora.
2009 Jul 31
1
theora and videopress
Hi all, In order that theora is the default, there is need for more and more tools and sites to support it. In that area I came across videopress in my web wanderings. http://videopress.com/ which is supposed to be a 'complete video solution' for putting on the web. I also saw that videopress has a plugin http://wordpress.org/extend/plugins/video/ The fact that the plugin
2009 Mar 09
1
how to write svn for dahdi-linux and dahdi-tools when using svn 1.4
Hi, When we use svn branches-1.4 such as: # svn checkout http://svn.digium.com/svn/asterisk/branches/1.4 asterisk-1.4 # svn checkout http://svn.digium.com/svn/libpri/branches/1.4 libpri-1.4 how to write the others such as dahdi-linux and dahdi-tools? Regards, Zen
2003 Mar 18
6
bitstream changes
ok now I see why we need another packet in the header. The first one is basically for ID purposes (theora_decode_header()). I've jammed my huffman trees in there but it sucks because I need them later on when I actually build the huffman tree structs (theora_decode_init, calls InitHuffmanSet()). At that point the original header packet is gone so I've been keeping it around in a buffer.
2010 Mar 28
2
[LLVMdev] [repository] Make LLVM repository Git-clonable
On Mar 28, 2010, at 10:35 AM, Jon wrote: >> A good solution, surely, would be to anoint a single official >> Git/Mercurial mirror, and announce it in the same page as the SVN >> checkout instructions? > > MRI Ruby interpreter development did that and it seems to working fine. Of interest is their handling of branches and tags as discussed by Vladimir and Eric in this
2004 Dec 01
2
streaming versus editing
On Thu, 25 Nov 2004 10:25:43 -0800, Ralph Giles <giles@xiph.org> wrote: > I think it would be better to say which formats are technically > superiour for streaming (ogg and mpeg program streams) or > editing (quicktime/matroska) or dead/obsolete (AVI, MCF?), If video is recorded and saved in ogg/theora container/format, could it be converted into matroska/theora container/format
2007 Jun 30
1
[LLVMdev] Repository Layout
Hello, Reid. > Fortunately, with SVN, making such a change isn't hard and its tracked > in the commits. Anyone object or have other ideas in this realm? I'm also confused. At one hand, proposed layout (with BTT in the top) seems to be "unnatural", when we will create new tags/branches. In theory, each module can have its own version, thus if the want to "tag"
2012 Oct 23
4
building libtheora 1.0 on win64
I have an old conferencing app that uses theora and I'm building it for win64. libthora 1.1 builds just fine, but libtheora 1.0 has errors related to assembly code when building for x64. I've tried using 1.1, but the video does not look right -- the clients all generate their own first 3 packets instead of sending them over the network since they assume they are all on the same version
2010 Mar 31
0
[LLVMdev] [repository] Make LLVM repository Git-clonable
On 03/28/2010 09:54 PM, Chris Lattner wrote: > On Mar 28, 2010, at 10:35 AM, Jon wrote: > >>> A good solution, surely, would be to anoint a single official >>> Git/Mercurial mirror, and announce it in the same page as the SVN >>> checkout instructions? >> MRI Ruby interpreter development did that and it seems to working fine. Of interest is their handling
2003 Jun 08
5
bitstream versioning
as per yesterday's discussion at #theora -- It has been suggested that we devise a method such that we will be able to add certain features to the bitstream (interlace, exotic color subsampling, clip length flag for download, etc), in such a way as to not obsolete streams encoded previously. Rillian's suggestion, which is pretty much standard practice, is to add a bitstream revision