Hoth-Nudist said:
"now with 40% more womp-rats!"
Haha! I must remember that one.
Yeah, 4 files unavailable here.
Hi Harmy, I too would like a PM at your convenience.
Moth3r said:
Since a 0.1% difference in speed is negligible, and Puggo will be re-syncing the audio anyway, it would be wisser to go with 23.976fps. The AviSynth command is then:AssumeFPS("ntsc_film")
Ooh, thanks, I was wondering about that.
Harmy said:
.. it seemed incredibly complicated to me, so many buttons and windows and not enough space for anything on my laptop's 15.4" monitor ;-D
The only windows that come up by default are a timeline, a preview window, an audio slider, and a file browser. You can change the file browser to any of a number of other things (for instance, if you want to browse backgrounds instead). It all fits on my 15" screen, but I do have to resize things to keep the preview window reasonably large while still viewing multiple tracks on the timeline. I make the timeline tracks as small as they'll go, and the preview window as large as I can. You're right there are little buttons all over the place, but most of them can be ignored as they are shortcuts to functions that are on the right-click menus. You only need to use a few of them at the start, like the mute and solo buttons, and the play, stop, and pause buttons.
You can generally start right out by browsing for the files you want, stacking them in rows on the timeline, and pressing play. Where Vegas excels is in manipulating the clips on the timeline... stretching, cutting, moving them around, and crossfading them is, I found, intuitive. And pretty much everything can be previewed in real time without rendering or pre-rendering, so you can try stuff out immediately as you move things around. Even Avid requires pre-rendering a lot of things that Vegas can just preview instantly.
I started out with iMovie and was impressed with its ease of use. However, as my needs became more intricate, I found myself finding it hard to get it to do the things I needed to do. The first time I fired up Vegas, I never opened iMovie again. I've also used Premiere, MovieMaker, and Avid, and find Vegas by far the easiest to use. Of course, this is my personal opinion and other people may have their own style of working/thinking.
Vegas is one of the easiest video applications to learn how to use. That is why it became so popular so quickly.
As long as he releases the original theatrical versions, I don't care what he adds to his latest "new special editions".
I definitely would like to try it - can you post your new script too? (when it's safe, of course) :) thanks!
That's a promising idea. I was wondering if there was a way of taking the bright clip and chopping out all information above 128 luma, taking the dark clip and chopping out all information above 128, and then simply adding them together.
Or maybe something slightly more sophisticated would be to do the above on the extremes (say, above 192 and below 64), and blending the center range.
Of course, there might be some strange effects I haven't considered. If there is a way of "chopping" above/below a certain luma with some small degree of fuzziness, that would probably reduce the possibility of artifacts.
I remember 1977 being a great year for movies. Star Wars had some tough competition at the Oscars.
althor, I'm curious, the script in xvid4psp says "directshowsource"... is there a reason that it doesn't say "avisource"? Does it matter?
althor1138 said:
What I mean is when you entered your captures into the script, was it cap1 or cap2 that was the darkest of the 2 captures.
The posted clip did not use your overlay script. Some of the scenes were from the bright capture, some from the dark capture.
althor1138 said:
The base clip is the "bottom"clip in overlay. The overlay clip is the clip put on top of the base clip. the base clip is always the first clip entered into the overlay filter. So the base clip in the filter below should be your darkest clip, regardless of whether it's cap1 or cap2. If they are backwards, just flip them around.Overlay(BASE clip,overlay clip,mode="luma",opacity=0.5)
Ok, that's clear. What about the first of the two scripts? this one...
reel1cap2 = avisource("PATH TO FILE")
reel1cap1 = avisource("PATH TO FILE")
blank=reel1cap1.blankclip()
inter=interleave(reel1cap2,reel1cap1,blank)
return(inter)
Does it matter which one is the darker ("base") clip?
thorr said:
You can add the black bars in xvid4psp to get it to 1280x720. I don't remember how to do it off the top of my head, and I can't get to my computer right now to try it out because my dad is sleeping in there. If you can't figure it out, I will eventually get to my computer and try to help. :-)
There isn't a rush on that. Whenever it's convenient, if you could find out and let me know that would be great. I have plenty of things to keep me busy for at least several weeks before I actually need it.
althor1138 said:
The base clip should probably be the darker clip and the overlay clip should be the lighter clip. Then change the opacity to try and find what you are looking for. opacity=1 might even work.
Ok, that gives me some things to experiment with. By "base clip", do you mean cap1 or cap2 in the script?
AssumeFPS("film") worked. Thanks!!!
The scripts for aligning and combining the clips also worked! So now I have to identify those scenes that might benefit from it, because judging from the output many scenes won't. If there were a way to have it choose pixels based on which pixel is less extreme (that is, pick the pixel closer to the midpoint, which should use the lighter source in the dark areas, and the darker source in the light areas - rather than averaging them), then it could probably be used everywhere. Hmm, I wonder if anyone has ever written a script to do that? As it is, it may only be useful for improving sections that are already pretty good in both sources.
Pretty remarkable nonetheless. I could see using this for a variety of applications besides this one.
dark_jedi said:
Puggo - Jar Jar's Yoda said:
dark_jedi said:
Got damn, that is way overkill and a half for stereo audio LOL,This is mono!
Hey, I am just commenting on what thorr said, and that is way to much, but if it is mono, it is still way to much, but ultimately, it is your decision to make, not ours.
I was agreeing with you.
dark_jedi said:
Got damn, that is way overkill and a half for stereo audio LOL,
This is mono!
thorr said:
You definitely want to encode it to 23.976 frame rate dropping extra frames from your 30 fps capture. You may also want to encode it to 1280x720.
Just to clarify, I didn't do a 30fps capture. I captured frames one-for-one into a .avi file with a DV codec. When played back, I think that a player is going to assume that it needs to be played at 30fps, so it appears too fast. Thus I don't need to drop any extra frames. (note, there are extra frames in the posted demo, because I added them after capture... but I won't do that in subsequent versions).
I've got the width stretching properly to 1280, but I'm not sure how to encode the height to 720 so that it adds black bars. Right now I'm encoding the height to 480 (i.e., leaving it as-is), and luckily VLC and GOM are adding the black bars on playback. But I'm not sure how to add them in the context of using xvid4psp for resizing. Should I resize the height to 720 in Vegas first, and then stretch the width in xvid4psp?
By the way, everyone, try out GOM player. On my 58" screen, with this clip, it does a better job than both VLC and WMP.
canofhumdingers said:
how are people playing this in windows media player? I checked to make sure mine's current but it still won't play the sample. I don't really want to dl yet another player just to see it.
Do you have Windows 7? I think that only the version of WMP under Windows 7 will play dimensions larger than 1080.
VLC is a very lightweight viewer. Another very nice one is GOM. Between the two of them, you can play just about anything.
hairy_hen said:
It's my understanding that you really shouldn't do actual pulldown to film sources--just leave the real film frames alone and tell it to run at the proper speed, adding pulldown flags during the encoding stage if need be. Hard-interlaced material wastes space and bandwidth by having to encode duplicate fields, and is just that much more difficult for de-interlacing to sort out during progressive playback.
Absolutely... PG was made with a pulldown flag. But my understanding is that HD doesn't have pulldown flags. I did the hard pulldown this time for the PSB demo because I didn't know the right way to handle it in HD... now that I'm armed with the correct method(s), the next one will be better! (and smaller).
Harmy said:
I would recommend using 23.976fps instead of 24fps, because 24fps can cause playback problems. Ady made his EpIV AVCHD 24fps and I know there were people who had to remux it to 23,976 in order to play it.
Very good to know, thanks!
thorr said:
Also, you can change the frame rate using xvid4psp. There are several options, but I think the "Assume" is the correct one as mentioned (not 100% sure).
Can I merge a separate audio file in xvid4psp?
Also, what audio settings should I use? I just used default settings for everything... any suggestions you have for tweaking it would be appreciated.
Nerfherder said:
Amazed how blue Hoth looks esp. in the wampa scene, after all the hooplah about the 2004s colour balance. Perhaps it was always meant to be that blue afterall! At any rate its grand to see Empire looking like a film again :) Plays perfectly using VLC on my Mac.
The trouble with the 2004's color balance is that other things that aren't supposed to be blue are blue. You can't tell the blue shift based on things that are already blue, but you can tell from the things that used to be white, or flesh-toned :)
Not to nit pick, but I've noticed with both the Puggo Grande and the Empire clip that there is a strange sort of 'echo-y' effect on some of the music. Almost like a vibraphone in places! Is this sort of audio effect common on 16mm film prints?
I don't know the answer to that. If both this and PG have the same effect, then I'm not too worried about it. I used a different projector to grab the audio this time, and my main concern was that the audio be comparable. I'm not sure why there would be an echo-y effect... that can happen with tape because of print-through, but that shouldn't be an issue with optical.
My way of grabbing the audio is a bit crude... I have an Elmo 16CL projector, and I simply take the 1/4" speaker output and route it into my DAT deck, adjusting the projector's output and tone levels by ear, and the record level on the DAT. The digital out of that goes straight into the computer (I have a nice RNE sound card). The only thing I adjusted on that file was to cutoff the very low end, and fix a few waves that clipped. There is probably a way of getting a better quality sound out of the optical pickup, but I've been reasonably satisfied with what I've gotten this way.
Moth3r said:
The video is easy - if you're using an AviSynth script, just add AssumeFPS("film"). This will cause the video to play at the correct speed without changing any frames.
You could also use AudioDub() to add the audio for your sync check. There's also a great filter that adds the audio waveform over the top of the video to assist with this process, I'll post back when I remember its name.
Edit - AudioGraph
Ok, I was thinking more about how I would set it up to sync by hand. Remember that audio capture is a completely separate step with a different projector than video capture. So they aren't synced at all. I have to go through stretching and shrinking scene by scene until the audio matches the video. Vegas makes that step doable, albeit tedious. But when Vegas imports DV, it assumes the wrong frame rate, which is why I've made a temporary pulldown. In PG, I discarded the version with the temporary pulldown and replaced it with the original video with pulldown flag set. In this case, I'm assuming that I'll need to replace the version with the temporary pulldown and replace it with the one that has been set to "film"?
To mux final video and audio together into the MKV container use mkvmerge.
Ok, I'll check that out. Thanks!