sagamusix / JDTools

Patch conversion utility for Roland JD-800 / JD-990 and compatibles
Other
46 stars 5 forks source link

ConvertSetup800to990 issues? #13

Closed gitl0ver closed 9 months ago

gitl0ver commented 9 months ago

Reporting here again, my apologies...but at least one of the issues I'm reporting is new, and the other I have explained in better detail/made the issue more clear. I'm running the latest public release on Windows 10, and I haven't been able to get JDTools to accurately convert JD-800 special setups to my JD-990 (running firmware revision 1.01, if this helps). My issues:

sagamusix commented 9 months ago

The tones are erratically panned left and right, which shouldn't be possible since this is an 800 setup. I don't know where it's producing the nonexistent data from, since it even does this on initialized patches where the pan for all tones is set to 0.

JD-800 setups (just like JD-990 setups, where this information is part of the regular tone settings) have an individual pan settings for each note. This is not a bug, and it is a feature the JD-800 default setup makes use of. I'm not sure what you mean by your second sentence because patches and tones don't have any panning settings on the JD-800, only setup keys do, and generally the conversion of setups and patches is completely unrelated.

As for the second issue, I don't quite understand what the problem is, as you keep switching between patches/tones and setups, which are two distinct things. As mentioned before, there is no effect information on JD-800 setups, so the JD-990 setup effect information is pre-filled with default settings. Those defaults were taken from the standard JD-990 setup if I remember correctly, but I could be wrong. The SysEx dumps that JDTools create are always for a complete patch or setup. It is not possible that only parts of a setup or patch are overwritten, unless there is a data transmission issue.

gitl0ver commented 9 months ago

My apologies. I explained rather poorly, but from what you've suggested, I'll just chalk it up to a case of user error here, so the issue is resolved I suppose. Again, thanks for the awesome tool!