Chris Young
Forum Replies Created
-
If you have marked an ‘in’ and ‘out’ point and have the ‘loop’ icon selected using the ‘home’ and ‘end’ key will take you to ‘in’ and ‘out’ points.
Chris Young
Sydney -
Very much so. I have some no name Chinese el chepo USB numeric keypad and it works fine, WinXP SP2. I did try one of the Casio combo keypad/calculator pads and it also worked. Have you tried any others pads and USB ports? Also under ‘Device Manager’ can you isolate it and check which drivers it’s using. Kensington may have updated drivers for it. If you are on WinXP SP1 there is a USB update which is almost a ‘must install’ which fixed a number problems. If it is SP1 then chase down the info here:
https://support.microsoft.com/?kbid=822603
Geez! Would hate to work without the numbers pad. Do all trimming, slip/slide etc with it.
Chris Young
Sydney -
Check out Timothy Duncan’s post about working with Vegas and Digi-Beta it may be of use as a pointer as to what you can do:
Chris Young
Sydney -
Yes, that’s a good question. I am beggining to wonder myself if my belief and what I have been told is incorrect. Have a look at this link from Disctronics. Disctronics being one of the worlds largest DVD replicators:
http://www.disctronics.co.uk/ downloads/sales_docs/dvd_logos.pdf
In this PDF point #2 states “The use of DVD logos is strongly recommended but not mandatory” Nowhere does it state or mention any fee structure for the use of the DVD logo on ‘pre-recorded’ discs and this PDF is based around ‘General rules for DVD logos’. So I guess the whole matter of using these logos on pre-recorded DVD’s needs to examined further. When I get the time I might contact Disctronics here in Aussie and see what I can find out.
Chris Young
CYV Productions
Sydney -
Peter ~
Thanks for suggestion. Yes, had me confused. Not that it’s hard to do these days, confuse me that is! On the laptop, where I have both V5 and V6 the nested vegs open fine with V6. Going back to the Vegas workstation I had another look at the file associations and discovered that even though I had selected V6 and selected ‘always open with this program’ it kept using V5 to open the nests??
Upon further investigation I found that when I went through ‘Folder options’, ‘File type’, ‘Advanced’, ‘Edit file type’ and then the ‘Edit’ button it was pointing to V5.exe. Re-directed this to V6.exe and, what do you know, the nests now open correctly in V6. I guess it must be something to do with the fact that V5 was installed after V6 on the workstation as I had just rebuilt it and installed V6 first.
On the laptop V5 was already installed before V6 went on so it looks like whichever version goes on last grabs the file association by default. Can’t think of any other explanation. Had that not worked I was going to try your idea of uninstall/reinstall. Though going through what I just uncovered I think I would have still have had the problem… not 100% sure on that statement but what the heck, it’s working fine now.
Chris Young
CYV Productions
Sydney -
‘Tis basically what we do Pete!
Chris Young
Sydney -
You are correct in your observation. You are supposed to be licensed to use the DVD logo. Check the following link and its associated pages and it will give you a pretty good idea of what is and isn’t allowed.
https://www.dvdfllc.co.jp/dvdlogo.htm
That being said I have seen numerous instances of duplicated (burnt) DVD’s using the logo and know full well that the companies and businesses using it are not licensed.
Chris Young
CYV Productions
Sydney -
Doh! Sorry ’bout the double post. Got a phone call and didn’t realise that I had already sent it after I hung up.
Chris Young
Sydney -
Alan ~
No suggestions as yet. I have managed to get around the render problem in most case when I have set the ‘Dynamic RAM preview’ settings back to 16MB. Even set at this figure though there are massive memory consumption problems when rendering timelines with large 32 bit TGA files, i.e. 3000 x 3000 pixels. If you have say three or four layers of these all with ‘pan’ moves set in the pan and crop settings V6b just chokes up and then hangs. Funny one, because on V5d with the same jobs on the same machine and it just chugs on through with never a problem. Speed wise as yet I have seen no real improvement in V6 over V5 running on a P4 3.2 Gig machine. As Dr. D says we probably won’t see much render speed improvement until we move V6b to a dual proc or dual core CPU.
I can’t understand though how you can edit away in V5d using a high dynamic ram preview setting, of let’s say 1 Gig, and then render a timeline with nil problems and without having to change this setting. Try leaving a high dynamic ram preview setting in V6b, useful for your more complex longer previews, and then render. If we do this in V6b we know we are heading for disaster. It becomes an absolute memory hog and we know it is going to hang. Not very confidence inspiring!
I am by no means convinced that there isn’t some major memory/render issue with V6 and the sooner it is admitted and worked on the better. Trying to defend V6 and fend off the numerous posts around many forums re this issue is not what you expect from the likes of Sony, especially if they want more editors to consider it a ‘pro’ tool. Going on Sony’s past performance I think that this will be something that they will be looking at real soon… I hope!
Chris Young
CYV Productions
Sydney -
Alan ~
No suggestions as yet. I have managed to get around the render problem in most case when I have set the ‘Dynamic RAM preview’ settings back to 16MB. Even set at this figure though there are massive memory consumption problems when rendering timelines with large 32 bit TGA files, i.e. 3000 x 3000 pixels. If you have say three or four layers of these all with ‘pan’ moves set in the pan and crop settings V6b just chokes up and then hangs. Funny one, because on V5d with the same jobs on the same machine and it just chugs on through with never a problem. Speed wise as yet I have seen no real improvement in V6 over V5 running on a P4 3.2 Gig machine. As Dr. D says we probably won’t see much render speed improvement until we move V6b to a dual proc or dual core CPU.
I can’t understand though how you can edit away in V5d using a high dynamic ram preview setting, of let’s say 1 Gig, and then render a timeline with nil problems and without having to change this setting. Try leaving a high dynamic ram preview setting in V6b, useful for your more complex longer previews, and then render. If we do this in V6b we know we are heading for disaster. It becomes an absolute memory hog and we know it is going to hang. Not very confidence inspiring!
I am by no means convinced that there isn’t some major memory/render issue with V6 and the sooner it is admitted and worked on the better. Trying to defend V6 and fend off the numerous posts around many forums re this issue is not what you expect from the likes of Sony, especially if they want more editors to consider it a ‘pro’ tool. Going on Sony’s past performance I think that this will be something that they will be looking at real soon… I hope!
Chris Young
CYV Productions
Sydney