SYNTH ZONE
Visit The Bar For Casual Discussion
Topic Options
#510143 - 10/28/24 11:13 AM SysEx files causing trouble in registration memory
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
Sysex files are causing trouble in registration memory by selecting undesired MFX

Here is what I'm doing:

I want a drum track. I select the style, I turn off the arranger part, press REC then I press Start and I record the drum part, once I'm done, I'll save it as an SMF. Then not to mess up and change the selection of the tones in the registration Upper 1, Upper 2 and Lower -> I go into the 16 track sequencer by pressing MENU -> I select Channel 4 , I press REC , I select "REPLACE", I also select STD, than I press START and I let it record (nothing) for 5 measures. I do this to all the channels except Channel 10 for the drum -> then I SAVE everything as a MIDI file.

By doing this when I play the MIDI file with the drum track, it won't change the tones in my Upper 1 and Upper 2 (in the performance memory) that is linked and saved with that MIDI file; however, for some reason if I have a PIANO selected in UPPER 1, the MIDI file won't change the PIANO tone which is good, but it will change the MFX to the MFX of the "TONE" that wasn't even highlighted (the LED button wasn't ON) during the drum recording.

Question: How can I get rid of the Sysex file that is still selecting the MFX?

Top
#510187 - 11/16/24 04:28 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
I'll try to describe the issue a little better:

What I'm trying to accomplish is to use a style to record only the drum track (as SMF) , and then have it linked with one of my performance memories. The problem is when I play back the recorded MIDI file (that has only the drum track on it) , it selects a different MFX for the UP1 tone. It uses the MFX of the Tone that was residing in UP1 when the drum track was created, even though the UP1 button wasn't even lit , and neither was the MFX button.

Before I link the MIDI file with the Performance Memory, I go into the 16 Track Sequencer, and record nothing on Track 4, by selecting STD and REPLACE, and it's still not getting rid of the MFX, it's still present somewhere in the SysEx files.

So unless I record the drum track right from the get go with the TONE that I want for Up1, this thing will keep changing the MFX back to the MFX of the TONE that was residing in UP1 during the drum recording.

This is a big problem, since what if I want to use a different TONE in Up1 (in the performance memory) , and that TONE has a different MFX, once I start playing the MIDI file, the MFX will be selected back to the TONE that was residing in UP1 when the drum track was created.

I even tried going into the MFX (holding the button), and turning it OFF for UP1 which is MFX1, and then do the recording, but it still records the MFX into the MIDI file.

At this point I have two options, I either record it with the desired Tone right from the get go, or I turn OFF the MFX in the performance memory for UP1.

I'm hoping that you might have an idea, what I should do.

Top
#510192 - 11/16/24 10:49 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
Diki Offline


Registered: 04/25/05
Posts: 14262
Loc: NW Florida
Easy solution might be to erase all sysex. There’s a parameter in the sequencer when you start a track from scratch that decides if it’s recording the Style track or KBD Part. Can’t remember what it’s called (away from my computer atm) but that might solve the problem.

I only sequence on a computer, so I'm not that familiar with the issue, but I do vaguely remember the issue a long time ago. When I get back to my computer I’ll look at the manual and see if it jogs my memory. There’s definitely some weirdness in the way the BK9 deals with trying to deal with a 16 channel SMF and still have 5 more channels left over for KBD Parts and the Melody Intelligence. It involves a sysex header if I remember.

I used to use the sequencer to record a style, then import the saved SMF into my DAW. I think I solved the issue by simply erasing all sysex, but that sometimes lost some drum editing. I simply recreated the edits if needed when I reimported the SMF to the BK9.

Wish I could help more, but that might give you the area to concentrate on.
_________________________
An arranger is just a tool. What matters is what you build with it..!

Top
#510197 - 11/17/24 06:34 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
" Easy solution might be to erase all sysex. "

I tried that, but the drum part was OFF. It sounded like a drunk drummer who's timing is off here and there.


" There’s a parameter in the sequencer when you start a track from scratch that decides if it’s recording the Style track or KBD Part. "

That would be a good solution to specify what to record. I wonder where can you specify that?

I even tried to use the SMF Make Up tools, after I recorded the style/drum track, by selecting the desired MFX for the instrument on track 4. I used the Freeze Data, and saved the SMF, and it still selects the same MFX when the recording was created.

