Report Redcine Bugs

[Peter Savage]

sadly I was a little premature in my reply. After adding 6 shots to Redcine, even after restart with reset I now get the same frozen frame for every clip I try to output. UNLESS the clip I want to output is before the frozen frame in the Redcine timeline. Re-organising the clips in the time line makes no difference. In the current example the frozen frame is numbered 1450 but in previous attempts (different projects) the same thing happens on a different timeline frame.
Oh well back to the drawing board

p

[Bruce Allen]

Since nobody from RED seems to care about the errors, how about this?

I suggest we come up with creative names and use different colors and fonts for them to make it more fun for them to read.

Today I bring you the...
:ph34r: <<SAD PANDA ERROR!>>:ph34r:

I hit this fun little error today while trying to work around the dreaded NAUGHTY TURTLE ERROR (where REDCINE stops short when you give it too many clips to import).

Here are the steps:

1. Clean prefs, reinstall REDCINE 3.1.2
2. New Project
3. Library -> Depth -> 10
4. Import All Shots... point to //volumes/BACK UP/footage/red_drive_1
5. when that's done... Import All Shots from //volumes/BACK UP/footage/red_drive_2
5. when THAT's done... Import All Shots from //volumes/BACK UP/footage/red_drive_3.
6. okay buddy, try to import NOW.
7. haha, we're screwed (can't see any folders) - screenshot #1
8. wow, can't even save (same problem) -screenshot #2

EDIT: 9. Now when I try to reload REDCINE, it crashes immediately after the big RED logo splash screen goes away

Attached is .log file, plus the latest Construct.reg, Project.reg and ProjectMedia.reg files (can anyone from RED tell me what the last two do? I assume Construct.reg is the autosave or something?)






Bruce Allen
www.boacinema.com

[Pawel Achtel]

Bruce,

I think the Red Team does care about the bugs, but this does not mean they have time or resources to respond to the reports on Reduser. The reports are valuable as long they contain technical information and no less no more helping them to siff through irrelevant text such as people whinging.

[Bruce Allen]

While I'm at it, can I officially submit two more names:

1. GRUMPY BEAR DEFECT - the way REDCINE fails to export color info with its XML files (thereby forcing you to start from scratch with your color each time you try to online)

2. FEROCIOUS POSSUM FUCKUP - the fact that (unlike any editing program made after 1985) there is no way to let REDCINE know that the R3D files it is looking for have moved to a different drive. This also makes it impossible to go from Mac to PC.

Bruce Allen
www.boacinema.com

[Bruce Allen]

Bruce,

I think the Red Team does care about the bugs, but this does not mean they have time to respond to the reports on Reduser. The reports are valuable as long they contain technical information and no less no more helping them to siff through irrelevant text such as people whinging.

If they cared they would have hired a bigger QC team and more coders.

I understand error reports but it's a two-way thing. On other Beta programs I'm used to the developers getting back to me promptly. I'm used to seeing errors that get reported find their way onto an official public error list, and slowly get checked off. That's how software development works.

Problem is, it's not happening with REDCINE. Why? I guess the team is too small and the person making the hiring/budget decisions (Jim?) doesn't understand this.

Big problems, such as the relinking problem, have been an identified issue since March 2008.

The "importing many clips at once error" has been around a long time. But you don't see it on the list of known issues in the REDCINE changelog, do you? I can't believe that they haven't nailed down that down. Very irresponsible.

Someone at RED who makes hiring decisions does not understand the magnitude of the problem. They need to hire more people, that's the only answer.

So drastic measures are needed. Submitting normal bug reports right now has failed. After over a year, REDCINE is still not production-ready by any means.

Bruce Allen
www.boacinema.com

[Eugenia Loli-Queru]

Hi all, I am not sure if the following bug is already posted or not.

So, I downloaded the latest REDCine the other night to test it for the first time. It installed fine, doubled clicked it, but its widgets show up only on the higher half of the screen, not in the whole screen. So for example, the upper half of my screen shows the lower part of the REDCine window. The lower part of the screen is just grey with nothing in it. While in this state, NONE of the buttons are clickable!

I was able to get around the bug when my suspicion as to what's wrong proved to be correct: REDCine doesn't like setups with *rotated* secondary monitors, EVEN if itself is not trying to load on the rotated monitor. When I changed the secondary rotated monitor to be the "primary" monitor, then REDCine did load correctly, and the buttons were responding.

Here's my setup that created the problem:
Primary monitor: 1280x1024 (REDCine was loading with the bug here)
Secondary monitor: 1200x1600, rotated.

Here's the setup that did fix the problem, but this was not the monitor I wanted REDCine to load on:
Primary monitor: 1200x1600, rotated (REDCine loaded here successfully)
Secondary monitor: 1280x1024

Apparently, REDCine *assumes* that both monitors are running the same resolution, and if not, it requires the monitor with the highest resolution to be the primary one, otherwise it just doesn't work properly. I am interested in seeing this bug fixed, I am not interested in workarounds. I have my monitors setup this way because that's how I want them.

Please let me know if you need more info. I run XP 32bit, nvidia card, all updates installed.

[Benjamin Broad]

Hi,
Redcine 3.12 (Mac) is crashing when working with Anamorphic footage shot 30 Nov 2008. Footage is 2816 x 2304.

Attached are:
Problem Report for Apple
Redcine.log

Redcine 3.15 (PC) opens the footage, however the pictures are snow/black

Benjamin Broad
Frame, Set & Match
Australia.

[Benjamin Broad]

Hi,
REDcine 3.15 (XP) is displaying a corrupted image - Footage is 2816 x 2304.
In addition, REDcine crashes on new/exit. Crash log attached.

Benjamin Broad
Frame, Set & Match
Australia.

[Dick Maney]

In attempting to resize footage, the resulting Quicktime out of RedCine flashes rapidly between the resized picture and the original full frame, two to four frames of each in random and rapid succession. Also, continue to have freeze frames after a minute or so (it varies) into a longer clip of several minutes in length. Shorter clips of 20 to 30-seconds usually work. Have tried RedCine reset and everything else but have just about given up on RedCine.

Fortunately, RedAlert and RedRushes work perfectly--always have.

[Josué Ignacio Saldaña]

Anyone knows how to fix?
http://reduser.net/forum/showthread.php?t=19123