开云体育

Yes, my DX7Editor is still coming along. A lot of stuff keeps getting added to it.

My initial plan was to release it without help files apart from a tutorial video. But, I've started writing help and in doing so I'm discovering bugs. So, rather frustrating for myself but I think I need to get the help written if only for the side effect of debugging.

I've spent a lot of time using it to program my TX7, and I feel that the program basically works well and makes it very easy to program DX/TX synths. A lot of the "additional" capabilities over and above just being able to change the parameters, such as extensive copy and paste of all sorts of different things, being able to save and load parts of voices, using the second window for "detailed" editing etc., seem to work very well in practice, and vastly ease programming.

Extensive (computer) keyboard control modes have been added. So, you can (more or less) just edit an attached DX7 by typing on the computer keyboard, through parameter shortcut codes and using the arrow keys to move around the parameters. In this mode the program reports on actions through built in speech. This part of the program isn't quite complete, with the main remaining problem being how to load and save patch banks through keyboard commands. But, I think I know how to do this and will have a crack at completing that bit soon. I found references to how to send custom MIDI commands to a synth in a past discussion on here, so I added a facility to create custom MIDI commands, which then appear in a menu. I've added a lot of things like that.

I did find some nasty bugs though. MIDI in Java on the mac doesn't work too well, which is a bit of a pain as I'm developing primarily on Mac OSX. I have a workaround, but didn't realise that the interface between the main program and the workaround bit sometimes merged MIDI messages, so that they didn't work as the workaround program would try to send (e.g.) a six byte MIDI message that wasn't recognised. Resulting in stuck notes on the TX and other problems. Fixed now, but that sort of thing is a nasty bug. I'd be very happy for a brave person to have a go using my software, if they promise not to judge it based on its current state :) There is no packaged installer, so any extremely early adopter would have to do things such as unzipping the help files and putting them in the correct directory.

Regards,

Ross Clement

ross available for the pc too?

charles

--- In YamahaDX@..., charlie 'chop' copp <charles.copp@...> wrote:

ross available for the pc too?

charles

It should run on the PC too, but I have never tested it. I'll take my TX7 into work today and give it a go.

To run my program on any machine, you have to have Java installed and it be set up to run .jar files. If Java is installed normally, you can run .jar files just by double clicking on them. I've put a test file up into that you or anyone could use to test if they have java installed and set up. Called "TestJar.jar". If you save this on your desktop and double click, it'll run and bring up a small window saying that you can run .jar files, or it won't. Could you please give that a test?

I've just tried on my Mac (OS X 10.6.8) and it runs a .jar file fine if double clicked, with just the standard java and java setup that comes with the operating system.

At present I have no installer. I can send a .jar file by normal email (don't want to upload one in public yet), but I will also have to send the help as a zip file that you'd have to extract. If you want the "speech" part of it, then that's a 15M zip file of audio (which needs to grow once I work out the full list of words and phrases it needs and add the missing ones), which I'd need to distribute .... somehow.

Cheers,

Ross

Does your editor also work with the 4-op TX series, TQ-5, etc?

sorry unwilling to instsall java

sticking with my atari editor

release the source and i will try to port to atari

no java got enough stuff on the pc as is

thanks

charles

On Thu, 1 Sep 2011, Ryan Daum wrote:

?

Does your editor also work with the 4-op TX series, TQ-5, etc?


I'm a Java developer also, I'd be willing to help out with both testing and development if you
want.

I've got a DX200, FS1R, and TQ-5. ?The DX200 should act like a DX7 for testing, and it would be
interesting to try to adapt your code to work with the latter two.

The TQ-5 is a COMPLETELY different beast!
Yes, it is both FM and it is both Yamaha. But that's where the similarity
stops.

I can tell: I wrote YSEDITOR for the 4-op synths and DXconvert for the DX7
(etc). DXconvert can import 4-op sounds and convert them to 6-op DX7
sounds. Works quite well, but still what you get is a conversion not a 1
to 1 copy.

A similar 4-op import/conversion in the new DX7 editor would be nice
though. Is a Java program able to call an external program that is written in Python ? In that case I won't mind if it uses my DXconvert to import
all kinds of file formats. That would be a nice collaboration!

--

MT

--- In YamahaDX@..., Ryan Daum <ryan.daum@...> wrote:

Does your editor also work with the 4-op TX series, TQ-5, etc?

I'm a Java developer also, I'd be willing to help out with both testing and
development if you want.

I've got a DX200, FS1R, and TQ-5. The DX200 should act like a DX7 for
testing, and it would be interesting to try to adapt your code to work with
the latter two.

Ryan

At present it doesn't work with four operator synths. However, I own a FB01 (which I bought when it was just released and have never really used). So, when I get the basic 6-op series work, as well as weird and unusual plugins :) I hope to get it working with the FB-01. That would require some adaptation of sysex etc., and once that's done, it should be easy to expand to other 4 and 6 op synths. I don't know how sysex compatible the various 4 op synths and 6 op synths are. At present there is an "Instrument" choice in one menu, but the only options are DX7 or TX7, and nothing is done with that choice yet. Adding a FB01 choice, disabling operators 5 and 6, and then propagating changes throughout the software (different algorithms etc. would prepare it for adding additional instruments.

At present the code is fairly rough. Occasionally I go through things already written and smooth them out a bit :), but I wasn't thinking of exposing my code to public scrutiny just yet. Ryan, I'll send you the executable .jar file including source, but would like to keep smoothing it out and completing it. Particularly for the "detailed editing" window, there's a lot still undone, but the basic editing seems to work OK.

The design of the software is that it will be a program to which additional functionality can be added through plugins. So, if you or other java developers wanted to add something to it, plugins would be a good way to do things. I was hoping to head up the route towards the more advanced FM synths, but for something as advanced as the FS1R, with it's additional filters etc., I'm not sure how that would be easy. My next target was actually the DX7II, which I don't yet own. But, when I get to the situation where it's more important for me to have a DX7II, then I'll up my ebay bid amounts from "waiting for a bargain" to "I want one now!".

Charlie, your computer probably already has java on it, as many web pages require it. You could try running the sample java program I uploaded to DXFiles, and see if it works.

I'm hoping to do some trial runs on Windows XP today or thereabouts. Testing on Windows 7 was .... inconclusive. The program works, but Windows 7 suddenly lost my USB MIDI interface half way through. It then wouldn't recognise it, even if unplugged and plugged back in again, until I rebooted. The interface also vanished from other MIDI enabled software such as Max/MSP. Searching around suggests that Windows 7 has "issues" with MIDI, so I don't know if this was a problem with my program or a general MIDI/Operating System problem. More experimentation will follow.

The program is designed to use fairly high resolution screens, in order to get sliders and parameter boxes for all basic parameters on the screen at once. But, the monitors that I tested on were even bigger in pixel terms (and physical size) than my mac, and my interface took up nothing like all of the screen. I think I'd better make the program realise that there is additional screen size, and use it appropriately.

Cheers,

Ross