New Update!!!

Comments

Dave McCallister wrote on 7/24/2013, 6:17 PM
(David McKnight)

16bit /44.1 CD track from HD

How can Vegas tell what HD interface the data is coming from?
How can Vegas tell how big the drive is?

Is the issue actually 24-bit vs 16?

set wrote on 7/24/2013, 7:03 PM
Glad to hear this although I have been quite comfortable here in 563 :)

BTW, I still kept using catalyst 12.08, and thinking of make upgrade, does the latest release of catalyst is stable for use with VP12 ?
How much influence will it be to me, as I still using Radeon 5750 ?

And good to hear about Color Match large size issue fixes, hopefully it will work as expected.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

DavidMcKnight wrote on 7/24/2013, 7:50 PM
Dave McCallister - yes, the issue is with 24-bit / 48K WAV files. The workaround is to use the files on an internally connected drive and transcode to a lossless format like FLAC.
Lovelight wrote on 7/24/2013, 8:12 PM
I'm using a sony recorder with sony's v12 & it doesn't work.

I'll try different settings to see if it helps.

I have a zoom, but I prefer the sony recorder. I would think sony would want me to use their gear with their software, but they know better.

Would be nice if an update could square this away.
Mark_e wrote on 7/25/2013, 5:34 PM
Giving vegas one more go,
did clean install of windows 7 64bit, have only installed vegas 670
Touch wood this update + the new radion driver update for firepro 7900 seems to have made a massive difference to my system. fan even comes on on the graphics card, I could never get enough load on it before to do that,
Tested the benchmark Press Release Project and I can now set it on 32 bit, best full in the panel + preview on external monitor 1080p and it plays through with no frame drops and really uses the firepro card. could get no where near that before.

This is how I imagined vegas should work! fingers crossed, will gradually add in plugins and see how it goes but so far so good.
OldSmoke wrote on 7/25/2013, 6:06 PM
Would be nice if you could render the benchmark project to MC AVC 1080p and let us know the render time. I am always looking for something better then my system and Keppler cards are not option for now.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Paul Fierlinger wrote on 7/25/2013, 6:10 PM
I can't get Vegas to give me the black events anymore. I've put the software through all the tricks I've learned just to create black events but it won't happen anymore. The ultimate was to switch from one large project to another within the File menu and Vegas was going to fail me. Now I can go back and forth and scrub back and forth at breakneck speeds and the black events just won't happen and Vegas won't freeze for a few minutes to catch up after all that scrubbing. I've also tried importing several events with all the AVI codecs I have available to me and none of them fail. This is pretty good.
larry-peter wrote on 7/25/2013, 6:21 PM
This looks promising. At least I'm seeing the same playback performance as I did with VP11 on my system 2 (560ti card). I only threw a few 1080 clips at it but it already feels much better than the previous build. I'll install on system 1 tomorrow and see if this version finally works correctly with the AJA Kona again.
Byron K wrote on 7/25/2013, 11:40 PM
They fixed something.
On this thread I was having issues,
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=863974

But now I can now render to .mov intermediates w/ 12 multi-threads and cranked up my preview RAM to 10Gigs. Renders my 7-10 minute videos in 15-20 minutes vs 1.5 hours.

I don't have to reboot my machine between renders either.

