Jump to content

St Bosse

Members
  • Posts

    97
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

St Bosse's Achievements

Expert

Expert (5/7)

0

Reputation

  1. Thanks borate, Never thought of looking there. Not wanting to labour the point, how does one then get the 64-bit version if preferred? Check for update only says "new update available", (without choice?) St B
  2. . . .mmm . . . How does one know whether it is the 32 or 64-bit version? I cannot find a place where one can see this. Then, when one check for updates on the menu of VP, why would it then say yes to the wrong n-bit version? Shouldn't it stay in-line with the bit version already installed? St B
  3. Why is the latest VP update (v10.63) file size so much smaller than the previous one? (about 30%). I am hesitant to update, reading about some of the complaints. St B
  4. hi Borate, Thanks for the offer. I don't want to waste your time. As you have said, you cannot replicate the situation. I can replicate a specific instance easily by using 29.97 (NTSC) fps. Then again on other clips, 29 will work just fine, but it is unpredictable. So, to be on the safe side, I'll just use 30fps all the time and all is fine. Thank you for your interest. St B
  5. After all my projects were finalized and exported (14 of them), I started stringing the exported files together in a new project to form the final production. Then, did the final export using the (technically / politically? correct(lol)) frame rate of 29.97 (NTSC). Mistake! Frozen frames are back! Was surprised at first when somebody contacted me and pointed out the issue. On closer investigation I tried full 30fps and the frozen frames are gone. I can replicate the issue every time when using the 29.97 (NTSC) fps. So my conclusion is that maybe one should stay away from 29.97 (NTSC) or its double of 59.94fps. Is there any technical reason why one should use 29.97 (NTSC) fps? St B
  6. Hi Nat, Yes we are on the same page here. Sure, the work-around is very clumsy but it seems for now , it could be the only way until something better arrives. VP in totality does have quite a few shortcomings regarding its operation. I for example did a few pen and paper calculations during editing due to a lack of indicators, such as a "selection length" as in WavePad. See also my post on text line feed speed. Any case, thanks for your detailed response. St B
  7. . . . or keep blank inserts with one's text notes on one track and then "Hide track on output"? and group them to ensure they stay attached to the specific issue. St B
  8. While working on my assignment with about 300+ takes (clips) ending up with about 25 projects, all to eventually end up as one project, I was wondering if there is any way of adding "editor's notes" to a timeline. Working on this assignment, going back and forth, I sometimes stop at a timeline position, being revisited for some reason, and then for the life of me, cannot figure out why this weird step is on the timeline, but working perfectly fine. Or working on a timeline, expanding, etc. removing a weird piece, totally illogical, only to discover when I test the project, why that weird thing was doing there. Question: Can one add editor's notes to a timeline? St B
  9. I have seen quite a few discussions (with frustrations) of people that hates the text scroll stuttering. So do I. I have gone on the internet and it is interestingly enough, a frustration all round regardless of which editing software is used. During my search to get solutions to this problem, I can across posts of people that know (I think and hope) that states the following or similar amongst two or three lessor important suggestions:- “The single best thing you can do for your end credits is reduce scroll speed. Our recommended sweet spot is 3 pixels per frame (in 2k or HD) or 6 pixels per frame (in 4k and UHD).” Question: Has anyone ever did this calculation? How does one apply this in VP? How do I apply this statement or translate this to scroll speed (ie. 50 lines per minute or clip length in sec = lines x 2.75 sec/line - [my formula, but still has the odd hiccup])? How to include font size in the formula etc. Anyone ever tried this calculation or got to a formula? Please let me know. Judging from all the posts, I am sure lots of editors would like to hear a about this. St B
  10. Thanks Nat, I'm sort of done, for the "n" th time. Now to experimenting to get the optimum compression and other specs to not loose picture quality when uploading to YouTube and/or Vimeo. I've checked through all the sequences which will be exported to become cuts in the final sequence, and all the cropping and fading is moving to black. (check) Thanks for you and Borate's assistance. St B
  11. Hi Nat, Thanks for the response. I think I now fully understand the fading and cropping transparency characteristics. I used the cropping and fading to get some special effects and also to hide actor dance errors in the footage (all I had to work with). So placing the black blank on track 2, solved the problem and track 3 showed exactly what I wanted without track 1 now starting to shine thru during track 3's cropping or fading moves, confusing the flow. (ie. from a viewers point of view, they may think, oops, the editor forgot something). 🤦‍♂️ St B
  12. Thanks Borate, So I assume the same goes for fading on the upper levels, i.e. fading also goes transparent thus revealing the track underneath at that point in time. If not, what then? Not sure I understand this. St B
  13. Upload on its way. Sorry, I see it's a bit of a stiff size. Track 2 at +/- 0:59.204 had a black blank. I see this is a bit different because it is not cropping involved but fading. As the fading de/increase lower levels' shine thru increases. Track 3 at +/- 1:52.758 has cropping where you will see a shine thru across the top. Thanks St B
  14. Lower levels video tracks shine through. First, my take on how the track setup works:- Track 1 is the main video track/clip Track 2 (maybe shorter clips) overrides track 1 (ie. Track 1 won’t be visible for track 2’s duration) Track 3 (still shorter clip pieces, etc), will again override track 2 and 1. (ie. Track 1&2 won’t be visible) . . . and so on. The highest track # has “video show” priority. This works all perfectly until the other day when I started to do some “cropping” on the top levels. I noticed that that in the “black area” of the cropping, the lower level tracks will shine through and become visible instead of the black cropped area staying solid black. The only way I could solve this problem was to add another track with black “blank” inserts below the cropped track to block the shine through effect. Now this works, but it is a clumsy work around. What is the correct way to solve this problem? Any suggestions? St B
×
×
  • Create New...