Menu

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.

Show posts Menu

Messages - canoneer

#1
Thank you all, I will do some more research.
#2
I have done this search  :-[ - the use case depend on reacting on non- visable infrared thermal frequence appearence, which I hope to get filters for if converting the EOS camera. Normal commercial triggers are for visable light.
#3
Could you point me to such, please?
#4
Another critical requirement is that it should allow a 24/7 setup - without overheating or going asleep. Probably not very frequent clips.
#5
I thought it needed some work from my own testing some years back. The length of the clip should ideally be possible to set from options but probably not critical. A question is also which EOS - ideally 4k - but clips not longer than 5-15 seconds should give some alternatives.
#6
I think it might work, but to my knowledge it triggers an image- not video. Or am I wrong?
#7
The use case discussed is to trigger and video appearence and movement of what can be called lightning or energy «bulbs» in the sky - day or night.
#8
Hi all. I am a ML user (not developer) - back in time on 60D - with Crop Mood on Ms and 700D today.

A discussion I have been in is about triggering video capture for a certain length - with adjustable trigger-light/ temperature change - thought to be used on a infrared converted EOS camera.

Been searching historic topics - and there are some about triggering for lightning back in time - a function I have previously used for both lightning and bird photos then on the 60D.

This use case is kind of the same but for video and triggered by changes in different infrared frequency light levels - helped by filters. Is there a direction in the ML history or development that could help in this?
#9
Quote from: theBilalFakhouri on May 05, 2023, 05:32:59 PM
@canoneer

For SD write drops, make low level format in camera also set "Small hacks" to "All" from RAW video submenu to maximize write speed. Make sure the OC at 240 MHz.

For shutter issue in ML menu, there are two builds for 700D:



If the one without "Shutter" produce the shutter issue, try the version with "Shutter" (vice versa).

Thank you very much. It was a combination of the shutter issue - did not catch that before you told me - and the SD drop, possibly also me testing an avalanche of cards in pure frustration. Now it looks very promising - first UHD take green 23 seconds, 72.4MB/s 14% idle.

Happy camper.
#10
Quote from: canoneer on May 05, 2023, 12:55:12 PM
After this I tried the off- on-video  on the mode wheel --I have on 700D used the Video position. Tried the On position, and it seems the shutter line is available....witll test more in this position now. Coming from the M it is required to be in the Video position.

I am able to prepare all until going back from 240Mhz to set Raw video - under the On position - that menu page is greyed out without data. restarting and going to the Video position, I can set all except the shutter speed.- and I am not getting normal record times.

I find this pretty difficult. Going back to my M until a diagnose of what I should do.....
#11
Quote from: canoneer on May 05, 2023, 12:46:55 PM
Quote from: canoneer on May 04, 2023, 03:36:30 PM
(Crop Mood 700D issue - card speed or something else)

After another uninstall of ML Cr.M............
Shutter       N/A, -191       TV10.0
This is in fresh installed and virgan startup window.

It is not possible to change this line at all, at start up or later.

After this I tried the off- on-video  on the mode wheel --I have on 700D used the Video position. Tried the On position, and it seems the shutter line is available....witll test more in this position now. Coming from the M it is required to be in the Video position.
#12
Quote from: canoneer on May 04, 2023, 03:36:30 PM
(Crop Mood 700D issue - card speed or something else)

After another uninstall of ML Cr.M., I refomatted card in camera, copied Ml files from Bilals original, installed ML Cr.M. on camera and restarted it - the following is then shown on shutter line when opening ML.

Shutter       N/A, -191       TV10.0

This is in fresh installed and virgan startup window.

It is not possible to change this line at all, at start up or later.




#13
(Crop Mood 700D issue - card speed or something else)

Bilal - I think your highly apreacheated help is needed.

I have a setup on one of my M´s - working fine and my preferred UHD 1x3 crop runs green and without stopping. When setting up my recently acquired 700D I have really tried to follow your video the same way I did for the M, with all the settings.
I have tried cards working fine on my M with 240MHz, but on 700D I get impossibly low record times, and speed. Newly bought card samme issue. Changed MHz several times.
I have run benchmark on them and the speed vary from 20 to 70 MB/s - on same card - and seem to be inherited between tests.
The only visible problem in the setting is the un-accessable shutterspeed - set to 353-354 degrees 1/25-1/26. Not possible to change, only the referred Tvx.x number - unknown phrase to me. I have re-downloaded, re-formatted and re-installed ML. Please check attached video if you have some time available. Thank you. (I hope access is working) https://vimeo.com/823731441?share=copy

I also have a few crash logs and images - https://www.dropbox.com/sh/mj0b74r7d0049ir/AAADZ1_ke9UCDrsMv51J7_sBa?dl=0

It seems I am alone with the problem - so I guess it is me or my camera, but hope for some help.
#14
Hi all. Been advised to build a local test - and have follow Dannes simple route for Mac on 1st page.

Though being lost in Mac-details I managed to compile - but I do not know where to pick up the result from the compile nor what next step should be - a successful compile do not help much without getting next step done I guess (42 years since programming was my job for a short while).
#15
Hi MlvApp contributors.
Getting h265 playback from MlvApp export on IOS is probably beneficial to many including me. Masc4ii made the minor change required to open that, and it would be appreciated if a new "1.121" could be built including this....?
#16
re  #4600

After numerous approaches I managed to get my long forgotten RC-6 to function for both video (channel#2) and photo. Thanks for your effort Walter Schulz!
#17
I restarted, reconnected mike and I then managed to trigger in photo mode, but not in video.
#18
Tried without troggertrap, with and without external microphone. No xx response in photo or video. It do detect external micrphone - I had to try that as well since I could not make sound load enough with camera mike.
#19
I have one M with nightly 11 august - triggertrap-tested with xx volume meter showing 8, 10, 20, 35 with no trigger response - microphone test same. Different M nightly 19 september - tested same way - no response.
#20
Yes, I see the «Audio release on» message on my display.
#21
Quote from: canoneer on October 15, 2020, 06:09:04 PM
Re Remote triggering the EOS M. I have way back in time managed to get the Triggertrap Audio remote function to work. Now I can see the volume peek when triggering on the iPhone but it seems impossible to get a reaction. Do I need to do more than activating the function in the ML menu? If you have time to throw a lifeline?

Hope you are all well and enjoy more tech fun during local close down periods.

I have a little EosM rig where I would benefit a lot from using a remote trigger.  So any help to get it running would be great.
#22
Re Remote triggering the EOS M. I have way back in time managed to get the Triggertrap Audio remote function to work. Now I can see the volume peek when triggering on the iPhone but it seems impossible to get a reaction. Do I need to do more than activating the function in the ML menu? If you have time to throw a lifeline?
#23
ref to earlier post:

........ The assert file reported about mlv lite packaging (deleted it as I tried to release space (silly me)). ..........

(nightly 13 jan eos m 202.)

Clip - only audio played by mlvapp.

The assert files hold versions of this text when generated to the card for my issue:

ML ASSERT:
0
at mlv_lite.c:2751 (compress_task), task compress_task
lv:1 mode:3

compress_task stack: 1de948 [1de9d8-1dd9d8]
0x0009EC24 @ be6338:1de978
0x0009E564 @ 9ec80:1de948

Magic Lantern version : Nightly.2020Jan13.EOSM202
Mercurial changeset   : bdda3ceefa0c+ (crop_rec_4k_mlv_snd_raw_only) tip
Built on 2020-01-13 17:08:33 UTC by Windows@ALPHA.
Free Memory  : 232K + 2610K

I am clueless to if this is due to my handling - the lighting conditions, lens (18-55), card (64gb SanDisk extreme pro), or settings(raw, 1736x976, 5 sec clip, 25fps, focal 42mm, 1/50s, 180 deg, f9.9 iso100, 14bit lossless, audio 2ch,48kkhz)

Next clips normal take and play so I am not having a stable problem. But on my other card -same build - 32gb same type - I have had reported available disk space 36gb on 32gb card - and full card when 7gb available - after same assert reports.

#24
Quote from: canoneer on May 02, 2020, 07:13:24 PM
Thanks. Will do. I have another SD card set up and use that at the moment. Experienced a pink artefact in the raw files I produced for test today. If I am able to include an image I will. I seem not able to edit it away in Resolve after converting to DNG or in MLVapp prior to.

https://www.dropbox.com/s/0d5mgub0se5ow57/Untitled_1.1.1.jpg?dl=0

#25
Thanks. Will do. I have another SD card set up and use that at the moment. Experienced a pink artefact in the raw files I produced for test today. If I am able to include an image I will. I seem not able to edit it away in Resolve after converting to DNG or in MLVapp prior to.