My favorites | Sign in
Project Logo
Project Home
  
Downloads
  
Issues
  
Source
    
Summary | Updates | People
Details: Show all Hide all

Last 30 days

  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by evilblender   -   I'd love to help debug this - but lack the proper coding kung-fu. What would be helpful in looking at it - I would be happy to post "sample process" reports from Activity Monitor or any kind of log file if you'd like. I've got the same issue others have. With 10.6, memory slowly gets eaten up by ComSkipper application. I wouldn't mind knowing how to stop it and restart it again... maybe a cron job every 24 hours killing and restarting it? Let me know if you need any files that would help you debug. Regards, Jeff
    I'd love to help debug this - but lack the proper coding kung-fu. What would be helpful in looking at it - I would be happy to post "sample process" reports from Activity Monitor or any kind of log file if you'd like. I've got the same issue others have. With 10.6, memory slowly gets eaten up by ComSkipper application. I wouldn't mind knowing how to stop it and restart it again... maybe a cron job every 24 hours killing and restarting it? Let me know if you need any files that would help you debug. Regards, Jeff
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by nowalmart   -   As I said in the EyeTV forums, I have Wine+Comskip v80.025 working on my machine using the etv-comskip script. It works, but does have some annoying aspects - the biggest is that Wine launches X11 everytime it is called. I have not tried running it using wineconsole since upgrading to Snow Leopard, so maybe this report is accurate: http://bugs.winehq.org/show_bug.cgi?id=16702 I do not have ComSkipper running due to the memory leak, but since I generally share out my EyeTV recordings to a UPnP device, this is not as important to me. I will be getting some directions on this setup on the Elgato forums on Thursday (my next day off from work).
    As I said in the EyeTV forums, I have Wine+Comskip v80.025 working on my machine using the etv-comskip script. It works, but does have some annoying aspects - the biggest is that Wine launches X11 everytime it is called. I have not tried running it using wineconsole since upgrading to Snow Leopard, so maybe this report is accurate: http://bugs.winehq.org/show_bug.cgi?id=16702 I do not have ComSkipper running due to the memory leak, but since I generally share out my EyeTV recordings to a UPnP device, this is not as important to me. I will be getting some directions on this setup on the Elgato forums on Thursday (my next day off from work).
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by jon.christopher   -   Thanks for the feedback, azstefano. I'll have to look in to this memory leak. ComSkipper is different from comskip itself. In fact ComSkipper itself is just a python script which polls EyeTV to see if it's playing a recording, and if so, if the current time is within a commercial interval. I don't see anything in the script which should make the memory usage grow. Perhaps there's a leak in python itself, or appscript? Something which would cause a long-running process to gradually accumulate memory. -Jon
    Thanks for the feedback, azstefano. I'll have to look in to this memory leak. ComSkipper is different from comskip itself. In fact ComSkipper itself is just a python script which polls EyeTV to see if it's playing a recording, and if so, if the current time is within a commercial interval. I don't see anything in the script which should make the memory usage grow. Perhaps there's a leak in python itself, or appscript? Something which would cause a long-running process to gradually accumulate memory. -Jon
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by azstefano   -   Comskipper works fine for me on Mac OS 10.6.2. It is reliable and has a very good "sense" of what content is not programming (for my off-air ATSC broadcast media). The comskip process occasionally crashes - about 5% of the time - but that leaves the media file unaffected. While there does seem to be a memory leak, I don't find it nearly enough of a problem to forgo using it. I use it every day.
    Comskipper works fine for me on Mac OS 10.6.2. It is reliable and has a very good "sense" of what content is not programming (for my off-air ATSC broadcast media). The comskip process occasionally crashes - about 5% of the time - but that leaves the media file unaffected. While there does seem to be a memory leak, I don't find it nearly enough of a problem to forgo using it. I use it every day.
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by techydude   -   i'm glad it works well for some :) but it's never worked reliably for me or anyone i know whose tried it. some recordings get marked, some (more than 50%) don't. sometimes it skips marked commercials on playback, most of the time it doesn't. and it always, after a day or three, consumes ridiculous amounts of ram. i'm not blaming you or anyone, obviously this is a casual best-effort non-commercial project. but after rebuilding with Snow Leopard recently, and seeing my friend install the new SL-compatible version of it, and experience exactly the same issues above, i'm over it & wont be spending anymore time with the current 18month old code. maybe it was you that i/friend-of-mine googled the other day, i can't remember now - are you documenting this new update somewhere else? need testers? i'm happy to help.
    i'm glad it works well for some :) but it's never worked reliably for me or anyone i know whose tried it. some recordings get marked, some (more than 50%) don't. sometimes it skips marked commercials on playback, most of the time it doesn't. and it always, after a day or three, consumes ridiculous amounts of ram. i'm not blaming you or anyone, obviously this is a casual best-effort non-commercial project. but after rebuilding with Snow Leopard recently, and seeing my friend install the new SL-compatible version of it, and experience exactly the same issues above, i'm over it & wont be spending anymore time with the current 18month old code. maybe it was you that i/friend-of-mine googled the other day, i can't remember now - are you documenting this new update somewhere else? need testers? i'm happy to help.
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by jon.christopher   -   As it happens, I'm currently working on updating comskip. "farce" is a bit strong. Its been working just fine for me, so I've had no need to update it. As you say, comskip itself is windows-centric, so the port is non-trivial. Patches welcome.
    As it happens, I'm currently working on updating comskip. "farce" is a bit strong. Its been working just fine for me, so I've had no need to update it. As you say, comskip itself is windows-centric, so the port is non-trivial. Patches welcome.
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by techydude   -   Comskipper for Mac is a farce, its core code is 18 months old & not being updated, because the development is focusing on Windows API calls that can't easily be ported to Max OS X. i think development is continuing elsewhere, when i find out more i'll post again, but forget this strain of Comskipper!
    Comskipper for Mac is a farce, its core code is 18 months old & not being updated, because the development is focusing on Windows API calls that can't easily be ported to Max OS X. i think development is continuing elsewhere, when i find out more i'll post again, but forget this strain of Comskipper!
  • Dec 07, 2009
    issue 12 (comskip compiled for Intel64 runs 20% faster) commented on by david.blanchard   -   I take it this must be installed manually, where exactly does this go?
    I take it this must be installed manually, where exactly does this go?
  • Dec 07, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by david.blanchard   -   Any progress with this bug? As it is right now, I have to kill comskipper and restart it every other day due to the memory leak/bug (when it reaches around 1.5gb).
    Any progress with this bug? As it is right now, I have to kill comskipper and restart it every other day due to the memory leak/bug (when it reaches around 1.5gb).

