Welcome to our community

Be a part of something great, join today!

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.
One of the export bugs still remains in the newest beta release 1.0.90:

When I try to export to QuickTime from a clip which is not the first one (by setting IN and OUT) I still get a freeze frame movie of a single frame in the first clip. There's no such problems with other output formats.

Dual Quad Core Mac Pro 3.2GHz
MacOS 10.5.1
QuickTime 7.3
8 GB RAM
ATI Radeon HD 2600
 
Also to echo Thom's findings. Copy and paste of color information also copies scaling settings, which I think it shouldn't. Here's why. I have a Redcine project of 4k and 2k scaled down so that it is letterboxed SD for export to DV50. I've applied a color correction, and for quick and ease, I've copied and pasted the color settings all all my clips, but if it also copies the scaling from the clip. This is problematic especially when copying color settings between 2k and 4k and vice versa.
 
With Build 90 I still have the QT frozen frame effect after 10 sec on an exported 45s clip. Very frustating... At this point the only working solution is to export a DPX sequence and encode it to DNxHD in After Effects...

When will there be a stable and reliable solution on the PC side ?

Thanks !

XP
QT 7.3
NVidia
Etc...
 
if i use the "load all" function, and then open a redcine xml, some shots in the viewer turn blue, but are visible in the timeline, some are completly black (viewer+timeline)

4k@2:1 mixed with 2k@2:1
 
Load All breaks file browser

Load All breaks file browser

Once I do a "load all" with depth 2, I can no longer use the file browser. Trying to open or save any other files I'm only presented with top-level choices and clicking on them does not give me further choices. This persists until I delete /Library/Redcine

Mac Pro
Leopard 10.2 fully upgraded
Redcine Build 90
QT 7.4.1
nVidia 8800GT
 
Chase Gordon said:
Once I do a "load all" with depth 2, I can no longer use the file browser. Trying to open or save any other files I'm only presented with top-level choices and clicking on them does not give me further choices. This persists until I delete /Library/Redcine

Mac Pro
Leopard 10.2 fully upgraded
Redcine Build 90
QT 7.4.1
nVidia 8800GT
Click to expand...

Same problem here. It's very frustrating, and makes conforming your edit in Redcine more of a pain than anything else. Not sure what it is associated with because I "load all" with 160+ clips (but less than 200) and they are all from the same Reel. As soon as I load clips from both reels (approx. 245 clips) the file navigator becomes unavailable as already described.

Mac 8 core OSx.4.11.
 
Latest Build - Macbook pro, Luki said I could reframe a shot with click and drag while holding down the M key (maybe even zoom with the scroll wheel)

Tried every combination of hit drag, hold drag, etc. but it doesn't seem to work.
 
MBP Santa Rosa 2.2GHz, 10.5.2, RedCine Build 90

Switching to 4K medium or high locks RedCine (command-Q does work for exiting). Next time I launch RedCine, the interface is garbled in various grey blotchy squares. Command-Q works for exiting, but system is in some sort of lock up where clicking etc. freezes for 10 seconds, every 5 or 10 seconds. Have to reboot, trash /Library/RedCine and start over.
 
Freeze Frame effect also here.. not the first frame anymore but after 21 seconds. and it would allways choose the same frame to freeze.

it'd be very convenient to get a compressed format like ProRes out of REDCINE
to save space. 45minutes of DPX is blowing up my momentarly available space by a 10 fold...

thanks for solving this soon.

martin
 
Freeze frame export again (first frame). Maybe because of my updating the OS to 10.5.2 (including graphics update). Cannot export to any QuickTime format any more. :angry03:

Funny thing is that during export all the frames are displayed correctly on screen.

Please smash this bug already!

Dual Quad Core Mac Pro 3.2 GHz
MacOS 10.5.2 with graphics update
QuickTime 7.3
8 GB RAM
ATI Radeon HD 2600
 
Just playing loaded footage at 1/4th resolution

Just playing loaded footage at 1/4th resolution

OS Version: 10.4.11 (Build 8S2167)

Command: RedCine

Version: ??? (1.22)

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000004

