Avidemux Forum

Participate => User interface and Usability => Topic started by: Grobe on July 17, 2013, 07:13:05 PM

Title: Three feature requests
Post by: Grobe on July 17, 2013, 07:13:05 PM
Hi.

I use Avidemux regularly to encode my home video clips into x264/mp4 so that it's more practically to store. Therefore I feel to say that I think Avidemux is a great program for that purpose. Thanks  :)

I have three feature requests and I hope it's ok to put it all in one thread  :)

1. Cursor should keep position when adding a new movie clip
Every time I add a new clip, I need to set the cursor back to watch the transition between clips. When adding several clips together, I use quite a bit time just to slide the cursor to the time when the video clips meets.

2. Add to queue
Often I find myself making several "versions" of the output file from the same source. Often, the differences is compression rate together with filters. As it is today I have to wait for Avidemux to finnish encoding, then I take a look at the end result, and If I have doubt about if filters and compression settings gives a satisfying result, I do all over again with some different settings.
Therefore, I would like Avidemus to be able to save multiple output files by adding the encoding jobs in a queue. That way, I don't need to sit put - waiting for Avidemux to finnish one job before I alter the settings and having Avidemux do the next encoding jo
b.
Ok, there is an option "Add to queue", but it doesn't work. Either I get an error message saying "Cannot add the juv <job name> to queue", or the job list is just empty when starting the avidemux_jobs.exe, even if I have added jobs.
The feature request is changed to a wish for the queue function to be fixed so it work properly. Tested on Avidemux r8810.

3. Filters - compare output with and without filters
I like to play around with filter settings. However, since my eyes isn't perfect I'cannot tell if a filter do what I want just by looking at the preview in the filters dialog box. I would like to be able to watch two pictures side by side, one with filters and another one without filters.
This is of cours not a wish for transform filters, but for noise filters I think it would helped me a lot in order to pick the most correct filter.


Title: Re: Three feature requests
Post by: bernd_b on July 19, 2013, 10:10:51 AM
Quote from: Grobe on July 17, 2013, 07:13:05 PM
Ok, there is an option "Add to queue", but it doesn't work.

A work around for me is to save the jobs to be done as *.py project and start them via commandline.
Title: Re: Three feature requests
Post by: Jan Gruuthuse on July 19, 2013, 11:55:22 AM
Your OS? You did follow steps as shown in video demo? When queued, then start jobs. Saved jobs should also being found in folder ~/.avidemux6/jobs or its windows equivalent.
Title: Re: Three feature requests
Post by: Grobe on July 19, 2013, 10:49:49 PM
OS: Windows (mostly)

