What version are you on? I had that on a test version.
I will remove that log. I though I did. I was trying to track down a very aggravating bug that only happened when I went with it built on GitHub. Come to find out, It turned out to be and issue with how I packaged yt-dlp I will have that removed in just a few.
Sorry about that. The log file is no longer being written. I did remove my debug log file, but I left the sync log in by mistake. The new release has that corrected.
It mostly seemed odd that you were probing to support a feature that was disabled, but I can see how a quick debugging trace got thrown in at initialization without regards to the flags and you never expected the unwashed masses to ever see it.
This is why I stopped developing Clicker... too many demands, not enough time or energy to meet them. I don't know how you do it @Bobby_Vaughn.
When I was testing the build on my test machine, it worked fine. When I used the one built on GitHub actions, it was failing. I was rushing to figure out why there was an issue with one but not the other since they were the same build. After several failed fixes, I went full scale debug mode and forgot to remove the sync log. I also forgot to remove the placeholder IP address, the http://127.0.0.1:7777/pluto/us_east/vod.json link. It all boiled down to me adding yt-dlp wrong in my Inno installer. I should have tested it better before pushing the release out. Sorry for the confusion.
If I left the impression that I urgently needed/wanted/expected a fix for this, that was not my intent at all. I was merely providing information for the developer for him to use as he sees fit. If an issue is really bothering me, then I might start asking when the developer expects to fix it, but this report was for information only.
Developers should keep their code to themselves if they don't expect any feedback at all. Personally, I like knowing someone has it installed and using it rather than hearing crickets.
Users should be grateful for what they get from volunteers.
Thanks! Fixed in 1.5.2. We appreciate your efforts.
Yeah, we've already seen that 'tude with Prism.
Yeah, I mean, I asked for one thing. A lot of people came forward with issues for Clicker, and I just asked for GitHub issues because I am dealing with some personal health issues right now and don't have the energy to handle it at the moment. So I was going to have to wait a little bit. And tracking things on a forum thread is very hard, but tracking and triaging GitHub issues is a lot easier. I waited a little bit. No one opened a single issue that had one. So I stopped producing the app, and now the repo is private, and I'm just going to slowly maintain it for myself as a private project.
Not to mention a user decided to take their app, take my concepts, particularly the Rust Foundation. MPV as the player. As well as a few other features I really worked hard on and rolled it into their own app that honestly doesn't work quite as well, from what I could tell. Actually, it was their app that prompted me to make Clicker because I needed a laptop-focused Channels client for Windows that actually worked well with a full grid guide, downloads, etc. And their tool at the time didn't have any of that, so I didn't take any of their code or concepts. I just built my own tool with the idea of Channels needs a Windows app that isn't made for HTPCs. At that time, that tool did not even play videos particularly well from just regular streaming sources.
Regardless, I found this discouraging enough to just cease development as well, combined with the other stuff. It's just, I could have used the help from them maybe to make Clicker a better project, and, you know, working together would have been better than making two separate projects, or at least, you know, consulting me and asking, hey, you cool with me using some of your ideas in my tool, you know, something like that, just as a fellow community member, as a courtesy, but I didn't get any of that, and, you know, not gonna support my tool anymore. It's just not worth it. I encourage everyone to use this tool actually. It's really well designed, it's great, and I think Bobby is a saint for building so many great tools around Channels.
Regardless, I put a lot of time, a lot of energy into getting Clicker to working on every major platform. And I feel like it was just kind of taken by someone else. And even though I wanted to fix things, my one ask wasn't met at all by anyone requesting. So I'd rather just focus on my health and not focus on building extraneous tools outside of the ones I really am passionate about, like ah4c. Like, perhaps if that developer had chosen to open some pull requests, we could have joined forces and made a better client for everyone. But unfortunately, they didn't reach out or ask to do that.
v1.5.3 Released
-
Updated MPV to latest release
-
Removed Placeholder IP in Pluto Settings
-
Fixed Live Scores in Sports Section
Sorry for all the updates all at once. This should be the last for a week or so.
1 Like
I don't know how you do it, Bobby, but your work is fantastic. And you won't take a penny in donations for it. Thank you.
1 Like
v1.5.4 Released
- Added Vertical Guide Timeline
- Improved Movie Trailer Quality
- VOD Improvements
- Added Cast and Crew Images to Shows
1 Like
Just clicked the button in the app to upgrade. And it won't come back up afterwards. I'm getting:
Application Error
EventID: 1000
Faulting application name: HTPC.exe, version: 1.5.6.0, time stamp: 0x6ac20000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.7802, time stamp: 0x34805822
Exception code: 0xe0434352
Fault offset: 0x0000000000025369
Faulting process id: 0x3258
Faulting application start time: 0x01dd6806629bc053
Faulting application path: C:\Users\Dad\AppData\Local\Programs\NucleusHTPC\HTPC.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 59f4724c-4364-4d1a-8ad9-dfcac3c1990e
Faulting package full name:
Faulting package-relative application ID:
I'll look into it
Try to download the file installer directly and running it again.
I just pushed an update that should fix the issue as well as updating yt-dlp to the latest security fix.
I've dug into it further on my side, and I saw that earlier I wasn't looking at the totality of the EventLog entries being thrown. What is happening is that the new build of MPV-2.DLL requires instructions that my older i5-750 just doesn't have, and the MPV-2.DLL initializer tries to use one of those instructions and crashes with an invalid instruction error. I confirmed this by grabbing the older MPV-2.DLL out of 1.5.1 and dropping it in the 1.5.6 folder and the application launches (though I'm not sure what functionality is affected, if any).
Solutions would be:
-
Telling the installer to block installation on machines that don't have needed instruction sets
-
Compiling the code for MPV-2.DLL using a different processor requirement. For example, if you're using march=native on the build of MPV-2.DLL, then your own processor family becomes the requirement. Common options for march would include
x86-64,x86-64-v2,x86-64-v3and `x86-64-v4'. My system would run x86-64 and x86-64-v2, but not x86-64-v3 or x86-64-v4. -
Using the x86-64 prebuilt mpvplayer library instead of the x64-64-v3 one. (If you're using the prebuilt mpv).
I recognize I'm running old silicon and will understand if you need to leave the old architectures behind. I will say some low-end devices made more recently (e.g. Celerons and Pentiums) might also be missing the newer, more fancy, instruction sets. Note that ffmpeg will still use the newer instructions if available, even if mpvplayer isn't compiled to expect them.