Forum Replies Created

Page 15 of 17
  • Kevin Snyder

    March 8, 2006 at 2:41 am in reply to: Spare yourself the misery of 2.0. IT’S A MESS!

    Number lock is on…to be more clear, I just make sure that I’m at the end of the clip then press -100 (=1:00) and hit enter to get to my location…yea, I like the fact that if you have the timeline selected you can just enter your number and not actually select the timecode display.

  • Kevin Snyder

    March 7, 2006 at 11:31 pm in reply to: Spare yourself the misery of 2.0. IT’S A MESS!

    It doesn’t do it all the time, but frequent enough to be a problem. I use it often when I am setting keyframes. If I want a keyframe 1 second from the end of a clip I just hit page down then -1:00 and bingo I’m there.

    I know that not everyone uses that feature, but I use it a lot and it is hard to make myself not use the feature in my workflow. I have had other people post that have run into the same problem with the +/- time feature.

    If you have a master clip that is 30 minutes long, make a 5 minute subclip from it and try to play it on the timeline or source window. I think that you will still see a lag in the time it takes to play the clip.

    Kevin Snyder

  • Kevin Snyder

    March 7, 2006 at 10:21 pm in reply to: Spare yourself the misery of 2.0. IT’S A MESS!

    Paul,

    I love using Adobe software, so I’m not attacking the software or the people that use it (I still plan to use it!), however, there comes a time when a person has to admit that there are problems that exist. Problems that I think should have been caught in beta testing. A lot of times when people are frustrated they need to rant a little, but unfortunaletly the truth is over loooked by others due to the tone of a post. So, I will clarify some of my points in the most productive manor possible.

    To start with, subclips are a mess. Try these steps:

    1) Import a “large” video file (mine was about 1 hour)
    2) Double click the file in the project window so it opens in the source window.
    3) Scrub the CTI in the source window to the middle of the clip, set an inpoint
    4) Move the CTI approximately 5 minutes forward and set your outpoint.
    5) Drag the clip from the source window to the project window.
    6) Rename your subclip something.
    7) Double click the subclip in the project window so it is opened in the source window and try to play it. (Tried on a couple of machines and it does not play, the hard drive just reads. The clip will eventually play, but after 10-15 seconds)
    Drag from the source window to the timeline and try to play the timeline…..Same Thing. If you had a timeline full of subclips, the project would be useless.

    Long clips….
    The problem with long clips in the source window is not major, just noticed that it was slower than 1.5, I ussually feel that things should improve with a new verson…Yes, I am using DV and the project setting are correct.

    Clean install of what?…Windows XP, Service Pack 2, All drivers and software.

    RPF – My workflow involves using cinema 4d, so RPF files are important to me because the contain z-depth information. Therefore, other file formats would work, but there is no z-depth information in the file itself. I don’t know why the alpha channel was correct in AE and incorrect in PPRO if it is just frame serving…The problem with DL was not a deal breaker, just one more frustration added to the pile. I was willing to work around the problem, but I just wanted to post my findings in case someone else had trouble. This is the first round of DL, I didn’t think that it would be perfect.

    The DV AVI file that I created did have audio embeded, but should the program not work if that is the case?

    I see that there was no mention of PPRO crashing when using the + and – with a number value in the timeline to move the CTI forward or backwards. All the tracks become locked (with the lock icon) and then I get the message that PPRO has crashed. It must have happened to you too?

    “Sounds like you try something the way you think it should work, dont get what you want and then give up. Have you read the book? Are you sure you know what your doing? A lot of people think they are and so blame the software in the first instance.”
    Software is like a little brother sometimes. There are things about it that bother you, but when someone bad mouths it people always jump to its defense. Yes, I have read the book and you can just dismiss me as another one of those people that do not know what I am doing or use some of the features that I mentioned and see for yourself. Just because your workflow does not include some of the features I have mentioned, does not mean that everything is okay. If it is a feature, it should work.

  • Kevin Snyder

    March 7, 2006 at 6:35 pm in reply to: Spare yourself the misery of 2.0. IT’S A MESS!

    Yep.. I have been a little disapointed with 2.0 as well. Good thing for the money back policy. Here is a message from a previous post.

    I just have to star off by saying that I love using Adobe’s software for video productiom; however, this release of the Production Studio has been a large disapointment. I am just finishing up my first and last job with the Production Studio due to the fact that I have not had this much trouble since I used Premiere 6.0.

    Subclips do not work with large source files (confirmed with everyone that has tried). So I had to go back and recreate all my subclips with clip instances. Kinda a pain, but I was willing to work around subclips for the time being.

    Working in the source window is just plain slower in PPRO 2.0. If you bring in a 80 minute clip in the source window there is serios lag in scrubbing the CTI and setting In and Out Points.

    PPPRO 1.5 has crashed on me maybe 5 times since I bought it (when it first came out). PPRO 2.0 has crashed 5 times just on this project alone. (Yes, it is a clean install of the OS and Studio) PPRO 2.0 crashes the most when I use the + and – with a number value in the timeline to move the CTI forward or backwards. All the tracks become locked (with the lock icon) and then I get the message that PPRO has crashed.

    Tried to use the Dynamic Link. Cool idea, but still needs some work. I imported a RPF image sequence with an alpha channel into AE and used DL to bring the clip into PPRO and the clip was not correct. The alpha channel was correct on the sides of the screen, but drastically wrong in the middle. Okay, maybe I can’t use DL with RPF files…I still remained hopefull.

    The last straw…I finally exported my final video (2 hours). In order to get the data rate correct, I exported and avi file so Encore could pick the correct rate so it would fit on the DVD. After Encore encoded the file, Encore displays a message that it is importing the transcoded file. However, it never finishes. Encore just keeps reading the file over and over again and is never successful.

    Sad to say, but I am very dissapointed with the studio. I had such high hopes for it. I hope that others are not having the same luck that I had. I returned my copy of the studio in hopes that the next version will be better for me. Back to Video Collection 2.5.

    I looked at other options for editing because this experience reminds me of Premiere 6.0, but I am so used to Adobe’s workflow that there is no other choice for me.

  • Kevin Snyder

    February 16, 2006 at 8:08 pm in reply to: Premier Pro 2.0 PRE-Render for Multi-cam

    I think the bottle neck is in the drive speed, not the cpu. All the audio for the four clips have to be rendered…

  • Kevin Snyder

    February 12, 2006 at 6:02 pm in reply to: Back to 1.5

    I’m going back to 1.5 as well. Try and make a lot of subclips from a large master clip and put them on the timeline. PPRO 2.0 is terrible. If you don’t believe me, try this:

    1) Import a “large” video file (mine was about 1 hour)
    2) Double click the file in the project window so it opens in the source window.
    3) Scrub the CTI in the source window to the middle of the clip, set an inpoint
    4) Move the CTI approximately 5 minutes forward and set your outpoint.
    5) Drag the clip from the source window to the project window.
    6) Rename your subclip something.
    7) Double click the subclip in the project window so it is opened in the source window and try to play it. (Tried on a couple of machines and it does not play, the hard drive just reads.)
    Drag from the source window to the timeline and try to play the timeline…..Same Thing.

  • Kevin Snyder

    January 26, 2006 at 10:43 pm in reply to: PP2 – subtimeline audio distortion

    Did you render the audio in the “subtimeline”?

  • Once I wrapped my head around the idea it only took me about 45 minutes. After reading this thread, it took me a day and a half to come up with a productive way to tackle the task.

    KMS

  • Here is my attempt at folding paper in AE.

    https://home.sou.edu/~snyderk/ae/foldingpaper.mov

  • I’m not a Maya user (C4D), but I know that AE will import both RLA and RPF files. I have used z depth information in RPF a lot in AE. If you export your files with an alpha channel, AE does not always reconize the alpha channel and everything looks bad on the aliasing. If you did export your files with a alpha channel, go into the clip properties and make sure that the alpha channel is not set to none. Also, with z depth information, sometimes it helps to export your files at twice the resolution then scale it down to 50% in AE. It helps to clean up the aliasing a bit.

Page 15 of 17

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy