Thanks to esm for quick reply.
Unfortunately I don't want to use win 2000, It sucks! Must
be one of the worst OS's ever been programmed. So I guess
what you are saying, is that Vegas can not handle large
files. If this is true, it must count as being a very
serious omission from what seems to be an excellent
program. Please fix immediately if not before. I also have
a program from Mainconcept which does handle large files,
but the program has lots of bugs. (nothing to do with the
file handling).
More info please!!!!!!
RichardG

Hi,

>I don't want to use win 2000, It sucks! Must
>be one of the worst OS's ever been programmed.

Why?

Bye

By the way, it's not Vegas that's the problem. It's
Windows. Vegas doesn't put a file size limit on anything.
It's Windows that does that. Windows 98SE and previous have
a file size limit of 2GB. Windows ME has a limit of 4GB.

Hi,
Rockaway17, Sorry to argue with you, but it is Vegas that
is the problem. The point is that Windows98 file system
puts a limit on the maximum size of file we can use, An
operating system restriction. It is up to the programmers
at Sonic Foundry to overcome this restriction as have other
programmers. You can't just turn round and say "Use another
operating system like Windows2000!" My system is fine using
Windows98me. I have alot of software and hardware which
will not run on Windows2000. So I don't intend changing for
one program. I feel that this is a major problem for Vegas
and one in which Sonic Foundry should concentrate on in
solving. The rest of the program is superb.
Regards
RichardG

We will be providing a workaround for the FAT32 file size
limit a future release.

Thanks once again SonicEPM for the reply.
It's good to see that you take an active interest in what
your end users need. However, while you fix the problem,
what do you suggest we video makers do?
I see I'm not the only one who needs to exceed the 4gig
limit. Suggestions from other users would be appreciated.
But please do not suggest using windowsNT or Win2000 'cos
I'm just not interested. :-)
Many thanks.
RichardG

I have heard of many users doing all they're editing in
Vegas and then using other programs like Studio DV to put
many clips together or being able to play back files larger
than 4gig with that program. Sorry I don't have personal
experience with this, because I do very little video. I
don't like win2k yet either, I'm more use to win98 and have
a hard time finding a lot of tools in win2k. For one I
can't figure out how to shut off "auto-play/auto insert"
when I insert a CD, and this is a big pain in the ass, when
I'm trying to digitally rip 1 track and it opens up Siren
and starts playing the CD.Anyone know how to shut this off
in win2k?

Thanks,
Brian Franz

Don't give up on Win2k yet. I had same problem finding
stuff, but now that I'm used to it, I LOVE it and can't
stand anything else.

The HELP is great. To find things you used in other
versions of Windows, Win2k has a set of stuff to guide you.
Trouble is, I don't know how to get there directly cuz I
stumbled on it while looking up CLIPBOARD, so this is how
indirectly:
Start Menu
Help
Search
Type "clipboard" in blank field. Press "list topics".
One of the topics that comes back is "If you've
used windows before" so click it and there's a whole list
of topics to help you.
And incidentally the "help" is great. Take a few minutes
and just browse the "table of contents" to give u idea of
what is available. Win2k has so many great "systems" type
features and it's made for big stuff with no limits. For me
it is so stable I can't believe it, even tho I have several
Vegas Video's, a Photoshop, and the Net going at the same
time.
Sorry, I don't know how to keep the CD from playing.

Hi all,
Turning AUTOPLAY OFF IN 2000 IS AS FOLLOWS:-


1.. Double-click My Computer.
2.. On the Tools menu, click Folder Options, and then click
the File Types tab.
3.. In Registered file types, click AudioCD, and then click
Advanced.
4.. In Actions, click Play, and then click Set Default.

Note:
a.. You can temporarily disable AutoPlay by pressing SHIFT
while you insert an audio CD.
b.. Repeating steps 1 through 4 enables AutoPlay.
c.. When Play is displayed in bold, AutoPlay is enabled.
When Play is not displayed in bold, AutoPlay is disabled.
Thanks again for answering my messages, unfortunately I
still don't have an answer to the problem. I guess I will
have to find some other software. This is getting expensive.
It was just too good to be true, to think that vegas was
just the ticket, the answer to my prayers :-)
Regards
RichardG

That doesn't really disable Autorun under Win2K ... If I am
not mistaken all that does is disassociate that file type
from being played by the CD Player.

According to Microsoft, here is the correct way to disable
AutoRun under Win2K:

Open Regedit on the run line and go to

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\CDRom
1

To disable the Autorun feature, change the Autorun value to
0.

To enable the Autorun feature, change the Autorun value to
1.

KAC ...

About Windows 2000, I can tell that it is much better than
Windos 9x or Windows Me.
At this moment I have avery stable system, I do not get any
GPF or blue screens. It is much faster; my hard disk
delivers up to 32MB/seg while on the same hardware Windows
9X only gave me about 20MB/seg and the cache memory is
incredible. Adobe Photoshop loads in 10 sec and reloads in
just 3 sec with all the plug-ins.
About the hardware, it is true, there are many problems. I
have to change my parallel Zip drive for a USB. I found no
way for it to work.
I have to download patches for my HP scanner, for my
digital camera and the HP CD-Writer, but besides the Zip
drive, every thing was solved with software.
To install Windows 2000 I recomend a good chipset for the
motherboard; this is very important.

I'm not sure why RichardG continues to proclaim that the 4g
limit is a Vegas shortcoming. The same shortcoming is
present in any capture program, and is clearly a function
of the FAT32 file size limitation. That some programs
provide a work around doesn't change the fact that they are
still working within that file size limitation.

