Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 20 Nov 2018, 23:41
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Multimedia
wex screencast, webcam, audio recorder
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 5 [69 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Author Message
mikeslr


Joined: 16 Jun 2008
Posts: 2791
Location: 500 seconds from Sol

PostPosted: Tue 06 Nov 2018, 21:14    Post subject:  

I can confirm that installing pupradio resolved the problem. Just to be clear, I'm running Xenialpup64-7.5 with Mike Walsh's all in one Wex, obtained and having followed the instructions from here: http://murga-linux.com/puppy/viewtopic.php?p=1009203#1009203
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Tue 06 Nov 2018, 21:41    Post subject:  

Mike Walsh wrote:
I've also included the 'gifenc-sel' GIF creator Fred published, though for some mysterious reason, no matter what size settings I give this, everything comes out the size of a postage stamp..!! Question Question


Did you get that gifenc-sel issue resolved to your satisfaction Mike?
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4392
Location: King's Lynn, UK.

PostPosted: Wed 07 Nov 2018, 07:31    Post subject:  

wiak wrote:
Mike Walsh wrote:
I've also included the 'gifenc-sel' GIF creator Fred published, though for some mysterious reason, no matter what size settings I give this, everything comes out the size of a postage stamp..!! Question Question


Did you get that gifenc-sel issue resolved to your satisfaction Mike?


No, I haven't, Will. I thought it was just in the 64-bit Pups that I've been working on the last couple of days, but I've just tried it out in a couple of the 32-bit Pups. Previously, it was working fine in these.....but now even these are doing the postage stamp thing!

Which points to something I must have installed system-wide recently, across the kennels. Hmmm.....

I'm in Slacko 560 ATM. I thought perhaps it might have summat to do with my putting Fred's ffmpeg in /usr/bin for system-wide use, so I temporarily replaced it with the original version that shipped with 560 by default. No dice; gifenc-sel wouldn't even do the job. Refused point-blank. So I put Fred's version back.....

The terminal gives no clues at all; according to that, it's doing what it's supposed to do.

Will, is gifenc-sel meant to use the version of ffmpeg that's built-in with Fred's 'portable' AppImage?


Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
fredx181


Joined: 11 Dec 2013
Posts: 3544
Location: holland

PostPosted: Wed 07 Nov 2018, 13:12    Post subject:  

Mike Walsh wrote:
wiak wrote:
Mike Walsh wrote:
I've also included the 'gifenc-sel' GIF creator Fred published, though for some mysterious reason, no matter what size settings I give this, everything comes out the size of a postage stamp..!! Question Question


Did you get that gifenc-sel issue resolved to your satisfaction Mike?


No, I haven't, Will. I thought it was just in the 64-bit Pups that I've been working on the last couple of days, but I've just tried it out in a couple of the 32-bit Pups. Previously, it was working fine in these.....but now even these are doing the postage stamp thing!

Which points to something I must have installed system-wide recently, across the kennels. Hmmm.....

I'm in Slacko 560 ATM. I thought perhaps it might have summat to do with my putting Fred's ffmpeg in /usr/bin for system-wide use, so I temporarily replaced it with the original version that shipped with 560 by default. No dice; gifenc-sel wouldn't even do the job. Refused point-blank. So I put Fred's version back.....

The terminal gives no clues at all; according to that, it's doing what it's supposed to do.

Will, is gifenc-sel meant to use the version of ffmpeg that's built-in with Fred's 'portable' AppImage?


Mike. Wink


Hi Mike, I can't reproduce that the .gif becomes the size of a postage stamp.
Tested on XenialPup 32-bit (but needed to upgrade yad, version 0.12 included in XenialPup is too old).

The ffmpeg included in "wex_portable" is to workaround problems for weX itself (with older ffmpeg (or without compiled in some required options) weX will not work properly AFAIK)
William knows more about that.

The gifenc script is another thing, it should work with any newer ffmpeg version (as I said, with the ffmpeg version in XenialPup it works okay for me).

If you have further ideas how I could reproduce the problem, please tell me.

Fred

_________________
Dog Linux website
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4392
Location: King's Lynn, UK.

PostPosted: Wed 07 Nov 2018, 18:10    Post subject:  

Hi, Fred.

I wish I could, mate. I don't know what to tell you, because I don't have a clue what I may have done to cause this.

All I can say is that an 'area' video clip from weX (approx 700 px high, by maybe 250 px wide) will end up, regardless of size settings at something like 100px x 35 px. And it does this in every Pup I've tried it in - 32- or 64-bit (which is very, very odd, because until very recently it worked fine under the 32-bit Pups).

Regardless of the clip used, or the choice of size, whatever is selected for conversion ends up something like 5% of the original full size. It's like it's stuck on the 'default' smallest selectable size.....if that makes any sense.

It's weird as hell. I fail to see how this could simultaneously go wrong in over a dozen separate, individual installs of gifenc-sel.

Personally, I'm stumped, mate.


Mike. (*shrug*) Shocked Sad

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Thu 08 Nov 2018, 06:21    Post subject:  

Another issue has arisen in Bionic systems, at least in BionicPup64, which I am currently testing weX on (not the All-In-1 dotpet but using the ffmpeg already provided in BionicPup64): That inbuilt ffmpeg doesn't have the asyncts filter capability weX needs from ffmpeg (in default recording case). It appears that newer ffmpeg is no longer the new issue since:

From ffmpeg version 3.3 onwards:
https://github.com/FFmpeg/FFmpeg/blob/master/Changelog

Quote:
Removed asyncts filter (use af_aresample instead)


hmmm... I'll need to work on that since I have no idea how to replace current asyncts filter with aresample filter (don't yet know how to use that). As far as I remember, my old workaround for no asyncts filter ability in some ffmpegs was to simply drop that part of the command (but with loss of audio/video sync) - presumably aresample filter can fix that issue, but now I have to research how to do that and upgrade weX commands accordingly. What a pain. At least Fred's specially compiled ffmpeg portable (as in All-In-1 assembly) can be used for now anyway but I don't want to have to rely on that overall. The whole ffmpeg capability seems to be full of moving goalposts.

