!BatchFFMPEG Alpha
Raik (463) 2061 posts |
There was a privat problem. A lot of private videos from various sources (Smartphones, Camera, what ever) in different formats. Have a hardware media player with a limited range of supported codecs. It create a obey with the ffmpeg options and start if [Convert] is pressed. If [Quit] is pressed, the Obey is only closed and BatchFFMPG ends. FFMPEG should be in !Boot.Library. Works only with newer hardware because any options of ffmpeg are changed. !BatchFFMPEG is a part of a other unfinished fun project. Feel free to download and try. Feedback would be fine. |
David Feugey (2125) 2709 posts |
Nice :) |
Raik (463) 2061 posts |
For me useful and my wife is happy ;-) “New” version. Download “Quit” is now “Cancel”. The output Obey in RAMDisc will be closed, all counter are set to zero. |
John Rickman (71) 646 posts |
Status: does not work for me:-( This is on a Raspberry Pi 3 with 5.23 Dec 17. |
Raik (463) 2061 posts |
Thanks for your feedback. Have try with my Pi3 Pi-Top. Is working like it should. Ahh… is it possible your RamDisc is not present? Have try without gives a uncommented crash. Can you try this version ? Is without using RAMDisc. Create the Obey in the <BatchFFMPEG$Dir>. *unset BatchFFMPEG$Running set it “already not running”. After a unexpected exit it is not unset. |
John Rickman (71) 646 posts |
Can you try this version ? Is without using RAMDisc. Create the Obey in the <BatchFFMPEG$Dir>. Success – thanks. Status: now works for me:-) |
John Rickman (71) 646 posts |
It probably failed before because my RAM discs are renamed for sharing. cofirmed – with the following change original program works REM RAM$=“RAM::RamDisc0.$.” RAM$=“RAM::X6_RAM.$.” |
Andrew Rawnsley (492) 1445 posts |
Try RAM::0.$ which should work on everything (until someone decides that RAM disc is like a hard disc and should be numbered :4, but we’ll cross /that/ bridge when we come to it). |
Rick Murray (539) 13840 posts |
How about |
John Rickman (71) 646 posts |
How about RAM:$. works for me: |
Raik (463) 2061 posts |
Where ist the best place? !Scrap, RamDisc, <BatchFFMPEG$Dir>.Temp… ? |
John Rickman (71) 646 posts |
Where is the best place? RAM is good – I always have the RAM disk open, and if you use the identifier :- RAM:$. it works on any machine. Please don’t use !Scrap. Also inside the App is not good as it is not normally visible. |
John Rickman (71) 646 posts |
Is a Edit button to change the TaskObey after the collection has closed useful? Yes – good idea. It does not matter then where you put the obey file. In fact you could just open it by default for inspection and edit before execution. |
Rick Murray (539) 13840 posts |
And for those who don’t habitually have a RAMdisc open? 1
Why not? Isn’t that what Scrap is there for? Maybe a compromise is required: Try to read the catalogue of 1 My mother knows to press Ctrl-Shift-F12 to perform an orderly shutdown of the system.2 I have a prompt that asks if I wish to shutdown, restart, or cancel. I have a little NoError module to auto-cancel the pop up error box after five seconds (by faking pressing Esc). My shutdown prompt is designed in such a way that ESC press performs a shutdown. 2 Which happens more than you might think due to the thunderstorms that bite. |
Steve Fryatt (216) 2105 posts |
Indeed. Scrap is the correct place. Inside the application folder is bad, as you’re assuming that it’s writable. If you want to use the RAM disc, make it an option that users can turn on (default to off), and fall back to Scrap if the option is on but no RAM disc is present. |
John Rickman (71) 646 posts |
Why not? Isn’t that what Scrap is there for? Scrap is best used for intermediate files that Application deletes when it closes. The obey file that BatchFFmpeg creates may well be wanted for inspection and edit by the user. So I don’t think Scrap is a good place for it. It is not easy to access and is likely to not be deleted thus adding to the (S)crap that gets left in the !Boot directory. Of course if you have moved !Scrap out of !Boot and into RAM it does not matter. |
John Rickman (71) 646 posts |
Where is the best place? Upon reflection. How about a pop-up Save dialogue box. Then it can be dragged dropped where it suits the user. I would always like to examine the generated commands before executing them. |
Rick Murray (539) 13840 posts |
Except for the part where more than a few apps use it as cache space. Manga, PhotoDesk (clipboard), PlingStore (when it isn’t writing into itself!), NetSurf… ;-) Perhaps better to say “Scrap is best used for intermediate files which are deleted after use, and transient/cache files whose deletion won’t cause software to break.” [note: transient as in temporal, not as in utility]
Fixed that for you. |
RonM (387) 60 posts |
Perhaps better to say “Scrap is best used for intermediate files which are deleted after use, and transient/cache files whose deletion won’t cause software to break.” I always use WimpScrap$Dir in RAMFS. One advantage not quite so obvious, if FS corruption happens before the temp usage is over, you then only have a duff RAMFS. |
Steve Pampling (1551) 8170 posts |
I’m sure there’s probably more that abuse the Scrap by treating the location for ephemeral files as a long term storage area. |
Raik (463) 2061 posts |
I think I try something like this At start it tells a “default place”, if anybody will change… drag the icon. Not sure if I should make a writable field. Maybe. But step by step. I not really know what I do. ;-) |
Steve Pampling (1551) 8170 posts |
Interesting, a day later and I don’t a collection of irate programmers replying… |
Raik (463) 2061 posts |
A new Version is available from here. Main changes: |
Raik (463) 2061 posts |
A new Download with any small changes is available now. |