If Richard wants to be precise, he can acknowledge Vegas'
obvious weakness as it relates to output to tape, as there
is no function that allows outputting seamless batches of
avi's so that the net effect of output exceeds the FAT 32
limit.

I take pleasure in Sonic's assurance that the function is
under development. To me, SF appears to be a solid
company, with a great reputation, and, among my set of
tools, the VV has merits which make me want to stick with
it inspite of the fact that it isn't "complete" yet.

I am one of those who presently uses StudioDV to import
Vegas-edited avi's for assembly. Studio has it's own set
of problems, but, if you are patient and willing to inform
yourself of the work-arounds, it is a good tool with which
to string Vegas avi's together. Like VV, there is a
constant string of requests from users wanting more
features or better working features, and, hence, a major
upgrade of that program is in the works at this moment.

From what I read, while a very competent program in its
class (especially for the money), the upgrade will still
leave it short of Vegas in the editing department. Until
Vegas puts together a complete output module, however, SDV
will continue to outshine VV as an output to tape tool.

I, too, find Win2k more stable than anything on the Winx
side. Just try terminating a program via task manager in
Win2k and compare that with the effort required to
terminate in Winx-whatever.

Win2k delivers first time, everytime. Winx almost always
takes longer and requires more than one set of redundant
keystrokes.

By the way, the FAT32 file size limit is 4G in Win98FE,
Win98SE, and Win98ME, and also in Win2k if you configure
using FAT32. I've reached that limit in all these
operating systems. The limit is a function of the file
system, and is not operating system specific. The 2G
limit, if memory serves me correctly, was a function of
FAT16.

Caruso

Thanks Caruso for your comments. I am not concerned with
file limit on capture. What I do want to do is to record
back to dv tape a 60 minute movie. Vegas does not allow me
to do this. Or to be precise the windowsME operating system
or should I be even more precise the FAT32 file system does
not allow me to do this. Now all I asked in my first post
was how to work around this problem. I was advised to
change the OS. to win2000. I may do this in the future, but
at this moment in time, for various reasons, I don't want
to. There are other programs which will split the avi into
fat32 chunks and then seamlessly print them to tape when
required. Why doesn't vegas do this? I think vegas is an
excellent program and I congratulate the programmers on
their achievement. Sonic Foundry make good software. This
is the only fault or limitation I can find. There must be
other users who have or are finding the same problem. What
are they doing? I have heard studiodv or dvstudio mentioned
which will actually do file splitting. Is there a download?
Keep the comments coming!!! :-)
RichardG

I have a zip 250 parallel drive. It works fine under win2k.
I never downloaded any special drivers or anything, it
worked immediately after I installed win2k.

ive used vegas video on a sony system before..the problem i
encountered was that vegas video doesnt exactly write
dvgate friendly avi files..i would have to import using
sony dvgate to be able to batch capture , then render to
ntsc dv and export using vegas video capture...so even with
the sony i was limited to a 2 gig/ 4 gig file size limit ,
only because vegas video capture cant print to tape more
that 1 file at a time....

- eddie -

Hey, Richard. Thanks for the response. You and I actually
share the same frustration. StudioDV in theory assemlbes
multiple AVI's seamlessly. However, SDV has a problem
playing those SDV's seamlessly to tape. Some garbage
involving codecs.

I currently am working with about 35 minutes of family
video shot back in 1987. Vegas did a remarkable job of
restoring underexposed areas of the footage, a fantastic
job of editing, complete with slo-mo, exposure adjustment,
and other special FX.

After posting my message yesterday, I downloaded the 2.0d
version of the software and installed it.

It would appear that avi's rendered in StudioDV then
imported to Vegas run from the timline much more
reiliably. My 35 minute family video recorded to tape with
only three momentary (but noticeable) video glitches (bugs
the @#$% out of me).

If I (or SF) could get view to external (from timeline)
working flawlessly, that would solve my problem.

Present incarnation of the software brings one very close.

The Pinnacle product still suffers from a hiccup or two
which prevents me from completing the same project.

Using StudioDV, I have imported 4g segments (ok, one 4gig,
one less than 4gig segment) edited (very skillfully, I
might add) in VV2.0b, rendered them, them tried printing to
tape.

Everything works just fine, except that, at one particular
point in the "production" there is a video hiccup after
which sound is out of sync.

I've tried any manner of workarounds to defeat this hiccup,
none, to date, have been successful.

To my knowledge, StudioDV is not available as a download,
but, I don't know for sure.

The program (as programs go) is a bargain, sub $100.00
purchase, is very capable within it's design constraints.

For my money, I'd be happy if SF could make "view to
external monitor" reliable (would also help if there was
some way to enable sound preview) so that I could assemble
miles and miles of rendered avi's and output them to tape
(by the way, I captured sound from the external preview
playback to my S-VHS vcr via my soundcard output
jacks . . . haven't figured out a way to accomplish this
via the camcorder/pc firewire connection yet).

Fortunately, I do this because I'm curious, and find it
fun. Glad I don't have to meet any deadlines.

Looking forward to your response (or the response of
others).

JC

One more thing . . . my work around on the sound issue as
regards preview to external via the timeline, is to hook
RCA cable from sound card to S-VHS recorder.

Results are acceptable, but, of course, there is not DV
recorded archive from which to make future copies.

JC

Lil: As I see it, the inability of VV or VC to print more
than one AVI to tape at a time is precisely the problem,
which, once solved, should make this package premiere in
its class.

Hope SF is (are) listening with sympathetic ears.

JC