Fórum Image Line

If you press F1, or in the main menu > Help > Help index it still takes you to the online manual in your web browser. If you press the pin icon on the top right of the pop out Help/Gopher etc it won't disappear when you click away... unless you have the playlist or piano roll maximized and click on it.

guess what now

Thanks for reporting. Normally you should use the Ticketing System not Looptalk to report bugs. The pink squares appearing on the playhead are GPU redraw artifacts. FL Studio’s macOS graphics engine is failing to repaint certain UI regions correctly. When the scaling is set to 100%, FL Studio switches into a fallback rendering mode that avoids partial‑rectangle painting - which is why the pink boxes disappear. The team is investigating. Your second issue - the Clip Properties window closing, reopening, and freezing is also a known FL Studio macOS UI bug, also being dealt with. viewtopic.php?p=2064768#p2064768 Regards Scott ah my bad, first time on forum, will do that nextime. my other question, is it just me where fl studio uses more resources for example, ram? I had a project that i made on my windows pc that only has 16GB of ram, and then opened it on my mac and somehow my mac was using a whole lot more ram like 19GB, how does this make sense? as my laptop is more powerful than my current cpu in my pc? and i have a template ive made, it does have quite a fair bit of plugins preloaded for example serum. but on my pc, it stays around 2GB ram usage and on my laptop, 4GB and quickly goes up if i do anything more. is there a memory leak or something going on here? thank you for your reply i do appreciate it! hope youre having a great day

It;s now in that pop up window on hthe right that keeps disspaearing and is much harder to use. Is it a push to use gopher more? The help on that pop out thing i find much harder to read and is more overwhelming somehow.

Thanks for the input. Mixer track copy API (whole track + single FX slot). Mixer track save/restore to FST with returned file path. Channel Rack save/restore instrument state to FST. Create new channels from FST files. Playlist API: read items, read audio paths, add/remove items. Automation linking via shared FST link IDs for auto‑binding on restore. Undo grouping functions to avoid dozens of undo entries. Bulk mixer/channel info queries instead of hundreds of calls. Stable internal IDs for tracks, channels, FX slots, playlist items. <-- This one is coming EOY hopefully. Channel Rack group API: list groups, names, membership, move channels. Script‑accessible FL Studio version string. API for collapsing/uncollapsing mixer groups. Open Gopher‑level API access to third‑party developers. <-- Definitely working on it but we have to move carefully. Thanks! We’re getting closer to being able to save and restore everything together. Would love to test those APIs in future

"Hi Nico, could you please let us know when the next update or hotfix will be released to fix these issues?"

With regard to Stable internal IDs for tracks, channels, FX slots, playlist items. <-- This one is coming EOY hopefully. Would this mean if we output FPC and slicex samples and the like (and even patcher routing) to certain mixer tracks these mixer track mappings would finally stay put if we reorder those tracks? Yes

It's visible in the Envelope/Instruments Settings and the Miscellaneous Functions tabs in FL 12. I believe it has to do with it now being able to load in Patcher and it no longer being hardcoded in FL itself but being it's own plugin. Exactly- you can't see the keyboard anymore on the other tabs since 3xOsc graduated to full plugin status. That keyboard being there is indeed inherited from the Sampler which in itself is more of an outgrowth of FL Studio than its own plugin at this time. So just the code pertaining to 3xOSC does not include the built-in testing keyboard on the other tabs. Because that is part of FL Studio, not the plugin itself.

The only way to keep FLS's fps at a standard level, is to Bridge plugins that are bringing the programs fps down. Annoying, but at least it works This seems to help somewhat. Since the GUI freezes happen randomly I'm not sure how I can reproduce it. All I know is this would happen at the very least once a week. Have rolled back to NVIDIA driver 581.80 and had to do a couple of extra steps to do it. Apparently Windows forces an update on it so I had to restrict the card from being updated on Group Policy. If you don't see me posting here within the next couple of weeks, then I guess the issue is gone. If anyone has any info, do let me know. Have a good day! Hey, did you face any issues with UVI plugins, Drumreplacer in example ?

I tried here but I don't see the difference when exporting to a mp4 file. Please note that if your video player scales down the video then it could affect the brightness of thin lines like this.

I've found a similar problem using peek effects: audio plane. The lines look thick and bright in the preview but when rendered at higher resolution they are dim and very thin