• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle
  • It’s a poor analogy, but imagine a public IP like a hotel, there can be lots of guests (clients) at this hotel. Hotel policy is they won’t let any outsiders in unless you know the room number (port) of the person you’re trying to reach.

    Imagine you and a friend are staying in separate hotels and want to give each other copies of your favorite Linux .ISOs, but neither of you knows the other’s room number - you show up at the hotel and the front desk tells you to pound sand because you don’t have their room number.

    As long as one of you knows the other’s room number though, you can meet.

    Torrenting without port forwarding means you can only trade your favorite .ISOs with people who have port forwarding enabled (sharing their room number to the tracker), which makes you less effective of a seeder. Enabling port forwarding allows you to share with anyone (sharing your room number with the tracker).






  • You’re about to embark on a massive journey and I wish you the best of luck :D

    Compressing 110 4K movies is going to be a long encode time, but it will be so nice to digitize that collection.

    First question: if you already have them ripped and stored, do you even need to re-encode them? If you have a powerful enough Jellyfin server for transcoding, that may be enough.

    That said, if you’re looking to optimize for space and quality, there’s some questions to ask:

    • proprietary (but ubiquitous) HEVC or the emerging open standard AV1? It’s going to be a lot easier finding tips/guides for HEVC.

    • Constant Rate Factor (CRF), or Average Bit Rate (ABR). CRF tends to be more straightforward if you have a varied collection of content because it let’s the encoder choose settings to deliver consistent quality. 2-pass average bit rate is good if you have a target size or compatibility in mind - great for squeezing out the absolute optimal quality if you’re trying to fit on a Blu-Ray disc or meet certain streaming criteria, but 2x the encode time (hence “2-pass”) can be a tough sell.

    Stick with software encoding, steer clear of hardware solutions like NVENC. They’re crazy fast, but inconsistent quality.

    There’s some guides out there on converting DV to HDR 10+ etc, but I don’t have a lot of experience with that process.









  • Their follow-up:

    I have written to Haier to try to get some clarification and perhaps an agreement. I hope Haier will listen to us now that so many people are supporting us. Thank you all!

    Dear Haier team,

    you have probably noticed that my announcement to delete the plugin has met with a lot of displeasure from the community. There are a number of people who bought your appliances not only because of the good price/performance ratio, but also because they can be integrated into home assistant.

    I think it would be helpful to the discussion if you could explain the following questions:

       Please provide details of WHICH clauses of terms of service does this project violate?
       What is an unauthorized manner?  
       What significant economic harm is being faced by the company? (in terms of dollar figures)
       When did these projects violate your intellectual property?
    

    I’m sorry if some people have gone over the top, but this doesn’t have to escalate and there doesn’t have to be a bad reputation for your brand in the open source community.

    Can we find a common solution here? Can I do something to make the plugins use the API more economically? Should we reduce the polling? I would like to release a new version that uses the API in a way that does not harm your business. You can also consider an official home assistant integration, the home assistant guys would like to get in touch with you for that. This would be a great competitive advantage within the smart home community.

    I hope to get an answer and until then I’ll leave the repos online.

    Andre