Tweet
Re: Asset UPnP For OSX (MAC)
Hi amosh,
my opinion about EyeTV - especially regarding communication between any "iDevice" as a remote client and it's "server component" on a Mac - is different from your approach. This may be caused that I also keep a large amount of movies played once on TV saved for future viewing, and I have found that EyeTV does a suitable job in recording, cutting out some unwanted commercials and finally archiving the material, together with some meta data also transmitted via TV. Especially compared to the method I used before (recording on a dedicated hard disk satellite receiver, then transferred to a PC, then converted into DVD format and afterwards cut to the "clean" movie and finally converted into a H.264 mp4-format was somewhat more time consuming ;-). But that's personal preferences.
Anyhow, I was now quite surprised when I changed to the actual beta of Asset [0.12 (1)] after removing it's previous version: At the time of installing it EyeTV was up and running, and EyeConnect was not disabled at this time. And - guess what - the newly installed Asset started without any error. I thought that either Mr. Spoon found a solution for this problem or it was removed by Elgato, since they recently released many updates [EyeTV on the Mac is 3.6.4 (7306), EyeTV on iPad is actually 2.0 (814) and EyeTV netstream is now 2.0 (412)]. To ensure my opinion I did some reboots, but still no problem with Asset. But ...
As there was pointed out somewhere that in earlier versions Asset came up only if Twonky was running, I wanted to be sure that Twonky was "disabled" (meaning that it still could be installed on the Mac, but it should not be auto-started within the user profile as well as that it should not be visible as a UPnP server). And: Both of these conditions were fulfilled. As I found out that Twonky was still installed at this time, I thought that uninstalling it - at least temporarily - could ensure that Twonky could under no circumstances be involved. So I did not simply remove the program from the programs folder, but had an uninstaller used to find if any dependencies were still existing in some other folder(s). And at this time the authorisation of an admin was requested for uninstalling the complete stuff. And, after quitting Asset and restarting it - the well known error message was shown.
For the first moment I thought that this was another proof that EyeConnect was the reason that Asset could not start correctly. So I used the Uninstall Programm supplied by Elgato to remove EyeConnect. As expected, the next try to start Asset was successful. But I did not give up, enabled EyeConnect within EyeTV, connected an iPod to EyeTV, rebooted my Mac thus auto-restarting EyeTV as well as Asset, and: Asset started as expected. Another try - I shut down EyeTV and Asset and did another reboot. Than initiated the start of EyeTV on the Mac by calling it from EyeTV on an iPod, and then starting Asset: No problems with Asset.
This leads me actually to the following opinion:
- Twonky, if not uninstalled properly, builds, although "not fully" active, something like a bridge that does not harm Asset,
- EyeConnect, if Twonky is still present, does not allow Asset to start (it seems to use the same port as Asset if Twonky is present),
- EyeConnect, if Twonky is not present, uses a different port thus allowing Asset to successfully lock to it's desired port.
I do not have enough technical experience or suitable tools to ensure that this theory is correct, but I think that many of us may have tried Twonky as well and may have only removed the program itself, so there might be the prestarted thread of Twonky still active thus preventing the correct start of Asset.
If I remember correctly, you had Twonky installed as well. If you could do a correct re-install, than a correct uninstall using something like "AppCleaner" and afterwards enable EyeConnect within EyeTV and then see whether Asset comes up correctly, this might be helpful to clarify things.
If something changes regarding EyeConnect I will keep you informed accordingly.
Regards,
Niko
Hi amosh,
my opinion about EyeTV - especially regarding communication between any "iDevice" as a remote client and it's "server component" on a Mac - is different from your approach. This may be caused that I also keep a large amount of movies played once on TV saved for future viewing, and I have found that EyeTV does a suitable job in recording, cutting out some unwanted commercials and finally archiving the material, together with some meta data also transmitted via TV. Especially compared to the method I used before (recording on a dedicated hard disk satellite receiver, then transferred to a PC, then converted into DVD format and afterwards cut to the "clean" movie and finally converted into a H.264 mp4-format was somewhat more time consuming ;-). But that's personal preferences.
Anyhow, I was now quite surprised when I changed to the actual beta of Asset [0.12 (1)] after removing it's previous version: At the time of installing it EyeTV was up and running, and EyeConnect was not disabled at this time. And - guess what - the newly installed Asset started without any error. I thought that either Mr. Spoon found a solution for this problem or it was removed by Elgato, since they recently released many updates [EyeTV on the Mac is 3.6.4 (7306), EyeTV on iPad is actually 2.0 (814) and EyeTV netstream is now 2.0 (412)]. To ensure my opinion I did some reboots, but still no problem with Asset. But ...
As there was pointed out somewhere that in earlier versions Asset came up only if Twonky was running, I wanted to be sure that Twonky was "disabled" (meaning that it still could be installed on the Mac, but it should not be auto-started within the user profile as well as that it should not be visible as a UPnP server). And: Both of these conditions were fulfilled. As I found out that Twonky was still installed at this time, I thought that uninstalling it - at least temporarily - could ensure that Twonky could under no circumstances be involved. So I did not simply remove the program from the programs folder, but had an uninstaller used to find if any dependencies were still existing in some other folder(s). And at this time the authorisation of an admin was requested for uninstalling the complete stuff. And, after quitting Asset and restarting it - the well known error message was shown.
For the first moment I thought that this was another proof that EyeConnect was the reason that Asset could not start correctly. So I used the Uninstall Programm supplied by Elgato to remove EyeConnect. As expected, the next try to start Asset was successful. But I did not give up, enabled EyeConnect within EyeTV, connected an iPod to EyeTV, rebooted my Mac thus auto-restarting EyeTV as well as Asset, and: Asset started as expected. Another try - I shut down EyeTV and Asset and did another reboot. Than initiated the start of EyeTV on the Mac by calling it from EyeTV on an iPod, and then starting Asset: No problems with Asset.
This leads me actually to the following opinion:
- Twonky, if not uninstalled properly, builds, although "not fully" active, something like a bridge that does not harm Asset,
- EyeConnect, if Twonky is still present, does not allow Asset to start (it seems to use the same port as Asset if Twonky is present),
- EyeConnect, if Twonky is not present, uses a different port thus allowing Asset to successfully lock to it's desired port.
I do not have enough technical experience or suitable tools to ensure that this theory is correct, but I think that many of us may have tried Twonky as well and may have only removed the program itself, so there might be the prestarted thread of Twonky still active thus preventing the correct start of Asset.
If I remember correctly, you had Twonky installed as well. If you could do a correct re-install, than a correct uninstall using something like "AppCleaner" and afterwards enable EyeConnect within EyeTV and then see whether Asset comes up correctly, this might be helpful to clarify things.
If something changes regarding EyeConnect I will keep you informed accordingly.
Regards,
Niko
Comment