#apertus IRC Channel Logs

It can load more than one frame now

I think now, I can go for sliders, if everything is alright more or less

update u soon

hi dev_, your version had problems on my machine and was not playing anything, only one frame was there and it was only partially correct, around 25%, have used M11-1526.VB.mlv as always

don't have time to check on it now, as i have to leave for work soon

off for now, will be back later

Can u see the logs of loading frames , extraction by downscaler , conversation from 14->16 bit , demosacing etc on terminal .

Also , i am using sample mlv from https://www.magiclantern.fm/forum/index.php?topic=11899.0

The version doesn't take account of frame rate yet , but i think it simply load frames (due to logs)

morning folks!

Hi BAndiT1983|away, when I debug the code , I found out that only last frame is rendering on screen

for different sample , it is giving different behavior like some times it crashes by giving segmentation fault

hi dev_, don't know what you mean, as the code is not that difficult

are you looping the frames at the end?

wondering about a lot of things in your code at the moment

why are you debayering in MLV loader and again in presenter?

also EnableRendering() was added to prevent crashes, when no data is present, you call it in every frame, please clean up the loop from such stuff, as it show me that you still have a lot to learn

I am clear till the processor debayer the frames , but then how each frame is displayed on screen

ehm?

https://github.com/kakashi-Of-Saringan/opencine/blob/dev/Source/ProcessingTest/Presenters/ProcessingPresenter.cpp

which methods are there in the presenter?

THis my local repo , In which i am trying to loop the process , each time i access a channel from allocator(line 72 , 76 , 79)) the processor debayer it and then setframe method shows it on screen (which fails)

until the loop ends

you are debayering in the loop again

I am changing the data of red, green , and blue each time

process in the presenter was done for one frame to show the pipeline, you have moved it to loader partially, so why is the code executing multiple times?

remove all the things from loop first, which do not belong there, i expect 4 lines: red channel, green channel, blue channel and SetFrame(), besides that everything else is not needed there

so it executes quickly and stops with last frame

aren't the images already stored somewhere? or what is the point in setting data over and over in the object?

and the prize question is, have you fixed OCImage? as it'S the main point why it's not working probably

what do you see in this file? -> https://github.com/kakashi-Of-Saringan/opencine/blob/new/Source/OCcore/Image/OCImage.cpp

format

besides the fact that no aspect ratio is present there

I mean height and width , sory

I have changed it by removing memmove , and other data allocations

i clearly see a problem there

no, next try

*destructor

but it's not the main problem

It is overriding the data already present in channel

OCImage has only few methods and 3 of them have a problem

really? then trust me, there is something really wrong

not*

let's say you call SetRedChannel(), what happens then?

Y_G, you there?

have you checked if smbus is really required?

It's preferred ,have'nt gone into the details of why

Did you get time to test the CMV config register ?

will test it now

is your ssh key there?

https://wiki.apertus.org/index.php/AXIOM_Beta_Remote_Access

Tunneling part has to be done from the local or the zbox ?

how to test the my local code on beta ?

git clone ...

i can also test something for you locally, as i have a sensorless beta here

do you have access to the zbox?

ok, currently trying to find out what the new credentials and names are

usually it was ssh root@beta, but new one should be something like ssh operator@beta, but it doesn't work at the moment

hm, i can see the webcam, but beta is not in the picture

Ahh,was trying with 'ssh root@beta' ,was stuck for almost 2 hours figuring out what was wrong :')

ok, will plan some time for it

hm, beta is there, but zbox doesn't have access

can't really say which camera this is, as we have 2 available, one with sensor and another without