EDIT: I also notice I now have two main weX threads because for a while mcewanw could no longer log in so I started new weX thread as wiak. But that is a real pain and I'll have to fix that disorganisation. When I do manage to build a newer weX, inspired by Mike Walsh's assembly, I've decided to include weX, weav and scrox in the one package (so will have a 32bit version and a 64bit version). I'm hesitant to include your gifenc-sel in that manner, Fred, since it is your package, and you may upgrade it from time to time. Better, I feel, to just include gifenc-sel as one of the defined weX buttons since weX won't show that button anyway unless it detects gifenc-sel actually installed on system. I really want to try and get weX working in recent pups with the ffmpeg they provide though, rather than having duplicate via additional portable ffmpeg (since that is quite a big addition when duplicated on the system).
wiak

Last edited by wiak on Thu 08 Nov 2018, 06:59; edited 6 times in total
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Thu 08 Nov 2018, 06:39    Post subject:  

/root/.wex/plugins/audio_in.plug is the code I'm going to have to work on (see my previous post for why):

Code:
# The audio_in assignments given below for ffmpegFilter_Complex0 and ffmpegAudioIn0 are user-editable but you need to use correct bash and ffmpeg syntax in any such modification (e.g. no spaces on either side of the equals signs). The main reason I am including this plugin is that some older ffmpegs do not understand -filter_complex asyncts or -thread_queue_size. For such a case it is best you upgrade your ffmpeg/avconv, but if you insist on using an old one, uncomment the two commented alternatives below and comment out the current ones:

# Of course, if you get this at all wrong, weX will temporarily not function correctly, if at all, so you are advised to back up the original plugin before trying to modify this one! However, no harm will be done to the actual weX program itself if you do make an error here. If the worst comes to the worst you can simply delete the plugin since the assignments used by default within weX itself work fine with newer ffmpeg :-)


ffmpegFilter_Complex0="-filter_complex asyncts"
ffmpegAudioIn0="-thread_queue_size 512 -f $audiosystem $channels_arecord $asamplerate -i $plughw"


# The following are for old ffmpeg/avconv that don't understand options asyncts or -thread_queue_size:

# ffmpegFilter_Complex0=""
# ffmpegAudioIn0="-f $audiosystem $channels_arecord $asamplerate -i $plughw"


I'm assuming (will have to test BionicPup64 ffmpeg) that -thread_queue_size option still works.

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Thu 08 Nov 2018, 06:47    Post subject:  

Yes, weX is now working in BionicDog64, using the ffmpeg it provides by default, if I edit /root/.wex/plugins/audio_in.plug and use:

ffmpegFilter_Complex0=""
(i.e. edit audio_in.plug to uncomment this one; meaning remove the hash)

instead of:

ffmpegFilter_Complex0="-filter_complex asyncts"
(i.e. edit audio_in.plug to comment out this line)

Only further testing will reveal if audio/video will remain in sync during long recordings with that change. However, I really want to see if aresample can be used such that AV sync works for most ffmpegs (though old ffmpegs certainly don't accept -thread_queue_size option; but that at least is okay since I don't intend supporting such old ffmpegs anyway).

