Hello, I currently use fc2-live-dl on an old Windows 8 tablet. For this reason, I have disabled the remux option to consume fewer resources. I have no problem transferring the segments to my main PC and joining them together there later. My problem arises when there are several streams and I haven't yet transferred the segments from the previous stream, causing the names of the following fragments to continue upwards. For example, if the last segment of the stream is called 2025-09-08-CHANNEL.180.ts, the first segment of the next stream is 2025-09-08-CHANNEL.181.ts. If we had a unique ID it would look like this: 2025-09-08-CHANNEL-QWERTY8.180.ts and 2025-09-08-CHANNEL-ASDFG4.1.ts, where QWERTY8 is the unique ID from the last segment of the stream and ASDFG4 is the unique ID for the most recent stream.
It's not a critical problem because I correct it manually, but it could be more efficient (in my opinion) if we had a unique ID for each stream.
Good morning and thank you for reading.
Hello, I currently use fc2-live-dl on an old Windows 8 tablet. For this reason, I have disabled the remux option to consume fewer resources. I have no problem transferring the segments to my main PC and joining them together there later. My problem arises when there are several streams and I haven't yet transferred the segments from the previous stream, causing the names of the following fragments to continue upwards. For example, if the last segment of the stream is called 2025-09-08-CHANNEL.180.ts, the first segment of the next stream is 2025-09-08-CHANNEL.181.ts. If we had a unique ID it would look like this: 2025-09-08-CHANNEL-QWERTY8.180.ts and 2025-09-08-CHANNEL-ASDFG4.1.ts, where QWERTY8 is the unique ID from the last segment of the stream and ASDFG4 is the unique ID for the most recent stream.
It's not a critical problem because I correct it manually, but it could be more efficient (in my opinion) if we had a unique ID for each stream.
Good morning and thank you for reading.