Can't start HD channels directly (1 Viewer)

[Spooky]

I am running floppy and firedtv's on WinXp SP3, Vista and Windows 7 without issues (on W7 RTSP streaming is not fully working yet), so i doubt that this is the cause.
Do both systems also use the "same" CAM? It could be that the issue is there.

It's not the same CAM. And the CAM shouldn't be an issue, since it happens on every HD channel and not just ORF 1 HD.

Since both systems have nearly the same hardware, testing the floppydtv + MP on an other hardware would be great!

True. I will do that next weekend. Luckily I have lots of unused hardware lying around .

 

[Spooky]

Bwah! I was under the impression, that I already had the newest firmware for my FloppyDTV installed (and I also thought that the newest firmware was already present on the new card for the HTPC of my friend). Well, it turns out that I didn't have the newest firmware. And after updating the firmware, this problem is gone.

Jesus, so simple . It's always the simple things...

 

[infinite.loop]

*pheew*
I am just happy that you got it working!

 

[Ron7Cs]

Thanks a lot guys.
Had exactly the same issue. Thought its a problem of my testing with win7+MP alpha because the HD channels work when I switch from another channel directly. But updating the firmeware of the floppydtv did it - version 1.4 didnt work - actual one works fine.

 

[Cecile]

I've seens a similar (if not they same problem) in a multiseat setup. When I stop MP while watching a TV channel, then start MP again. Go to My TV and select TV On, then I get an error about not being able to start time-shifting.
My conclusion is the following. When you try to watch the channel after starting MP, that you we're watching when yoy stopped MP before. Which is the default behaviour. Then you get the time-shifting error.

 

[amilewski]

Spooky, which version of firmware you used to solve your problem?
Have same problem but not sure if it is related to firmware version in my installation.

 

[Spooky]

Spooky, which version of firmware you used to solve your problem?
Have same problem but not sure if it is related to firmware version in my installation.

Simply the latest one, 1.5.2 - B30740.