Magic Lantern 0.2.1 for 550D firmware 1.0.9

[Alex]

Following Chris' suggestion, I'm increasing ML version number in order
to prevent further thread splitting problems :)

I've upgraded to GCC 4.6.0, with the attached summon-arm script
(which is a modified version of
https://github.com/dan-wellkeeper/summon-arm-toolchain ). Results:

* With the new GCC, autoexec.bin shrunk by 8k (which I think it's pretty good).

* There was a strange structure alignment problem with picture style
data, and maybe with bitrate structure too: 0x12345678 was displayed
as 0x56781234. The issue was only present with -Os; it was working
fine with -O1 and -O2 (but with larger autoexec.bin). Adding the
"aligned" attribute to the buggy structure fixed the problem. There
might be more issues like this, but I didn't notice anything so far.

* String trimming problems seem to have disappeared as far as I could
notice (yay!).

Code is pretty much the same as with previous builds, except the
alignment attribute:
https://bitbucket.org/hudson/magic-lantern/changeset/548b44db0789

Before doing further changes, I'd like to know if there are more (or
less) side effects from upgrading the compiler, so please report any
issues you find. I'm looking especially for issues which only happen
with only one of last two builds (but not with the other). Thanks.

P.S. This message should have arrived yesterday, but I've looked it up
in the mailing list and it's not there, so I'm reposting it. That's
why this build is still marked as Jun07.

[VisualRender]

Hi Alex,
In version Jun07 If the split screen and Magic Zoom are activated and
you when you begin recording all functions become buggy it happens
with both the 160k autoexec.bin and in the 168k earlier Jun7version,
The May25 version is Ok.
I miss Movie AF.

On 8 jun, 08:50, Alex <broscutama...@gmail.com> wrote:
> Following Chris' suggestion, I'm increasing ML version number in order
> to prevent further thread splitting problems :)
>
> I've upgraded to GCC 4.6.0, with the attached summon-arm script

> (which is a modified version ofhttps://github.com/dan-wellkeeper/summon-arm-toolchain). Results:

>
> * With the new GCC, autoexec.bin shrunk by 8k (which I think it's pretty good).
>
> * There was a strange structure alignment problem with picture style
> data, and maybe with bitrate structure too: 0x12345678 was displayed
> as 0x56781234. The issue was only present with -Os; it was working
> fine with -O1 and -O2 (but with larger autoexec.bin). Adding the
> "aligned" attribute to the buggy structure fixed the problem. There
> might be more issues like this, but I didn't notice anything so far.
>
> * String trimming problems seem to have disappeared as far as I could
> notice (yay!).
>
> Code is pretty much the same as with previous builds, except the
> alignment attribute:https://bitbucket.org/hudson/magic-lantern/changeset/548b44db0789
>
> Before doing further changes, I'd like to know if there are more (or
> less) side effects from upgrading the compiler, so please report any
> issues you find. I'm looking especially for issues which only happen
> with only one of last two builds (but not with the other). Thanks.
>
> P.S. This message should have arrived yesterday, but I've looked it up
> in the mailing list and it's not there, so I'm reposting it. That's
> why this build is still marked as Jun07.
>

>  summon-arm
> 19 KVerDescargar
>
>  magiclantern-2011Jun07.550d.fw109.alex.zip
> 1832 KVerDescargar

[Chris71]

A warm welcome to version 0.2.1!! :-)

I didn't test it yet very much, but I want to give you a short
feedback to the problems I encountered with yesterday's build:

* With today's build, it seems that the black-screen-on-startup-
problem is now gone with my camera. It seems that the 8k smaller
binary size is helping here. :-)

* The problem with the camera crashing after taking a photo in live
view is still the same, but if I turn off the special actions for
display (last
item in LiveV menu) as you suggested, the problem does *not* occure!
Usually I had it set to "Clr on HalfShutter", but setting it to "No
special action" is OK for me.

Now that live view is working again, I now also tested moving the
ghost image with the arrow keys (for which Follow Focus has to be
disabled) and I think that this feature is now nicely implemented.

I have just one more suggestion for this feature: If the ghost image
has been moved with the arrow keys (which in my opinion only makes
sense for making a panoramic shot), it would be useful if ML would
automatically generate a ghost image of the next picture taken and
move it to the same position in live view as the previous ghost image.
This way this procedure (which will be needed until the last picture
of the panoramic shot) wouldn't have to be performed by hand.

