• AI and the Law – This Vox article is OpenAI training data – How AI is holding the internet hostage and media is no exception

    ,

    https://www.vox.com/technology/352849/openai-chatgpt-google-meta-artificial-intelligence-vox-media-chatbots

     

     

    • Pros of AI Chatbots:
      • Efficiency and Accessibility: AI chatbots can handle a large volume of queries simultaneously, providing quick and consistent responses, which is beneficial for customer service and support.
      • 24/7 Availability: Unlike human operators, chatbots are available around the clock, ensuring that users can get assistance at any time.
      • Cost-Effective: Implementing chatbots can reduce operational costs for businesses by minimizing the need for large customer service teams.
      • Personalization and Scalability: Advanced AI can offer personalized responses and scale effortlessly to meet demand.

     

    • Cons of AI Chatbots:
      • Bias and Misinformation: AI chatbots can inadvertently propagate biases present in their training data, leading to inaccurate or offensive responses.
      • Lack of Human Touch: Chatbots may struggle to understand and respond appropriately to nuanced human emotions and complex queries, potentially frustrating users.
      • Technical Limitations: While AI is advancing, chatbots can still make errors and provide incorrect information, which can undermine user trust.
      • Environmental Impact: Training and running large AI models consume significant energy, contributing to carbon emissions and environmental concerns.

     

     

    The deployment of AI chatbots raises significant ethical concerns. Biases in training data can lead to the generation of skewed or harmful content, posing risks to users and undermining trust in AI systems. Additionally, the potential misuse of AI chatbots for spreading misinformation and the environmental impact of training large AI models are critical issues that require attention.

     

    The trajectory of AI chatbot development points towards increasingly sophisticated and generalized AI capabilities. As research progresses towards Artificial General Intelligence (AGI), the potential applications of AI chatbots are expected to expand further, encompassing more complex and nuanced tasks. However, achieving AGI will require addressing current ethical and technical challenges to ensure the responsible development and deployment of AI technologies.

  • Embedding frame ranges into Quicktime movies with FFmpeg

    ,

    QuickTime (.mov) files are fundamentally time-based, not frame-based, and so don’t have a built-in, uniform “first frame/last frame” field you can set as numeric frame IDs. Instead, tools like Shotgun Create rely on the timecode track and the movie’s duration to infer frame numbers. If you want Shotgun to pick up a non-default frame range (e.g. start at 1001, end at 1064), you must bake in an SMPTE timecode that corresponds to your desired start frame, and ensure the movie’s duration matches your clip length.

    How Shotgun Reads Frame Ranges

    • Default start frame is 1. If no timecode metadata is present, Shotgun assumes the movie begins at frame 1.
    • Timecode ⇒ frame number. Shotgun Create “honors the timecodes of media sources,” mapping the embedded TC to frame IDs. For example, a 24 fps QuickTime tagged with a start timecode of 00:00:41:17 will be interpreted as beginning on frame 1001 (1001 ÷ 24 fps ≈ 41.71 s).

    Embedding a Start Timecode

    QuickTime uses a tmcd (timecode) track. You can bake in an SMPTE track via FFmpeg’s -timecode flag or via Compressor/encoder settings:

    1. Compute your start TC.
      • Desired start frame = 1001
      • Frame 1001 at 24 fps ⇒ 1001 ÷ 24 ≈ 41.708 s ⇒ TC 00:00:41:17
    2. FFmpeg example:
    ffmpeg -i input.mov \
      -c copy \
      -timecode 00:00:41:17 \
      output.mov
    

    This adds a timecode track beginning at 00:00:41:17, which Shotgun maps to frame 1001.

    Ensuring the Correct End Frame

    Shotgun infers the last frame from the movie’s duration. To end on frame 1064:

    • Frame count = 1064 – 1001 + 1 = 64 frames
    • Duration = 64 ÷ 24 fps ≈ 2.667 s

    FFmpeg trim example:

    ffmpeg -i input.mov \
      -c copy \
      -timecode 00:00:41:17 \
      -t 00:00:02.667 \
      output_trimmed.mov
    

    This results in a 64-frame clip (1001→1064) at 24 fps.