[6238] Peacock is doing the Puss-in-Boots error again...

0xFeedBeef

As soon as you try to analyse something, but works fine in 6235, don't know about the intermediate versions... Probably a similar problem with prime reporting content not playable in SF "browser" in 6238 when amazon tries to queue up the "play" button in the browser (although the prime downloader's working as that's extracting links in a different way)...

Cats4U

Can anyone confirm this? Peacock is basically the only module I use at this moment, and I'd hate to go through the bother of an update if I'm only going to be pussied out.

0xFeedBeef, are you located in the US and not using a VPN? Please attach your StreamFab.log of a 6238 Peacock session. Thank you.

Justin

Working fine for me

Cats4U

Working fine for me
Justin

Thank you, Justin. I knew I could count on you, a fellow DOOL recorder. I'll give it a shot now. Fingers crossed.

Justin

Speaking of dool getting good at the moment I have subscribed via iTunes usa in Australia

0xFeedBeef

Can anyone confirm this? Peacock is basically the only module I use at this moment, and I'd hate to go through the bother of an update if I'm only going to be pussied out.

0xFeedBeef, are you located in the US and not using a VPN? Please attach your StreamFab.log of a 6238 Peacock session. Thank you.
Cats4U

Did you miss the part that it was working fine with 6235 despite the Puss-in-Boots with 6238? Sure, when I eventually have a reason to try 6238 again, or more likely 6239 when that gets released and I have a reason to try it. Maybe when you install 6238 over 6235 some component gets kept back that is missing in a fresh 6238?

I don't see what the fuss about "upgrading" is- just install each new version in a separate folder, and you can flip between versions any time you like...

Cats4U

Speaking of dool getting good at the moment I have subscribed via iTunes usa in Australia
Justin

I don't watch it myself. I just get it for my wife. That's why I wrote DOOL recorder and not DOOL watcher. :)

0xFeedBeef

Seems to be resolved now, probably was some glitch somewhere

Cats4U

Did you miss the part that it was working fine with 6235 despite the Puss-in-Boots with 6238? Sure, when I eventually have a reason to try 6238 again, or more likely 6239 when that gets released and I have a reason to try it. Maybe when you install 6238 over 6235 some component gets kept back that is missing in a fresh 6238?
I don't see what the fuss about "upgrading" is- just install each new version in a separate folder, and you can flip between versions any time you like...
0xFeedBeef

I didn't miss anything. You specifically wrote about 6238 and even put it in the title. That's why I wrote about 6238 and your error. I have no interest in 6235. That was the past. It had its own problems at the time, maybe not with the Peacock module, but something gave cause for them to create 6236 and later. As for separate folders, that would be hell, keeping track of which version/folder works best with each individual modules. Besides, SF has on occasion invalidated prior versions before a certain date. As far as I know, they only support (I use that word loosely :rolleyes:) the latest release.
As far as your comment -

Maybe when you install 6238 over 6235 some component gets kept back that is missing in a fresh 6238?

It won't happen to me. I do a clean installation with every update. Nothing gets left behind. And on that note, like Justin, I had zero issue with the 6238 Peacock module.