Hi David!
I'd be very lazy: just pad your pre-recorded signal with zeros, and play it on loop with
the file source.
Padding of files is easy, and essentially free in terms of storage space if your file
system supports sparse files (and if you're on linux, yes, it almost certainly does).
#!/
On 09/02/2024 09:04, Elof Wecksell via GNU Radio, the Free & Open-Source
Toolkit for Software Radio wrote:
You might be interested in the unix command newgrp, that can change the group
id of your session such that new files greated should have this group.
The normal behavior for any program is
You might be interested in the unix command newgrp, that can change the group
id of your session such that new files greated should have this group.
The normal behavior for any program is to create files with the group of the
current session. It would of course be possible for grc to have such
Ah!
No, that's not implemented in GRC. It's also relative unusual for that to be done, as far
as I can tell – for example, if you use gcc to compile a C file into an executable, then
that executable will have the GID of the executing user.
Best regards,
Marcus
On 09.02.24 12:43, kron...@tisc
Hi Marcus,
No, I'm not referring to the category. I'm talking about
the file group ownership.
I would like that the generated python
scripts had the same user/group owner of the grc file opened in GRC.
Thanks for help.
Ivan
Il 08.02.2024 11:14 Marcus Müller ha scritto:
> Hi Ivan,
>
> I
