I didn't like the fact that limbs were missing and/or mangled with the running players if I'd used ReplaceFramsMC on the whole frame. A disappearing or badly warped basketball didn't appeal to me any more than it would to you, if there was a cleaner way to do it.

I mean to say that the bottom of the patch was 28 pixels down from the top at both ends.

Not for defects like the one in the upper right corner:

http://www.digitalfaq.com/forum/atta...1&d=1497462659

FixRips is a last resort. There's a lot that it won't fix, and it can destroy objects at random. Besides, there were very few rips in that particular project, barely a handful of small ones fixed with RemoveSpotsMC. It had mostly defects like the one shown (and that was a commercially produced VHS tape!).

Well, I just stumbled across some BetacamSP masters of some of these tapes...unfortunately without the ability to play them, it's not much help.

In large cities in the U.S. there are shops that lease Betamax players (not free). Wouldn't know about your area.

Betamax and Betacam are entirely different things, aren't they? I imagine a consumer Beta player would be gettable on eBay or such, but I'm under the impression Betacam was the professional format. Strikes me as something that would be harder to obtain, not to mention use.

Oops. I meant BetaCam. Old habits, hard to break.

Even if I could obtain one, would it be as simple as plugging it into my current capture device via the same cables, popping the tape in, and pushing play?

I did find a place that might rent them - DigiBeta is the closest thing mentioned though - and had a look on eBay, and there seem to be a few on there that are cheaper than the rental price, oddly.

You should consider the cost of purchase/rental vs having a local post/transfer house convert however many BetaSP tapes you have. From the first page of Google results:

https://www.diskbank.com.au/transfer...cam-transfers/
http://www.procopy.com.au/video-tape-transfer-to-dvd/
http://www.ezdigital.com.au/video-to...mpeg2-mp4.html

Some Betacam players had S-Video outputs; I don't think any DigiBeta did. Otherwise, BNC composite and component. You would need BNC to RCA plugs, if you don't have them already, but they're cheap. My local electronics store charges $1.25 CAD and if you don't mind a long trip on the slow boat, eBay, AliExpress, etc. would be even cheaper.

More importantly, they only use XLR balanced audio, not RCA unbalanced. This is more of a complication.

