Jump to content

Victor Peters

Members
  • Posts

    12
  • Joined

  • Last visited

Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks again, JoseC. I will change the title of the thread. Cheers.
  2. Thanks JoseC. That did the trick. After disabling the option "Always use Sysex banks for MIDI files" and loading the original Mission Impossible tune , I now see the GS Reset at the beginning of the song in the SysEx Viewer/Editor and the other SysEx messages in the Event List. I'm so greatful for your help. Thanks to everyone who participated in this discussion.
  3. Well, the event list in Reaper and Sekajiu clearly show that the GS Reset is actually performed/sent at the end of the song. But somehow Cakewalk places all the SysEx messages at the beginning of the song or at least executes them when opening/loading the MIDI file...
  4. When I open/load the MIDI file with the Mission Impossible tune in Cakewalk and look at the events in track 1, I only see Program Change ("Patch"), Control Change ("Control"), Registered Parameter Number ("RPN") and Non-Registered Parameter Number ("NRPN") events. No SysEx. Why is it that I can't see the SysEx events in the Event List?
  5. Hi, Thanks all for helping me out, but I'm not quite there yet. For starters, the MIDI interface I'm using is a Roland UM-2ex (1 x MIDI-in, 2 x MIDI-OUT) USB-MIDI interface. If the interface or its driver were at fault, than I would expect that Reaper and Sekaiju also would have trouble playing back the Mission Impossible file. Or all other MIDI files I own. So why won't I use one of these two sequeencers/DAW's? Well, in short, I like the interface of Cakewalk better. I've added some screen shots of all three programs, to show you what information is displayed after having opened/loaded the Mission Impossible MIDI sequence. The differences are confusing to me and I would like to share this with you, along with a brief description. Reaper Above is the screen shot of the full and unfiltered MIDI Event List in Reaper of track 1. This is the track where all SysEx events reside according to Reaper. Tracks 2 to 17 contain all Control Change and Program Change events for MIDI channels 1 to 16 and from track 18 and upwards the actual Note events are shown. From the above image you can clearly see at what song position the SysEx messages are sent to the sound module. The sound module receives a GS Reset at 1.1.00 and shortly afterward track/channel 11 is switched from 'normal' to rhythm at position 1.1.17 and the song is played back properly. At the end of the song (at 91.4.00) a GS Reset is sent again to undo all the changes (SysEx, PC, CC, etc.) made by the song during play back. Sekaiju Above you see a screen shot of the MIDI Event Editor in Sekaiju of the same original and unaltered sequence. The Event Editor shows a list of all MIDI events, including SysEx, Control and Program Change and Note events, with the song position at which they occur. According to this list all SysEx events in the sequence are on track 2 !!! (see highlighted lines in the image). The track number precedes the actual name of the track in the Track column. This seems odd to me. Why the difference? Cakewalk by Bandlab Above you see a screen shot of the SysEx viewer/editor in Cakewalk (same original, unaltered song opened/loaded). In the list with SysEx messages you can see that they all have "Auto" checked/activated. I'm not sure , but I think this means that al SysEx messages with the check mark in the list are sent to the sound module on opening the MIDI file. To find out if I was right, I removed/unchecked the check marks for all messages in the list and saved the MIDI file under a different name. I restarted Cakewalk and opened/loaded the altered file. Upon opening I wasn't asked if I wanted to send the SysEx data to my sound module. But when I opend the SysEx viewer/editor, all SysEx messages were gone! The above screen shot is also from Cakewalk, but it's the MIDI Event viewer/editor (after having opened/loaded the original, unaltered MIDI file again). I've cycled through all tracks (using the "Tracks" drop down) looking for any track and/or song position where any of the SysEx events from the list in the SysEx viewer/editor might occur. But I can't find any track contains a spot where a SysEx event is fired. Therefore I conclude that the "Auto" check mark in the SysEx viewer/editor means that these events are automatically fired upon opening/loading the MIDI file. That might also mean that these events are fired to close to one another for the sound module to be able to handle them properly. I wonder if it is possible in Cakewalk to fire a SysEx event (on from the list of SysEx events in the editor/viewer) at a specific position in the middle or at the end of a song. The Mission Impossible song performes a GS Reset again at the end of the song in both Reaper and Sekaiju, but not in Cakewalk. Also, Cakewalk keeps playing after the end of the song, the other two programs simply stop at the end of the song because there's no more data in any track to play back.
  6. Thanks for all the input. I'm at work now, but will try all suggestions and report back.
  7. I'm using Cakewalk by Bandlab (version 2019.09 Build 70, 64-bit). Since I purchased my Windows 10 laptop (in September 2017) I have NEVER used any previous version of Cakewalk or Sonar before installing Cakewalk by Bandlab. So Cakewalk by Bandlab has been the first and only version of Cakewalk / Sonar that I've installed and used on my PC. The MIDI driver mode is MME by default and changing it to UWP doesn't solve the problem. I'm a Cakewalk novice and noticed that I'm unable to see any System Exclusive event in the Event List view. Not even the GS Reset message at the beginning of the song. Despite having made sure that all MIDI data are displayed in the Event List view. I found an option in the Preferences dialog [under File > Ask Before Sending System Exclusive (When Opening Project)] and activated it. Now when I open the original MIDI file, I'm asked if I want to send the SysEx message in the MIDI file to my MIDI gear and upon confirmation the GS Reset is sent to and executed on my SC-880. I can verify this by looking at the flashing of the display and the fact that after the event has been fired all channels are set to instrument 1 in bank 1 ("Piano 1" for all normal parts, drum patch "STANDARD 1" for part 10). Why can't I see the System Exclusive events in the MIDI file in Cakewalk by Bandlab? Should I activate an option in the Preferences dialog that I haven't discovered yet? I can see the SysEx events in Reaper and I can see them in a free MIDI sequencer named Sekaiju (version 5.7). When I play the MIDI file in Reaper all SysEx data are sent to my SC-880 and part 11 is switched to become a thrythm part, thus sounding as it was meant to be by the programmer of these sequences. When playing the MIDI file in Sekaiju, the GS Reset message is sent and the module is reset to GS, but the SysEx message to switch part 11 to rhythm is not sent and/or received by the sound module. This time I've attached the original, unedited commercial MIDI file. I also attached another commercial MIDI file that utilizes the same mechanisme for switching a normal part (part 11) to become a rhythm part and has the same problem in Cakewalk by Bandlab. When playing both files in Reaper, the module does the GS Reset and switches part 11 to rhythm mode. Sekaiju on the other hand plays the Flintstone tune properly (switching part 11 to rhythm), but doesn't do so while playing the Mission Impossible tune. Since I'd prefer to use Cakewalk by Bandlab, I would likt to find out why that is and would like to get this issue resolved. Edit: I stated that Sekaiju doesn't play back the Mission Impossible tune properly. The reason for this is that the uploaded file is corrupt. After copying the original file with its original 'cryptic' name from my external drive to my hard drive and renaming it, soemhow in this process the file got corrupted. When I play back the original file from the external drive, Sekaiju plays back the song properly. To make sure no SysEx, CC or PC or oher data remained behind in the sound module prior to loading the song into the sequener, I performed a factory reset before loading each song. It turns out I was wrong. I've attached the original, unaltered file as-is (with its original file name, 096103_G8.MID). I hope it doesn't get corrupted again. Copyright notice: Both attached files are copyrighted. Please use them only to examine this issue. Do not distribute them in any way. Thanks in advance for any advice you could give me. Theme from Mission Impossible.MID Theme from The Flintstones.MID 096103_G8.MID
  8. I'm currently at work, so I cannot verify what I'm about to state with the information in the original or edited MIDI file. Since I edited the MIDI file with Reaper to strip all channels but channel 10 and 11 from the sequence, I had to export the 'project' in Reaper to a MIDI file. The export dialog has a lot of options that I left at default. But because of this the attached file may have a different amount of tracks and those tracks may (or may not) contain the exact same data as the original did. What I do know is, that the original sequence has some sort of master track that contained all SysEx messages. At 1.0.00 there's a GS Reset command to initialize the sound module and (I believe) at 1.1.17 there's the SysEx command to switch part/channel 11 from 'normal' to rhythm. In a Cakewalk knowledge base article (https://www.cakewalk.com/Support/Knowledge-Base/2007013095/System-Exclusive) it is suggested that adding a statement to TTSSEQ.INI might solve the issue. I found the INI file and edited it accordingly. But restarting Cakewalk and playing the original MIDI file still causes the same problem.
  9. I think that I'm missing your point. Indeed, I could perform the switch manually, but then I would. also need to delete the GS reset SysEx message at the very start of the sequence. My old Voyetra MIDI Orchestrator Plus and Voyetra Digital Orchestrator Pro were able to play back these sequences properly on my SC-88 back in the day. I would expect that Cakewalk, which has a long standing reputation for sequencing on PC, would be able to play the songs properly too. The SysEx messages are on track 1, 3 and/or 3 of the attached MIDI file.
  10. Hi, I've searched this forum on the topic but couldn't find an answer. Hopefully here someone has an explanation (and maybe solution) to the following behaviour of Cakewalk. I have some commercially produced MIDI sequences for the Roland Sound Canvas series of synthesizer modules (SC-88 and up) that I've purchased several years ago. After years of doing nothing with synths and sequencing (I sold all my gear, kept only an acoustic guitar) I recently purchased a Roland SC-880 Sound Canvas module and started doodling with it. Some of the commercially produced sequences use System Exclusive messages to enable the Sound Canvas module to have a second rhythm track (instead of only track/channel 10). The SysEx message (F0 41 10 42 12 40 1A 15 02 0F F7) effectively switches part/channel 11 from a 'normal' instrument part to a rhythm part, thus adding a second rhythm track to the 16 track/part sequence. Playing back the sequence in another sequencer/DAW that I own (Reaper) all parts sound as they should. Part 11 is a rhythm part and for that part a sound effects rhythm kit is selected. When I play back the same sequence in Cakewalk, the sequencer/DAW does not seem to recognize the System Exclusive message and does not change part/channel 11 to become a rhythm part and makes the sequence/song sound wrong. I've attached the MIDI file to this post, but have stripped all the non-rhythm tracks/parts from it (I used Reaper for that). Be aware that it is copyrighted material and is only provided as a means to demonstrate the issue I'm having with playing back the MIDI sequence. Can someone help me get Cakewalk to properly handle System Exclusive messages such as the one in the provided sequence? Thanks in advance. midi_export.mid
  11. Hi, I just downloaded and installed Sound Canvas VA and I'm trying to get it to work and play some of my GS MIDI files. I was able to play MIDI files throught the Sound Canvas VA in Reaper (https://www.reaper.fm/), but I'm unable to do so in Cakewalk by BandLab version 2019.03 (build 20l, 64 bit). I can't find a way to direct the output of the (MIDI) tracks to the Sound Canvas VA VST plugin. I've had a hardware Sound Canvas (SC-8850) in the past and was able to play the MIDI files through that unit, but it seams that Cakewalk doesn't recognize the Sound Canvas VA as a VST-instrument that can handle MIDI data. Any help to get this working before the trail expires would be very appreciated.
×
×
  • Create New...