Chris Young
Forum Replies Created
-
Oh yes! This has been done. Sony have got back to me with a request for examples of TGA files that V 7.0a won’t import. I have sent them some, will wait to see what transpires. The sad answer was on the DVDA 4.0 front. Whereas I have had no problems importing m2v files into DVDA 3.0, done dozens of them since it came out. With DVDA 4.0 it now appears that this is not possible. Sony support states that DVDA 4.0 will import MP2, M2P,MPG and MPEG but not a M2V file. If I rename the m2v file as any one of the above I can actually import the file… and even preview it. It even brings in the correspondingly named AC3 audio file. Click on the file though and ‘poof!’, back to the desktop. Why on earth have they decided to drop support for the import of m2v files? So many good steps forward in both V 7.0 and DVDA 4.0 but sadly some things that worked in the past got broken. I have no doubt that 7.0b will have a fix for the TGA issue but am seriously hoping that DVDA 4.0 gets back its m2v import capability. Stuck on v3.0 otherwise for jobs where clients supply m2v files or I have three hour plus DVD requirements which as I have said in the past work out better quality for us, and render quicker, if done in Canopus Procoder as m2v.
Chris Young
Sydney -
2 cents worth here. Right click offending media, select ‘switches’, select ‘reduce interlace flicker’ and select ‘force resample’ and under ‘project properties’ set for ‘best’ render quality and set for ‘blend fields’ under deinterlace method. Seems to work here for many problematic pan & crop problems.
Chris Young
Sydney -
Generally if I am looking for the loudest peak I do it visually by vertically expanding the audio track and quickly scroll through it and look for the greatest audio waveform amplitude. Usually this is the loudest part of your program. Another way you could do it, if it is a finished fully rendered audio track, would be to set your normalize peaks to -0.1 under the ‘audio’ tab under preferences and then right click the audio track and under switches select ‘normalize’. This then would normalize that track to the -0.1 level and when it normalizes it uses the highest peak to scale the normalise value from. Now scroll through the track and find the peak that goes from the top of the waveform to the bottom and that is generally the highest value on which the normalize was based on. Once you have determined this you can always use undo to bring the levels back to where they were or just deselect ‘normalize’ under switches. Any better methods out there? Always good to get other peoples work arounds.
Chris Young
Sydney -
Hmmm! Yes, a bit of a worry. Think we will be staying with V 6.0 and DVDA 3.0 until these quirks are sorted. The problem being that once you save a job in either program in versions 7 and 4 you can no longer open them in the earlier variants. Could be a nasty ‘gottcha’ if more anomalies show up. I actually tried a ‘copy paste’ from v6 to v7 and the graphic media on the timeline says ‘media offline’ so 7.0a is definitely not seeing some stuff.
Chris Young
Sydney -
I had a similar problem with Sony Z1 and HVR-M25 decks. Drove me mad but got it sorted. Have a look at my post
https://forums.creativecow.net/cgi-bin/new_read_post.cgi?forumid=24&postid=864955&pview=t#head
and follow method #1 one that I outlined and see if your JVC is recognized. If it is you are sweet to go. If not you will have to use method #2 and it might sort the problem for you. The problem is you need the device ID to solve the problem in method #2. If method #1 doesn’t work post back and I will give you pointers on how to determine the JVC’s device ID.
Chris Young
Sydney -
Not on the site yet. When can we get it?
Chris Young
Sydney -
Leslie ~
Off and on more than I should have. Maybe a day spread out over a few days. This approach should work for almost any firewire device that comes up as unrecognised in Device Manager. The trick is finding out the Hardware ID codes for the device involved so that it can be entered into the AVC.INF file. This in turn talks to the drivers required and then the process loads the required AVC entries under HKEY_LOCAL_MACHINE in the registry. It’s a black art understanding that registry, quite a brain twister at times. Remind me not to go there again!
Chris Young
Sydney -
The reason this happens is that the sound level coming in is just way to high, that’s why you need to use an attenuator, to reduce the audio level at input. My previous post had a link to Pro-Co where you can get the units. Most good PA and Pro audio suppliers should be able to supply these. You would have to call one of them for pricing ‘cos the only pricing I have is in Aussie $’s and that won’t help you 🙂
Chris Young
Sydney -
As long as the mic you are using can handle the pressure levels you can use something like a Microphone Attenuator. These are in-line XLR>XLR units. Have a look at the Max Series Microphone Attenuators at
https://www.procosound.com/kwikfixers.htm
In the past I have found the 20dB pads will handle most rock bands even front of stage. These generally restore a pretty useable range to your gain control when working under extreme sound pressure levels. Mind you when it goes quiet you can here nothing, nada! so beware!
Chris Young
CYV Productions
Sydney -
As Nancy says, have numerous Vegas instances open. I often have anything up to a dozen or so open and cut/copy/paste etc between them. For me it works like as many timelines as you want. Just minimize the ones you are not working directly on to the taskbar. Available in an instant when you need them.
Chris Young
CYV Productions
Sydney