Comments

Tom Pauncz wrote on 4/6/2015, 4:54 PM
Well, that's just dandy.

What about the long outstanding Closed Captioning issue SONY??

Not thrilled.

Tom

EDIT:
Apologies SONY. When I did not see the CC issue as listed in notable fixes, I assumed ... MY BAD. It seems that this has indeed been fixed. THANK YOU!
xberk wrote on 4/6/2015, 5:08 PM
Installed Build 444 without a problem ....... so far.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

Paul Fierlinger wrote on 4/6/2015, 6:29 PM
Issue with Preview Master Bus has not been addressed and still crashes Vegas unless you keep it floating.
videoITguy wrote on 4/6/2015, 6:41 PM
Subject: RE: VEGAS PRO 13 and PXW-X70
Reply by: videoITguy
Date: 3/3/2015 4:18:03 PM

Rumor has it ...XAVC-L codec news straight from the top at Sony (SCS) today. but can't divulge sources at this point....-We at SCS are in the process of finishing the work on VegasPro 13 XAVC L support and the plan is to have that out before the beginning of April 2015."

FYI _
Notable fixes/changes version 13.0 (Build 444)

Added templates for rendering XAVC long-GOP files.

Notable fixes/changes in version 13.0 (build 428)

Added support for HitFilm 3.0.

Notable fixes/changes in version 13.0 (build 373)

Vegas Pro 13 can now open Movie Studio 13 project files.
Added support for rendering XAVC HD (1920x1080) video in 50i and 59.94i formats.
Fixed a bug that could cause Vegas Pro to crash during startup on some machines that have JRiver Media Center installed.
Fixed a bug that could cause Vegas Pro to crash when using File > Import > Import Media from Project.
Fixed a bug that could cause Vegas Pro to crash on some computers when expanding the HitFilm plug-ins in the Video FX window.
Fixed a bug that could cause Vegas Pro to crash when dragging some audio plug-ins from the Plug-In Manager to audio events.
Fixed a bug that could cause Vegas Pro to hang when playing some H.264 MP4 video files.
Fixed a bug that could create a loop region when attempting to multiselect locked events using shift-click.
Fixed a bug that could cause the Project Media window to scroll unexpectedly when right-clicking an event and choosing Select in Project Media List.
Fixed a bug that prevented timecode from being read for Panasonic P2 clips that span multiple files.
wwjd wrote on 4/6/2015, 6:59 PM
now Vegas crashes on every exit. Great. :)
Tom Pauncz wrote on 4/6/2015, 9:46 PM
Not here, mate.
Tom
mountainman wrote on 4/6/2015, 11:30 PM
I don't need to render to it. I NEED TO BE ABLE TO READ IT. Still can't open -L files from my X70. Maybe its me. j
NickHope wrote on 4/7/2015, 2:39 AM
No crashes on exit here either yet.

Of the bugs that affect me, only the following one is fixed. I wish SCS would report such bug fixes in the release notes like they used to.

Closed captions do not display

However none of the following 7 bugs are fixed:

1. Crash when renaming files in Vegas Explorer window
2. Panasonic GH4 23.976p and 24p clips have extended video
3. Crash after paste event attributes
4. Bug loading windows layout at startup
5. GPU bug: Pale edges of imported Photoshop layers
6. Sony Sharpen behaves differently with GPU
7. Project Properties Frame Rate Undo Bug

Disappointing, especially considering it's more than 4 months since the last release.

Of those bugs, #1 only affects VP13. The others affect both VP12 and VP13.
megabit wrote on 4/7/2015, 2:43 AM
It's you. VP13 new build reads XAVC-L without problems (at least the 1080p version files from the X70 camera that I just tested.


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)

PeterWright wrote on 4/7/2015, 6:15 AM
SCS why would you include fixes in Build 444 and not list them?
wwjd wrote on 4/7/2015, 8:33 AM
^ This.
SonyKevin wrote on 4/7/2015, 11:11 AM
Hi, all--

You're right -- the Closed Captioning fix should have been included in the "Notable fixes/changes in version 13.0 (build 444)" list.

I've revised the release notes, and the new version will be posted shortly.

I apologize for the confusion.
Tom Pauncz wrote on 4/7/2015, 11:20 AM
Thank you Kevin....
That one was a long time coming.
Tom
videoITguy wrote on 4/7/2015, 1:21 PM
for clarity a re-post made here:
Subject: V13 Build 444 Problem
Posted by: ScheffFrog
Date: 4/7/2015 11:02:56 AM

Downloaded Build 444 and installed it. However, is it just me... When I open Vegas it shows Build 428, not Build 444. Did it not install? The installation says it updated just fine.

Anybody else notice this? And... is it possible I didn't really install the update? It said that it saw the older version...

