Bob Leathers
Forum Replies Created
-
Sweeeeeeeet, this is exactly what I was aiming for. Thanks man!
On to the next practice comp.
-Bob
Salt: Contains salt.
-
Hah hah, yeah, it has been quite the headache so far. Every time I troubleshoot I keep thinking, “oh, I’ll just do this and this and… oh wait, different workflow.”
Thanks for the link. However, I don’t want to create new ripple effects through the logo but use the pre-existing ones in the video so the logo matches perfectly with the ripples in the water.
I want to pretty much recreate this.
https://vimeo.com/37401039#=at75EDIT: Bleh, I thought that link would direct to the specific part on the timeline. 1:14
-Bob
Salt: Contains salt.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Yeah, I bumped up both settings on the VBR. Even with the highest bitrate setting that DVD Studio Pro would allow me to burn there were still quality issues on that specific scene. The defaults were set to 6.2 minimum, and I think around 7ish maximum. I bumped it up to 7 minimum, 8 maximum and still had issues. It wasn’t until I set it to CBR when the artifacts and shifting stopped. It’s currently at 7.5mbps. Even a lower CBR setting would’ve worked, but space wasn’t much of an issue so I just bumped it as high as I could without receiving “too high bitrate” errors in DVD Studio Pro.
The problem is fixed. I’m just curious what caused the degrade in quality in the first place just in case I come across it again and require VBR for space efficiency.
Also, previously, before initially posting my problem, I did multiple render tests after changing the frame controls. I’m not completely familiar and still am learning to effectively export video, so it was more-so “playing around” with the frame controls. But nothing I did was successful. I also tried putting some compression markers on the problem spots. Setting the footage to CBR seemed to be the only fix, at least so far.
-
The problem just seemed to be in the variable bit rate. Switching to CBR fixed the issue. I don’t understand why, though. I mean, VBR has its cap, so why would certain sections drop so low that quality becomes a major issue? I even bumped up the low-end VBR settings and still had the same quality degradation.
-
SUCCESS!! I had to go to select the clip in the sequence, go to Modify -> Remove Subclip Limits. This removed the artificial start and end points of the subclip and reset it to the main clip. So, now when the information is sent to Shake via “Send to -> Shake” the in and out points calculations are in conjunction with the main clip and not the referenced subclip.
Thanks for the help, Lightning Ad.
-Bob
Salt: Contains salt.
-
Nope, didn’t seem to work. The same issue occurred in Shake.
-Bob
Salt: Contains salt.
-
I consulted a friend of mine about this issue and he’s come up with one solution that I can’t say I’m all too happy about. One solution is this, I could export the sublip then drop the file into my browser, using in and out points on the new main clip. I haven’t yet tried this out, the subclip is currently rendering out. I know this will work, though.
However, one issue I don’t like about this, I’ll have to render out every subclip I’m going to use “Send To -> Shake” on, reapply the same in and out points from the subclip to the new main clip, drop the new cut into the timeline, then finally use Send To -> Shake. I personally would not like to add more to my workflow, especially adding more rendering time, unless there isn’t any other way.
For some reason I’m always thinking there’s a certain setting I’m overlooking that’ll fix the way FCP is sending correct in and out point information to Shake that’s in conjunction with the main clip and not the referenced subclip.
-Bob
Salt: Contains salt.