similar to: CPU usage while encoding...

I am trying to write a sample app that uses Theora for encoding/decoding a network video stream. Unfortunately, I keep running into this error: Run-Time Check Failure #3 - The variable 'MVect' is being used without being defined. It always happens on decryption, line 467 in decode.c. The issue is that CodingMethod is equal to 5 (CODE_GOLDENFRAME), which doesn't initialize the

Hi all. I would really like to use Theora for the commercial product I work on... It's a Linux based DVR. Actually we use ffmpeg to produce MPeg4 short clips from 4 BNC channels in CIF resolution. I made a small module for our project that uses Theora... but I see that it gets a lot of CPU :( So I'm here to ask for any kind tips to reduce the CPU usage. - Hardware... do you think there

Hi all. I post a small app I made that create 2 clips using a V4L device. I would like to get every tips you think it's useful... Some notes: - I make 2 clips because in our project we create series of clips and it's important to check that the all the resources ( memory, descriptors, etc. ) are freed correctly and to reuse all the resources that can be reused - the clips are not well

Hi everybody, me again. I'm trying to write my own VFW-like dll... It doesn't need to do much. 1.) compress a single frame and give it back to the host application 2.) host applications sends the frame 3.) client application receives frame 4.) client application tells the dll to decompress the data So if I try to do this, something is going wrong... Perhaps someone could have a look at my

Hi all. I'm Mat & I'm new :) I'm testing libtheora + libogg perhaps for a commercial product. I started watching encoder_example.c ... I simplified it for testing it easier. It seems ok to me but I have no experience with theora so I would like to know if my code is correct. I tried to debug it with Valgrind and I found 4 possible memory leaks... but I think they can be

Hi! Some background: I am trying to create an application that would encode video taken by USB camera using Theora and then send it to the client. I have almost succeeded, but I have one problem. When I grab video frames from the camera and encode them they form 4KB OGG pages, then I send them over TCP/IP to the client application. Since I want to achieve as small latency as possible I

For last few days I was trying to learn ffmpeg and libtheora API. In the process, I have modified ffmpeg2theora code to include support for start time and end time. ffmpeg2theora -s 60 -e 130 file.avi will produce file.ogg which will be from 60th to 130th second of input file (something like -ss and -endpos in mencoder). This is a useful feature for someone who wants to cut a part of video

I've got my encoder working now... and i put a proeprty page interface to allow the user to set a few encoding paramters to start off with... but changing the paramters doesn't seem to make barely any difference... These are the defaults i'm using... mTheoraInfo.target_bitrate=400000; mTheoraInfo.quality=30; mTheoraInfo.dropframes_p=0; mTheoraInfo.quick_p=1;

Hi, the attached patch (against current SVN) adds three new options to ffmpeg2theora: --keyint (set keyframe interval) --smoothness (set the theora_info::sharpness encoding parameter) and --noautosync (disable the new frame dropping/duplicating code). It also fixes a bug with the processing of --cropright that sometimes segfaulted. The sync adjustment code is now tuned to be more reliable. BTW

Hi I'm evaluating Theora for a video communication system and would like some info as to what the following struct members (from the theora_info structure) do and what values one should pass to them: If there is some documentation somewhere that I've missed, please direct me to it. ===== Extract from theora.h ===== int quality; int quick_p; /* quick encode/decode */

Hi, Ralph recently checked in a version of theora/tests/noop.c that uses the new API. Part of the reason for this test is to check for memory leaks in the library's constructors and destructors. You can run the test suite under valgrind by configuring with --enable-valgrind-testing. The test passes, but gives output like: make[1]: Entering directory

Hello everyone, I'm currently developing an adaptive videoconferencing application based on Ekiga which uses TFRC as a congestion control mechanism to adapt the video encoding rate according to the quality of the network experienced. My goal was to use the open-source Theora codec for video transmission. Unfortunately, it seemed that Theora 1.0 did not properly implement any correct CBR mode.

Hi There, i want to stream some pictures out of my application using the Theora codec. I can stream to a socket or a file. The current work based on the png2theora example. Something while enconding went wrong: I can see the whole video in VLC, but the complete duration of the file will not be displayed. If i play the video in Firefox, the first 2 seconds will not be played. I think the

below is an rfc-style bitmap of the initial theora header. I've checked it against the spec and the code in libtheora; please double check :) I'm posting it here for those implementing demux stages (which necessarily don't use libtheora), and hence offering it for the spec. A typical demux stage just needs to pick out the FRN, FRD and KFGSHIFT fields, without going through the whole

Hey Folks. I'm currently working on implementing Theora Video playback for the Unity engine (http://www.unity3d.com). So far everything works fine, But I have a small question: Is there a reliable way to predict what bitrate a stream will have when encoding or decoding? Of course, there's the target_bitrate parameter in the Theora Info structure, but somehow, I always get quite

Hello, I'm not sure if this list is the proper place for this post; please correct me if it is not. I am attempting to use libtheora and I have been looking through the examples in the distribution Excerpt from encoder_example.c -- case 'V': video_r=rint(atof(optarg)*1000); if(video_r<45000 || video_r>2000000) { fprintf(stderr,"Illegal

Hi Is there a way to estimate the number of bytes per second from the information passed in the th_info-struct to the Theora encoder's th_encode_alloc()? I'm trying to be able to give users a rough estimate of the file size needed to encode with the setting provided to th_info-struct (frame width/height, fps_numerator/fps_denominator, target_bitrate and quality). -- Bjoern

Hello, I'm about to release a first version of etheora, a simplified api to programming theora video encoding/decoding applications with ogg containers. It uses and encapsulates libtheora + libogg API and structures, so users need to know very few , about video and data containers. An encoding process is made by these steps: /*a context declaration.*/ etheora_ctx *ec; /*encoder

Hello, I'm about to release a first version of etheora, a simplified api to programming theora video encoding/decoding applications with ogg containers. It uses and encapsulates libtheora + libogg API and structures, so users need to know very few , about video and data containers. An encoding process is made by these steps: /*a context declaration.*/ etheora_ctx *ec; /*encoder

I have almost finished integration of Theora into our videoconferencing program. Since a videoconferencing program is realtime, it is UDP-based and wraps the Theora stream in RTP (More on that later). The problem here is that most examples I could find, wraps the theora stream in ogg, and used over tcp or files. I send over UDP and clients need to be able to start in the middle of the stream.