Thread 0:
0 libSystem.B.dylib 0x9002490f swtch_pri + 7
1 AssimCore.dylib 0x0002c125 mp_yield() + 11
2 AssimCore.dylib 0x00024385 io_complete64(int, int*, bool) + 119
3 AssimCore.dylib 0x0002467a io_read64(int, void*, long long, unsigned long) + 78
4 REDCODE.node 0x60b3bd4b REDCORE::File::ReadFromFile(REDCORE::Buffer&, unsigned long) const + 995
5 REDCODE.node 0x60b3ad64 REDCORE::TokenStream::GetBytes(REDCORE::Buffer&, unsigned long) + 172
6 REDCODE.node 0x60b3ad8b REDCORE::TokenStream::GetBytes(REDCORE::Buffer&) + 37
7 REDCODE.node 0x60b3a337 REDCORE::Tokenizer::GetPayloadInNewBufferFromOffset(unsigned long, unsigned long, unsigned long, char const*) + 187
8 REDCODE.node 0x60b38886 REDCORE::RedFileParser::ParseFrameFromFile(unsigned long, REDCORE::MetadataStore*) + 118
9 REDCODE.node 0x60b3cf7e REDCORE::RedClip::DecodeVideoFrame(unsigned long, OutputJob&) + 306
10 REDCODE.node 0x60c608bd RC_Track::decode_image(int, int, int&, double&) + 475
11 REDCODE.node 0x60c6120a RC_Track::ensure_image(int, bool) + 202
12 REDCODE.node 0x60c61414 RedCodeNode::lock_image(double) + 212
13 AssimServices.dylib 0x3b147f14 IBuffer::is_valid() const + 124
14 REDCODE.node 0x60c63742 RedCodeNode::get_result(double) + 944
15 AssimComponents.dylib 0x015265a8 FXNodeViewImpl::pre_draw() + 240
16 AssimServices.dylib 0x3b0eeb20 Widget_render() + 3424
17 AssimServices.dylib 0x3b0c9ca4 asrv_render(bool) + 346
18 AssimComponents.dylib 0x01365ef6 Exec_REDCINE + 952
19 RED.DIGITAL.CINEMA 0x00002ce4 0x1000 + 7396
20 RED.DIGITAL.CINEMA 0x000022c2 0x1000 + 4802
21 RED.DIGITAL.CINEMA 0x000021e9 0x1000 + 4585

Thread 1:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 AssimCore.dylib 0x0002918f m_entry(void*) + 87
2 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 AssimCore.dylib 0x0002918f m_entry(void*) + 87
2 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 3:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 AssimCore.dylib 0x0002918f m_entry(void*) + 87
2 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 4:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 AssimCore.dylib 0x0002c304 mp_cond_wait(__cond_str*, __mutex_str*) + 24
2 AssimServices.dylib 0x3b0a4b5e cache_thread_entry(void*) + 82
3 AssimCore.dylib 0x0002c634 as_thread_entry(void*) + 26
4 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 5:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 AssimCore.dylib 0x0002c304 mp_cond_wait(__cond_str*, __mutex_str*) + 24
2 AssimServices.dylib 0x3b0a4b5e cache_thread_entry(void*) + 82
3 AssimCore.dylib 0x0002c634 as_thread_entry(void*) + 26
4 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 6:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 AssimCore.dylib 0x0002c304 mp_cond_wait(__cond_str*, __mutex_str*) + 24
2 AssimServices.dylib 0x3b0a4b5e cache_thread_entry(void*) + 82
3 AssimCore.dylib 0x0002c634 as_thread_entry(void*) + 26
4 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 7:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 REDCODE.node 0x60c064de kdu_thread_entity::process_jobs(kdu_thread_queue*, bool, bool) + 468
2 REDCODE.node 0x60c08140 worker_startproc(void*) + 48
3 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 8 Crashed:
0 REDCODE.node 0x60b7e245 kd_thread_env::flush(bool) + 1351
1 REDCODE.node 0x60b7e7fd kdu_thread_env::do_sync(bool) + 65
2 REDCODE.node 0x60c06bde kdu_thread_entity::process_jobs(kdu_thread_queue*, bool, bool) + 2260
3 REDCODE.node 0x60c08140 worker_startproc(void*) + 48
4 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 9:
0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7
1 REDCODE.node 0x60ba02e6 kdu_subband::open_block(kdu_coords, int*, kdu_thread_env*) + 792
2 REDCODE.node 0x60b5216c kd_decoder::do_job(kdu_thread_entity*, int) + 382
3 REDCODE.node 0x60c0683a kdu_thread_entity::process_jobs(kdu_thread_queue*, bool, bool) + 1328
4 REDCODE.node 0x60c08140 worker_startproc(void*) + 48
5 libSystem.B.dylib 0x90024227 _pthread_body + 84

Thread 8 crashed with X86 Thread State (32-bit):
eax: 0x0000357b ebx: 0x60b7dd0c ecx: 0x003786a0 edx: 0xffffffff
edi: 0x60c39f98 esi: 0x00000000 ebp: 0xb0407e68 esp: 0xb0407e10
ss: 0x0000001f efl: 0x00010206 eip: 0x60b7e245 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037


Model: MacPro1,1, BootROM MP11.005C.B08, 4 processors, Dual-Core Intel Xeon, 3 GHz, 8 GB
Graphics: NVIDIA Quadro FX 4500, NVIDIA Quadro FX 4500, PCIe, 512 MB
 
REDCINE will not launch.

REDCINE will not launch.

Here's the scoop. We're in our second week of shooting a feature on #406. Everything has been running great until Saturday. We tried our first render out of an .R3D file to a self contained movie in QT (7.3.1) using H.264, 720x480, at 23.98. We got an error message saying Redcine could not process certain frames. Ever since then Redcine crashes on launch. We have tried every combination of fixes, reboots, and re-installs, to resolve the issue, with no luck. We even reverted to a cloned image of the system we started with, and it still crashes on launch.

