| Author | Topic: .fxb file format - patch name limit? | |
| gnu23 | Posted: 23rd May 2004 19:59 | |
Hi all -
I am working on a patch bank for one of my favorite synths and I've run into something odd. When I load my bank into the synth via energyXT, it loads ok, but the first patch is almost always not right sound-wise. Fortunately, I save all my patches as .fxp's, and by loading the offending patch into its proper slot in the bank seems to fix it. When I try to load the same bank via MiniHost, I get an error saying the bank was not made for the synth I'm working with. I realize MiniHost is in the alpha phase, but the factory patches for the synth load fine there. I also get the same error for my individual patches but not for factory ones. Those are the symptoms. In all cases, initial patch development was done in energyXT, by the way. Now then, I tend to use descriptive patch names - the longest is under 20 characters. Everything else being relatively equal, the only thing I can think of is that patch name length may be pushing patch data out a bit past where the synth thinks the data should start. Is there a specification for the .fxb file format and/or one for .fxp? Any other theories? Many thanks in advance | ||
| tobybear | Posted: 23rd May 2004 23:19 | |
Can you tell us what synth has this problems?
So far I found that for example Linplug Alpha behaves very strange concerning loading of its own patches from different hosts. FXB/FXP format specification is available from Steinberg in the SDK, but I don't have it at hand right now. Cheers Toby www.tobybear.de | ||
| gnu23 | Posted: 24th May 2004 08:23 | |
M42 Nebula from Algomusic. Thanks, Toby. BTW, I don't believe this issue is a bug of some kind in MiniHost alpha. | ||
| tobybear | Posted: 26th May 2004 04:23 | |










