Recording file names no longer have underscores

[point17]

I've noticed since installing 6.6.006 (and restoring settings) that the filenames of recording files are slightly different. Whereas beforehand the filename would include the name of the TV programme with any colon replaced with an underscore, it now does not have the underscore. Is this a change, a bug, or is it that this is configurable setting and somehow I must have changed the setting?

As an experiment, I recorded the same programme on the box with 6.6.006 and on another box running an older build. The filenames were different:

• The Poughkeepsie Shuffle_ Tracing The French Connection - 20240829 2239_BBC FOUR.ts (old build)
• The Poughkeepsie Shuffle Tracing The French Connection - 20240829 2239_BBC FOUR.ts (6.6.006)

If this is the result of an inadvertent setting change, can anyone please tell me what to change to revert to the old behaviour?

Thanks,
Dan

[twol]

I've noticed since installing 6.6.006 (and restoring settings) that the filenames of recording files are slightly different. Whereas beforehand the filename would include the name of the TV programme with any colon replaced with an underscore, it now does not have the underscore. Is this a change, a bug, or is it that this is configurable setting and somehow I must have changed the setting?

As an experiment, I recorded the same programme on the box with 6.6.006 and on another box running an older build. The filenames were different:

• The Poughkeepsie Shuffle_ Tracing The French Connection - 20240829 2239_BBC FOUR.ts (old build)
• The Poughkeepsie Shuffle Tracing The French Connection - 20240829 2239_BBC FOUR.ts (6.6.006)

If this is the result of an inadvertent setting change, can anyone please tell me what to change to revert to the old behaviour?

Thanks,
Dan

what problem does this cause you?

[point17]

what problem does this cause you?

Nothing major :-) It's just that I have various folders with recording files in them and I run various bits of code to process and organise files. For example: I have code that sweeps up new recordings, looks for a folder containing items with the same programme name, and files the new recordings accordingly. I can modify that piece of code to treat two programme names as identical if they differ only in one of them having an underscore missing from the other. But it's trickier to fix, for example, sorting of a spreadsheet of programme names derived from recording names. Likewise, the revised behaviour means that recording names from recordings made on another PVR (older model that is not able to run the latest build) will be inconsistent with those made on a PVR running the latest build.

Like I say, it's not very important, but I do think it's a good general principle that the mapping from EPG programme name to recording filename works consistently the same way (or can be configured to do so).

[Huevos]

Why don't you just use collections? It is a built in feature.

[point17]

Why don't you just use collections? It is a built in feature.

I don't know anything about collections - is there some documentation you could point me to? I don't know if it would do many of the things I do, such as cataloguing recordings held on a Windows PC as well as on 3 PVRs (including one stranded on OpenViX 5.2.045), but I'd be interested to find out.

Thanks

[birdman]

You could get the recording name from the meta file. This will have it with no edited characters....

[Huevos]

I don't know anything about collections - is there some documentation you could point me to? I don't know if it would do many of the things I do, such as cataloguing recordings held on a Windows PC as well as on 3 PVRs (including one stranded on OpenViX 5.2.045), but I'd be interested to find out.

Thanks

Just turn it on and it groups programmes with the same name.

[point17]

You could get the recording name from the meta file. This will have it with no edited characters....

That's true - I extract other stuff from the meta file already so it wouldn't be difficult. It's more a question of consistency with the thousands if recordings I already have and the direction I should go in to maximise consistency going forwards.

Like I say, it's not really a problem - I'm just trying to find out if this is 1) a deliberate change to the way recording files are named, 2) a bug, or 3) something configurable by the user. If the first of these then I'll maybe do a few code changes, or write something to rename all the existing recordings, or some such. If it's a bug and is likely to get fixed then I'll hold fire. And if it's a configuration setting then I'd like to revert to the former behaviour. Is anyone on the conversation able to tell me which of the three it is?

Thanks

[twol]

That's true - I extract other stuff from the meta file already so it wouldn't be difficult. It's more a question of consistency with the thousands if recordings I already have and the direction I should go in to maximise consistency going forwards.

Like I say, it's not really a problem - I'm just trying to find out if this is 1) a deliberate change to the way recording files are named, 2) a bug, or 3) something configurable by the user. If the first of these then I'll maybe do a few code changes, or write something to rename all the existing recordings, or some such. If it's a bug and is likely to get fixed then I'll hold fire. And if it's a configuration setting then I'd like to revert to the former behaviour. Is anyone on the conversation able to tell me which of the three it is?

Thanks

Its a code change to better handle file names etc … fixes a few issues on the original code and so not a bug

[point17]

Its a code change to better handle file names etc … fixes a few issues on the original code and so not a bug

OK, thanks. In that case I'll treat it as how things will be, going forwards, and make my plans accordingly. Thanks, all, for engaging in the discussion.