We have had several bome crashes in the past but it has getting more and more frequent. On one macbook pro, it has crashed about every other day we use it since we bought that macbook. That was about 6 months ago. Now it is starting on another MacBook. This other MacBook was recently updated to the current OS last week and now we are getting crashes that we haven’t had before. We had 2 crashes on this macbook in the past week. Included the dump files. Thank you for your help.
error logs.zip (25.0 KB)
Steve…Shawn is a member of our team. Would these log files help you solve our issue?
Bome Network.log (410.8 KB)
Bome Network1.log (512.0 KB)
As I have looked at these, they look like they show logs for today when we were running smoothly - not when it crashed. I’ll leave anyway if it is helpful.
Thanks for the help as always. Mike
How do you have your computers connected to each other and to the network?
From the log it looks like your computers are using DHCP but the DHCP server is dropping so your Mac is redefining its IP address by self assigning.
You could probably solve this in 2 different ways.
- Make sure both of your computers are connected to the same network and as a DHCP client and that your DHCP server is active before you start your computers.
or
- Set fixed IP address for your Macs (with same network and mask) and make sure the IP addresses assigned do not conflict with the DHCP server address it will assign.
Usually option 1 would be cleaner as you wouldn’t have to worry about ever assigning an IP addresses.
If the only devices on your network are the Macs (connected via ethernet with no DHCP server), then use option 2,
From your log file:
2025-03-05 16:53:08.129 NetDirectory type #1 remote port ‘PV ProPresenter Bome’ seen with new address: 192.168.1.185:37000
The above is a standard DHCP address assigned by a server
2025-03-05 16:53:09.045 NetDirectory type #1 remote port ‘PV ProPresenter Bome’ seen with new address: 169.254.208.2:37000
The above is a self assigned IP address and most computers will switch to this when the DHCP server is absent.
Any time the computer switches from one mode to another, you would need to restart Bome Network, therefore it is important that you establish and maintain a solid DHCP connection. Uplugging and re-plugging ethernet cables could also cause this re-assignment.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thanks Steve. We have 2 MacBooks and ProPres PC on a dedicated “production network” with no DHCP. The have assigned IP addresses for those devices on this network. The ProPres PC is also on our main network. It also connects via Bome to a Camera control PC. You helped me solve my issue with midi into ProPres a few weeks back. Now, the Bome program on the Macs is crashing almost daily. When it crashes, all of the devices are on the 169 network. We aren’t experiencing Bome program crashes on the PCs.
Once we restart Bome after the crash connection is solid until the next crash.
Any devices that you have on a fixed IP cannot be on a 169 network as 169 networks are only supposed to be used for APIPA (Automatic Private IP Addressing) . Put them on an unused 192.168 network instead.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thanks, Steve. We moved to a 168.0.0.0 network and had the same crash on the Tracks MAC. Florian contacted Shawn in response to an email regarding a potential GUI issue.
OK, just to be sure could you show me screenshots of the IP configuration of your devices on the network? Clearly, from the log tat you sent, Bome Network was detecting and switching IP addresses so I’m not convinced that it is strictly a GUI issue. I will discuss with Florian.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Sorry, it should be on 192.168 network. 168 is reserved for virtual public IP address. My bad for the typo. So if you already have 192.168.0.xxx used try 192.168.1.xxx with netmask 255.255.255.0
Steve