Smart fade triggers AmplitudeService: DirectProbe over mobile data despite waveform extraction being disabled

Support
1

App version

Beta

Issue description

Hi Tolriq,

Following up on the feedback regarding mobile data usage with Smart fade:

I have confirmed that “extract wave form” under Advanced / Database is disabled on mobile data as per default settings. However, after inspecting the debug logs, I found that having Smart fade enabled still triggers full track downloads over mobile data.

When Smart fade is turned on, queued tracks immediately invoke AmplitudeService: DirectProbe over mobile data to extract waveform arrays for calculating mixes:

2026-08-25 22:49:52.673 Verbose/AmplitudeService: DirectProbe [3291ms]: Amplitudes array extracted 402 (4020) [http://…/getTranscodeStream.view?mediaId=o8XXJfL3PeFxATABXZ5wjt…]
2026-08-25 22:49:53.337 Verbose/AmplitudeService: DirectProbe [647ms]: Amplitudes array extracted 208 (2085) [http://…/getTranscodeStream.view?mediaId=qHW5YNDzU4yq6QI7dCrDmu…]
2026-08-25 22:49:53.347 Verbose/CrossfadeManager: Smart mixes[fallback]: 4020/2085 → 29200/900/d=-/c=-

This causes the entire transcoded stream of both the current and the upcoming track to be fetched immediately over mobile data just for amplitude calculation.

Conversely, when Smart fade is disabled, this network probe does not occur (Smart fades: No amplitudes, and MetadataWarmupSkippedMobile is logged), keeping mobile data usage normal:

2026-09-12 14:12:11.165 Error/ForwardingPlayer: Smart fades: No amplitudes
2026-09-12 14:12:11.606 Verbose/CurrentMediaDetailsWarmupCoordinator: MetadataWarmupSkippedMobile […]

Could you please consider applying the mobile data restriction to this on-the-fly DirectProbe used by Smart fade as well?

Thank you for your time and continuous support.

Device type

Phone

Media provider

Navidrome

Steps to reproduce

  1. Ensure “extract wave form” under Advanced / Database is set to default (disabled on mobile).
  2. Connect to a mobile data network.
  3. Enable “Smart fade” in playback / crossfade settings.
  4. Start playback of any playlist/track from Navidrome where tracks do not have cached waveform data yet.
  5. Observe that full transcoded streams for both current and upcoming tracks are downloaded over mobile data via AmplitudeService: DirectProbe.

Additional information

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

m.soga.nn

2

Thanks for the detailed report and log. I confirmed that Smart fades extracted waveforms for two Navidrome tracks on August 25. The Wi-Fi-only waveform restriction already applies to this Smart fade path, but that part of the log does not show the network classification or preference values, so I cannot establish why those probes were allowed.

The September 12 “No amplitudes” message is Smart fades falling back while still enabled. In the September 24 beta log, Smart mixes runs without a new amplitude probe.

If this still happens, could you reproduce it on 15.1.0 with a track that has never been analyzed, while on mobile data (And disconnecting from wifi while debug mode is enabled), and upload a fresh log immediately afterward? Please include the values of all three waveform extraction switches, especially “Always.” That should let me identify whether the connection is being classified incorrectly or another path is starting the extraction.

3

Hi Tolriq,

Thank you for looking into the code path and for the detailed explanation.

To answer your question regarding the settings:

Under Advanced / Database, the waveform extraction switches (including “Always”) are kept at their default values (disabled on mobile data).

I tested again with unanalyzed tracks on mobile data using 15.1.0B2, and the log confirms that `AmplitudeService: DirectProbe` is no longer triggered; it properly falls back with `Smart fades: No amplitudes` and `MetadataWarmupSkippedMobile`.

I will keep Smart fade enabled for a while during my daily use on mobile data to monitor the data consumption and see if the issue reoccurs. If I notice unexpected data spikes or probes again, I will capture a fresh log and follow up here.

Thank you for your continuous support!