Cutlist editor tweaks

[singlefished]

All good Adoxa, back to normal and installed fine ~ InfoBar didn't have any problems either.....

Now.... to update or not to update (beta feed) ~ that is the question

[adoxa]

"End at this position" has been replaced by, and become an option of, "Quick execute", which also provides "Punch cuts" and "Both" (truncate at this position, then punch). Punch will replace the cuts with zero bytes, deallocating complete file blocks, i.e. you can very quickly reclaim the file space without having to do a full execute. U4 owners could go one step further and "collapse" the cuts, so the file size actually shrinks, at the expense of even less precise cuts (at multiples of 188KiB). Let me know if you're interested and I'll implement it (at some point). The new version is part of Patches by Adoxa.

I might replace the skin files for the next release (to avoid having separate versions), but I would still prefer to patch (to preserve customisations).

As it turns out I patched after all, providing three patch versions for the skins.

Here's something I did notice though.... Both times when I checked the cut after the processing the audio seemed to drop out/go funny just before the cut point and just after the cut the video looked like it was playing double speed for a second to catch up to the audio...

I've addressed this with autoskip, but not executed, which will have to wait a bit longer (I've really gotta get back to other stuff). If anyone wants to try the new autoskip, let me know your box type and I'll provide a new binary. I think the issue is similar to what happened during initial trickplay, so I've done a similar fix - keep track of the play position and when it reaches an "out" point, seek to the next "in" point. Naturally, that's why it won't work with executed cuts. I might be able to do something with splicing or discontinuous packets (any TS experts out there?) or possibly readjust all the PTS values, but as I said, that's gonna have to wait...

[adoxa]

My editing process is (from the start of a program segment) jump five minutes, then every 1:30 until I find an ad. Then (at the start of the ad) jump 1:30, 1:30 and 30s (and back & forth at 10s, usually) until I find the program again. Repeat for each ad. It's under five minutes for an hour show, so not all that long. I was just thinking that rather than doing the skipping manually, it could be done automatically. E.g. press 8 and it skips five minutes, waits 0.25s, then skips 1m, waits 0.25s, ... Press 8 again to stop when you see an ad. Once at the start of the ad, press 5 and it skips one minute, waits 0.25s, then skips 30s... Press 5 again when you see the show. I'm not sure if quarter of a second is long enough, or even too long, that'll be interesting to see. Thoughts?

[MrQuade]

What does all that automation actually gain though? Is it actually any faster, or does it just save you pressing buttons? If automation doesn't speed up the task, then it sounds like just one more thing that could potentially break and/or just adds a layer of complexity.

[adoxa]

I think it will be a little faster (or at least feel faster), but I won't know until I code it (hopefully by the end of the week).

[Paul_oz53]

I think it will be a little faster (or at least feel faster), but I won't know until I code it (hopefully by the end of the week).

The biggest advantage I see is reducing wear on my remotes. I've killed a few over the years. Editing is a very concentrated user of certain keys.

I'd certainly try it out. It's very good already but this sounds promising.

The only reservation I have is whether 0.25s is the right pause duration. Maybe it should be programmable and capable of being switched on/off but you're probably onto that already.

[adoxa]

Switching it off is the same as manual, so that won't be an option; maybe one- to four-eighths of a second (any longer also seems pointless). If it works out it'd be a good time to make all the other durations configurable, too.

[dRdoS7]

Hi,

Would it be possible to add a number/colour for each option in the menu (except maybe for "back")?

That would save a few button presses.

I should add that I use Remove before/after mostly, and also I can never remember what colour button does what.

Thanks,

dRdoS7

[adoxa]

Would it be possible to add a number/colour for each option in the menu (except maybe for "back")?

Maybe, but...

I should add that I use Remove before/after mostly, and also I can never remember what colour button does what.

...isn't that what the help's for?

LONG GREEN - remove before (this is where it starts)
LONG RED - remove after (this is where it ends)

[dRdoS7]

Hi,

That was quick.

Would it be possible to add a number/colour for each option in the menu (except maybe for "back")?

Maybe, but...

I should add that I use Remove before/after mostly, and also I can never remember what colour button does what.

...isn't that what the help's for?

LONG GREEN - remove before (this is where it starts)
LONG RED - remove after (this is where it ends)

I used "Help" to check if the coloured buttons were assigned to those functions.

I had just updated the FW from 20180417 to 20190206, and wanted to see if that had changed.

It seems your Cutlist Editor mods are now part of FW, which wasn't the case with previous FW. Time to update "Patches by..."?

Thanks,

dRdoS7

PS. I didn't equate the text in the Help screen to the text in the Menu!

[MrQuade]

It seems your Cutlist Editor mods are now part of FW, which wasn't the case with previous FW. Time to update "Patches by..."?

I thought they were already incorporated last year sometime when PeterU was madly merging heaps of adoxa's other mods?

[Star6key]

Hi,

Would it be possible to add a number/colour for each option in the menu (except maybe for "back")?
...

+1

I find that I only have to use the 'Execute cuts and exit' option, and since that is in the middle, it's a pain having to scroll to it every time.

[adoxa]

I find that I only have to use the 'Execute cuts and exit' option, and since that is in the middle, it's a pain having to scroll to it every time.

LONG BLUE.

[Paul_oz53]

I edit extensively using the colour buttons, direction keys and numbers. It really doesn't require the menu or back buttons now but I am wearing out the number keys. This is why I think automating the search will save some keystrokes but I think the current color key assignments are fine.

[paullings]

Paul_oz53 wrote: :
I edit extensively using the colour buttons, direction keys and numbers. It really doesn't require the menu or back buttons now but I am wearing out the number keys. This is why I think automating the search will save some keystrokes but I think the current color key assignments are fine.

