Build 20 (Beta) bug tracker

[Stuart English]

Post your questions and comments about Build 20 (BETA) bugs here

 

[Dustin Cross]

headphone out and phantom power still not staying on through power cycle.

Dusty

 

[Brice Ansel]

Is it me, or the redspace view in the red LCD isn't accurate anymore?

 

[Lauri Kettunen]

These are not bugs but requests for new but small features:

i) When upgraded to build 20 the camera did not first record at all. After a while figured out the problem had to do with the Birger mount and GPIO settings. So, it would be convinient if the GPIO settings were stored to the profile-files.

ii) Every upgrade causes the media counter reset, and thus, when formatting drives or cards the index starts from one. It is possible to set the counter, but still, if one wants a continuos indexing used with the previous build, one has set the indexing manually every time the media is formatted (or format say a CF card multiple times). It would be useful if after upgrading and setting the counter the index increased thereafter by one from the value employed in the previous format.

Otherwise, build 20 looks like a great improvemtn in managing with noise in low light conditions --thanks.

 

[Lauri Kettunen]

This seems to be a bug: If I change the project from 4K 16:9 RC36 to 3K 16:9 RC36 and record and then try to go back to 4K, the image in the LCD goes black as if a lens cap was there. Second, earlier it was possible to boot having the Birger mount connected to the Aux port, but this is not possible anymore. If boot having the cable on the port, the camera fails to record and prompts and internal error message.

 

[Stuart English]

Birger and boot error

Birger and boot error

earlier it was possible to boot having the Birger mount connected to the Aux port, but this is not possible anymore. If boot having the cable on the port, the camera fails to record and prompts and internal error message.

Which of the two Aux ports are you plugged into - upper (A) or lower (B) ?

Note that we changed the default for GPI B from TIMELAPSE to RECORD.

Can you try changing that back to see if there is a difference?

 

[Erik Widding]

Birger boot issue

Birger boot issue

We think these issues are related to the lens data interface. If people want to help with this, I need to know which combinations of the following items work and don't work:

• RED: 18.3.6.4 -or- 20beta
• Birger: 19x -or- 19z
• Units: English -or- Metric

RED and Birger both changed i/data interface in both of these releases. I have a hunch that unit selection is playing into the problem, because not everybody is having the issue. We stripped some of the i/data protocol in 19y/19z to get some ROM space back. We eliminated commands that the previous versions of camera software did not issue. I do not have access to a test camera for another couple of days.

 

[Lauri Kettunen]

Which of the two Aux ports are you plugged into - upper (A) or lower (B) ?

Note that we changed the default for GPI B from TIMELAPSE to RECORD.

Can you try changing that back to see if there is a difference?

Tried and it does not make any difference whether the cable is in port A and B. In fact, Birger users set both ports the same way; Record and Active Low. So, guess the port should not even matter with those settings

Another possible bug: Although the Birger mount is NOT plugged to Aux A or B
-the (CMOS) sensor freezes (and the image is black) after setting any of the sound channels on. Thereafter, for instance, running black shading will fail.

Further observations:

-WITHOUT the Birger mount cable plugged into a aux port have been able to change the resolution back and forth between 4K and 2K, but also have seen cases the sensor freezes.

-WITH the Birger mount plugged to aux port A or B can change say from 4K to 2K but have not been able to change back to 4K without making the sensor to freeze.

Finally, interestingly enough,

- tried to back to Build 18 version 3.6.4 but it didn't help. Changing resolution was now unstabe also with buil 18 and it made the sensor to freeze. Did not have this problem before although have changed resolution in fly a lot before.

 

[Lauri Kettunen]

• RED: 18.3.6.4 -or- 20beta
• Birger: 19x -or- 19z
• Units: English -or- Metric

Erik,

i) Red 18.3.6.4 and Birger 19x, units metric, worked out flawessly

ii) Rolling back to Red 18.3.6.4 from Red 20.0.0.0 and Birger 19y, units metric, is unstable with or without the cable in aux port A or B.

iii) Red 20.0.0 and Birger 19y, units metric, is unstable with or without the cable in aux port A or B.

Without knowing the details, one of the symptoms makes me to hesitate whether it is a Birger issue: Power cycling the camera on after upgrading to buil 20 without have Birger cable in an aux port, and changing the audio channel on from the sound menu makes the CMOS sensor to freeze.

 

[Anson Fogel]

Same Birger Experience/Combination

Same Birger Experience/Combination

Erik -

My experience mirrors that of the prior poster above. I initially thought my GPIO settings were causing the problem, and then B20 - but rolling back to B18 current, and altering the GPIO settings has not resolved it.

Same series of combinations as above, but in addition, I still get frequent record internal errors, even without the mount cable attached.

 

[Lauri Kettunen]

It seems that combination

Red 20.0.0 and Briger lens library 19x and metric units works out.

