Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Report Redcine Bugs

Status
Not open for further replies.
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
 
Sad panda error!

Sad panda error!

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?)


553_1228256345.jpg


553_1228256371.jpg


Bruce Allen
www.boacinema.com
 
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.
 
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
 
Pawel Achtel said:
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.
Click to expand...

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
 
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.
 
Redcine 3.12 Crash

Redcine 3.12 Crash

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.
 
REDcine 3.15 (XP) Corrupted Image and Crash

REDcine 3.15 (XP) Corrupted Image and Crash

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.
 
RedCine Issues

RedCine Issues

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.
 
Hi Eugenia,

I had the same problem, because I also run two monitors. One of my LCDs is 20" and the other is 23", and the resolutions are also different. The moment I down re-zed the bigger screen to the same resolution as the 20" - 1680x1050, the redcine worked OK.

The alternative was to go into my Nvidia Properties and make the 23" the PRIMARY screen - the REDCINE would then open up there, and work OK, with the 20" screen now being a spare...

This worked in my case - hope it is somewhat helpful
cheers,
Lav
 
hey all,

id like to put my bug forward...
I am using REDCINE on PC, version 3.1.5.
I can get the R3D files opened in there, and I can export XML, convert it to XSL and eventually to ALE (for Avid) but I cannot output QUICKTIME Avid DNxHD file, no matter what I try.

Actually... any QuickTime file (any codec) that I try, the error is the same:

Player: Failed to write frame _____and then there would be frame 1, frame 2, frame 3, etc...

Underneath that line, it says:

Node: RedMag
At: ___date____time____

that is it...
Any ideas on what could be causing this? I tried to re-install the REDCINE few times, used all settings I can think off - different clips, in and out points, no in and out points, formats, folder output settings, etc etc.. but anything you can think of, please let me know

thanks!
Lav
 
Too many files loaded into Redcine seems to break the Open dialog - I pulled in a bunch of shots for a 10 minute short, then couldn't load the Redcine XML file I'd made with cineXML - the dialog wouldn't show anything when I clicked on volumes. This is with Redcine 3.18, OS X 10.5.6, 8 core 3.0GHz, ATI X1900, 5GB RAM.
 
Redcine can load maximum of 112 clips at a time.
 
112 shot limit?

112 shot limit?

and WTF is up with that limit!!!???? Seems so arbitrary. I'd rather have laggy performance than none...so that is why the open dialog barfs out? Crazy.

Fix, anyone?
 
I'm with you, Mike. I am so tired of RED Cine not working correctly or at least as good as it should.

I just completed a 2 minute edit in FCP. All I want to be able to do is to bring the frames I used (via XML) into RED Cine, color them, and export back out. Crimson immediately gave me an error and that was that. UGH! This does not seem to be overly difficult or asking too much!

Beside the clip quantity limitation you are having trouble with, we also found there to be a clip length issue on an earlier project, where crimson/RED Cine didn't work with long clips (over a 4 gig limit). Not sure if this issue has been resolved or not.

I really want RED's tools to "just work" the way they should. Again, the instance I asked for above (a simple conform/color process) isn't that crazy. Not after this much time...
 
MikeCurtis said:
and WTF is up with that limit!!!???? Seems so arbitrary. I'd rather have laggy performance than none...so that is why the open dialog barfs out? Crazy.

Fix, anyone?
Click to expand...

didnt you know it only costs 17500 USD with Scratchcine to have this.
this is exactly what redcine should be.--

i kicked out redcine a long time ago out of my workflow.
its only a viewing tool on set...sometimes
 
New to Redcine. Just playing with a few clips from Redrelay to learn a little about the workflow while awaiting Scarlet.

Toshiba laptop: 2MHz Intel Core2 Duo 8750, 4GB ram, 256MB DDR2 ATI Radeon 3470, 2 x 200GB 5400rpm drives. Vista 64bit home premium. Redcine 3.1.8

Program loads and runs fine. Plays 4k clips at 1/4res medium at about 18fps. Plays 2k clips real time at the same setting. All picture controls work correctly and instantly. All menus and functions work fine with no crashes or hangups of any kind except for output rendering.

I have tried loading Jarred's 2k dragstrip clip from redrelay and encoding to output at native size with no changes using every format and filter combination available except QT, I only have the QT player not the full version. All produce garbled frames, noise and banding, color shift, no usable image. everything else about the program works just fine except the encoding.

Any clues?
 
MikeCurtis said:
and WTF is up with that limit!!!???? Seems so arbitrary. I'd rather have laggy performance than none...so that is why the open dialog barfs out? Crazy.

Fix, anyone?
Click to expand...

It's a bug. Not a hard limit. Has been reported for AGES (years?).

I don't think anyone at RED has actually tried to use REDCINE on a real-world project over a minute long. If so they would know that bugs like this one really are showstoppers and would have fixed them by now.

I'm not sure how to let RED know that this is important. I've tried polite posts, rude posts, polite emails, rude emails... no results except getting the entire RED software team angry at me. They think it's just me whining.

I don't care any more - I am shooting on Canon 5D Mk2, HV20, EX1, HVX200 and having lots of fun. Until the workflow gets fixed I probably won't bother with Red unless I have a project with sufficient budget for me to either buy a new Mac or can afford to have everything processed on a Scratch.

Anyway, over to you guys. Why don't you write something in ProVideoCoalition, Mike?

Anyway, I'm sure that RED will fix it by the time Scarlet is released - imagine what's going to happen when 1000s of consumers hit this issue (and all the others)?

Bruce Allen
www.boacinema.com
 
Status
Not open for further replies.
Back
Top