BUG: Skip-back in Cut-list editor on V2 skips forward

[MrQuade]

Running the December 19 firmware release.

As per the title, using the LEFT or YELLOW button in the cutlisteditor results in a skip forward operation rather than the expected skip back.

This is observed on the V2, but not the U4.

I attempted to set a non-default time value for the Skip-back button, but this didn't fix the issue.

Skipping back using the LEFT button during regular recording playback works properly.

[adoxa]

Running the December 19 firmware release.

I flashed 20191106 and there were no updates, so I'm not sure what version you mean.

As per the title, using the LEFT or YELLOW button in the cutlisteditor results in a skip forward operation rather than the expected skip back.

I don't experience that.

[MrQuade]

I don't experience that.

Strange, this was reported by a user on Whirlpool and I was able to replicate it.

My V2 is on the beta feed and hasn't been flashed fresh, rather has received incremental updates over the course of the beta.

U4 has been in the same update feed and does not see the problem.

[adoxa]

Trying again on the test V2 I can replicate it immediately on starting the editor. However, once you press PLAY (or something) to update the picture they work as expected (sort of). Since presumably you want to see where you're cutting I'm not sure there's anything to be done.

I have thought about doing a play/seek/pause sequence, but no one else has complained about the picture not updating during pause, so I gather it's not much of an issue.

[MrQuade]

Trying again on the test V2 I can replicate it immediately on starting the editor. However, once you press PLAY (or something) to update the picture they work as expected (sort of). Since presumably you want to see where you're cutting I'm not sure there's anything to be done.

I have thought about doing a play/seek/pause sequence, but no one else has complained about the picture not updating during pause, so I gather it's not much of an issue.

I am seeing even worse behaviour after pressing PLAY.

Once I press PLAY, then PAUSE, I can no longer skip in any direction. skipping while in play mode behaves very strangely.

Again, no issue on the U4.

[adoxa]

Once I press PLAY, then PAUSE, I can no longer skip in any direction.

