VP8b Wav audio export crashes application

Christian de Godzinsky schrieb am 02.02.2008 um 14:00 Uhr
Hi,

So far everything has bee smooth with VP8b and XP x64 on my quad core.

I get fatal application error (and a clean exit) when I render out Scott audio wav files (44100@16bit). This happens especially with short renders, less than 2 minutes...

Anyone else seen this behavior ??? Any hints ????

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

Kommentare

Christian de Godzinsky schrieb am 02.02.2008 um 16:56 Uhr
Hi,

Here is some more info about the problem:

Sony.MediaSoftware.MediaMgr.MediaMgrException: Rethrow of same type to avoid stack trace loss ---> Sony.MediaSoftware.MediaMgr.MediaMgrException: Paths must be either drive letter or UNC based (Misty Country Repaired.wma).
at Sony.MediaSoftware.MediaMgr.ItemMgr.MapPathToVolume(String fullPath, String& relativePath)
--- End of inner exception stack trace ---
at Sony.MediaSoftware.MediaMgr.ItemMgrFactory.TxDeadlockVictimRetryProxyInvocationHandler(Object target, MethodBase method, Object[] parameters)
at Sony.MediaSoftware.Tools.ObjectProxyImpl.Invoke(IMessage msg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Sony.MediaSoftware.MediaMgr.IItemMgr.MapPathToVolume(String fullPath, String& volumeRelativePath)
at Sony.MediaSoftware.MediaMgr.ItemFactory.CreateFromFile(String fullPath, ItemFactoryCreateParams createParams, TagTreeNode& newUserDefinedTreeNodes, IDictionary& newUserDefinedPropTypes)
at Sony.MediaSoftware.MediaMgr.RelationWorker.FindOrCreateItem(String name, String filePath, String originalFilePath, TagTreeNode tagTreeRootNode, MediaLibraryChanges& changes)
at Sony.MediaSoftware.MediaMgr.RelationWorker.CreateRelation(RelationType type, String sources, String targetName, MediaLibraryChanges& changes)
at Sony.MediaSoftware.MediaMgr.RelationWorker.DoWork(Boolean cancelRequested, Object genericArg)
at Sony.MediaSoftware.Kernel.Threading.WorkerBase.DoWorkWrapper(Object genericArg)

Can anyone explain what this means in plain language? What can I do to avoid this error? Am I doing something wrong?

Regards,

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

pwppch schrieb am 02.02.2008 um 22:36 Uhr
Please fill out your system specs in your user profile.

We do not support Vegas on XP 64.

The problem appears to be related to the Media Manager. You may want to try disabling the Media Manager from the General Prefs page.

Peter
Christian de Godzinsky schrieb am 03.02.2008 um 18:45 Uhr
Hi Peter,

I highly appreciate your answer! Nice to know you are monitoring the forum :)

Yes - I admit - I took the (however so far no regrets) risk of installing VP8 on XP x64. Everything runs smooth and nice. I wanted to enter the 64-bit world without stupid memory restrictions, while waiting for the much avaited Vegas Pro 64 bit version. I sincerely hope it will run on XP x64, not only on Vista 64. No serious users have Vista installed...

I will meanwhile disable the media manager, a nice feature to have, but I can live without it.

Just for your information and to help you pinpoint the problem, the problem occurs only if I have audio clips on the timeline that are "orphans":

In other words, whe I open the application I answer (when the popup occurs asking for missing files) "ignore and leave them off line", then I have problems. If everyting is on-line, the application works ok.

I hope the development work with the 64-bit version goes smoothly. Do you have any new schedule for it? Or just even an estimate to publish, quite many of us are waiting!!! And do I hope for too much if I assume it also works on XP x64 ???

Sincerely,

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

pwppch schrieb am 04.02.2008 um 15:08 Uhr
There is no announced release date for Vista 64 bit release of any of our products at this time.

There is no planned support for XP 64. Vegas and our other products depend upon drivers and third party components to work correctly. There is little third party interest or activity on XP 64 and many key components that Vegas and our other products depend upon will not be available under XP 64. There is little - if any - chance of this changing.

Peter
Christian de Godzinsky schrieb am 07.02.2008 um 10:36 Uhr
Hi,

In other words, you are forcing us to install Vista if we like to run Vegas 64 bit??!!

What a shame!!! Vista stinks. For sure - not your fault, but the situation is anyhow becoming very frustrating. Vegas could become the only reason why I we would be forced to install Vista - if that is the only way to go (64 bit)... Aaarghh...

