Frage von movingframe:
Good evening,
have a problem with Vegas 8.0c and 9.0:
the rendering process starts normally. Paging file reaches the 2GB, then the process will remain standing. Vegas needs to close it via Task Manager will. The same effect can be reproduced when a Vegas project file (; no preference which format) in the timeline of the open application via d & d is drawn. Vegas begins to render, this is but a soon as 2 GB by Auslagerungsdat. be achieved.
I described my problem to the support in Wisconsin. They advised me to version 9.0. There, the effect is completely the same. Thereafter, no further reply came. I type on a setting that manages the size of pagefile.sys IZM Vegas. The settings in XP all comply with the Standardkonfig., As in Vegas. Hauptsächlilch mxf-files I edit a Sony SD Camera.
System: XP Prof. 32-bit (; updates to date, all framework versions), MB Asus P5QC (; current BIOS) Intel C2D E 6700, 4 GB RAM, GK Ati 3850, Vegas 8.0c & 9.0 installed, latest QuickTime Player.
Tests: Progs all going well, except Vegas. Prime by running CPU at max. 60 degrees (; Turmkühler). 3DMarc, SPECviewperf, Cinebench, Everest and Dr. Hardware show good values.
Would I be pleased about feedback. In my network, this problem is synonymous with some other Vegas users encounter (; especially in the U.S.). None had a solution, unfortunately, are only stopgap solutions that run on a performance-reducing addition.
Already s.dieser my thanks
mf
Antwort von jazzy_d:
2GB? As I still type views on FAT32
Computer -> C: or write down where Vegas (; right mouse button) -> Properties -> File System?
Antwort von vaio:
"2GB? As I type but times on FAT32" Good evening!
Files on FAT32 can max. 4 GB in size. Do you have enough capacity on your drive, or your HDD / partition? Do you mean with "swap file" the "pre-rendered files" (under the project properties; menu "File / Eingenschaften")? The location of these files is the default user directory under Windows. XP did not change you - you write (; swap file, etc.).
Otherwise, what file system?
How does the system with other files (; not "mxf")?
Gruß Michael
Antwort von Marco:
You Used version 9.0 or 9.0a. With Vegas Pro 9.0a such problems are not known. Then a FAT32 partition would be more likely as the cause.
Marco
www.vegasforum.de
Antwort von B.DeKid:
Mach mal 8 instead of the virtual memory to 4GB. This once again on another partition 4 GB .....
Otherwise you would need is provided for time on / in the files of the Progs schaun to see how the distribution
...............................
@ jazzy_d and Marco
As the C partition should be FAT32 under XP, please explain ...;-/
MfG
B. DeKid
Antwort von Marco:
Is there not in the area of the impossible, that the original path has changed the paging file to a FAT32 partition.
The growth of the paging file on such securities is not yet normal for rendering in Vegas. It should therefore only be ensured that the current version 9.0a is used.
What video compression is used in the MXF clips (actually, the camera that is)?
Marco
www.vegasvideo.de
Antwort von darg:
As the C partition should be FAT32 under XP, please explain ...;-/
MfG
B. DeKid If his Rechnerkist was drilled to hire via Windoof98 update. As unlikely as it sounds but there :-)
Antwort von movingframe:
Good evening,
First my thanks for the many ideas and suggestions of all stakeholders. I apologize if I can establish no direct dialogue, it is a pure timing issue.
My answers chronologically:
@ Jazzy_d
File system is NTFS on all disks. Classic construction of the panels and partitions.
@ Vaio (; and so ...)
Plate 1) has 2 partitions: C / System 50 GB (and 30 GB free, D / 430 GB data (; free) 250th Plate 2, Raid 0 (; 2x1TB) via PCIe, so over map. On this record is the swap file. Last plate is a pure backup drive with 500 GB, also NTFS.
The system responds with all video files the same.
With the swap file pagefile.sys I mean the operating system, set under System Properties / Advanced / Settings / performance options, such as current display (through the task manager, tab: system performance). The size of the paging file of XP, I'll manage, she lies on the RAID-0 system. I localize the error as follows: I open the task manager, Vegas and other system indicators (; temperature, memory usage). ... Now I leave (any video file, such as synonymous DV, render AVI, mpeg2). The rendering process starts very quickly and the swap file grows in parallel. The paging file reaches 2GB (and after about 17 sec at mxf files) are still Vegas. The main memory is during the process with max. 1.2 GB used (in theory would be possible) and full capacity 3.3 GB.
Marco @ (, 1)
So far I have only really used 9.0, because this was the recommendation of support. I will now download 9.0a, install, and report it. We really wanted to finish the projects started with Vegas 8.0c, but the support assured me that all EDLs and effects would be no problem detected. So I'm assuming. Otherwise I would have preferred a change in the system after the completion of projects.
@ B. DeKid
I now synonymous virtual memory (on D; data) established. XP therefore represents about these other pagefile.sys 4096 MB available. Vegas rises to the change in attitude is also to reach out of 2 GB.
@ Jazzy_d and Marco
NTFS so, to C (; plate 1) the first partition only Programs (; System)
@ Marco (, 2)
Is NTFS. 9.0a'll try, but I have a difference of memory management, and utilization of the paging behavior would find astonishing. But I will make (;!!).
As far as I understand it, is merely an MXF "enveloping" format, format, no compression. This container can be present different data and codecs / transported. Importantly, Camera and editing device codectauglichen properties (some, for example, mpeg2). This here is guaranteed. I worked up my old cut're already mxf files of the camera.
The camera is the Sony PDW 700 of. We process but mostly SD material, but in this mxf container.
One of my questions at the end:
Which setting coordinates (the resource allocation system, XP Prof.) !” Vegas in such a case? About the system registry of the operating system, although more can I Pagefile - establish this even on a hard drive, but in my opinion is no sense, because XP can already put 4096 MB available as needed (; and other Progs effectively synonymous) makes. This maximum is not used only in conjunction with Vegas. Rather Vegas already rising completely out at 2 GB.
I hope I've forgotten anybody?
Again, my thanks and
so long
mf
Antwort von vaio:
"The size of the paging file of XP, I'll manage, she lies on the RAID-0 system." Hello moving frame,
Once put the page file on partition C or D, so no raid drive. Lass (thereby determine the size and management by XP, the default). How does the system work?
"What setting coordinates the resource allocation system (; XP Prof.) !” Vegas in such a case? About the system registry of the operating system, although multiple page file, I can ..." Resources are allocated by the operating system (and I should everything first), indicate a standard. The project files and temporary files by the editing software.
Gruß Michael
Antwort von Marco:
"Get 9.0a taste, with a difference, I storage management, and utilization of the paging behavior found amazing." Right. It is in this point there were during the upgrade of 9.0 to 9.0a amazing improvements.
"As far as
I understand it, is merely an MXF" enveloping "format, format, no compression. This container can be present different data and codecs / be transported." Sure, that's why I had asked for the compression, since you have not been described in detail. If you use MXF SD video with this camera, could be the compression of both DV and IMX synonymous.
IMX, the system calls for more than DV, although usually both should work properly in Vegas. Is of course still depends on what you are doing so within the project and vssynonymous of rendering format. But I am optimistic that it will work correctly with version 9.0a.
Marco
www.vegasforum.de
Antwort von movingframe:
Good day,
Unfortunately, these proposals have caused no improvement.
We now have the system set up from scratch schooled: only the operating system, the necessary updates and Vegas 8.0c. Now, Vegas renders really easily all file formats, the swap file is hardly more than 800 MB. We ourselves can not explain it to us, but they are relieved. Speculation, there are countless (and it lay zBsDirectX 10, now we go back to work with 9), but I think this is all just fantasy with snow, to the excellent error analysis ill-suited.
@ Marco (and only the sake of completeness)
Streams
Video: 00:00:15,360, 25.000 fps interlaced with, 720x576x32,
IMX, 50Mbps
Audio: 00:00:15,360, 48.000 Hz, 16 bits, 8 ch, Linear PCM
Additional metadata
Regions / markers: Yes
Command markers: No.
Media Manager
Media Day: No.
Plug-In
Name: mxfplug.dll
Folder: C: \; Programs \; Sony \; Vegas Pro 8.0 \; FileIO plug-ins \; mxfplug
Format: SonyMXF
Version: Version 1.0 (; Build 1815)
Company: Sony Creative Software Inc.
What remains is only one problem with the existing project files, cut on the old system with 8.0c. I Draw one of these files to the timeline, the effect again. This is synonymous, if I bring in to open the Project on "File /" and then try to render. I guess one for Vegas unmanageable Constellation in the old project files, which leads to the "overflow" of the swap file (; Info Vegas computer properties:
Memory
Physical memory: 2097.1 MB
Paging memory available: 4194.3 MB
Virtual memory possible: 2097.1 MB.)
The same way, files can be processed without problems in the timeline and synonymous clean gone, only the rendering is not exactly, then comes the familiar mistakes. We only see the possibility of the entire EDLs again work through the current projects in order to finally be able to play off final. In commercials with many effects, the effort is, of course. But the new cut all projects run by clean, so it's our way.
I wish to thank once again all for the tireless guidance. The reasons for the failure for us still in the dark, but on the contrary to support has taken place here once a committed dialogue, class (;!!!).
We will remain faithful to Vegas synonymous in the future, but we might not feel quite so sure.
This thread is now pleased to be closed.
Always a good cut, you can see in the forum
mf
