Sur d’autres sites (16037)

• Trolls in trouble

  6 juin 2013, par Mans — Law and liberty

  Life as a patent troll is hopefully set to get more difficult. In a memo describing patent trolls as a “drain on the American economy,” the White House this week outlined a number of steps it is taking to stem this evil tide. Chiming in, the Chief Judge of the Court of Appeals for the Federal Circuit (where patent cases are heard) in a New York Times op-ed laments the toll patent trolling is taking on the industry, and urges judges to use powers already at their disposal to make the practice less attractive. However, while certainly a step in the right direction, these measures all fail to address the more fundamental properties of the patent system allowing trolls to exist in the first place.

  System and method for patent trolling

  Most patent trolling operations comprise the same basic elements :

  1. One or more patents with broad claims.
  2. The patents of (1) acquired by an otherwise non-practising entity (troll).
  3. The entity of (2) filing numerous lawsuits alleging infringement of the patents of (1).
  4. The lawsuits of (3) targeting end users or retailers.
  5. The lawsuits of (3) listing as plaintiffs difficult to trace shell companies.

  The recent legislative actions all take aim at the latter entries in this list. In so doing, they will no doubt cripple the trolls, but the trolls will remain alive, ready to resume their wicked ways once a new loophole is found in the system.

  To kill a patent troll

  As Judge Rader and his co-authors point out in the New York Times, “the problem stems largely from the fact that, [...] trolls have an important strategic advantage over their adversaries : they don’t make anything.” This is the heart of the troll, and this is where the blow should be struck. Our weapon shall be the mightiest judicial sword of all, the Constitution.

  The United States Constitution contains (in Article I, Section 8) the foundation for the patent system (emphasis mine) :

  The Congress shall have Power [...] To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.

  Patent trolls are typically not inventors. They are merely hoarders of other people’s discarded inventions, and that allowing others to reap the benefits of an inventor’s work would somehow promote progress should be a tough argument. Indeed, it is the dissociation between investment and reward which has allowed the patent trolls to rise and prosper.

  In light of the above, the solution to the troll menace is actually strikingly simple : make patents non-transferable.

  Having the inventor retain the rights to his or her inventions (works for hire still being recognised), would render the establishment of non-practising entities, which most trolls are, virtually impossible. The original purpose of patents, to protect the investment of inventors, would remain unaffected, if not strengthened, by such a change.

  Links

  • Taking on Patent Trolls to Protect American Innovation
  • Fact Sheet : White House Task Force on High-Tech Patent Issues
  • Make Patent Trolls Pay in Court
  • Constitution of the United States

• OSError : [WinError 126] Não foi possível encontrar o módulo especificado. Error loading [closed]

  27 août 2024, par Felipes

  Informações relevantes

  


  **
SO : Windowns 11
Dependencias : torch —extra-index-url https://download.pytorch.org/whl/cpu ;
openai-whisper ;
ffmpeg-python
Microsoft Visual C++ Redistributable

  


  Tudo isso dentro de um ambiente virtual
**

  


  Então... eu to com o seguinte codigo em python :

  


  import whisper
import os

# Carregar o modelo
model = whisper.load_model("base")  # Pode usar 'small', 'medium', 'large' conforme a necessidade

# Carregar o áudio
audio_path = "audio.mp3"  # Substitua pelo caminho do arquivo de áudio extraído
result = model.transcribe(audio_path)

# Obter o texto da transcrição
transcription_text = result['text']

# Salvar a transcrição em um arquivo .txt
with open("transcription.txt", "w") as file:
    file.write(transcription_text)

print("Transcrição salva em 'transcription.txt'")


  


  Basicamente é pegar um arquivo .mp3 e salvar a transcrisão no em arquivo txt
