Getting Synth PCM Samples and more

[inkapmb]

I was trying to dump Synth PCM Samples from e2 synth with the dump_extracted_pcm.py script but I have some issues, in particular to open midi port with mido.open_input('electribe') saying OSError: unknown port 'electribe'. I patched it as

mido.open_input() port = mido.get_input_names()[0]

then I got new issue with the e2SysEx.read_cpu_ram() function, therefore I fill I might misunderstand the process to dump Synth PCM samples.

What I did is :

1. turn on my e2 synth
2. plug USB from e2 synth to my computer
3. lsusb to ensure that e2 synth is detected by my computer
4. then python scripts/dump_extracted_pcm.py

I hope @bangcorrupt you can detail the steps needed.

In addition, I wonder that if we can use e2SysEx.read_cpu_ram() to get Synth PCM Samples we should be able to get the other samples of the e2 synth ?

Thank you in advance for your attention to my questions!

[bangcorrupt]

The steps you're taking look correct, there is likely an issue with the port name.

mido.get_input_names()[0]

What is the output of mido.get_input_names() and mido.get_ouput_names()?

then I got new issue with the e2SysEx.read_cpu_ram()

Can you describe the issue and post any logs you get from the script?

get the other samples

There are no other samples.

[bangcorrupt]

You also need to make sure you have patched the firmware using the synth-pcm-dump branch.

[inkapmb]

Okay, so if I understand right :

1. I have an original e2 synth
2. I have to patch it with synth-hacked-SYSTEM.VSB
3. then revers it in to synth version with synth-revert-SYSTEM.VSB
4. then I will be able to dump Synth PCM Samples with python scripts/dump_extracted_pcm.py

am I right ?

[inkapmb]

There are no other samples.

In addition when I mean the other samples, I mean sample from 001 (SubBeef) to 325 (Oldie)

[bangcorrupt]

No, you need to install synth-hacked-SYSTEM.VSB patched using the synth-pcm-dump branch I linked above.

Then you will be able to dump synth PCM samples using scripts/dump_extracted_pcm.py.

I mean sample from 001 (SubBeef) to 325 (Oldie)

These will be included, it will dump all the samples as one file. It should take about a minute and will look like it is doing nothing.

If you still have issues with the script, post the logs I asked for above.

[inkapmb]

Okay, so I did patch my e2 synth with synth-hacked-SYSTEM.VSB patched using the synth-pcm-dump branch you linked above, then I tried to dump with scripts/dump_extracted_pcm.py.

It gaves me OSError: unknown port 'electribe2 sampler electribe2 s' as the first time.

What is the output of mido.get_input_names() and mido.get_ouput_names()?

>>> mido.get_input_names() 
['Midi Through:Midi Through Port-0 14:0']
>>> mido.get_output_names()
['Midi Through:Midi Through Port-0 14:0']

and lsusb gave me Bus 001 Device 007: ID 0944:012e KORG, Inc. electribe2 sampler

Then I added port = mido.get_input_names()[0] before this line

and it gave me :

Traceback (most recent call last):
  File "./hacktribe-synth-pcm-dump/./scripts/dump_extracted_pcm.py", line 8, in <module>
    e = E2Sysex()
        ^^^^^^^^^
  File "./hacktribe-synth-pcm-dump/scripts/e2sysex.py", line 37, in __init__
    self.global_channel, self.id, self.version = self.search_device()
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: cannot unpack non-iterable int object

[bangcorrupt]

>>> mido.get_input_names() 
['Midi Through:Midi Through Port-0 14:0']
>>> mido.get_output_names()
['Midi Through:Midi Through Port-0 14:0']

This shows that mido can't see the electribe, it would be listed after 'Midi Through...'.

What is the output of mido.backend?

In a bash shell, what is the ouput of aconnect -l?

[inkapmb]

What is the output of mido.backend?

gaves : <backend mido.backends.rtmidi (loaded)>

In a bash shell, what is the ouput of aconnect -l?

~$ aconnect -l
client 0: 'System' [type=noyau]
    0 'Timer           '
	Connexion À: 144:0
    1 'Announce        '
	Connexion À: 144:0
client 14: 'Midi Through' [type=noyau]
    0 'Midi Through Port-0'
client 144: 'PipeWire-System' [type=utilisateur,pid=3656]
    0 'input           '
	Connecté Depuis: 0:1, 0:0
client 145: 'PipeWire-RT-Event' [type=utilisateur,pid=3656]
    0 'input 

[bangcorrupt]

~$ aconnect -l
client 0: 'System' [type=noyau]
    0 'Timer           '
	Connexion À: 144:0
    1 'Announce        '
	Connexion À: 144:0
client 14: 'Midi Through' [type=noyau]
    0 'Midi Through Port-0'
