search

tmiranda1962 / tmiranda

Automatically exported from code.google.com/p/tmiranda
2 stars 1 forks source link

Feature addition: Provide better SJQ status regarding which files are processed #14

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
The current output does not clearly display which video files are processed. 
The SJQ3 web GUI clearly displayed which video files were processed, which 
files were in the queue, and which files failed to process. Screenshots of the 
SJQ3 web GUI that show the video files in the queue, completed, and failed 
clearly show the type of display information needed.

What version of the product are you using? On what operating system?
I was using SJQ3 with the web GUI. I am now using SJQ4 with the UI plugin.

Please provide any additional information below.
If you look at the application from a functionality viewpoint of which video 
files are processed with Comskip, it is very difficult to determine the status. 
With SJQ3 and the web GUI it was very easy to see which files where in the 
queue waiting to be processed, which files are currently being processed, and 
by which client. The video files that were processed and that failed to process 
was also displayed. The main lacking from the SJQ3 web GUI was no overall 
statistics for the total number of files in the queue, processed, and failed. 
The most important of the three overall statistics are the number of files in 
the queue waiting to be processed. When starting SJQ Comskip processing, there 
could be hundreds or even thousands of files in the queue. A summary number 
would be helpful.

The way the SJQ4 UI functions now is the files are processed by Comskip. It is 
difficult to determine which files are processed. It is sort of like the 
Comskip processing is being done blind. The Comskip jobs are getting done, but 
there's no clear idea of which video files are being processed by Comskip.

Original issue reported on code.google.com by dave.bor...@gmail.com on 15 Feb 2011 at 8:43

GoogleCodeExporter commented 9 years ago

Original comment by tom.mira...@gmail.com on 1 Mar 2011 at 11:36