Project

General

Profile

Bug #5560

Windows prohibited characters not removed when creating subdirectory names

Added by Sterling Rorden over 5 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Adam Sutton
Category:
PVR / DVR
Target version:
4.6
Start date:
2019-02-25
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1428~gbef96c5d2-dirty
Affected Versions:

Description

Enabling "Use Windows-compatible filenames" in the Configuration/Recording/Digital Video Recorder Profiles tab will allow creation of Window-compatible filenames but not Windows-compatible subdirectory names.

For example, when "NCIS: Los Angeles" is scheduled to record it will start recording and immediately complete the recording. The recording appears in the Digital Video Recorder/Removed Recordings tab with a "file not created". The name for the subdirectory to be created appears in the Digital Video Recorder/Autorecs tab as "NCIS: Los Angeles". Removing the ":" allows the subdirectory to be created and the recording successfully completes.

Suggested change is to have the "Use Windows-compatible filenames" include subdirectory names or have a separate option in the Subdirectory Settings to use Windows-compatible subdirectory names.

History

#1

Updated by Jaroslav Kysela over 5 years ago

  • Target version set to 4.4
#2

Updated by Flole Systems over 3 years ago

  • Target version changed from 4.4 to 4.6
#3

Updated by Sterling Rorden over 3 years ago

Any particular reason this bug fix has been postponed?
Thanks

#4

Updated by Flole Systems over 3 years ago

Yes, lack of developers and I finally wanting to get a release out soon. Everything still open and on 4.4 was moved to 4.6.

There are many users still on 4.2 and they should really update to the current codebase. If someone implements this in time it will be in 4.4, so this is not a "this won't be in 4.4" but more a "4.4 will be more or less the current codebase which doesn't contain this fix yet and nobody is working on it to my knowledge".

#5

Updated by Sterling Rorden over 3 years ago

I understand. Honestly, I probably won't be upgrading Tvheadend any time soon anyway.
I'm running version 4.3-1784 that someone had ported over to the Shield TV. The author has gone MIA. Unless someone else compiles a version that runs on the Shield TV (it's probably beyond my skillset) I'll need to invest in some more hardware to run Tvheadend. I figure it is just a matter of time. I cringe every time there is a Shield TV update. My main hesitation is the combination of running the Tvheadend frontend and backend on the Shield gives me very snappy response. I'm concerned I may loose that if I go to a dedicated Tvheadend server and a separate client.

Also available in: Atom PDF