search

mackworth / cTiVo

TiVo Show Downloads for MacOS
220 stars 36 forks source link

Downloading shows fails to complete #74

Closed RevChas closed 9 years ago

RevChas commented 9 years ago

I have been trying to download shows using both cTiVo 2.3.1 and 2.4.0b3. In both cases cTiVo tries to download the show, but it appears to fail at the end of the download.

You can get a copy of my 2.3.1 configuration file at this link:

http://www.sorrydave.org/ctivo/com.cTiVo.cTiVo.plist-v2.3.1

The log file from the download using version 2.3.1 is at this link:

http://www.sorrydave.org/ctivo/log-736980.txt

The configuration file used with cTiVo 2.4.0b3 is at this link:

http://www.sorrydave.org/ctivo/com.cTiVo.cTiVo.plist-v2.4.0b3

The log file from the download attempt is at this link:

http://www.sorrydave.org/ctivo/com.cTiVo.cTiVo_2014-11-26_04-16.log-v2.4.0b3

Please let me know if there's any other help I can give you with this bug.

mackworth commented 9 years ago

Sorry it's not working well for you. First, I take it from "download shows" that this is happening for more than just the one DailyShow/Cleese episode in the logs? Second, you're getting errors directly from Handbrake immediately upon launch, that it's missing CSS symbols, and then crashes with a uncaught signal 11. So, I'll bet that if you switch to mencoder (e.g. AppleTV encoder), then you'd be ok.

I don't know why Handbrake would crash on you like this on startup. I don't think it's running another copy, as we call our copy by full path name. Do you know if you have another copy installed, could it have changed default configurations? Maybe it's loading the CSS decoder from somewhere else?

hb_init: starting libhb thread HandBrake 0.9.9 (2013051800) - Darwin x86_64 - http://handbrake.fr ... libdvdnav: Using dvdnav version 4.1.3 libdvdread: Missing symbols in libdvdcss.2.dylib, this shouldn't happen ! libdvdread: Using libdvdcss version for DVD access

mackworth commented 9 years ago

closed due to lack of response

vtrandal commented 9 years ago

I have downloads failing a lot, but I have been more interested in trying to build the latest cTiVo. I might open a case on code signing and crashlytics soon.

mackworth commented 9 years ago

Have you followed the instructions in appDelegate re crashlytics? If you either create the two files (or remove crashlytics entirely, as you don't really need it for your own use), it should work. Note that I fixed one hardwired reference in this new release.

vtrandal commented 9 years ago

Which two files are you referring to? I see on one reference to MTCrashlyticsKey.m in cTiVo:MTAppDelegate.m. What is a hardwired reference? I'm not new to software development but I am new to Mac development.

Crashlytics is now part of Fabric. Seems I need a Fabric account to get Crashlytics for Mac. Who knows how long that will take?

I tried commenting out the reference to MTCrashlyticsKey.m in MTAppDelegate.m with bad results indicating it cannot be an empty file. I have no idea what goes in it.

So either way it seems I'm stuck again and cannot build cTiVo. Not sure where to get Crashlytics and not sure how to remove Crashlytics.

As for code signing paying the $99 Mac developer fee seems the best way to build cTiVo 2.4 and a bunch of other Xcode projects on GitHub that want that.

I really want to get over these issues and start working on the latest cTiVo code. I was able to build and run master1 and it is nice! (except for lots of downloads that fail)

Thanks!

Vincent Randal Longmont, Colorado

On Sat, Dec 6, 2014 at 3:35 PM, Hugh Mackworth notifications@github.com wrote:

Have you followed the instructions in appDelegate re crashlytics? If you either create the two files (or remove crashlytics entirely, as you don't really need it for your own use), it should work. Note that I fixed one hardwired reference in this new release.

— Reply to this email directly or view it on GitHub https://github.com/dscottbuch/cTiVo/issues/74#issuecomment-65916995.

vtrandal commented 9 years ago

Now that I've whined and complained sufficiently, the nice comment following Crashlytics startWithAPIKey: in MTAppDelegate.m is starting to make some sense. So I will give that a try. Wish me luck!

Vincent Randal Longmont, Colorado

On Sat, Dec 6, 2014 at 4:50 PM, Vincent Randal vtrandal@gmail.com wrote:

Which two files are you referring to? I see on one reference to MTCrashlyticsKey.m in cTiVo:MTAppDelegate.m. What is a hardwired reference? I'm not new to software development but I am new to Mac development.

Crashlytics is now part of Fabric. Seems I need a Fabric account to get Crashlytics for Mac. Who knows how long that will take?

I tried commenting out the reference to MTCrashlyticsKey.m in MTAppDelegate.m with bad results indicating it cannot be an empty file. I have no idea what goes in it.

So either way it seems I'm stuck again and cannot build cTiVo. Not sure where to get Crashlytics and not sure how to remove Crashlytics.

As for code signing paying the $99 Mac developer fee seems the best way to build cTiVo 2.4 and a bunch of other Xcode projects on GitHub that want that.

I really want to get over these issues and start working on the latest cTiVo code. I was able to build and run master1 and it is nice! (except for lots of downloads that fail)

Thanks!

Vincent Randal Longmont, Colorado

On Sat, Dec 6, 2014 at 3:35 PM, Hugh Mackworth notifications@github.com wrote:

Have you followed the instructions in appDelegate re crashlytics? If you either create the two files (or remove crashlytics entirely, as you don't really need it for your own use), it should work. Note that I fixed one hardwired reference in this new release.

— Reply to this email directly or view it on GitHub https://github.com/dscottbuch/cTiVo/issues/74#issuecomment-65916995.

mackworth commented 9 years ago

To walk through removing crashlytics, remove lines 119-127 in MTAppDelegate, the crashlytics framework from the file list on the left, and then click on the cTiVo project, then Targets>cTiVo, then Build Phases, then hit the x at the far right of Run Script (to remove the crashlytics script).

Then still in Targets>cTivo, go to General at the top and click on None for the Signing, and you should be able to compile.

mackworth commented 9 years ago

Also, I'm curious; what would you be working on in the code?

vtrandal commented 9 years ago

A codec

Vincent Randal Longmont, Colorado

On Sat, Dec 6, 2014 at 5:41 PM, Hugh Mackworth notifications@github.com wrote:

Also, I'm curious; what would you be working on in the code?

— Reply to this email directly or view it on GitHub https://github.com/dscottbuch/cTiVo/issues/74#issuecomment-65921398.

mackworth commented 9 years ago

Ok, let me just point out the Edit Formats command. You should be able to test out and use any codec without Xcode (other than writing the codec itself). See docs in https://github.com/dscottbuch/cTiVo/wiki/Advanced-Topics. (Second topic)

vtrandal commented 9 years ago

thank you

Vincent Randal Longmont, Colorado

On Sat, Dec 6, 2014 at 8:18 PM, Hugh Mackworth notifications@github.com wrote:

Ok, let me just point out the Edit Zfornats command. You should be able to test out and use any codec without Xcode (other than writing the codec itself). See docs in https://github.com/dscottbuch/cTiVo/wiki/Advanced-Topics. (Second topic)

— Reply to this email directly or view it on GitHub https://github.com/dscottbuch/cTiVo/issues/74#issuecomment-65924803.