EDIT: Perhaps this alternative will do the job (it works at least - but I'm not sure if it is doing anything useful or not or what it does...):

ffmpegFilter_Complex0="-af aresample=async=1000"

wiak

NOTE: Refer to my previous two posts to see what this is all about...
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4392
Location: King's Lynn, UK.

PostPosted: Thu 08 Nov 2018, 08:28    Post subject:  

@ Will:-

Quote:
[quote="wiak"]Another issue has arisen in Bionic systems, at least in BionicPup64, which I am currently testing weX on (not the All-In-1 dotpet but using the ffmpeg already provided in BionicPup64): That inbuilt ffmpeg doesn't have the asyncts filter capability weX needs from ffmpeg (in default recording case). It appears that newer ffmpeg is no longer the new issue since:

From ffmpeg version 3.3 onwards:
https://github.com/FFmpeg/FFmpeg/blob/master/Changelog

Quote:
Removed asyncts filter (use af_aresample instead)


Mm-hm. That's the exact item that threw me out when I was trying out the 'all-in-one' I put together for the 64-bit Pups. So; if I have this correct, the 'fix' is to comment out

Code:
ffmpegFilter_Complex0="-filter_complex asyncts"


...and un-comment

Code:
ffmpegFilter_Complex0=""


.....in the audio.in plugin, yes?

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

BTW:- You're probably right about Fred's gifenc-sel; it should be left as a separate package. I think I'll re-build my 'all-in-one' to omit it for now, and concentrate that just on WeX, Weav & scrox. Gif conversion is, after all, not a necessary part of what you want to achieve here, TBH. It's 'icing on the cake'.....and not everybody wants, or even likes icing..!


Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Thu 08 Nov 2018, 17:07    Post subject:  

Mike Walsh wrote:
So; if I have this correct, the 'fix' is to comment out

Code:
ffmpegFilter_Complex0="-filter_complex asyncts"


...and un-comment

Code:
ffmpegFilter_Complex0=""


.....in the audio_in plugin, yes?


Yes, that is correct Mike. However, I'm also experimenting with alternative to using ffmpegFilter_Complex0="":

Code:
ffmpegFilter_Complex0="-af aresample=async=1000"


in case that second one (or similar) results in better audio and video syncing (no difference that I see on my own laptop so far though).

There is a possible issue though... some older systems do work better with the asyncts line as it is... So if I find an alternative that works for all cases (holy grail...) then I'll later make new version of weX with any change code incorporated in main script. For now, leaving things as they are works best for many systems (when using that Fred compiled ffmpeg since that ffmpeg recognises asyncts filter anyway).

As for gifenc-sel: I think it is a very worthwhile extra but better as a separate dotpet since being developed separately by Fred (so hard to maintain if put in All-In-One package) - but definitely recommended to be installed since I really like weX having that utility available.

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Thu 08 Nov 2018, 17:28    Post subject:  

I don't have any audio/video sync issues to test (all recordings on my machine are coming out in sync) so that's problem trying to decide on 'best' filter option. For the moment however, I'm tending to favour using:

Code:
ffmpegFilter_Complex0="-af aresample=async=1000"


since that 'might' help some systems and doesn't seem to cause any problems otherwise. I'm on BionicPup64 at the moment (using its inbuilt ffmpeg); I'll switch to XenialDog64 in a moment to see how that audio_in.plug alteration effects things with XenialDog64's inbuilt ffmpeg. Don't want to test earlier than that really since don't have the isos or space on my system currently.

My aim would be to not need Fred's special portable ffmpeg (which I don't use on XenialDog anyway, since not required there at least). However... for older Puppy systems you are best to use Fred's special portable ffmpeg since some of these very old ffmpegs used in old Pups do not allow the essential ffmpeg option -thread_queue_size (or asyncts for that matter) so for a 'universal' package including portable ffmpeg is best option (but increases package size a lot and need both 32bit and 64bit version of the portable ffmpeg - i.e. two alternative All-In-One packages. However most older pups are 32bits anyway, so maybe just one 32bit All-In-One would indeed be enough in practice).

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Thu 08 Nov 2018, 23:07    Post subject:  

After some further tests, I think it is fine to just use:

ffmpegFilter_Complex0=""

for 64bit systems (seems to work okay for Xenial and Bionic at least; I'm not supporting 64bit Tahr so not testing that).

for older Pups, which tend to be 32bits, I think it is best to use All-In-One by Mike Walsh that includes Fred's special compiled static ffmpeg.

I don't think I'll modify weX itself at present though. Just a note to make the above edit to /root/.wex/plugins/audio_in.plug if using Bionic and above anyway (no need to change anything at all for Xenial as far as I see).

For Puppy users the best situation would be if new Pup builders would build weX in and then they can check if modified /root/.wex/plugins/audio_in.plug gives optimum results (wex is just a tiny script afterall and scrox is small - the ffmpeg in modern pups is fine so no extra ffmpeg required on new builds. Furthermore scrox contains all traditional scrot functionality so scrot being a symlink to scrox works fine for taking screenshots scrot-fashion). I have no control over that so it's up to Puppy users to ask the builders if they want weX configured out of the box. Fred tends to configure weX appropriately (at least in XenialDog; I don't have BionicDog installed at the moment, so don't know if weX is on that - good if it is. Did try BionicDog earlier, but can't remember).

