What should I do next?

Where all the announcements go
Post Reply
erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

What should I do next?

Post by erik »

There are many possible new extensions for Comskip so I need your input.
Some of the extensions are not realy feasible on short term.
Vote in the poll and add you comments so I know what you are waiting for.

stattik
Posts: 17
Joined: Sat Dec 24, 2005 9:09 pm

Post by stattik »

We talked about this in the past and there was a post in the GBPVR forums involving you, Sub and Jere but I don't know where we stand on it.

http://forums.gbpvr.com/showthread.php?t=10872

For ATSC broadcasts that change FPS, comskip correctly identifies the right frames but when it's gets translated to the EDL files, the times are off. I realize that this may be major work to get comskip to identify by time and not frame so I don't know if it can be done.

erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

Post by erik »

So if I would track the changes in fps and recalculate the frame numbers to the correct time taking these changes into account that would be solved.
Now I have to find a stream with these chages so I can test.
Did I already receive such a stream from you?
I do remember a strange stream with switched continuesly between 25fps and 30 fps resulting in 29.97fps.

stattik
Posts: 17
Joined: Sat Dec 24, 2005 9:09 pm

Post by stattik »

Yeah, I sent you an stream a few months ago that had the FPS changes along with some commercial transitions. I could put together another one if you need it.

K.B
Posts: 11
Joined: Sat Feb 25, 2006 4:16 am
Location: Australia

Post by K.B »

I would hate to see a windows GUI version created if its at the expense of the command line version.

How about making comskip more COM friendly? That way people could put their own GUI on it and it would also be easily embedded in VB or VBScript (which have better error handling and debugging than BAT files).

It should be easy to wrap it into a COM object, just add a property for each command line param and a Convert method that outputs a collection of break points.

I can't get the current comskip version to work from VBScript at all at the moment, it gets about 40 seconds (or 15000 or so frames) in and goes into an executive wait state. To get around this I have to schedule a command using "at" and monitor the queue waiting for completion.

Love the product, keep up the good work :D

erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

Post by erik »

stattik wrote:Yeah, I sent you an stream a few months ago that had the FPS changes along with some commercial transitions. I could put together another one if you need it.
No need for the moment but thanks anyway.

erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

Post by erik »

K.B wrote: It should be easy to wrap it into a COM object, just add a property for each command line param and a Convert method that outputs a collection of break points.
Any pointers on how to do that?
I stopped learning programming after K&R C on Unix System V
:oops:

K.B
Posts: 11
Joined: Sat Feb 25, 2006 4:16 am
Location: Australia

Post by K.B »

Well there's the easy way and the hard way. :wink:

The hard way being to spend the next 12 months of your life stuggling to make it work in C/C++.

The easy way is to re-package comskip pretty much as is into a DLL and export one or more functions (see http://msdn2.microsoft.com/en-us/library/z4zxe9k8.aspx) to expose the functionality then use either VB6 or .Net to take care of all the nasty COM stuff.

The more interfaces you expose the better the COM interface would be for people wanting to write GUIs. Personally, I run all my stuff on a server without a monitor or keyboard so I'm not fussy.

I haven't wielded a compiler professionally for a year or two but I could knock something up quickly if you created the DLL.

Obviously you would need to create both your EXE and the DLL for every release going forward. That might be possible using two make files depending on how your code is structured.

roy
Posts: 11
Joined: Sun Mar 19, 2006 9:25 pm

Post by roy »

Faster is always good.

Also, I don't know if it's a new detection method, but, I seem to be seeing more promos for network shows, I think because the logo is there and it leads into or out of a commercial, it looks more like show than commercial. Is there an existing method to tune for this?

erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

Post by erik »

shrink_logo can be used to reduce the duration of the logo.
its in seconds
setting
shrink_logo=5
makes comskip assume the logo disappears 5 seconds earlier than in reality.
It also causes comskip to assume the logo appears 5 seconds later.

You can set it to any value.
A unreliable logo and a too high shrink_logo will cause false cutpoints leading to possible false positives.

Ralph
Posts: 12
Joined: Wed Dec 07, 2005 11:16 pm

Post by Ralph »

How can I vote???
I can't choose any of the options above?

But nevertheless I would choose this:

1. Make Comskip faster (20% faster may be possible, not much more)
That would be a great. Comskip works quite stable and can use a lot of input files and creates many output files.
That's why I think now performance should be enhanced.

2. Combine all the documentation in one nice manual (possible)
The documentation is quite good right now.
But it would be nice having every single option that's in comskip.ini explained.

3. Give comskip a nice windows userinterface (specify why)
It doesn't matter if it's nice or not, but a userinterface to specify all option,
even locations of mpgtx or other cut programs without using the text-editor to go through the ini and bat files would be quit userfriendly, that's right.
The possibility to use Comskip right from this GUI to start the scan, having a preview to correct the cutpoints
and to cut the file without leaving the GUI would make Comskip quite interesting for more users.
But right now, I don't need that, that much.

Because I would like to use Comskip with MediaPortal, Point 1 and 2 are more important to me.
And now Comskip can use dvr-ms files it's my turn to get it work within MediaPortal.

Thanks for your efforts
Ralph

Jim_
Posts: 3
Joined: Thu Mar 16, 2006 6:45 am

Post by Jim_ »

Hi Eric,
You have everything covered so well that it?s hard to think of a request! I even noticed that comskip marked VRD cut points are much more accurate in the latest versions.
One thing I?ve always thought would be nice, is if comskip could include "scene markers" in the videoredo project. Seeing all the scenes comskip detected (used or not) would sure make tuning and VRD editing easier for us VRD fanatics.
Thanks for a utility I cant (will not) live without! :D
Jim

erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

Post by erik »

Could you post en example of such scene marking?

Jim_
Posts: 3
Joined: Thu Mar 16, 2006 6:45 am

Post by Jim_ »

Sure can Eric, and thanks for considering it.
Comskip detected 38 blocks (would not want all 308 black frames) and VideoReDo detected 30 on this show.
I scanned the mpeg with VRD afterwards, and just added the SceneMarkers to the bottom of the comskip generated project.
Thanks again!
Jim


<Version>2
<Filename>G:\comskip79_46\mpg\MXC_20060518_00000030.mpg
<Cut>4255584667:5666994667
<Cut>8590582000:11001991000
<Cut>13372692667:15438756667
<Cut>18673655000:18978626333
<Cut>19189503667:19189837333
<SceneMarker 0>797115333
<SceneMarker 1>1083729555
<SceneMarker 2>4254502333
<SceneMarker 3>4708947222
<SceneMarker 4>5011243222
<SceneMarker 5>5162391222
<SceneMarker 6>5463686222
<SceneMarker 7>5667552555
<SceneMarker 8>8587744555
<SceneMarker 9>8711198777
<SceneMarker 10>8891708777
<SceneMarker 11>9193003777
<SceneMarker 12>9345152666
<SceneMarker 13>9496300666
<SceneMarker 14>9797595555
<SceneMarker 15>10097889444
<SceneMarker 16>10401186333
<SceneMarker 17>10700479333
<SceneMarker 18>11002107888
...
..
.

erik
Site Admin
Posts: 3344
Joined: Sun Aug 21, 2005 3:49 pm

Post by erik »

Jim_ wrote: One thing I?ve always thought would be nice, is if comskip could include "scene markers" in the videoredo project. Seeing all the scenes comskip detected (used or not) would sure make tuning and VRD editing easier for us VRD fanatics.
Will be in build 53 and later

Post Reply