Earlier this year

  • Nov 20, 2009
    issue 12 (comskip compiled for Intel64 runs 20% faster) commented on by Jens.Lan...@light-speed.de   -   After having checked out the sources of etvcomskip I took the hassle to try to compile comskip for x86_64. As brian pointed out libmpeg2 needs to be updated to version 0.5.1 to let comskip compile properly. After some time of diff checking and patching I was finally able to compile a x86_64 version of comskip. I will attach it together with the patch against the latest SVN sources of etvcomskip so that it may get integrated one day ;)
    After having checked out the sources of etvcomskip I took the hassle to try to compile comskip for x86_64. As brian pointed out libmpeg2 needs to be updated to version 0.5.1 to let comskip compile properly. After some time of diff checking and patching I was finally able to compile a x86_64 version of comskip. I will attach it together with the patch against the latest SVN sources of etvcomskip so that it may get integrated one day ;)
  • Nov 20, 2009
    issue 30 (Excluded Station Names feature doesn't seem to work) commented on by Jens.Lan...@light-speed.de   -   Please note that this problem is already fixed in the 0.3.1 version of MarkCommercials.py which I attached to my old bug report here: http://code.google.com/p/etv-comskip/issues/detail?id=10
    Please note that this problem is already fixed in the 0.3.1 version of MarkCommercials.py which I attached to my old bug report here: http://code.google.com/p/etv-comskip/issues/detail?id=10
  • Nov 19, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by alrasaltinnin   -   My computer has been on with EveTV running to record a few shows and ComSkipper is now using 3.53 gigs of real memory...
    My computer has been on with EveTV running to record a few shows and ComSkipper is now using 3.53 gigs of real memory...
  • Nov 06, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by evilblender   -   My ComSkipper PID 266 is up to 542.9 MB real mem usage with 0.0%CPU usage. Virtual Mem 3.12GB Virtual Private 548.1MB OS 10.6.1 Etv 3.1.2 comskipper
    My ComSkipper PID 266 is up to 542.9 MB real mem usage with 0.0%CPU usage. Virtual Mem 3.12GB Virtual Private 548.1MB OS 10.6.1 Etv 3.1.2 comskipper
  • Oct 20, 2009
    issue 30 (Excluded Station Names feature doesn't seem to work) commented on by m...@martin-probst.com   -   No, "Das Erste" is the literal name, without any umlauts, so this should not be an encoding problem. I will try your code change, lets see if this helps. I field another bug for umlauts within MarkCommercials.cfg (not supported atm).
    No, "Das Erste" is the literal name, without any umlauts, so this should not be an encoding problem. I will try your code change, lets see if this helps. I field another bug for umlauts within MarkCommercials.cfg (not supported atm).
  • Oct 20, 2009
    issue 30 (Excluded Station Names feature doesn't seem to work) commented on by jon.christopher   -   Given that the names of the stations appear to be in a non-english language (German?) I suspect that may be part of the problem. For printing purposes, MarkCommercials.py strips non-ascii characters from the station name, and replaces them with an ascii compatible version. This is necessary to prevent a crash. msg=' Station name: %s' % stationName ==> print msg.encode("ascii","replace"), if stationName in excludedStationNames: However, the actual comparison is done on the full unicode version of the station name. Does the actual station name "Das Erste" contain umlauts or some non-ascii character? If so, can you change the line in the config file to match the actual station name? Alternately, you might want to try comparing the ascii version: if stationName.encode("ascii","replace") in excludedStationNames: Finally, you could try using station number instead. -Jon
    Given that the names of the stations appear to be in a non-english language (German?) I suspect that may be part of the problem. For printing purposes, MarkCommercials.py strips non-ascii characters from the station name, and replaces them with an ascii compatible version. This is necessary to prevent a crash. msg=' Station name: %s' % stationName ==> print msg.encode("ascii","replace"), if stationName in excludedStationNames: However, the actual comparison is done on the full unicode version of the station name. Does the actual station name "Das Erste" contain umlauts or some non-ascii character? If so, can you change the line in the config file to match the actual station name? Alternately, you might want to try comparing the ascii version: if stationName.encode("ascii","replace") in excludedStationNames: Finally, you could try using station number instead. -Jon
  • Oct 20, 2009
    issue 30 (Excluded Station Names feature doesn't seem to work) reported by m...@martin-probst.com   -   What steps will reproduce the problem? 1. Given the config line: EXCLUDED_STATION_NAMES = NDR FERNSEHEN|Das Erste|3sat|ZDF|WDR Kln|Sdwest BW/RP 2. Running MarkCommercials all gives output like this: > 2. Processing "Babel" on [Das Erste] channel [1]... > Channel: 1 , not skipped > Title: Babel , not skipped > Station name: Das Erste , not skipped What is the expected output? What do you see instead? I'd expect this recording to be skipped du to the station name. Maybe it's because of the trailing whitespace in the name? However I tried changing MarkCommercials.py to call stationName.trim(): > if stationName.strip() in excludedStationNames: > ... But that doesn't seem to make a difference.
    What steps will reproduce the problem? 1. Given the config line: EXCLUDED_STATION_NAMES = NDR FERNSEHEN|Das Erste|3sat|ZDF|WDR Kln|Sdwest BW/RP 2. Running MarkCommercials all gives output like this: > 2. Processing "Babel" on [Das Erste] channel [1]... > Channel: 1 , not skipped > Title: Babel , not skipped > Station name: Das Erste , not skipped What is the expected output? What do you see instead? I'd expect this recording to be skipped du to the station name. Maybe it's because of the trailing whitespace in the name? However I tried changing MarkCommercials.py to call stationName.trim(): > if stationName.strip() in excludedStationNames: > ... But that doesn't seem to make a difference.
  • Oct 20, 2009
    issue 29 (MarkCommercials.cfg cannot contain extended characters (UTF-...) reported by m...@martin-probst.com   -   What steps will reproduce the problem? 1. Enter a station name with an Umlaut in any encoding into the cfg 2. Run MarkCommercials I'd expect MarCommercials to read the config file using UTF-8 encoding, but apparently it insists on ascii. Thus, users who receive stations that have Umlauts (or any other non-ascii characters) in their names cannot filter for them.
    What steps will reproduce the problem? 1. Enter a station name with an Umlaut in any encoding into the cfg 2. Run MarkCommercials I'd expect MarCommercials to read the config file using UTF-8 encoding, but apparently it insists on ascii. Thus, users who receive stations that have Umlauts (or any other non-ascii characters) in their names cannot filter for them.
  • Oct 14, 2009
    issue 28 (Comskip crashing occasionally ) reported by mohawk   -   What steps will reproduce the problem? 1. record many shows (say 6) 2. while 4 shows are being skipped compact 2 and start encoding immediately after company 3. more shows start recording and then comskipping 4. wait for the grey transparent apple fatal warning box to appear What is the expected output? What do you see instead? see 4 What version of the product are you using? On what operating system? Snow Leopard 10.6.1, EyeTV 3.2, turbo.264 HD Please provide any additional information below. The console displays event and launchd errors when this occurs. Could the problem I am observing be related to this? --> http://db.tidbits.com/article/10643
    What steps will reproduce the problem? 1. record many shows (say 6) 2. while 4 shows are being skipped compact 2 and start encoding immediately after company 3. more shows start recording and then comskipping 4. wait for the grey transparent apple fatal warning box to appear What is the expected output? What do you see instead? see 4 What version of the product are you using? On what operating system? Snow Leopard 10.6.1, EyeTV 3.2, turbo.264 HD Please provide any additional information below. The console displays event and launchd errors when this occurs. Could the problem I am observing be related to this? --> http://db.tidbits.com/article/10643
  • Sep 30, 2009
    issue 27 (Multiple PIDs cause commercial skipping not to work - possib...) reported by benblaughs   -   What steps will reproduce the problem? 1. Running the triggered script What is the expected output? Commercials are marked. What do you see instead? No commercials are marked and the log file says Multiple PIDs found. Whilst you can specify a PID for comskip (and one of the identified PIDs does mark the commercials correctly) there is no way in the current version of MarkCommercials to specify a PID. What version of the product are you using? On what operating system? 1.0.3-10.6 on MacOS X 10.6 Please provide any additional information below. I have modified MarkCommercials.py to allow for specifying the PID. Additionally there are two triggered scripts to support this. RecordingStarted.scpt runs the MarkCommercials normally, RecordingDone.scpt checks if multiple PIDs are present and reruns MarkCommercials for a specific PID. Can this be included in a new release of etv-comskip?
    What steps will reproduce the problem? 1. Running the triggered script What is the expected output? Commercials are marked. What do you see instead? No commercials are marked and the log file says Multiple PIDs found. Whilst you can specify a PID for comskip (and one of the identified PIDs does mark the commercials correctly) there is no way in the current version of MarkCommercials to specify a PID. What version of the product are you using? On what operating system? 1.0.3-10.6 on MacOS X 10.6 Please provide any additional information below. I have modified MarkCommercials.py to allow for specifying the PID. Additionally there are two triggered scripts to support this. RecordingStarted.scpt runs the MarkCommercials normally, RecordingDone.scpt checks if multiple PIDs are present and reruns MarkCommercials for a specific PID. Can this be included in a new release of etv-comskip?
  • Sep 22, 2009
    issue 26 (Commercials are not excluded during export) reported by gheadley   -   What steps will reproduce the problem? 1. Set a recording 2. Instruct EyeTV to export to AppleTV upon recording completion 3. If I instead manually export to AppleTV later, commercials are removed. What is the expected output? What do you see instead? Commercials to be removed from the output video. Instead, exported video still contains commercials, although they are marked properly inside EyeTV. What version of the product are you using? On what operating system? ETVComskip-1.0.3-10.6.dmg on 10.6.1 with EyeTV 3.1.3b1 (5275) Please provide any additional information below. I'm still trying to fully understand the way EyeTV handles scripting requests, but I feel as though EyeTV is running the export script to AppleTV (and iTunes) prior to the markers being added to the recording. Does this make sense? So when a recording completes, it first starts the export and moments later sends the recording to markcommercials where it is properly marked. Any assistance is appreciated.
    What steps will reproduce the problem? 1. Set a recording 2. Instruct EyeTV to export to AppleTV upon recording completion 3. If I instead manually export to AppleTV later, commercials are removed. What is the expected output? What do you see instead? Commercials to be removed from the output video. Instead, exported video still contains commercials, although they are marked properly inside EyeTV. What version of the product are you using? On what operating system? ETVComskip-1.0.3-10.6.dmg on 10.6.1 with EyeTV 3.1.3b1 (5275) Please provide any additional information below. I'm still trying to fully understand the way EyeTV handles scripting requests, but I feel as though EyeTV is running the export script to AppleTV (and iTunes) prior to the markers being added to the recording. Does this make sense? So when a recording completes, it first starts the export and moments later sends the recording to markcommercials where it is properly marked. Any assistance is appreciated.
  • Sep 21, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by nerdbaby   -   It seems to grow at about 10ish MB per hour. I'm running 10.6.1 SL, with etv-comskip v1.0.3.
    It seems to grow at about 10ish MB per hour. I'm running 10.6.1 SL, with etv-comskip v1.0.3.
  • Sep 20, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by nowalmart   -   I am seeing the same issue under 10.6.1 with v1.0.3 You can watch Activity Monitor for a while and watch the Real Memory grow before your eyes.
    I am seeing the same issue under 10.6.1 with v1.0.3 You can watch Activity Monitor for a while and watch the Real Memory grow before your eyes.
  • Sep 16, 2009
    issue 19 (Export stalls) commented on by spinespecialist   -   Manually compacting the file (which removes the markers) seems to markedly improve the reliability of the Exports. I once saw a script for auto-compact. Seems like this could be run BEFORE they are auto-exported and we'd have a reasonable solution to this problem.
    Manually compacting the file (which removes the markers) seems to markedly improve the reliability of the Exports. I once saw a script for auto-compact. Seems like this could be run BEFORE they are auto-exported and we'd have a reasonable solution to this problem.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) Status changed by jon.christopher   -   The 10.6 version is posted. Thanks to @nowalmart!
    Status: Fixed
    The 10.6 version is posted. Thanks to @nowalmart!
    Status: Fixed
  • Aug 31, 2009
    ETVComskip-1.0.3-10.6.dmg (Version 1.0.3 for Snow Leopard (10.6)) file uploaded by jon.christopher   -  
    Labels: Featured Type-Installer OpSys-OSX
    Labels: Featured Type-Installer OpSys-OSX
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by nowalmart   -   Did not need to change anything. Will email you.
    Did not need to change anything. Will email you.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by jon.christopher   -   @nowalmart: Thanks. Did you have to change anything, or did you just type "make dmg". If the latter, could could you email me the .dmg file at jon.christopher at gmail dot com, and I'll post it.
    @nowalmart: Thanks. Did you have to change anything, or did you just type "make dmg". If the latter, could could you email me the .dmg file at jon.christopher at gmail dot com, and I'll post it.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by nowalmart   -   Looks like it worked on a third recording. I just moved this week (and have a new cable provider), so it is difficult for me to say if the missing PID issue is a result of Snow Leopard or something different in my set-up. In the meantime I do have a .DMG that seems to work on Snow Leopard. I was unable to compile a newer version of comskip - that was simply beyond my knowledge/ability.
    Looks like it worked on a third recording. I just moved this week (and have a new cable provider), so it is difficult for me to say if the missing PID issue is a result of Snow Leopard or something different in my set-up. In the meantime I do have a .DMG that seems to work on Snow Leopard. I was unable to compile a newer version of comskip - that was simply beyond my knowledge/ability.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by jon.christopher   -   @nowalmart: Hey, thanks. The no PID issue may be a duplicate of Bug #17. I keep meaning to update the comskip source itself, which may have fixed this issue, but the last time I tried it didn't compile cleanly and I haven't had time to fix it.
    @nowalmart: Hey, thanks. The no PID issue may be a duplicate of Bug #17. I keep meaning to update the comskip source itself, which may have fixed this issue, but the last time I tried it didn't compile cleanly and I haven't had time to fix it.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by nowalmart   -   Everything works fine except for ComSkip itself - it keeps throwing up errors that it cannot find a video PID. Will work on it later today.
    Everything works fine except for ComSkip itself - it keeps throwing up errors that it cannot find a video PID. Will work on it later today.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by nowalmart   -   I just recompiled under Snow Leopard and then restarted. No errors on reboot (as I was getting before). Making a recording now to test and make sure it is actually working.
    I just recompiled under Snow Leopard and then restarted. No errors on reboot (as I was getting before). Making a recording now to test and make sure it is actually working.
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by jon.christopher   -   I don't have Snow Leopard yet, so if there are any developers who do and want this issue fixed, please contact me.
    I don't have Snow Leopard yet, so if there are any developers who do and want this issue fixed, please contact me.
  • Aug 31, 2009
    issue 25 (Not Snow Leopard compatible) changed by jon.christopher   -  
    Status: Duplicate
    Status: Duplicate
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by jon.christopher   -   Issue 25 has been merged into this issue.
    Issue 25 has been merged into this issue.
  • Aug 31, 2009
    issue 24 (ComSkip doesn't work with Snow Leapord) changed by jon.christopher   -  
    Status: Duplicate
    Status: Duplicate
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by jon.christopher   -   Issue 24 has been merged into this issue.
    Issue 24 has been merged into this issue.
  • Aug 31, 2009
    issue 21 (Comskip fails to initalize) changed by jon.christopher   -  
    Status: Duplicate
    Status: Duplicate
  • Aug 31, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) commented on by jon.christopher   -   Issue 21 has been merged into this issue.
    Issue 21 has been merged into this issue.
  • Aug 31, 2009
    issue 21 (Comskip fails to initalize) commented on by jon.christopher   -   Issue 23 has been merged into this issue.
    Issue 23 has been merged into this issue.
  • Aug 31, 2009
    issue 23 (Comskipper does not work on Snow Leopard) changed by jon.christopher   -  
    Status: Duplicate
    Status: Duplicate
  • Aug 31, 2009
    issue 25 (Not Snow Leopard compatible) commented on by jlbr...@bordo.com.au   -   Oops. Sorry. Didn't read the previous issue.
    Oops. Sorry. Didn't read the previous issue.
  • Aug 31, 2009
    issue 25 (Not Snow Leopard compatible) reported by jlbr...@bordo.com.au   -   Upgrade to Snow Leopard and a dialog appears at startup asking to terminate etv-comskipper. Others have reported the issue at: http://forums.elgato.com/viewtopic.php?f=91&t=5958 James.
    Upgrade to Snow Leopard and a dialog appears at startup asking to terminate etv-comskipper. Others have reported the issue at: http://forums.elgato.com/viewtopic.php?f=91&t=5958 James.
  • Aug 30, 2009
    issue 21 (Comskip fails to initalize) commented on by david.blanchard   -   I can confirm this error. I just upgraded a box to 10.6 from 10.5.8 and got the error too.
    I can confirm this error. I just upgraded a box to 10.6 from 10.5.8 and got the error too.
  • Aug 29, 2009
    issue 24 (ComSkip doesn't work with Snow Leapord) reported by MuadDib001   -   What steps will reproduce the problem? 1. Install Snow Leapord 2. Reboot What is the expected output? What do you see instead? Expected it to load. It crashes. What version of the product are you using? On what operating system? Latest and greatest as of this date (29 Aug 2009), and just installed Snow Leapord. Please provide any additional information below. Doesn't seem to be compatible.
    What steps will reproduce the problem? 1. Install Snow Leapord 2. Reboot What is the expected output? What do you see instead? Expected it to load. It crashes. What version of the product are you using? On what operating system? Latest and greatest as of this date (29 Aug 2009), and just installed Snow Leapord. Please provide any additional information below. Doesn't seem to be compatible.
  • Aug 28, 2009
    issue 23 (Comskipper does not work on Snow Leopard) reported by spyker3292   -   What steps will reproduce the problem? 1. Launch Comskipper or have it as a login item What is the expected output? What do you see instead? Expect: Nothing, since it always runs in the background. What happens: An error pops up and it gives me the option to terminate Comskipper. What version of the product are you using? On what operating system? The current version on Mac OS X 10.6. Please provide any additional information below. The error is: "ComSkipper Error An unexpected error has occurred during execution of the main script ValueError: Unknown typestr"
    What steps will reproduce the problem? 1. Launch Comskipper or have it as a login item What is the expected output? What do you see instead? Expect: Nothing, since it always runs in the background. What happens: An error pops up and it gives me the option to terminate Comskipper. What version of the product are you using? On what operating system? The current version on Mac OS X 10.6. Please provide any additional information below. The error is: "ComSkipper Error An unexpected error has occurred during execution of the main script ValueError: Unknown typestr"
  • Aug 28, 2009
    issue 22 (ETVcomskip crashes under Snow Leopard) reported by rebeccam   -   What steps will reproduce the problem? 1. Upon booting into Snow Leopard, when ComSkip tries to launch, an error is produced 2. 3. What is the expected output? What do you see instead? It is expected that Comskip will run in the background, instead it launches an error dialog that says: ComSkipper Error An unexpected error has occurred during execution of the main script ValueError: Unknown typestr What version of the product are you using? On what operating system? I am running version 1.0.3-10.5 Please provide any additional information below. The relevant console log is attached.
    What steps will reproduce the problem? 1. Upon booting into Snow Leopard, when ComSkip tries to launch, an error is produced 2. 3. What is the expected output? What do you see instead? It is expected that Comskip will run in the background, instead it launches an error dialog that says: ComSkipper Error An unexpected error has occurred during execution of the main script ValueError: Unknown typestr What version of the product are you using? On what operating system? I am running version 1.0.3-10.5 Please provide any additional information below. The relevant console log is attached.
  • Aug 15, 2009
    issue 21 (Comskip fails to initalize) reported by AppleIIguy   -   What steps will reproduce the problem? 1. Upgrade to Snow Leopard 10.6 2. Boot Machine 3. Get Error 8/15/09 3:24:16 PM com.apple.launchd.peruser.501[177] ([0x0-0x22022].org.pythonmac.unspecified.ComSkipper[254]) Exited with exit code: 255 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] Traceback (most recent call last): 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "/Library/Application Support/ETVComskip/ComSkipper.app/Contents/Resources/__boot__.py", line 31, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] _run('ComSkipper.py') 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "/Library/Application Support/ETVComskip/ComSkipper.app/Contents/Resources/__boot__.py", line 28, in _run 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] execfile(path, globals(), globals()) 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "/Library/Application Support/ETVComskip/ComSkipper.app/Contents/Resources/ComSkipper.py", line 19, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] import AppKit 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "AppKit/__init__.pyc", line 10, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "Foundation/__init__.pyc", line 10, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "CoreFoundation/__init__.pyc", line 17, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "objc/_bridgesupport.pyc", line 129, in initFrameworkWrapper 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "objc/_bridgesupport.pyc", line 53, in _parseBridgeSupport 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] ValueError: Unknown typestr 8/15/09 3:30:08 PM ComSkipper[493] ComSkipper Error 8/15/09 3:30:08 PM ComSkipper[493] ComSkipper Error An unexpected error has occurred during execution of the main script ValueError: Unknown typestr 8/15/09 3:30:56 PM com.apple.launchd.peruser.501[177] ([0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493]) Exited with exit code: 255 Macbook Core 2 Duo 4 Gb Ram Mac OS X 10.6 (10A432)
    What steps will reproduce the problem? 1. Upgrade to Snow Leopard 10.6 2. Boot Machine 3. Get Error 8/15/09 3:24:16 PM com.apple.launchd.peruser.501[177] ([0x0-0x22022].org.pythonmac.unspecified.ComSkipper[254]) Exited with exit code: 255 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] Traceback (most recent call last): 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "/Library/Application Support/ETVComskip/ComSkipper.app/Contents/Resources/__boot__.py", line 31, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] _run('ComSkipper.py') 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "/Library/Application Support/ETVComskip/ComSkipper.app/Contents/Resources/__boot__.py", line 28, in _run 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] execfile(path, globals(), globals()) 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "/Library/Application Support/ETVComskip/ComSkipper.app/Contents/Resources/ComSkipper.py", line 19, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] import AppKit 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "AppKit/__init__.pyc", line 10, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "Foundation/__init__.pyc", line 10, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "CoreFoundation/__init__.pyc", line 17, in <module> 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "objc/_bridgesupport.pyc", line 129, in initFrameworkWrapper 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] File "objc/_bridgesupport.pyc", line 53, in _parseBridgeSupport 8/15/09 3:30:08 PM [0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493] ValueError: Unknown typestr 8/15/09 3:30:08 PM ComSkipper[493] ComSkipper Error 8/15/09 3:30:08 PM ComSkipper[493] ComSkipper Error An unexpected error has occurred during execution of the main script ValueError: Unknown typestr 8/15/09 3:30:56 PM com.apple.launchd.peruser.501[177] ([0x0-0x5b05b].org.pythonmac.unspecified.ComSkipper[493]) Exited with exit code: 255 Macbook Core 2 Duo 4 Gb Ram Mac OS X 10.6 (10A432)
  • Aug 02, 2009
    issue 20 (Comskipper consuming large amounts of RAM?) commented on by ktuluz   -   same issue here. I have to manually kill (force quit) comskipper after a few days. using large amounts of ram ? not flushing ?
    same issue here. I have to manually kill (force quit) comskipper after a few days. using large amounts of ram ? not flushing ?
  • Jul 26, 2009
    issue 7 (No video pid found return from "comskip": 3) commented on by d...@danethomas.net   -   I'm also seeing this issue. Any chance we could see an update mac port of the current version of comskip so we can get this fixed? Cheers.
    I'm also seeing this issue. Any chance we could see an update mac port of the current version of comskip so we can get this fixed? Cheers.
  • May 24, 2009
    issue 18 (Not working - No video pid found return from "comskip": 3) commented on by techydude   -   i am also experiencing this problem. i'm trying the batch marking process as described in the readme/readme-eyetv3. the instructions say EyeTV should not be running while doing this, so i close EyeTV, run '.../MarkCommercials all', which launches EyeTV again. i don't get the prompt to press enter as suggested (which i assume is my cue to close EyeTV again). but whether i do or don't close EyeTV again while 'MarkCommercials all' is running, i get the errors described above, and no commercials marked in the recordings.
    i am also experiencing this problem. i'm trying the batch marking process as described in the readme/readme-eyetv3. the instructions say EyeTV should not be running while doing this, so i close EyeTV, run '.../MarkCommercials all', which launches EyeTV again. i don't get the prompt to press enter as suggested (which i assume is my cue to close EyeTV again). but whether i do or don't close EyeTV again while 'MarkCommercials all' is running, i get the errors described above, and no commercials marked in the recordings.
 
Hosted by Google Code