Help!
Ribbit...
mountainman wrote on 4/7/2015, 5:15 PM
Well it seem its not just me having trouble with x70-L files. DVinfo folks are having the same problem.

Vegas seems to load files from other cams that are using the -L format but not from the x70.

I'm sure they will figure it out. j
videoITguy wrote on 4/7/2015, 5:37 PM
A single sample experience - use this info with a grain of salt.

It WILL IMPORT XAVC-L files from the Sony PXW-X200 but IT WILL NOT IMPORT XAVC-L files from the PXW-X70. At least that's my - the original writer - experience of this moment. If anyone else can confirm this ASAP I, the user reporting this, would love to here back. ( I ) have contacted Sony SCS and have sent them files and media file breakdowns on the differences in the file structures of the two cameras in question. I've only just done this so no response as yet.

The ONLY difference I can see in the file structures between the two XAVC-L 422 50-mbit 50P files from the two different cameras is in the file 'Transfer characteristic' readouts. See below:

Sony PXW-X200
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Sony PXW-X70
Color primaries : BT.709
Transfer characteristics : IEC 61966-2-4 ?????? What's with this?
Matrix coefficients : BT.709

Why the difference in the PXW-X70 having IEC 61966-2-4 characteristics as opposed to the PXW-200 and the other XAVC-L cameras which all show BT.709 as the transfer characteristic?
OldSmoke wrote on 4/7/2015, 5:53 PM
[I] IEC 61966-2-4 ?????? What's with this?[/I]

Isn't that x.v.Color ?

BTW: The AX100 files show the same transfer characteristics as the X70.

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)

NormanPCN wrote on 4/7/2015, 6:10 PM
The HSL Adjust effect GPU=ON problem has not been fixed.

The Wave Hammer Demo problem is still not fixed.

and of course the Titles and Text fonts issue is still there.
wilvan wrote on 4/8/2015, 12:56 AM
Discussed the wrong loading windows lay-out after restart with the support team after I got a reply about 6 weeks after submitting.. They are way too busy with the catalyst and spectralayers issues and did apologize for the laste reply. When they finally understood the issue of the windows lay-out , I was asked to submit a prouct suggestion to the other ? team . ( they also confirmed being aware of the mouse getting stuck when trying to glide the audio master and that this will b fixed later in a next release ).
Petty vegas pro being putten the last on the list. ( catalyst edit gets priority since a while )

Sony  PXW-FS7K and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices )
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 , 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2018
Adobe After Effects CC 2018 & Adobe Media Encoder CC 2018
Avid Media Composer 2022.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

megabit wrote on 4/8/2015, 2:20 AM
On my FS7 sample, MediaInfo also reports "Transfer characteristics : IEC 61966-2-4", and yet I can ingest the file into VP13 444. However - even though the sample clip I got is just 4:2:0, 8 bit - it being Long-GOP throws Vegas to its knees, literally.

Frankly, I don't get it as the sample clips from the AX100 I have are also "AVC Long" (as Catalyst Browse reports) , 4:2:0 8 bit, and they play full speed in Vegas... OK, these are the "consumer" XAVC-S codec, but - with everything the same - what is the reason of FS7 codec being so "hard" for Vegas?

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)

wwjd wrote on 4/8/2015, 8:51 AM
YEA! Fixing new profit stuffs instead of fixing CURRENT dysfunctional product! FTW :(
videoITguy wrote on 4/8/2015, 4:57 PM
Re: Subject: RE: New Build 444
Reply by: SonyKevin
Date: 4/7/2015 9:11:02 AM

Hi, all--

You're right -- the Closed Captioning fix should have been included in the "Notable fixes/changes in version 13.0 (build 444)" list.

I've revised the release notes, and the new version will be posted shortly.

I apologize for the confusion.

As of the date of this post edit - here is the revised explain for Build 444
2.0 What's New
Notable fixes/changes version 13.0 (Build 444)

Added templates for rendering XAVC long-GOP files.
Fixed a bug that prevented closed captions from displaying in the Video Preview window.
Fixed a bug that prevented shot marks from being read in 4K XAVC clips.
Christian de Godzinsky wrote on 4/8/2015, 4:57 PM
Hi,

Build 444 crashes repeatedly - just clicking the header of the first empty column in the Explorer window (in the details view) and boom!!! It does not matter if the timeline is playing or not. Even an empty project can be crashed like this.

OK - I should not click the empty hearer - but:

HOW CAN SUCH A BASIC THING CRASH A PRO APPLICATION??? HOW IS SCS TESTING THE SOFTWARE?

Is this a bug that has bee there for a long time? And not yet fixed? Can someone reproduce? Gooosh...

Cheers,

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