[
    {
        "role": "user",
        "content": "I%20have%20files%20in%20my%20Sonos%20music%20library%20which%20are%20four%20hours%20long.%20If%20I%20play%20part%20of%20one%20of%20those%20files%2C%20and%20then%20play%20other%20things%2C%20how%20do%20I%20return%20to%20that%20file%20in%20the%20place%20I%20left%20off%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s what I found about whether and how you can return to the point at which you left off in a **long file** (e.g. 4 hours) in your Sonos music library, and what the limitations might be. Unfortunately, it depends on a few things.\n\n---\n\n### What Sonos Offers: \u201cResume\u201d Support\n\n- Sonos supports a feature called \u201cSave & resume playback,\u201d which allows some kinds of content (like podcasts or audiobooks) to resume at the last played position when you return to them. This is only possible if the track or content is flagged as **resumable**. ([docs.sonos.com](https://docs.sonos.com/docs/save-resume-playback?utm_source=openai))  \n- In Sonos' documentation, **resumable tracks** must provide certain metadata (e.g. `canResume = true`) for Sonos to keep track of where you paused. ([docs.sonos.com](https://docs.sonos.com/docs/save-resume-playback?utm_source=openai))  \n\n---\n\n### Local Music Files\n\n- If these 4-hour files are part of your **local music library** (e.g. MP3/AAC/WAV files on a computer or NAS that Sonos indexed), Sonos generally treats them as standard music tracks\u2014not necessarily as resumable content. That means Sonos doesn\u2019t always remember where you left off.  \n- In user discussions, people have reported that when they switch to another source (Spotify, radio, etc.), Sonos may forget the playback position in local files and restart the track from the beginning when they come back. ([en.community.sonos.com](https://en.community.sonos.com/controllers-and-music-services-228995/how-to-pick-up-right-where-you-left-off-in-an-audio-file-after-spotify-or-another-service-has-been-used-6830713?utm_source=openai))  \n\n---\n\n### What You Can Do: How to Return to the Spot\n\nAssuming Sonos does *not* natively remember where you left off in that specific file, here are some workarounds / manual steps you might take:\n\n1. **Manually note the time** during playback (e.g. 1:35:42 into the 4-hour file).  \n2. When you want to return, open your local files in the Sonos app.  \n3. Use the scrubber (seek bar) to move to that time-position you noted. It might be tricky with very long files, but you *can* seek to specific points in a track if the format supports that.  \n\n---\n\n### What Determines Whether Sonos Can Resume Automatically\n\nWhether Sonos will remember and return to your last point depends on:\n\n- Whether the file/content is flagged as **resumable** (metadata support).  \n- Whether you paused the content, or just switched sources. If you paused and resume shortly afterward, sometimes the position may be retained; but switching sources often clears this.  \n- The **format** and how the track is accessed (local file, streaming service, etc.).  \n- Whether the content is being treated like an audiobook or podcast, which are more likely to support \u201cresume.\u201d  \n\n---\n\nIf you tell me which format your four\u2010hour files are in (MP3, FLAC, etc.) and how you access them (NAS, local folder, etc.), I can check whether there\u2019s a specific setup that *might* let you automatically resume where you left off for those. Do you want me to look up for your specific case?"
    },
    {
        "role": "user",
        "content": "Yes%2C%20they%20are%20mp3%20files%20uploaded%20to%20my%20music%20library.%20If%20placing%20those%20files%20somewhere%20else%20whould%20be%20helpful%2C%20I%20will%20do%20this."
    },
    {
        "role": "assistant",
        "content": "Here\u2019s what I found about using MP3 files in your local music library on Sonos\u2014and whether you can have them automatically resume from where you left off (plus what you might be able to adjust to get closer to that behavior).\n\n---\n\n## What Sonos Supports\n\n1. **File Compatibility & Formats**  \n   Sonos supports MP3 files in its local (shared) music library. The system supports most MP3 sample rates (except 8 kHz and 11 kHz) and standard compressed formats for streaming and local files. ([docs.sonos.com](https://docs.sonos.com/docs/supported-audio-content?utm_source=openai))\n\n2. **Save & Resume Playback Feature**  \n   Sonos has a documented \u201cSave & resume playback\u201d capability\u2014but **only** for content that provides certain metadata (e.g. podcasts or audiobooks via services), where a track is marked `canResume = true`. This is part of Sonos\u2019 SMAPI (Sonos Music API) structure. ([docs.sonos.com](https://docs.sonos.com/docs/save-resume-playback?utm_source=openai))\n\n   - Local library music tracks **are not automatically treated** as resumable just because they\u2019re long MP3s.  \n   - Sonos expects the service to store/resume playback if it supports it, but local files typically don\u2019t supply that metadata or service-layer support. ([docs.sonos.com](https://docs.sonos.com/docs/save-resume-playback?utm_source=openai))\n\n3. **Seeking / Manual Resuming**  \n   Even though automatic resume probably won\u2019t work, MP3 files do support seeking. This means you **can manually jump** to the position you want via the progress bar or scrubber in the Sonos app, assuming the file is streaming over HTTP with byte-range support or via a local share. ([docs.sonos.com](https://docs.sonos.com/docs/playback-on-sonos?utm_source=openai))\n\n---\n\n## What That Means for Your MP3 Files\n\nSince yours are MP3s in your local music library, here\u2019s how Sonos behaves in practice:\n\n- It likely **won\u2019t remember** where you last stopped automatically when you stop playback and switch to something else.  \n- You'll probably have to **manually seek** back to the point where you stopped (e.g. 2 hours and 37 minutes in) using the progress bar in the Sonos app.\n\n---\n\n## Possible Workarounds & Tweaks\n\nHere are some ideas that might improve things, though none are perfect:\n\n| Tweak | What It Might Help With | Limitations |\n|---|---|---|\n| **Convert MP3 files into an audiobook/podcast format** (split into smaller chapters or wrap with audiobook metadata) | Audiobooks *can* resume automatically if Sonos treats them properly (i.e. with `canResume = true`, correct metadata). | Converting long files and arranging metadata can be time-consuming. Sonos may still not pick up on the metadata correctly unless you host it via a service that supports SMAPI. |\n| **Use a streaming server** (one that supplies range requests and resume metadata) | Sonos supports HTTP byte-range requests which helps with seeking and potentially pausing/resuming from a spot in tracks. ([docs.sonos.com](https://docs.sonos.com/docs/playback-on-sonos?utm_source=openai)) | You\u2019ll need to set up or use a server that Sonos sees as a \u201cservice\u201d and that supports these SMAPI features. Most local libraries probably don\u2019t support SMAPI unless you're using something like Plex or a similar server. |\n| **Always leave the track paused instead of switching away** | Sonos may remember the paused position for short periods if you don\u2019t explicitly stop or switch to another track. | Practical only if you don\u2019t travel far away in your listening session; switching sources usually resets the context. |\n\n---\n\nIf you like, I can help you plan a specific approach for your library\u2014say, using a media server or splitting files\u2014based on what hardware or software you already have. Do you want me to draw up some options?"
    }
]