Announcement

Collapse

Technical Posting Guidelines

PLAYING TECHNIQUE DISCUSSION ONLY! DO NOT POST TECHNICAL QUESTIONS!
See more
See less

Customizing TD-17 via USB - technical data sheets?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Alan VEX
    replied
    Guys, please take this private. I donít think it is wise to test apps publicly. It can put userís machines at risk.

    Leave a comment:


  • jonskeet
    replied
    (Apologies for not replying before - despite being subscribed to this topic, I'm not receiving emails. I need to investigate that.)

    Fantastic! That definitely sounds like a good use of the software (And there'll be no cash involved - this is open source software. Admittedly it's only hobby code, with the obvious caveats, but I'll do what I can.)

    Now, I'm awful as an application author (as opposed to other aspects of software engineering) so my user interface skills are terrible - including accessibility. This will be a good opportunity to improve! You may well find that when we first get the application running on your machine, your screen reader doesn't pick much up to start with... or it may all just work out of the box! But before it'll really be usable on a TD-50, I'll need a sample data file. That will basically involve getting you the code, you running it, saving a file and then emailing it to me. In theory, what should happen is:
    • You turn the TD-50 on and connect it to the computer
    • You run the program
    • It detects the TD-50 (there's a log with lots of information about what it finds)
    • A button saying something like "Load from device" will be enabled when it detects the TD-50
    • When you click on that button, it will probably take quite a long time to load all the data - it does it one memory segment at a time, and there are thousands of segments
    • Eventually, a second window will pop up - this would normally be where you'd "explore" the kit, but I haven't put time into the layout yet, as I wouldn't be able to test it
    • There will be a File menu with a "Save" menu item - this is where you can save all the data into a file, and then email it to me
    Currently the code only supports some prereleases of .NET Core - I'll see if I can change things to allow it to work on any version of Windows 10. Watch this space

    Leave a comment:


  • 1 eyed willy 73
    replied
    Hello, this would be a great add on for blind users like me.
    I would have no problem getting some cash together for this program.
    I recently picked up the TD 50, and i would greatley be easier to navigate the module.
    As long as i can use it on win 10 pc in explorer, i would check it out.
    I have a yamaha dtxtreme 3, but i finally had to give up on it cuz i did not no where i was at on screen,ect..
    A guy by the name John Mellis, finally created way to hook up the later dtx modules, like the dtx 700, ect, to work for connecting to pc.
    I downloaded the program, and my screenreader, was able to read everything to me, function, what i could change edit, ect..
    But i was not willing to shell out more cash for a dtx 700 module.
    Personally, i would support this idea all the way untill final beta testing.
    The blind and visually impaired would be your greatest customers, for shure.

    Leave a comment:


  • jonskeet
    replied
    Pulsc The code now supports editing and saving the data back to the kit - it seems to work with my TD-17, at least. I've got a rudimentary TD-50 schema which would *hopefully* be enough to get a data dump from you, then I can make it more reasonable. If you could ping me by email ([email protected]) we can work out what you'll need to get it working.

    Leave a comment:


  • jonskeet
    replied
    Hmm... the "generic dump without understanding file structure" program is proving harder than expected, in terms of the module not returning all the data. I suspect I'll need to come up with a skeleton TD-50 schema based on the implementation document, and load each section directly. That's fine, but it means it won't happen before I go on holiday on Friday...

    Leave a comment:


  • jonskeet
    replied
    Fantastic. My code is currently written against a preview version of .NET Core (a development platform) but for the purposes of getting a dump file, I can probably whip up a new program that just uses .NET 4.6, which I suspect you've got on your system already (assuming you've got a Windows 10 machine you can connect to the kit).

    This is likely to become easier by email - if you'd like to email me at [email protected], we can take it from there. If you'd prefer the discussion to stay here, that's fine too.

    Leave a comment:


  • Pulsc
    replied
    Yeah, I have a 50. Interesting. If there's a way of doing it remotely between us, that would be pretty handy.

    Leave a comment:


  • jonskeet
    replied
    > If you did manage to get your hands on a 50 to do something similar, I would throw money at you almost right away!

    Do you have a TD-50 yourself then? Given that we're both in the UK, maybe we could work something out once I've got it all working well with the TD-17.
    They way I've built this, it *should* just be a matter of adding all the relevant JSON files to describe the TD-50 schema, and that's all documented. Reality means it's likely to take rather longer than that, but I may be able to sort out a program you could run that would give me a "dump" of your module that I could then use...

    Leave a comment:


  • Pulsc
    replied
    I'm very interested in this! I don't have a 17 currently, but the idea of picking one up down the line is floating around so this would be great.

    If you did manage to get your hands on a 50 to do something similar, I would throw money at you almost right away!

    Leave a comment:


  • jonskeet
    replied
    Currently it's read-only - it just lets you view all the parameters. (Not "all" currently as I haven't transcribed the schema for some of the MultiFx options - there are a lot of them! But it will be every piece of data I can get out of the system eventually.

    I definitely want to make it read/write, so that basically any changes you can make via the console could also be made via the explorer. So for example:
    • Copy an existing kit into another slot
    • Rename a kit
    • Change the module-wide midi note settings
    • Change the 10" Beech Tom highlighted in the screenshot to be a snare instead
    • ... or add a sub instrument for the same trigger
    • ... or change the muffling for the tom
    • ... or change the kit to have tape echo
    I only have access to a TD-17, so that's all I can code and test against, but it's all parameterized via huge JSON files... I expect that with the right JSON files, the TD-50 should work too (and I'd love to support that). I don't think any other models support the sysex messages I'm using... it's possible that I could write something so that a TD-11/15 could dump all its data to the explorer, but then there wouldn't be any edit functionality (as far as I can tell). That may be the case with a TD-30 as well; it's hard to tell from the documentation.

    I can see myself buying second-hand modules to test this all, of course...

    Leave a comment:


  • MilosDrummer
    replied
    It's always great to see new ideas! Keep 'em coming ☺️

    In the meantime, could you explain what this explorer does (apart from exploring )? If you manage to edit parameters, how do you know what to change and by how much?

    Leave a comment:


  • jonskeet
    replied
    I don't know whether anyone else is actually interested in this thread - I won't update it again unless someone replies saying they want to know more - but the project is coming along quite nicely...

    2019-7-22 (41).png

    Leave a comment:


  • jonskeet
    replied
    Just to follow up on this, I've now found the following documentation of the TD-17 midi implementation:
    https://static.roland.com/assets/med...le_eng01_W.pdf

    (I'm not sure how I missed it before.) I suspect that the SysEx messages could do everything I need.

    I've also worked out most of the details of what's in a TD0 file, which could prove handy - and which on inspection looks like it's identical to the parameter address map in the midi documentation. Obviously it's still very early days, but if I end up creating anything interesting, I'll share more details.

    Leave a comment:


  • jonskeet
    replied
    Righto. Seems A pity - it would be fun, but I don't want to get into the realm of reverse engineering. (My expectation would be sitting at computer *and* kit together.)

    Leave a comment:


  • Alan VEX
    replied
    Even I have never used the PC editor feature of VDL. You canít tell what your doing, so you might as well sit at the kit and do it right. Not to shoot the idea down, but very few people use such a feature. It wouldnít be worth your time.

    Leave a comment:

Working...
X