Benoit

Just a follow up (think you just dropped digging in this issue). Upgraded to wp 3.1 and the issue remains. I still have to manually upload thumbs even though ffmpeg IS present.

Many thanks Umka. You put the finger right on it. Inserted the function call in the single.php file and it works like a charm.

Now it’s only a matter of tweaking the CSS for aesthetic details to match the theme a bit better. Thanks a lot for the quick response. Much appreciated!

Hi again Praveen,

Here is what the ffmpeg command returns:

FFmpeg version SVN-r26402, Copyright (c) 2000-2011 the FFmpeg developers
  built on Mar  6 2011 14:25:27 with gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
  configuration: --prefix=/usr/local/hgffmpeg --enable-shared --enable-nonfree -         -enable-avfilter --enable-filter=movie --enable-gpl --enable-pthreads --enable-l         ibopencore-amrnb --enable-libopencore-amrwb --enable-libfaac --enable-libmp3lame          --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --extra         -cflags=-I/usr/local/hgffmpeg/include/ --extra-ldflags=-L/usr/local/hgffmpeg/lib          --enable-decoder=ac3 --enable-decoder=asv1 --enable-decoder=asv2 --enable-decod         er=flac --enable-decoder=wmv1 --enable-decoder=wmv2 --enable-decoder=wmv3 --enab         le-decoder=mpeg1video --enable-decoder=mpeg2video --enable-decoder=flv --enable-         decoder=fraps --enable-decoder=h263 --enable-decoder=h264 --enable-decoder=libgs         m --enable-decoder=mjpeg --enable-decoder=mpeg4 --enable-decoder=mpeg4aac --enab         le-decoder=mpegvideo --enable-decoder=mpeg4aac --enable-decoder=msmpeg4v1 --enab         le-decoder=msmpeg4v2 --enable-decoder=msmpeg4v3 --enable-decoder=pcm_alaw --enab         le-decoder=pcm_mulaw --enable-encoder=ac3 --enable-encoder=asv1 --enable-encoder         =asv2 --enable-encoder=flac --enable-encoder=h263 --enable-encoder=flashsv --ena         ble-encoder=flv --enable-encoder=libgsm --enable-encoder=mjpeg --enable-encoder=         msmpeg4v3 --enable-encoder=pcm_alaw --enable-encoder=pcm_mulaw --enable-encoder=         mpeg1video --enable-encoder=mpeg2video --enable-encoder=mpeg4 --enable-encoder=m         smpeg4v1 --enable-encoder=msmpeg4v2 --enable-encoder=rv10 --enable-encoder=rv20          --enable-encoder=vorbis --enable-encoder=wmav1 --enable-encoder=wmav2 --enable-e         ncoder=wmv1 --enable-encoder=wmv2 --disable-demuxer=v4l --disable-demuxer=v4l2 -         -enable-version3
  libavutil     50.36. 0 / 50.36. 0
  libavcore      0.16. 1 /  0.16. 1
  libavcodec    52.108. 0 / 52.108. 0
  libavformat   52.93. 0 / 52.93. 0
  libavdevice   52. 2. 3 / 52. 2. 3
  libavfilter    1.74. 0 /  1.74. 0
  libswscale     0.12. 0 /  0.12. 0

GD for images is supported and I use WordPress 3.0.5

OK, did just that and it returns ‘No manual entry for ffmpeg’ so what should I ask my provider for exactly?

just did a check using the ‘which ffmpeg’ in command line and it returned the path /usr/local/bin/ffmpeg, so I don’t understand why the plugin cannot find it.

Just uploaded a video and it shows the default thumb. I then tried to upload an image through the plugin, and it does not work either. I get no error message, and no image uploads. For the galleries I have up so far, I have had to upload images manually, using ftp.

I changed the path on line 451 to read $command = "/usr/local/bin/ffmpeg and in overview, it still says FFMPEG : Not Installed.

Hi Praveen,

I reinstalled a fresh download (even though I already had version 1.3 installed) and it still indicates there is no ffmpeg. I’ll try to change the core.php path and let you know if that works in a few minutes.

I had my host install ffmpeg. They tell me “it’s at /usr/local/bin/ffmpeg however /usr/bin/ffmpeg is linked to it so will work as well”. However, when I upload videos, I still do not get the thumbs and have to manually upload pictures via FTP as the edit preview image/upload image doesn’t work either. Any suggestions?

Does the gallery look for a specific path for ffmpg? I know it is installed on my server, but CVG says it isn’t.

I updated to WP 2.7-RC2 and still get an error message, which now reads: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 786432 bytes) in /specifics removed/wp-includes/functions.php on line 2901

Sorry Kevin, I was out of town and didn’t think about connecting here. The CSS above is in my theme CSS. I changed it around some and am pretty satisfied with the results I got. Even though it’s not perfect, it covers my needs, although I’ll admit it does get tedious to copy/paste the various div within each posts.

First, here’s the CSS I added to the theme stylesheet:

/* Begin Images */

div.aligncenter { width: 300px; border: none; margin: 0.3em 145px 0.3em auto; padding: 0.3em 40px 0.3em 0.3em; }

.aligncenter p { text-align: center; font-size: 0.7em; text-indent: 5px; margin-right: -45px; }

div.figureright { float: right; width: 300px; border: none; margin: 0.3em; padding: 0.3em; }

.figureright p { text-align: center; font-size: 0.7em; text-indent: 0; }

div.figureleft { float: left; width: 300px; border: none; margin: 0px 10px 0px 5px; padding: 0px 10px 0px 0px; }

.figureleft p { text-align: center; font-size: 0.7em; text-indent: 0; }

img.alignleft { float: left; margin: 0.3em; padding: 0.2em; }

img.alignright { float: right; margin: 0.3em; padding: 0.2em; }

/* End Images */

Now, that covers the following presentation styles:

– Image aligned left with caption and text-wrapping
– Image aligned right with caption and text-wrapping
– Image aligned in the center with caption and no text-wrapping

I also added two options for an image (either left or right) without caption.

I’m having a somewhat similar issue: I upload an image, process seems to work fine as checking through ftp shows the image and generated thumbnail showing up on the server.

However, using send to Editor only puts the image title in the post, and preview mode only shows the image titles, not the images themselves.

How do I go about fixing this?

Thanks David. Checked out your site and I see what you mean about the level of complexity. In the long run (i.e. after getting familiar with php, which I’m working on), a method like yours does look doable.
The two blogs running as one would obviously work, but some of the drawbacks I see are (besides the risk of discrepancies slipping in) at the pinging, referring and stats levels.
Junesix: thanks for the idea. I’ll definitely explore more what the Links Manager can handle. I agree with you that it would indeed make handling it one notch simpler than straight hard-coding.

*bump* Still nobody wanting to tackle this one?