- h323plus - lists.packetizer.com

H264 PLUGIN in H323Plus
by ooi khai chin 19 Mar '10

19 Mar '10

Hi All, In my latest status, I able to have the conference with polycom and other softphone using H.264 plugin. But I face the problem of delaying (my movement only show on the other endpoint after around 5 seconds in local network). I think this problem occur because of fragmentation of 1 encoded picture that has size greater than 1.4KB to multiple slices, then sent it out. Currently, my default frame rate is 10fps. My question is how to solve the delaying problem because I see polycom PVX 8.0.2 and other softphone do not have any delay? Another question, If my default frame rate is 10fps, is it means that my program will call Codec Encode function 10 times in a second? As I know, inside the encode function, every time it will check for remanding frame length for last packet, if exist it repeatably packet it with size less than 1.4KB until finish, then it only start to encode a new frame. So, Let say I have one encoded picture that consist of 10 slices, is it means that I only able to sent one complete picture in 1 second (if my fps=10)? Thanks.

5 11

Re: [h323plus] [h323implementers] How does the H323Plus handles the codecs
by Simon Horne 23 Feb '10

23 Feb '10

This should be on the h323plus mailing list. You place the plugins directory next to src and header directories in the h323plus directory and then compile them seperately. This will create seperate **_p[t-w]libplugin.so files in the /release or /debug directory which you copy to your application directory or set the PTLIBPLUGINDIR env variable to point to directory you have placed your plugins. The plugins are automatically detected and loaded when you start your application. Simon _____ From: h323implementers-bounces(a)lists.packetizer.com [mailto:h323implementers-bounces@lists.packetizer.com] On Behalf Of Thiago Martins de Sousa Sent: Wednesday, 24 February 2010 7:47 AM To: h323implementers(a)lists.packetizer.com Subject: [h323implementers] How does the H323Plus handles the codecs Hi, I'm studying the H323Plus library to start a project but I have a doubt. How does it handles with de audio and video codecs? I look the source code and thought that I have to download the plugin and put then at the /include and then compile all together or I compile the source of the plugins and then put the archives *.o at the /include folder? _____ Fique protegido enquanto navega na Internet. Instale o Internet <http://go.microsoft.com/?linkid=9707132> Explorer 8.

1 0

Re: [h323plus] RES: h323plus working plugins
by Carlos Haj 29 Jan '10

29 Jan '10

