TD-50 will not load kits from module to V-Drum Explorer
Closed this issue · 8 comments
Hi
Thanks for explaining the required settings so promptly for my last problem.
I am now struggling to get kits to load into the software. I tried the whole module first and I have tried just one kit, and both failed.
This is the log file for the error.
Best regards
Carl
Thanks for the log data. Unfortunately this is the problem with me not having a TD-50 - I can't test anything for myself :( Basically this is going to be a schema problem somewhere. That's a particularly odd problem though, as it's not that the value is out of range - it's the offset itself.
I'll have a look in the schema for container of size 164, and try to add a bit more early validation. I hope I'll have a new build for you over the weekend. The really weird part is that I have a .vdrum file for a TD50 that someone captured for me a long time ago, and that still works. I'd expect that to fail in the same way if it's a schema problem. Hmm. Will have to investigate.
One thing you could try in the meantime is loading a single kit instead of loading all data. If that works, then that would suggest the schema problem is in a non-kit part (settings, set lists etc).
Whoops, I see you've already tried just loading a single kit. If you load different kits, do you always get the same error? (Some aspects of the data are dynamic and might only affect some kits.)
Hi
Yes seemingly the same error. I tried loading vex kits, my own kits, and others. All the same as below.
Don't know if this helps, but I am not sure that the explore feature is working for me either. The software does not seem to display the actual data, it just gives what data to expect and typical ranges?
Right - thanks for the info. I'll see what I can work out. (The data file I'm using was captured a very long time ago, so it's possible that's why it's still working for me - I may have broken something since then.)
That screenshot is the schema explorer. That's working as intended - telling you what fields are available etc, which is precisely what's in the schema. (That's how you can see the schema for any device, whether you've got one or not.)
It's of more use to me than anyone else I suspect, but I thought I might as well still make it available for everyone.
Good news - I think I've found the problem.
I want to spend a bit of time finishing up the AE-10 MFX details, but I hope I'll be able to do that before the end of the week, then create a new release.
Version 1.0.0-alpha07 has now been released - please uninstall 1.0.0-alpha06 and give the new build a try. I'm confident it will fix this, so I'll close the issue for now.