Man I wish this fix came out two weeks ago, could have saved me a LOT of time rendering 11 videos... I wasn't going to re-render my vids w/ tweaks that I made to them because of the painfully long render times but now I'm re-rendering. (;
Mark_e wrote on 7/26/2013, 3:25 AM
@ Old Smoke render test using the default project settings 8bit - good and all default vegas settings it renders in 52 secs switching the project to 32bit best takes 2.09 to render (I haven't got all my disks set up properly yet etc. literally just have fresh patched w7 64bit ultimate and vegas on a wd raptor at the moment.

I need to use it in anger a bit and get the plugins loaded etc but it's the general using / browsing time line etc that's really improved for me so far, fingers crossed!
set wrote on 7/26/2013, 3:51 AM
I'm just testing the new Color Match, and apply one.

Here's the file size project differences:
Before I add color match : 966 KB (989,968 bytes)
After I add (source external file - save snapshot JPEG) : 1.20 MB (1,268,504 bytes)
After I added with preview captured scene : 1.20 MB (1,268,528 bytes)
The store data for color match reference is just 278,536 bytes.

Snapshot JPEG file Best Full : 425 KB (436,012 bytes)
Preview Half: 135 KB (138,275 bytes)

Really good... Very Efficient!
Thank you SCS!

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

malowz wrote on 7/26/2013, 3:55 AM
my script icons in toolbar still go blank... just saying... ;P
i am erikd wrote on 7/26/2013, 3:56 AM
Well still no fix for "automatically save trimmers and markers in original file". This bug has been acknowledged by Sony for versions 10,11 and 12 and still no fix. A real shame when you consider it is for proper integration with their own product, Sony XDCAM!!

Come on, fix it already!

Erik
dtudela wrote on 7/26/2013, 9:22 AM
Happy to report that GPU acceleration is working great on my system (i7 3770 onboard hd 4000 graphics) with the latest install of VP12. Also, no longer need to set preview ram at 0. I set ram preview to 256, 512, 1024, etc. while testing and render times were the same and no issues at all. GPU on clearly renders faster than when turned off. So far STABLE here with hour + renders.

--Darrell
megabit wrote on 7/26/2013, 11:40 AM
"Also, no longer need to set preview ram at 0"

Not quite so great here, unfortunately. With my 10-camera MC tracks previewed in the preview monitor at Preview/Half, and the active take full screen on the Secondary Windows Display - I still need to set RAM preview to zero in order to get a decent fps.

The same with the "Optimize GPU usage for preview" (or whatever it is called); I had to disable it for the fps to be useful (and it still is lower than in VP11, the same project).

Piotr

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

David Johns wrote on 7/27/2013, 1:50 PM
Sadly I'm having ongoing problems with previewing material via my Blackmagic Intensity Pro (which used to work beautifully in Vegas 10e).

I haven't quite nailed down what causes it but it seems playback of some formats makes Vegas crash, whilst others play at normal speed but will crash if I use the playback rate bar to speed it up.

It's random enough to make me have to live without it - which is tiresome - as I don't want to crash my project whenever I play back the timeline!

Regards
Dave
Lovelight wrote on 7/27/2013, 1:51 PM
Well did some experimenting, it still does not work. The problem is vegas does not build the peaks correctly. It brings the audio clip in & instantly builds the peak as a straight line with no sound. This is very unprofessional of Vegas to not work with its own sony pro audio gear. Let's get it together. How hard could this be to fix?
larry-peter wrote on 7/27/2013, 3:08 PM
@David Johns,
This is a "do it at your own risk" suggestion, but If there is a .dll for BlackMagic cards and you have a prior version, you may get some results by swapping the older .dll file into VP12. I use AJA Kona for preview and it won't work in VP12 either. Replacing the AJA .dll with the one from VP11 made it usable.
Tom Pauncz wrote on 7/27/2013, 5:07 PM
@Dave & atom12,

I don't use the BMD's Intensity Pro but do use BMD's Decklink Studio and can confirm some issues, going way back to the release of VP12 that was solved by using three DLLs from VP11/701.

After I upgraded to the latest build (670), ext preview was totally dead with BMD's Desktop Video v9.7.1. VP11/701 was perfectly fine but using the VP11/701. DLLs with VP12/670 did not work.

The DLLs are:
In the VP12 root directory:
DecklinkVideoProperties.dll
In the Video Hardware Drivers directory:
extviddev.dll
DecklinkVideoDevice.dll

Started playing around with this to see if I could pin it - it now works on build 670 with BMD's Desktop Video v9.7.5 (their latest).

Here, in a nutshell, is what I did.
1. Removed both DV v9.7.1. and VP12/670 and rebooted
2. Installed DV v9.7.5, rebooted and then installed VP12/670

I can confirm that external preview now works, not at full framerate, but it works. I could not make it crash.

Should add that the exact same .veg file opened in VP11/701 plays back full rate to external preview with this setup.

I recall reading a long while back that the BMD software needs to be installed before Vegas, so a remove of both, as above, may provide some joy.

@atom12
The above steps may be worth trying with your AJA device. You never know.

YMMV...
Tom
ushere wrote on 7/27/2013, 8:00 PM
@ dj - i'm having ;some' minor problems with my inte. pro - most noticeably an occasional freeze on the external monitor. have to close and reopen vegas to clear it.

i don't know whose at fault here, but it's very annoying trying to work with supposedly professional equipment that keeps loosing the plot.

btw. latest bm drivers on i7/920/16gb/550ti/gigbyte mb.