Thijs Koerselman

I've tried 2 different approaches to recording movies to photo jpeg codec.

- qt.record @raw -> afterwards export to photojpeg in quicktime player.

Exporting afterwards generates much better quality and higher bandwidth. For

example exporting from raw to jpeg quality high results in 29mbit/s as

opposed to 11mbit/s for recording directly to jpeg @ quality max. I don't

really understand why it has to be like this. Is it maybe possible for

jitter in the future to export good quality jpeg?

I remember a discussion about the qt.record options some time ago, ending in

a vague promise about extending the export possibilities for a future jitter

update. Is this maybe the case in 1.6? I would just love to be able to

export good quality jpeg without having to deal with the filesizes of raw

- qt.record @raw -> afterwards export to photojpeg in quicktime player.
- qt.record @jpeg max

Exporting afterwards generates much better quality and higher bandwidth. For
example exporting from raw to jpeg quality high results in 29mbit/s as
opposed to 11mbit/s for recording directly to jpeg @ quality max. I don't
really understand why it has to be like this. Is it maybe possible for
jitter in the future to export good quality jpeg?
I remember a discussion about the qt.record options some time ago, ending in
a vague promise about extending the export possibilities for a future jitter
update. Is this maybe the case in 1.6?  I would just love to be able to
export good quality jpeg without having to deal with the filesizes of raw
video first.

jit-qt-record-jpeg-quality

Am 28.06.2006 um 00:44 schrieb Thijs Koerselman:

> I don't really understand why it has to be like this.

t=msg&goto=57576&rid=0&S=74f61f2ce0a11734f1ef793ac21571ef#msg_57576

and it is still the same now with different QT and jitter versions. All 

files generated by attached patch are 685685 Bytes in size for me. They 

are not identical, viewed in a hex editor there are a few bytes that 

I have the same problem:
https://cycling74.com/forums/index.php? 
t=msg&goto=57576&rid=0&S=74f61f2ce0a11734f1ef793ac21571ef#msg_57576
and it is still the same now with different QT and jitter versions. All  
files generated by attached patch are 685685 Bytes in size for me. They  
are not identical, viewed in a hex editor there are a few bytes that  
differ, but size is always the same.

Thanks for the reports. The bug has been identified and will be fixed 

Am 28.06.2006 um 13:11 schrieb Georg Bosch:

> t=msg&goto=57576&rid=0&S=74f61f2ce0a11734f1ef793ac21571ef#msg_57576

> and it is still the same now with different QT and jitter versions. 

> All files generated by attached patch are 685685 Bytes in size for 

> me. They are not identical, viewed in a hex editor there are a few 

> bytes that differ, but size is always the same.

Thanks for the reports. The bug has been identified and will be fixed  
for the next releases.

> I have the same problem:
> https://cycling74.com/forums/index.php? 
> t=msg&goto=57576&rid=0&S=74f61f2ce0a11734f1ef793ac21571ef#msg_57576
> and it is still the same now with different QT and jitter versions.  
> All files generated by attached patch are 685685 Bytes in size for  
> me. They are not identical, viewed in a hex editor there are a few  
> bytes that differ, but size is always the same.


> Thanks for the reports. The bug has been identified and will be fixed 

> Thanks for the reports. The bug has been identified and will be fixed 
> for the next releases.

is it fixed in 1.6 beta? if not, any timing ?

also would it be possible to add a quality parameter to exportimage 

message to jit.matrix, jit.qt.grab,... when saving in jpeg.

BTW, thanks for adding in 1.6 a 'datarate' parameter to jit.qt.record 

>Thanks for the reports. The bug has been identified and will be 

>Am 28.06.2006 um 13:11 schrieb Georg Bosch:

https://cycling74.com/forums/index.php?t=msg&goto=57576&rid=0&S=74f61f2ce0a11734f1ef793ac21571ef#msg_57576

>>and it is still the same now with different QT and jitter versions. 

>>All files generated by attached patch are 685685 Bytes in size for 

>>me. They are not identical, viewed in a hex editor there are a few 

>>bytes that differ, but size is always the same.

