#timvideos

xfxf: new problem - if we use firewire, how do we get audio?

CarlFK: the same way, ALSA?

I just showed deeprave my ... alsa mux client stuff, he is going to try to add that to your fw script

it won't be hard to change

there's two ways to do it

actually i'm pretty sure i can make what needs to happen

i'll do it now and commit up

i obv can't test tho

i can though

Title: video-scripts/ryan/lca/other/firewire-capture at master · xfxf/video-scripts · GitHub (at github.com)

haven't tested them but they should be a start

also in tim's directly he had a version of the alsa only script that tee'd off the audio and pushed it into a video generator which showed a waveform

it's probably a good idea if not too computationally expensive

(obviously watch CPU with all of this too, should never exceed 80% - DV on the i5's for me was eating up a lot, i couldn't run voctocore/voctomix/DV on the same i5...)

s/directly/directory/

if the scripts don't make sense, ask Tim to show you what he showed me a few nights ago, that plus playing with a few pipelines and i now kinda grok how it all works

xfxf: why?

why wht

what*

why write video generator which showed a waveform

it's not required, but it's just a nice to have tim added

i believe the logic is to show the source has audio visually

but the VU meter also achieves that

I don't see that being used.

if doing this seperate ALSA thing i'd suggest putting the ALSA source first anyway, like we did with dvswitch, so it's the default one chosen

a step of 'select the audio source' is another thing volunteers will forget

CarlFK: you'll observe i didn't add it to my script, i dunno why you're arguing that with me :)

that would be 3 streams over cat5.

not at all

you run that on the voctocore/mix machine...

well, ok. still not sure why

i'm happy if it's muxed in with the DV source, all i'm giving you guys are options for testing

"if the scripts don't make sense, ask Tim..." <- that is direction to do something. not "if you are bored and run out of things to do.. bother tim so he stops doing what he is doing."

so stop that

why are you being argumentative, i'm not doing anything that opposes you

if you don't want my scripts, shrug, fine - i'm attempting to help. please be positive

yes you are

tumbleweed says 682Mbs is coming into the core from 2 clients

xfxf: what is your work address?

_florent_: ping me when you get up / ready to work

CarlFK: /etc/openntpd/ntpd.conf

CarlFK: content: server $NAME (repeat times n)

uhh

these have isc dhcp

err ntp

_florent_: Ping?

_florent_: I could use a second pair of eyes on this. This is the core to a frequency counter w/ FIFO storage. Before I try hooking it up to the CSR bus, do you see anything egregious? https://gist.github.com/cr1901/7dd73f989bada9c0...

Title: Migen Frequency Counter · GitHub (at gist.github.com)

mithro/cr1901_modern: pong

morning _florent_

evening :)

ok, so what are the news?

_florent_: I fixed the ROM problem

_florent_: and the version info problem

_florent_: It appears that the HV30 you have is in NTSC mode, while everything here is in PAL mode

_florent_: I switched my HV30 (also tested HV20) to NTSC mode and then got this ->

_florent_: https://goo.gl/photos/icLZAX5t7CnN12GD9

are you testing with both Opsis and Atlys? or just Opsis?

_florent_: mainly Opsis, just about to try with an Atlys board

because I don't understand why there are some differences between Opsis and Atlys boards with some camera

_florent_: Hi. I'm here. Just wanted a second pair of eyes on my freq counter. Although it seems the problem is solved :O?

cr1901_modern: yes I'm looking at the code

why are you using a fifo?

here is something I use on another design:

Title: [Python] class FrequencyMeasurement(Module, AutoCSR): def __init__(self, pulse): - Pastebin.com (at pastebin.com)

_florent_: with the version info being incorrect, it was hard to understand what firmware versions the Atlys/Opsis are using

ok

_florent_: I'm still trying to get an Atlys onto the exact same firmware we have been testing the Opsis with

_florent_: should have it working in the next 10-15 minutes

ok

I'm just trying to understand why we have different behaviour

_florent_: Yes, so am I :)