At least all troubles I had seem to have disappeared once rolled back to library 19x. Tested and changing resolution or toggling audio channels on and off worked out as usual.

 

[Martin Weiss]

Not a build 20 bug per se, more something that has been bugging me:

I find the handling of audio in the GUI a bit discombobulating. One has to enable the phantom power under a different menu than the one used to set the level. Would be great if all could be accessed under one menu, which should probably under "system". Also, maybe Tracks, Type and Phantom could all be placed as one menu:

I.e. System>Audio:
>Enable Tracks (Off, On-line, On-Mic, On-48v; all selectable with the wheel)
>Levels
>Headphones

(Actually, would be great if some 3rd party could make a little USB gadget, that would let us control audio settings; 4 knobs would do.).

(And as noted by others: please re-enable that the phantom power remains during power cycles. Diminished already 2 otherwise fantastic shots.)

And it would be great to have a quicker, less intrusive option for formatting new CF-cards. If they are empty (i.e. the DIT transferred them, double checked everything, and lastly deleted all files), they should auto-format, without disturbing the display. Alternatively, please at least remove the full-screen note that the magazine is formatted. Think of those of us who work in cold climate and would prefer to keep the gloves on as often as possible
I would also still like an option to delete - at least - the last take. There should of course be a warning just as it is now when trying to format a magazine that contains R3D files.

 

[Stuart English]

4k to 3K to 4K

4k to 3K to 4K

This seems to be a bug: If I change the project from 4K 16:9 RC36 to 3K 16:9 RC36 and record and then try to go back to 4K, the image in the LCD goes black as if a lens cap was there.

That works fine for me when I test it, is it still happening for you ?

 

[Joel Kaye]

I find the handling of audio in the GUI a bit discombobulating. One has to enable the phantom power under a different menu than the one used to set the level. Would be great if all could be accessed under one menu, which should probably under "system". Also, maybe Tracks, Type and Phantom could all be placed as one menu:

Yep.

I hope the entire interface gets redone for Scarlet/Epic. Or stick a bunch of buttons on the camera and let us program them all. Things like that will contribute to RED's edge as other companies offer 35mm lens options. They may lag in usability.

 

[Lauri Kettunen]

That works fine for me when I test it, is it still happening for you ?

Once went back to Birger library 19x everything started to work ok. Changing the resolution or setting audio channels on or off create no problem any longer. So, it was the i-data that created the problems.

 

[Martin Weiss]

(Actually, would be great if some 3rd party could make a little USB gadget, that would let us control audio settings; 4 knobs would do.)

Or maybe add a function that when not under playback, the four top buttons would be assigned to the four channels, and the joystick could be used to set the sound level for those channels?

 

[Stuart English]

I data on Birger

I data on Birger

So, it was the i-data that created the problems.

I guess I should really ask Erik this question, but what I data version is the 19 x or 19 y emulating?

 

[Rainer Fritz]

That works fine for me when I test it, is it still happening for you ?

this black display bug also happens sometimes when you change from magnify back to normal, specially in lower resolutions. happened four times to me at 2k 100fps. but pushing again magnify changed it to normal. that was at build 17.

 

[Casey Green]

RED Alert! v20.0.1

RED Alert! v20.0.1

I already sent this in to Graeme, but I thought I'd post it here as well to see if others have noticed this:

If I load a clip (in this case an older clip from build 15), and choose Defaults, and load the same clip again, no change in the color look.


However, if I am in Defaults mode, load the clip, then switch to Metadata, THEN go and reload the same clip, a color tone similar to the old looking color science appears. If I then click on MetaData, Defaults, or Grade, this look changes and there is no way to get back to the look that the clip loaded in with... (perhaps somehow it is skipping the new code on load in if you are are already in Metadata mode?)

It almost seems like if you are in Metadata mode when you load a new clip, it is bringing in the White Balance from that particular build, but if you select Meta data, it then over-writes that with the new color science White Balance.

Actually, kind of useful for comparing old and new color science, if that is what is happening, but not sure.

Am I just not understanding something, or is this a bug?

 

[Deanan]

I already sent this in to Graeme, but I thought I'd post it here as well to see if others have noticed this:

If I load a clip (in this case an older clip from build 15), and choose Defaults, and load the same clip again, no change in the color look.


However, if I am in Defaults mode, load the clip, then switch to Metadata, THEN go and reload the same clip, a color tone similar to the old looking color science appears. If I then click on MetaData, Defaults, or Grade, this look changes and there is no way to get back to the look that the clip loaded in with... (perhaps somehow it is skipping the new code on load in if you are are already in Metadata mode?)

It almost seems like if you are in Metadata mode when you load a new clip, it is bringing in the White Balance from that particular build, but if you select Meta data, it then over-writes that with the new color science White Balance.

Actually, kind of useful for comparing old and new color science, if that is what is happening, but not sure.

Am I just not understanding something, or is this a bug?

It's likely that the old RSX file might be causing some confusion. Can you try deleting the old rsx?