RedAlert won't output QT's

[Paul Didier Mogg]

Hi Folks,
Just got my camera, incredible machine, thank you RED!

RedAlert however, won't output ProRes QT's for me. It appears to go through the process, displaying a count of the frames, but the QT movie produced is always only 8k in size and has what appears to be just one frame of content.
RedRushes isn't outputting anything either.

I'm using the following setup:

MacBook Pro - Intel Core Duo 2.16Ghz
Quicktime 7.5
OSX 10.4.11

Is there a central thread to go to for information on:
1) Known bugs / System Configuration no-no's?
2) Written instruction manuals for RedAlert / RedCine / RedRushes?

(Please don't say that they're self-explanatory or too simple to require instructions)

Thank you,

Paul

 

[Deanan]

Can you try using the render in terminal button in RA and let us know what happens in the terminal?

 

[Paul Didier Mogg]

Here's what I get when I hit the Render In Terminal button, no idea if I'm using this tool correctly...

Welcome to Darwin!
MacBookPro:~ moggy$ REDline -i (null) -o /Volumes/100Gb_Disk 1/RED Test Footage/MoggyTest1.mov -w 11 -R 2 --filter 5 --fit 1 --QTcodec 0 -I 320 -B 0.000000 -C 0.000000 -x 0.000000 -k 5600 -T 1.247312 -t 0.000000 -r 1.000000 -g 1.000000 -b 1.000000 -X 0.000000 --blackX 0.000000 --blackY 0.000000 --toeX 25.000000 --toeY 25.000000 --midX 50.000000 --midY 50.000000 --kneeX 75.000000 --kneeY 75.000000 --whiteX 100.000000 --whiteY 100.000000 --black 0.000000 --white 100.000000 -G 14 -d 4 -D 100 --NR 1000 -c 11 -s 1 -e 1 -V 0
-bash: syntax error near unexpected token `('

 

[Paul Didier Mogg]

Also, RedAlert always crashes if I hit the Render Button after having hit the Render In Terminal button. Hope that helps.

 

[Alex Carr]

It may be Quicktime 7.5 and Mac OS X 10.4.11.... I'm sure 10.5 and 7.5 works,

re-install Redcode Quicktime Codec, update FCP to 6.0.4,

You might have to downgrade Quicktime or upgrade to Leopard... Neither sounds pleasent....

 

[Deanan]

It looks like a problem with funny characters in the path of the R3D file.

Which version are you using?

 

[Paul Didier Mogg]

I'm using RedAlert version 3.48
There are spaces in the folder name "RED Test Footage" but no other unusual characters in the path name.

 

[Deanan]

The input path that says (null) is of concern. What's the path to the R3D file?

 

[Paul Didier Mogg]

I just ran a clean test, rebooted the laptop first, shut down all other programs, but got the same result unfortunately.

In RedAlert, after hitting the RENDER button and the output destination dialogue pops up, I navigated to these path and filenames:

Folder: /Volumes/100Gb_Disk 1/RED Test Footage

Filename: Test5.mov

then hit the Render in Terminal button and got this...

Last login: Sat Aug 30 19:49:14 on console
Welcome to Darwin!
MacBookPro:~ moggy$ REDline -i (null) -o /Volumes/100Gb_Disk 1/RED Test Footage/Test5.mov -w 11 -R 2 --filter 5 --fit 1 --QTcodec 0 --resizeX 1920 --resizeY 1080 -I 320 -B 0.000000 -C 0.000000 -x 0.000000 -k 5600 -T 1.000000 -t 0.000000 -r 1.000000 -g 1.000000 -b 1.000000 -X 0.000000 --blackX 0.000000 --blackY 0.000000 --toeX 25.000000 --toeY 25.000000 --midX 50.000000 --midY 50.000000 --kneeX 75.000000 --kneeY 75.000000 --whiteX 100.000000 --whiteY 100.000000 --black 0.000000 --white

Paul

 

[Paul Didier Mogg]

Oops, part of my post got cut off, here's the results again..

Last login: Sat Aug 30 19:49:14 on console
Welcome to Darwin!
MacBookPro:~ moggy$ REDline -i (null) -o /Volumes/100Gb_Disk 1/RED Test Footage/Test5.mov -w 11 -R 2 --filter 5 --fit 1 --QTcodec 0 --resizeX 1920 --resizeY 1080 -I 320 -B 0.000000 -C 0.000000 -x 0.000000 -k 5600 -T 1.000000 -t 0.000000 -r 1.000000 -g 1.000000 -b 1.000000 -X 0.000000 --blackX 0.000000 --blackY 0.000000 --toeX 25.000000 --toeY 25.000000 --midX 50.000000 --midY 50.000000 --kneeX 75.000000 --kneeY 75.000000 --whiteX 100.000000 --whiteY 100.000000 --black 0.000000 --white 100.000000 -G 14 -d 4 -D 100 --NR 1000 -c 11 -s 1 -e 1 -V 0
-bash: syntax error near unexpected token `('
MacBookPro:~ moggy$

I then noticed that the program is adding a "1" to the end of my disk pathname when I navigate to it, it should be just "100Gb_Disk" not "100Gb_Disk 1"
I tried running another test and deleting the added "1" from the pathname, but got the same "null" in the results as you mentioned.

 

[Deanan]

OSX sometimes adds the 1 when you have two disks with the same name.

Maybe that's what's causing the RA/OSX to get confused?

Try rendering the same file from/to the desktop.

Can you open up a terminal window and do a "df" and post the output?

 

[Paul Didier Mogg]

The "null" was caused by my silly mistake, in my hurry to runt the tests I forgot to load the .R3D file. Just did it again and got this....

Last login: Sat Aug 30 19:55:49 on ttyp1
Welcome to Darwin!
MacBookPro:~ moggy$ REDline -i /Volumes/100Gb_Disk 1/RED Test Footage/A005_08281E.RDM/Spoon_Drip_300m lens.RDC/A005_C007_0828DH_001.R3D -o /Volumes/100Gb_Disk 1/RED Test Footage/Test2.mov -w 11 -R 2 --filter 5 --fit 1 --QTcodec 0 --resizeX 1920 --resizeY 1080 -I 320 -B 2.365592 -C 0.139785 -x 1.462365 -k 6502 -T 1.591398 -t -2.300000 -r 1.000000 -g 1.000000 -b 1.000000 -X 0.537634 --blackX 0.000000 --blackY 0.000000 --toeX 25.000000 --toeY 25.000000 --midX 50.000000 --midY 50.000000 --kneeX 75.000000 --kneeY 75.000000 --whiteX 100.000000 --whiteY 100.000000 --black 0.000000 --white 100.000000 -G 14 -d 4 -D 100 --NR 1000 -c 11 -s 190 -e 196 -V 0
MacBookPro:~ moggy$

Then I hit the render button, the program seemed to output a few frames and then crashed. A .mov file was created but was only 4k in size.

I just tried running the test again on another Macbook Pro 2.4 Ghz core 2 duo with OSX 10.5.4 and Quicktime 7.5 using the same disk attached and same file, and it ran fine and output the file. So it's probably not the disk or file causing the problem.

 

[Paul Didier Mogg]

Just tried again (on the original problem MacBook Pro) to double check and loaded a different .R3D file, but RedAlert always crashes after a few seconds of hesitation and the start of the blue progress bar appearing.

 

[Deanan]

It could be 10.4.11 that's causing a problem.

 

[Paul Didier Mogg]

Here's the "df" results you asked for. Yes, it would seem that maybe 10.4.11
is the culprit, guess I'll finally have to upgrade this computer.

Last login: Sat Aug 30 20:28:11 on ttyp1
Welcome to Darwin!
MacBookPro:~ moggy$ df
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/disk0s2 182452224 168569168 13371056 93% /
devfs 196 196 0 100% /dev
fdesc 2 2 0 100% /dev
<volfs> 1024 1024 0 100% /.vol
/dev/disk0s3 12223608 11239784 983824 92% /Volumes/WINDOZE
automount -nsl [241] 0 0 0 100% /Network
automount -fstab [249] 0 0 0 100% /automount/Servers
automount -static [249] 0 0 0 100% /automount/static
/dev/disk1s3 195109344 173809624 21299720 89% /Volumes/100Gb_Disk 1
MacBookPro:~ moggy$