I have an old Cakewalk DAW, but I'm not that familiar with it. I don't know how to setup the BK-9 with the channels in order so I can record directly to the DAW. If you could also give me some advise on that, I'd appreciate it.

Top
#510198 - 11/17/24 08:43 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
TedS Offline
Member

Registered: 04/28/06
Posts: 834
Loc: North Texas, USA
I don't really understand much about effects architecture. Coming at your issue from a different angle, what happens if you "lock" your keyboard tones (including Upper 1) before selecting the registration with the MIDI file? This should prevent the tone itself from changing; not sure about its related MFX.

The BK-9 has a pretty straightforward set of menus that determine which channels are output via MIDI, whether or not the output includes SysEx or just note-on, etc. If you scroll through the menus with the manual handy, you might be able to figure how to send the desired output to your DAW. My $.02.

Top
#510199 - 11/17/24 11:46 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
TedS -> " Coming at your issue from a different angle, what happens if you "lock" your keyboard tones (including Upper 1) before selecting the registration with the MIDI file? This should prevent the tone itself from changing; not sure about its related MFX."

I see what you are saying, but I don't have a problem with the tones, in other words they stay put. I also don't use a MIDI file to select my keyboard part tones, but I will give it a try.


TedS -> "The BK-9 has a pretty straightforward set of menus that determine which channels are output via MIDI..."

I will definitely have to look into it. I will have to learn this old Cakewalk and also how to set up the BK-9. I was hoping that I could just use the 16 Track Sequencer within the BK-9 for all my needs.

I had a Roland D-10 in the past that I used with a Roland sequencer an MC-50 MkII. I never used a DAW.


Diki - you said - "There’s a parameter in the sequencer when you start a track from scratch that decides if it’s recording the Style track or KBD Part."

I looked in the entire manual, I don't see an option for selecting style or keyboard parts for recording. If you find that option let me know, maybe I missed it in the book. I looked in Global, but there you can only specify Audio or MIDI, nothing else. Once you go inside the 16 Track Sequencer from the MENU , you can't record with the style.

Top
#510202 - 11/18/24 06:16 AM Re: SysEx files causing trouble in registration memory [Re: Diki]
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
I found the solution. I looked in the MIDI implementation manual/pdf, on page 17 the sysex codes for the MFX1/2 Tone part effects start with 18 00 02 00.

I got rid of the 18 00 02 00 and the 18 00 08 00, as a result MFX1 and MFX2 are not changed once the MIDI file starts playing.

So I can change the TONES in Up1 and Up2, the MIDI file has no influence on MFX1 and MFX2.

The 18 00 02 00 was clear to me that deals with MFX1, but the 18 00 08 00 I found by trial and error, and that seems to deal with MFX2, I just don't know whats the meaning of " MFX control 2 sens" is. See if you can make any sense what's the reasons that it works.


Attachments
Sysex delete not change MFX - 2.png

Midi Implementation - Page 17.png



Top
#510203 - 11/18/24 07:19 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
Actually the 18 00 08 00 is not on the chart, I made a mistake that is not what I'm erasing ( the 18 00 02 08 "MFX control 2 sens" ).

The one that I'm erasing is the 18 00 08 00. So than what is 18 00 08 00? It works, but I have no clue what it is and why it works...


18 00 02 00 SysEx definitely deals with Tone Parts Effects MFX1 and MFX2.


sorry 'bout the mistake.

Top
#510212 - Yesterday at 10:00 AM Re: SysEx files causing trouble in registration memory [Re: Dengizich]
Diki Offline


Registered: 04/25/05
Posts: 14262
Loc: NW Florida
I believe the ‘Control Sense’ parameter determines by how MUCH moving the MFX Control sliders on the front panel affect whatever parameter they are connected to. It’s a limited list sadly, not every MFX parameter gets slider access…

Once again, Dengizich, your dogged persistence pays off in useful knowledge..! 🙏🎹💡👏🏻
_________________________
An arranger is just a tool. What matters is what you build with it..!

Top
#510216 - Yesterday at 05:09 PM Re: SysEx files causing trouble in registration memory [Re: Diki]
Dengizich Offline
Member

Registered: 07/19/21
Posts: 88
Loc: Upstate NY, US
Thank You.

Top

Moderator:  Admin, Diki, Kerry 



Help keep Synth Zone Online