On 8 Jun., 15:50, Alex <broscutama...@gmail.com> wrote:
> Following Chris' suggestion, I'm increasing ML version number in order
> to prevent further thread splitting problems :)
>
> I've upgraded to GCC 4.6.0, with the attached summon-arm script

> (which is a modified version ofhttps://github.com/dan-wellkeeper/summon-arm-toolchain). Results:

>
> * With the new GCC, autoexec.bin shrunk by 8k (which I think it's pretty good).
>
> * There was a strange structure alignment problem with picture style
> data, and maybe with bitrate structure too: 0x12345678 was displayed
> as 0x56781234. The issue was only present with -Os; it was working
> fine with -O1 and -O2 (but with larger autoexec.bin). Adding the
> "aligned" attribute to the buggy structure fixed the problem. There
> might be more issues like this, but I didn't notice anything so far.
>
> * String trimming problems seem to have disappeared as far as I could
> notice (yay!).
>
> Code is pretty much the same as with previous builds, except the
> alignment attribute:https://bitbucket.org/hudson/magic-lantern/changeset/548b44db0789
>
> Before doing further changes, I'd like to know if there are more (or
> less) side effects from upgrading the compiler, so please report any
> issues you find. I'm looking especially for issues which only happen
> with only one of last two builds (but not with the other). Thanks.
>
> P.S. This message should have arrived yesterday, but I've looked it up
> in the mailing list and it's not there, so I'm reposting it. That's
> why this build is still marked as Jun07.
>

>  summon-arm
> 19KAnzeigenHerunterladen
>
>  magiclantern-2011Jun07.550d.fw109.alex.zip
> 1832KAnzeigenHerunterladen

[John Veto]

With this build and the last two (May 25th? maybe) I've noticed the
Magic Zoom window flickers. Seems like it's refreshing and there seems
to be a transparency to the Magic Zoom window so it's difficult to see
what's in focus. The transparency could just be caused by the
flickering too. This behavior is the same when Split Screen is on or
off.

[Alex]

Are you using 720p? It won't work well in this mode.

[John Veto]

Yes that was the problem! Camera was set to 720p... set back to 1080p
and all works as expected. Many Thanks for all your hard work!

[Ryan Novak-Smith]

Everything works fine so far, except the kelvin whitebalance. It only
shows autowb, but I can change the value, just the temperature won't
show.

On Jun 8, 9:50 am, Alex <broscutama...@gmail.com> wrote:
> Following Chris' suggestion, I'm increasing ML version number in order
> to prevent further thread splitting problems :)
>
> I've upgraded to GCC 4.6.0, with the attached summon-arm script