video demo? Haven't seen that. Can you provide a link?
If you refer to this thread (http://www.avidemux.org/smf/index.php/topic,12095.0.html), I wasn't able to find a working solution.

bernd_b - How do you make the .py file tell Avidemux what filename to save as? Or do you just run multiple instances of Avidemux?
Title: Re: Three feature requests
Post by: Jan Gruuthuse on July 20, 2013, 04:53:47 AM
Download 3.6 MB:  QueueAddJob.zip (http://rapidshare.com/files/453225013/QueueAddJob.zip) <- click and download this file. It is not a solution. It shows how to do it.
Title: Re: Three feature requests
Post by: bernd_b on July 21, 2013, 02:05:34 PM
Quote from: Grobe on July 19, 2013, 10:49:49 PM
How do you make the .py file tell Avidemux what filename to save as? Or do you just run multiple instances of Avidemux?

You don't. The py-file only contains the filename of the video to be loaded. When you saved your project, you run it like this, e.g.:
avidemux3_qt4 --nogui --run your_project_file.py --save filename_to_save_the_reencode --quit
where
your_project_file.py
is, of course, your project file

filename_to_save_the_reencode
is what you were asking for, this tells avidemux what filename to use to save the results intended.
Title: Re: Three feature requests
Post by: Grobe on July 26, 2013, 07:00:03 PM
Quote from: Jan Gruuthuse on July 20, 2013, 04:53:47 AM
Download 3.6 MB:  QueueAddJob.zip (http://rapidshare.com/files/453225013/QueueAddJob.zip) <- click and download this file. It is not a solution. It shows how to do it.
I use version 2.6.4 on Windows, and the user interface is not completely similar.
In the vidoeo at 00:30, there pos up a hidden window. I assume that in the windows version, I get it by starting avidemux_jobs.exe.
Problem is - It's empty. There is no jobs to be seen in the window, not a single item, no nothing.

I've also tried to run avidemux_jobs.exe before starting avidemux.exe. When I click File --> Queue, I just got the following error message:
Quote from: Avidemux errormessageQueue
Cannot add job <job name>


bernd_b:
Thanks. I think I can do that using a batch file, but I also considering it being a little too time consuming. I hope that I can manage to make it work the gui way  :D
If I doesn't get the gui to work, I will give this a shot. Not today, maybe next week or so when I can find time.
Title: Re: Three feature requests
Post by: Jan Gruuthuse on July 27, 2013, 05:35:34 AM
QuoteIn the vidoeo at 00:30, there pos up a hidden window. I assume that in the windows version, I get it by starting avidemux_jobs.exe.
no linux ubuntu, yes it is jobs that was closed.
Important you follow steps:
set everything in video, when done:
Text menu: Queue
Click [Open], browse to location where you want to save video (take in to account some folders you can't save = Windows)
give a name: test
click save
In Output file you should see partial the path showing where you want to save.
Give now Job name: job01
press ok
now start avidemux_jobs.exe

job01 should be somewhere $HOME/.avidemux6/jobs/
Start avidemux as administrator and see if this works: if it works you have entitlement properties issues.

If it still fails: user zakk (windows specialist, will be gladly to help out with this windows issue)

This was my last support posting in this forum: you want to know why: ask zakk.

update:--------------------
Search for job01 in windows browser with option include system folders / hidden files.
Part of the problem could be you're installing indifferent partitions/ different paths or if your paths include non US ascii (éèàçñ, ...) or spaces.
Try to keep paths/names as simple as possible. Part of the operation uses command line and this could have issues to.


Title: Re: Three feature requests
Post by: AQUAR on July 27, 2013, 07:44:10 AM
@ Jan  Surely not your last support post!

Your responses are often coming from a well informed user perspective.
So they bridge the technical gap between those involved in the guts of this program and the end user.

These kinds of responses are the most valuable type in these kinds of technical forums.

Now Zakk called me a nobody because I only have a few posts. By that reasoning, with a post number just a fraction of yours, Zakk is a nobody.

And looking through Zakk's posts they are not all that much value adding IMHO.
Just ignore Zakk's baiting posts.

I really do hope you will continue your support here.


Title: Re: Three feature requests
Post by: Jan Gruuthuse on July 27, 2013, 09:18:17 AM
I appreciate what you're trying. Sorry! When the joy of doing something is out of it/taken away, what is point in going on with it.
I restrict myself from now on to supply feedback to developer(s), if there is any feedback.

bye, it was nice to share the avidemux working experience
Title: Re: Three feature requests
Post by: AQUAR on July 27, 2013, 10:06:57 AM
It was worth to try for the avidemux community, pity I failed.

I moderate a couple of forums myself and understand where you are coming from.
Self absorbed/centred people are everywhere and unavoidable in forums like this.
Some just don't get that their persistent negativity spills over to other visitors.
Others are just spammers and polluters by choice.

Deciding, after 3145 post's to quit, is gracious no matter the reason.
So, thanks for all your effort.


Title: Re: Three feature requests
Post by: Grobe on July 27, 2013, 04:11:03 PM
I answer for this post. I cannot see how the later posts in this thread gives sense anyway.

I put my comments as italic text so that it makes sense.

Quote from: Jan Gruuthuse on July 27, 2013, 05:35:34 AM
QuoteIn the vidoeo at 00:30, there pos up a hidden window. I assume that in the windows version, I get it by starting avidemux_jobs.exe.
no linux ubuntu, yes it is jobs that was closed.
Important you follow steps:
set everything in video, when done: ok, done
Text menu: Queue There is no "text-menu in the version I use (Windows, Avidemux 2.6.4 r8810). I find it under File --> Queue.
Click [Open], browse to location where you want to save video (take in to account some folders you can't save = Windows) The place I save the mp4 file is not restricted, tested.
give a name: test File name, ok named it testsaturday.mp4 since I have many testfiles stored there
click save Saved
In Output file you should see partial the path showing where you want to save I see the whole name because I store it on a root folder
Give now Job name: job01 Ok, done
press ok Ok, done
now start avidemux_jobs.exe

jobs should be somewhere $HOME/.avidemux6/jobs/ I install all programs in a separate partition, but should not matter
Start avidemux as administrator and see if this works: if it works you have entitlement properties issues. I use Windows XP and the user I'm logged into has administrative rights

If it still fails: user zakk (windows specialist, will be gladly to help out with this windows issue)
It does fail, I'm afraid. The job window is still just empty.

This was my last support posting in this forum: you want to know why: ask zakk.

Thanks for a throughfull guide, but sadly the problem is still there. I guess that it's just a bug in the program
Title: Re: Three feature requests
Post by: bernd_b on July 27, 2013, 06:24:10 PM
Quote from: Jan Gruuthuse on July 27, 2013, 09:18:17 AM
When the joy of doing something is out of it/taken away, what is point in going on with it.
I restrict myself from now on to supply feedback to developer(s), if there is any feedback.

bye, it was nice to share the avidemux working experience

Well, at least I want to add that I will miss your support posts. To my experience they were always fast, full of knowledge and experience and very helpful. Leave people like me at least with the hope, that there is a chance that joy may will come back after having some break.


So let's try this batch-job-business:

I load a file, do my settings. Instead of choosing "Save" in the File menu I click on "Queue". Here I choose a Job name and the name of the file to which I want the work of avidemux to be saved.

Then I start avidemux3_jobs and the jobs are listed here as expected and can be run both. I checked the box "use qt4" because I don't use the gtk-Version.

To sum up: at least here it seems to work pretty well. Tested on linux, r-8820

So I download a nightly windows version to fire it up with the help of wine:
Doing the same, the Job window of avidemux_jobs.exe stays emtpy.
Title: Re: Three feature requests
Post by: AQUAR on July 28, 2013, 02:56:57 AM
I've never used this feature myself so I am just replying with an observation from a proper installed windows OS.

Applying "que" and then running these qued "jobs" does pop up an empty job list for me.
Looking at the admlog it seems that avidemux_jobs does look in the proper place (user\appdata\roaming\avidemux) for these job files.
But in my case there are no files there because I am using the "nightly" as a portable (to keep all files in the same folder).

Now if I also change the avidemux_jobs executable into a portable version, the job window will pop up and shows all the jobs created.
So if you are using avidemux as a portable then avidemux_jobs is looking at the wrong location.

If you are copying a "nightly" into a location and running it from there you may find the applications flagged as blocked.
This is because it came from another computer (unknown account) and probably creates some access issues to these jobs files.
Look at the properties for the executables (right click on it and select properties) then unflag them if blocked.
This issue may be more critical under windows 7  64 bit.

I've not looked at the windows installer type of avidemux but I guess it may not have these issues.

@ bernd_b

Jan left because Zakk dishes his responses too much.
I unfortunately was caught in a thread were all this came to a head.

If zakk was "adult" enough he would bury the hatchet and try to reverse Jan's resolution.
No doubt both Jan and Zakk are valued posters here and really ought to be able to get along.

For the sake of supporting a great piece of free software and the avidemux end user I vote for JOY.
 

 
Title: Re: Three feature requests
Post by: bernd_b on July 28, 2013, 07:39:34 AM
Quote from: AQUAR on July 28, 2013, 02:56:57 AM
This issue may be more critical under windows 7  64 bit.
Here is a new track:
http://www.avidemux.org/smf/index.php/topic,12437.msg64587.html#msg64587 (http://www.avidemux.org/smf/index.php/topic,12437.msg64587.html#msg64587)
Title: Re: Three feature requests
Post by: Grobe on July 29, 2013, 10:21:58 PM
Ok, after reading your post I realize that if Avidemux (windows version) is just unpacked to a directory and running, there might be access problems.
I'm running Windows XP SP3 and those access problems mentioned in Windows 7 does not aply. Also, Avidemux is properly installed and nightly versions is just unpacked and overwrites the files in the install dir of Avidemux.

What about having the user decide wich folder the job files should be saved into? E.g with an ini file in the Avidemux install folder. Just to avoid access problems? Just like Firefox have this ini file that can be edited to have a users profile dir located elsewhere.
Title: Re: Three feature requests
Post by: AQUAR on July 30, 2013, 01:51:17 PM
I no longer have windows xp installed so I can't see where avidemux puts these job files under this OS.

You are right in that access issues probably don't exist under win XP. 
Leaves the question of where are these job files saved? And is the "nightly version" of avidemux_jobs still looking there?

Why not look in the admlog file and see where avidemux_jobs is looking under XP?
I think its not the same location as for windows 7, but if it is then that might be the reason.

Try portable mode (just append "portable" to the name).
Would solve the issue as everything stays in the avidemux folder (wherever you put it).

Anyway, they are just some ideas for you to consider.
Title: Re: Three feature requests
Post by: bernd_b on July 30, 2013, 02:18:47 PM
Did someone try to run the 32bit version under Windows - which version whatsoever? I run 64bit version and 32bit Windows version of avidemux under linux(!) with the help of wine.
I repeat my results:
64bit: no jobs visible
32bit: jobs visible
So I don't get the point of talking of different windows version, when the last observations seem to suggest a dependency to the version of avidemux? Or did I miss something?
Title: Re: Three feature requests
Post by: AQUAR on July 31, 2013, 01:51:16 PM
I did not see this 64bit: no jobs visible and 32bit: jobs visible.

So looks like we both missed something!

First, Wine is a windows emulator, so you're experience may not apply to the real thing.
Second, different versions of windows behave differently.

XP assumes everyone has super admin rights and therefore lacks "security measures".
Not so with later versions. Windows vista / 7 /8 is set up such that no-one has admin rights (even normal admin accounts).
Security measures are beefed up with any actions that are not normal.
Eg A program installed by an account holder is okay but just copying that program into the program folder will result in it having a blocked flagg.

Your observation is of course perfectly valid, it may well be some broken dependency in the program code.
May also be some broken dependency with windows system calls to locate user data storage folders.