Midi Control 64 problem in X3

Author
Bach57
Max Output Level: -90 dBFS
  • Total Posts : 8
  • Joined: 2008/04/06 11:38:01
  • Status: offline
2014/01/12 15:06:27 (permalink)

Midi Control 64 problem in X3

I just upgraded to X3 Producer from 8.5 Producer. Transition good. However, when playing back previous files created in 8.5, X3 intermittently ignores sustain pedal data (Control 64) during playback. This results in notes being inappropriately sustained. When I reference the same files in 8.5, I do not have this problem. Is anyone experiencing this, and can someone provide insight regarding this issue?
 
Thanks
#1

5 Replies Related Threads

    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Midi Control 64 problem in X3 2014/01/12 15:13:23 (permalink)
    Check the "Prepare Using nnn Millisecond Buffers" setting in Preferences > MIDI > Playback and Recording. The current default value  is 250, try 500 (the SONAR 8.5 default value) or 750.
    #2
    Bach57
    Max Output Level: -90 dBFS
    • Total Posts : 8
    • Joined: 2008/04/06 11:38:01
    • Status: offline
    Re: Midi Control 64 problem in X3 2014/01/12 16:46:31 (permalink)
    I tried both 500 and 750 without any change. X3 repeatedly ignores the sustain off (0) control at the same points in the file at playback.
     
    Thank you. 
    #3
    Splat
    Max Output Level: 0 dBFS
    • Total Posts : 8672
    • Joined: 2010/12/29 15:28:29
    • Location: Mars.
    • Status: offline
    Re: Midi Control 64 problem in X3 2014/01/12 17:16:04 (permalink)
    Please update to X3D.

    Sell by date at 9000 posts. Do not feed.
    @48/24 & 128 buffers latency is 367 with offset of 38.

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
    #4
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Midi Control 64 problem in X3 2014/01/12 19:02:41 (permalink)
    First you need to determine whether SONAR is failing to send the message, or the synth is failing to respond. Watch the MIDI activity indicator at the top of the track meter for a flash when passing each pedal up event, assuming you can differentiate controller activity from note ons/offs. If not, you might need to copy the track and thin the notes events so you can see what's going on. Lowering the tempo will also help.  If you see the flash, and the synth doesn't respond, make sure the channel is correct. And what synth/patch is being used?
     
    If you don't see the activity indicator flash on a pedal up, that would be really surprising, and I'm not sure what would cause that right offhand. Is there a MIDI FX on the track?

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #5
    Bach57
    Max Output Level: -90 dBFS
    • Total Posts : 8
    • Joined: 2008/04/06 11:38:01
    • Status: offline
    Re: Midi Control 64 problem in X3 2014/01/14 00:08:39 (permalink)
    I am appropriate receiving midi sustain on and off messages for the problem track. I cloned the track (piano) and deleted the notes so that I could better observe the sustain pedal midi messages. However, when I played back the cloned track, the problem had been solved somehow. I cloned a another problem track (string pad) and noticed that the sustain problem had been resolved as well. The original tracks were still problematic; however, when I soloed both the problem track and the cloned track, I did not noticed a sustain problem. Can't figure out why this happened, but the cloning workaround appears to resolve the problem. I have quite a few tracks from different files which have the same problem, and I will be applying the same fix. 
     
    Thank you all for the help..Peace 
    #6
    Jump to:
    © 2025 APG vNext Commercial Version 5.1