Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - PhilthyM

#1
How do I say this without being rude...?! I'm not sure that I can!

I have to do settings for somebody weekly of up to 10 or 12 programs sometimes. What used to take me a minute or two now takes ages!

Did anybody do any useability testing of the UI before launching it? It's incredibly cumbersome now, a massive step backwards. On the old system, I could select the desired recording device, click the program, change series to single and that was it. If there was a requirement to do the same show again it was still there the search results, so I could repeat that process. Simple, elegant, consistent.

Now, I have to select which device each time, as it defaults to the first device - why? Then I have to go through a bunch of other options that all default badly for my needs. Was any consideration given to which might be the more likely defaults? Perhaps it was and I am at odds with the majority, fair enough. But why not allow me to save the defaults to suit my needs? Or even save them from one program selection to the next. It is so frustrating to have to go through half a dozen dropdowns for every program, and completely unnecessary. Its hard to believe that it could be implemented so badly!

Please can we get this reviewed and give some consideration to better handling of defaults? Thanks.
#2
Thank you Peter, I had come to the same conclusion, and just wanted to make sure I had not overlooked something.
#3
I think I've partially answered my own question, after a bit more playing this morning. I can see why it would not work to have two different device types as the format of the data being sent would be different for Media Centre and EyeTV, so that would not work.

So I guess the question is whether there's any other way of achieving this, apart from having the same recording schedule being entered twice, once for each device?
#4
I'm trying to work out if it's feasible to set up mirrored recordings, so set the recording once and have two separate machines pick up the same recording schedule. One would be using Windows Media Centre 7, the other EyeTV on a Mac Mini. I'd presumed that it would simply be a case of setting the device name the same on both, but it looks as if it's not that simple.

Anyone know if this can be done, and if so, how, please?

Thanks
#5
Quote from: brianh on April 23, 2009, 05:54:25 PM
I think that is a wise decision - we have waited this long so a little longer won't hurt us!

Yes, the chances are we could go a few months and not miss anything that's any good on the Nine Network!
#6
EyeTV / Re: EyeTV Remote - Leopard problem ?
April 06, 2008, 07:24:15 AM
Thanks futzle I've checked the device name and all looks correct. I'm sure it did work once, but that was prior to the most recent widget update.

Might give them a call next week.
#7
EyeTV / Re: EyeTV Remote - Leopard problem ?
April 04, 2008, 12:52:43 PM
This doesn't look very encouraging, no updates since February!

Anyway, I too am on Leopard 10.5.2 and EyeTV 2.5.2. I can see that if I login to IceTV Remote the programs are scheduled there, so that suggests the widget part of it is working correctly.

On the EyeTV end of things, an EPG update request works as expected, and shows my account expiry date, so that suggests the EyeTV to IceTV communication is working (at least to a point anyway).

However, if I attempt to update via Remote Scheduling nothing appears to happen. Other parts of the preferences page seem to give some sort of feedback, eg under the account details it's showing my expiry date, while the EPG section shows the time of the last successful update. However under the remote scheduling section it says "EyeTV will check only when you have a network connection", which seems to suggest it's having problems seeing the network. Maybe there's some other setting required there? If the EPG updates are working, I don't quite understand why remote scheduling isn't simply accessing the network in the same way?

Any hints gratefully received.