Hello,
I'm looking for a way to cut recordings using the vdr (on a different machine), but I don't want the new recording on the same disk as the origin - normally the disk of the recording has no free space, when I like to start cutting.
So I tried to fake the video-root to get the new recording to another disk.
I tried to link the recordings title directory to a disk, where I do have free space and startet the vdr like this: vdr -v /path-to-disk-with-free-space --edit=/linked-directory-on-disk-with- free-space
With that call I got the error message, that the recordings title directory is not a directory. So I tried to change things. I created the title-directory on the disk with free space and linked the timestamp-directory to the original recording.
Trying again to cut that recording - vdr keeps on claiming, that the recordings title directory is not a directory. But this time it is a directory!
So how can I cut the recording without having to copy it to a new drive?
kind regards
Gero
Am Montag, den 10.01.2011, 08:49 +0100 schrieb Gero:
So how can I cut the recording without having to copy it to a new drive?
Take the next step and do:
mkdir -p <target>/<title>/<*.rec>
Then link every file from the original source to <target>/<title>/<*.rec>/.
e.g.:
(vdrcut source target 00:00:05.00 00:00:10.00)
Tobias
Hello,
Tobias Grimm wrote:
Thank you for the hint. I'll try it.
(vdrcut source target 00:00:05.00 00:00:10.00)
I gave it a quick look, when you first posted it. I have no idea about ruby, but when I found that 'mv' - stuff - I thought: no, that's not, what I was looking for - I try to avoid any 'mv' or 'cp'.
May be I got confused with that ruby stuff, so I try your hint.
kind regards
Gero
Hello,
Tobias Grimm wrote:
Sorry, but it does not work here. I did not try your script, but called vdr by commandline. Same error message than before: "<target>/<title>" is not a directory.
I verified, that the whole path til <*.rec> does not contain any link and I linked every file from the original <*.rec> directory.
The vdr-recordings are exported readonly. Could that be a problem? Ownership and permissions are ok.
kind regards
Gero
Hello,
Gero wrote:
I think I got it.
Looks like vdr has a problem with directories, that start with a dot. The read/write state of the exported fs did not change anything, but when I renamed the directory, that started with a dot, vdr started to cut the recording.
Don't know, whether this behaviour is intended.
kind regards
Gero