![]() ![]() It seems odd that the -s switch (pts and buffer stats) would make any difference to the system behaviour. Perhaps we can work together to gather data that will help contributors and users.Ĭould you post your (commented) bash script and links to your. I have had some systems looping continuously for up to 10 days. I'm not a programmer but I have a strong interest in using Pi's as video players in installations and have been undertaking a lot of long term stability testing of looped video playback using various bash scripts I've found online while I learn bash scripting myself. Please let me know if you need anymore information This goes beyond my level of expertise so if anyone could show me a way of doing this I would be greatly appreciated, although this wont be needed if omxplayer can be fixed. ![]() I have no idea how to do this, but im guessing I could use ffmpeg -i to get video duration and use this in an argument to check against omxplayer process runtime. ![]() One way to get around the problem would be the check the actual video duration against omxplayer running process time and if omxplayer runs for longer than video duration then kill omxplayer. I have two raspberry pi's which I have tested and both produce the same symptoms of locking up on the last frame and not ending. I can provide the scripts I have created so someone can recreate the problem and maybe provide a fix if possible. ![]() I have no idea where I need to look to fix this problem and the stats output from omxplayer does not give any indication on what has happened. This process works ok but after some time the process stops running and omxplayer gets stuck on what looks like the last frame of the current video being looped. I have managed to get omxplayer looping wmv files for a longer period of time by adding -s and logging output to file. 00:00:00 T:0 DEBUG: DllBcm: Using omx system libraryĠ0:00:00 T:0 DEBUG: DllOMX: Using omx system libraryĠ0:00:00 T:0 DEBUG: DllAvFormat: Using libavformat system libraryĠ0:00:00 T:0 DEBUG: DllAvUtilBase: Using libavutil system libraryĠ0:00:00 T:0 DEBUG: DllAvCodec: Using libavcodec system libraryĠ0:00:00 T:0 DEBUG: COMXCoreComponent::Initialize input port 80 output port 81Ġ0:00:00 T:0 DEBUG: Previous line repeats 5 times.Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::Initialize _decode input port 130 output port 131Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::Initialize _render input port 90 output port 90Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::Initialize _scheduler input port 10 output port 11Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::Initialize _scheduler input port 150 output port 151Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::AllocInputBuffers component(_decode) - port(130), nBufferCountMin(1), nBufferCountActual(60), nBufferSize(81920), nBufferAlignmen(16)Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::AllocInputBuffers component(_scheduler) - port(150), nBufferCountMin(1), nBufferCountActual(100), nBufferSize(1024), nBufferAlignmen(16)Ġ0:00:00 T:0 DEBUG: COMXCoreComponent::AllocOutputBuffers component(_scheduler) - port(151), nBufferCountMin(1), nBufferCountActual(1), nBufferSize(1024) nBufferAlignmen(16)Ġ0:00:00 T:0 DEBUG: COMXVideo::Open - decoder_component(0x0x17f3f40), input_port(0x82), output_port(0x83) deinterlace 0 hdmiclocksync 0Ġ0:00:00 T:0 DEBUG: OMXThread::Create - Thread with id 1153053792 started ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |