Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - thebishop

Pages: [1] 2
1
Chronos User Discussion / Re: Adapting other lenses to C-mount
« on: November 17, 2017, 02:00:21 PM »
Hi Martin,

Just fyi i went with a fotodiox EF adapter and the
Samyang 14mm T3,1 ED AS IF UMC II VDSLR lenses - works great and is a “normal” focal length.

Cheers,

Joakim

2
Chronos User Discussion / Re: Let's talk lighting
« on: November 10, 2017, 05:44:19 AM »
Feedback on the godox: no flicker at 9k FPS at least, so looks good so far!

3
Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 14, 2017, 08:35:45 AM »
I loved velocity control with my original iPod's, but the prerequisite is a control wheel that allow fine motor control (like the oversize iPod jog wheel) - not sure it would translate that well to the small knob on the Chronos, but worth trying out too...

4
Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 13, 2017, 05:39:37 AM »
I think it'll not be very pratical to select a value from a menu each time you want to switch it, I much prefer to set the values once and be able to switch between them with just a click.

Fair enough! Then I would suggest the following based on all the above:

Clicking the jogwheel will switch between the following speed settings:

- Single-step
- Slow
- Normal
- Fast

The textual representation of the currently selected speed would be displayed somewhere on screen during playback such that one gets feedback on what the current setting is when pressing the button.

The % settings for each such mode would have a reasonable set of defaults based on testing, but could optionally be fine-tuned in the camera settings somewhere if one wants to have more fine-control over those speeds.

Having those textual representations will make more sense to the average user, while still being able to be fine-tuned in camera settings if desired (to whatever granularity needed).

5
Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 13, 2017, 01:21:46 AM »
Pushing and holding the jogwheel opens up a window on screen, allowing you to select from a number of frames-per-detent selections. Rotate the jogwheel to select one you want, then release the jogwheel and that speed is applied. Turning (not pressed) now goes at the speed you selected. This speed selection menu would also be duplicated in the Util menu somewhere. I like having shortcuts to frequently used things like this, because you're often changing the jogwheel rate several times when reviewing or saving a shot.

Question is, what rates are appropriate, without having too many? I was thinking of something like 1, 2, 4, 16, 64 frames per dentet, and maybe some that are a fraction of the buffer length like NoDak suggested, as the small numbers may not be appropriate when you're saving hundreds of thousands of frames at low resolution. Perhaps from 1/1024 of the buffer down to 1/32 of the buffer per detent.

I think the press-to-hold-select speed you suggest would be even easier if just using "push to open", "Push to close" the settings window, then you don't need the dexterity to actually press-hold-rotate at the same time. As the currently selected "speed" would be pre-selected when pressing, you can always get rid of the settings easily by just pressing a second time if doing it by mistake.

But thinking about it, with the possible exception of single-frame stepping, wouldn't one always want to use a fraction of the buffer length (%) as the speed selection?

For e.g. a total of 5 choices: 1 (fixed), 0.1%, 0.25%, 1%, 2.5%

Then you know for e.g the 2.5% settings, 40 detent clicks will always be the full current range moved?

It would be slightly simpler but always consistent behaviour then. The actual % above probably are good, but real-world experience needed to nail them down - and see if perhaps even just three values would cover the needed use cases, then you could have the even more user friendly:

Jog wheel speed setting
+++++++++++++++
Single-step
Slow
Normal
Fast

(and fine-tune what those settings means so it 'feels' good)

6
Chronos User Discussion / Re: Recommended Lens brands...etc....
« on: October 11, 2017, 12:52:49 PM »
I just tried shooting with a canon EF 50mm 1.4 prime - looked quite good at initial glance! But with 3.9x crop, it is quite the telephoto. Have ordered a 14mm Samyang lens with canon EF mount too, that corresponds to 55mm which should be quite useful focal length...

7
Chronos User Discussion / Re: Chronos 1.4 Footage Thread
« on: October 11, 2017, 09:57:30 AM »
I finally have a way to quickly aim and follow targets using a $40 Amazon gun sight, now I just need to find a way to quickly pull focus.

All the clips were shot with a 400mm lens (effective 1560mm) at ~f8-f11 and 6db gain on the camera.