> (which is a modified version ofhttps://github.com/dan-wellkeeper/summon-arm-toolchain). Results:

>
> * With the new GCC, autoexec.bin shrunk by 8k (which I think it's pretty good).
>
> * There was a strange structure alignment problem with picture style
> data, and maybe with bitrate structure too: 0x12345678 was displayed
> as 0x56781234. The issue was only present with -Os; it was working
> fine with -O1 and -O2 (but with larger autoexec.bin). Adding the
> "aligned" attribute to the buggy structure fixed the problem. There
> might be more issues like this, but I didn't notice anything so far.
>
> * String trimming problems seem to have disappeared as far as I could
> notice (yay!).
>
> Code is pretty much the same as with previous builds, except the
> alignment attribute:https://bitbucket.org/hudson/magic-lantern/changeset/548b44db0789
>
> Before doing further changes, I'd like to know if there are more (or
> less) side effects from upgrading the compiler, so please report any
> issues you find. I'm looking especially for issues which only happen
> with only one of last two builds (but not with the other). Thanks.
>
> P.S. This message should have arrived yesterday, but I've looked it up
> in the mailing list and it's not there, so I'm reposting it. That's
> why this build is still marked as Jun07.
>

>  summon-arm
> 19KViewDownload
>
>  magiclantern-2011Jun07.550d.fw109.alex.zip
> 1832KViewDownload

[skater1121995]

Everything works fine, but the kelvin white balance doesn't display
temp, only says autowb. But it will change the value.

[heartbeat]

is it possible to get shuttertimes bigger than 1/30 sec. maybe till 2
sec. ? it is not so good but a user in a german board ask about it
becouse of filming Satellite-Flares

[Alex]

http://groups.google.com/group/ml-devel/browse_thread/thread/9e8135bcef006c25

Avidemux+ImageMagick will work too; maybe avisynth too (I didn't try).
You need some coding skills for these.

If you find a better program for doing this, please post a link to it.

> --
> http://magiclantern.wikia.com/
>
> To post to this group, send email to ml-d...@googlegroups.com
> To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en

[James Donnelly]

It's a shame it is not possible to do with the firmware.

Is it actually possible to simulate this effect in post?

If you expose a static background correctly for long shutter speeds, then transient elements, like people walking through will not get fully 'developed' because they are not there long enough, resulting in 'ghostly apparition' type shots.

I sometimes use this effect for stills; you can photograph buildings with apparently no people in front of them, even if people do walk past in between the lens and the building - so long as they don't hang around too long.

[heartbeat]

my old 500d used lower shutterspeed if the iso doesnt reach enough or i
´m wrong?

On 10 Jun., 18:31, James Donnelly <jam...@easynet.co.uk> wrote:
> It's a shame it is not possible to do with the firmware.
>
> Is it actually possible to simulate this effect in post?
>
> If you expose a static background correctly for long shutter speeds, then
> transient elements, like people walking through will not get fully
> 'developed' because they are not there long enough, resulting in 'ghostly
> apparition' type shots.
>
> I sometimes use this effect for stills; you can photograph buildings with
> apparently no people in front of them, even if people do walk past in
> between the lens and the building - so long as they don't hang around too
> long.
>

> On 10 June 2011 16:03, Alex <broscutama...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
> >http://groups.google.com/group/ml-devel/browse_thread/thread/9e8135bc...

[Alex]

> Is it actually possible to simulate this effect in post?

Of course; you have quoted my messages saying how to do this :)

[James Donnelly]

Yes I have.  And I read all the links too.  I also downloaded Frame merger and read the included description.

After all that, I still don't understand how merging frames achieves all the the effects possible with slow shutter speeds.  It seems to me they would be visually different, which I obviously explained very poorly in my last post.  I can see how frame merging might tackle the staccato effect of high shutter speeds, by introducing motion blur.

I would be grateful if someone would correct my misunderstanding, and if possible link to some footage demonstrating the 'ghost' effect achieved with frame merging.  Example here:

http://vimeo.com/5588719, 03:24

If you shoot this scene at 1/30th, the guy and the background are exposed properly, and a frame merge just blurs him, while the slow shutter speed effect means the guy is under-exposed with respect to the background, and blurs but also slightly disappears.  Right or wrong?

I can't put this to the test, because I don't have a video camera with slow enough shutter speeds to try what I'm thinking of.

On 10 June 2011 18:05, Alex <broscu...@gmail.com> wrote:

> Is it actually possible to simulate this effect in post?

Of course; you have quoted my messages saying how to do this :)

On Fri, Jun 10, 2011 at 6:31 PM, James Donnelly <jam...@easynet.co.uk> wrote:
> It's a shame it is not possible to do with the firmware.
>
> Is it actually possible to simulate this effect in post?
>
> If you expose a static background correctly for long shutter speeds, then
> transient elements, like people walking through will not get fully
> 'developed' because they are not there long enough, resulting in 'ghostly
> apparition' type shots.
>
> I sometimes use this effect for stills; you can photograph buildings with
> apparently no people in front of them, even if people do walk past in
> between the lens and the building - so long as they don't hang around too
> long.
>
>
>
> On 10 June 2011 16:03, Alex <broscu...@gmail.com> wrote:
>>
>>

>> http://groups.google.com/group/ml-deveWith slow shutter speeds, you would shoot a scene with a smaller aperture or lower l/browse_thread/thread/9e8135bcef006c25

[Alex]

If you shoot at 1/30 at 30fps, the duty cycle of the sensor is very
close to 100% (i.e. most of the time, the sensor gets light). This
means if you average every 2 consecutive frames, you will get the
equivalent of 1/15 seconds for each frame. Of course, there will be
some overlapping.