Open your eyes and please, reconsider this seriously, there are fore sure others professional users that also agree, and can se the beginning of a big storm... XP x64 is a very stable platform, albeit not as widespread as XP, but a serious professional platform that has been around for a while. It deserves some professional software, as Vegas Pro!!! Vista is a joke. Vegar Pro 64-bit should run on any (Microfost) 64 bit operating system!!!

Sincerely,

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

Kennymusicman schrieb am 07.02.2008 um 13:21 Uhr
"Open your eyes and please, reconsider this seriously"

No - focus on what is forward - not what is behind! Xp64 never took off, and never will. Yes, it's good but because it is based on server code. Vista is also the same idea. If you really want to avoid vista then wait for Windows 7, but please, lets not step backwards for a dead OS.

Why do you think there were never a large amount of drivers for XP64...
pwppch schrieb am 08.02.2008 um 07:43 Uhr
In other words, you are forcing us to install Vista if we like to run Vegas 64 bit??!!
Yes, but saying we force you is a bit harsh. We require a specific OS based upon the technical requirements of our products. All software has OS requirements.

Vista stinks.
Why?
What problems did you run into?
Have you spent any time using it?

Why are you not using Vista 64?

..there are fore sure others professional users that also agree, and can se the beginning of a big storm... XP x64 is a very stable platform, albeit not as widespread as XP, but a serious professional platform that has been around for a while. It deserves some professional software, as Vegas Pro!!! Vista is a joke. Vegar Pro 64-bit should run on any (Microfost) 64 bit operating system!!!

I am sure there are others that like XP 64.

However, Vista is a professional platform. I know lots of serious professionals that use Vista. I know a lot of professional tools - serious tools mind you - that support Vista and Vista 64. More are on the way.

Vista is not a joke, and it is not going away.

XP 64 is not widely supported by third parties and some of the compenents Vegas requires will NEVER be available on XP 64.

Peter
Christian de Godzinsky schrieb am 11.02.2008 um 08:54 Uhr
Hi Peter,

I really highly appreciate your comments and feedback, even though we think differently about many things (especially Vista)! I value highly the possibility to have a fruitful discussion with an insider, I am not probably wrong when I say that the forums and we (the Vegas) users deserve more of this kind of close encounters :) Highly appreciated !!!

I have to apologize if I sounded a little harsh, you should never mix feelings into your feedback, but sometimes it's hard to avoid. And please note that my native language is not english, that might explain something ;)

However, my comments about Vista are not based on feelings, just on pure experience. I never run Vegas on Vista, so my experiences are based on using other (serious) software.

There IS a general problem about Vista. I do not want to turn this thread into a detailed Vista complaint list. You can read about this is so many other forums and columns... Or just interview any serious IT-people...

I just want you to know that our IT-department has completely banned Vista for now. Every new PC entering the company is reinstalled with XP or XP x64 (some even running Linux). These are stable platforms that perform fast and well, and without any unnecessary ridiculous eye-candy or other overhead. Microsoft was even forced to publish a "downgrade" path to XP for unhappy Vista users... Not without reason, or what do you think? For me - Vista stinks.

You are right about the fact that Vista is not going away. Applications as (the upcoming 64-bit version of) Vegas will take care of that. I understand that you might be in a difficult position here. Probably it is so that the tools you use to write Vista code do not support the XP x64 platform. It seems that these third party vendors have doomed XP x64 it as a dying operating system. I completely understand that you are here between "two fires". No-one wants to put his eggs in the wrong basket. Some decisions in the industry are not based on facts, just feelings...

It is too early to call XP x64 a dying platform. Yes - every platform dies sometime. But XP (X64) It will NOT die before Windows 7 is out. And that can still take some time!!! Meanwhile we need stable working 64-bit platforms - as XP x64 (or the Server version). There is excellent support from many companies, we have not found any hardware yet that would not be compatible with XP x64 (excluding hardware older than 3 years).

The important thing is that you keep your customers or end users informed. There seems to be lots of uncertainty about the Vegas 64 bit version.

You should consider to immediately officially publish an update about the new time schedule. You should also make it immediately public that you ONLY support Vista 64-bit - not XP x64!!

Vegas deserves a good and stable 64-bit environment, where the artificially stupid memory restrictions are gone. It's a pity if XP x64 is not on the list. Is it totally out of question? What are the development tool restrictions? Could Vegas 64 be built for XP x64, omitting some (for many users unnecessary) fetures like the media manager?

I do not asssume that you will give me a complete explanation about the internals of code writing procedures, but it would have helped at least to understand better what are the restrictions (by third parties) you mentioned.

Thank's again Peter for your kind assistance.

Best regards,

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