We're on build 14 -- shooting 4k -- 2:1 -- 23.98 -- 8 Proc Mac Pro -- Latest versions of everything except we're running QT 7.3.1 -- Nothing has changed from day one. We know about trashing the Redcine folder in the library when re-installing Redcine. Red Alert even stopped working for a while (we did get it back up and running).

I'd really appreciate any help I can get on this one. We're all stumped.

Kelly H.
kelly@all-in-one-truck.com
1-888-81-TRUCK

EDIT: We started launching with the "Redcine Reset" utility, and that seems to be working fine. Now the problem is, Redcine won't let us load files from separate volumes (drives) in the same "project". We also can't save multiple projects if the files are located on separate drives.
 
freeze frame help!!!

freeze frame help!!!

While exporting red one 4K to SD the first clip on the timeline comes out grate then all other clips have a freeze frame coming from the first clip.

mac quad 2.8
2gb
ati 2600

any ideas?

Thanks.
 
The 1.33:1 NTSC 4:3 guides in RedCine are incorrect. They appear to be based on non-square pixel math; the area bounded by these guides is actually 1.48:1, which is equivalent to the aspect ratio of a 720x486 frame.
 
Ok, not sure if anyone has posted this yet or not. But today I came across an interesting freeze frame rendering issue. So the company I work for shot some footage this past week, and my co-worker opened it in Redcine in such a way that all of the footage was in one stack. Instead of trying to fix the problem, he just went ahead and started coloring the footage. So, when it was handed to me, I had to manually un-stack all the footage (I know the level depth field exists, but I couldn't get it to work with footage that was already in the project and keep his color settings). Upon rendering, it rendered the first shot fine, but everything from then on was a freeze frame. Thought it was my Redcine settings on the mac, so I cleared that. Still same issue. Re-downloaded redcine, cleared cache again, same issue. Tried the same thing on 4 other macs. Same issue. So I just imported the raw footage correctly and tried to export it without any color correction and it worked like a charm. So I went back to his project, exported color settings for the shots, and merged those with my project and everything is rendering correctly. Not sure if there was something better that I could have done, but it seems to me that manually re-ordering your stacks and getting freeze frame renders on output is considered a bug.
 
These may already be posted (some may be considered feature requests):

1) Saving Project does not save Thumbnail changes.

2) When Rendering Clips or Saving Snaps (JPG / TIF), there is no requester which asks to Overwrite if a file already exists. Sometimes this leads to accidental replacement of a good file, when one wanted to save an alternate version instead.

3) S-Curves do not have numeric entry.

4) When in "Fit" View, the top swipe bar is overlaid on top of the Image. If present, "Fit" should account for this and fit the image inside all present menu bars.

5) Copy and Paste effect both color AND shot settings. This makes it difficult in certain situations where you have made changes to a shot in color and size, but only wish to copy and paste one of the changes to other clips.

thanks for the opportunity to give direct feedback.
 
timecode different in FCP and Redcine

timecode different in FCP and Redcine

The displayed timecode is different in Redcine 0.90 and FCP 6.0.2. I'm sure the Timecode from the H proxies in FCP is right, because it timecode syncs in FCP with double system audio that was jam synced in shooting. Interestingly the timecode in Redcine is always later ( using time of day code ) than the fcp proxies. The dpx files exported from Redcine have the wrong timecode. Redcine displays the correct timecode on screen but writes the inccorrect timecode into the dpx metadata.

10.4.11 Mac pro 4 x 2.66 5GB ram NVIDIA GeForce 7300 GT
 
Cyclotron said:
The displayed timecode is different in Redcine 0.90 and FCP 6.0.2. I'm sure the Timecode from the H proxies in FCP is right, because it timecode syncs in FCP with double system audio that was jam synced in shooting. Interestingly the timecode in Redcine is always later ( using time of day code ) than the fcp proxies. The dpx files exported from Redcine have the wrong timecode.

10.4.11 Mac pro 4 x 2.66 5GB ram NVIDIA GeForce 7300 GT
Click to expand...

Shooting 25fps?

Make sure your REDCINE construct/project is set to 25fps; if defaults to 24 and if you don't change it all your TC will be wrong.
 
All of a sudden I am now having the freeze frame render issue in Red Cine and it's holding up this Kleenex job I shot and I need to get a fix. Any way to fix this freeze frame render issue? I've uninstalled and reinstalled Red Cine and it's still happening.
 
MacOS 10.5.3 bug

MacOS 10.5.3 bug

Just updated to 10.5.3. I have a failed import from xml files. Those files are maded with crimson. There is nothing wrong with the crimson files.
On another computer with 10.5.2 the same settings will it work.
 
Status
Not open for further replies.
Back
Top