Converting QByteArray to QString
-
As already told you on so - make sure there is no
\0char in your string - otherwise it might get ignored either by QString::fromLocal8Bit() (which is still wrong when you use utf8 in python) or by python arguments parser. -
As already told you on so - make sure there is no
\0char in your string - otherwise it might get ignored either by QString::fromLocal8Bit() (which is still wrong when you use utf8 in python) or by python arguments parser.@Christian-Ehrlicher
What should I do with them?
I searched the QString and it seems there isn't any\0.
Do you know how can I find them?
Each of the elements of QByteArray was a uint8 number. -
Hi,
Why do you want to dump a blob of binary data as argument to a Python script ?
-
@Christian-Ehrlicher
What should I do with them?
I searched the QString and it seems there isn't any\0.
Do you know how can I find them?
Each of the elements of QByteArray was a uint8 number.@Sina-Ranjkesh-zade said in Converting QByteArray to QString:
Each of the elements of QByteArray was a uint8 number.
The first one of these 3686400 bytes in the input QByteArray that is zero will terminate the string conversion. The zero byte is in the input, not the output QString.
What you are trying to do makes little sense. Even if you got a meaningful 3686400 character QString, and that's doubtful IMHO, I am fairly confident no operating system will accept such a long command line.
Seems far more likely that the python script is expecting binary data in a file, and the file name as an argument.
-
@Sina-Ranjkesh-zade said in Converting QByteArray to QString:
Each of the elements of QByteArray was a uint8 number.
The first one of these 3686400 bytes in the input QByteArray that is zero will terminate the string conversion. The zero byte is in the input, not the output QString.
What you are trying to do makes little sense. Even if you got a meaningful 3686400 character QString, and that's doubtful IMHO, I am fairly confident no operating system will accept such a long command line.
Seems far more likely that the python script is expecting binary data in a file, and the file name as an argument.
@ChrisW67
Thank's for your response.
I want to pass an image from Qt to python. The image is high-resolution (1920*1080). I've converted the image data to QByteArray. To overcome the/0problem, I convert to Base64 coding.
As you said, when I want to send it as an argument to python code, I got this error:
"execvp: Argument list too long"
(When I convert to Base64, data size is 4915200).
Do you have any suggestions on how to solve this problem?
(I'm working with video frames and I should do that for each of the frames. So the speed is important too)
Any help will be appreciated. -
What is the python program expecting, or are you writing that also?
Edit:
You certainly do not want to be starting a new python process for every frame of video (assuming 25 or 30 FPS) . Start one process and feed it frames through its standard input or perhaps a shared memory block (QSharedMemory) -
What is the python program expecting, or are you writing that also?
Edit:
You certainly do not want to be starting a new python process for every frame of video (assuming 25 or 30 FPS) . Start one process and feed it frames through its standard input or perhaps a shared memory block (QSharedMemory)@ChrisW67
I'm writing that too.
For "standard input" if you mean input arguments of the process, I got this error:
"execvp: Argument list too long".
I also tried QSharedMemory too. I wrote data to memory in Qt successfully but I cannot read it from memory in python. -
@ChrisW67
I'm writing that too.
For "standard input" if you mean input arguments of the process, I got this error:
"execvp: Argument list too long".
I also tried QSharedMemory too. I wrote data to memory in Qt successfully but I cannot read it from memory in python.@Sina-Ranjkesh-zade said in Converting QByteArray to QString:
"execvp: Argument list too long".
As @ChrisW67 observed earlier
Even if you got a meaningful 3686400 character QString, and that's doubtful IMHO, I am fairly confident no operating system will accept such a long command line.
You cannot pass this sort of size literal string or byte-blob on the command-line to a process. And as @ChrisW67 also said, you will want just one external process (if at all) and pass data to it via shared memory or sockets or similar.
I do not know whether a
QSharedMemoryobject is supposed to be sharable with a non-Qt process. Though I would have thought it was. Can't say anything about what might happen from Python accessing it, check out documentation. -
As was already asked, can you explain what exactly does your Python script expects as input ?
How does it handle it ?
-
@ChrisW67
I'm writing that too.
For "standard input" if you mean input arguments of the process, I got this error:
"execvp: Argument list too long".
I also tried QSharedMemory too. I wrote data to memory in Qt successfully but I cannot read it from memory in python.@Sina-Ranjkesh-zade said in Converting QByteArray to QString:
For "standard input" if you mean input arguments of the process, I got this error:
No, I meant standard input. That is , the python program reads from a terminal and accepts input just as if you typed it (except it is the Qt program sending that input). The Qt program can send a command to the python program, send the data it needs, and read the result (if there is one) back on the python program's standard output. Or you can used shared memory, or a socket, or files, or do whatever the python program is doing in the Qt program...
