Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Multimedia
  4. QMediaPlayer connect signal from its started ffmpeg backend

QMediaPlayer connect signal from its started ffmpeg backend

Scheduled Pinned Locked Moved Unsolved Qt Multimedia
2 Posts 2 Posters 311 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Z Offline
    Z Offline
    zedmatrix
    wrote on last edited by
    #1

    I have a iheart stream opened using QMediaPlayer, and the QMediaMetaData shows nothing and had to initiate a special ffmpeg routine just to retrieve the metadata, and when QMediaPlayer is open and playing a HLS Stream it shows this info >
    [https @ 0x7fafc4023280] Opening 'https://n03b-e2.revma.ihrhls.com/zc5235/3_kmxlygnrjs0302/playlist.m3u8?rj-ttl=5&rj-tok=AAABkaQl1GgApzAXNQXzlTn8yg' for reading
    [https @ 0x7faf9046c240] Opening 'https://n03b-e2.revma.ihrhls.com/zc5235/3_kmxlygnrjs0302/main/172770034.aac' for reading
    [https @ 0x7faf9011cd80] Opening 'https://n03b-e2.revma.ihrhls.com/zc5235/3_kmxlygnrjs0302/main/172770035.aac' for reading

    But none of the signals from QMediaPlayer::error or ::mediaStatus or ::metadataAvailable are empty. I think this is from the ffmpeg started by the player function but haven't found a way to connect to it?

    Axel SpoerlA 1 Reply Last reply
    0
    • Z zedmatrix

      I have a iheart stream opened using QMediaPlayer, and the QMediaMetaData shows nothing and had to initiate a special ffmpeg routine just to retrieve the metadata, and when QMediaPlayer is open and playing a HLS Stream it shows this info >
      [https @ 0x7fafc4023280] Opening 'https://n03b-e2.revma.ihrhls.com/zc5235/3_kmxlygnrjs0302/playlist.m3u8?rj-ttl=5&rj-tok=AAABkaQl1GgApzAXNQXzlTn8yg' for reading
      [https @ 0x7faf9046c240] Opening 'https://n03b-e2.revma.ihrhls.com/zc5235/3_kmxlygnrjs0302/main/172770034.aac' for reading
      [https @ 0x7faf9011cd80] Opening 'https://n03b-e2.revma.ihrhls.com/zc5235/3_kmxlygnrjs0302/main/172770035.aac' for reading

      But none of the signals from QMediaPlayer::error or ::mediaStatus or ::metadataAvailable are empty. I think this is from the ffmpeg started by the player function but haven't found a way to connect to it?

      Axel SpoerlA Offline
      Axel SpoerlA Offline
      Axel Spoerl
      Moderators
      wrote on last edited by
      #2

      @zedmatrix said in QMediaPlayer connect signal from its started ffmpeg backend:

      But none of the signals from QMediaPlayer::error or ::mediaStatus or ::metadataAvailable are empty.

      I don't understand this sentence. QMediaPlayer::error and mediaStatus aren't signals. You can find the related signals here. What do you mean by "are empty"? What is an empty signal?

      I think this is from the ffmpeg started by the player function but haven't found a way to connect to it?

      What's "this"?

      Maybe you wanna rephrase your question into something easier to understand.

      Software Engineer
      The Qt Company, Oslo

      1 Reply Last reply
      0
      • Nhan NguyenN Nhan Nguyen moved this topic from General and Desktop on

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved