Open HatKidTheHatLoli opened 2 years ago
PetitNigaud
commented
1 year ago I can confirm. Before I launch the broadcast the receiver radio plays just noise, then with PiFmAdv it plays the desired sound, but when I stop its execution with CTRL+C the receiver radio is just silent. Only when I shut down the RPi it plays noise again.
ryanginn
commented
1 year ago I can confirm as well.
The carrier is still active, however no sound is produced.
It seems that I have to reboot the Pi or kill the task to stop it.
On Sat 27 Aug 2022 at 17:49, PetitNigaud @.***> wrote:
I can confirm. Before I launch the broadcast the receiver radio plays just noise, then with PiFmAdv it plays the desired sound, but when I stop its execution with CTRL+C the receiver radio is just silent. Only when I shut down the RPi it plays noise again.
— Reply to this email directly, view it on GitHub https://github.com/miegl/PiFmAdv/issues/96#issuecomment-1229225904, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXQFX4Y7JUSBXIGHNZOVYXDV3JBI3ANCNFSM56JMOQNA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Regards, Ryan Ginnelly St Gerald's DLS College
craftxbox
commented
10 months ago Make sure you have no GPIO modules loaded in the kernel. For me, this kept happening until I removed the one wire module: sudo rmmod w1-gpio
gpu_freq=250 is in the boot config file before you ask. Often, it will stop producing the signal altogether. It appears to still be "working", like it's still trying to modulate. But of course nothing is being transmitted. Also noticed that in my case, the CPU usage jumped up a bit when this happened.
Also some strange behavior, if I close the program (Ctrl+C) or if the pipe is broken, the carrier signal does not stop being generated, and it will continue to produce the signal. If I run the command again, it'll keep generating the signal without cutting out, but will eventually hit a point where it says "waiting" before terminating itself (It doesn't kill the carrier frequency at this point either.) I assume the waiting thing is part of the buffer underflow/overflow issue mentioned in other issues.