Video stopping and blocking device

heimi · 24 November 2023 13:52

I am downloading TV videos from the Internet, trimming them with LosslessCut and storing them on a HD.
Playing on a Raspery3+ with OSMC (many versions) it happens that the video stopps suddenly, blocking the Raspi in a way that I have to unplug it to get access again.
I am using OSMC and LossLessCut since many years. The effect began about an year ago.
I tried older versions, bought a Raspi4 and all versions of OSMC with the same effect.
The videos run ok with QuicktimePlayer or VLC on the mac.
Any idea?
Mac Os Ventura, MacBookPro M1, Gigabit-Ethernet

sam_nazarko · 24 November 2023 13:55

Hard to tell without MediaInfo output, but perhaps you are encoding it in a way that is not compatible.

darwindesign · 24 November 2023 16:32

I was curious what this software was so I spent a few minutes reading up on it. My takeaway was that the dev doesn’t expect perfect results. It seemed rather clear to me that results were variable depending on the specifics of the input file, how exactly you had configured your cut and with what options as well as the output container. Their suggestion was to basically try different things till you found a working result.

github.com

mifi/lossless-cut/blob/master/issues.md

# FAQ

- **Can LosslessCut crop, resize, stretch, mirror, overlay text/images, watermark, blur, redact, re-encode, create GIF, slideshow, burn subtitles, color grading, fade/transition between video clips, fade/combine/mix/merge audio tracks or change audio volume?**
  - No, these are all lossy operations (meaning you *have* to re-encode the file), but in the future I may start to implement such features. [See this issue for more information.](https://github.com/mifi/lossless-cut/issues/372)
- Can LosslessCut be batched/automated using a CLI or API?
  - While it was never designed for advanced batching/automation, it does have a [basic CLI and a HTTP API](./cli.md), and there are a few feature requests regarding this: [#980](https://github.com/mifi/lossless-cut/issues/980) [#868](https://github.com/mifi/lossless-cut/issues/868).
- Is there a keyboard shortcut to do X?
  - First check the Keyboard shortcuts dialog. If you cannot find your shortcut there, [see this issue.](https://github.com/mifi/lossless-cut/issues/254)
- When will you implement feature X?
  - I have limited time and I have a lot of projects to work on, so I cannot promise any timeline. I will usually prioritize the issues with the most likes, [see here for a list of the most popular issues](https://github.com/mifi/lossless-cut/issues/691).
- How to *cut away* a middle part of a video?
  - Enable "advanced view" and then click the Yin Yang symbol. It will invert the segments.
- Where is application data, settings and temp files stored?
  - Electron's [appData](https://www.electronjs.org/docs/api/app#appgetpathname) folder.

## App Stores and GitHub difference

LosslessCut version in the App Stores is often a few versions behind the latest GitHub version, because I want to be sure that the new versions work perfectly before releasing in the App Stores. The GitHub version will contain new, untested features and may contain some bugs (even in existing functionality). I consider the newest GitHub versions to be a public "beta" test. Then, once I'm sure that the new version works well, I will release it in the App Stores as well to give a frictionless as possible experience for customers.

### Feature differences

This file has been truncated. show original

I don’t know about quicktime but I have seen VLC play some very messed up files that I couldn’t play with any other player I’d tried. This was a reflection on the state of the file and an impressive result from VLC, but nonetheless still a damaged file that was out of spec enough that most players couldn’t handle it. You may find that disabling hardware acceleration in Kodi’s settings gives more forgiving results, but this is going to come with lower limits to the resolution and complexity of files that the RPi is able to process with just the CPU.

heimi · 26 November 2023 08:10

thanks, I will give VLC another try.

darwindesign · 26 November 2023 10:41

Perhaps I could have been more clear. What I was trying to say was VLC tends to be very forgiving with files that are damaged or not encoded well and therefore should not be used as a method to determine if a file is good. The program your using to do the lossless edits with has some configuration options on how it processes and exports the files. I was saying that you should try to tweak how your making those files to see if you can find a process that gives you files that play correctly in Kodi.

In case you were not aware you could also make edl files (edit decision list) that are just simple text files that would tell Kodi which parts of the file to skip over which would allow you to avoid editing the file in the first place.

heimi · 28 November 2023 19:23

very interesting, I will try these aspects