Comment by: ktadd (69.181.249.19) | At: 12 Aug 2024, 07:22 | File version: v3.5 |
@Frank I'm a bit confused by your question about the order of window gadgets. As far as I can tell the gadgets are in the default order. From top outside to inside: "Front/Back" "Wdindow size toggle" which doesn't really toggle the size since I've fixed the height. "Iconify" "Menu" If I'm missing something, feel free to send me an email at the address listed in the guide file.
|
|
|
Comment by: Frank (94.31.67.226) | At: 10 Aug 2024, 13:31 | File version: v3.5 |
Would it be possible to put the window gadget in the usual default position? Starting form the top right corner from the outside to the inside, the unusual order is: "gadget menu" "iconify" "Front/Back" "size toggle" I am used to the default AmigaOS. Starting form the top right corner from the outside to the inside: "Front/Back" "Window size toggle" "iconify" "Menu" thanks for reading!
|
|
|
Comment by: ktadd (69.181.249.19) | At: 11 Dec 2023, 18:24 | File version: v3.5 |
Re-uploaded v3.5 with corrected tooltypes.
|
|
|
Comment by: ktadd (69.181.249.19) | At: 11 Dec 2023, 18:06 | File version: v3.5 |
@Primax Actually, you don't need to fill out the tooltype. If you leave them disabled ffmpegGUI will try using AppDir: to automatically find it. I believe I also check the C: directory if the tooltype is not set. The Tooltype is there in case you don't like using AppDir: and you have ffmpeg located other than in the C: directory. Unfortunatly It looks like i forgot to clean out the ToolTypes before uploading. The defaults should look like this: (CMD_PATH = <volume:> [path] ) (VPLAYER = <volume>[path]/<player program name>) (VPLAYER = APPDIR:MPlayer) (INFILE0 = <volume:>[path]/ [filename]) (INFILE1 = <volume:>[path]/ [filename]) (OUTFILE = <volume:>[path] <filename.ext>) OUTFILE = Ram:Outfile SETTINGS_PATH = Settings (STACKSIZE = 300000) (USE_KINGCON) (DISABLE_AUDIO) (START_OFFSET = <string>) (DURATION = <string>) (ADD_OPTS = <command string>) (VERBOSE_OUTPUT)
|
|
|
Comment by: Primax (91.18.230.149) | At: 11 Dec 2023, 10:38 | File version: v3.5 |
Thanks! I actually do not understand why I have to manually add the link for videoplayer in the tooltypes. That makes no sense, having a GUI for a program which should avoid writing and editing paths and values...
|
|
|
Comment by: Fan (91.64.151.111) | At: 10 Dec 2023, 20:10 | File version: v3.5 |
Thanks you a lot gor the Update!!!
|
|
|
Comment by: thematic (88.114.191.143) | At: 22 Apr 2021, 06:48 | File version: v3.4 |
If "Start Offset" isn't accurate enough, you should use "-ss <seconds>" in Output, instead. Explanation: if the option is after the input file, ffmpeg will work the beginning from all frames, not only keyframes.
|
|
|
Comment by: Ben (82.197.222.230) | At: 15 Nov 2018, 13:42 | File version: v3.4 |
Thank you, very usefull programm.
|
|
|
Comment by: tommysammy (93.221.60.72) | At: 09 Feb 2015, 06:15 | File version: v3.2 |
Hey Kevin Your spam filter is activated I can`t send any mails to your address. Everytime they come back to me
|
|
|
Comment by: ktadd (206.49.107.56) | At: 30 Jul 2013, 19:23 | File version: v3.1 |
If anyone has usage questions please feel free to email me at the address listed in the ffmpegGUI.guide file.
|
|
|
Comment by: ktadd (206.49.107.56) | At: 30 Jul 2013, 19:21 | File version: v3.1 |
@Petral Make sure ffmpegGUI's Scale and Aspect settings are set to Default. In the additional Options / Output field add the following: -vf scale=320:-1 Set 320 to what ever width you would like. -1 tells the filter to keep the aspect ratio.
|
|
|
Comment by: MickJT (124.171.138.30) | At: 30 Jul 2013, 15:20 | File version: v3.1 |
I know on the command line if you put -s WxH just before the output filename, it will resize it to that size. I think the developers want you to use -video_size now though.
|
|
|
Comment by: Petrol (141.227.1.38) | At: 30 Jul 2013, 08:44 | File version: v3.1 |
Thank you for this update! How can I resize a video, without stretching it or without adding black bands! I tried to specify a custom size as video output with the -s LxH option, but it didnt work!
|
|
|
Comment by: ktadd (24.130.98.19) | At: 16 Jan 2011, 02:08 | File version: v3.0 |
@DavyW I looked into adding libx264 support into the v3.0 release and in testing it out I found that libx264 does not work properly. It produces unacceptable results that aren't watchable. Using it is not that straight forward as it requires a preset file so I don't plan to go through the trouble to add support for it until it's working properly. You can try it out yourself from ffmpegGUI by creating a preset file and adding the command line options in the outupt field of ffmpegGUI. I will add support if it ever works correctly. Let me know if you find a way to get good results from it.
|
|
|
Comment by: DaveyW (203.109.166.8) | At: 15 Jan 2011, 23:25 | File version: v3.0 |
Thanks for the update Kevin. Now that the OS4 compile supports it, would you consider adding libx264 as a codec? Haven't used it myself but people seem to prefer it to Mpeg4 Part 2.
|
|
|
Comment by: ktadd (24.130.98.19) | At: 29 Nov 2010, 06:55 | File version: v3.0 |
@shadowsun Make sure your using either the April 1st or summer version of MPlayer. In older version the AREXX interface either didn't exist or didn't work properly.
|
|
|
Comment by: shadowsun (10.20.211.11) | At: 29 Nov 2010, 06:24 | File version: v3.0 |
Thanks for this GUI. - wwhen HELP is open by menu, it's not asynchronous - panel control for MPlayer don't work
|
|
|
Comment by: VooDoo (83.131.242.26) | At: 01 Aug 2010, 08:47 | File version: v2.3 |
Thanx for this new version!!
|
|
|
Comment by: ktadd (24.130.98.19) | At: 01 Aug 2010, 07:51 | File version: v2.3 |
Sorry, forgot to include the iphone settings file. If anyone want's it just email me at the address in the ffmpegGUI.guide file.
|
|
|
Comment by: spot (83.248.105.187) | At: 01 Aug 2010, 06:07 | File version: v2.3 |
atleast in the old screenshot, might be fixed now?
|
|
|
Comment by: spotUP | At: 01 Aug 2010, 06:06 | File version: v2.3 |
the about window has a typo. it says requres, should say requires i guess. =)
|
|
|
Comment by: ktadd (24.130.98.19) | At: 04 Feb 2009, 15:13 | File version: v2.1 |
Ok. Thanks orgin. I was wondering how that work. At least this will be linked to ffmpeg then.
|
|
|
Comment by: orgin | At: 04 Feb 2009, 10:49 | File version: v2.1 |
Note to uploader: It is not possible to add an arbitrary link at the bottom of the readme page. The list of links are generated automatically by matching the filename of teh file you are watching with other files in the same category. Examples: myfile.lha will show links to anything named myfile#? myfile-src.lha will show links to anything named myfile#? myfile_src.lha will show links to anything named myfile#? myfilegui.lha will show links to anything named myfilegui#?
|
|
|
Comment by: Amigan (91.140.32.29) | At: 20 Jan 2009, 03:00 | File version: v1.2.1 |
should = shouldn't
|
|
|
Comment by: Amigan (91.140.32.29) | At: 20 Jan 2009, 02:44 | File version: v1.2.1 |
Could you consider making a 68k version? It should be difficult for this kind of program.
|
|
|
Comment by: ktadd (24.130.98.19) | At: 19 Jan 2009, 17:48 | File version: v1.2 |
New v1.2.1 with fix uploaded!
|
|
|
Comment by: ktadd (24.130.98.19) | At: 19 Jan 2009, 17:24 | File version: v1.2 |
I've gotten reports that v1.2 fails when trying to open a library. I've got a fix and will upload soon! Sorry for the trouble.
|
|
|
Comment by: anonymous (217.95.208.119) | At: 11 Nov 2007, 23:21 | File version: v1.0 |
Very nice thanks.
|
|
|
Comment by: MichaelMerkel (62.214.208.100) | At: 04 Sep 2007, 19:53 | File version: v1.0 |
looks coool!!! the tool of the history.txt.info is set to "SYSOS4:Utilities/MultiView"... that should be SYS: instead of SYSOS4:. byebye...
|
|
|
Comment by: ToAks (80.202.194.155) | At: 04 Sep 2007, 19:47 | File version: v1.0 |
Great!, a gui was always needed for this cli tool, thanks for dooing one, much appriciated. 2 things in 1 day that i really want, wow :)
|
|
|
Comment by: PEB (75.3.121.117) | At: 17 Aug 2007, 14:06 | File version: v0.6 |
Thanks! This should make using ffmpeg a whole lot easier.
|
|
|