I'll think more about this matter later if I decide to produce a 0.8.18 version of weX.

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Fri 09 Nov 2018, 00:09    Post subject:  

Just installed BionicDog64. weX is pre-installed. However, wasn't working because of same Bionic ffmpeg issue above. Simple fix, Fred, is to edit the config file (really should be the one in /etc; i.e. /etc/wex/plugins/audio_in.plug) and, as explained above posts, use:

Code:
ffmpegFilter_Complex0=""

i.e. uncomment above line in audio_in.plug

instead of:

ffmpegFilter_Complex0="-filter_complex asyncts" (i.e. comment that line out)

When weX is run for the first time it copies /etc/wex folder to ~/.wex automagically, so all should be fine if ~/.wex is removed before first run.

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1000
Location: not Bulgaria

PostPosted: Fri 09 Nov 2018, 03:18    Post subject: Coming soon  

Coming soon

Refer to my above post for recent related info. Tonight I'm busy re-organizing weX package (version for 32bit and another for 64bit system). For simplicity of installation (and maintenance from my point of view) it will now contain scrox and weav in the package. It will NOT itself however contain any version of ffmpeg or any program developed by someone else, such as gifenc-sel (however, the ~/wex/user_utility config script will by default list gifenc-sel as one of the utilities weX will try to include as a button action.

EDIT: Oh, and 'possibly' precord will become included as part of weX package since they share a great deal of common code and precord offers more efficient arecord-based audio recording (though lame, installed by default on most all? Pup/Dog systems, is a dependency). I tend to develop precord weX at same time since helps me keep them in step in terms of user interface improvements. EDIT2: Tonight mainly been revamping Precord (to version 9.0.6) to give it audio-related post processing user-editable utility buttons (like in weX) - also using some weX code in Pecord to make config file handling a bit more robust. Otherwise much the same user-interface as previous Precord. Also now uses defaultfilemanager, or pcmanfm, if available, or checks what's otherwise available, such as rox, for filemanager view of save dir.

In the wex/weav/scrox re-organisation process, I will update main weX program itself to version 0.8.19 to address some of the recent issues. In particular, I will probably provide an optional extra plugins package (deb and dotpet), which will be distribution dependent to address the various ffmpeg variations these use. The new 32bit version of the weX package should be conveniently able to be used by Mike Walsh for assembly of his All-In-One package (which will include portable ffmpeg, which is known to work well on older 32bit Pups too).

Finally, once the new wex version 0.8.19 packages are complete I will be reorganising the wex/weav/scrox threads to one main thread (it got out of control...) and later working-on/polishing my github site containing these projects.

The above are my current plans anyway... Wink
Thought I'd better list them since they affect Mike's All-In-One assembly.

wiak
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4392
Location: King's Lynn, UK.

PostPosted: Fri 09 Nov 2018, 07:42    Post subject:  

@ William:-

Just to let you know, those audio plugin modifications are working nicely in Bionicpup64.

The whole idea of putting the 32-bit 'all-in-one' package together, initially, was for my own benefit! I run around 14 Pups in total.....mostly 32-bitzers. I just wanted to make installation easier across the kennels; rather than installing 3 or 4 packages in each one (or multiple sym-links to each one from a remote partition), I wanted a simple process of click-to-install, click to use. Of course, it then occurred to me that by doing so, I'd inadvertently created a package which would quite possibly be of interest to many other Puppians.....newbies in particular.

So, I published it.

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

It does work well across a whole range of Puppies, certainly as far back as early 5-series Pups.....rerwin's Lucid 5.2.8.7 & BK's T2-based Racy 5.5 being my oldest ones. The only thing with these is that they need a bit more experimentation to get the mixer settings correct, since the sliders don't have the 'logarithmic' unit-on-unit increase - only the 'linear' one - and need to be set rather higher to achieve the desired result. Again, this is going to vary from not only Puppy to Puppy, but also machine to machine in any case. As the saying goes, YMMV.

(I never thought I'd hear myself saying this, but in this particular instance a totally 'home-brewed' solution has proven to be so much more effective than any number of 'commercially available' ones. Again; thank you so much!)

I'll keep an eye on developments, and will re-build/re-pack the 32-bit 'all-in-one' when you release WeX 0.8.19. BTW, are you intending to consolidate things by re-doing an old thread, or arrange things with Flash so that you start a new thread, including relevant stuff from those older threads, followed by removing the latter? Just curious, so I'll know what to look out for.....


Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 3 of 5 [69 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Multimedia
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1236s ][ Queries: 13 (0.0202s) ][ GZIP on ]