If you use a POV demo the player will NOT show in 3rd person shots (smooths).
I think this is because the player is still bound to the camera, so the game kinda moves the player itself to watch the game from a different perspective - this is at least how I understand it.

With STV demos it should work!

Sorry for my bad english >:D

Thanks for the explanation, understood perfectly. I'm still experimenting a lot with smooths so I wasnt aware of this.

STV demos can't be smoothed tho :(

If you're willing to spend a few days figuring out how it all works, HLAE + Cinema4D 11.5 (must be version 11.5) will let you do this. It's what I used to make this video.

There are no really good tutorials out there and I'm at work so I can't make any in depth guides at the moment, but the gist of the workflow is as follows:

1. Record your demo.
   
2. Using this wiki page (scroll down to the bottom where it links to mirv_camexport) as a reference, export the camera path from the part of the demo you'd like to use.
   
3. Install the Cinema4D plugin and import your camera data. (Note: I didn't realize there were also plugins for 3dsMax and After Effects! Might be better to use one of those programs if you already have them. I will say that Cinema4D might be the best tool for the job, though. Lots of camera keyframing options and it's built from the ground-up to do this kind of 3d work.)
   
4. At this point, you will have a camera path in your C4D workspace, but nothing else. You will need to import the map played in the demo so that you have some idea of where the camera is in relation to the game world.
   
5. Export the map as *.obj with Crafty.
   
6. Import the *.obj into C4D. There are a few ways to do this, I used Riptide. Note that I haven't figured out a consistent way of getting textures imported, but they are not necessary. The map here is just used as a visual reference for you when creating the new camera path, nothing more.
   
7. Add a camera to your C4D scene and make a path for it with keyframes. Controlling C4D can be very odd at first, but you'll get used to it.
   
8. Set your scene FPS to 500, the highest it will go. This will ensure that your new camera path plays back as smoothly as possible in-game. The default framerate of 90 will have noticeable jitter.
   
9. Select your camera and export it with the HLAE exporter plugin.
   
10. Import your new camera path with mirv_camimport
    
11. Record your smooth.

There's a few oddities you may run into with this. For example, when you import maps, they may be rotated 90 degrees. Just select the whole thing and rotate it in C4D. You may also need to mess with the "90 degree fix" checkbox in the C4D HLAE exporter.

You also don't need to import/export the entirety of the demo's camera path. If you just want ticks 1000-1250, you can do that. VDM scripting of your mirv_camexport and mirv_camimport commands is necessary for this, though.

It will take you some time to get used to all the quirks of this workflow, but once you have it figured it out you will be able to iterate much more quickly and efficiently than you can with normal in-game smoothing. Plus, you can also do camera motions/rotations that are otherwise impossible.

Thanks lange, will be trying that in the future for a more lengthy project. For now I just found a quick workaround to this.

Holy fuck Lange that's incredible. What is the workaround you found Kaneco?

Since what I'm working on is a "play of the day" clip for comp.tf which is rather short I figured I could get away with it using a split screen and cover the missing player area with the second pov. Not sure how it will work in the end but it's looking ok atm. It's all about trying new things tho. So I'm up for that.

Note that you don't need to use smooth or any other angles for one clip.