NEWS: Mike Walsh has kindly created an All-In-One dotpet for weX, which includes fredx181's portable app version of ffmpeg, as well as scrox, and weav, and fredx181's gifenc-sel (for creating animated gifs either from within weX or run separately). Mike says it will run on most Pups from old 5.x series and up to latest. More details and download link available here:

New version released. Downloads for different distributions (dotpets are for 32 or 64bit Pups) below.

Aside from gtkdialog and ffmpeg (and bash), 'no' additional dependencies are required for audio-only recording or manually entered 'Fixed Area' webcam recording or screencasts (scrox required for automatic fullscreen or mouse-selectable webcam-size or screencasts) - basically, it is best to install scrox too (which requires giblib). See notes below about ffmpeg requirements for best results.

Because of new installation defaults it is advised old config directory is manually removed before installation of this new weX version (i.e. delete $HOME/.wex before installing. NOTE WELL!!! The very first time you try to run weX thereafter it will appear to not work. Just run it again - on that first run attempt it is just automatically creating its config directory $HOME/.wex
Also NOTE WELL: If you have an older ffmpeg that causes wex to fail with unrecognized option thread_queue_size then you should download the video and audio plugins from the following link, remove their dummy tar extensions, and place them in your $HOME/.wex/plugins folder: http://www.murga-linux.com/puppy/viewtopic.php?p=922081#922081 No problem then for audio recording, but for webcam or screencast recording, you might also need giblib and imlib2 (scrox needs these), also described in that link (newer Pups may already have these). To be honest... older ffmpeg are hopeless and need to buffer for ages before capturing anything. Without thread_queue_size and -filter_complex asyncts capability built into your ffmpeg I doubt you will get decent webcam captures (too much buffering required in that case for libx264 - so do yourself a favour and upgrade your ffmpeg in such cases...). Ubuntu xenial ffmpeg works great with no such issues.

Changes from previous version: Only minor (mainly fixed the tooltip documentation help text for those using pulseaudio rather than straight alsa) but also made the config file non-hidden and now uses aac, x264, with mp4 video container by default (tho I personally usually use mkv) for video/screencast recording and, by default, webcam is now NOT selected. gifenc-yad is now one of the external utility buttons by default (note that the button will only be visible if you actually also install fredx181's gifenc-yad; see download link below).

Licence is now MIT (aka liberal GPL-compatible X11 license).

Note that, weX automatically 'remembers' your selections when you choose other than the defaults anyway.

weX can be used for:

1. audio-only recording (as replacement for Precord), or

2. webcam (with or without audio) recording (as superior replacement for pAVrecord), or

3. screencast (with or without audio) recording (as superior replacement for pAVrecord and quality similar or matching SimpleScreenRecorder but without needing any Qt libs and allowing embedded optional webcam).

4. One button press to create scaled animated gif from weX recorded video/screencast assuming fredx181's gifenc-yad program is also installed.

Capturing an area of your screen (needs scrox program installed):

weX also allows a capture area to be defined using the mouse, or a single application window to be captured; for that additional functionality weX requires 'scrox' to be installed (a fork of MIT licensed scrot, which has all of scrot's functionality and options but with addition of ability to report back mouse cursor coordinates, which is what weX uses scrox for). You can find scrox in old wex thread, in link below:

Note that once you have created an animated gif in weX using gifenc-yad you can view the gif by simply changing the extension to .gif in the "File to record or process" editbox, and then press mpv assigned utility button (you can also re-assign that to mplayer if you wish).

Note that, aside from the look and feel of the GUI, pretty much all ffmpeg commandline details are user-changeable without altering main wex script. Such alterations are implemented via a simple plug-in facility incorporated into weX. weX can also call up external commands/utilities via buttons incorporated in its GUI - which utilities are available is also user-configurable.

Not been tested much on Pups. Kindly test and let me know if you find any issues.

Just thought I'd let you know how I'm getting on with WeX throughout the kennels.

So far tested (and fully working) in Slackos 560/570, Racy 5.5, and as of now, Lucid 5.2.8.7. This is using the re-packed all-in-one I put together from weav & scrox, and Fred's re-build of WeX with the newer ffmpeg.

Only issue I've noticed so far is the VU meter doesn't appear in Racy.....but that's a very minor niggle, and not that important.

EDIT:- Now also working nicely in Precise 571, ETP's 'Chromepup' (as I call it) - based on 571, and pemasu's Upup Raring

EDIT: Sorry, removed dropbox link, need to change some first in the wex script (relative paths, I forgot, back later )
EDIT2: Fixed now, changed some absolute paths to relative in weX script, required to work for portable image, re-uploaded, link above.

Thanks for that. Just wondered if you still provide separate version of that ffmpeg you compiled that maybe Mike Walsh could also also supply as dotpet so would be usable as ffmpeg system wide (with weX, scrox, weav, gifenc-sel or gifenc-yadin separate second dotpet)?

I remember you posted about the extra efficiency of that kind of alternative long time back.

Just wondered if you still provide separate version of that ffmpeg you compiled that maybe Mike Walsh could also also supply as dotpet so would be usable as ffmpeg system wide (with weX, scrox, weav, gifenc-sel or gifenc-yadin separate second dotpet)?

I take it this 'upgraded' AppImage could simply be swapped for the 0.8.17 AppImage, and everything would still work, yes?

Having now got the 'all-in-one' .pet I put together installed in at least seven Pups ( ), I don't really want to have to uninstall/re-install every single one with a new version..!

I'll probably re-pack with the new AppImage, then make the 'all-in-one' available here, or on one of the other threads (if that's OK with you two?) Where would be the best place for it?

----------------------------------------------------

I'll also see about packaging the ffmpeg build as a .pet.....although if that's done, should any advice be given to remove previous versions first (or would simply over-writing work)? I know the ffmpeg libs all need to be present and correct (as a 'matched' set) for everything to function properly, but I'm rather out of my depth with the 'mechanics' of much of this AV stuff.....I've got a feeling that simply over-writing would then interfere with existing ffmpeg stuff required by other programs that have probably been built to work with the older libs.

Is that an accurate assumption? Oh, BTW, Fred; what build is this? I can't simply label the .pet 'New ffmpeg...' And what about location; /usr/bin, since it's a compiled binary?

I take it this 'upgraded' AppImage could simply be swapped for the 0.8.17 AppImage, and everything would still work, yes?

Yes, from what I tested, but could do no harm if you test also first, before swapping with the older version.
The only change is that wiak's newest weX is included, the rest is the same (ffmpeg and btw, also scrox is included)

Quote:

I'll also see about packaging the ffmpeg build as a .pet.....although if that's done, should any advice be given to remove previous versions first (or would simply over-writing work)? I know the ffmpeg libs all need to be present and correct (as a 'matched' set) for everything to function properly, but I'm rather out of my depth with the 'mechanics' of much of this AV stuff.....I've got a feeling that simply over-writing would then interfere with existing ffmpeg stuff required by other programs that have probably been built to work with the older libs.

As promised, here's an 'all-in-one' (AIO) .pet for WeX. It includes the newest version of Wex-portable (0.8.18 - scrox now 'built-in'), weav, and the addition of GifenC-sel (for creating short .gifs with a single click).

Don't forget to check first to make sure your system has the following libs installed (most Pups seem to have them by default):-

libgiblib.so.1
libImlib2.so.1 (that's a capital 'i' before the m, not an 'L'.)

Once installed, follow Fred's instructions for enabling one of the utility 'buttons' in the main config window to start GifenC-sel:-

.....and you should find this will work in pretty much all 32-bit Pups from early 5-series onwards. I, personally, have it working from Racy5.5 & Lucid 5.2.8.7 all the way up to peebee's current Upup Bionic.

Enjoy.

EDIT:- Apparently libglib and libImlib2 are also now 'built-in', so the step about checking you have them can be skipped. (Thanks to Fred for the info - see below.)

As promised, here's an 'all-in-one' (AIO) .pet for WeX. It includes the newest version of Wex-portable (0.8.18 - scrox now 'built-in'), weav, and the addition of GifenC-sel (for creating short .gifs with a single click).

Hi Mike,

Link to your weX-portable dotpet post is added to first post of thread.

As promised, here's an 'all-in-one' (AIO) .pet for WeX. It includes the newest version of Wex-portable (0.8.18 - scrox now 'built-in'), weav, and the addition of GifenC-sel (for creating short .gifs with a single click).

Don't forget to check first to make sure your system has the following libs installed (most Pups seem to have them by default):-

libgiblib.so.1
libImlib2.so.1 (that's a capital 'i' before the m, not an 'L'.)

For info: the libgiblib and libImlib2 libs are already present in the AppImage, so not needed to install (see pic)
When you run an AppImage, you can look in /tmp/.mount_xxxxx (mountpoint) to see what's inside.

For info: the libgiblib and libImlib2 libs are already present in the AppImage, so not needed to install (see pic)
When you run an AppImage, you can look in /tmp/.mount_xxxxx (mountpoint) to see what's inside.

Ah! Excellent...

Just as an aside, did you know that the versions of those two libs have hardly changed in years? Libglib has been 1.0.6 all the way back to Racy/Lucid.....and apart from your version here, libImlib2 has been 1.4.2 for pretty well all Pups from Lucid through to Xenial; it's only the Bionics that seem to have finally begun updating them.....

I thought initially your updated wex-portable didn't have scrox.....despite what you said. It wasn't until I looked closer that I realised you'd left the 'default' settings on something else at the very moment you'd created the AppImage. I'd deleted /root/.wex, y'see, and allowed it to re-create the directory.

I'd had it on .mkvs, area selection, and audio/X11/webcam. You'd left it on .mp4s, fullscreen and audio/X11 only. So there's me wondering why I couldn't select an area....and why the webcam feed wasn't showing!

I have discovered what might be a wee 'bug'. If you close WeX with the provided 'Exit' icon, everything's fine & dandy. But if you close WeX with the window 'X', it appears to lose the settings you've selected, and reverts to the 'default' ones at the time of install.

I'd had it on .mkvs, area selection, and audio/X11/webcam. You'd left it on .mp4s, fullscreen and audio/X11 only. So there's me wondering why I couldn't select an area....and why the webcam feed wasn't showing! Laughing

Not sure, but I think that's one of the changes wiak has made for v0.8.18 , that the webcam checkbox is not checked by default (and defaults to mp4 and full-screen ?), maybe wiak can confirm ?
Well...Not very important, I guess, just mentioning.

I'd had it on .mkvs, area selection, and audio/X11/webcam. You'd left it on .mp4s, fullscreen and audio/X11 only. So there's me wondering why I couldn't select an area....and why the webcam feed wasn't showing! Laughing

Not sure, but I think that's one of the changes wiak has made for v0.8.18 , that the webcam checkbox is not checked by default (and defaults to mp4 and full-screen ?), maybe wiak can confirm ?
Well...Not very important, I guess, just mentioning.

Not sure, but I think that's one of the changes wiak has made for v0.8.18 , that the webcam checkbox is not checked by default (and defaults to mp4 and full-screen ?), maybe wiak can confirm ?

Yep, William to 'blame', but I made these changes on purpose. Reason being that if with webcam checked, weX would bomb out for those using machine that doesn't have a webcam, so I made no webcam the default.

I put mp4 since some (probably Hamoudoudou...) seemed to prefer that (claiming that some of video players didn't work with mkv). Personally I use mkv. Let's not say I don't listen to user feedback - Hamoudoudou gave feedback back then and I responded accordingly...

I must confess to using mkv more & more myself. It just seems more.....stable? (Is that even the right word here?) I used to use mp4 myself (reasoning that the standard had been around for ages, and must, therefore be 'sorted').....but in recent years quite a few new standards have appeared, some of which just seem to be far more versatile.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum