[Mike Smith]

https://forums.creativecow.net/cgi-bin/new_read_post.cgi?forumid=24&postid=861111&pview=t#head

https://forums.creativecow.net/cgi-bin/new_read_post.cgi?forumid=3&postid=860311&pview=t

[Mike Smith]

Apologies for the unstructured nature of these responses – I don’t have this problem and haven’t seen it, but I guess I may well in future, and others will.

Trying start / run / regedit, then searching for UserChosenExecuteHandlers produced a list of flags for me, including one for my Sony DVCAM recorder. This flag was set to MSTakeNoAction.

Editing the registry direct is risky though and not recommended unless you’re already comfortable with it – a mistake could stop your machine from booting.

[Mike Smith]

One last thought … I guess an old-fashioned hold down the shift key while plugging in / powering up the firewire device doesn’t do it …?

[Mike Smith]

Other approaches might be more drastic.

There’s an XP utility called gpedit.msc – start / run / gpedit.msc – where you can turn autoplay off or on again. Might help. Mentioned in posts at https://blogs.msdn.com/oldnewthing/archive/2005/10/25/484602.aspx

And I haven’t used the XP version of Microsoft’s TweakUi, and I don’t know if it will do this, but old versions were powerful. https://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx

[Mike Smith]

Hmm … autoplay doesn’t appear as an option for my DV deck either.

I guess you could try start / control panel / system / hardware / device manager, select the recorder (under imaging devices?) right click and scan for hardware changes …? Should find that the device has changed …

Report back if it works ..?

[Mike Smith]

To allow system access to RAM above 2 Gig on a standard Windows XP machine you need to
change a setting in the boot.ini file, called “setting the 3Gb switch”. Details follow.

AE is one of the few apps as yet which can take advantage of the extended memory space, of up to 3Gb. There are risks attached in doing this: the virtual address space available to Windows is reduced, which it’s reported can have an impact if you are running very large disc arrays and/or lots of high-resolution screen display.

For more than 3Gb of memory, you really need a 64bit version of Windows XP, which you will probably want dedicated to your video tasks – I believe a

The PAE and AWE technologies were ways to extend 32-hit operating system with a 36-bit virtual address space and supporting hardware registers – designed for high-performance SQl Server systems. PAE / AWE will not be carried forward into the 64-bit generations of Windows, which are not too far away …

https://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
https://www.gehrytechnologies.com/catia/catia/catia_windows_large_memory.htm

Proceed with caution!

[Mike Smith]

Don’t know why PPro should be crashing. Out of memory? Damaged media? Very large clips / timelines? Some non-standard plug-in not behaving? (Is the machine with PPro normally stable?)

BTW, how do you like Vegas … it seems tempting, what with the Acid-style interface and all ..?

[Mike Smith]

Athlons are high performance chips, though AMD has the Opterons which are faster. (I understand Intel has, for the first time, accepted an outside lead and is to build on chip architecture developments initiated with the Opteron.)

High speed discs, including of course a separate AV media drive, or, better, a small RAID, will help data throughput.

Plenty of RAM is good. Of course, you need a decent video (NTSC/PAL) monitor, amplification and speakers so you can see and hear what you are working on …

Overnight renders may drive you nuts. The worst isn’t the waiting: it’s the knock-on effect of inhibiting your creative experimentation.

For an expert editor, it’s a frustration. For a leaner, it puts a severe clamp on your ability to learn by trial and improvement … so speed can be good! On the other hand, a new, fast Athlon with a decent hard disc arrangement and lots of RAM should slice through most DV editing tasks …

It’s great if you can get an affordable system and produce decent results out of it. On the other hand, if it were to slow your learning and you were to produce beginner-style, tedious / unwatchable edits for longer, would that be worth the saving …?

Good luck with it.

What part of the IT industry did you retire from (I’m guessing not chip design!)

[Mike Smith]

Not sure where “should” comes from, Timothy. That surely depends on what the user wants to achieve.

Mpeg 4 / MP4 is surely here, and may become bigger – it’s made a start in the HD world in the H.264 codec, and of course DivX has made use of it, along with a Quicktime flavour and variants in Microft’s video9. If Mpeg4 takes off as a distribution format, then ability to edit it will become an asset.

And of course .avi files can run from uncompressed to very heavily compressed. Mpeg 4 of course is a broad standard, and can be used at varying compression levels.

More from adobe on this at
https://www.adobe.com/products/dvcoll/pdfs/DV_Compression_Primer.pdf
https://www.divx.com
https://streamingmediaworld.com/video/docs/MPEG4

[Mike Smith]

Interestingly, Premiere Elements 2.0 appears to support mp4 use.

see https://www.adobe.com/support/techdocs/328587.html