+1
I use it extensively as well to top and tail all my recordings and it works really well at the moment with minimal button presses.

[Star6key]

I find that I only have to use the 'Execute cuts and exit' option, and since that is in the middle, it's a pain having to scroll to it every time.

LONG BLUE.

Cool... but it would still be good to actually have it on the menu (as I have no idea what the other colours/numbers shortcuts are for the other menu options).

[prl]

LONG BLUE.

Cool... but it would still be good to actually have it on the menu (as I have no idea what the other colours/numbers shortcuts are for the other menu options).

HELP is your friend:

1_0_0_0_0_0_0_0_0_0_20190218161646.jpg (88.32 KiB) Viewed 4007 times

[Star6key]

HELP is your friend:
1_0_0_0_0_0_0_0_0_0_20190218161646.jpg

Maybe I should add the Help button on the 650 remote.

Thanks Prl.

[prl]

I certainly have it on our 785.

[adoxa]

Here's a preliminary version of "Smart skip". I seriously misjudged the timing, so it's now initially one second. I've also added a "manual" mode, after all. There's no configuration atm, but edit /etc/enigma2/smartskip (created the first time you run CLE after the patch): 0 for manual; otherwise wait time in milliseconds.

In manual mode: 2 will initially skip 3m, then repeat 30s; 5 will skip back 15s. Then it's 5s once or twice, then either +2s or -3s, then it steps. 5 will initially skip 5m, then repeat 1m; 8 will skip back 30s. 8 will initially skip 8m, then it's the same as 5 (using that to switch direction).

Automatic mode is much the same, only you use the same key to switch direction and it stops after +2s or -3s (or any other key).

I'm not sure manual is really any different to the current situation (a quick test with "Young Sheldon" took about 1:25 for each method), but automatic did seem quicker (about 0:55).

Apart from a means to switch between manual and automatic, a way to set the initial skip would also be nice. Some shows have short breaks, so an initial skip of 1:30 would be better; similarly, SBS has long show segments, so an initial skip of ten minutes would be appropriate. I could perhaps use 8 as a menu with some presets, and/or replace the menu's "back" with "settings" and do something in that.

[Paul_oz53]

Here's a preliminary version of "Smart skip". I seriously misjudged the timing, so it's now initially one second. I've also added a "manual" mode, after all. There's no configuration atm, but edit /etc/enigma2/smartskip (created the first time you run CLE after the patch): 0 for manual; otherwise wait time in milliseconds.

In manual mode: 2 will initially skip 3m, then repeat 30s; 5 will skip back 15s. Then it's 5s once or twice, then either +2s or -3s, then it steps. 5 will initially skip 5m, then repeat 1m; 8 will skip back 30s. 8 will initially skip 8m, then it's the same as 5 (using that to switch direction).

Automatic mode is much the same, only you use the same key to switch direction and it stops after +2s or -3s (or any other key).

I'm not sure manual is really any different to the current situation (a quick test with "Young Sheldon" took about 1:25 for each method), but automatic did seem quicker (about 0:55).

Apart from a means to switch between manual and automatic, a way to set the initial skip would also be nice. Some shows have short breaks, so an initial skip of 1:30 would be better; similarly, SBS has long show segments, so an initial skip of ten minutes would be appropriate. I could perhaps use 8 as a menu with some presets, and/or replace the menu's "back" with "settings" and do something in that.

Thanks Adoxa. It is more a marginal improvement than a quantum leap here.

I found myself not dexterous enough to press the right key at the right time so I don't think I'm a good judge. The way I edit probably is a factor too. It suits me to just press 2 and press zero when I spot an ad, then press 2 again and zero when the ad ends.

I then use the list of marks just created to manually edit out the ads, etc.

Often I will play a movie at 4-8 times normal and press 0 when ads appear. It's very similar to what Smart skip does so I didn't get an improvement in editing time but, as noted, probably more in my agility than anything else.

[adoxa]

Often I will play a movie at 4-8 times normal and press 0 when ads appear. It's very similar to what Smart skip does so I didn't get an improvement in editing time but, as noted, probably more in my agility than anything else.

So you went from 4-8x to 30x to identify the ads, but the actual fine-tuning to get the start/end didn't change much.

I'm not sure if it's worth it, myself; sometimes it works well, other times not so much. I probably won't keep it.

[Paul_oz53]

...
I'm not sure if it's worth it, myself; sometimes it works well, other times not so much. I probably won't keep it.

I think you're right - not a large gain but a fairly big increase in complexity. Worth a try though to settle the question.

[adoxa]

All the jumps should be user configurable.

I still haven't done that, but I've done the next best thing and added a custom keymap. This allows you to override the keys directly to define your own seek values, without worrying about patching the global map. Not as convenient as modifying them on the fly in the GUI, but I needed this for something else, so this is just a bonus.

Code: Select all

<keymap>
    <map context="CutlistSeekActions">
        <key id="KEY_LEFT" unmapto="seek:-60" flags="m" />
        <key id="KEY_RIGHT" unmapto="seek:60" flags="m" />
        <key id="KEY_1" unmapto="seek:-120" flags="m" />
        <key id="KEY_3" unmapto="seek:120" flags="m" />
        <key id="KEY_4" unmapto="seek:-180" flags="m" />
        <key id="KEY_6" unmapto="seek:180" flags="m" />
        <key id="KEY_7" unmapto="seek:-240" flags="m" />
        <key id="KEY_9" unmapto="seek:240" flags="m" />
        <key id="KEY_PREVIOUS" unmapto="seek:-600" flags="m" />
        <key id="KEY_NEXT" unmapto="seek:600" flags="m" />
    </map>
</keymap>

Change the values to suit, put it in /etc/enigma2/keymap_user.xml and voila (in the 20190630 beta).