The V2 has always been that way, you must press PLAY again and only the last skip is effective (for TS, other files do skip, but still don't update the picture).

skipping while in play mode behaves very strangely.

I've not noticed any problems with forward; the second/step (LEFT/YELLOW) backwards don't work too well, though. I don't think there's anything I can do about it, other than either using a play/skip/pause sequence or a very slow slow.

[MrQuade]

Yikes ok then.

Sounds like the V2 needs some more driver lovin' than I originally thought!

[dRdoS7]

Hi,

Trying again on the test V2 I can replicate it immediately on starting the editor. However, once you press PLAY (or something) to update the picture they work as expected (sort of). Since presumably you want to see where you're cutting I'm not sure there's anything to be done.

I have thought about doing a play/seek/pause sequence, but no one else has complained about the picture not updating during pause, so I gather it's not much of an issue.

We received our V2 yesterday, and I noticed that "feature" too, found it slightly annoying, as the T2 was able to skip when paused. It's something I use a lot.

Is it a bug?

I tried the U4, and it wouldn't skip either, but then when I tried again later it was fine.

It's good they all use the same remote codes, as I don't have to swap remotes, just cover the IR receiver.

My T2's HDMI out failed last week, and I brought the U4 in from the caravan, then decided I better but another for the 'van, and as a spare. Have needed one several times in the past.

Thanks,

dRdoS7.

[adoxa]

We received our V2 yesterday, and I noticed that "feature" too, found it slightly annoying, as the T2 was able to skip when paused. It's something I use a lot.

Okay, I'll have a go at getting it working.

Is it a bug?

Hard to say, could just be the way the drivers work. My previous PVR didn't update the picture, either (actually, it didn't allow seek during pause at all, but I patched that, then discovered the picture didn't update). It's probably a bug that it only skips by the last key pressed (unlike other media files, which you could try by renaming .ts to .mpg).

[MrQuade]

Is it a bug?

Yep, and pretty sure it is a bug in the drivers and/or gstreamer or a combination of the two. Something that only PeterU or the upstream guys can solve.

It's good they all use the same remote codes, as I don't have to swap remotes, just cover the IR receiver.

The U4 can use any of the supported IR code sets, but the V2 cab only use the one U3/V2 code set. If you ever need to set it up so they respond to different remotes, you need to change the U4.

[adoxa]

Transport streams (.ts and .trp files) are not played by GStreamer, but by DVB. GStreamer will properly seek, but not update the picture; transport streams will only seek by the last-pressed key (that's the difference you can see by renaming .ts to .mpg).

I use the V2 remote for the T2 and V2, using a user key map on the V2 to use long POWER for wakeup (and to keep the front panel button working).

[dRdoS7]

Hi,

We received our V2 yesterday, and I noticed that "feature" too, found it slightly annoying, as the T2 was able to skip when paused. It's something I use a lot.

Okay, I'll have a go at getting it working.

Good luck.

It's good they all use the same remote codes, as I don't have to swap remotes, just cover the IR receiver.

The U4 can use any of the supported IR code sets, but the V2 cab only use the one U3/V2 code set. If you ever need to set it up so they respond to different remotes, you need to change the U4.

As George would say: "I'm aware".

I think I've got enough tuners with either one, beside cricket's only on one network nowadays. Have both U4 and V2 in the lounge ATM, for setting up and testing. V2 is powered down now, until I swap them over so I can run it over summer, prior to using it in the caravan. I'll hold off that until skipping when paused is (hopefully) fixed.

Thanks,

dRdoS7

[adoxa]

Here's a plugin to update the picture during a paused skip (effective immediately, no need to restart). It's a bit dodgy, so I hope it works okay, but it might be the best I can do. Note that step back goes back twice, so you might like to step forward again.

[dRdoS7]

HI,

Here's a plugin to update the picture during a paused skip (effective immediately, no need to restart). It's a bit dodgy, so I hope it works okay, but it might be the best I can do. Note that step back goes back twice, so you might like to step forward again.

Would it be possible to make it work on a U4?

I tried, but it wouldn't install.

I've been using the U4, and it has "freezed on pause" too (despite me saying it worked earlier).

Thanks,

dRdoS7

[adoxa]

Here you go.

[dRdoS7]

HI,

Here you go.

Great, that worked.

I figured out why it didn't work, then worked the next time: it was an mp4 that wouldn't skip (noticed it watching a re-encoded Doctor Who last night), and a recording that would.

Thanks,

dRdoS7

[dRdoS7]

Hi,

It's a bit dodgy, so I hope it works okay, but it might be the best I can do.

I've been using the U4 a fair bit. The plug-in worked first time when installed, but I probably only did a couple of skips to test it. I've noticed that the skip buttons may work OK once or twice, but then not. If I then try a different button it may, or may not work. It may skip forwards, then freeze, and backwards, then freeze. Then it will skip back OK, using a different number button. It may work for one or two skips then not. Finally nothing will skip. Have press Play, then same again. The same with the RW button: it may step back one or two times, then not.

Doesn't matter if it's a recorded show, or a "re-encoded" file.

So, not dodgy enough.

I'll add that I'm not using it with Cut-list Editor, just watching media.

Does the problem need to be escalated? Is it already listed as a bug?

Hopefully it can be remedied.

I am surprised that not many have mentioned it. Maybe most use FF/RW buttons only.

Thanks,

dRdoS7

[MrQuade]

I think most people use skips, not FF/REW. God help them if they are.

I've not encountered any particularly bad skipping issues on the U4 with either recorded or downloaded media, and the U4 is my fault driver now. You might have another issue at play?

[adoxa]

I didn't notice any issues with a .ts (but not a recording), but an .mp4 was a bit wonky. Disable Paused Skip, set slow to 25 and see how that goes. If Paused Skip isn't going to work, adding /100 as an option might be the next best thing.

[dRdoS7]

Hi,

Disable Paused Skip

That's easy, though I didn't realise there was that ability until a few days ago when I saw it was listed under "Plugins".

set slow to 25 and see how that goes. If Paused Skip isn't going to work, adding /100 as an option might be the next best thing.

Where are these options?

Also, I just realised the U4 is using V17.5, will that make a difference? The V2, I think, is V19.

Thanks,

dRdoS7

[adoxa]

set slow to 25 and see how that goes. If Paused Skip isn't going to work, adding /100 as an option might be the next best thing.

Where are these options?

MENU > Settings > TV > Recording settings > Slow motion speeds. /25 is currently the slowest, /100 is effectively what Paused Skip does.

Also, I just realised the U4 is using V17.5, will that make a difference?

Not to the plugin, not sure about playback.

[dRdoS7]

Hi,

Just updated the V2 to 20200901 FW.

Skipping when paused still doesn't work.

Installed PausedSkip 0.9, and it works perfectly.

Thanks,

dRdoS7

[dRdoS7]

Hi,

Having just updated to beyonwiz-19.3 20201114, I thought I would try skipping while paused. Found it still doesn't, so enabled PausedSkip, then tested it, worked fine. Skipping wise.

I changed from ABC21 to 7. It was on Tuner A, but it swtiched to Tuner B. Tuner A showed yellow as if it was being used for recording, which it wasn't. I switched back to ABC, the picture was frozen at the last frame I saw on ABC. Then it crashed.

I think I had disabled it due to a problem previously, but can't sure. I've only recently decided to use the V2, instead of the U4 (which has better tuners for caravan use).

I've attached the crash log.

Enigma2_crash_2020-11-15_18-51-00.log

(39.76 KiB) Downloaded 42 times

Forgot: It was actually the second time, the first time it didn't crash immediately, and I was able to view ABC by pressing pause, waiting a few seconds, then pressing play. But it eventually crashed. When it rebooted, I disabled PausedSkip, and there was no problem. Then I had a second go.

I've attached the crash log.

Enigma2_crash_2020-11-15_18-46-46.log

(40.77 KiB) Downloaded 42 times

Thanks,

dRdoS7

[peteru]

Code: Select all

{2090}<  4757.803> /usr/bin/enigma2(handleFatalSignal(int, siginfo_t*, void*)) [0x6ebac]
{2090}<  4757.803> /lib/libc.so.6(__default_rt_sa_restorer) [0xb51d5da0]
{2090}<  4757.803> /usr/bin/enigma2(eDVBServicePMTHandler::SDTScanEvent(int)) [0x108c80]
{2090}<  4757.803> /usr/bin/enigma2(eDVBScan::nextChannel()) [0x11e3c4]
{2090}<  4757.803> /usr/bin/enigma2(eDVBScan::channelDone()) [0x123aa8]
{2090}<  4757.803> /usr/bin/enigma2(eGTable::sectionRead(unsigned char const*)) [0xe9084]
{2090}<  4757.803> /usr/bin/enigma2(eDVBSectionReader::data(int)) [0xb06b8]
{2090}<  4757.805> /usr/bin/enigma2(eMainloop::processOneEvent(unsigned int, _object**, ePyObject)) [0x79984]
{2090}<  4757.805> /usr/bin/enigma2(eMainloop::iterate(unsigned int, _object**, ePyObject)) [0x79f30]
{2090}<  4757.805> /usr/bin/enigma2(eMainloop::poll(ePyObject, ePyObject)) [0x7a2f8]
{2090}<  4757.806> /usr/bin/enigma2(n/a) [0x1ac990]

[adoxa]

I didn't experience a crash, but it did freeze, which this update fixed. Hopefully it will fix your issue, too.

[dRdoS7]

Hi,

I didn't experience a crash, but it did freeze, which this update fixed. Hopefully it will fix your issue, too.

Great, that didn't crash. Now I can skip while paused, and that will please Mr. Beyonwiz as I can now buy a second V2, for my wife. Which, in theory, should please her too: she'll have 4 tuners to record cr@p. Everybody's kicking goals.

Thanks,

dRdoS7