Hey gang - Is it normal for Soundflow to create massive log files? I've got a few that I found via Disk Inventory X and one has got up to 18gb! I'm assuming these can be deleted? Any idea why it happens or how to prevent it in future?
Thanks!
- SSoundFlow Bot @soundflowbot
Thanks for contacting SoundFlow support.
Please note, that the best way to get help with a script, macro or other content installed from the Store or content that you've made yourself, is to select the script/macro, then click the red Need help button, and then click "Get help with this script or macro".
By using this method, we will get access to more information and so should be able to help you quicker.
You can read more about how this works here: bit.ly/sfscripthelpIf you're seeing an error that isn't related to scripts or macros, and you think this is a bug in SoundFlow, please file a Help/Issue bug report.
You can see how to do this by going to bit.ly/sfhelpissue 
In reply toRobin_Newman2⬆:Kitch Membery @Kitch2023-07-12 17:38:00.295ZHi @Robin_Newman2,
These files seem way larger than they should be. If you open the 6.74GB log file, do you see a log line that seems to repeat itself over and over? If so can you copy and paste it here in the thread?
Thanks in advance.
Christian Scheuer @chrscheuer2023-07-12 19:22:06.226ZYea this definitely sounds like something's wrong. It may be you have a MIDI device that's sending invalid MIDI messages for example - or something else may be repeating as Kitch suggested.
Kitch Membery @Kitch2023-07-12 19:46:44.842ZFYI @chrscheuer,
I'm seeing a lot of Migrations calls when testing Robin's account.
Every time I select a new command in the commands list a backend Migration log line is appended to the log.12.07.2023 12:39:18.69 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:19.41 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:20.50 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:21.09 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:21.54 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:22.24 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:24.83 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:27.09 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:27.95 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:28.91 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:30.97 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:33.45 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:34.70 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:36.13 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:36.96 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:37.67 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:38.53 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:39.23 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:39.81 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 -> 12.07.2023 12:39:40.27 <info> [Backend]: Migrations: DL19L2A00295 -> Migrations: CL30I1A01746 ->I don't see any MIDI or HID triggers assigned, or any MIDI scripts in the account. So I think that invalid midi messages can be ruled out maybe?
- Christian Scheuer @chrscheuer2023-07-12 20:29:03.582Z
Hmm, that's a new one.. Does this go away if no Stream Decks are attached?
- Kitch Membery @Kitch2023-07-12 20:39:20.848Z
Yes, disconnecting seems to make it go away.
- In reply tochrscheuer⬆:Kitch Membery @Kitch2023-07-12 21:09:28.833Z
On further inspection @chrscheuer, an instance of the "Migrations" log is appended to the SF Log when you follow these steps in Robin's account.
- Select the "Default Package"
- Select either the "App Launcher" or "Pro Tools" subfolders within the "Default Package" package.
- Repeat steps 1 & 2.
Selecting a new deck in the commands list also appends "Migrations" entries. So the easiest way to recreate the issue is to select "Search Results" in the package list and then filter all decks using the "Decks" button. Then navigate through them in the "Commands list"
When I detach all my stream decks the "Migrations" log is no longer appended. And when reattaching, the "Migrations" logs resume.
In reply toRobin_Newman2⬆:Robin Newman @Robin_Newman2Thanks for looking into this! I'm sorry, my Mac HD was full and my computer was grinding to a halt so I have already deleted the log files and can't share the contents - However, I've just looked at my current main log file which was last updated yesterday and I do think maybe you're on to something with the midi device hunch. I recently got a Midronome which is a midi/analog clock to sync all my external gear - So that's sending constant midi clock when it's plugged in to my midi interface (which is the point of it). The log is absolutely full of " [Backend]: Unexpected MIDI byte: 248" messages. When I unplugged the Midronome to take to band practice last night, these midi log entries stop. Is there any way to exclude these messages from the log or tell Soundflow to ignore them? I still need my clock as it's part of my studio setup, but I imagine midi clock is never something that Soundflow would need to 'listen for' in the same way as midi note/cc data?
- Christian Scheuer @chrscheuer2023-07-14 12:17:15.162Z
I just confirmed this is a bug in our MIDI parsing code. I've made a fix for this in our internal 5.4.4 previews so the fix should be out with 5.4.4 soon.
Robin Newman @Robin_Newman2Awesome, thanks Christian!
- Christian Scheuer @chrscheuer2023-07-14 17:17:47.340Z
Hi Robin,
Please try installing this preview to see if it fixes the log issue:
- Christian Scheuer @chrscheuer2023-07-15 19:02:23.019Z
Here's another preview with a few more fixes in the same area:
- In reply toRobin_Newman2⬆:Robin Newman @Robin_Newman2
Hi Christian, I've just installed that latest preview and so far all seems well. I'm not seeing any of the Unexpected Midi byte messages in the log. I'll keep an eye on the log file sizes over the next week and let you know if I have any more issues.
Thanks again for all the amazing work and support!
- Christian Scheuer @chrscheuer2023-07-16 17:41:28.944Z
Awesome, thank you for confirming!
I've since worked with some other MIDI-related changes in preview 3 - could I get you to double check with that version that I didn't mess up the fix that worked for you in preview 2?
See more here & link to download preview 3:
Pro Tools doesn't launch after installing Soundflow #post-27
- In reply toRobin_Newman2⬆:Robin Newman @Robin_Newman2
Thanks Christian, I did just have three days in the studio away from my home rig and came back to find the log had grown to 24gb again, so I've just installed this preview 3 and saw the bit in the other thread about being able to view the log 'live'. Viewing the log now it seems that I'm not getting spammed with the midi messages so that's good. Whilst I'm not actively using soundflow (i.e. pressing any buttons on Streamdeck, etc), the log just gets updated with "20.07.2023 09:58:09.37 [Backend]: [SF_FIREBASE_WS]: Sending keep-alive" - roughly every minute or so. Is that expected?
- Christian Scheuer @chrscheuer2023-07-20 10:02:11.254Z
Great! Yes, that's expected. Thanks for confirming preview 3 seems to fix things :)
- Christian Scheuer @chrscheuer2023-07-20 10:04:02.841Z
We're promoting this preview to become a final build, so it'll make its way into the official 5.4.4 build very soon :)
Thanks for your help testing this!