If you average 30 frames (i.e. mean(frames 1:30) => frame 1;
mean(frames 2:31) => frame 2 and so on, you will get the equivalent of
1 second exposure time.

If you have staccato effect, which is obtained for short exposure
times, it means sensor duty cycle is very low (let's say 10%). In this
case, you are discarding most of the "data", which will result in...
aliasing. Of course, on the temporal axis this time :)

In plain words, frame merging won't remove the staccato effect (it
might reduce it a bit, just like how bluring reduces moire a bit).

I believe the simplest way is to change Frame Merger's source code to
allow for merging more frames. A moving average filter (IIR) may do a
similar job with much less memory overhead than plain averaging (but
the visual effect may be a bit different).

[James Donnelly]

It makes more sense now.  Thanks for your time,  I appreciate it.  I can't find the source for Frame Merger, but I've done a bit with ImageMagick in the past, so I might have a crack at that approach

In any case, we're not able to introduce lower shutter speeds because they're controlled in DIGIC land rather than DryOS land, right? 

[Alex]

It's in the other thread; I'm reposting the link. That little program
is not maintained any more, but right now it has the chance to get a
new life :)

http://www.findthatfile.com/search-10704809-hZIP/winrar-winzip-download-virtualdub-filters-zip.htm

With shutter speeds faster than 1/fps, you expose a frame, then save
it, expose another, save it (with some parallelism involved, of
course). With slower speeds, you will also have to do the averaging,
so it's not just changing a parameter.

[jwr94]

When i use an external mic only the left channel is working.

[Malcolm Debono]

Are you sure the mic is stereo? Have you checked the source settings in the ML audio menu?

In any case, you can always duplicate it to the right channel during the editing stage.

[Justin Williamson]

My whitebalence is stuck in Auto with latest release.

[Milan Kajnar]

Hi Alex...

Last build is really bad for White Balance. If I am using previous
autoexec.bin it works normal. But after taking picture in liveview my
camera crashed. Last picture is on LCD and camera is frozen. Please
make new build and distribute all the time whole archive of ML in one
file. Distributing autoexec.bin separately is not good... Thank you.
Milan

2011/6/11, Justin Williamson <justi...@gmail.com>:

> --
> http://magiclantern.wikia.com/
>
> To post to this group, send email to ml-d...@googlegroups.com
> To unsubscribe from this group, send email to
> ml-devel+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/ml-devel?hl=en
>

--
Milan Kajnar, dipl. technik
Gordic(c)Reseller - ASI Informační technologie s.r.o., 1. máje 3, 789 85
Mohelnice
tel.: +420 583 430 311, e-mail: milan_...@gordic.cz, milan....@asi.cz
www: http://www.gordic.cz

[JaKob]

milan... most anything thats not in a zip file with a date is pure testing autoexec.bin file... 

- Jakob

[Milan Kajnar]

I know, of course :-). I am using version from 25.5.2011 (+- 1 day) now...

2011/6/13 JaKob <jako...@gmail.com>

Gordic©Reseller - ASI Informační technologie s.r.o., 1. máje 3, 789 85 Mohelnice

[Justin Williamson]

Yes last 2 releases are very unstable. found myself removing the
battery all the time on my last shoot.

On Jun 13, 9:31 am, Milan Kajnar <milan.kaj...@asi.cz> wrote:
> I know, of course :-). I am using version from 25.5.2011 (+- 1 day) now...
>

> 2011/6/13 JaKob <jakob...@gmail.com>

>
>
>
> > milan... most anything thats not in a zip file with a date is pure testing
> > autoexec.bin file...
>
> > - Jakob
>

> > On Mon, Jun 13, 2011 at 6:31 AM, Milan Kajnar <milan.kaj...@asi.cz> wrote:
>
> >> Hi Alex...
>
> >> Last build is really bad for White Balance. If I am using previous
> >> autoexec.bin it works normal. But after taking picture in liveview my
> >> camera crashed. Last picture is on LCD and camera is frozen. Please
> >> make new build and distribute all the time whole archive of ML in one
> >> file. Distributing autoexec.bin separately is not good... Thank you.
> >> Milan
>

> >> 2011/6/11, Justin Williamson <justindu...@gmail.com>:

