It used to be 12 months, and I was so mad at that that I stopped subscribing, used all my credits, and basically never went back. I won’t even consider subscribing again so long as things I pay for don’t continue to be mine. I paid for the those credits, and they should be there forever until I use them. If they don’t like that, they should give my money back instead.
If you’re only watching on 1 TV, I don’t think there’s any reason to keep them a separate 4k library. And if your server can handle transcoding easily, there’s still not much reason.
If you have an often-used second (or third, etc) TV with lower resolution and your server doesn’t handle transcoding well, then it’s probably worth keeping them separate.
I’ve also started to disagree with the guide about file size. I don’t think I can tell the difference, and I’m not trying to preserve media for the future. So long as the video has the features I want, I think just about any file size is fine.
https://ivopereira.net/efficient-pagination-dont-use-offset-limit
This seems to be the same article.
I have my doubts about the technique, but it could be useful in certain controlled situations.
Even if you release multiple times every day, refusing to release on Friday still makes sense. It’s not about expecting bugs, it’s about guaranteeing that your devs’ time is their own. If you aren’t okay with paying your devs for time they spend dealing with their own problems at home (without charging them their PTO time for it!) then you shouldn’t be okay with making them work on weekends, no matter how rare it is.
I voted you up, but this is tough. I write tests at work when they’ll help me, but nobody else maintains or creates them. Except for the tests that the boss created and insists that everyone run.
I haven’t pushed terribly hard for my tests, but it’s pretty obvious that I wouldn’t get any traction if I did, and I’m picking my battles.
So while I agree with “write your tests anyhow”, it’s a lot harder than it sounds, and a lot less successful than a proper testing strategy that’s embraced by the team.
I bought one recently for 4k BRs. It’s awful, even though I bought one of the highest-recommended ones. They’re still slow, lose your place, and generally suck. And if there’s any dirt on the disc, you’ve got a major problem, no matter how small the smudge.
And that isn’t even counting the problems with the format, such as unskippable intros and copyright notices.
Ripped media is so, so superior that it’s absolutely ridiculous.
I don’t usually torrent, but I just looked at recent eps from Usenet and it looks like the majority is 1080p max. 4k exist, but tend to be from streaming services like Netflix, Hulu, HBO, or AppleTV it seems.
I find NZBFinder to be a decent usenet indexer for free, so maybe take a look on there for the shows you’re wanting and see if they’re even out there. It could be they just aren’t available at all.
To expand upon that, I had something similar to the OP’s setup at one point, and I found things worked a lot better when the files could be moved on the same volume, rather than appearing as separate volumes (because they were mounted separately). I ended up re-engineering my whole setup for that and it’s much faster now.
As for duplicates… I assume this is so you can continue seeding after the file has been moved? I can’t think of anything that would fit the bill for that off the top of my head. Ideally, I think you’d want QBT to just start serving from the new location instead, though I admit hard links does sound like a solution that could work.
And after Googling, it seems like it already does hard links for torrents for this exact reason. I think if you just map /media (and drop the 2 maps you have after that) things will work like you want.