Hello, I noticed that encoder_set_options of h263-ffmpeg plugin only works while codec initialising. So if you are interested to change bandwidth or quality setting during a videocall you must modify the plugin. in encoder_set_options: add context->Lock(); context->CloseCodec(); /* here options changing ... */ context->OpenCodec(); context->Unlock(); Then add two function Lock and UnLock to H263_Base_EncoderContext with a mutex to ensure no encoding frames while openning or closing a codec! CriticalSection _mutex; void Lock() { _mutex.Wait(); } void Unlock() { _mutex.Signal(); } Add a mutex signal to the beginning of H263EncoderContext::~H263EncoderContext() { WaitAndSignal m(_mutex); /* function code...*/ and int H263EncoderContext::EncodeFrames(const BYTE * src, unsigned & srcLen, BYTE * dst, unsigned & dstLen, unsigned int & flags) { WaitAndSignal m(_mutex); /* function code...*/ So the parameters of ffmepg h263 become usable at least! Anyone tried with h263-1998 ? I'm still not able to make it working for h323 for same reasons I mentioned in my first post. Could be interesting to share some ideas! Greetings, Carlo Subject: RES: [h323plus] h323plus working plugins Date: Fri, 22 Jan 2010 14:48:41 -0200 From: leandro.alvares(a)caixa.gov.br To: unazona(a)hotmail.com Hi Carlos, I got the same results as you.... I’m not happy with my vídeo quality (CIF) and I need to activate the H.264 or H.263 4CIF, but I’m having a lot of dificults.... Regards, Leandro Oliveira Alvares De: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] Em nome de Carlos Haj Enviada em: sexta-feira, 22 de janeiro de 2010 08:38 Para: h323plus(a)lists.packetizer.com Assunto: [h323plus] h323plus working plugins Hello Everyone, I've been experimenting Opal plugins on h323plus stack. I would like to share you my experience as it seems to me that most opal plugins doesn't work for h323plus. I compiled plugins along with correct ffmpeg and x264 revisions, on both windows and linux platforms. Here is my test results: H.261vic OK H.263_ffmpeg OK H.263_1998 * Crashes before packetising process, it works after I delay the packetiser function. * Video pixels are melting strikes, even while disabling all h263 annexes. MPEG4 * AVCodec crashes on encoder function H.264 * It doesn't compile at all after activating H323_H264_TEST * Complains about some missing constants, which I added * Compilation errors in structure definitions (h323 capabilities) Theora Not tested I'm unsure about the development priority and/or status of video plugins, as no document states that. Anyone tried to experiment video codecs using h323plus?! do you have same results as me?! Thanks, I appreciate. Vous cherchez l'intégrale des clips de Michael Jackson ? Bing ! Trouvez ! Subject: RES: [h323plus] h323plus working plugins Date: Fri, 22 Jan 2010 14:48:41 -0200 From: leandro.alvares(a)caixa.gov.br To: unazona(a)hotmail.com Hi Carlos, I got the same results as you.... I’m not happy with my vídeo quality (CIF) and I need to activate the H.264 or H.263 4CIF, but I’m having a lot of dificults.... Regards, Leandro Oliveira Alvares De: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] Em nome de Carlos Haj Enviada em: sexta-feira, 22 de janeiro de 2010 08:38 Para: h323plus(a)lists.packetizer.com Assunto: [h323plus] h323plus working plugins Hello Everyone, I've been experimenting Opal plugins on h323plus stack. I would like to share you my experience as it seems to me that most opal plugins doesn't work for h323plus. I compiled plugins along with correct ffmpeg and x264 revisions, on both windows and linux platforms. Here is my test results: H.261vic OK H.263_ffmpeg OK H.263_1998 * Crashes before packetising process, it works after I delay the packetiser function. * Video pixels are melting strikes, even while disabling all h263 annexes. MPEG4 * AVCodec crashes on encoder function H.264 * It doesn't compile at all after activating H323_H264_TEST * Complains about some missing constants, which I added * Compilation errors in structure definitions (h323 capabilities) Theora Not tested I'm unsure about the development priority and/or status of video plugins, as no document states that. Anyone tried to experiment video codecs using h323plus?! do you have same results as me?! Thanks, I appreciate. Vous cherchez l'intégrale des clips de Michael Jackson ? Bing ! Trouvez ! _________________________________________________________________ Découvrez Windows 7 en 7 secondes ! http://clk.atdmt.com/FRM/go/181574577/direct/01/

3 3

Re: [h323plus] Video Resolution
by Carlos Haj 22 Jan '10

22 Jan '10

Hello Simon, Thanks for your time and effort. I had the same problem using H263 plugin on both windows and linux. I found the glitch finally in h323plus code, the following function calls fine but sends absolutly nothing to the video plugin DLL h323pluginmgr.cxx::730 PBoolean SetCodecControl(...): you can verify that by tracing "encoder_set_options" in the video plugin dll!! Codec options can't be changed during a call, including framewidth, bandwidth, quality, etc... on the other hand, the call to encoder_set_options in H323PluginVideoCodec constructor works, that's why the plugin has initial default profile values. h323pluginmgr.cxx::1590 PluginCodec_ControlDefn * ctl = GetCodecControl(codec, SET_CODEC_OPTIONS_CONTROL); etc... I modified the SetCodecControl static function, here is it static PBoolean SetCodecControl(const PluginCodec_Definition * codec, void * context, const char * name, const char * parm, const char * value) { PluginCodec_ControlDefn * codecControls = GetCodecControl(codec, name); if (codecControls == NULL) return FALSE; PStringArray list; list += parm; list += value; char ** _options = list.ToCharArray(); unsigned int optionsLen = sizeof(_options); bool result = (*codecControls->control)(codec, context, SET_CODEC_OPTIONS_CONTROL, _options, &optionsLen); free(_options); return result; /* old Code .... char const * options[2] = { parm, value }; unsigned optionsLen = 2; return (*codecControls->control)(codec, context, SET_CODEC_OPTIONS_CONTROL, options, &optionsLen); */ } With that, I'm able to have a CIF-QCIF and QCIF-CIF calls!! Hope this was helpful, good luck appreciate your effort. Greetings, Carlos From: s.horne(a)packetizer.com To: unazona(a)hotmail.com Subject: RE: [h323plus] Video Resolution Date: Mon, 18 Jan 2010 22:50:42 +1000 Carlos The framesize information is passed to the encoder as part of the frame header information. The codec should adjust the frame size according to the header information passed to it. This would be a bug in the H.261 encoder. Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Carlos Haj Sent: Monday, 18 January 2010 9:19 PM To: h323plus(a)lists.packetizer.com Subject: Re: [h323plus] Video Resolution Simon, I've been working on this, I have more detailed results. First of all, my webcam VideoInputDevice has the correct qCIF size before the attachVideoReader, while tracing the read of the codec it the rawChannel and grabwidth and grabheight are correct. I traced the plugin DLL. When H323plus callback OpenVideoChannel, the videoCodec framesize is already set using H261EncoderContext::SetFrameSize(352,288); which corresponds to default frame size I suppose. The only problem.. A further call to codec.SetFrameSize sets the new framesize only in h323 capabilities, and it never reachs the plugin DLL I have traced one call to h261encodecontext::SetFrameSize. No trace for h261 setframesize while invoking the codec.setframesize. So, each call of H261 EncodeFrames(...) returns 0 on TRACE(1,"H261\tPayload of grabbed frame too small for full frame"); as assigned frameSize is different than the videoDevice. It seems that mediaFormat.SetOptionInteger never tell the pluginDLL about the frameSize option changing. Have you and idea? Regards, Carlos From: s.horne(a)packetizer.com To: unazona(a)hotmail.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Date: Sat, 16 Jan 2010 04:05:25 +1000 Carlos Maybe I should rephase my last email The old openH323 behaviour in the OpenVideoChannel allowed the user to safely set the webcam framesize to the default size of the codec because it was always fixed. So if your codec was CIF webcam was CIF. So that is why QCIF/CIF in both directions works. Now you have changed the frame size of CIF capability to QCIF in the codec it won't. Why? You must make sure in your code the framesize coming out of the VideoInputdevice when you create it is set to QCIF otherwise it will be CIF and the encoder will expect QCIF and that is why you are getting the codec encoder call returning 0 and the channel being closed down. Did I miss something? Simon From: Carlos Haj [mailto:unazona@hotmail.com] Sent: Saturday, 16 January 2010 3:24 AM To: s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Simon, I used fixed width and height to determine display and reader working, and I traced again my application. This time I went deeper into the h323plus library, I think it's a bug of h323plus, between the library and the video codec plugin. Bug Scenario: I have set AddAllCapabilities(0, P_MAX_INDEX, "*"); I only use H261 this time SetVideoFrameSize(H323Capability::cifMPI); Set the maximum Frame size and send a kind of parameter cifTag to the plugin on my OnVideoChannel I initialise if (encoder) codec.SetFrameSize(176, 144); This is the call stack by chronological order for an h323 video call using a CIF<->QCIF endpoint (trace is for endpoint that sending qcif) 1) H323PluginVideoCodec::H323PluginVideoCodec(...) it creates the encoder, and set frame size to CIF (the default plugin maximum value) 2) H323PluginVideoCodec::SetFrameSize(...) it adjusts the frame size, called from my OnVideoChannel, with qcif Value 3) H323PluginVideoCodec::Read(...) All work, my rawChannel, renderer, etc... until I reach line 1690 H323pluginmgr.cxx::1690 - THE FIRST READ call to encode video fails int retval = (codec->codecFunction)(codec, context, bufferRTP.GetPointer(), &fromLen, dst.GetPointer(), &toLen, &flags); retval = 0, which results into closing the channel as it returns false, if I change SetVideoFrameSize(H323Capability::cifMPI); into SetVideoFrameSize(H323Capability::qcifMPI); The codec function works again, but naturally with qCIF on both sides I think that once the codec parameter was tagged to use a cif or a qcif it can't change resolution during the call. so the encoding function fail for a resolution different than one setted using the SetVideoFrameSize. It's likely that the SetVideoFrameSize send an additional information to plugin code using a setcontrolcodec which are required later so the encoding function works properly. I noticed, that video resolution fail is only a local behaviour, and has nothing to do with remote endpoint. I will be debugging more, I still don't know the plugin code so much, so you might have a clearer idea than me? I think if you make a simple test you would encounter the same behaviour! Thanks From: s.horne(a)packetizer.com To: unazona(a)hotmail.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Date: Sat, 16 Jan 2010 01:37:07 +1000 Carlos You cannot know what the remote will send when you call OpenVideoChannel for the decoding side, that can only be done when you receive the first RTP packets. You need to do a level 6 trace to work out who and why the channel is being closed. I don't think it is a capability issue, usually the problem comes from either the video encoder device (webcam) or the display device. Check to see that you have set the video input device to send at the same size as your encoder. The old openH323 used to do be able to do that automatically as the frame size for the capability was known. You have to make sure the input to the encoder from the webcam is correct. Version of h323plus would be irrelevent in this case. Simon From: Carlos Haj [mailto:unazona@hotmail.com] Sent: Saturday, 16 January 2010 1:06 AM To: s.horne(a)spranto.com.au; s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Simon, Thanks for valuable information. What is happening literally in a minimised case: I derived OnVideoChannel on the Local endpoint if (encoding) { codec.SetFrameSize(352, 288); ..... } else { cout << codec.GetWidth(); cout << codec.GetHeight(); // I receive CIF (ERROR) ..... } on the Remote endpoint if (encoding) { codec.SetFrameSize(176, 144); ..... } else { cout << codec.GetWidth(); cout << codec.GetHeight(); // I receive CIF (normal) ..... } I looked into H323 trace Log, (remote endpoint which supposed to send QCIF) PLUGIN Error encoding frame from plugin H.261-CIF H245 Request CloseLogicalChannel H323RTP Transmit H.261-CIF thread ended It seems that the H.261 channel is closed prematurely. As my local endpoint received an incorrect video size I suppose that local endpoint causes remote to close the transmission channel. Could this be related to the version of the plugin or h323plus lib which I use? it's likely that the video resolution is sent before codec.SetFrameSize is invoked! Did you in practice used different video resolution under the same capability? e.g. CIF<->QCIF calls Carlos From: s.horne(a)spranto.com.au To: unazona(a)hotmail.com; s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Date: Fri, 15 Jan 2010 23:14:23 +1000 Carlos The current behaviour is correct. The old OpenH323 used to only send CIF with *-CIF{sw} capability and only QCIF with *-QCIF{sw} . This was changed with the video plugins so the capability could do up to CIF so it would also supported QCIF. This is perfectly H.245 legal. In this way only 1 capability can do both frame sizes. This is the way most manufacturers implement the capability exchange. The capability has a flag for the size it supports so the old CIF capability used to say QCIF - 0 CIF - 1. So if you wanted to do QCIF you had to use the *-QCIF{sw} capability as the QCIF flag in the *-CIF{sw} was 0. This was changed so that the *-CIF{sw} capability had the QCIF flag so it could also support QCIF. Then it was safe to remove the *-QCIF{sw} capability and only exchange using the *-CIF{sw}. Now SetVideoFrameSize() will set the global frame size limit so regardless of the direction that will be the maximum size permitted (if CIF only up to CIF capability is available). The codec.FrameSize() in the MyH323Endpoint::OpenVideoChannel() allows the implementor to set the actual frame size to send. Is there something else I missed? Simon From: Carlos Haj [mailto:unazona@hotmail.com] Sent: Friday, 15 January 2010 8:39 PM To: s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Simon, Thanks for your quick answer, just noticed that I had a bad thread name;) Well, I have the codec.SetFrameSize(w, h); in my OpenVideoChannel When adding capabilities I use AddAllCapabilities(0, P_MAX_INDEX, "*"); SetVideoFrameSize(H323Capability::cifMPI); Capabilities table shows as Set 0: 0: audio 1: H.261-CIF{sw} I receive an OpenVideoChannel for encoder, I open channel and attach video reader + colourConverter, just after that I receive a close video signal from a H245Negotation, here I join Call Stack > testApp.exe!mmDDSVideoOutputBridge::close2() Ligne 359 C++ testApp.exe!mmVideoInputDevice::~mmVideoInputDevice() Ligne 43 + 0x1b C++ testApp.exe!mmVideoInputDevice::`scalar deleting destructor'() + 0x2b C++ testApp.exe!PVideoChannel::CloseVideoReader() Ligne 203 + 0x24 C++ testApp.exe!PVideoChannel::Close() Ligne 145 C++ testApp.exe!H323Codec::CloseRawDataChannel() Ligne 488 + 0x11 C++ testApp.exe!H323VideoCodec::Close() Ligne 747 C++ testApp.exe!H323Channel::CleanUpOnTermination() Ligne 716 C++ testApp.exe!H323_RTPChannel::CleanUpOnTermination() Ligne 1160 C++ testApp.exe!H245NegLogicalChannel::Release() Ligne 1219 C++ testApp.exe!H245NegLogicalChannel::HandleCloseAck(const H245_CloseLogicalChannelAck & __formal={...}) Ligne 1086 C++ testApp.exe!H245NegLogicalChannels::HandleCloseAck(const H245_CloseLogicalChannelAck & pdu={...}) Ligne 1372 + 0xf C++ testApp.exe!H323Connection::OnH245Response(const H323ControlPDU & pdu={...}) Ligne 3293 + 0x22 C++ testApp.exe!H323Connection::HandleControlPDU(const H323ControlPDU & pdu={...}) Ligne 3189 + 0x12 C++ testApp.exe!H323Connection::HandleControlData(PPER_Stream & strm={...}) Ligne 3170 + 0x18 C++ testApp.exe!H323Connection::HandleReceivedControlPDU(bool readStatus=true, PPER_Stream & strm={...}) Ligne 3103 + 0x12 C++ testApp.exe!H323Connection::HandleControlChannel() Ligne 3085 + 0x13 C++ testApp.exe!H245TransportThread::Main() Ligne 700 C++ If I remove the "SetVideoFrameSize(H323Capability::cifMPI);", I get the following capabilities set 1: H.261-CIF{sw} H.261-QCIF{sw} H.261{sw} with exactly same strange behaviour, QCIF is not sending while CIF is being received, by the way qcif endpoint says Local Video Codec - H.261-CIF{sw} Local Resolution - 176x144 Remote Video Codec - H.261-CIF{sw} Remote Resolution - 352x288 I tried a "ReorderCapabilities(PStringArray("QCIF"));" after my addcapabilities, I ended up with both endpoints using QCIF and ignoring my SetFrameSize anyway!! Is there a glitch using H323Plus video plugins? my code works perfectly on openh323 stack. "SetVideoFrameSize(H323Capability::cifMPI);" is supposed to define a maximum video resolution?! as you said in API doc "... to set the maximum framesize allowed to the specified value " Is that usual to have H.261-CIF with a QCIF resolution? On which order codec plugins can be added to avoid such problems of negotiation? Regards From: s.horne(a)packetizer.com To: unazona(a)hotmail.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Valid sessionID in OpenLogicalChannel command Date: Fri, 15 Jan 2010 08:12:54 +1000 Carlos In your derived H323EndPoint::OpenVideoChannel(() (isEncoding) codec.SetFrameSize(w,h); Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Carlos Haj Sent: Friday, 15 January 2010 12:59 AM To: h323plus(a)lists.packetizer.com Subject: Re: [h323plus] Valid sessionID in OpenLogicalChannel command Hello Guys, I would like to have different frame sizes for two endpoints, first I tried to play around with H323Endpoint::SetVideoFrameSize, but it seems that part changes the maximum allowed size, which means that if I switch the videoFrameSize to qCIF, I wouldn't be able to receive CIF from the other endpoint. my test only received QCIF. I tried also to modify the OpalMediaFormat by using a GetWritableMediaFormat for a capability, that ended with unusual CIF format while having a QCIF resolution. On the other hand, I looked Opal examples where they use an OpalManager, but unfortuntly that seems incompatible with h323plus, while old openh323 tutorials and exampls don't have any video plugins support. How I can manage to receive and send different resolutions (frame sizes) using H323plus? I appreciate a lot your help Carlos Discute avec tes amis partout, grâce à Messenger sur ton mobile. Cliquez ici ! Avec Internet Explorer, surfez en toute discrétion sur internet Cliquez ici ! Avec Internet Explorer, surfez en toute discrétion sur internet Cliquez ici ! Discute avec tes amis partout, grâce à Messenger sur ton mobile. Cliquez ici ! _________________________________________________________________ Découvrez Windows 7 en 7 secondes ! http://clk.atdmt.com/FRM/go/181574577/direct/01/

2 3

Generating docs
by Rogerio F Cunha 19 Jan '10

19 Jan '10

Hi All, I'm trying to generate the doxygen docs on 1.21.0 (make docs), but the openh323_cfg.dxy is missing. Is there any source for this file? Thanks Rogerio.

2 1

Valid sessionID in OpenLogicalChannel command
by Igor Pavlov 18 Jan '10

18 Jan '10

Hi. I have problem when I reject OpenLogicalChannel (audio) while communicating with Tandberg T1000. In most cases Tandberg send me OpenLogicalChannel again with sessionID=0 so my application falls in assertion in file rtp.cxx line 760 : PAssert(id > 0 && id < 256, PInvalidParameter); I could not find valid value range for sessionID, but I don't like when application crashes in this case :( What can I do in this situation? Igor Pavlov

4 17

Myphone2 FPS problem
by ooi khai chin 15 Jan '10

15 Jan '10

Hi All, Currently, I found that when I start the myphone2 application (compiled from myphone2 source code), the settings->device(settings dialog box) can not change to my own driver name, it show Microsoft WDM Image Capture <Win32>. I run the myphone2 exe provided, it show me my own device is "Logitech QuickCamPro 4000". If I used my own compiled version, It only show me the 10fps during conference with the other. While if I used the myphone2 exe provided(able show device "Logitech qucikCamPro 4000"). It can achieve 25-30fps. It happen for any video codec (H.261, H.263, H.264). Anyone, What is the problem? Thanks.

3 2

Re: [h323plus] Adding H263 codec to openmcu
by Michael Bondi 12 Jan '10

12 Jan '10

Hi Jan, I tried the ffmpeg 0.4.7 patched version you sent but the following happens: voyage:~/ffmpeg# make make -C libavcodec all make[1]: Entering directory `/root/ffmpeg/libavcodec' gcc -O3 -Wall -fPIC -g -DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o msmpeg4.o msmpeg4.c msmpeg4.c: In function 'msmpeg4_pred_dc': msmpeg4.c:845: warning: pointer targets in assignment differ in signedness msmpeg4.c: At top level: msmpeg4.c:660: warning: 'ff_old_msmpeg4_dc_scale' defined but not used wmv2.c:103: warning: 'wmv2_encode_end' defined but not used wmv2.c:481: warning: 'ff_wmv2_decode_init' defined but not used msmpeg4.c: In function 'msmpeg4_decode_dc': msmpeg4.c:734: error: can't find a register in class 'BREG' while reloading 'asm' common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints bswap.h:26: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints msmpeg4.c:734: error: 'asm' operand has impossible constraints msmpeg4.c:698: error: 'asm' operand has impossible constraints msmpeg4.c:698: error: 'asm' operand has impossible constraints make[1]: *** [msmpeg4.o] Error 1 make[1]: Leaving directory `/root/ffmpeg/libavcodec' make: *** [lib] Error 2 voyage 0.6.2 apt-get install flex bison build-essential subversion cvs pkg-config Mike Jan Willamowius wrote: > Hi Michael, > > here's my patched ffmpeg source. Its really just a quick fix until the > updated codec is ready. > > Regards, > Jan > > Michael Bondi wrote: > >> Hi Jan, >> >> Any idea of when the new ffmpeg 0.5 will be able to be compiled with >> h323 support? >> >> Are you able to supply me with your patched ffmpeg 0.4.7 so I can >> continue with my current compilation with gcc 4.3, albeit an inelegant >> solution? >> >> I'd like to learn how the openmcu works with your fantastic gnugk before >> the day is over. >> >> Mike >> >> Jan Willamowius wrote: >> >>> Yes, the old ffmpeg code doesn't compile with gcc 4.x. >>> >>> Jan >>> >>> Michael Bondi wrote: >>> >>> >>>> Hi Jan, >>>> >>>> It appears that I have ver 4.3 of gcc. >>>> >>>> Could that be the reason for the ffmpeg 0.4.7 make failure? >>>> >>>> Thanks >>>> >>>> Mike >>>> >>>> >>>> Jan Willamowius wrote: >>>> >>>> >>>>> I have a patched version of ffmpeg-0.4.7, that compiles with gcc 4.4.x, >>>>> but there is work going on to let the H.323-ffmpeg plugin compile with >>>>> current versions of ffmpeg, which is a much better solution. >>>>> >>>>> Regards, >>>>> Jan >>>>> >>>>> Michael Bondi wrote: >>>>> >>>>> >>>>> >>>>>> Thanks Prasad, >>>>>> >>>>>> I try install ffmpeg 0.4.7 from >>>>>> http://www.voxgratia.org/bin/ffmpeg-0.4.7.tar.gz but I get the following: >>>>>> >>>>>> voyage:~/ffmpeg-0.4.7# make >>>>>> make -C libavcodec all >>>>>> make[1]: Entering directory `/root/ffmpeg-0.4.7/libavcodec' >>>>>> gcc -O3 -Wall -g -DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 >>>>>> -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o common.o common.c >>>>>> In file included from avcodec.h:14, >>>>>> from common.c:27: >>>>>> common.h:65: error: array type has incomplete element type >>>>>> common.h:69: error: array type has incomplete element type >>>>>> make[1]: *** [common.o] Error 1 >>>>>> make[1]: Leaving directory `/root/ffmpeg-0.4.7/libavcodec' >>>>>> make: *** [lib] Error 2 >>>>>> >>>>>> But I proceed and continue to configure and make and make install the >>>>>> a/v pugins in the ~/h323plus/plugins directory. >>>>>> >>>>>> I create a directory ~/codecs and copy both >>>>>> h263-ffmpeg_video_pwplugin.so and libavcodec.so (from the >>>>>> libavcodec-0.4.7-linux.bin.tar.gz file) into there. I rename >>>>>> libavcodec.so to avcodec >>>>>> >>>>>> I set export P_T_LIBPLUGINDIR=~/codecs (does this have to be >>>>>> P_W_LIBPLUGINDIR ?????) >>>>>> >>>>>> I run openmcu and connect with Polycom PVX, and I see the video >>>>>> window!! But the video has strange lines with pink and blue colours, >>>>>> but it is the video from the webcam! >>>>>> >>>>>> I assume it may be because I do not have the ffmpeg 0.4.7 installed >>>>>> correctly? >>>>>> >>>>>> I will have a look at installing ffmpeg 0.4.7 direct from ffmpeg site. >>>>>> >>>>>> So I am closer.... >>>>>> >>>>>> Thanks again for the help. >>>>>> >>>>>> Mike >>>>>> >>>>>> >>>>>> Prasad Mohire wrote: >>>>>> >>>>>> >>>>>> >>>>>>> HI Michael, >>>>>>> >>>>>>> I guess you have compiled PTLIB and H323plus and OpenMCU correctly. >>>>>>> H323plus doesn't need ffmpeg. ffmpeg is needed by h323plus avplugin. >>>>>>> You were able to hear audio because h323plus comes with G711 codecs. >>>>>>> You will need to build H263 plugin separately. >>>>>>> >>>>>>> h263 plugin needs ffmpeg version 0.47. To install it: >>>>>>> run ./configure --enable-shared, then make and make install in ffmpeg >>>>>>> directory. >>>>>>> >>>>>>> Once that is done, download the plugins directory from h323plus.com >>>>>>> <http://h323plus.com>. >>>>>>> untar the direcory under h323plus directory so that you will have >>>>>>> plugins directory under h323plus. >>>>>>> Goto plugins directory. >>>>>>> run ./configure >>>>>>> You should see h263 : yes in output of configure script. This means it >>>>>>> will build H.263 plugin. If it is 'no' there is something wrong with >>>>>>> prerequisites i.e. ffmpeg. make sure that libavcodec.h file is in >>>>>>> include path. >>>>>>> >>>>>>> once you see H.263: yes as output, run make and make install in >>>>>>> plugins directory. >>>>>>> create a directory to store the plugins. Set environment variable >>>>>>> PWLIBPLUGINDIR pointing to that directory. Copy >>>>>>> h323plus/plugins/video/h.263/h263-ffmpeg_video_pwplugin.so file to >>>>>>> $PWLIBPLUGINDIR. Copy libavcoded.so to $PWLIBPLUGINDIR and rename it >>>>>>> to avcodec. >>>>>>> >>>>>>> Now start openmcu, it should load with H.263 capability. >>>>>>> >>>>>>> File "C:\\traces.txt" will be created in directory from which you will >>>>>>> start openmcu. You can see what all capabilities are added while >>>>>>> openmcu is started in that file. >>>>>>> >>>>>>> >>>>>>> Thanks and Regards, >>>>>>> Prasad. >>>>>>> >>>>>>> >>>>>>> On Fri, Jan 8, 2010 at 3:32 PM, Michael Bondi >>>>>>> <mike(a)bridgeconference.co.za <mailto:mike@bridgeconference.co.za>> wrote: >>>>>>> >>>>>>> Hi all and Happy 2010! >>>>>>> >>>>>>> This may have been asked before, but I cannot help myself but to >>>>>>> ask again. >>>>>>> >>>>>>> I have compiled ptlib 2.4.5 and h323plus 1.21 and openmcu 2.2.5 on >>>>>>> a Debian 5 machine. >>>>>>> >>>>>>> I am able to connect and hear the tones and message for connecting >>>>>>> but am unable to get video on the screen. >>>>>>> >>>>>>> I have tried compiling h323plus with only the 0.4.7 ffmpeg >>>>>>> libavcodec.so placed in a directory /root/codec and compiled with >>>>>>> ./configure --enable-rfc2190avcodec=/root/ffmpeg switch, all >>>>>>> compiles fine, but still no h.263 video. Is there any more I need >>>>>>> to do here? >>>>>>> >>>>>>> Also, I am getting confused where to unpack and install the a/v >>>>>>> plugins from file >>>>>>> http://www.h323plus.org/source/download/plugins-v1_21_0.tar.gz >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> >>>>> >>> >>> > > >

3 3

Adding H263 codec to openmcu
by Michael Bondi 11 Jan '10

11 Jan '10

Hi all and Happy 2010! This may have been asked before, but I cannot help myself but to ask again. I have compiled ptlib 2.4.5 and h323plus 1.21 and openmcu 2.2.5 on a Debian 5 machine. I am able to connect and hear the tones and message for connecting but am unable to get video on the screen. I have tried compiling h323plus with only the 0.4.7 ffmpeg libavcodec.so placed in a directory /root/codec and compiled with ./configure --enable-rfc2190avcodec=/root/ffmpeg switch, all compiles fine, but still no h.263 video. Is there any more I need to do here? Also, I am getting confused where to unpack and install the a/v plugins from file http://www.h323plus.org/source/download/plugins-v1_21_0.tar.gz Thanks Mike

3 7

H264 PLUGIN in H323plus
by ooi khai chin 24 Dec '09

24 Dec '09

Hi All, In my situation, I have set my marker to 1 when it is the last partial frame, And it able to display on the remote endpoint every frame I sent. The problem is it just delay around 5s for all frame picture. Why? I already do some testing on my x264 encoder, it can encode frame with acceptable speed, So it wouldn't be encoder problem. Thanks.

2 2