Chris Young
Forum Replies Created
-
Mike ~
Ah! It’s probably just me. I tend to use the ‘mimimalist’ player settings and it might be these that have minimal buttons. I guess I should go back and do my homework! Wish you success.
Chris Young
CYV Productions
Sydney -
That’s an odd one? We do this every week and use a fair bit of opacity in these jobs. Using ‘Save As’ with 2 second handles and the new files created are correct length, as per the timeline plus their handles, this is on v6.0c and d. Got me puzzled to the point I just tried doing it again on a small job and yes, it saved correctly. Why should this problem happen?
Just a thought, haven’t tried it but maybe this is a work around. Save your master job with the opacity settings, do another save with the opacity settings but call it ‘version 2’ or something. Next reset all opacity levels to no opacity, do a ‘save as’ with ‘trim media’ selected into a new folder called ‘archive’, call this job something like ‘save as trim job’. This should then archive everything with the correct clip lengths plus your defined handles into the archive folder. Remove or delete the .veg file for ‘save as trim job’, rename the ‘version 2’ .veg file to ‘save as trim job’. Open this .veg file and direct it to the archive folder where all the assets are and hopefully, as this .veg has your correct opacity settings it should open up the archived job with the correct opacity levels intact and hopefully you have overcome the 18 Gig file problem.
If that won’t work than that I guess it means a tedious job of resetting all opacity levels. If you try this work around let us all know if it works. It may dig any of us out of a hole in the future if we find this happening.
Chris Young
CYV Productions
SydneyChris Young
CYV Productions
Sydney -
Mike ~
FLV will do the job fine for you. If you got any queries just post ’em!
Chris Young
SydneyPS. The major problem with FLV is the amount of follow up junk mail you will receive from them, be warned!
-
Mike ~
Both are very easy to use. If anything the quality on the current version of Swish (v2) I think is a little better but unless you are comparing both Swish and FLV output files directly side by side on the same avi encode you would never really know the difference. The big plus for me is that Swish 2 handles QuickTime files for encoding whereas FLV won’t.
Having battled for ages to get the best results I find the following work flow gives very good results. Don’t ask me why but it does. You can go from a 720 x 576 or 720 x 480 avi straight into Swish but the best results I have got is by exporting from Vegas in the dimensions that I want my final Flash video (.flv file) to be, let’s say Multimedia 320 x 240 as an example. Go to ‘Render As’ select QuickTime, next go to the ‘Custom’ tab then select the ‘Video’ tab and from the drop down menu select, in this case, Multimedia 320 x 240 and push the quality slider to ‘maximum’. Set the frame rate you want, with us it’s 25 frames, select progressive and leave the audio settings as they are, uncompressed, 48KHz. I have saved these settings as a user template, that’s up to you.
When you make this QuickTime 320 x 240 you will find it is way larger than the original DV file would have been at 720 x 480 had you rendered that out. No worries, you can ditch this big QT file afterwards. The thing is that this QuickTime .MOV file will make a very clean .FLV file once converted in Swish 2. In both programs you can select a range of player skins. The ones in FLV give you additional pause and volume buttons which sadly you don’t get in the Swish player selections. All said and done both programs are a simple three to four step click process to output a file. The final output contains all the assets required plus an HTML file ready to upload to a site. The down side is that neither offer a trial/demo version that people can check out. Good luck!
Chris Young
CYV Productions
Sydney -
We handle around six to nine hours each week for a weekly TV show and have never found the render thing a big issue. Our regular show encompasses around thirty plus graphics with opacity, slow-mo replays, additional music and VO’s and has around eight to twelve tracks and at fifty-six minutes duration will render in around seventy to eighty minutes on your average P4 3.0 to 3.2 Gig CPU. It is quicker on the Dual Core system but only by a number of minutes. That hour fifteen or so is a minor trade off and a small percentage in time relative to what is usually a three day edit. The speed, stability and reliability of Vegas to get a job out is by far the most important thing when having to meet regular weekly deadlines.
Chris Young
CYV Productions
Sydney -
Hi Leslie ~
Yes, glad to see the TC fix, it was long overdue. Give the guys at Sony Media their dues they do fix things as time goes by. As you say I can live with the collapsing folder tree but it is annoying. Oh well, edit on and see if NAB brings v7.0 with more fixes and features. One I would like to see is XDCam HD support… or is it already there with the XDCam support?
Cheers
CY
Sydney -
Tend to agree that if there is no speed increase on 1394b then there is no advantage of going with an 800 Raid. Thankfully the higher speeds offered by 1394b can be achieved under SP2. Below is a quote from an [unnamed] MS spokeperson re the issues surrounding the MS ‘retro’ firewire 800 support. As he puts it:
“We have never supported 1394b. It ran under certain conditions on Windows XP and Windows XP SP1. The problem we are confronted with is that OHCI 1.0 and OHCI 1.1 do not support the speed code (0x3). This is a reserved value in the OHCI specification we support that cannot be used. What are we doing? Things become problematic when you start mixing 1394a and 1394b devices. If we ignore OHCI conformity and bump up the speed to 800 MBit/s the old devices down tools. If we set the speed to S100, all devices start enumerating and working. It was a tough decision but we have little room for maneuver if we don’t want to dispense with 1394b support.”
I think the easiest answer to overcome the 1394b bottleneck in SP2 is to use Unibrain’s UbCore 1394b drivers which fully support 1394b firewire 800. The current driver release is v4 and they are available at:
https://www.unibrain.com/Products/DriverAPI/ubcore.html
I believe some people have had success installing the old SP1 1394a drivers under SP2 to recover the original 400 speed because there were reports that SP2 with 1394b pulled transfers speeds down to as low as 10MB/s
Chris Young
CYV Productions
Sydney -
Norton’s, ah! When Peter Norton had it as Norton Utilites it was a great set of tools. Since Symantec took it over it’s become bloated over the years, it consumes more registry real estate than almost any other antivrus going, it’s slow, doesn’t keep updated often enough and uses more CPU power than most and is a right piece of excrement to uninstall completly. Not that the CPU overhead is such an issue these days with more powerful CPU’s about but that’s no excuse for a poorly designed app, my opinion, when compared to it’smodern counterparts such as AVG, Kaspersky, Computer Associates eTrust etc. Aditionally lately it has suffered some serious security problems which Smantec knew about but didn’t come forward with until security researchers posted warnings about ‘Norton AntiVirus flaw ready for exploitation?’. Check out:
https://www.zdnet.com.au/news/security/0,2000061744,39165422,00.htm
From this post you will no doubt discern that I also am no great fan of Norton AV these days.
Chris Young
Sydney -
Check out the ‘Maxtor OneTouch III Turbo Edition’ external unit. It has firewire 400/800 and USB2. Available as a 600GB or 1TB unit. Configures as Raid 0 or Raid 1. Going to have a look at it myself because even in Aussie $ you can get it for around a $ a Gig. Long URL for what it’s worth but you can download a .pdf of it here:
Phew! that’s some URL.
Chris Young
Sydney -
John ~
Two cents worth here. Look under Options/Preferences/Video and see if your Dynamic RAM Preview is set high. This needs to be set high if you are using ‘Shift B’ to build ram previews of any length but for normal editing and the smoothest playback on your preview it’s best set to 16MB. Setting ram preview to say 1GB will tax the page file and it will grow and grow. Best also to set the ram preview to 16MB when rendering for the same reason. Also on some systems I have seen better playback with the preview set to ‘Preview Full’ than ‘Preview Auto’ which seems to be the default setting. Don’t ask me why but that’s the way it seems to be.
Chris Young
Sydney