Can't start a new session in logic with logic pro 16

Logic 2 Software
1

I have a problem with starting new session in Logic 2 (tested on 2.4.40 and 2.4.40) using logic pro 16.

What I did:

  1. connected the device via USB

  2. looked in devices dispatcher to make sure it connected

    {FB1FD132-3E6C-4210-A113-D400E25F12CC}

  3. opened Logic 2 software. It says that device connected, gives me a button to start session, but when I press it, nothing happens

    {CFD89386-3BC5-439D-9E00-BBC8D6B12C17}
    {CFD89386-3BC5-439D-9E00-BBC8D6B12C17}1920×1032 45.1 KB

What is the possible troubleshooting and causes of a problem?

I am using Win 11. I tried reinstalling the USB 3.0 drivers, it didn’t help

2

Hi @samforaccreg,

Thanks for sending this in, and sorry for the trouble with the software!

This looks like something is failing in session initialization. When you connect a device, the software is supposed to automatically create a new session (tab) for you, but that is clearly failing. Pressing the “Start a new session” button does exactly the same thing, so that’s likely encountering the same bug.

This is probably not a problem with the device.

Let’s try the following:

  1. Please send in your machine ID. That will help us locate any error reports from your system, if error report uploading is enabled. Machine ID instructions here: Getting your Machine ID | Saleae Support

  2. Reset your software’s settings. (note, this will reset the machine ID too. Please send us the old one first, so we can check that for error reports) The config file is located here: %APPDATA%\Logic\config.json. We would appreciate it if you backed it up first, so in case this fixes the problem, you could send us the defective config file for analysis.

  3. Send in the software logs. Logs are located in %APPDATA%\Logic\Logs and there is 1 directory for each time you open the software, with the timestamp in the name. Please send us a recent log, and we can check that for possible issues.

I expect we should be able to get this fixed soon. Hopefully the above reset fixes it, and if it does, hopefully we can root cause the problem with the original config file.

3

Thanks for your reply. Here is some information

  1. {“Environment”:“production”,“Branch”:“master”,“Commit”:“34d965a1131aff7a5f8e71e3b202f5f5bfaac430”,“Version”:“2.4.39”,“AutomationVersion”:“1.0.0”,“MachineID”:“e185d2f4-c109-4509-9466-5522a62889df”,“PID”:41464,“LaunchId”:“0919ffc7-d763-4f0a-96af-20018c5bed9d”,“Architecture”:“x64”}

  2. saved old config.json

    config.txt (13.1 KB)

  3. Sorry but I can’t upload this files. This is what I see when I try to download the log file

    {68901195-C942-4BF9-8FD7-582980522F47}
    {68901195-C942-4BF9-8FD7-582980522F47}851×194 8.63 KB

    so I renamed this files to *.txt

    graphio.txt (16 KB) 2025-12-17_19-38-20_222f22c0-f3d6-405e-9eb6-334f8301dcd5

    graphio2.txt (12 KB) 2025-12-17_19-39-18_7c652fb8-4a23-4fce-83aa-74d8319bf33f

4

Hi @samforaccreg,

Thanks for sending this in. I was able to find a few error reports that I’m still looking into. In the short term though, could you update to the latest version of the software?

You can download the latest version here: Download Logic 2 - Saleae

So far, I suspect that something is actually taking a really long time to complete, rather than simply failing out right. Could you connect the device, open the software, and let it sit for 60 seconds? Let me know if you get any errors in that period, or if the software is still sitting at the same “Logic Connected” screen.

Also, if you deleted your old config.json file, please send the new machine ID with your next update.

5

  1. New machine id {“Environment”:“production”,“Branch”:“master”,“Commit”:“05ad8d6be271a0d95ad14dd2e3d455413996c8a8”,“Version”:“2.4.40”,“AutomationVersion”:“1.0.0”,“MachineID”:“2d9ea92a-bb76-4c53-9b13-395097376557”,“PID”:108628,“LaunchId”:“98572e92-2834-48bf-a5a0-4c0a382d79fa”,“Architecture”:“x64”}

  2. New logs. App still in logic connected screen. I didn’t see any error messages

    graphio 2025-12-30_17-05-49_e645a908-5bc4-43bb-b4c6-50b85bd930cd.txt (12 KB)

    graphio 2025-12-30_17-11-00_98572e92-2834-48bf-a5a0-4c0a382d79fa.txt (12 KB)

p.s.

I tried keeping the app open for a very long time (about 2 hours), and it worked; the app launched a new session. Here are some logs

graphio 2025-12-30_17-22-56_cb47bba4-14dc-4d48-b1b9-f542f31cfa70.txt (32 KB)

6

Thanks @samforaccreg,

This will be hard to prove, but I suspect the problem is the calibration check phase of the device initialization is taking an unusually long time. I don’t know why though.

Logic 8, Logic Pro 8, and Logic Pro 16 will download calibration data from our servers automatically. The download is performed only once, however the software will check for updates again each time the software is opened and the device is connected. The check should usually complete instantly, or if the machine is offline, or our web service is blocked, it should fail immediately. My guess is something very unusual is happening at the network level, that blocks our software from accessing the calibration service, without causing the operation to actually fail.

We’ve never seen this problem before, nor have we heard any other reports like this before, and unfortunately our logs don’t record the status of this. However there is a very quick check to perform. Could you close the software, disconnect your computer from the internet (e.g. turn off Wifi, or unplug the Ethernet cord, or disable your network adapter) then open the software and see if the device is recognized and the session is created quickly? Logic Pro 16 should initialize in about 3 to 5 seconds.

If that works, then the problem is most likely the one I mentioned. Our software accesses the internet for several other reasons (checking for updates, loading the extension marketplace, etc) but none of these other operations block normal operation of the software. Calibration is required to be downloaded before taking any recordings for analog readings to be accurate, and usually completes instantly (or fails instantly, in which case a missing calibration warning will be shown) but in either event the session gets created without delay.

Is this is on a company network, there could be an unusual network security policy in place that is blocking the software in such an unusual way.

Let me know your findings. However if this is the case, I don’t think I have a quick fix handy. I may need to modify the software to add logging and timeouts then send you the build to debug further.

Also, you can learn more about our device calibration here:

If when completely offline, you still have the same problem, then I’ll need to go back to hunting for more possible issues, or try to add more logging to the application.

In the meantime, I’m very sorry for the trouble with your device! I hope we can get this fixed soon.

1 Like
7

Hello again!
The problem somehow disappeared, everything works fine now. It looks like the problem was indeed with the network. I’ll let you know if the problem occurs again
Thanks for your help!

1 Like