Opened 20 years ago
Closed 20 years ago
Last modified 20 years ago
#2061 closed defect (fixed)
Enable MPEG4 idct/ime recording profile settings
| Reported by: | Owned by: | Isaac Richards | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Patch to enable the mpeg4optionidct and mpeg4optionime options that weren't being used by NVR. NOTE: Using these options requires significantly more CPU during MPEG4 encoding.
Attachments (1)
Change History (4)
by , 20 years ago
| Attachment: | NVR_mpeg4_enable_idct_ime.diff added |
|---|
comment:1 by , 20 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 20 years ago
Turn off the mpeg4optionidct and mpeg4optionime options. Both these options require a large amount of processing power. They may have been enabled by users in 0.19 before the settings were actually honoured.
Added a warning about the high cpu usage to the help text for these settings.
comment:3 by , 20 years ago
(In [11064]) Update the help text for mpeg4optionidct and mpeg4optionime options. The real problem is that the code is not processing the data properly and can cause damaged video regardless of CPU usage. These damaged artifacts can be seen at low resolution when the CPU is not even close to being pegged (in fact, the high CPU may be a symptom of the problems while mis-handling the data).
What the user needs to know is that if they turn these on then see damaged recordings (for whatever reason) they should turn these off again as they are almost surely the cause of any new problems.
Because these option flags didn't work in previous versions, I agree that resetting them in dbcheck is a non-intrusive, good solution to prevent new complaints with 0.20.
Refs #2061
Enable MPEG4 idct/ime