Recording starts too late

[bleuzen]

Recording starts too late

[Bleuzen]

Hi, it is hard to get it right. Every system is a little slower/faster. SpotRec already gives ffmpeg some time to start up, but in your case it seems not enough.
For now, you can tweak it by changing this variable in the script:

SpotRec/spotrec.py

Line 52 in eda66b1

_recording_time_before_song = 0.25

Currently it is set to a quarter of a second, but you can increase it to for example a half of a second by changing it to:

_recording_time_before_song = 0.5

I may also check your example song / album when I get to that, maybe increase the pre-configured time.

---

Just out of interest, because it could play a role:
Are you using PulseAudio or Pipewire (as pulse replacement)?

[lewumpy]

Currently it is set to a quarter of a second, but you can increase it to for example a half of a second by changing it to:

_recording_time_before_song = 0.5

Thanks for your reply! I played around with the time a bit. Unfortunately, it did not bring success. Even when I set 5 seconds, there was 5 seconds of silence at the beginning of the song and and still the first sound was cut off anyway. Unfortunately I have no idea if you can make settings for ffmpeg somewhere else.

Just out of interest, because it could play a role: Are you using PulseAudio or Pipewire (as pulse replacement)?

I'm using PulseAudio.

[Rijul-A]

Can you try my working-config branch? The large differences are

• When a song change is detected, Spotify is paused. This way, the next song does not feature in the current song's recording.
• Spotify remains paused until time needed to cleanly finish the FFmpeg process.
• A larger wait time is used between starting a new FFmpeg process and resuming the paused song.

Of course, this method will produce some silence at both ends of the song; this is trimmed later in post-processing.py.