mas ao rodar o codigo eu recebo o seguinte erro :

  


  Traceback (most recent call last):&#xA;  File "C:\Users\Felipe Bezerra\Documents\ytDownload\transcrisao.py", line 2, in <module>&#xA;    import whisper&#xA;  File "C:\Users\Felipe Bezerra\Documents\ytDownload\venv\Lib\site-packages\whisper\__init__.py", line 8, in <module>&#xA;    import torch&#xA;  File "C:\Users\Felipe Bezerra\Documents\ytDownload\venv\Lib\site-packages\torch\__init__.py", line 148, in <module>&#xA;    raise err&#xA;OSError: [WinError 126] N&#xE3;o foi poss&#xED;vel encontrar o m&#xF3;dulo especificado. Error loading "C:\Users\Felipe Bezerra\Documents\ytDownload\venv\Lib\site-packages\torch\lib\fbgemm.dll" or one of its dependencies.&#xA;</module></module></module>

  


  É como se as dependências não estivecem instaladas, já verifiquei a variavél de ambiente, criei outro ambiente virtual, e sempre caio nesse mesmo erro.

  


  PS : o msm codigo rodou perfeitamente no Debian 12

  


  Verifiquei o ambiente virtual, reistalei tudo

  


• Package is installed inside docker but actual command provide exception

  1er juin 2022, par user1765862

  I'm trying to use ffmpeg core package inside .net 6 dockerized project. I install ffmpeg core inside Dockerfile, reference actual package FFMpegCore inside solution but when I try to apply any of the commands from the ffmpeg core lib I'm getting error

  


  


  An error occurred trying to start process './ffmpeg' with working
directory '/var/task'. No such file or directory

  


  


  Docker build is done with no error.

  


  Dockerfile

  


  FROM public.ecr.aws/lambda/dotnet:6 AS base
....
RUN apt-get install -y ffmpeg
....
FROM base AS final
WORKDIR /var/task
COPY --from=publish /app/publish .


  


  As per ffmpeg core docs in order to use ffmpeg I need to set its binary folder, so I add ffmpeg.config.json

  


  {
  "BinaryFolder": "/var/task",
  "TemporaryFilesFolder": "/tmp"
}


  


  Actual error is being thrown when I try to execute following command

  


  


  An error occurred trying to start process './ffmpeg' with working
directory '/var/task'. No such file or directory

  


  


  This is the place where error gets triggered

  


   using FFMpegCore;&#xA; ...&#xA; public class MyController : ControllerBase&#xA;    {&#xA;        public async Task<string> Get()&#xA;        {    &#xA;             await FFMpegArguments&#xA;                   .FromPipeInput(new StreamPipeSource(myfile))&#xA;                   .OutputToPipe(new StreamPipeSink(outputStream), options => options&#xA;                      .WithVideoCodec("vp9")&#xA;                      .ForceFormat("webm"))&#xA;                      .ProcessAsynchronously();&#xA;             ...&#xA;        }    &#xA;    }&#xA;</string>

  


  Update :
After changing BinaryFolder location to /usr/bin I'm getting following error

  


  An error occurred trying to start process '/usr/bin/ffmpeg' with working directory '/var/task'. No such file or directory


  


  Update #2
This is my complete Dockerfile

  


  FROM public.ecr.aws/lambda/dotnet:6 AS base

FROM mcr.microsoft.com/dotnet/sdk:6.0-bullseye-slim as build
WORKDIR /src
COPY ["AWSServerless.csproj", "AWSServerless/"]
RUN dotnet restore "AWSServerless/AWSServerless.csproj"

WORKDIR "/src/AWSServerless"
COPY . .
RUN dotnet build "AWSServerless.csproj" --configuration Release --output /app/build

FROM build AS publish   

RUN apt-get update \
    && apt-get install -y apt-utils libgdiplus libc6-dev \
    && apt-get install -y ffmpeg

RUN dotnet publish "AWSServerless.csproj" \
            --configuration Release \ 
            --runtime linux-x64 \
            --self-contained false \ 
            --output /app/publish \
            -p:PublishReadyToRun=true  

FROM base AS final
WORKDIR /var/task

CMD ["AWSServerless::AWSServerless.LambdaEntryPoint::FunctionHandlerAsync"]
COPY --from=publish /app/publish .