When the subject of allowing multiple recording locations was brought up, I was tempted to suggest that you could use the method suggested by muzicman0, but did not. The reason was that I was not sure it would work.
I did a test last night, and then one this morning. The result was mixed (though better than I expected).
Last night I left the computer unattended (in fact I locked the computer). I specified [Filename(path)] (and [Filename(name)] separately) the path had a folder that did not exist. I was recording "BBC World News". So I specified "F:\Video\TV Recordings\BBC World News FormatDate([date recorded, 0], yyyyMMdd)\". The last part I expected to come out to be "BBC World News 20161006", and it did not exist.
As a result, this morning when I unlock my computer I saw a confirmation message box about creating an non-existing folder. I clicked OK. An error was encountered. The result was that my jtv recording was in an unusable state. MC started moving the files, and a bunch of temp files were created, but nothing was moved to specified folder (which remained non-existent).
This morning, I did not specify the last part of the path, but just gave it an existing folder. In the end, the move was completed without any fuss, except that MC asked whether I wanted to delete the empty folder. The only problem I have is that, since I recorded in jtv format, all chunk files and helper files are moved into the existing folder without creating a separate folder for the recording itself. So it is a bit messy.
I have not tried recording in TS format. But I think it will work better since it does not need a separate folder per recording.
So to make it work, you should only specify a path that does exist. Counting on MC to create a new folder is troublesome because you need to be present to confirm. I would say, this feature works more or less.
I will make an improvement when I have time, so that we record directly into the specified folder, and create the folder if it does not exist, silently, at recording start time. This should solve both the problems I observed. Notice that I already added special coding to handle [Filename(name)] at the recording start time. I did not handle [Filename(path)] because it requires more changes inside the TV engine, which currently does not allow externally specified recording location.