Thank you for PIP support!
No problem, it was actually a good suggestion. I just was hesitant because it was really hard to get working.
Getting this on 1.3.1 after inputting IP address of server on Mac:
http://192.168.x.xxx:8089 answered but not as a DVR:HTTp status client error (403 Forbidden) for url (http://192.168.x.xxx:8089/dvr) If macOS asked about the local network, allow it and try again.
I gave it access when opening for the first time but it hasn't asked again.
Nice App!
I finally took it for a test drive and am keeping it.
I loaded all 7 of my dvr servers and played a mix of formats from them.
Appreciate the settings for locations of buffer, cache, downloads and logs.
I tried it on my Mac mini and it worked but the issue I posted was on my Macbook
That's an issue related to your configuration, not something I can fix for you.
Thanks anyway!
@mackid1993 are the channel collections working for you? Its not for me. Im getting blanks when i'm going into my Channel Collections
They don't work for me either. I just get "Nothing matches. No channel is in both of those filters".
The only filter I select is the Collection name. The sources filter is set to All sources.
No issues with channel collections here, so I don't know.
Is there any way we can help debug it to figure it out?
I can't reproduce. Maybe open a PR if you find the issue.
I'm getting the same issue on the MacOS app. Anything but "All Collections" nets zero channels.
Other than that, it's a nice app. Typically on my Mac I'll just run the Channels iPad app which has worked well too.
like I said, this is not happening to me in my environment, so I don't really know why.
If someone wants to try to fix it, it's open source MIT. I'll try to take a look when I have time, but it's kind of impossible to fix something that you can't reproduce.
I couldn't reproduce this. I had to have a SOTA model just go at this blind. Claude Fable
5 looked through the code and discovered that when you have one channel collection that is completely empty, it triggers this regression. So it should be fixed in this release. Please let me know if this works.
@mackid1993 Is there any issue you know of with Clicker running in a Windows 11 VM that's being accessed via RDP?
Try turning on the option for software decoding. It's in the settings. That might work.
When I double-click the Clicker icon from my VM over RDP absolutely nothing happens. I'd imagine I need to launch it to change settings?
Does your VM have a GPU?
It uses mpv and ffmpeg to render video. I wonder if that is a limitation.
Not this one -- it's strictly for testing. I initially installed Clicker using WinUtil-for-Channels, but when it didn't work I installed it manually with the same result. I've been able to install it without issue on regular Windows machines. So I agree it might have something to do with not having a GPU, but it'd be nice if the app handled that with a dialog box instead of dead air.