Working with Nebula Man 1.5.2 (x64) and Acqua 1.4.006 (x64) in 96kHz.
In preview Mode B I save an Fx Chain with AlexB 4KC Console - Line in program on 96kHz which has program number 259. After having saved the Fx Chain, closed Nebula Man and reloaded the Fx Chain again it is showing the 44.1 kHz program which is number 232.
In Nebula Man 2 RC1 everything is fine. Same setting - the Fx Chain is loaded properly.
Is this happening only with 96 kHz ? Can you replicate this with some other Nebula programs ?
What is the name of the program 232 ?
NebulaMan 1.x identifies programs using combination of top level category and program name. So hypothetically, this could happen if another program with the same top level category and the same name, but other subcategory, exists.
NebulaMan 2 is more clever, it identifies program by its program file name (.N2P), which is always unique.
zabukowski wrote:Is this happening only with 96 kHz ?
It does happen with all programs which are not 44.1kHz as far as I can see for now.
zabukowski wrote:Can you replicate this with some other Nebula programs ?
I checked right now with Tim Pethericks' Silk for Nebula in 48kHz. I loaded the program "SILK MID v3 st" which has program number 358 and saved it as Fx Chain. After loading the Fx Chain again Nebula man shows me tat it has loaded program 356 which corrsponds to the 44.1kHz program "SILK MID v3 st".
zabukowski wrote:What is the name of the program 232 ?
It's the same name as of program 259 "4KC Line In". I have attached screenshots.
Yes, this is the exact problem i've described. Programs are identified using combination of top level category and program name, so NebulaMan sees them as duplicates. So, it always uses the first program found -> 44.1 kHz.
I recommend you to use NebulaMan2 or to temporarily remove 44.1 programs from repository to avoid duplicates.
Unfortunately, fixing this in NebulaMan 1.5 would require huge amount of work and possibly cause a lot of backward compatibility issues.