Peter Honig
Forum Replies Created
-
I (like many others) find Vegas 14 to be an overwhelming disappointment in both quality and price. You may want to consider the Vegas 13 upgrade for $179 instead, which is still available from B&H Photo.
Peter
-
I had a somewhat similar problem but in Adobe CS6. Red Giant support told me to update my graphics driver and the problem was solved. Perhaps this is your problem as well.
Peter
-
Boris, I thank you and your team for getting this issue analyzed, corrected, tested and released in just two weeks. Excellent job!
Peter
-
Hi Boris, I have Vegas Pro version 10e and absolutely DO see this problem. It is definitely not new and 100% repeatable. In fact, it is absolutely unavoidable and appears in both 32 and 64 bit version on both Vista and Windows 7.
If you wish to send me a pre-released version, I would be willing to test it for you. I would be very disappointed if this fix did not address the identical issue in version 10e, as Vegas Pro 11 is too unstable for me to make the upgrade at this time
Peter
-
Dear Boris,
I am very pleased to hear that your developers are working on this issue. Like Glass Onion, I too believe that this is a “show stopper” error. In fact, through all the years that I have been using Red with Vegas, I have never seen a bug as significant as this. As such, I would greatly appreciate if you could give this issue your personal attention by having your people raise the priority of this bug fix to the highest level.
I have always felt that Boris Red is one of the finest products on the market and it is an essential part of all my post-production work. I look forward to seeing this issue resolved where I can use Red in all my projects again.
Sincerely yours,
Peter Honig -
No, I’m not flipping on you, I am quite unhappy about this bug as well. I just wish to point out that you first posted about this on Friday Jan 6, then followed up with this thread on Tuesday Jan 10. I just don’t think it is very realistic to expect a fix in just two business days.
To expedite the correction of the bug I would suggest calmly writing an email or a post to Boris Yamnitsky (the president of the company) to request a rapid fix because this is affecting your income. If you wish, I will do the same. I believe in the old saying that you “catch more flies with honey than vinegar”.
Peter
-
Before you get your knickers in a twist, you should know that the Boris folks have always been very responsive when it comes to important bug fixes. If you rather throw in the towel and find some other product, that is certainly your choice. I prefer to wait.
Peter
-
I was just about to post on this topic as well. I have the identical problem with VegasPro 10e, and have boiled the issue down to the simplest example. Namely, send ANY (LFF or UFF) interlaced clip via Vegas to RED5 where the RED5 project contains nothing other than the media V1. By repeatedly activating/bypassing the RED FX within Vegas, one can easily see that the interlacing is incorrectly returned from RED. Specifically, it looks as if RED has used one field from one frame and the other field from a DIFFERENT frame (either next or previous). As such, RED is only usable for me when I have non-interlaced projects.
Note that resolution was set to “high” and “full” in Vegas per the user manual and this problem exists in both the 32 and 64 bit versions on both Win7 and Vista. It is 100% reproducible.
Peter
-
Thanks Peter. Your suggestion worked as described.
Peter
-
Hi Peter,
Thanks for your response. I am currently traveling and will try your suggestion this weekend.
Regards,
Peter