Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
What do you think about this? Is *.mpg also appropriate for h.264 encoded files?
Klaus
On 4 Jan 2009, at 20:55, Klaus Schmidinger wrote:
What do you think about this? Is *.mpg also appropriate for h.264 encoded files?
Surely the move to native h.264 and dvb-s2 support and transport stream recording would ultimately call for incrementing the major revision number of vdr, so the file extension would then naturally be .vdr2? :)
Hello,
On Sun, Jan 04, 2009 at 11:55:07AM +0100, Klaus Schmidinger wrote:
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
What do you think about this? Is *.mpg also appropriate for h.264 encoded files?
I would prefer .ts, as this stands for transport stream and it is widly spread. Konqueror can be reconfigured to threat the file "correct".
Greeting, Artem
I also vote for '.ts' :-) '.mpg' is definitely the wrong extension for that.
Thanks....
-----Ursprüngliche Nachricht----- Von: vdr-bounces@linuxtv.org [mailto:vdr-bounces@linuxtv.org] Im Auftrag von Pertti Kosunen Gesendet: Sonntag, 4. Januar 2009 12:20 An: VDR Mailing List Betreff: Re: [vdr] Which extension for TS files?
Klaus Schmidinger wrote:
What do you think about this?
I vote for .ts, it's widely used on different programs and hardware media players.
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 04.01.2009 11:55, Klaus Schmidinger wrote:
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
What do you think about this? Is *.mpg also appropriate for h.264 encoded files?
AFAICT the "norm" is to name the suffix after the container-format used, not what is stored inside the container. (Or would you use different suffixes for different types of files you put into a .tar-Archive?)
So as .ts is the container it should be the appropriate suffix.
Bis denn
Klaus Schmidinger ha scritto:
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
What do you think about this? Is *.mpg also appropriate for h.264 encoded files?
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
I vote for .ts extension too, since most application use it (same situation for program streaming .ps) ;-)
On Sun, Jan 4, 2009 at 8:37 AM, Diego Pierotto vdr_mlist@tiscali.it wrote:
Klaus Schmidinger ha scritto:
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
The obvious choice is of course .ts as every app I've ever seen/used that handles transport streams uses it by default. Using .mpg would be wrong for the reasons already stated. The extention (.ts, .avi, .mkv, etc) should designate the contianer, not the contents.
I don't see why VDR should have to worry Konqueror's problems. If the Konqueror devs made the mistake of assuming *.ts is a quicktime file, it's up to them to fix it, not VDR to do something goofy to compensate for it! Or if Konqueror offers an option like 'Open With' with and a 'always use this' checkbox like Windows Explorer then users can control it themselves.
If this is a vote, then I say .ts without question.
Klaus Schmidinger a écrit :
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Nicolas,
You right. For example I'm keen of LinuxMCE (www.linuxmce.org) and it has a script that looking for media files, thus all .vdr are recognised as a video files of VDR while is not. It would would be a very wise step to improve this at the same time...
On Sun, 2009-01-04 at 19:21 +0100, Nicolas Huillard wrote:
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Vladimir Kangin
On Sunday 04 January 2009, Vladimir Kangin wrote:
You right. For example I'm keen of LinuxMCE (www.linuxmce.org) and it has a script that looking for media files, thus all .vdr are recognised as a video files of VDR while is not. It would would be a very wise step to improve this at the same time...
Without knowing a thing about LinuxMCE, I suppose its scripts could be improved to only look for <numbers>.vdr. For example, if it uses find(1), instead of
find /some/dir -name '*.vdr'
...it could do:
find /some/dir -regex '.*/[0-9]+.vdr'
...or if "-regex" is a problem, perhaps even simply this would be an improvement over '*.vdr':
find /some/dir -name '???.vdr'
(This is not in any way an objection to the renaming plans discussed here lately, the outcome of that seems good to me.)
On 04.01.2009 19:21, Nicolas Huillard wrote:
Klaus Schmidinger a écrit :
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
Klaus
Klaus Schmidinger a écrit :
On 04.01.2009 19:21, Nicolas Huillard wrote:
file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
Having no extension at all can also be a problem in itself (I'd personnaly be OK with it, but some may argue). Since the extension should match the content type, what about this: index.bin info.txt marks.txt resume.bin ...
On 04.01.2009 22:34, Klaus Schmidinger wrote:
On 04.01.2009 19:21, Nicolas Huillard wrote:
Klaus Schmidinger a écrit :
Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player.
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
I'd suggest .dat for binary and .txt for text content. More or less another "container" question. :-)
Bis denn
On Sun, 04 Jan 2009 22:34:17 +0100 Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
I would vote for that. Having .ts for the recording has the nice effect that media-players and who knows what can just handle the recordings. The other files I would consider VDR private data which is not standardized like TS. So I do not see a point in them having any extension at all. If they are in a .rec-directory it should be pretty clear what a file named "index" contains.
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Greets Malte
On 05.01.2009 00:34, Malte Schröder wrote:
On Sun, 04 Jan 2009 22:34:17 +0100 Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
I would vote for that. Having .ts for the recording has the nice effect that media-players and who knows what can just handle the recordings. The other files I would consider VDR private data which is not standardized like TS. So I do not see a point in them having any extension at all. If they are in a .rec-directory it should be pretty clear what a file named "index" contains.
I also strongly tend to drop the '.vdr' extensions and have the files just named plain "index", "info", "marks" and "resume".
Klaus
On 05/01/2009, Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
I also strongly tend to drop the '.vdr' extensions and have the files just named plain "index", "info", "marks" and "resume".
Klaus
I suppose if the manual page is updated accordingly it shouldn't be a problem (:
On 05.01.2009 11:01, Klaus Schmidinger wrote:
On 05.01.2009 00:34, Malte Schröder wrote:
On Sun, 04 Jan 2009 22:34:17 +0100 Klaus Schmidinger <Klaus.Schmidinger at cadsoft.de> wrote:
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
I would vote for that. Having .ts for the recording has the nice effect that media-players and who knows what can just handle the recordings. The other files I would consider VDR private data which is not standardized like TS. So I do not see a point in them having any extension at all. If they are in a .rec-directory it should be pretty clear what a file named "index" contains.
I also strongly tend to drop the '.vdr' extensions and have the files just named plain "index", "info", "marks" and "resume".
dropping the extensions is bad for windows users, since files without extension cannot be assigned to a specific application (like notepad).
so i vote for the suggestion of Matthias Schniedermeyer: .dat for binary (e.g. index.dat) .txt for text content (e.g. info.txt)
Greets Andreas
On 05.01.2009 19:06, Andreas Besse wrote:
On 05.01.2009 11:01, Klaus Schmidinger wrote:
On 05.01.2009 00:34, Malte Schröder wrote:
On Sun, 04 Jan 2009 22:34:17 +0100 Klaus Schmidinger <Klaus.Schmidinger at cadsoft.de> wrote:
I think the option is clearly defined now. I little thing that always annoyed me was that every recoding file had the .vdr extension, whatever the actual contents (it seemed like the file name was used as an extension). See: index.vdr info.vdr marks.vdr resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the ".vdr" part away altogether?
I would vote for that. Having .ts for the recording has the nice effect that media-players and who knows what can just handle the recordings. The other files I would consider VDR private data which is not standardized like TS. So I do not see a point in them having any extension at all. If they are in a .rec-directory it should be pretty clear what a file named "index" contains.
I also strongly tend to drop the '.vdr' extensions and have the files just named plain "index", "info", "marks" and "resume".
dropping the extensions is bad for windows users, since files without extension cannot be assigned to a specific application (like notepad).
so i vote for the suggestion of Matthias Schniedermeyer: .dat for binary (e.g. index.dat) .txt for text content (e.g. info.txt)
I've already dropped them. Besides, these files are just auxiliary internal files for VDR's very own purposes. There should normally be no need to edit them at all.
Klaus
-
Andreas Besse -
Artem Makhutov -
Diego Pierotto -
Hendrik Müller -
Klaus Schmidinger -
Malte Schröder -
Matthias Schniedermeyer -
Nicolas Huillard -
Pertti Kosunen -
Theunis Potgieter -
Torgeir Veimo -
user.vdr -
Ville Skyttä -
Vladimir Kangin