@bitman, thanks for your question. I was sloppy in my presentation and should have made the very distinction you mention. VEGAS Pro Edit will get the new Hub Explorer window. However, VEGAS Edit owners will not get VEGAS Transfer or Hub space. In other words, the comparison chart is accurate.
Initially the plan has been that VP 365 users will get those things as part of the 365 bundle. Details would be announced on how perpetual users will get access to them, but those dare still being worked out, so I can't say anything definitely. Thus, you should go by the chart as you make your purchase decisions. I'm sorry I can't be more clear about it at the moment.
Whan u download vp 18 is says it comes with Boris effects and spectral layers but i didn't see any email or anything about this with the 365 and what about sound Forge
@James_Patrick Correct me if I am wrong, I presume you mean whether Vegas 18 + Vegas Post now works with Boris FX ? Vegas 17 works fine with Boris FX without Vegas post, the 3 together not. At least I never got any notification they ever fixed this for my outstanding bug reports (submitted on all companies Magix, Boris, FXhome as it is an compatibility issue - which they confirmed). Moving or removing OFX libraries from certain folders (and putting back again if needed) is suggested in the forums, but it is a hassle and is not really workable if you have multiple NLE's installed which use Boris FX...
Any confirmation if the combination of "Vegas 18 + Vegas Post + Boris FX" is fixed now would be welcome.
Shot a short 20-minute project a few days after v18 came out so for the heck of it I did both v17 and v18 project versions in parallel. Single video track shot with a zcam in hevc 4k with separate mono 24-bit vocal and stereo piano tracks from a 788t ssd recorder. Everything went fine but I had to turn on proxies to keep both v17 and v18 from hanging when doing even the simplest audio volume envelope edits before even doing anything to the video track. Playback and rendering performance were just fine (more like spectacular) without proxies but both systems would hang inexplicably unless I did cntrl-s saves after every 4 or 5 envelope edits. Added 2 more stereo tracks in post with a hardware Bricasti reverb unit. Done by adding 2 extra audio busses to Vegas fed off of 2 extra channels on an RME UCX usb audio unit hooked into the reverb ins and outs. Did the buss/recording thing in v18 and it was great. Afterwards, just copied the reverb tracks back to v17 and muted the extra busses on v18. Color grading went smooth as glass on v17 and v18. The v18 specific problems didn't show up till I duplicated the video track adding track motion and transparency to the dup. The idea being to simulate multicam. v18 blew up almost immediately. Same behavior on both my 9900k/Radeon7 and xeon/5700xt systems. Seems to be issues in v18 with track motion on hvec tracks. Maybe its amd gpu specific. I'm still working on the track motion with pip part but cannot use v18 at all for that. When I'm done I'll post a separate more detailed thread on my trials and tribulations.
The lack of a competent Audio Synchronization Tool and Text event that allows for more then one text in the same manner as Pro Type Titler are the only two features that are missing, in my book.
I've read somewhere in this thread that the roadmap for development now encompasses audio, so here's fingers crossed for the Audio Sync feature.
For the text, I do wonder if its possible to treat Text & Titles as an FX. It's going to be an odd workflow, but being able to add several text "FX" in the same event, is none the less, a solution that I'd be willing to work with.
Anything that alleviates me from the need to introduce new video tracks so I can pile text. Nesting Timelines or Grouping Tracks shouldn't be so heavily relied upon in this regard.
That's it. For me, if those two are addressed, VEGAS PRO is complete.
The rest is, essentially, "nice to have" but not as important.
Btw Audio in VP18 pro : You can open your Audio with "Edit in Soundforge Pro" and e.g. VST3 is possible: Wondering about "Open in S..." compared to "Open Copy in S...", is it destructive? In my first experiments it changes the properties (name) of the event in the timeline, converting .mp3 to wav, but the original file was not altered.
Only problem is for the upgrade version of VP18, SFP14 doesn't come with Ozone Izotope Elements 7, or the cleanup RX7 plugins, even though selection of them is hard-coded in the new SFP15 quick menu! they are installed, but you are not issued with an activation code to use them! This is what MAGIX told me when I asked.
Btw Audio in VP18 pro : You can open your Audio with "Edit in Soundforge Pro" and e.g. VST3 is possible: Wondering about "Open in S..." compared to "Open Copy in S...", is it destructive? In my first experiments it changes the properties (name) of the event in the timeline, converting .mp3 to wav, but the original file was not altered.
Only problem is for the upgrade version of VP18, SFP14 doesn't come with Ozone Izotope Elements 7, or the cleanup RX7 plugins, even though selection of them is hard-coded in the new SFP15 quick menu! they are installed, but you are not issued with an activation code to use them! This is what MAGIX told me when I asked.
As is expected for bundled third-party software worth hundreds of dollars... However, it is still far cheaper to buy VEGAS 18 with SF and then buy those plugins separately than if you bought SF bundled with them.
Something very simple... The thumbnails are still that: thumbnails. (very small) But it is IMPOSSIBLE to leave them to a custom size... 😟 It would have been more convenient to work with and not have to enlarge them every time VP is opened...
@James_Patrick Correct me if I am wrong, I presume you mean whether Vegas 18 + Vegas Post now works with Boris FX ? Vegas 17 works fine with Boris FX without Vegas post, the 3 together not. At least I never got any notification they ever fixed this for my outstanding bug reports (submitted on all companies Magix, Boris, FXhome as it is an compatibility issue - which they confirmed). Moving or removing OFX libraries from certain folders (and putting back again if needed) is suggested in the forums, but it is a hassle and is not really workable if you have multiple NLE's installed which use Boris FX...
Any confirmation if the combination of "Vegas 18 + Vegas Post + Boris FX" is fixed now would be welcome.
Yeah, I pretty much received the same response from support. Something along the lines of they are aware of the problem but have zero intention of fixing it. With the solution they provided me being "We just don't include Boris FX with Post"
Which is pretty disappointing since currently if I choose to use vegas effects, I have to close pro, move plugins, open effects, do the things, close effects, move plugins, open pro. Every time.
@James_Patrick Correct me if I am wrong, I presume you mean whether Vegas 18 + Vegas Post now works with Boris FX ? Vegas 17 works fine with Boris FX without Vegas post, the 3 together not. At least I never got any notification they ever fixed this for my outstanding bug reports (submitted on all companies Magix, Boris, FXhome as it is an compatibility issue - which they confirmed). Moving or removing OFX libraries from certain folders (and putting back again if needed) is suggested in the forums, but it is a hassle and is not really workable if you have multiple NLE's installed which use Boris FX...
Any confirmation if the combination of "Vegas 18 + Vegas Post + Boris FX" is fixed now would be welcome.
Yeah, I pretty much received the same response from support. Something along the lines of they are aware of the problem but have zero intention of fixing it. With the solution they provided me being "We just don't include Boris FX with Post"
Which is pretty disappointing since currently if I choose to use vegas effects, I have to close pro, move plugins, open effects, do the things, close effects, move plugins, open pro. Every time.
This is something that either Boris or FXHome would have to correct, probably Boris.
@James_Patrick Correct me if I am wrong, I presume you mean whether Vegas 18 + Vegas Post now works with Boris FX ? Vegas 17 works fine with Boris FX without Vegas post, the 3 together not. At least I never got any notification they ever fixed this for my outstanding bug reports (submitted on all companies Magix, Boris, FXhome as it is an compatibility issue - which they confirmed). Moving or removing OFX libraries from certain folders (and putting back again if needed) is suggested in the forums, but it is a hassle and is not really workable if you have multiple NLE's installed which use Boris FX...
Any confirmation if the combination of "Vegas 18 + Vegas Post + Boris FX" is fixed now would be welcome.
Yeah, I pretty much received the same response from support. Something along the lines of they are aware of the problem but have zero intention of fixing it. With the solution they provided me being "We just don't include Boris FX with Post"
Which is pretty disappointing since currently if I choose to use vegas effects, I have to close pro, move plugins, open effects, do the things, close effects, move plugins, open pro. Every time.
This is something that either Boris or FXHome would have to correct, probably Boris.
Whoever. I'm always going to continue using Boris FX. Only difference is if I use it in vegas or Adobe. There's some things I prefer in vegas. But simple plugin support not working since launch. And now into a new version and still not fixed. When using your app becomes a chore, those little preferences begin looking less and less important.
Included items are different from magix splash page than in shopping cart.
I'm responding to an email link that takes me to a splash page that shows Boris Continuum, ActionVFX Action Pack, Zynaptiq Unveil, and NewBlue Transitions 5 as part of Suite. When I add Suite to my cart, I only see Spectral Layers as a separate line item.
Are the other items included?
I'm not quite sure how this works, as I usually only purchase Edit. Thanks for any clarification.
Just be aware that Boris Continuum is not the complete Boris continuum FX, but selected elements from the Boris complete continuum FX as stated correctly in the comparison.