So I'm been making a movie lately and I've been collecting demos from people. But it seems that all the demo ticks that are marked with prec are ~200 ticks PAST when the moment actually happens. Can someone else confirm that they're getting this or is it just me?
prec/demo indent?
posted in
Videos
So I'm been making a movie lately and I've been collecting demos from people. But it seems that all the demo ticks that are marked with prec are ~200 ticks PAST when the moment actually happens. Can someone else confirm that they're getting this or is it just me?
People have to manually hit their prec key to bookmark, probably just the time between when it happened and when they hit it. If it's on the automatic killstreak bookmarks then there might be a buffer for those but I'm not sure
People have to manually hit their prec key to bookmark, probably just the time between when it happened and when they hit it. If it's on the automatic killstreak bookmarks then there might be a buffer for those but I'm not sure
Thing is: some people looked over their demos and sent in the exact ticks. But when I make vdm's in lawena and just record them, the end part is cut out.
Another scenario is that I personally go into the demo and find ticks. But when I make vdm's and record, the end is STILL cut off.
Thing is: some people looked over their demos and sent in the exact ticks. But when I make vdm's in lawena and just record them, the end part is cut out.
Another scenario is that I personally go into the demo and find ticks. But when I make vdm's and record, the end is STILL cut off.
Another scenario is that I personally go into the demo and find ticks. But when I make vdm's and record, the end is STILL cut off.
RainmanThing is: some people looked over their demos and sent in the exact ticks. But when I make vdm's in lawena and just record them, the end part is cut out.
Another scenario is that I personally go into the demo and find ticks. But when I make vdm's and record, the end is STILL cut off.
ya vdms fuck up their tick numbers for me too, idk if it's normal but I don't think it has to do with prec
[quote=Rainman]Thing is: some people looked over their demos and sent in the exact ticks. But when I make vdm's in lawena and just record them, the end part is cut out.
Another scenario is that I personally go into the demo and find ticks. But when I make vdm's and record, the end is STILL cut off.[/quote]
ya vdms fuck up their tick numbers for me too, idk if it's normal but I don't think it has to do with prec
Another scenario is that I personally go into the demo and find ticks. But when I make vdm's and record, the end is STILL cut off.[/quote]
ya vdms fuck up their tick numbers for me too, idk if it's normal but I don't think it has to do with prec
It's really frustrating because I will go to about 1000 ticks before the mark, expect something to happen, but nothing happens. I don't bookmark for no reason, so I have no idea what this bookmark is here for and where the actual moment is.
It's really frustrating because I will go to about 1000 ticks before the mark, expect something to happen, but nothing happens. I don't bookmark for no reason, so I have no idea what this bookmark is here for and where the actual moment is.
I haven't worked with Lawena in a while (Premiere is the bane of my editing right now), but when I have, I always made sure to leave at least 500 ticks of space before and after the bit I actually want.
My process is fairly simple, but could be considered tedious:
Reviewing your ticks, whether sent by you or straight from your killstreaks.txt: I load up the demo, and go maybe a thousand or so ticks backward from my given bookmark, or just start at the tick. Usually the former, but I've done both.
I may review one small section of a demo pertaining to that set of ticks multiple times, then I right down a starting and end point for that demo. I've done this both in my killstreaks.txt for my own demos, on paper, and in other files depending on the project. These starting and end ticks are what go into the VDM generator.
It end up looking something like this: http://puu.sh/jaGa1/bd93ac3dcd.png (This was for my GXL 2014 HL demos)
As for your later post; sometimes I find I'll go through bookmarks, and there's nothing interesting, before or after the marked number. At that point, I label the bookmark as per the RuneScape game message "nothing interesting happens." It happens. Just label the tick as useless, and move on.
In short, always allow lots of space before and after your cut when recording demos through Lawena. It's often very helpful to keep track of your bookmarks: label them, note when or when you haven't recorded them, and make sure you know your starting and ending points.
Hope this helps, happy editing!
I haven't worked with Lawena in a while (Premiere is the bane of my editing right now), but when I have, I always made sure to leave at least 500 ticks of space before and after the bit I actually want.
My process is fairly simple, but could be considered tedious:
Reviewing your ticks, whether sent by you or straight from your killstreaks.txt: I load up the demo, and go maybe a thousand or so ticks backward from my given bookmark, or just start at the tick. Usually the former, but I've done both.
I may review one small section of a demo pertaining to that set of ticks multiple times, then I right down a starting and end point for that demo. I've done this both in my killstreaks.txt for my own demos, on paper, and in other files depending on the project. These starting and end ticks are what go into the VDM generator.
It end up looking something like this: http://puu.sh/jaGa1/bd93ac3dcd.png (This was for my GXL 2014 HL demos)
As for your later post; sometimes I find I'll go through bookmarks, and there's nothing interesting, before or after the marked number. At that point, I label the bookmark as per the RuneScape game message "nothing interesting happens." It happens. Just label the tick as useless, and move on.
In short, always allow lots of space before and after your cut when recording demos through Lawena. It's often very helpful to keep track of your bookmarks: label them, note when or when you haven't recorded them, and make sure you know your starting and ending points.
Hope this helps, happy editing!
My process is fairly simple, but could be considered tedious:
Reviewing your ticks, whether sent by you or straight from your killstreaks.txt: I load up the demo, and go maybe a thousand or so ticks backward from my given bookmark, or just start at the tick. Usually the former, but I've done both.
I may review one small section of a demo pertaining to that set of ticks multiple times, then I right down a starting and end point for that demo. I've done this both in my killstreaks.txt for my own demos, on paper, and in other files depending on the project. These starting and end ticks are what go into the VDM generator.
It end up looking something like this: http://puu.sh/jaGa1/bd93ac3dcd.png (This was for my GXL 2014 HL demos)
As for your later post; sometimes I find I'll go through bookmarks, and there's nothing interesting, before or after the marked number. At that point, I label the bookmark as per the RuneScape game message "nothing interesting happens." It happens. Just label the tick as useless, and move on.
In short, always allow lots of space before and after your cut when recording demos through Lawena. It's often very helpful to keep track of your bookmarks: label them, note when or when you haven't recorded them, and make sure you know your starting and ending points.
Hope this helps, happy editing!
http://i.imgur.com/3eNEvBi.jpg
I'm already on that haha. But thanks for the advice. I'll just allow some space with the ticks. I'm also going to try indenting them.
[img]http://i.imgur.com/3eNEvBi.jpg[/img] I'm already on that haha. But thanks for the advice. I'll just allow some space with the ticks. I'm also going to try indenting them.
Please
sign in through STEAM
to post a comment.