-
Videoon 5/25/2016
Bye Sony, Hi Magix !
Jamon, I simply meant I don't know the *future* of Vegas. I don't work for MAGIX and don't know their management or their plans. I just posted here so people did not think my little G+ post was implying some much bigger story. No need for a petition on my behalf, but I appreciate the kind thoughts about my poor little sick Tiny Tim. I'm sure he'll pull through. Chris
-
Videoon 5/25/2016
Bye Sony, Hi Magix !
Hi Tim L, thanks for the shout-out. That Google+ post is just my personal opinion, by the way. I have very, very little inside knowledge about the future of MAGIX+Vegas so don't read too much into my message. :-) Chris
-
Videoon 7/16/2014
File Missing?? No its not. HELP!
If the files really are there, I'll speculate that it has something to do with file permissions: Vegas can't open the files for some reason. Perhaps you can try the Security settings on one of the files to see if you have read access to it.
-
Videoon 7/16/2014
can't install vegas 13 - failed to register module
ryclark, Thanks very much for reporting success to this thread! This particular problem has consumed a lot of time for our installer team at SCS with not much to show for it. We had suspected C++ redist, but never could prove it because we've failed to get a machine into the bad state despite considerable effort. If anyone else can try ryclark's solution and report back success or failure here, it would be very helpful to us. Chris
-
Videoon 6/24/2014
Vegas12 keeps crashing with nvoglv64.dll exception
Steve Mann, "Unmanaged" means the crash was in native code, i.e. C++. "Managed" means the crash occurred in a virtual machine language, i.e. C#. Most of the Vegas crashes are in unmanaged code, whether Sony code or 3rd party code. In this case, "nvogl64" is Nvidia's 64-bit OpenGL driver. Chris
-
Videoon 6/11/2014
Vegas 13 issue or user error?
Sort of. The output render will indeed be 5.1, but if the nested project has any 5.1 content it will be truncated to stereo for inclusion in the parent project (only the first two channels are kept and the other 4 are ignored) and then upmixed back to 5.1 for render. The core reason for this limitation is a technical detail: the audio of a nested project is always pre-rendered to a WAV proxy when you first bring it into the parent project. That audio proxy is always 32-bit stereo float PCM. So, if you are doing a surround project, you should use nested projects only for video or ambient audio, not for precise audio.
-
Videoon 6/11/2014
Stability - lucky 13 vs 12 vs 11?
@24Peter, I haven't heard about that "parameters unsupported" issue before. Can you offer any more details? As for the crash on exit, that bug is DRIVING ME CRAZY! I've been working on it off-and-on for 4 months, and it seems impossible to reproduce reliably. The good news is that it's totally harmless because the crash happens after we close all projects, media, and preferences but of course it's ugly.
-
Videoon 6/10/2014
Vegas 13 issue or user error?
Good discovery, BobMoyer. Indeed, dragging a .veg from Explorer (either Windows Explorer or Vegas Explorer) to the timeline makes a *nested* project inside of the current project, and we only support stereo for nested projects. Chris
-
Videoon 6/10/2014
What is the 64-bit format Code for vegas ?
Nice analysis, NormanPCN.
-
Videoon 6/9/2014
V13 Loudness Meters Question
wwaag, how are you stopping playback? If you stop via Stop or Pause buttons (Space or Enter) then the numbers should persist in the UI until you seek or play again. If they don't, I'd like to hear some steps to reproduce because it would be a bug (it was a bug during beta, but I fixed it back in March). Or maybe you've got a plugin that's causing a seek and wiping out the data?? As Grazie says, you can get a persistent loudness report via "Tools > Generate Loudness Log" or via the new option on the Render As... dialog. Chris
-
Videoon 6/9/2014
What is the 64-bit format Code for vegas ?
Yes, XAVC Intra is 64-bit. All of our video file formats are 64-bit except QuickTime and XDCAM Proxy. We load Apple's QuickTime DLL directly into FileIOSurrogate so you will not see QuickTime in the process list unless you manually launch that app. Chris
-
Videoon 6/9/2014
Vegas Pro 13 crashes on render, but 11 works fine
A useful nvidia fact is that the version number "9.18.13.3165" is generally the same as "331.65" (look at the last 5 digits). I don't know if that's always true, but I've noticed the pattern a couple of times.
-
Videoon 6/5/2014
What is the 64-bit format Code for vegas ?
One more note about memory: all of our frame caching happens on the 64-bit side, so you should rarely see the 32-bit FileIOSurrogate.exe consuming a large amount of RAM even if you have a lot of QuickTime files on your timeline. In theory anyway, since neither we nor Apple can control what happens inside the various QuickTime plugins...
-
Videoon 6/5/2014
What is the 64-bit format Code for vegas ?
Laurence and John_Cline are right. Apple only makes 64-bit QuickTime for Mac, not for Windows. All of our video file formats are 64-bit except QuickTime and XDCAM Proxy. And if your QuickTime .mov is H.264, we even try to read it with our 64-bit AVC MP4 reader first to gain performance, falling back to QuickTime if that fails (.mp4 and .mov are very similar under the hood). Several of our audio formats are 32-bit (MP3, Ogg, AC-3, AAC, Atrac), but those are obviously not as memory or bandwidth intensive so converting to 64-bit was never worth the effort.
-
Videoon 5/28/2014
Crash during Rendering to BD AVC (VP12b770)
set, I found your crash (thanks for the keyword -- brilliant idea) but unfortunately the crash occurs in the AMD OpenCL DLL on a thread spawned by the AMD driver, so I cannot determine a cause for the crash. I wish I could give you advice for how to avoid crashes like this, but I regret that I do not have any. Chris
-
Videoon 5/27/2014
can't install vegas 13 - failed to register module
One of our engineers has been working directly with user gwailo. So far, we haven't been able to reproduce it at SCS and when we got detailed install logs, the results have been pretty perplexing. We'll continue working on it and will definitely post here when we figure out a solution.
-
Videoon 5/27/2014
File sorting in project media window
The way the Vegas P2 plugin works is that it starts with the video clip and looks for the related clips as follows. Say the video clip is 0001XX.MXF. The audio should be in files ..\..\CONTENTS\AUDIO\0001XX01.MXF thru ..\..\CONTENTS\AUDIO\0001XX04.MXF. If not found in the ..\..\CONTENTS\AUDIO folder, then we look for the audio files in the same folder as the video. The clip metadata likewise should be in ..\..\CONTENTS\CLIP\00001XX.XML, or in the same folder as the video. We do not use any of the other files (VOICE, ICON, PROXY). (that's a bit of a simplification, but it's close enough) So if you choose to rename, make sure you rename the video, audio and clip in the exact same manner, preserving the audio channel number in those filenames, and optionally keep or ignore the P2 directory structure.
-
Videoon 5/27/2014
Vegas Pro 13 Crash on startup
DanVM, Yes, we believe it blocks all of our apps that use ASIO, although we've verified only a representative subset. Chris
-
Videoon 5/27/2014
Media tags in VP13
Indeed, you're right. We're failing to create a .sfl sidecar file for storing the media tags along with the P2 video file. I'll file a bug for this. Thanks for reporting the problem.
-
Videoon 5/27/2014
Vegas Pro 13 Crash on startup
apsc, OK, then JRiver Media Center 19 is 99% likely the cause of the crash -- we see the same crash with many other Sony products, and other vendors have reported issues with the JRiver ASIO driver as well. I've pursued this at length with their staff but we've reached no satisfactory resolution. So, in the next version of VP13 we'll simply refuse to load the JRiver DLL in our ASIO host. In the meantime, the best solution is to uninstall JRiver, but other workaround solutions include: 1) Uninstall JRiver temporarily, then launch Vegas, then reinstall JRiver. If you never go to the ASIO tab of the Preferences or clear your preferences, then we will likely never load their ASIO driver again and you won't experience the crash. This works is because we only probe the system for ASIO drivers on the first launch of Vegas and cache the results. But anything that causes us to rebuild the cache and reload the ASIO driver will crash Vegas again. 2) Disable the JRiver ASIO driver. **This is a quick-and-dirty fix and will prevent JRiver's ASIO feature from working.** Open Regedit.exe, go to "HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\JRiver Media Center 19" and rename the "CLSID" key to something like "CLSID_disabled" so Vegas won't find it. To re-enable it, change the name back. I'll also continue to work with JRiver and hopefully we'll reach a solution that makes everyone happy in the long run.
-
Videoon 5/27/2014
Build 310 change to another languaje interface
The official translations are not ready yet. They are in progress and will be available in a future update. Chris
-
Videoon 5/27/2014
File sorting in project media window
Yeah, sorry, that particular issue bothers me too with P2 clips. But we decided that matching the Windows Explorer sort order was the least bad solution. The P2 file naming is the main place this happens because of the uniquifying random characters after the clip number in the file name. That means that any better sorting would require P2-specific code in the explorer window, which we generally try to avoid because our P2 support is all in a plugin. So, I regretfully say that it's highly unlikely we'll change the software to sort in the human way you'd naturally prefer for these files. I hope you understand. Chris
-
Videoon 5/23/2014
Computer Crash.
Bummer. If you send Sony a crash report with your user name in the message, I'll look for it in the database. Chris
-
Videoon 5/23/2014
no audio when rendering
That is really puzzling... Do you have some audio effects or audio hardware that require real-time rendering? If so, then as a wild guess I might say that a slower hard drive might cause the render to become slower than real time and the FX might fail? I'm not sure it that even makes sense, but I can't think of a better explanation right now. Chris
ChrisDolan (SCS)
Offline, Member since 9/10/2013