> >> > My whitebalence is stuck in Auto with latest release.
>
> >> > On Jun 11, 12:56 pm, Malcolm Debono <mdebon...@gmail.com> wrote:
> >> >> Are you sure the mic is stereo? Have you checked the source settings in
> >> >> the
> >> >> ML audio menu?
>
> >> >> In any case, you can always duplicate it to the right channel during
> >> the
> >> >> editing stage.
>
> >> > --
> >> >http://magiclantern.wikia.com/
>
> >> > To post to this group, send email to ml-d...@googlegroups.com
> >> > To unsubscribe from this group, send email to
> >> > ml-devel+u...@googlegroups.com
> >> > For more options, visit this group at
> >> >http://groups.google.com/group/ml-devel?hl=en
>
> >> --
> >> Milan Kajnar, dipl. technik
> >> Gordic(c)Reseller - ASI Informační technologie s.r.o., 1. máje 3, 789 85
> >> Mohelnice

> >> tel.: +420 583 430 311, e-mail: milan_kaj...@gordic.cz,
> >> milan.kaj...@asi.cz

> >> www:http://www.gordic.cz
>
> >> --
> >>http://magiclantern.wikia.com/
>
> >> To post to this group, send email to ml-d...@googlegroups.com
> >> To unsubscribe from this group, send email to
> >> ml-devel+u...@googlegroups.com
> >> For more options, visit this group at
> >>http://groups.google.com/group/ml-devel?hl=en
>
> >  --
> >http://magiclantern.wikia.com/
>
> > To post to this group, send email to ml-d...@googlegroups.com
> > To unsubscribe from this group, send email to
> > ml-devel+u...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/ml-devel?hl=en
>
> --
> Milan Kajnar, dipl. technik

> Gordic(c)Reseller - ASI Informační technologie s.r.o., 1. máje 3, 789 85
> Mohelnice

> tel.: +420 583 430 311, e-mail: milan_kaj...@gordic.cz, milan.kaj...@asi.cz
> www:http://www.gordic.cz

[mohan manu]

Hi,
Is there any cropmarks for working in SD PAL format? 720x576 resolution? I am recording in 1920x1080 and downsizing it to SD in Post.

[heartbeat]

i have a new bug maybe

i can not turn the display off while the intervalometer runs in
silent picture mode (full hd)

display shut down and awake after some seconds by the next picture

[heartbeat]

and a bug again if i delet some picture from card, after the the cam
crashes and say no communication with the card

[Alex]

I've never noticed this kind of behavior, can you format your card,
check if it happens without ML, and then tell me how to reproduce it?

[heartbeat]

i have formated my card and now the behavior is away but the problem
with turn display off is always reality

[Alex]

I can't reproduce this problem.

In LV mode, the display will turn back on if you cover the LCD sensor.

[konarix]

Hi.

And What about kelvin white balance - it displays only autowb?

Best Regards.

[David Edward Therault]

I too am running magiclantern-2011Jun07.550d.fw109.alex (the second fixed version) and am not able to take stills without having to remove the battery after a varying number of shots.

I reformatted my cards before this installation.

Symptoms are that the shutter release button becomes unresponsive. After a slight delay it sounds like it is cycling through a very slow shutter release before the mirror drops. Then the camera freezes and the battery must be removed. I have had this experience with three cards.

Another thing I have noticed is that ML may "unboot" after having booted with it, so that all of a sudden I am running without it.

Also force live view always is not working.

Here is what the order of malfunction seems to be.

1) ML "unboots" and the T2i picture counter is blinking.
2) shutter button becomes unresponsive
3) subsequent attempt to press the shutter button results in nothing but the mirror finally drops.

Oh, and yes, sometimes black LCD for no reason, but this is during a hang.

I also sometimes get a hang upon switching between AF and MF.

Lastly, this is all only during LV.

These are just some casual observations. I wish I had more to offer.

Thanks. -Dave

[heartbeat]

hi alex,

here is a little video from the bug i report to you last days before
the first part of the video is about a problem by movie recording,
there is always the text busy but the film records and the seconde
part is about the turn off display problem bei silent picture mode in
full hd with intervalometer

http://www.youtube.com/watch?v=dU_eWUnz-io

[Dremelv21]

