9 replies to this topic

[sjlouis]

I have some problems when I use backward and forward jumps in MoviePlayer and CutListEditor.

 

 

1. With the 1 and 3 touches, it jumps backward 12 seconds and forward 10 seconds.

 

I detected this problem since I used the Vu+. With the Xtrend, the jumps seemed to be the same backward and forward.

 

It was annoying but not dramatic but I should want to correct it.

 

 

2. In CutListEditor, it does not cut where I press "OK" because there are 2 counters for the same point in the movie as you can see in the picture and there is ~2 seconds difference. It's not convenient at all to have the good cut because it cuts with the mark on the left list while the good mark is under the picture.

 

 

3. I sought in CutListEditor files and I found keymap.xml. Then I could see there are options I did not know about as left and right touches to jump 1 second backward and forward.

 

Then I did other tests and I detected the jumps are approximate and not exactly with the requested value. There is an error of 1~2 seconds. Not very well to get the good mark.

 

I tried an application on the PC and the jumps seem to be good but it's not convenient to use the PC and the application is not as user-friendly than CutListEditor. In addition, it can only cut at the beginning and at the end of the file.

 

 

 

I've done some corrections in the keymap.xml and I've added additional jumps with "2", "5", "8" touches.

 

With the left touch, it jumped backward ~2 seconds and ~1 second backward with the right touch. Then, I replaced "seek:-1" with "seek:0" and "seek:1" with ""seek:2". But sometimes, it didn't work well. Then I tried "ReconstructApSc" and it seems to solve this problem but it's not convenient to use it on a lot of files. I have also modified the other standard touches.

 

I should also want to modify the MoviePlayer jumps to avoid asymmetric jumps but I haven't found the files of this application.

 

 

Thank you for your help.

 

Attached Files

•  screenshot_2024-02-06_15-11-54.jpg   85.86KB   0 downloads

[littlesat]

Here a lot depends on drivers…. Nothing we can really do about…
It also depends on the frame and content where a cut can be made

Edited by littlesat, 1 March 2024 - 20:16.

[sjlouis]

I thought it was due to the drivers but it seems to me that I had read that Openpli communicated with the manufacturers for the drivers. This is not the case ? No longer the case ?

 

Littlesat, can you respond to this subject please ?

 

https://forums.openp...dpost&p=1609177

 

Thank you.

[WanWizard]

Most, if not all, manufacturers don't have their own development team.

 

They have some third party create a BSP when they have a box (usually based on either an SDK reference design or on something the real manufacturer supplied), and once the box is in retail, any further development costs money and requires hiring that third party again.

 

Which rarely ever happens these days.  Most are OEM sellers, they have a few pallets produced as a one-off, and that's it.

[sjlouis]

OK WanWizard but when I download a new OpenPli version, sometimes the drivers are not the same even though they have never fixed this problem.

[WanWizard]

That happens very rarely, and usually when it is in their own interest, for example when a newer type of the same model introduces different tuner or wifi chipsets (as recently happened with the Octagon SF8008 for example).

 

For example, the VU+ Ultimo 4K drivers are dated 20190424, so almost 5 years old.

 

And apart from Edision, no vendor has ever updated the linux kernel version for their box (as that requires compatibility fixes to their drivers, they don't want to spend that money as it doesn't sell more boxes).

[sjlouis]

Effectively, in \\VUULTIMO4K\root\lib\modules\3.14.28-1.12\extra, the drivers are dated 2022 September 10 (OpenPli 8.3) but they have the same size than OpenPli 7.2 for which drivers are dated 2019 December 10 .

 

There were not the same for OpenPli 7.0 a few months ago.

[WanWizard]

The timestamp of a file says absolutely nothing about the version of that file.

 

Chances are those are the dates the drivers were unpacked from their tarball during the build, so the effective creation date of the file.

 

Drivers are supplied by the vendor as binary files, all the BSP does is download them from the vendors website, and package them so they can be installed.

[sjlouis]

OK. Before you write on this topic, I thought a new date was for a new version because several OpenPli versions have the same date for the drivers.

 

Thank you WanWizzard   .

[WanWizard]

The exact content of the tarball:

[wanwizard@buildserver3] $ tar -tvf vuplus-dvb-proxy-vuultimo4k-3.14.28-20190424.r0.tar.gz
-rw-rw-r-- shcheong/shcheong    8116 2018-04-26 01:01 bcm_event.ko
-rw-rw-r-- shcheong/shcheong    5992 2018-04-26 01:01 brcmfb.ko
-rw-rw-r-- shcheong/shcheong 7774196 2019-04-24 08:37 dvb_base.ko
-rw-rw-r-- shcheong/shcheong 1435508 2019-04-24 08:32 dvb-bcm7444.ko
-rw-rw-r-- shcheong/shcheong    2804 2019-04-19 08:55 fpga_directc.ko
-rw-rw-r-- shcheong/shcheong    5256 2018-04-26 01:01 procmk.ko
-rw-rw-r-- shcheong/shcheong    8668 2016-08-11 04:22 wakeup_drv.ko