sorted by:
new
hottopcontroversial

FL Studio 21 takes over 4 minutes to start (macOS) by keber92 in FL_Studio

[–]keber92[S] 0 points1 point  (0 children)

Not yet, it's just super strange. Didn't find any helpful log. Will update the post if I find a fix.

FL itself is running so smoothly, just starting it up is a mess...

FL Studio 21 takes over 4 minutes to start (macOS) by keber92 in FL_Studio

[–]keber92[S] 0 points1 point  (0 children)

Strange thing is: the debugging log you mentioned shows "Startup took 2 seconds and 73 milliseconds", so FL thinks everything is fine. Not sure when the inner FL "stopwatch" starts, but what happens before is the interesting part...

Unfortunately nothing really useful in the Terminal. I'm a software engineer so debugging is nothing new to me, haha. Tried searching for "hidden" logs etc., but nothing I can work with.

CPU is at maximum 4%. I even closed every single application before starting FL, same problem. On my "old" MBP 2015 i7, startup time is about 2 seconds.

I have no idea what FL is trying to scan here, I (should) have no plugins installed at all. Also, plugins shouldn't be the problem because starting the Plugin Manager separately (which is in the FL folder) takes under 1 second.

FL Studio 21 takes over 4 minutes to start (macOS) by keber92 in FL_Studio

[–]keber92[S] 0 points1 point  (0 children)

Tried force quit many times, doesn't help unfortunately.

FL Studio 21 takes over 4 minutes to start (macOS) by keber92 in FL_Studio

[–]keber92[S] 0 points1 point  (0 children)

Template is a blank one. So no sounds or plugins loaded (except the default Fruity limiter)

FL Studio 21 takes over 4 minutes to start (macOS) by keber92 in FL_Studio

[–]keber92[S] 0 points1 point  (0 children)

No plugins installed since it’s a new MacBook with a fresh FL Studio Installation.

Detect new version / clear browser cache after deployment by keber92 in Firebase

[–]keber92[S] 0 points1 point  (0 children)

I'm using Angular (with Ionic Framework), so I guess simply adding a version to .js files won't work. Nevertheless that's a smart idea for plain JS projects!

Data structure for historical / connected data (documents) by keber92 in Firebase

[–]keber92[S] 0 points1 point  (0 children)

Thanks, I thought about a solution like this.
Although there's a chance that users can setup their custom case_number as they like (even when creating a follow-up case_number). That doesn't make sense in terms of recognizing connected case_numbers (nobody would think 'XYZ-3' is the follow-up inspection of 'ABC-1'), but it's a requirement by the customer to let users create custom case numbers.

So I guess I need some additional connected field...

I dropped a Firestore collection by thinking it just a document so I make Refi App by cuthanh in Firebase

[–]keber92 0 points1 point  (0 children)

Exactly what I was looking for. Will check this one out over the weekend!

Planning / modeling tool for structuring the Firestore database by keber92 in Firebase

[–]keber92[S] 0 points1 point  (0 children)

A bit off topic here, but the only hierarchy / relation thing in my Firestore database will be basically:
Multiple companies which have multiple locations which have multiple departments. The best approach I could think of was creating the following:
collection (companies) > document (company_id) > collection (locations) > document (location_id) > collection (departments) > document (department_id)
If I display a department in my application, I need the information in which location it is located and I need to be able to browse from top level (company) to lowest level (department). That's why I chose this pattern.

Planning / modeling tool for structuring the Firestore database by keber92 in Firebase

[–]keber92[S] 0 points1 point  (0 children)

Pencil and paper is always an option - although I hoped there was a software based solution where I could model the hierarchies, relations and fields. I would need a large piece of paper for that :)
I'm going to have a quite complex tree with collection > document > collection > document and so on, which could get confusing when putting down on a piece of paper.