Once you get it connected, it's just a VCR with some fancy settings and editing operations available. You'd want to ensure the proc amp is reset to defaults and then adjust if desired. Later, you could even try to see whether the TBC works as a passthrough with your other sources (unlikely, but it should be full-frame w/line, so it's possible).

Some DigiBeta players are backwards compatible with Betacam (& its SP upgrade).

I don't even know what BNC is. Some time on Google recommends avoiding S-Video.

I have no idea what any of that means.

EDIT: Created a new thread in the capturing section.

Okay so I've been going through with that ReplaceFrames script, and after 77 replacements it's apparently run out of memory?

Is that just it having to do too many things and I need to start clean? How do I work around it?

That's rather general information, but it sounds as if you're trying to run too many operations in a single script. Two ways around it. Either reduce the number of operations in that script and break it into two scripts to take some load off memory swapping, or stop and reboot to clear some RAM. I reboot a couple of times daily, or more. I've also used ReplaceFrames/FreezeFrame/BadFrames on more than 200 frames in a single script, and that was for just 1 to 5 minutes of video. I'd never try industrial-strength cleanup on an entire capture at one time.

Not sure what other information would help. It throws an error in VDub saying "AviSynth open failure: ReplaceFramesSimple: insufficient memory".

I tried deleting the last replacement, and it still doesn't load, despite that exact script having worked earlier.

I'd think that calls for a look at your script.
Or we could just guess.

Replacements 2-75 omitted because it's exactly the same code as the rest and merely takes up scrolling time and space.

44,400-plus frames? If I had heavy duty detail coding work on that many frames at once, I'd protect my sanity by moving on to a new project. In any case, your posted script snippet ran without a hitch, all the way to frame 44476. I did have to change "Source2" in your script to "Source75" in order to match up with Source75 in the next paragraph. And I had to make a special source file because yours is at least 4 times larger than the segments I usually work with, and mine are broken into even smaller individual shots. I had 47,000 frames and added another paragraph for frame 46,999. It worked.

There would appear to be much more happening in your original script, possibly some typo that's causing problems (and a "typo" could be a comma instead of a period, or that sort of thing). I seem to be a champ around here when it comes to embarrassing typos. There's too much missing here.

Not if it's attached to a post as an .avs file or .txt file, which is what I would suggest.

The whole thing is an hour and five.

Question is whether it's just running too many operations or something.

Well it worked, I added the last replacement, it stopped working, I removed the last replacement, it still wouldn't work.

The whole thing is one shot, so it doesn't really have natural break points or anything.

Thanks. I'll give it a run. First I have to convert my 47000-frame NTSC file to PAL dimensions.

OMG! I haven't worked that many frames at o0ne with heavy detail coding, just simple stuff. Disadvantage with running long files: one error means doing it all over again. Advantage with smaller sequences: catch errors early and don't repeat them with the whole video.

Going over your long script:

A sequence garbled here between 13 $ 14. It probably worked anyway.

The lines below are a waste of code and time:

It's replacing the entire frame (no crop, no patch made) and fills b01, b02 with full frames in memory. You can simplify and do the same thing this way:

I made a test file with 109,460 frames, 720x576 from a noisy VHS capture.

I ran your posted script and changed only the input file. It ran without errors.

I changed your script to eliminate unnecessary coding in the patch routines. It ran without errors on the same test file. I've attached the new script with embedded "####" comments. The code at the end replaces some long patch code with simpler and faster code.

The AssumeFPS() is so I can watch it through in slow-mo to figure out which frames need replacing/patching.

I don't understand what the 'change source #' comments mean/are for.

I figured.

This section of code appears in your original script:

This code starts with Source6 in the top paragraph and creates Source7. The next paragrpah of four lines starts with Source7 and creates Source8. The next paragraph starts with Source8 and creates Source9. Then the next paragrpah starts with Source9 and creates Source10. The last paragraph starts with Source10 and creates Source11.

What do you suppose would happen if the middle three paragraphs were commented-out or deleted, and later replaced by simpler code. After all, those three middle paragraphs don't create a small patch, they just overlay an entire frame. So let's just comment-out those three paragraphs:

AVisynth will ignore the commented paragraphs. Avisynth doesn't know what's in thosse commented lines and doesn't care. So, after the lines are commented-out, Avisynth sees only this:

The ReplaceFramesMC statements in those deleted lines will be replaced later at the end of the script. As you can see, the first paragraph in the above code starts with Source6 and creates Source7. The next paragraph starts with Source10, and....Wait a minute. What is Source10? Avisynth doesn't know what Source10 is because the lines that created Source10 aren't there. So you get an AVisynth error: "I don't know what Source10 is". And it really doesn't know, not at all.

Enter the following comment:
# ########## Change Source # in the above line to match later routine ###########

The comment means that the last line in the earlier code must be changed, and I changed it to skip Source7 and to create Source10, as shown below:

Now in the first paragraph Source7 is skipped, Source10 is created, and the next paragraph starts with Source10 as it did originally, no problem. Meanwhile, you won't need Source7, 8, or 9. The operation that those lines performed on frames 13778, 14388, and 16060 are replaced by one-line statements applied to Source76 at the end of the script, as shown below:

The memory issue does seem to be number-of-replacements related; it always starts hitting at about 90 per file regardless of the length of the clip to that point - I've had breaks of 45 minutes with no issues, or several seconds of replacing every second frame.

So I've had to just cut it up into a different AVS file every time the memory issue started happening too often, which means I've got several of them. Is there an easy way to combine them back into one file, or do I have to manually save them as AVI files and then create another AVS file with all the splices typed out manually?