https://youtu.be/JyLn4jDvqTU

https://www.bhphotovideo.com/c/product/1049634-REG/focusshifter_eng_fs02_set_follow_focus_for_dslr.html with appropriate lenses/adapted?

8
Chronos User Discussion / Re: F-stop when using lenses from 35 mm camera
« on: October 07, 2017, 10:31:06 AM »
Effective focal length will change, for example Chronos is about a 4:1 crop factor from 35mm, so a 28mm lens on Chronos would be like a 112mm lens on 35mm.

Wouldn’t that be the other way around, a 28mm on a full frame camera would be 112mm on the cropped sensor of the Chronos?


9
Software Dev / Re: Suggestion: Reverse direction of buffer bar
« on: October 02, 2017, 12:20:49 PM »
One more vote for left-right or to reverse the current one.

I thought there was a bug when my in/out points always were reset to the same value, but I just had misunderstood the direction of scrolling.

For a westerner used to left-right, top-bottom temporal direction it was non-intuitive.


10
Chronos User Discussion / Re: Let's talk lighting
« on: September 29, 2017, 06:10:03 AM »
Initial feedback from actually shooting with the Godox 200 (x3) now - there seems to be no discernible flicker when shooting at 8K fps, so I think it looks as a good alternative. Haven't done more than initial "let's plug everything together and get some random test video done", but have hopes it will work ok also for my final intended use case.

Looks promising!

11
Chronos User Discussion / Re: List of good (and bad) SD cards
« on: September 29, 2017, 06:07:42 AM »
One more good card:

https://www.kingston.com/en/flash/sd_cards/sda3

I used a 256 GB variant formatted as FAT32 on macOS as outlined at http://forum.krontech.ca/index.php?topic=34.msg568#msg568

It seems to work just fine!

12
Chronos User Discussion / Re: SDXC Card
« on: September 26, 2017, 04:32:41 AM »
For anyone having trouble with large size SDXC (e.g. 128GB) on macOS, I succeeded using the tips from the following article:

https://www.michaelcrump.net/the-magical-command-to-get-sdcard-formatted-for-fat32/

The normal Disk Utility failed to format FAT32, even if it allowed me to try.

I haven't tried it with the camera yet (have not received delivery), but it looks like it works alright.

Code: [Select]
solid:~ jocke$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         500.1 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.1 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            337.3 GB   disk1s1
   2:                APFS Volume Preboot                 19.4 MB    disk1s2
   3:                APFS Volume Recovery                520.0 MB   disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4

/dev/disk2 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +3.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Time Machine Backups    3.0 TB     disk2s2

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *256.5 GB   disk3
   1:                 DOS_FAT_32                         256.5 GB   disk3s1

solid:~ jocke$ sudo diskutil eraseDisk FAT32 CHRONOS MBRFormat /dev/disk3
Password:
Started erase on disk3
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk3s1 as MS-DOS (FAT32) with name CHRONOS
512 bytes per physical sector
/dev/rdisk3s1: 500867584 sectors in 7826056 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=2 drv=0x80 bsec=500989950 bspf=61142 rdcl=2 infs=1 bkbs=6
Mounting disk
Finished erase on disk3
solid:~ jocke$

13
Chronos User Discussion / Re: Let's talk lighting
« on: September 21, 2017, 12:27:56 PM »
It is kind of funny, I looked around and retrieved my old light meter (Minolta Auto Meter V F) - can actually be useful again :-)

14
General high-speed discussion / Re: Measuring Speed
« on: September 20, 2017, 12:12:09 AM »
https://www.amazon.com/Stripe-Black-White-Fabric-Yard/dp/B00QFHHK32/ref=pd_sbs_201_3?_encoding=UTF8&psc=1&refRID=80BQSVXYM05QWKWJXACC ?

 :)

That might be crazy enough to work.  I could cut off some of the black strips and make 1-foot segments to put below the 1-inch segments.  I wonder how accurate their 1" strips are...not that any of this is going to be super-precise anyway.

The important thing is that the striping is uniform, then you can simply adjust by measuring the exact width.

Pages: [1] 2