-
Videoon 6/24/2014
WMV encoding & playback /VP11
Thanks John, I will try re-rendering with your settings and see what happens. Will be back to report. Was just seeing if I could create a listing of similar spec details from the file that won't play in WMV Player (though to note, it does in Media Classic or VLC) but Gspot won't provide a video rendering 'path' either. Only noteworthy thing about this file is that it's 50ffs. For the web, I never think there's a good alternative to wmv. FLV always seems to be for streaming servers, and mp4 files still seem pretty rare, for downloading -- but maybe I'm stuck in the past somewhere! :) Wondering what format you render to most often (for web purposes).
-
Videoon 7/16/2012
Re: Temp rendered file before copy
I solved this issue by turning back on my page-file (which effectively doubled the available memory from 4GB to 8GB). I don't know how Vegas handles memory when it's rendering, but when I had 4GB available, RAM usage was getting up to 99%. Presumably, when it came to copying across the file (I still believe that to be the case), being at 99% it was just bombing out.
-
Videoon 7/10/2012
Re: Temp rendered file before copy
lol Chienworks - how could you do that to my bubble! Actually with the wmv render the final file doesn't seem to grow at all during the time of the render. All that seems to take place is an approx 6k header is written - and remains that way through the whole render time. It's only after render time reaches zero that the file seems to be written. I'm presuming there's different behavior for different render types/codecs. You may be correct though - I can't say I'm 100% certain at this time.
-
Videoon 7/10/2012
Re: Temp rendered file before copy
Hi Soniclight - you know - I bet that is it. Before I read your post I had thought about that as an issue - but thought - no that can't be the case - as there's 14GB free & I'm expecting a final file of only about 6-7GB... But thinking about it again - if the temp file is 7GB and the new final file is going to be 7GB - at a certain point in time, the system is going to need 14GB to hold both (until it deletes the temp file). Hey presto - thanks Soniclight. Now I've just got to build up the fortitude to go through the 12 hours again!!! And free up a bit of disk space - somehow...
-
Videoon 7/10/2012
Stabilizer help needed bad here
I found Deshaker worked a treat for me & I'd recommend it.
-
Videoon 7/10/2012
Set 'Match Output Source' on all keyframes
Thanks Kimberly, Gary & altervic :)
-
Videoon 7/5/2012
pan tilts stuttering on rendering..
Hi Paul, I enjoyed watching the video :) Be interesting to see if this workflow helps with the stuttering: http://www.bubblevision.com/underwater-video/Vegas-YouTube-Vimeo.htm [I haven't tried it myself yet - but was just reading it & recalled your post/video.] Couple things I noticed: 1. The onscreen fonts - would have been nice to match them to style of shop (bill board, products text), etc, maybe a light script font. 2. Would have been nice to 'glam' up the young lady/entrepreneur using lighting a bit more. She seemed a bit far away - I was wondering if it was perspective created by the arrangement on the left (which was interesting in itself). Anyway - congrats - I was impressed. Simes
-
Videoon 7/2/2012
OT: Revenge Of The Great Camera Shootout
Hi Laurence, aside from WB, aperture, & basic scene presets, etc, what sort of settings are you referring to.
-
Videoon 7/2/2012
Will v11 be fixed before v12?
Has a very standard spec, low cost, easily available brand PC been identified as a system that runs Vegas 11 perfectly. For example, I'm running on an ASUS P5N32-E SLI PLUS with 4 gig mem, GeForce 8400 GS & no disk paging file - and - touch wood (dare I say it!), the system is very stable. (I also reduced the cpu voltages down to the VID figure shown in the Core Temp app (as before, the cpu was overheating while rendering and switching off). I'm probably not pushing vegas too hard, though this is essentially quite an old low cost system now - at least if a used system is obtained from ebay.(approx 300-400 dollars). I'm imagining that there are ibm, dells, hp models that are very standardised that are also run vegas very stable. (Like I described in another post, back with vegas 5, when all else was crashing during long renders, I found that a cheap Acer laptop with 256k ran it perfectly). I realise it's not like anyone's got money to throw around, but if such a low cost system can be identified, the investment might be considered worthwhile - in terms of all the saving of stress & time with crashing apps. I realise this doesn't solve the actual issue of software bugs (and/or driver interface bugs) - but it might be a way round for now for some who really want to use V11. Who else has a standardised widely available low cost off the shelf system, that is stable. And anyone else with a stable ASUS P5N32-E SLI PLUS based system like mine above.
-
Videoon 6/19/2012
Stabilization & veg size
After getting grips with deshaker & it's amazing deshaking - I have to agree all the more with Steve, that it would be best to leave vegas' inbuilt stabilisation as it is. I'm not actually sure why the vegas developers didn't focus more on an inbuilt deshaker interface instead. It's still not too late for that - as it strikes me the script method & frameserver method both have the advantages which might be combined in some manner. I don't know if the deshaker log size (i.e. the log deshaker builds of adjustments to apply for stabilisation) is directly comparable with the info vegas stores for stabilisation in the veg file - but compared to the 220MB veg file described above the full deshaker logs for the same video is 8.5MB
-
Videoon 6/19/2012
Deshaker settings
Been doing a lot of deshaking! Amazing program. Essentially, the footage I had was the equivalent of a studio interview situation with a fixed but single coloured background. I presumed deshaker v3 would find it a piece of cake to lock onto a fixed background, but it didn't find it so easy with the standard settings - & Gunnar explained me that in such a situation, a pattern on the background is what is needed for deshaker to lock on. Anyway, in case it's useful, Gunnar suggested trying out the following setting adjustments - and they did make a big difference. This is the gist of what he wrote me: === You could try decreasing "Discard motion of blocks that have 2nd best match > best - X", maybe all the way to 0. And if the video has very little noise you could try and decrease "Discard motion of blocks that have max pixel value diff < X" a little too, but not too much. If the vectors don't show any motion when there is motion, that setting is too low. Also, if the camera isn't moving around too much, you might want to decrease the value of "Discard motion of blocks that move > X pixels in wrong direction", to 1 or so. That way deshaker will try to ignore even objects that move very slowly. ===
-
Videoon 6/14/2012
Deshaker settings
Here is the detailed settings page I've been using to try & work out how to set: http://www.guthspot.se/video/deshaker.htm
-
Videoon 6/14/2012
Am I alone with all these v11 problems?
Yes Hitime, I see now min spec is Vista/Windows 7
-
Videoon 6/12/2012
Am I alone with all these v11 problems?
Hi Hitime - gee that sounds really frustrating. I've experienced similar myself several years back & it drove me nuts as vegas kept crashing near the end of very long rendering jobs. I ended up completing the job on my daughters low end acer laptop as was the only thing I could find that didn't crash. I was wondering if you'd tried running vegas on a virgin XP SP3 install (dual booting on same computer) with all latest drivers & updates (inc. net framework 4). I've no idea if it would fix it - but that's what I'd try as I find XP is incredibly stable & a lot lighter than later OS's. Be really interested to hear the results of such a test. If you've a copy of XP - would only take a couple of hours to test.
-
Videoon 6/12/2012
Is 682/683 the last build?
It's been many 4-5 years since I last used Vegas, so I'm surprised to hear major crashes are still happening for some users/installs. Maybe vegas's crash reporting tools could be improved, so dev can establish more precisely what's happening for users with crashes. Saying that, when Vegas works nice, I still think it's the nicest piece of NLE software around. So intuitive to use. I always find Adobe stuff back to front for my thinking. I was using LR4 recently, & it was typical Adobe functionality - to move a crop area to the right - I actually had to move the image to the left (so that the crop moved relatively to the right). Must have moved it the wrong way to begin with a 100 or more times.
-
Videoon 6/12/2012
Stabilization & veg size
Hi Steve, === 'I can just see the cascade of "unrelated" problems when this feature is added to Vegas. And I repeat, If It Ain't Broke, Don't Fix It!' === Yeah - I hear you - and know exactly what you mean - I too consider: 'If It Ain't Broke, Don't Fix It!'' one of the great truths of life :) Am going to give the deshaker script a go.
-
Videoon 6/12/2012
Stabilization & veg size
Thanks riredale - am going to give the DeShaker script a go.
-
Videoon 6/12/2012
Rendering progress window
I realise this issue is only a minor cosmetic thing - in the bigger picture... I found what I was remembering - which is that during pre-renders - there's a progression bar on the bottom left (as well as the popup). An option just to use a bottom left progression bar would be a nice addition.
-
Videoon 6/12/2012
Towards Stability?! - Separate Bak Folders?
Thanks Gary James, great idea - I always use save as to create a continual set of backups (in any app I'm using) - so this is great.
-
Videoon 6/11/2012
Stabilization & veg size
Hi Chienworks, I see what you mean, though I'm not sure it's using track motion keyframes in the way they were originally intended - i.e. veg & keyframes were designed/envisaged to hold 10's/100's, whereas I guess this implementation is using 100,000's+! Anyway, the issue is - is a 220MB+ veg file workable/safe... or is there a better way to hold the info...
-
Videoon 6/11/2012
2 More VP11 Finished Products
Hi Jaums, just been watching the first video. Seems to have some quality, though on the stills transitioning I felt you could have taken significantly longer for each transition & gone a lot slower (including displaying many of them for slightly longer). The transitions felt quite rushed for me as a viewer.
-
Videoon 6/11/2012
Stabilization & veg size
Dear Steve, yeah, but actually have a think about these figures: Without stabilisation (for 34 min project): 26KB With only 59 seconds of stabilisation in the 34 mins (very low level setting): 6482KB Given I need to stabilise a track in the project of 34 mins - that means my veg file will be approx 220388KB (i.e. 220MB) - which, I think, for a base project file, is a crazy size. Incorporating stabilise info into the veg is a relatively recent development & was not part of the original veg spec. Therefore, I think it would make far more sense to have them as sidecar files - especially in terms of reducing the chance of any veg file corruption happening on huge files.
Simes
Offline, Member since 6/11/2012