Content-Type: multipart/alternative; boundary="------------050403010207050000070406" --------------050403010207050000070406 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Christoph Bartelmus wrote: > Hi! > > Bob van Loosen "bob.loosen@gmail.com" wrote: > [...] > >> That part is ok, but I'm not sure you can guarantee synchronization >> between the data written/read from sendPipe and the assignment of the >> carrier frequency. >> > > Wait, this whole thing won't work anyway. fork() creates a new process > with its own address space. You can change any variable in the parent > process as you like, it won't affect the child. > Shared memory seems like overkill, so maybe your first idea with using > sendPipe to pass the carrier frequency to the child is the best option. Latest patch assigns carrier frequency, I also added a usleep to give portaudio some time to set up properly, otherwise the first transmission might fail. Bob. --------------050403010207050000070406 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Christoph Bartelmus wrote:

Hi!

Bob van Loosen "bob.loosen@gmail.com" wrote:
[...]

That part is ok, but I'm not sure you can guarantee synchronization
between the data written/read from sendPipe and the assignment of the
carrier frequency.


Wait, this whole thing won't work anyway. fork() creates a new process  
with its own address space. You can change any variable in the parent  
process as you like, it won't affect the child.
Shared memory seems like overkill, so maybe your first idea with using  
sendPipe to pass the carrier frequency to the child is the best option.

Latest patch assigns carrier frequency, I also added a usleep to give portaudio some time to set up properly, otherwise the first transmission might fail.

Bob.

--------------050403010207050000070406--