~martijnbraam

The Netherlands

https://brixit.nl/

I do computer stuff

Trackers

~martijnbraam/turbocase

Last active 3 days ago

~martijnbraam/logbookd

Last active a month ago

~martijnbraam/numberstation

Last active 5 months ago

~martijnbraam/mixolydian

Last active 7 months ago

~martijnbraam/synapsectl

Last active 9 months ago

~martijnbraam/createaport

Last active 1 year, 2 months ago

~martijnbraam/struct

Last active 1 year, 4 months ago

~martijnbraam/OpenAtem

Last active 1 year, 4 months ago

~martijnbraam/certtool

Last active 1 year, 6 months ago

~martijnbraam/Megapixels

Last active 1 year, 6 months ago
View more

#3 KeyError: 'fp_circle' 2 days ago

Comment by ~martijnbraam on ~martijnbraam/turbocase

I've pushed version 1.4.2 now which should fix this.

#3 KeyError: 'fp_circle' 2 days ago

Comment by ~martijnbraam on ~martijnbraam/turbocase

Certainly the Dsub connector, I have a rather lazy way of loading the mountingholes now which is checking if the footprint name contains "MountingHole".

#3 KeyError: 'fp_circle' 3 days ago

Comment by ~martijnbraam on ~martijnbraam/turbocase

Hmm interesting. It looks like there's a mountinghole footprint on the board that does not have any circle graphics to grab the measurements of. Can you write down which footprint it is so I can add it to the tests?

#2 ModuleNotFoundError: No module named 'turbocase.parts' 3 days ago

Comment by ~martijnbraam on ~martijnbraam/turbocase

Ah yes, the parts submodule was not listed in setup.py, I've pushed the 1.4.1 release now to fix it.

REPORTED RESOLVED FIXED

#1 Index out of bounds when reading in PCB file 12 days ago

Comment by ~martijnbraam on ~martijnbraam/turbocase

Looks like it's an issue with parsing a connector footprint. Currently it grabs the graphics on the F.Fab layer to do that and the footprint you added the height to might not have anything on that layer.

Can you copy and paste that footprint into the issue here for reference? The footprint parser can probably be improved.

#6 Incorrect parsing of RFC 5424 messages with NULL time quality 3 months ago

Comment by ~martijnbraam on ~martijnbraam/logbookd

I've added a testcase for this now and the fix will be in the next release

REPORTED RESOLVED FIXED

#5 Segfault when feeding non-syslog-formatted data 3 months ago

~martijnbraam assigned ~martijnbraam to #5 on ~martijnbraam/logbookd

#4 Don't output ANSI color codes if the output is not a terminal 5 months ago

Ticket created by ~martijnbraam on ~martijnbraam/logbookd

#3 limit size of database in memory 5 months ago

Comment by ~martijnbraam on ~martijnbraam/logbookd

The issue with -r mode is that the on disk database is the exact same one as the one loaded in memory. So writing it out doesn't actually save memory.

That's the major tradeoff with -r mode. if it's using disk-backed logs without reduced write mode it's using the sqlite memory management and you'll avoid this issue. With pure in-memory mode logs are already dropped when memory limits are hit.

#6 Test/fix live streaming on 8.6+ firmware 1 year, 4 months ago

Ticket created by ~martijnbraam on ~martijnbraam/OpenAtem

Seems like the default servers and possibly some protocol fields are changed in newer firmware and the streaming doesn't start properly from OpenAtem