| Comment by: Maijestro (79.198.28.20) | At: 14 Mar 2024, 21:15 | File version: 6.1.1 |
Thanks you MickJT ;-)
|
| |
| |
| Comment by: Daveyw (60.234.236.153) | At: 12 Feb 2024, 21:08 | File version: 6.1 |
Thanks Mick. Yep, I later figured out why x=10 kept appearing on the output. :-)
|
| |
| |
| Comment by: MickJT (115.69.35.90) | At: 12 Feb 2024, 12:41 | File version: 6.1 |
You're missing a colon before x=10, but also somehow the drawtext filter got disabled, or didn't get enabled, when compiling. So keep using 4.2.1 for now until I can update this.
|
| |
| |
| Comment by: DaveyW (60.234.236.153) | At: 12 Feb 2024, 03:37 | File version: 6.1 |
Hmmm... the Drawtext filter isn't working with this new build, it was working in 4.2.1.
This line works in 4.2.1:
ffmpeg -i Temp:Test.mp4 -ss 00:01:30 -vframes 1 -vf "drawtext=text='%{pts*:hms}'x=10:y=10:fontsize=24:fontcolor=white" ram:test.png
[backslash between * and ]
but with this build I get:
"[AVFilterGraph @ 0x448bfcc0] No option name near 'hms}x=10:y=10:fontsize=24:fontcolor=white'
[AVFilterGraph @ 0x448bfcc0] Error parsing a filter description around:
[AVFilterGraph @ 0x448bfcc0] Error parsing filterchain 'drawtext=text='%{pts:hms}'x=10:y=10:fontsize=24:fontcolor=white' around:
[vost#0:0/png @ 0x43d2f690] Error initializing a simple filtergraph
Error opening output file ram:test.png.
Error opening output files: Error number -22 occurred"
|
| |
| |
| Comment by: HKvalhe (89.10.145.67) | At: 10 Dec 2023, 20:38 | File version: 6.1 |
Thanks for the update! Works very well on my X5000!
|
| |
| |
| Comment by: Me (91.64.151.111) | At: 10 Dec 2023, 20:13 | File version: 6.1 |
Thank you!!!
|
| |
| |
| Comment by: DaveyW (60.234.236.153) | At: 01 Mar 2023, 21:49 | File version: 4.2.1 |
Thanks Mick, that does indeed work.
|
| |
| |
| Comment by: MickJT (115.69.35.90) | At: 01 Mar 2023, 14:26 | File version: 4.2.1 |
The previous comment doesn't show it, back there is supposed to be a backslash before each colon. The asterisks are also required. So for each colon, add an asterisk and backslash before it. The asterisk is the escape character for Amiga Shell. I also tried running it within bourne shell but didn't have any luck.
|
| |
| |
| Comment by: MickJT (115.69.35.90) | At: 01 Mar 2023, 14:22 | File version: 4.2.1 |
Finally figured it out. Some characters had to be escaped in a certain way. This works.
ffmpeg -i sample_640x360.avi -vf "drawtext=timecode='00*:00*:00*:00':fontfile=/Fonts/_TrueType/Comic.TTF:fontsize=30:r=25" test.avi
|
| |
| |
| Comment by: DaveyW (103.226.65.51) | At: 28 Feb 2023, 21:04 | File version: 4.2.1 |
@ktadd
It's not supposed to, the text is the timecode.
https://onelinerhub.com/ffmpeg/how-to-add-timecode-text-to-video-using-drawtext-filter
|
| |
| |
| Comment by: ktadd (192.25.50.127) | At: 27 Feb 2023, 23:35 | File version: 4.2.1 |
@DaveyW
I don't see any text="mytext" after the fontsize=30.
|
| |
| |
| Comment by: DaveyW (60.234.236.153) | At: 23 Feb 2023, 22:54 | File version: 4.2.1 |
Thanks Mick. Yes, got that working. I'm trying with timecode, but I get the error that I reported.
From what I've read online, this should work:
ffmpeg -i Misc:Downloads/Red.Dwarf.S11E01.mp4 -vf "drawtext=timecode='00:00:00:00':fontfile=/Fonts/_TrueType/Comic.TTF:fontsize=30" ram:test.avi
|
| |
| |
| Comment by: MickJT (115.69.35.90) | At: 15 Feb 2023, 07:07 | File version: 4.2.1 |
I did a test with
ffmpeg -i sample_640x360.avi -vf "drawtext=fontfile=/Fonts/_TrueType/Comic.TTF:fontsize=30:text=test 123" test.avi
That worked
|
| |
| |
| Comment by: DaveyW (60.234.236.153) | At: 27 Jan 2023, 00:04 | File version: 4.2.1 |
Hi Mick,
Does -vf drawtext work with this version of ffmpeg? I have been playing around with it but I get an error "Error reinitializing filters! Failed to inject frame into filter network: Error number -22 occurred"
|
| |
| |
| Comment by: MickJT (115.69.35.90) | At: 25 Jul 2021, 16:22 | File version: 4.2.1 |
Damn. The Altivec version has to be compiled with a linker script (files in ldscripts/) from an older binutils, or with the -N switch when linking, in order to stop that issue from happening. I don't have an altivec capable machine myself to test, but usually get someone to check it for me before releasing. I can't remember if I did that this time. Thanks for letting me know. I can't give a timeframe for an update yet.
|
| |
| |
| Comment by: Petrol (92.184.117.218) | At: 24 Jul 2021, 09:29 | File version: 4.2.1 |
Hi, with this new version, I’ve got problem converting h264 videos with the AltiVec version on my A1X1000. The converted video has green artifacts. I’ve also tried an older version, and the converted video was ok. No problem with the generic’s one. Converting avi to h264 works also. It seems to be a decoding issue with x264 video file. Regards,
|
| |
| |
| Comment by: walkero (212.2.173.66) | At: 06 Jan 2020, 12:55 | File version: 4.2.1 |
Thank you the new version. You are awesome
|
| |
| |
| Comment by: MickJT (118.211.111.216) | At: 27 Nov 2017, 07:37 | File version: 3.4 |
Correction to the readme. The solution for altivec binaries wasn't linker libs from 4.2.4, but using binutils 2.18 which has different internal linker scripts.
|
| |
| |
| Comment by: ghh (89.177.235.56) | At: 30 Jul 2016, 21:17 | File version: 3.1.1 |
Concat works (filter and protocol). Thank you!
|
| |
| |
| Comment by: MickJT (118.211.73.30) | At: 11 Jul 2016, 18:38 | File version: 3.0.2 |
It's an issue with a patch for is_dos_path. It'll be fixed in the next upload.
|
| |
| |
| Comment by: MickJT (118.211.73.30) | At: 11 Jul 2016, 18:10 | File version: 3.0.2 |
This is a different issue unrelated to the use (or non-use) of -safe 0. I'll look into it.
|
| |
| |
| Comment by: Jurassicc (31.50.64.210) | At: 10 Jul 2016, 17:06 | File version: 3.0.2 |
Many Thanks for the Tip
thumbsup:
|
| |
| |
| Comment by: k (73.252.224.45) | At: 10 Jul 2016, 02:46 | File version: 3.0.2 |
Put -safe 0 before the -i command and it will work again.
|
| |
| |
| Comment by: Jurassicc (31.50.64.210) | At: 09 Jul 2016, 22:56 | File version: 3.0.2 |
concat nolonger works
eg:-
ffmpeg -i "concat:VTS_01_1.VOB|VTS_01_2.VOB|VTS_01_3.VOB"
ask for volume concat:
|
| |
| |
| Comment by: MickJT (124.169.231.119) | At: 17 Apr 2016, 09:35 | File version: 2.8.5 |
I don't know if that's possible. As far as I know, OS4.x itself is 32bit.
|
| |
| |
| Comment by: J. Aarbakk (85.165.230.223) | At: 16 Apr 2016, 15:41 | File version: 2.8.5 |
Thanks for making this nice tool available for the Amiga!
Question: Would it be possible to provide binaries that is optimized for 64 bit CPU's?
|
| |
| |
| Comment by: J.T.Kirk (79.131.48.197) | At: 18 Jan 2016, 13:06 | File version: 2.8.5 |
"updating"... that was obvious...
|
| |
| |
| Comment by: J.T.Kirk (79.131.48.197) | At: 18 Jan 2016, 13:06 | File version: 2.8.5 |
Thank you for upading this excellent program; appreciated.
|
| |
| |
| Comment by: ghh (78.102.145.97) | At: 06 Apr 2015, 22:44 | File version: 2.6.1 |
Thank you! I love this program.
|
| |
| |
| Comment by: MickJT (124.169.172.153) | At: 17 Sep 2014, 01:21 | File version: 2.1.4 |
Paths starting with / will be translated by libunix. I'd rather not link it without that, because I find it useful. Adding ".." before the slash will work around it.
I need a command line example for filter_complex. I have sent you a private message elsewhere.
|
| |
| |
| Comment by: Hypex (202.173.193.240) | At: 16 Sep 2014, 18:13 | File version: 2.1.4 |
Does the filter_complex option work? If I specify it by itself it says I am missing arguments. But if I give arguments it says the option is not recognised! :-?
Also it doesn't accept Amiga path names. If it starts with a slash it thinks it is a volume.
Errors below:
ffmpeg_ppc: missing argument for option 'filter_complex'
Unrecognized option 'filter_complex'
|
| |
| |
| Comment by: MickJT (124.171.138.30) | At: 09 Aug 2013, 21:07 | File version: 2.0 |
If you have a volume called data: or even file:, that is going to confuse ffmpeg because those have special meanings. As you've noticed, changing the case is a workaround. Same goes with having a volume called http:
|
| |
| |
| Comment by: Thematic (88.113.184.161) | At: 07 Aug 2013, 23:25 | File version: 2.0 |
The solution was correct but the cause was actually the exact string 'data:' (read or write, write error message is "Impossible to open the 'data' protocol for writing").
|
| |
| |
| Comment by: Thematic (88.113.184.161) | At: 07 Aug 2013, 23:06 | File version: 2.0 |
Maybe this will save somebody's hair... the Amiga volume name (first part of a path) has to have a capital first letter or it seems to not get recognized as a volume name. The error message is "No ',' delimiter in URI".
I first thought it's just being case sensitive but that isn't the... situation.
|
| |
| |
| Comment by: MickJT (124.171.148.28) | At: 08 Mar 2013, 19:09 | File version: 1.1.3 |
@K-L
I probably should have said the Unpack script is in the FFmpeg directory. One thing I hadn't noticed was that you need to set the executable flag on the files created by xdelta3-decoder, with C:Protect or DOpus. Seeing as I already have the "unpacked" binaries anyway, I wasn't aware of that until now.
|
| |
| |
| Comment by: K-L (89.92.161.176) | At: 08 Mar 2013, 17:52 | File version: 1.1.3 |
Ok, it is written ON OS4Depot :-)
Sorry I did not read so far :-(
|
| |
| |
| Comment by: K-L (89.92.161.176) | At: 08 Mar 2013, 17:47 | File version: 1.1.3 |
Thanks BUT how are we supposed to create the Altivec version ??? I had to google about xdelta-decoder3 to find something on Aminet with a doc and even with this I could not manage to create anything.
I think that even a really small AmigaOS documentation woud have been useful.
BTW, why don't your create the Altivec version and then release it on OIS4Depot ?
|
| |
| |
| Comment by: samo79 (93.144.75.144) | At: 08 Mar 2013, 17:06 | File version: 1.1.3 |
@MickJT
Fantastic, thanks a lot Mick !
|
| |
| |
| Comment by: MickJT (124.171.148.28) | At: 08 Mar 2013, 16:18 | File version: 1.1.3 |
Thanks to Mikael "SMF" Rantanen for testing the Altivec build for me (1.1.3).
|
| |
| |
| Comment by: MickJT (124.171.67.161) | At: 13 Aug 2010, 13:21 | File version: 0.6 |
Make a thread about it on one of the forums. No such problem here. Need more info too, like what your input file is, exactly how you're using ffmpeggui. Post on the forums.
|
| |
| |
| Comment by: DaveyW (203.109.168.245) | At: 13 Aug 2010, 08:21 | File version: 0.6 |
@ktadd
No, I'm not talking about the buffer under-run report. The resulting file is somehow corrupt. If you create a file with mp3 audio, and then use "Input File Info" (on FFMpegGUI) to examine the file, the duration is reported as 00:00:00.00 and the bitrate is enormous (in the test I just ran off, I created with with 2040, but info reports it as "bitrate: 2147483 kb/s". DVPlayer & MPlayer can play the file, but can't seek.
|
| |
| |
| Comment by: ktadd (192.25.142.225) | At: 09 Aug 2010, 20:30 | File version: 0.6 |
Opps, sorry. The last comment was meant for when using with ffmpegGUI.
Still the ffmpeg reported error about buffer issues when encoding to mp3 can be safely ignored.
|
| |
| |
| Comment by: ktadd (192.25.142.225) | At: 09 Aug 2010, 20:27 | File version: 0.6 |
@DavyW
Read the requester that is displayed at the end when encoding to mp3 audio. It's a bug with the library used to encode mp3. It can safely be ignored as pointed out in the requester. Unless of course your getting a different requester? Post to Amigans or Amigaworld if that's the case.
|
| |
| |
| Comment by: DaveyW (203.109.175.230) | At: 06 Aug 2010, 21:01 | File version: 0.6 |
Still seem to be having problems encoding mp3 audio
|
| |
| |
| Comment by: MickJT (124.171.69.129) | At: 08 Jul 2010, 14:26 | File version: 0.6 |
sinisrus, a new version of the GUI will be available very soon. Don't worry.
|
| |
| |
| Comment by: sinisrus (86.70.206.233) | At: 08 Jul 2010, 13:07 | File version: 0.6 |
ffmpeggui crash with ffmpeg 0.6 :-(
|
| |
| |
| Comment by: afxgroup (80.183.222.154) | At: 15 Aug 2006, 13:20 | File version: cvs |
ffmpeg is really simply to compile using the original sources from main page.
but you need a working gg installed or (better..) a cross compiler.
if you need the sources just send a mail
|
| |
| |
| Comment by: anonymous (68.98.237.196) | At: 15 Aug 2006, 06:28 | File version: cvs |
I though you'd have the source included. The real nice thing is that you can use
the ffmpeg.lib and add video i/o to you apps.
Any plans to release the source ? or the lib ?
|
| |
| |
| Comment by: Lio (213.103.209.210) | At: 13 Aug 2006, 19:38 | File version: cvs |
I thought all codecs were already implemented hence the size of the binary.
no pb and thx for this port.
|
| |
| |
| Comment by: afxgroup (80.183.222.154) | At: 13 Aug 2006, 17:52 | File version: cvs |
i'll try to add more codecs, but atm i'm working on mencoder (and mplayer) to..
|
| |
| |
| Comment by: Lio (213.103.201.41) | At: 13 Aug 2006, 17:23 | File version: cvs |
some codecs play well -> thx
could be a multipurpose tool (audio player, video player, for web browser)
ogg is ok but FLAC support is missing.
here is the output :
11.RAM Disk:FFmpeg/Altivec> ffplay_altivec dha:TheRock-BOF.flac
dha:TheRock-BOF.flac: could not find codec parameters
|
| |
| |
| Comment by: spot (85.226.98.50) | At: 13 Aug 2006, 13:07 | File version: cvs |
top notch warez!
|
| |
| |
Audio (343)