so for the HV30, you are going to use it in PAL right?

_florent_: That is the current plan, but its open to discussion

_florent_: It is easy to switch back and forth between the two versions now I've figured out how

_florent_: The idea w/ a FIFO was to be able to take a sliding average every so often w/o needing to use the CPU to move data to main memory

ok, but we have to use very little ressource for that since we already have problem getting P&R done

Very well, I'll get rid of it

it's probably better to just have a register where the cpu can take actual frequency from time to time

_florent_: would it free up resources to punt the firmware rom onto the SPI flash

_florent_: I'd like to know if the frequency duty cycle isn't even too

Well, we need multiple freq counters, so we need multiple registers

mithro: yes, but that would only save blockrams

what do you mean by : "the frequency duty cycle isn't even too"?

cr1901_modern: yes of course, one frequency counter for each measure we want to do

_florent_: if the positive period is longer or shorter then the negative period

I forget exactly how to do this, but I seem to recall that old Migen has a BankArray class for combining very similar registers into a single module on the CSR bus?

you can just create registers with CSR/CSRStorage/CSRStatus

I'll need to make my own test signals since minispartan HDMI isn't ready yet

mithro: Where should I put the freq counter module? I was thinking under gateware/hdmi_in/analysis?

I can try to synthesize HDMI2USB on the minispartan as well, so I can test w/ real signals. Right now, all I can do is get to the MiSoC BIOS b/c I haven't figured out how to use flterm.py yet

_florent_: Your version of the freq counter gets the period. Is that gonna work w/ signals as fast as HDMI?

My version gets the frequency (divided by a constant factor)

i think it's enough to get a period, since the cpu is aware of the frequency it saves ressources letting the cpu computing the frequency

but you can keep your version

we'll do something simpler only if needed

_florent_: I'd really like to improve the debugging information we get from the firmware so we can better understand what the differences going on here are

I don't actually know which way is better lol. I do need to reiterate: I cannot actually test the freq counters w/ HDMI2USB. What I can do is synthesize signals from a separate FPGA of known freqs, and test via the MiSoC BIOS (which hopefully will be out of phase as well as not the same freq)

bblr - getting dinner

_florent_: One last req for advice when you have a minute?

back

_florent_: any idea why the Atlys board has a much harder time then the Opsis with routing?

hmm difficult to say, higher system frequency & different DDR controller

_florent_: any reason to not drop the system frequency so the Atlys and Opsis are the same?

we could do this now yes since the jpeg encoder is not working asynchronously

I've tried reconfiguring my HV30

but I don't have a mini-SD card here...

and when plugged to the computer is does nothing

when you are in NTSC, do you think we are running the same firmware (on the HV30)?

_florent_: You shouldn't need a mini-SD card

hmm at least when I do what you described in the issue, it does nothing

_florent_: Let me check the camera here

_florent_: you turned the dial on the top to the "play" mode and the little switch on the side to the "card" side, right?

yes

_florent_: so, what does the screen show?

_florent_: do you have a HV20 (silver) or HV30 (black)?

HV30

the screen shows NO SDCARD

and then a kind of menu with a sdcard blinking in red

the I plug it to my computer and nothing...

_florent_: testing now, give me a moment

ok

can you try without sdcard?

yes, I'm getting the same here

_florent_: apparently you do need a SD card :(

ok

but just to understand

when you are switching to NTSC

in camera mode i get hdmi out when connected to a monitor

you are using a custom firmware?

with no sd card

hi seaLne: thanks, same for me

but I wanted to update the firmware

ah, so that wasn't what you were wanting then? sorry

_florent_: so - I think the quickest thing is we debug with the NTSC mode

xfxf just confirmed the HV30 he sent you should have the same firmware as the one sitting in front me

hmm interesting

I realized that when I was doing my test, the little switch was in the tape position

when setting it to sdcard it seems the hdmi output is not the same

_florent_: that is the correct position for using the device

can you test with switch in tape position?

_florent_: yes

_florent_: can you check which mode the camera is in