Adding resume & navigational FF & FR function to TS files?

[Videonut]

Is there any way to add to TS files on USB stick so that the resume & navigational FF & FR buttons work?

A friend has given me a stick with heaps of TS files  that my T2 doesn't play very well when it comes to resume & navigational FF & FR functions.

Could the 'reconstructapsc' plug in or some other program do this & if so how?

Thanks in advance

[prl]

Could the 'reconstructapsc' plug in or some other program do this & if so how?

Resume points are time markers, and reconstructapsc generates the time-to-file-location index file for the TS file. That may also help with FF, REW and skip.

[Videonut]

But how would I run reconstructapsc on a file that's on a USB stick?

[prl]

In the same way as you'd run it on a file anywhere else, I imagine. I haven't used it.

[Paul_oz53]

Haven't checked lately but in the media player menu press YELLOW for other locations. Find the USB device.

Select the file and press MENU. Select reconstructapsc (after installation of course). It will run but there is no finished (edit: correction progress) message. Takes a couple of minutes typically so be patient.

[MrQuade]

But how would I run reconstructapsc on a file that's on a USB stick?

Exactly the same way you'd run it on a file that is on the Wiz's hard-disk.

[Grumpy_Geoff]

It will run but there is no finished message. Takes a couple of minutes typically so be patient.

There is a 'Reconstruct AP/SC is finished !' popup.
It runs as a background job, so by pressing BLUE/Extensions menu from live TV the background jobs will be shown at the top of the resultant list. For this plugin, I don't think there's any "dynamic progress" other than 0% and 100%, but you can select a background job and press OK on the 'In progress' job entry to open the 'Job View' window of the task.
Obviously processor speed and recording length come into play, on my T4 a 90 min recording takes about 30 secs.

[adoxa]

I could provide a Windows (command line) program to do it, which might be a bit more convenient and quicker (along the lines of createapsc e:\*.ts).

[Grumpy_Geoff]

If one is handy with command line access, then the .ap and .sc files (re)creation can be achieved with the createapscfiles program that is installed with the firmware (no plugin needed) -
/usr/lib/enigma2/python/Components/createapscfiles /path/to/recording_file.ts

[Grumpy_Geoff]

But how would I run reconstructapsc on a file that's on a USB stick?

How about shell script that'd reside on the USB thumb drive, and you'd execute via File Commander on the Wiz to iterate over the *.ts files present on the drive and "do the business"?
Something like -

Code: Select all

#!/bin/sh
dirname=$(realpath $(dirname $0))
cd $dirname
for REC in *.ts; do
    if [ ! -f "${REC}.ap" ]; then
        echo "$(date +'%T') - processing ${REC}"
        /usr/lib/enigma2/python/Components/createapscfiles "${REC}"
    fi
done
echo "$(date +'%T') - finished processing}"
echo -e "\nDon't forget to unmount the thumb drive once finished with it"

Attached as Recreate_APSC_batch.sh

Recreate_APSC_batch.sh

version #2

(358 Bytes) Downloaded 52 times

post edited for updating script

[prl]

it might be worth putting an if [ ! -f $REC.ap ] test in the loop, so that it can be run on a drive that has a mix of processed and unprocessed files on it.

[Grumpy_Geoff]

it might be worth putting an if [ ! -f $REC.ap ] test in the loop, so that it can be run on a drive that has a mix of processed and unprocessed files on it.

Yeah, I thought about that almost straight after I posted it, and being a bit lazy at the time I thought I'd leave it for a version 2

[prl]

[Grumpy_Geoff]

it might be worth putting an if [ ! -f $REC.ap ] test in the loop, so that it can be run on a drive that has a mix of processed and unprocessed files on it.

I updated the script as suggested, and re-posted the update in the original post.

[peteru]

I'm the type of person who would reach for the find command to provide a fully recursive solution.

[adoxa]

FWIW here's the Windows (64-bit) version (the .c file is the source; it should compile on macOS/Linux).

Obviously processor speed and recording length come into play, on my T4 a 90 min recording takes about 30 secs.

My 3.4GHz Core i7 took 56s for an hour SD (1.6GiB) and 84s for HD (2.4GiB) on the NTFS USB (running again took only seconds, though); reconstructing on the T2 took about 1m50s and 4m20s, respectively.