Comskip 81.055 released today.

Jul 15, 2013 at 12:16 AM
Edited Jul 15, 2013 at 12:18 AM
Is upgrading the comskip simply a matter of replacing the comskip.ini, comskip.exe and comskip.dictionary? The one currently in use is 81.051 (he skipped from 52 to 55 in the public release dir..probably because the last public release was in December 2012.)

Changes on 0.81.055
  • Bug solved: When the recording has only one commercial at the start and always_keep_first_seconds is set comskip gets into an endless loop
    Changes on 0.81.054
  • Completely new approach for processing while recording. Not fully tested. Do report problems
  • Bug solved: plist output wrong
  • Completely new seeking algorithm in debug window
    Changes on 0.81.053
  • Repaired the preview function in the debugwindow.
  • Multi thread decoding now also works fast on h.264 with video size changes
  • Improved decoding of some types of audio
  • Corrected another mistake in timeline decoding.
  • Bug solved: The .mls file did not contain the last deleted block when it extended to the end of the recording.
    Changes on 0.81.052
  • Parameter added: edl_skip_field, sets the skip indicator in an EDL file. Default value is '0'. Set to edl_skip_field=3 to have better skipping on XBMC
Coordinator
Jul 15, 2013 at 2:46 AM
Yes

Coordinator
Jul 15, 2013 at 2:47 AM
Or you can put it into a different directory and point mcebuddy to it in the expert settings page

Jul 31, 2013 at 1:40 PM
Edited Jul 31, 2013 at 1:41 PM
I have to say, I really love to watch / enjoy MCEBuddy mature ... thanks for your continued work.

Would you please provide just a small bit of clarification? Like MCEBuddy, there are "supporter" versions of many of these components like Comskip. I see that you also have added the ability to specify its location within MCEBuddy. Can we add the ability to enable those features that are in a supporter's version if it is useful to MCEBuddy? Perhaps a simple checkmark or such - I would think autodetecting more trouble than it is worth?

For example, I think the supporter Comskip can use multithread and the public does not.
I just thought this might be an interesting addition.

Mark
Coordinator
Jul 31, 2013 at 4:14 PM
I believe that Comskip configuration is stored in comskip.ini so you should be able to enable all your extra features within comskip.ini and store it along with the donator version and point the advanced settings to that folder/ini file (either in conversion tasks or expert settings).

Does that solve your problem?