|
|
|
11-21-2019, 06:22 PM
|
#1
|
Human being with feelings
Join Date: Jun 2012
Location: Spain
Posts: 7,242
|
Faster access to track chunk data when there is huge encoded plugin data
When the track chunk is very big, we need a faster way to access the track data from the API. Currently it is very slow because it loads all the plugin encoded data(which can be huge on some plugins) and it is not needed if I am only going to read the track data and plugin names, and not modify the chunk in any way. It is also slow from SWS extensions. For example how to get the number of Frozen plugins in a track without having to read all the chunk data?
Thanks!
|
|
|
11-21-2019, 06:28 PM
|
#2
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Agreed
Not sure if I'm qualified to suggest anything more than that but would love to see a solution to this.
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
11-21-2019, 06:32 PM
|
#3
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,623
|
I suggest to add an optional parameter "boolean omitFXEncodedData" that strips away all the Base64-encoded strings for FX, leaving the rest untouched.
|
|
|
11-21-2019, 06:39 PM
|
#4
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
+1
|
|
|
11-21-2019, 06:40 PM
|
#5
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,623
|
One thing we forgot, it should also be for ItemStateChunks, as they can have FX as well.
|
|
|
11-21-2019, 06:54 PM
|
#6
|
Human being with feelings
Join Date: Jul 2016
Location: Los Angeles, CA
Posts: 1,701
|
+1 Yes, please. Kontakt alone is just stupid.
|
|
|
11-22-2019, 12:00 AM
|
#7
|
Human being with feelings
Join Date: May 2011
Location: KZ ALA
Posts: 110
|
+1
Quote:
Originally Posted by heda
I was going to request a change in the RPP format But now since we are already 6.0rc, I feel it is too late to change this.
It was to store the plugins encoded data outside the track chunk with a ID link or something in a different part of the RPP file. This would improve performance of reading track chunks from API, when not needed to read the plugins encoded data, which can be huge for some plugins making it very slow to read from scripts.
|
With large data stored from plug-ins, the autosave of the project takes a very long time. This greatly slows down the operational work.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 09:34 PM.
|