[albertyong88]

I installed PyeTV 1.2, it rocks. However, I have a small request.

EyeTV 3.1 allows EyeTV sharing. I was wondering is it easy to integrate Sharing on PyeTV ?

I have 2 computers, both running EyeTV 3.1 and PyeTV 1.2 on Front row.

They share the same archrive on the NAS driver (it works). I have 2 problems with the computers accessing to the same archrive. When each one updates the archrive, the other doesn't know ... anyway to make them sync ????

I don't know about this. I haven't tried sharing before. Does EyeTV itself work properly if two different computers are writing to the same location? If that works, then PyeTV
should work...it just asks EyeTV for it's list of recordings.

If EyeTV itself doesn't work this way, then PyeTV won't work. It *might* be possible
with some tweaking to get two different EyeTV menus in Front Row, one for each archive, but that would be an awful hack.

eyeTV 3.1 allows sharing. (doesn't mean sharing the same archive). It looks for other shared content from other EyeTV ... So, if you can get PyeTV to get those shared content and play them, it would be great.

[j-christ]

If PyeTV in general could see Shared EyeTV archives it would make things a lot easier for me. I could let my wife's iMac do the recording and comskip-ing and just use the Mac Mini for playback.

I won't be able to do anything about this until Elgato fixes EyeTV. The basic applescript:

Code: Select all

tell application "EyeTV"
   recordings
end tell


which is all that PyeTV uses (and all it can use), doesn't return anything about shared recordings. I've submitted a bug report on it, so we'll se.

[PhyrePhox]

If PyeTV in general could see Shared EyeTV archives it would make things a lot easier for me. I could let my wife's iMac do the recording and comskip-ing and just use the Mac Mini for playback.

I won't be able to do anything about this until Elgato fixes EyeTV. The basic applescript:

Code: Select all

tell application "EyeTV"
   recordings
end tell


which is all that PyeTV uses (and all it can use), doesn't return anything about shared recordings. I've submitted a bug report on it, so we'll se.

Thank you for all your hard work in developing these apps and your willingness to discuss issues and feature requests with me. These two tools made it possible for me to retire a WMC system and replace it with a Mac, and not have my wife throw me out for doing it. If it takes time (or a sea change in the development direction of Elgato or Apple) to add capabilities, I can be patient.

[chefk]

I've submitted a bug report on it, so we'll see.

I'd like to gain this functionality as well--I'm in the same boat, a happy EyeTV, Front Row and PyeTV user with four El Gato tuners and two separate archives of EyeTV recordings. When I'm in the living room, have invoked Front Row, and thanks to the wonderful PyeTV see my first EyeTV archive, I'd love for there to be some way to access my "other" shared EyeTV archive elsewhere on the network.

Here's hoping someone on the El Gato team reaches out to see if this can be implemented or not. It would be a nice enhancement.

[sjk]

I'd love for there to be some way to access my "other" shared EyeTV archive elsewhere on the network.

Possible workaround is to use aliases, unless I'm misunderstanding what you're requesting.

[chefk]

Maybe I just don't know how to do it properly, but I'm talking about this situation: one Mac in the BR with two tuners and its local archive, a second Mac in the LR with two other tuners and its local archive--completely separate systems and archives, if you will, that just happen to be on the same local network and as a result can be shared within the EyeTV software. Problem is, we tend not to control things via the EyeTV interface.

Most of the time we watch EyeTV in the LR via Front Row thanks to the PyeTV plugin--it, however, just finds the LR Mac archive, even if the shared BR archive is loaded. If there were a way to use an alias so that when I'm "in" Front Row in the LR I'll also have access to the BR Mac's archive as well as the LR Mac's archive, that would be great.

[sjk]

If you mount the remote volume (I use AFP) containing your LR EyeTV recordings on the BR, then alias individual .eyetv recordings and/or their archive folders from it into your BR EyeTV Archive, the LR recordings should show up in EyeTV on the BR. Vice versa for the LR EyeTV Archive to access the BR recordings with aliases. If a remote volume isn't available any aliases to recordings on it are ignored (which can be useful). Once that's working with EyeTV I'd think your Front Row playback will work, too, but I can't test it.

There's no need for EyeTV Sharing functionality to be enabled with that archive sharing method. Btw, since you're using multiple tuners how does EyeTV handle the Live TV Buffer package in any EyeTV Archive folders being simultaneously accessed? Are there separate packages created for each tuner instance?

The default EyeTV Archive folder on my iMac G5 (which doesn't have a recording device) only contains aliases to other recordings/folders on different local/remote volumes, creating a unified view of whichever collection of recordings for EyeTV (and EyeHome) to currently access. Sometimes I'll temporarily switch to a specific EyeTV Archive on a local volume, e.g. one containing recordings for batch exporting, infrequently enough that quitting/relaunching EyeTV after switching isn't too much trouble although I wish it wasn't necessary.

I've haven't used EyeTV playlists, nor bothered to try deleting the duplicate default Smart Playlists for every aliased EyeTV Archive folder. I can use Spotlight to generate a simple list of recordings, e.g. by running mdfind "kMDItemKind = 'EyeTV Recording'" in Terminal.

I've got too many recordings (especially when those with deleted .mpg files are included) to not to be using multiple archives, made much more manageable with aliases.

[PhyrePhox]

If you mount the remote volume (I use AFP) containing your LR EyeTV recordings on the BR, then alias individual .eyetv recordings and/or their archive folders from it into your BR EyeTV Archive, the LR recordings should show up in EyeTV on the BR. Vice versa for the LR EyeTV Archive to access the BR recordings with aliases. If a remote volume isn't available any aliases to recordings on it are ignored (which can be useful). Once that's working with EyeTV I'd think your Front Row playback will work, too, but I can't test it.

There's no need for EyeTV Sharing functionality to be enabled with that archive sharing method. Btw, since you're using multiple tuners how does EyeTV handle the Live TV Buffer package in any EyeTV Archive folders being simultaneously accessed? Are there separate packages created for each tuner instance?

The default EyeTV Archive folder on my iMac G5 (which doesn't have a recording device) only contains aliases to other recordings/folders on different local/remote volumes, creating a unified view of whichever collection of recordings for EyeTV (and EyeHome) to currently access. Sometimes I'll temporarily switch to a specific EyeTV Archive on a local volume, e.g. one containing recordings for batch exporting, infrequently enough that quitting/relaunching EyeTV after switching isn't too much trouble although I wish it wasn't necessary.

I've haven't used EyeTV playlists, nor bothered to try deleting the duplicate default Smart Playlists for every aliased EyeTV Archive folder. I can use Spotlight to generate a simple list of recordings, e.g. by running mdfind "kMDItemKind = 'EyeTV Recording'" in Terminal.

I've got too many recordings (especially when those with deleted .mpg files are included) to not to be using multiple archives, made much more manageable with aliases.

OK, I moved the drive that contains the EyeTV archive and the tuner from the Mac mini to the iMac, and then shared the drive via AFP and mounted it on the mini. As the volume name was the same, EyeTV found the archive immediately without having to modify the preferences.

When the iMac records a new show, it doesn't automagically appear in the Mac mini's archive; I must exit and restart EyeTV on the mini. From what I've read elsewhere, EyeTV only parses the archive at launch, and then only adds new recordings as it creates them. Creating links or aliases to recordings on a networked volume doesn't change that. I'm trying to avoid having to constantly manage this.

Didn't someone say something about a modification to PyeTV that would make it quit EyeTV when exiting FrontRow?

[chefk]

well, right now it quits the open window, but the app itself is still open.

Once that's working with EyeTV I'd think your Front Row playback will work, too, but I can't test it.

sjk, I just did your alias method, and after a restart it does pick up the second archive and does show up within FR using PyeTV--so thank you. So the issue is, like PhyrePhox mentioned, to come up with something a little more manageable and seamless than having to close and restart EyeTV each day in order to pick up new recordings. But thank you again...

[sjk]

From what I've read elsewhere, EyeTV only parses the archive at launch, and then only adds new recordings as it creates them. Creating links or aliases to recordings on a networked volume doesn't change that.

Right. I'd briefly thought about that limitation, then just as quickly forgot to mention it.

I just did your alias method, and after a restart it does pick up the second archive and does show up within FR using PyeTV--so thank you.

You're welcome. Thanks for letting us know it worked.

So the issue is, like PhyrePhox mentioned, to come up with something a little more manageable and seamless than having to close and restart EyeTV each day in order to pick up new recordings.

Since opening recording packages makes them appear in the Recordings list it should be possible to trigger that for recordings newly added to an archive by copying or via aliases, somehow inhibiting player windows from opening (maybe difficult or impossible) or automatically closing them (possibly with AppleScript). I sometimes do that manually so EyeTV can temporarily access recordings (mostly for exporting) stored in inactive archive locations, wanting them to disappear from the Recording list after the next relaunch. You'd probably be adding them to and opening them from an active archive so they'll appear in the Recordings both immediately and after relaunching.

[PhyrePhox]

From what I've read elsewhere, EyeTV only parses the archive at launch, and then only adds new recordings as it creates them. Creating links or aliases to recordings on a networked volume doesn't change that.

Right. I'd briefly thought about that limitation, then just as quickly forgot to mention it.

I just did your alias method, and after a restart it does pick up the second archive and does show up within FR using PyeTV--so thank you.

You're welcome. Thanks for letting us know it worked.

So the issue is, like PhyrePhox mentioned, to come up with something a little more manageable and seamless than having to close and restart EyeTV each day in order to pick up new recordings.

Since opening recording packages makes them appear in the Recordings list it should be possible to trigger that for recordings newly added to an archive by copying or via aliases, somehow inhibiting player windows from opening (maybe difficult or impossible) or automatically closing them (possibly with AppleScript). I sometimes do that manually so EyeTV can temporarily access recordings (mostly for exporting) stored in inactive archive locations, wanting them to disappear from the Recording list after the next relaunch. You'd probably be adding them to and opening them from an active archive so they'll appear in the Recordings both immediately and after relaunching.

SJK, I didn't say thanks earlier, but I do appreciate this interim solution. My wife can sort out exiting EyeTV and relaunching; since the recording is happening on another machine, we can exit and relaunch EyeTV on the mini without concern.

Considering we are working well outside of the design intentions of both EyeTV and FrontRow, it's terrific that we have this much 10' functionality.

[sjk]

I didn't say thanks earlier, but I do appreciate this interim solution.

You're welcome, though just acknowledging my posts can suffice as an implied thanks.

Glad you're at least partly satisfied with some workaround solutions. Of course easier and more elegant ways to accomplish things is always desirable.

[mac37205]

Thank-you j-christ for an amazing plugin! PyeTV provides a simple yet elegant interface that allows my wife and son to view their favorite recordings without my intervention.

My opinion is that the date in each episode list is unnecessary for two reasons. First, the date of each (selected) episode is also provided in the lower left. Second, the title of each episode is more important for series that take months (or years) to compile. For this reason, I made a modification to the series list code (EpisodeAndDate) from "date" + "episode" to only "episode" (see attachment below).

Would it be possible to either change or have the option to modify the episode list from "sort by (recorded) date" to "sort by title", much like the option in the EyeTV program interface? I have episodes that are listed as "(SeriesEpisode) Title"; for example, (2-21) Meet the Grandparents. This way, it is much easier to find episodes that are watched in the order of episodes, rather than of date recorded. Just icing on the cake!

[chicowoodhill]

PROBLEM: FrontRow crashes when launching EyeTV

Hi - I first posted this in the software section but chefk suggested I look here. I just reinstalled PyeTV 1.2 but it didn't solve the problem.

On my machine, FrontRow always crashes when it tries to perform any action that requires it to launch EyeTV. Here's the sequence:

Enter FrontRow (using either Apple Remote or keyboard).
The top menu item is "EyeTV >"
Select "EyeTV>": The next menu contains "Recordings>, Channels>, Program Guide>"
Select ANY of those three, up comes a screen that says "Launching EyeTV..."

BOOM. Within a few seconds, FrontRow quits unexpectedly, displaying the error window:
"The Application Front Row quit unexpectedly", followed by all the system error info.

Front Row does NOT crash when accessing any menu items other than EyeTV ( such as movies, music, etc.)

Any help for this?

My system:
FrontRow 2.1.6
PyeTv 1.2
EyeTV 3.1 4513
MacBook Pro 2.4 Ghz Intel Core 2 Duo
10.5.5

Thanks in advance for any assistance....Chico

chicowoodhill
Level 1

Posts: 2
Joined: Today, 12:46 pm

[mattachu]

Hey and thanks for this nice piece of work.
I am testing it for the moment and have some strange behaviour.
Starting FrontRow and from there EyeTv for the first time seams to be fairly slow (perhaps caused by EyeTv starting), then being in the EyeTv Menu I cannot navigate up and down there. Pressing the Menu Button brings me back. Going into the menu for the second time allows me to navigate but switching into EyeTv shows the running programm with no sound or the main full screen menu of EyeTv with no option but pressing menu to go back to front row. Going back again to FrontRow show the "rotating wheel" until I press Menu for another time. Then stepping into EyeTv again lets me navigate through everything as normal.
System is an iMac c2d 2.4 / 4GB /320GB with 10.5.2 an EyeTv 2.5.2 (3304). Any help is greatly appreciated. Karsten

I haven't tested with EyeTV2 for a while, but it should work. Best results are to make sure EyeTV is started before Front Row. That's not a problem for me b/c I leave EyeTV running all the time, and it's a login item.

It sounds like you might be getting some sort of hang-ups waiting for EyeTV to respond to apple events.

I, too, have noticed that when returning from EyeTV to Front Row sometimes just leaves me at the blank pinweel screen until I press menu again. I'm not sure why that is; so far I've just been living with it.

hi there,

i'm running front row automatically at login, but i have the same problem as above, that when eyetv starts (by going into the eyetv menu in front row put there by pyetv) it steals away the apple remote and i can no longer control front row with it.

as you said above, is eyetv is already running before front row is launched, i don't have this problem. i've tried starting both eyetv and front row at login, but eyetv takes longer to load and eventually steals remote control when it finishes loading.

does anyone have an idea how to stop this happening, or should i just start eyetv at login and go into front row later? this is a bit less elegant!

cheers,
matt

[chicowoodhill]

PROBLEM: FrontRow crashes when launching EyeTV

Hi - I first posted this in the software section but chefk suggested I look here. I just reinstalled PyeTV 1.2 but it didn't solve the problem.

On my machine, FrontRow always crashes when it tries to perform any action that requires it to launch EyeTV. Here's the sequence:

I found the problem, I think. For others who may be searching for a solution to the same problem:

I had placed EyeTV in a subfolder within the applications folder (in my case it was called "Video"). I moved EyeTV back to the main applications folder and Front Row stopped crashing when it tried to open EyeTV via PyeTV.

I usually only keep Apple apps in the Applications folder, and keep everything else organized in sub-folders. But in this case it looks like EyeTV must reside there as well.

[charlesa]

I upgraded EyeTV to 3.1.1 earlier this afternoon and found PyeTV to be unusable.

Observed behavior included:

• EyeTV windows not going to fullscreen when selected via Play or Restart from PyeTV
• EyeTV thinking window content was paused when it was playing (always displays "play" icon in upper corner.
• "Play" button on Apple remote briefly pauses screen, but then play toggles back on (if started from within Front Row).
• Closing a window that PyeTV had launched causes that window to immediately reopen.

Has anyone else observed similar behavior? For the time being, I've downgraded to 3.1 so I don't feel like I'm wrestling with the software.

[safri]

Yup, same problems with 3.1.1. here.... Have to downgrade too.

[teddyb]

Yes after 3.1.1 update, Blinking starts when eyetv channel is opened from pyetv. Anyone got fix for this or do I have to downgrade too? Memory leak seems to be fixed so it is quite a shame to revert back to earlier versions...

-Teemu

[chicowoodhill]

It might be a good idea to post this as an issue at the PyeTV developement site:

http://code.google.com/p/pyetv/

It would be a shame if we had to stop using this wonderful plugin in order to use the repaired EyeTV...

[holderer]

Same problem for me

I think I have to downgrade too but I have no idea how to do.
Can anybody tell me how to downgrade?
Do I have to downgrade eyetv only or front row too? I made the front row update to 2.1.7 too (together with eyetv upgrade to 3.1.1)

Thanks in advance for your help!!

[sjk]

Or, search for and read this KB article:

How do I upgrade or downgrade EyeTV 3?

Some screenshots in that might be helpful.

[holderer]

Thanks a lot!

Downgrade was successful.
Hopefully there will be a solution to use pyeTV with eyeTV 3.1.1 soon.

[Captain Maniac]

Downgrading worked for me as well. The problem I was having with 3.1.1 was a situation where the Live TV window would flash continously, between "one moment please" and live TV. I would start up in Front Row as usual, but as soon as I clicked on Guide from that menu, I would encounter the flashing problem. Not only that, but my full screen EyeTV window would shrink to a much smaller size. Downgrading to 3.1 (4515) solved the problem.