is it fixed in 1.6 beta? if not, any timing ?
also would it be possible to add a quality parameter to exportimage 
message to jit.matrix, jit.qt.grab,... when saving in jpeg.

BTW, thanks for adding in 1.6 a 'datarate' parameter to jit.qt.record 
for codecs which support it!

>Thanks for the reports. The bug has been identified and will be 
>fixed for the next releases.
>
>jb
>
>Am 28.06.2006 um 13:11 schrieb Georg Bosch:
>
>>I have the same problem:
>>https://cycling74.com/forums/index.php?t=msg&goto=57576&rid=0&S=74f61f2ce0a11734f1ef793ac21571ef#msg_57576
>>and it is still the same now with different QT and jitter versions. 
>>All files generated by attached patch are 685685 Bytes in size for 
>>me. They are not identical, viewed in a hex editor there are a few 
>>bytes that differ, but size is always the same.
>

-- 
Yves Bernard    yb@imal.org
asbl iMAL vzw
rue d'Alost straat 7
1000 Bruxelles/Brussel
tel 32 2 213 37 10

http://www.imal.org
http://www.i-cult.be


Am 29.07.2006 um 13:37 schrieb Yves Bernard:

> is it fixed in 1.6 beta? if not, any timing ?

> also would it be possible to add a quality parameter to exportimage 

> message to jit.matrix, jit.qt.grab,... when saving in jpeg.

Maybe in the future. I would need to look into what's involved.

> BTW, thanks for adding in 1.6 a 'datarate' parameter to 

> jit.qt.record for codecs which support it!

> hi Jeremy,
>
> is it fixed in 1.6 beta? if not, any timing ?

> also would it be possible to add a quality parameter to exportimage  
> message to jit.matrix, jit.qt.grab,... when saving in jpeg.

> BTW, thanks for adding in 1.6 a 'datarate' parameter to  
> jit.qt.record for codecs which support it!

yes I have, and I recall it looks about the same, and is not as good as jpeg

can be. Jeremy already confirmed the bug and from what I understand it is

currently not possible to get the highest quality photojpeg directly from

On 7/31/06, darcysays  wrote:
>
>
> Have you tried the lossless setting?

yes I have, and I recall it looks about the same, and is not as good as jpeg
can be. Jeremy already confirmed the bug and from what I  understand it is
currently not possible to get the highest quality photojpeg directly from
jit.qt.record.

at least, on OSX, there is a workaround for exportimage jpeg quality control :

save in Max with exportimage in a lossless format (eg tiff), then 

call the Unix Apple sips tool (image processing) with the shell 

object of Bill Orcutt, as in this example:

/usr/bin/sips -s format jpeg -s formatOptions best test.tif --out test.jpg

i don't know if there is a shell command line interface to 

quicktime... (through applescript, this should be possible... but 

>Am 29.07.2006 um 13:37 schrieb Yves Bernard:

>>is it fixed in 1.6 beta? if not, any timing ?

>>also would it be possible to add a quality parameter to exportimage 

>>message to jit.matrix, jit.qt.grab,... when saving in jpeg.

>Maybe in the future. I would need to look into what's involved.

>>BTW, thanks for adding in 1.6 a 'datarate' parameter to 

>>jit.qt.record for codecs which support it!

save in Max with exportimage in a lossless format (eg tiff), then 
call the Unix Apple sips tool (image processing) with the shell 
object of Bill Orcutt, as in this example:
/usr/bin/sips -s format jpeg -s formatOptions best test.tif --out test.jpg

i don't know if there is a shell command line interface to 
quicktime... (through applescript, this should be possible... but 
this is applescript)

>Am 29.07.2006 um 13:37 schrieb Yves Bernard:
>
>>hi Jeremy,
>>
>>is it fixed in 1.6 beta? if not, any timing ?
>
>yes
>
>>also would it be possible to add a quality parameter to exportimage 
>>message to jit.matrix, jit.qt.grab,... when saving in jpeg.
>
>Maybe in the future. I would need to look into what's involved.
>
>>BTW, thanks for adding in 1.6 a 'datarate' parameter to 
>>jit.qt.record for codecs which support it!
>
>A pleasure.
>
>jb

jit.qt.record jpeg quality