Question about the x86_64 branch!

[lloydbayley]

Quick question for @Nachtzuster : Is the x86_64 branch being actively maintained (as far as you can manage, I know you're just tidying things up) along with the main branch? If so, I'd like to update my VM to that branch. However, the install files are still reflecting the main branch in that x86_64 branch. I could update it but it would be overwritten in the next update. I understand that it may stay static after this but was wondering if it could be used live yet?

[Nachtzuster]

I'm using that x86_64 branch for development of other actual 'feature' branches: so I rebase it onto main whenever I need it for testing. (way quicker and easier than messing with sd cards an RPi's 😉) Using it for 'production' is therefore not advised.
Merging to main would ease my workflow, but reasons for not merging with to main are

• Fonts look funny in View Log and Web Terminal due to the updated gotty - not sure how to fix this.
• I don't want to advertise x86_64 support - feels like opening Pandora's box (could mark it experimental maybe)

[lloydbayley]

Completely understood! Just thought I'd ask.
That's weird about the fonts. Gotty is a bit of a pain when it does things like that. It doesn't like change! :)
We don't want to release all the horrible things in the world from Pandora's Box!!!

[lloydbayley]

@Nachtzuster Just FYI, I have installed a test instance of your x86_64 branch (with a small branch-pointer modification) and it went in first time to a ProxMox debian bookworm VM without issue. Also, the Web Terminal and logs show up fine. It's only a play install but just thought the results might be interesting for you!

[Nachtzuster]

Thank for the confirmation!
Couple of questions:
Does gotty look ok on that install? (screenshot?)
Which browser are you using?

[lloydbayley]

Sorry, yes that's what I meant when I said that the Web Terminal and Logs looked fine. I remembered what you said about gotty and I tried it on Firefox, Chrome & Safari. All working fine. Will take screenshots in a min.

[lloydbayley]

Ok. Screenshots:

Chrome:

Safari:

Firefox:

[Nachtzuster]

That does look fine indeed. - I wonder why it looks so horrible in my Firefox on Ubuntu

(Chromium and mobile Firefox look fine here)

[lloydbayley]

I've no idea...I mean the screenshot looks readable albeit with some extra vertical space but it's a little 'jagged' as you point out. Could it be the font cache in your end needs refreshing?

[Nachtzuster]

There is something wrong with your install though: I'm seeing NaN 'not a number' in your logs. the analysis is deeply unhappy :-)

[lloydbayley]

Yes, it's just a test install, there is no mic connected at this time, thus the NaN....I just flashed the VM up to get you the screenshots!

[Nachtzuster]

I decided to merge the x86_64 branch as it does simplify my workflow.

The font issue will only affect a tiny percentage of users, I think, especially as I'm keeping the aarch64 version on the old version.

[kniftar]

Well I could certainty be wrong about that I'm not super literate about this stuff. I didn't know there WAS a x86_64 runtime. On your readme under Introduction is says [[using [pre-built TFLite binaries]](https://github.com/PINTO0309/TensorflowLite-bin)
When I goto that link it only talks about arm and raspberry pi's. Didn't see any x86_64 version mentioned so that's why I thought the tflite binary was for arm. When I installed tensorflow it looked like it compiled for my hardware and then worked.
My install is not on a VM, it's on an HP-T620 thin client with an AMD G-Series GX-217GA SOC: dual-core APU
1.65GHz.

[kniftar]

Interesting... not sure why that would be without install and/or runtime logs though

Here's my install log if it could help

[Nachtzuster]

Thanks!
Looks like the installer did the right thing and pulled the x86_64 version of TFLite. The rest also looks as expected, so all good here.
(Maybe remove the log now for your privacy)

Maybe the runtime log could still remove some of the mystery? If the logs are still on that machine: journalctl -u birdnet_analysis.service and scroll to the relevant date/time.

[kniftar]

Ok, here's the relevant runtime log snip:
analysis.log
Looks like it couldn't find the module then after I installed tenserflow and rebooted it starts working. Maybe something ro do with the AMD processor?

[Nachtzuster]

Thanks.
Weird that it says it can't find the module. I was expecting something like
The TensorFlow library was compiled to use AVX2 instructions, but these aren't available on your machine. Aborted That is what I get on an emulated SandyBridge machine.

Anyway I guess the takeaway is that the TFLite build this repo uses needs at least a Haswell (AVX2)

[lloydbayley]

Well, today I migrated my live install on a Proxmox VM to your (main) repo and all is working as it should. Just reporting in! :)