Will 8.0c new features migrate to 8.1 - and when?

Christian de Godzinsky wrote on 10/16/2008, 12:58 AM
I wonder why SCS decided not to include same new functionality (in 8.1) that 8.0c has?

Logical thinking gives me the answer that 8.1 development diverged from 8.0 at a much earlier stage, probably one year back...

SCS - it would be nice to know IF you bring the same fuctionality to 8.1 - and if the answer is yes - WHEN that will happend?

The other BIG question - when can I use all the same plugins that I used before - that now are just pieces of junk since they do not work with 8.1. Are there any plans to support 32 bit plugins with 8.1? I might answer that myself - probably not :(

Christian



Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

Comments

blink3times wrote on 10/16/2008, 4:59 AM
Good bloody question. I feel like Tom Hanks in that airport movie.... can't go backward, can't go forward... stuck.

I would love to move on to 8.1, but I've got a lot of $ worth of plugins that I use. I'm not even sure how this is going to go down either. Are the 3rd party developers going to charge extra for making these plugins 64bit compatible? Am I going to have to buy them over again? Will they simply adapt the existing plugins to fit 8.1.... and if they do then what will that do to the speed of Vegas?

It's all a pretty big issue for me.
Himanshu wrote on 10/17/2008, 6:14 PM
It was a bit surprising to me that the 64-bit version was 8.1 and the 32-bit version was 8.0c. I wonder if SCS just wanted to get the 64-bit version out the door, which they might have started based on 8.0b, while development on 8.0c was going on. Perhaps v8.2 will be a combined 64-/32-bit version with feature parity?
tcbetka wrote on 10/17/2008, 6:42 PM
My guess is that the 64-bit version was a stop-gap fix of the AVCHD issue. I only say this because I just installed a 64-bit version of Vista on an empty hard drive, and then installed version 8.1. The performance increase with AVCHD clips is STAGGERING on my quad core system. Of course I am running 8gb of RAM, versus 3.25gb (out of 4) on XP 32. But still--if the extra horsepower buys a quick way to handle the AVCHD woes, and they were developing the 64-bit version anyway...then why *not* release it?

I know that some folks in this forum have commented how it shouldn't make that much difference in rendering times to go to a 64-bit version, but I can tell you that at least on my system...it does. A HUGE difference. Like HALF the rendering time with a 73 minute AVCHD project (56 versus 113 minutes).

TB
MSK wrote on 10/17/2008, 9:51 PM
What features are you missing besides third party plugins?

The obligation is not for SCS to make 32 bit based third party plugs to work in 64 bit os in Vegas, but the other way around imho.
Himanshu wrote on 10/22/2008, 8:14 PM
MSK,

Going by the readme files for 8.0c and 8.1, what I see is:

8.0c lists changes from 8.0b to 8.0c
8.1 lists changes from 8.0b to 8.1, and is a much shorter list than the one above.

As an example small item that caught my attention in 8.0c was, "Added support for opening Vegas Movie Studio 9 projects" which is really nice because some of my family still use Vegas Movie Studio, and I would be able to open their projects (even if it's just one way)

Seems like development split off at 8.0b, unless the readme isn't complete.
jabloomf1230 wrote on 10/24/2008, 5:22 PM
"The obligation is not for SCS to make 32 bit based third party plugs to work in 64 bit os in Vegas, but the other way around imho."

Umm, no. Now if Vegas 8.1 was a true 64 bit program, like VirtualDub x64, then no 32 bit plug-ins and codecs would work with it at all. But it spawns a companion 32 bit program, every time it needs to access 32 bit elements. Now the problem is why SCS didn't work more closely with other software developers to make sure that their 3rd party 32 bit stuff worked with 8.1.

Basically, in my mind, Vegas 8.1 is a beta. SCS got scared that Adobe might come up with a full 64 bit CS4 suite and wanted to get something out the door. As it turns out, the first release of CS4 is almost entirely 32 bit, except for Photoshop CS4.
blink3times wrote on 10/24/2008, 5:46 PM
"Basically, in my mind, Vegas 8.1 is a beta. SCS got scared that Adobe might come up with a full 64 bit CS4 suite and wanted to get something out the door."

I think there's some truth to that.
Terje wrote on 10/26/2008, 1:07 AM
The obligation is not for SCS to make 32 bit based third party plugs to work in 64 bit os in Vegas, but the other way around imho.

Yeah, in the same way that it is not Microsofts job to make sure that applications work from one Windows version to the next. I wonder how the uptake of Windows would be if that was the case.