I guess you mean adjusting comskip.ini values.
I could just disable Logo as a detection method, but that would affect detection a lot.
So, the likely candidates would be Logo finding, i.e. border, give_up_logo_serch, etc.
Any suggestions?
Search found 3 matches
- Fri Jan 06, 2023 6:53 pm
- Forum: Support
- Topic: Could not allocate memory for logo frame buffer
- Replies: 4
- Views: 1805
- Fri Jan 06, 2023 2:14 pm
- Forum: Support
- Topic: Could not allocate memory for logo frame buffer
- Replies: 4
- Views: 1805
Re: Could not allocate memory for logo frame buffer
The DS218J has 512MB of DDR3 memory and a 2GB swap file.
Previously comskip had previously run sucessfully, so must be a close thing. Any suggestions to reduce RAM usage, etc. to get it working again?
Previously comskip had previously run sucessfully, so must be a close thing. Any suggestions to reduce RAM usage, etc. to get it working again?
- Fri Jan 06, 2023 11:13 am
- Forum: Support
- Topic: Could not allocate memory for logo frame buffer
- Replies: 4
- Views: 1805
Could not allocate memory for logo frame buffer
Having previously had comskip running sucessfully from a post processing script in TVHeadend, it has stopped working and has the following message in the log file (after the comskip.ini information) "Could not allocate memory for logo frame buffer" 36 or 37 Any suggestions? The hardware is...