client 144: 'PipeWire-System' [type=utilisateur,pid=3656]
    0 'input           '
	Connecté Depuis: 0:1, 0:0
client 145: 'PipeWire-RT-Event' [type=utilisateur,pid=3656]
    0 'input 

Linux can't see the electribe as a MIDI device, you need to fix that first.

[inkapmb]

Linux can't see the electribe as a MIDI device, you need to fix that first.

I'm currently searching but I dont have any clue of why and how to do it for the moment...

[inkapmb]

Well, I guess it was just an ALSA bug that didn't recognize the device, but after a reboot, everything worked fine and it was recognized. Then I did pyhton3 scripts/dump_extracted_pcm.py and a few errors occurred, but I think it worked. Here is the output :

python3 ./scripts/dump_extracted_pcm.py 
DEBUG:root:Initialise SysEx
INFO:root:Found electribe
INFO:root:Global channel 0
INFO:root:Firmware version 2.2
DEBUG:root:Getting decompressed PCM from CPU RAM
DEBUG:root:Called read_cpu_ram
DEBUG:root:Sending message

MidiInAlsa::alsaMidiHandler: unknown MIDI input error!
System reports: Resource temporarily unavailable

MidiInAlsa::alsaMidiHandler: unknown MIDI input error!
System reports: Resource temporarily unavailable
DEBUG:root:Received response
DEBUG:root:Decoding binary
DEBUG:root:Writing pcm-dump.wav

[bangcorrupt]

That looks right, you should have pcm-dump.wav in the same directory.

MidiInAlsa::alsaMidiHandler: unknown MIDI input error!
System reports: Resource temporarily unavailable

I get these errors too, I think it's just because it takes a long time.

[inkapmb]

I listenned to the wav created and at ~ 50 second it is totally noise, there is no wave form... do you have the same ?

In addition, if I want hacktribe now that the sampler firmware is installed on my e2 synth (originally) did I need to use sampler-hacked-SYSTEM.VBS or synth-hacked-SYSTEM.VBS ?

[bangcorrupt]

at ~ 50 second it is totally noise

It should all be audio samples. Do you get exactly the same thing every time? I will try it when I can.

sampler-hacked-SYSTEM.VBS or synth-hacked-SYSTEM.VBS

If you have any version of Hacktribe or the sampler firmware installed use sampler-hacked-SYSTEM.VSB.

[inkapmb]

It should all be audio samples. Do you get exactly the same thing every time? I will try it when I can.

Yes, It tried two times and it was the same, okay let me know

If you have any version of Hacktribe or the sampler firmware installed use sampler-hacked-SYSTEM.VSB.

Perfect, thanks

[inkapmb]

I retried to it, then it worked... wtf
So now I have all the sample from the electribe Sampler, but my goal wa to have the Synth working in hacktribe. According to this

Dumping the raw PCM data from flash will definitely happen. The pianos and some other instruments are multi-sampled, I can probably get this working at some point. The Osc Edit knob applies a drive effect, I hope I can get this working one day.

It is not possible for the moment ? (I might understand that lower in the discuss, you may have success to get synth sample in wav, but that doen't results is the same original synth fro the e2)

[bangcorrupt]

I retried to it, then it worked

`MidiInAlsa::alsaMidiHandler: unknown MIDI input error!
System reports: Resource temporarily unavailable

I think the ALSA MIDI input gets flooded with too much data and sometimes just fails.

trying to dump Synth PCM Samples from e2 synth

I have all the sample from the electribe Sampler

If you ran this with what was originally a synth, you should have got the synth samples.

It is not possible for the moment

I'll work on getting the instruments and drive working at some point, but it's unlikely to be soon.

[inkapmb]

If you ran this with what was originally a synth, you should have got the synth samples.

Perfect !

I'll work on getting the instruments and drive working at some point, but it's unlikely to be soon.

Okay thanks a lot for what you did for this project and your explanation! Maybe, I'll dig deeper to work also getting the intrument and drive work later ! And thanks again !!

[inkapmb]

So Tried to dig a bit into synth-revert-SYSTEM.VSB with ghidra, add the extension ghidra-blackfin and openned the binary with it, however I cant figured out how to use AM1802.pspec and ARM.ldefs.

@bangcorrupt Do you have any advice ? In addition, how do you set the offset adress in ghidra to avoid the header ?

Thanks a lot in advance

[bangcorrupt]

I answered in #89.

[GeorgDub]

Can somebody upload the dumped synth pcm, because i already get the synth firmware run on my sampler, but i have the problem that my pcm is still from sampler and so the pointer of the firmware show on pcm that dont exist, now im locking for a synth pcm dump to try to transform my sample finally into a synth

[GeorgDub]