Karly Melrose
Forum Replies Created
-
No worries guys – I’ve found the answer now.
For anyone else finding this thread looking for an answer to the question I asked and needs to access the internal settings, to access them simply hold down the shift key while clicking on ‘preferences’ in the ‘options’ menu. When it opens, an extra tab for “internal” will be present on the preferences box.
There’s a lot of options in there, but there’s a search function: I found “Ignore default DV codecs” and in the ‘Value’ column changed ‘TRUE’ to ‘FALSE’.
Vegas now uses the Cedocida DV codec I installed, which I can now configure via Virtual Dub (or the vegas ‘render as’ settings), which lets me set things like colour space settings to “[16 – 235] > [0 – 255]” or “[0 – 255] > [0 – 255]” at the decoding stage, rather than as an additional FX process using a colour corrector.
-
Yeah… I get that error too. I’m sure I’ve read that other people do also, so you’re not alone. I just don’t think you can render to 30fps using Sony AVC. No idea why. But considering 30fps isn’t actually available in the frame rate list (but things like 15fps and 50fps are), I’m guessing there must be a reason.
So I’m afraid all I can advise is if you want to avoid any hint of ghosting, don’t render to Sony AVC!
Hopefully maybe someone else can offer a bit more insight?
-
Glad I could help.
Sorry though for my long-winded way of getting to the point!
-
…or just try making sure your project properties are 30fps!
-
Hi,
Well, at first I could see no problem with your footage – there was no ghosting. BUT, after trying a few things, I think you might need to check your project settings!
It’s an odd one this – I imported your video in Vegas as is. All seemed fine: No ghosting (my project setting were the Vegas default)
However, I know I’ve had a similar problem in the past, and all I could figure out at the time is that it was because the frame rate and resolution of my project was different to the media I was using. So, I tried altering frame rate of my project, but couldn’t re-create ghosting.
I then used the ‘Match Media Setting’ in properties so that project settings were the same as the imported media. Media displayed at 1280 x 720 as per media settings. All fine, no ghosting.
THEN I set the project settings to use the NTSC DV Widescreen (720 x 480) template. And I now have a ghosting effect (with a combing effect on the ghost image – field order fixes the combing, but there’s still ghosting).
I suggest therefore that, to begin with, you use the ‘Match Project to Media’ function and see if that fixes your problem!
-
Yes, I remember Max Headroom! And to re-create the editing style I think you just need , well… a lot of patience and time! Though with NLE editors, the task should probably be easier than it was back then!
The stuttering bits? You just need to repeat small selections of frames I guess. But you also might want to insert tiny bits from other parts of ‘Max’ speaking into irrelevant places. Or maybe shoot ‘useless’ stuff solely for this purpose. I seem to remember that’s what they did with Max – have out of context pieces of him dropped in here and there.
Pitch shifting? Can’t remember off-hand if without looking if media clips can be pitch shifted on the time line. But I’m sure you can add a pitch shifting VST to each clip. Could be quite laborious though. Maybe look into using a sampler?
-
How was the audio recorded in the studio before it found its way onto CD?
If analogue tape was used at any point, then that will be your problem! Tape recorders don’t necessarily run at a constant, fixed speed, and are unlikely to be running at the same speed as your camera. Which means the speed of the audio recording might be different to your video recording, making it difficult to sync up.
One thing you could try doing is to stretch the audio so it fits – find one point at the start of the audio and sync it to picture (crop off everything from before that point). Then find a point towards the end of the audio that you intend to use as a sync point. Crop off everything after that point. Then stretch the end of the audio to the sync point on the picture. (only problem with this idea – stretching has never actually worked for me in Vegas 10, so don’t know if it’ll work for you either)
Personally I’d avoid splicing bits out of music audio at various intervals if I were you, unless you can do it without it being noticeable. But try it an see. Sometimes though even small cuts can affect the flow of music (unless your band’s time keeping is all over the place anyway!). Of course, whether you can use this method at all depends on which way the visuals/audio is out of sync anyway; if the picture is running ahead of the sound, then cutting bits out of audio won’t help – it’ll just make it worse!
Either way, ideally I’d recommend editing video rather than the music track. You don’t say how many cameras you’ve used. If it’s two, then it’s no problem – just cut to a different angle whenever you need to re-sync. I suspect it’s just one camera though – which means jump cuts at every point you need to bring it into sync. So turn it into a ‘pop’ video, and add effects to different shots. EG increase contrast for ‘clips’, make some shots black and white, add grain effects from time-to-time, and especailly use the crop and zoom to tool to deliberately emphasise the jump. Maybe add some quick fades to black in places too. Have fun with it! (If it’s for a whole set of songs though, it might be come a bit tiresome, for the viewer I mean!)
-
Sorry John, it must have took me about 30 mins to compose my last post as you seem to have posted in the meantime!
You may be right, though I may have got one or two things back-to-front myself when trying to explain. Point is though – my producer (the person paying me to edit something!) wants me to use the Cedocida codec for reasons that he’s researched quite heavily. SOME footage we’re using in the project is NOT DV encoded and uses a different colour space, and is correct. The DV footage is incorrect. The way to get it correct is to use the Cedocida codec (this works for my producer in Premiere, but not for my in Vegas… because Vegas is insisting (I presume) on using its own DV codec, which does things differently to other DV codecs. Or so I believe).
With that in mind, I’d still like to know how I can get Vegas to use the DV decoder of my choosing. Can this be done in the internal settings, and what do I have to do?
-
Thank you Mike.
Sorry, I probably should have said that I have already read those articles, but I believe those solutions provide workarounds to compensated for the Sony DV codec not doing it ‘right’ in the first place, not a true fix.
From the above mentioned article:
“You may need to manually wrangle all your color space conversions in Vegas, depending on the situation. Vegas does not do this for you. (It should but it doesn’t.)”I want to use the Cedocida codec for decoding, which lets me set up my workspace as I want it from the outset, rather than the Sony DV codec, which doesn’t.
Changing “internal” preferences to get Sony Vegas to use the DV decoder I want it to when I import my files looks like it might be the only way I can do this, but I don’t know where these are. Where do I find them and how can I change them?
Thank you for your help.
-
Hi. Thank you for replying.
I want to use a codec that lets me work in a YV12 colour space with a 16 to 235 brightness range (instead of the RGB one that the Sony DV codec ‘converts’ the DV footage into and reducing contrast in the process). I have a codec that in theory lets me do this, but don’t know how to get Vegas to use it.
How can I find/adjust the ‘internal’ preferences.
PS I’m aware there are colour correction presets to deal with this, but I think these are a workaround, not a solution. I want to make the adjustment at source, on import, not as a post-production effect.