This content has been marked as final. Show 27 replies
Set M-frames and N-frame both to 1 (so that it's I-frames only)
Bitrate: 100Mbps (or higher, if you can spare the disk space)
Audio: PCM (no multiplexing)
Thanks Jeff. So there is no way to create a muxed file that contains both the video and audio tracks? I guess it's not a problem if I can't, but it would make file management a bit easier (especially with the multiple exports I need to do).
>So there is no way to create a muxed file that contains both the video and audio tracks?
You should try it. I never have. I prefer elementary streams in all cases.
AME seems to throw an error whenever I try any of the muxing options with PCM audio. Didn't know if that was by design, or if I was doing something wrong. Seems to me that I've had DVD-sourced MPG files with muxed PCM audio, but I might be delusional :)
Thanks again for your help!
You're welcome. :)
Colin -- are you certain you have the very latest version of the Lagarith codec? I have not had any issues like that since I started using 1.3.19.
I'm with Dan. I had some Lags issues as well until I updated it. Not a once since.
Yes, I'm running 1.3.19. I thought it was happening on just my primary editing workstation, until I ran 10 encodes on my laptop and got the same random issue. I'll have to post a frame to show you what I mean. If it was repeatable, I could try and diagnose the issue, but the garbage happens randomly.
I'm running the 64-bit version of the codec--at least I think I am. It seems to me that the installer copies the 64-bit version of the codec to the System32 folder, and the 32-bit version to the SysWOW64 folder. Also, if you right-click on the DLL and check the file properties, the version states as 1.3.18; the actual interface when you select Codec Settings in an app, however, shows 1.3.19. Very peculiar...
Note that this only seems to be happening when exporting a timeline through AME. I can encode to an AVI from AE, and haven't been able to reproduce the bug.
I'm trying to get some information together, and I'm going to try contacting the codec author. He seems very receptive to bug reports, based on the changelogs on the Lagarith website.
The following are a couple of screen grabs from a Lagarith-encoded AVI showing the garbage frames. Note that this is hardly a complicated sequence: DV 29.97 Widescreen, containing a mix of XDCAM EX 1920x1080 resized to fit the DV frame and DVCAM media with no effects or transformations...
From DVCAM portion of timeline, and from XDCAM EX portion of timeline.
I didn't use Lagarith too frequently prior to CS4 and Vista 64, but without frameserving capability, it was what I turned to first. Obviously, I can't use it if it's going to through miscellaneous garbage. This happens on both systems, incidentally. Seen anything like this?
I've never used the 64-bit version, and it's not even installed on my system.
Try uninstalling it and using the 32-bit version instead.
Do you use the installer, or just the package with the INF you right-click and select install?
Yeah, that's weird alright.
Ah, even better.
If I uninstall Lagarith and remove all traces of it, and then reinstall the 32-bit only version, the encoder is not recognized by any application, and files encoded by Lagarith cannot be decoded and played back.
> If I uninstall Lagarith and remove all traces of it, and then reinstall the 32-bit only version
No, you need the 64-bit version (which includes both 32 bit and 64 bit versions).
Sorry for your LAGS troubles... write the author and show him the errors. He seems to be good about making fixes when problems are found.
Thanks Dan. You're right--that's the only way I can get my system to recognize the codec for encoding and playback.
Another issue I'm having (when able to successfully encode) is that Sorenson Squeeze crashes out when I try import a Lagarith-encoded file. The only way I can get them in is to install ffdshow and enable a few random decoders. Obviously, I'd prefer not to have to do this. Anyone use Squeeze + Lagarith - ffdshow successfully?
Oddly enough, one of the crashing components is "quicktime.qts"--what QuickTime is doing touching an AVI file with a non-Apple codec is completely beyond me.
Strange, Colin --- I use Squeeze with Lagarith sources all the time, sans-issue. I have ffdshow installed, but it is not being used by Squeeze.
The only problem I've ever had is when "Enable Null Frames" is checked the Lagarith options -- this causes Squeeze to skip a bunch of frames, but no crashes... ever.
> what QuickTime is doing touching an AVI file with a non-Apple codec is completely beyond me
F'in' QuickTime ?!?
I'm going to guess that this is a complication arising from Squeeze and QuickTime not being 64-bit, but who knows. It's funny--I remember before I wiped my laptop and reinstalled everything from the ground up, that I was able to bring Lagarith AVIs into Squeeze, and I didn't have ffdshow installed...
That sound? Oh, that's my head exploding.
> I'm going to guess that this is a complication arising from Squeeze and QuickTime not being 64-bit, but who knows.
I doubt it. It is more likely an issue with QuickTime itself or perhaps Vista (I am on XP64). But maybe these are just my anti-Vista, anti-Apple prejudices speaking.
Please do write the LAGS author and keep us posted on what he says about the "glitching".
Why does Colin need the 64-bit version? I have the 32-bit version *only* and I have no such problems.
> Why does Colin need the 64-bit version?
Well, it's not that he needs the 64-bit version of the codec, just the 64-bit installer. Basically, 32-bit codecs that are installed via an .inf tend to go in the /system32/ folder (instead of /SysWow64/) which is a problem. Codecs that have .exe installers do not tend to have this issue.
I am actually curious how you got the 32-bit .inf install to work on your 64-bit machine!
I didn't. I used the .exe installer.
Here's a weird one for you: using a program called inspectExe you can check out the properties of system files, like DLLs. It will tell you whether a file is 32-bit or 64-bit.
So here's the lagarith.dll file that appears in the C:\Windows\System32 folder...
And here's the lagarith.dll in C:\Windows\SysWOW64...
In other news, I'm testing out sending my PPro timelines to AE, and rendering to Lagarith AVI there, ala QuickTime in AME pre-4.0.2. So far, so good.
In Vista 64, the System32 folder is really the "System64" folder. SysWOW64 contains the 32-bit files for 32-bit applications.
Same in XP64, Jeff... that's what I meant. Did you install via the .inf or did you use the .exe installer (which handles all versions of Windows, allegedly)?
> In Vista 64, the System32 folder is really the "System64" folder. SysWOW64 contains the 32-bit files for 32-bit applications.
Wow. Leave it to Microsoft to defy logic. Thanks for the explanation.
>Wow. Leave it to Microsoft to defy logic
WOW64 is the 32-bit emulator in 64-bit Windows. 32-bit applications never know that they're running on a 64-bit system, so the WOW64 emulator has to direct everything to the right place to keep the 32-bit files and the 64-bit files separated.
I've been told that the System32 folder in 64-bit Windows is called that instead of System64 for the ever-popular "backward compatibility".
Backward compatibility... <shiver><br /><br />Nothing has held the Windows platform back so much as backward compatibility. I suppose that's the price to pay when you're on the majority of desktops.<br /><br />Thanks for info, Jeff--interesting stuff.