 |
|
| Still working on these MIDI projects? |
|
|
By Jace - Posted on November 14, 2006 - 00:55:56 (#20917)
Current version when comment was posted: 0.15 alpha |
|
|
i'm back to BeOS again after a long time... was wondering if SynthScan and related projects are still in development of any kind. i have three more synths that can be tested and added to the list if you're interested. Roland MT-32, Roland V-Synth XT, Alesis Fusion 8HD. i also have a MIDI capable t.c.electronic Fireworx effects unit and a Receptor (but i doubt the Receptor would respond like a synth; it's more like a glorified sampler). Oh, and i have an Akai S6000 sampler (again, don't think it would respond to an ID request, but who knows... i didn't have it last time we spoke about SynthScan, i think).
Cheers
|
|
| Nope also not working on R5 |
|
|
By nutela - Posted on May 30, 2005 - 14:11:59 (#16760)
Current version when comment was posted: 0.15 alpha |
|
|
Output (same as on Phos Beta6):
Welcome to the BeOS shell.
baron@:~# /PhosB6/home/SynthScan_0_15_alpha/SynthScan\ 0.15\ alpha
TweekFreek - Midi Device Auto-detect Scanner v. 0.15 alpha
1 MIDI ports detected.
Scanning /dev/midi/cmedia_pci/1
baron@:~#
|
|
| phos beta6 |
|
|
By nutela - Posted on May 30, 2005 - 12:06:32 (#16758)
Current version when comment was posted: 0.15 alpha |
|
|
Oh Sequitur works sort off, get crashes when I shut down my nord or use midi when I closed Sequitur all on Phos beta 6 I'll try r5 but I'm sick and tired of all this beta testing (not yours!) and want a useable BeOS again!!
Cya
|
|
| mailer deamon: user unknown |
|
|
By nutela - Posted on May 30, 2005 - 11:57:48 (#16757)
Current version when comment was posted: 0.15 alpha |
|
|
Tried to scan my Clavia Nordlead today but I don't get any info just found the midi port
Mail me at nutela at wolke7 dot net
|
|
| Those two Casios... |
|
|
By Jace - Posted on January 3, 2004 - 15:19:23 (#10322)
Current version when comment was posted: 0.13alpha |
|
|
I have a Casio MT-540 and a CT-460. These are nice little "toy" keyboards that were surprisingly supported by a few Sierra On-Line games way back when MIDI hit PC games (fully supported by Codename:Iceman, also by Space Quest 3 if you copy the driver from Iceman, and a few others in MT-32 mode, if you can put up with the instrumentation and channel limits of the Casio playing MT-32 data).
They are probably the last good cheap keyboard/synths Casio put out at the end of Casio's attempt at making synths (they used to make pro synths too). They are commanded like "dumb" synths, as you can see by sending them MT-32 game music MIDI streams, which works just fine mostly, except for the obvious differences in patches and capabilities (these Casios have no velocity capability, not even to respond to it!). I highly doubt they respond to queries of any kind. They never did for me.
Cheers to anyone who has these things. It's part of an era of fond computing for me...
|
|
| re: Baffled |
|
|
By euporia420 - Posted on August 24, 2003 - 15:32:06 (#8585)
Current version when comment was posted: 0.13alpha |
|
|
If your MIDI card works under BeOS and you are certain that the MIDI is connected properly (i.e. the synths work fine with Sequitar), then the synths must not support Midi Device ID requests.
This doesn't seem so unbelievable for the Casio synths, but I am supprised that the Korg wasn't identified as "Korg Unidentified Device". Korg generally seems pretty good at supporting general device ID requests and conforms to the same reply layout for most of their devices, including the system rom version bytes being in the same place.
I will try and find some specs on it, thanks for the info,
David Beckman
BeShare - :Wumpscut:
|
|
| Baffled |
|
|
By macsnafu - Posted on August 23, 2003 - 21:40:08 (#8582)
Current version when comment was posted: 0.13alpha |
|
|
I downloaded the app and tried to run it on a few of my midi keyboards, but I'm not getting any results. The program shows that it's scanning my midi ports (I've got two soundcards, but I just hook up one keyboard to one of them at a time), but it shows nothing, no recognized or unrecognized devices, no codes, nothing.
I tried my Casio MT-540, Casio CTK-650, and then my Korg X5. I've double-checked my midi cords and midi adaptor, and I'm baffled. I can't figure out why it's not working for me.
|
|
| David Beckham... |
|
|
By MYOB - Posted on June 24, 2003 - 06:26:17 (#7872)
Current version when comment was posted: 0.11alpha |
|
|
The Real Madrid joke is about David Beckham, a much hyped and not nessacerily very good Manchester United player who left recently to go to play for Real Madrid
I don't support Manchester United, hate the damn team.. so i'm glad their hype-monger is gone
|
|
| Real Madrid? |
|
|
By euporia420 - Posted on June 23, 2003 - 19:31:11 (#7867)
Current version when comment was posted: 0.10alpha |
|
|
Sorry, I didn't get your Real Madrid joke, must have been way over my head.
Anyways I appreciate all the testing I can get.
Thanks,
David
|
|
| why did you go to Real Madrid????? |
|
|
By moooooooo - Posted on June 19, 2003 - 09:59:17 (#7794)
Current version when comment was posted: 0.10alpha |
|
|
sorry David, just joking and that must be like the 53rd time you've heard that today!!!
Actually this is a cool app. I have an Alesis Quadraverb GT, an Ensoniq VFX SD and an Ensoniq Fizmo which i shall test this on and report back to you.
cheers
peter
|
|
| Sysex problems for USB MIDI in general, apparently |
|
|
By Jace - Posted on June 16, 2003 - 05:05:40 (#7761)
Current version when comment was posted: 0.09 alpha |
|
|
My Yamaha UX256 can't handle sysex dumps and such in Windows XP Pro. So I don't think the MIDI Oxygen 44 was the problem. Aparently the problem is in the lack garantee of data delivery on time due to the sloppy nature of USB timing.
I wasted almost 24 hours screwing with MIDI connections and interfaces and I accomplished NOTHING.
BE FOREWARNED
|
|
| Anything I can do to help? |
|
|
By Jace - Posted on March 17, 2003 - 18:36:42 (#6433)
Current version when comment was posted: 0.09 alpha |
|
|
I have the manuals for the TX802 and MT-32, so if there is specific info I could provide for you from them, let me know. Granted, this info is probably all over the net, but I'm offering anyway ;-) I also plan to grab a Yamaha FS1R as soon as two things happen at the same time: I can afford it and one appears on eBay!
|
|
| Yes, it's still being worked on |
|
|
By euporia420 - Posted on March 16, 2003 - 16:46:47 (#6413)
Current version when comment was posted: 0.09 alpha |
|
|
I've been very busy with school lately, but I try to work on it when I can. Sorry I haven't been able to add your synths yet. I need SysEx info for the Yamaha TX802. I have some for the MT-32 but I haven't looked into it yet. SynthScan should work with the MO44 just fine, many people have sent in results from these devices. The reason your synths don't show up is that they don't respond to general Device ID requests. This means I have to dig into SysEx documentation. So support will be added as I get the info and the time to work on them.
Your synths are definately high on my list.
-David
|
|
| TransTubeFex Responds, nothing else... What's new? |
|
|
By Jace - Posted on March 11, 2003 - 02:35:55 (#6343)
Current version when comment was posted: 0.08 alpha |
|
|
Hi there... I think I already emailed you the TransTubeFex reply to SynthScan, but I still can't get my Roland MT-32 or Yamaha TX802 to respond to it. This is still through the MO44 (but like I said, the TransTubeFex replies through the MO44 just fine). I'm getting a Yamaha UX256 soon via eBay, I think. Will try again with that, if I can get it to work w/BeOS
Still doing this project? Any new updates coming?
|
|
| MIDI Oxygen and SysEx |
|
|
By civello - Posted on November 20, 2002 - 00:40:22 (#4249)
Current version when comment was posted: 0.08 alpha |
|
|
Jace, I remember Eric Hackborn having trouble with Sysex requests where the MIDI Oxygen was in the picture, though what the exact problem was I can't recall. I guess one way to test it (cheaply) would be to get a MIDI cable that hooks to the joystick port of your sound card (providing that the joystick port is recgonized as a midi port...I know the number of cards is limited). Eric and I have both bumped up to the Yamaha UX/256 6 in 6 out midi interface...definitely no problems with sysex requests and that device. Pretty nifty little box.
-daniel
|
|
| I think I found the QS series problem - easy fix |
|
|
By euporia420 - Posted on November 11, 2002 - 21:58:51 (#4129)
Current version when comment was posted: 0.06 alpha |
|
|
Found the problem while looking at mMonitor input. I was accidently sending F0 7E 7E 06 01 F7...instead of F0 7E 7F 06 01 F7 as I should have sent. I was also expecting a 7E response instead of 7F.
It should work in 0.07 alpha...and your TX802 may talk back too. I will look into the TX802 specs in order to get the actual device request, but if it talks back with 0.07, be sure to send me that info as well. And if you can get me the Peavey message before 0.07 that would be cool as well.
Thanks,
David
|
|
| re: Identification |
|
|
By euporia420 - Posted on November 11, 2002 - 20:21:10 (#4127)
Current version when comment was posted: 0.06 alpha |
|
|
So I take it your Peavey sent back a SysEx message...was it recognized as "Peavey Unidentified Device"? That would be sweet, and adding recognition of the FX unit should be easy.
Did the other devices not respond with any message? Either an Unidentified Vendor/Device or Unidentified SysEx message?
If so, this would mean that they do not recognize or respond to the general device ID request and will have to be taken care of sepeartely. The QS8 is listed there because the way the app is set up, it should detect it if it responds to this general message (the Alesis DM5 does, and is detected on my system, the D4 should be the same); but it obviously doesn't. Luckily Alesis is wonderful about Documentation, so I should be able to find something. You are familiar with QS sysex, is there a SysEx request that calls the devices status, including say ROM version number and stuff...this would be a good SysEx string to use? I'm not sure about the Roland MT-32, but it can be detected (as SoundDiver detects it).
It should at this point recognize most any device that responds to general ID requests with the appropriate vendor name and Unidentified Vendor. But as your problem shows, this isn't the case for many synths. So far not detected are: E-Mu Morpheus, Korg Poly800, Kawai K1, Roland MT-32, Alesis QS8 (and probably the other QS and perhaps Nano synths), Yamaha TX802 and until last night the Yamaha TX7...this is the first device where I wrote seperate code to detect it. Not sure, but the 0.07 alpha TX7 detection may allow many oldschool Yamaha 6op FM synths to be detected as at least "Yamaha Unidentified Device", hope it will work with the TX802.
Remember, the lsitings are for generic support, which will work with about 60% of midi devices. The testing shows at 1% for a reason.
-Thanks,
David
|
|
| Identification |
|
|
By Jace - Posted on November 11, 2002 - 18:44:00 (#4126)
Current version when comment was posted: 0.06 alpha |
|
|
I'm planning to email a response from my Peavey TransTube Fex processor (it is a MIDI programmable FX box). Before I do that, I need to figure out why my Yamaha TX802, Roland MT-32 and Alesis QS8 will not respond to SynthScan. I know the older ones might just not support id inquiries, but the QS8 is already on your list! Any ideas? I have a MIDI Oxygen 44 (Rocks!) and also have tried the MIDI serial driver. No luck getting the QS8 to respond to SynthScan.
|
|
| Universal Synth Editor? |
|
|
By Francis - Posted on November 5, 2002 - 06:35:45 (#3960)
Current version when comment was posted: 0.03 alpha |
|
|
<<It will eventually be inegrated into TweekFreek, a native BeOS universal midi editor/librarian/tweaker.>>
Did you say "universal synth editor"? Well Alright! Wish you all the best of luck! Does a drag-n-drop interface creation for modules (ala Soundiver) seem like a possibility? Is TweekFreek already in development?
You should make an announcement to LeBuzz!
|
|
|
|
|
