Ok I have 2 questions......the first one is probably really easy so I will get it out of the way first.....
The is a red line right above my time line....it is some sort of stop and when playing a video it will stop there.....if I am in the program and I hold the shift key down and press play it will go past it....but if I burn a dvd it just stops where that red line ends....how do I remove that line.....
Second is I am getting a Ulead memory error...
http://www.offroadoverstock.com/picture ... _error.jpg
Here is a picture of it. Seems to happen at random when I am moving around inside a project. I had version 9 and now have 10 Plus. I did not have the probablem before so it is new....
Any help at all would be great.....thanks in advance......
Biff
Ulead Error and Red Line
Moderator: Ken Berry
The red line is the preview plane and it allows you to render sections of your project rather than the whole project. This is useful for things like seeing how a transition effect will actually look once rendered. You shouldn't be burning DVDs from the time line, you should render your project, or section of project, to one file, and then, with nothing in the time line, follow the recommended procedures for burning. As to your error code, I haven't seen it before, maybe one of the forum Gurus have seen it.
Terry
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
The error message -- particularly if you get similar ones at arbitrarily different points in your work flow -- can often be indicative of a fault or developing fault in your RAM sticks. Essentially, the message means that VS is trying to access a certain address in the RAM but cannot access it. This can be because another program which is running has already accessed that address and thus blocked it from access by VS; or that there are addresses in the RAM which can no longer be accessed properly (i.e. they are faulty).
I would first try closing down all other unnecessary programs possible (screen savers, anti-virus etc) so as to minimise the possibility of program conflicts over the same RAM address.
If that does not work, then I would download a RAM test -- Microsoft has a free one, though I am afraid I don't have the URL for it -- and run a comprehensive test on your RAM. A couple of years ago, I began receiving this sort of message. After running a RAM test, which contained 12 sub-tests, I found that one of my RAM sticks failed just one of these 12, but that was enough to make the stick defective. Naturally, I replaced it (and luckily, did so within the warranty period!) At least these days, RAM is relatively cheap...
I would first try closing down all other unnecessary programs possible (screen savers, anti-virus etc) so as to minimise the possibility of program conflicts over the same RAM address.
If that does not work, then I would download a RAM test -- Microsoft has a free one, though I am afraid I don't have the URL for it -- and run a comprehensive test on your RAM. A couple of years ago, I began receiving this sort of message. After running a RAM test, which contained 12 sub-tests, I found that one of my RAM sticks failed just one of these 12, but that was enough to make the stick defective. Naturally, I replaced it (and luckily, did so within the warranty period!) At least these days, RAM is relatively cheap...
Ken Berry