On Jun 13, 7:16 pm, mohan manu <mohan...@gmail.com> wrote:
> Ciao,* C'è qualche cropmarks per il lavoro in formato SD PAL?720x576 di risoluzione?Isto registrando in 1920x1080 e ridimensionamento a SD in post.
>
> *
should see it in my collection of cropmarks cinemahistory ... is
called Film4-3
http://www.montipramafilms.com/cropmks_cinemahistory.rar

[konarix]

Hi.

I've got weeding shooting at saturday, so can You tell me which
version of ML is most stable for now?
I use 12May version, but it also likes crash.

Best Regards.
MK.

[Dremelv21]

I use this version:
http://www.montipramafilms.com/17-5-2011-magiclantern-550d.fw109.alex.zip

I feel good, does not have many bugs, it is good for an evening of
shooting!

Have good day!

Mirko Zaru

On Jun 16, 8:52 pm, konarix <marcin.konop...@gmail.com> wrote:

> Ciao.
>
> Ho le riprese diserbo a sabato, così mi puoi dire cheversione di ML è più stabile per ora?Io uso la versione 12May, ma piace anche crash.
>
> I migliori saluti.MK.
>

[heartbeat]

THANKS FOR ML @ ALEX and devs


when we get a new stable version?

best regards

[Alex]

> when we get a new stable version?

When I'll kill the bugs :)

The version from the repo fixes slow startup issues and some crashes
in photo mode, but sometimes freezes in LiveView (all buttons stop
responding).

[Shawn Wytch]

so alex whats the most stable version? i just got a class 10 card and seems like i cant record at the same qscale i use to with the class 6. I have updated to the newest build, do you know what the most stable copy is?

--
Email me at too...@gmail.com 
Or call me at 316.312.5584 ask for Shawn

[Alex]

QScale has *nothing* to do with stability, and you should *not* use it
if you don't understand how it works (hint: *variable* bitrate!).
Should I remove it from the menu?

I'm always using the bleeding edge on my camera :)

[Gmail-Work]

NO

Tks\

M.C

Matias Ceppi

mobile (54 9 11) 6174-7461

www.finishfilms.com

http://web.me.com/mceppi/M.C/HOME.html

[Eric Rujiraviriyapinyo]

on the June 7th build and have noticed that in Manual mode if I set AUTO ISO with the ISO button on my camera or in ML (not pressing Q, just cycling the iso until it reads AUTO). ML does not take bracketed exposures, just multiple shots at one exposure. (Aperture mode works as expected ). but if i change the ISO to anything other than AUTO it then works again in Manual Mode. Not sure if this was working in previous builds, because i just noticed it.

[Shawn Wytch]

those were two different things there. i was also wondering why my class 6 can use qscale 12 but my class 10 can only run on qscale 10

[Shawn Wytch]

i shoot almost 7 hours a day sometimes 12 hours i bet i use it more then alot of people here.

[Malcolm Debono]

I don't know if it worked or not in previous builds, but from the way I see it I think that's the logical way it works (even though it is incorrect). Remember that bracketing takes overexposed and underexposed shots. While ML tries to take these shots, the camera compensates the ISO automatically to get a well-exposed image, thus making all shots exposed equally. 

[Alex]

Actually, in manual mode, ML performs shutter bracketing, which
explains this behavior.

You could consider it a feature (i.e. when you are not sure if you
want high iso / fast shutter, or low iso / long exposure).

Technical: PROP_AE in manual exposure modes is read-only (even with
ISO Auto); in other modes (Tv,Av,P) it's writeable.

[Alexander Kondratskiy]

Hi Alex,

I decided to start looking into the code again, to fool around with
the intervalometer for timelapses, however, I am unsure which branch
to use. In your first post in this thread you point to hudson's main
branch on bitbucket, but it's missing the 550d stubs. Your 550D branch
on the other hand hasn't been updated in 2 months. Are there extra
things needed to make the main branch work on the 550d besides the
stubs?

Thanks!

[Alex]

The link in the first post of this thread is to "550d" branch, not to
"default" branch.

The very latest code is the "unified" branch (which will become a
single source tree for all supported cameras). You may start with any
of them ("unified" or "550d").

[Alexander Kondratskiy]

Thanks for the very quick reply Alex.

Sorry, my fault, I think I checked out the "default" branch of
hudson's repository, hence my confusion.

Thanks again,

Alexander.