1

(9 replies, posted in Atari)

I am looking forward to read it!

2

(9 replies, posted in Atari)

Oh, you know what? There actually is an English manual in the 2.0 zip file! Hah... Guess that solves the problem then. big_smile

3

(9 replies, posted in Atari)

I found some web source which can run through google translate:

https://translate.google.com/translate? … edit-text=

Perhaps it can be a good start. smile

4

(9 replies, posted in Atari)

Aha Wordpad... Ok. smile

Edit: Tried with Wordpad and it opens but looks terrible. Does it look good for you?

5

(9 replies, posted in Atari)

Hi Matej!

Very nice! Perhaps we can collaborate. I'm trying to understand the TMC 1.11 by using the program and by looking at the in-program help. I don't understand much of the description, but at least I see which keys are involved and so I can press them and see what happens.

Can you please send me a link to the manual you have found? For which version of TMC is it? I have found one that is included in the 2.0 version, but first I have heard that the 1.11 version is a better choice, and I can't figure out what format the manual is. It is named .DOC but it won't open with openoffice.

6

(9 replies, posted in Atari)

I'm new to the Atari8 but quite familiar with trackers including JCH ED and Sidwizard on the C64 as well as a few on the Amiga. Trying to apply my knowle on some POKEY tracker now, but it seems like the few bits of information is in Polish.

Is there any kind of reference material for TMC and/or Enotracker in some widely understood language? I'd prefer one of these trackers as I want to utilize stereo sound. Other trackers with that support would do too of course.

I'm familiar with the concepts enough to be able to figure things out myself, but it would be quite helpful at least to have a manual for the user interface including keys, and of course a POKEY reference and how it is mapped in the tracker. The general POKEY reference I guess I can read out from programming books, but the tracker specifics are harder.

Greatful for any kind of advice.

Yogi: It very much might do. If I print the midi data using the midi test in Kerberos, both my keyboards continuously send $fe or something similar. I've tried to disable that but not succeeded. I will try some more and experimenting with different keyboards and perhaps combine with routers or something.

jefftheworld wrote:

Are you using a very long midi cable, a passive midi-thru box or anything else that might cause more events than normal to fail?

Thank you for replying! Good suggestions with long cable. I was actually using 5 meters. Though it has to be it! Tried with a 1 meter cable. Played some. Still the same. sad Directly connected from keyboard to Kerberos.

If it was 1 of 1000 notes I would also accept a panic button, but this is far too frequent to be usable.

I might need to test a few more keyboards. The MicroKORG XL works much better than the A-300 Pro. With the later, I cannot manage to send chords. I can send polyphonic events, but only if I press the keys one by one, keeping hold of each key. Pressing down several at once results in one single note. This goes for the Kerberos only and not other instruments. With the MicroKORG XL I can play chords. So in some way the Kerberos has to be more sensitive than other devices. I have four other different midi keyboards to try with (Minibrute, Yamaha YS-200, Akai MPK 61 and E-Mu E-Synth). I also have two different active midi routers/splitters I can try.

I received my Kerberos yesterday. Managed to get it working close-to-perfect, but not all the way to goal. My remaining problem is that some note on/note off events are missed. This goes for two different midi keyboards (Roland A300 Pro and MicroKORG XL) combined with all the midi enabled applications on the cart as well as Station 64. Sid wizard too, even with the NameSoft device emulation enabled. Same result on my C128DCR as well as my C64 Reloaded.

When playing the keyboards, most of the note events are received and correctly processed. I can play melodies and chords. But, approximately one out of 50 events are missed, making it unsuitable for performance.

Anyone else suffering from this?

I've now added a udev rule as suggested. Now I can reproduce the issue not being sudo. The device is still resetting.

libusb package in use: libusb-1.0-0:amd64

(Please note that it is resetting no matter what command you issue, including --read)

Been there done that. smile No sorry, as you see I run as sudo so there is no permission issue. The USB is reset as a result of the command, so obviously I have permission to do nasty things with the USB.

Already tried different ports, but I will try on another computer as well.

As I am new to this site, I am unable to bump old threads. Therefore I create a new one. I just received my freshly bought flashcart, trying to program it using ems-flasher. Compiled under Ubuntu 13.04 GNU/Linux.

johan@crypt:~/Projects/ems-flasher-0.03$ tail -f /var/log/syslog&
[1] 4591
johan@crypt:~/Projects/ems-flasher-0.03$ sudo ./ems-flasher --write lsdj.gb 
Nov 26 11:33:01 crypt kernel: [166453.168511] usb 1-1.2: reset full-speed USB device number 9 using ehci-pci
Could not find/open device, is it plugged in?
Nov 26 11:33:06 crypt kernel: [166458.239807] usb 1-1.2: USB disconnect, device number 9
johan@crypt:~/Projects/ems-flasher-0.03$ Nov 26 11:33:07 crypt kernel: [166458.304794] usb 1-1.2: new full-speed USB device number 10 using ehci-pci
Nov 26 11:33:07 crypt kernel: [166458.393021] usb 1-1.2: New USB device found, idVendor=4670, idProduct=9394
Nov 26 11:33:07 crypt kernel: [166458.393032] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 26 11:33:07 crypt mtp-probe: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Nov 26 11:33:07 crypt mtp-probe: bus: 1, device: 10 was not an MTP device

As you can see above, the device disappears from the system when starting the ems-flasher and shortly after reappears. The device is working, as I am able to flash it using a Windows computer.