Navigation

    Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    1. Home
    2. Tags
    3. qudpsocket
    Log in to post

    • UNSOLVED QUdpSocket: Picking a specific network interface
      General and Desktop • qnetwork qudpsocket multicast • • rtavakko  

      9
      0
      Votes
      9
      Posts
      44
      Views

      @rtavakko is Application doing unicast reception and multicast transmission? Application is using single socket for reception and transmission. QUdpSocket* UDPSocket; initialize() function in your code binds the socket to the interface for the incoming connection (input IPAddress and Port) and same is being used for the transmission. Are you using multicast series for transmission ?
    • UNSOLVED Signal inside readyread of QUdpsocket
      General and Desktop • signal & slot threading udp qudpsocket • • Lior  

      7
      0
      Votes
      7
      Posts
      101
      Views

      @Lior said in Signal inside readyread of QUdpsocket: why the UI main thread stoped to respond ? the msleep is in anthor thread. Because you do it wrong (and I would guess the msleep is not in the thread but in the gui thread) but without code...
    • SOLVED QUdpSocket Benchmark for Package Lost Ratio
      General and Desktop • qudpsocket package lost • • goldenhawking  

      5
      0
      Votes
      5
      Posts
      53
      Views

      There is no buffering of a udp datagram in Qt code - the only thing you can do is to increase the os udp buffer. But I don't see this as drawback of Qt - it's simply the nature of UDP.
    • SOLVED QUdpSocket disconnects after data writing
      General and Desktop • network qudpsocket • • ClingerWinger  

      4
      0
      Votes
      4
      Posts
      355
      Views

      @ClingerWinger Glad you figured it out and thanks for the feedback :)
    • UNSOLVED Best way to retrieve data from different servers using UDPSocket
      General and Desktop • qudpsocket many servers • • Gacha  

      4
      0
      Votes
      4
      Posts
      749
      Views

      @Gacha I am not sure where you see the problems. The connections between signal and slots are removed with destruction of either object There is an issue when you are deleting an object when you are deleting it from the slot routine which is called an object's signal. I can imagine that there you may face a problem when using unique_ptr. To avoid this there is deleteLater()
    • UNSOLVED Issues using QUdpSocket::writeDatagram for high volumes of data
      General and Desktop • udp qudpsocket writedatagram packet loss • • Jesse Kaukonen  

      3
      0
      Votes
      3
      Posts
      3617
      Views

      @kshegunov said: I advise benchmarking the code. For one a datagram will always arrive whole (not like with TCP where you can have the message chopped in pieces), but there's a maximum size to it. Also there's no reception notification (like with TCP) as UDP is a "connectionless" protocol. These two things in mind you either send the datagram or not, you can't have anything else returned for the written bytes. I suspected as much. Good to know. QByteArray datagram; // ... Insert size checks here as well! PendingCompressedFrame & frame = *reinterpret_cast<PendingCompressedFrame *>(datagram.data()); // No copying, valid while the byte array is still there. As of yet, the receiver's processing time hasn't been a bottleneck so I haven't looked into optimizing it (it completes in around 0-1ms). Thank you for the suggestion though. Additionally, why the mutex? What are you protecting with it exactly? The mutex is not needed there. There's some other data that is being accessed from a DLL from a separate thread, but I should have removed the mutex from the simplified receiver. One good way to deal with such throughput is to have a dedicated thread for the reception that'll put the received datagrams (no processing) into a thread safe queue (or you can also use a signal-slot connection). From there you can have another thread that orders them (they may not come in the order of sending) and ultimately preparing them for display. That's a good idea. Keep readyRead() as minimal as possible to get data out of the socket's buffer, allowing more data in. The biggest question I'm still wondering is the performance of writedatagram. I've been looking into the assorted socket options, but it will take some reading to really understand what's going on with each flag.
    • UNSOLVED Unexpected Memory Leak in Windows 10?
      General and Desktop • windows 10 memory leak qudpsocket • • AnnaB  

      7
      0
      Votes
      7
      Posts
      2873
      Views

      @AnnaB There's one thing bothering me though ... You said you can't afford to drop a frame, but you use datagrams, which are inherently unsafe (in that manner) ... otherwise I'd assume it's what @SGaist said - probably your processing is lagging behind and there's work queuing up ...
    • UNSOLVED QUdpSocket::hasPendingDatagrams() broken in Qt 5.5 on Windows Desktop
      General and Desktop • qt5.5 qtnetwork qudpsocket windows desktop • • bsomervi  

      3
      0
      Votes
      3
      Posts
      2490
      Views

      Raised issue https://bugreports.qt.io/browse/QTBUG-49301
    • Binding more than one time to the same UDP port
      General and Desktop • binding qudpsocket bind • • koahnig  

      2
      0
      Votes
      2
      Posts
      915
      Views

      OK, found that there are two sides for that coin as well. I need to check the other side as well as one sees in the mutlicast sender example.
    • Stepping into QUdpSocket WriteDatagram with Qt Creator
      Tools • qtcreator debugging qudpsocket • • kzawada  

      1
      0
      Votes
      1
      Posts
      465
      Views

      No one has replied

    • Multicast with QUdpSocket and QHostAddress::Any does not work
      General and Desktop • qudpsocket multicast • • kzawada  

      8
      0
      Votes
      8
      Posts
      3249
      Views

      Did you check with the latest Qt 5.5 if you still experience this behavior ?
    • QAbtractSocket bind flags
      General and Desktop • udp qudpsocket bind shareaddress • • koahnig  

      1
      0
      Votes
      1
      Posts
      641
      Views

      No one has replied

    • [SOLVED] Trying to get Ntp client to work
      General and Desktop • qudpsocket ntp • • koahnig  

      17
      0
      Votes
      17
      Posts
      7743
      Views

      @SGaist Thanks for following up. Certainly I will take care this next time. I guess I will remember.