(old)Puppy Linux Discussion Forum

I used previously viDrop converter.
I could burn text subtitle files into video with viDrop.
How to burning subtitle into a video with FFConvert?

gojko wrote:How to burning subtitle into a video with FFConvert?

I have not tried yet but maybe you can put additional options with the text filename in the 'Advanced options' at the video setting.
See the ffmpeg online document on the additional options.

Thanks! I will try.

Update: ffconvert-1.2.2.pet
http://shino.pos.to/linux/puppy/
# v1.2.2 - 30 Apr 2012: fix was failed 2-pass converting, fix was not allowed spaces in the destination path, again codec list under some locale(tnx to Karl Godt)

EDIT: Sorry but ffconvert-1.2.2.pet was uploaded again at 2012-05-02 with same filename. Please check the time stamp or the file /usr/bin/ffmpeg.

# v1.2.2 - 2 Mar 2012: fix was odd essage under some non UTF-8 loacle
VERSION="1.2.2"
CREDIT="FFConvert v.$VERSION"
TITLE=$CREDIT
MYNAME=$(basename $0)
export TEXTDOMAIN=ffconvert #$MYNAME
export OUTPUT_CHARSET=UTF-8 # v1.2.2 - 2 Mar 2012

Sorry but ffconvert-1.2.2.pet was uploaded again at 2012-05-02 with same filename. Please check the time stamp or the file /usr/bin/ffmpeg.
See the post above.

Karl Godt wrote:...
*
Installing some /usr/share/locale/*/LC_MESSAGES/glibc.mo i compiled with --prefix=/opt/glibc-2.6.1 by simply copying them there solved the 3 warnings i got by locale command :

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

Took me several weeks to figure that out that this meant the glibc.mo and not a /usr/lib/locale/default link to a directory ...

*
I hope i have not fogotten anything .

This has brought me to the idea of adding libc.mo to next langpack_de
Thank you, Karl.

Karl Godt wrote:Installing some /usr/share/locale/*/LC_MESSAGES/glibc.mo i compiled with --prefix=/opt/glibc-2.6.1 by simply copying them there solved the 3 warnings i got by locale command :

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

I guess those error messages are caused by lacking /usr/lib/locale/${LANG} contents or illegal LANG value, never mean the glibc.mo.

New test release: ffconvert-1.2.9.pet (2012-05-26)
http://shino.pos.to/linux/puppy/

New features:
1. Additional audio track. You can combine the 1st file for video and the 2nd for audio.
2. Screen capture. Note this feature is available on the Lupu and Slacko. Wary/Racy cannot.



Video using the screen capture:
http://www.youtube.com/watch?v=_8hcLmfxv8Y

Hi shinobar; I didn`t read the whole forum thread as it`s quite long.

Does ffconvert do ffmpeg x264 with the quality setting and single pass?
This is the best all around method, fast one pass and easy to set quality.
I`ve been using Handbrake, but it`s far more complex than is needed.

I tried the old ffconvert and it didn`t work, but I hope the new one does.

sunburnt wrote:I tried the old ffconvert and it didn`t work, but I hope the new one does.

Depends on the ffmpeg and the Puppy version.
What Puppy are you using?

It was maybe a year ago I tried ffconvert, not really that important.

Now I use Puppy-528-005 Lucid with Handbrake.
But Handbrake is more complex than is needed.
###
Just need audio stream selection, video and audio output format, and a few other options.
Perhaps this is in some of the preset files that ffconvert can use?
###
Q: Does ffconvert do x264 "quality based" encoding?

OR, are you planning on adding that to it?

sunburnt wrote:Now I use Puppy-528-005 Lucid

I recommend Pmusic Upgrade 005 and ffconverter 1.2.9.

Thanks shinobar;

I`ll get those packages and try it out.

Crrent: ffconvert-1.3.pet (2012-06-17)
http://shino.pos.to/linux/puppy/
You need not upgrade if you are content with the v.1.2.9.

# v1.2.9 - 26 May 2012: x11grab, mkplaylist, notebook, preset group
# v1.3 - 17 Jun 2012: upport avconv, fix unsupported codec error message, gtkdialog to avoid yaf-splash incompatibility, vcd for the default

Try '-isync' as the advanced options if you encounter no sync with the video and audio when grabing X by the ffconvert 2.9.1 and later.
(Thanks to smokey01)

FFConvert-1.3 supports screen capture. But you need to upgrade ffmpeg for Wary/Racy-5.3 or Puppy-4.x.
For Wary/Racy-5.3, install FFmpeg-0.8.12 to enable screen capture.
For Puppy-4.x, install ffmpeg-0.7.6.

You need not upgrade ffmpeg for slacko, dpup and most of Pupplet-5.x.
For the lucid puppy, the Pmusic Upgrade 005 is recommended.

TIPS:
ffconvert-1.3 has additional options in /usr/bin/ffconvert at line 80:
CAPTURE_SOUND="hw:0,0"

It specifies the sound device associates the screen capture.
"hw:0,0" means card 0, device 0.

You can edit the value by a text editor.
To see the available hardware, type the command 'arecord -l': The mixer setting can be tested by the recording feature of the mhWaveEdit.

"hw:0,1" is the line-in port for my desktop computer when recording audio.

Audacity's preferences is a good way to understand what
your audio ports are named by system


_

shinobar wrote:TIPS:
ffconvert-1.3 has additional options in /usr/bin/ffconvert at line 80:
CAPTURE_SOUND="hw:0,0"

It specifies the sound device associates the screen capture.
"hw:0,0" means card 0, device 0.

You can edit the value by a text editor.
The mixer setting can be tested by the recording feature of the mhWaveEdit.

Thanks for this Shinobar. I think I know what to do now (to get my USB headset working!)
mark

Hi shinobar,

I'm using the latest FFconvert on Akita... I get errors when trying to screen capture, with the ALSA option hw:0,0
To fix this, I must change the option to plughw:0,0

Can this be auto detected and done for users by ffconvert?

Also, I get errors about a missing -r option ... Each time this happens the -r 29.97 option has many spaces before it (not only 1), and it is separated from the -f 1024x768 option...

I can fix the errors about the missing -r option, if I move the -r option immediately after -f 1024x768 , and remove all double/triple spaces from the ffmpeg command....

Example:

From FFconvert (doesn't work): the above gives: Edited, moved -r option and extra spaces (still doesn't work): the above gives Edited again, using plughw (works): I hope you can fix these issues, so that I don't need to manually edit the command in a text editor, then paste back in to a terminal...