Replies created

 

Viewing 11 replies - 16 through 30 (of 71 total)
  • Jacob
    Participant

    Yep this is a bug introduced in the latest release, we will release a new version with a fix for this as soon as possible.
    The only workarounds right now are
    1) Exporting the midi with tempo 60.
    Or
    2) Turning on MIDI Out in Settings and then play through the track in Tracker while recording the midi in your host.

    Thanks for reporting in guys!

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @—Syt— said:
    The problem i have is when in tracker i do all the necessary work to my original drum tracks, then when i come to export the files down to the midi section, say the song length is 3 min 15 secs or 115 markers on the bpm, it only exports like half of the whole time line files and im not sure whats going on, before the update it would do the whole section no matter how long the files were.
     

    Yep this is a bug introduced in the latest release, we will release a new version with a fix for this as soon as possible (probably this week).
    The only workarounds right now is
    1) Exporting the midi with tempo 60.
    Or
    2) Turning on MIDI Out in Settings and then play through the track in Tracker while recording the midi in your host.

    Thanks for reporting in!

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @Mark Grace said:
    a delay in when the recorded snare hits vs the SD3 snare.
     

    So, running Studio One, when you play the transport in the tracker tab there is a delay between the recorded snare and the trigged samples, that is not there when using some other host or the Sd3 host?
    Does it matter wether you play with Follow Host turned off?
    There is a Delay option on each track (in studio one) that might cause some issue but it works for me…

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @Leo Trottier said:
    Looking forward to the next update.

    This is now fixed and will work in the next update, coming out hopefully in the beginning of the next year. Thanks for reporting.

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @Jim Saad said:
    Win 10 64
    Studio One Pro 64 3.5.4

    Then, when I go to export that midi info into Studio One so that it will trigger SD3, the hits do not line up.
     

    If the notes doesn’t line up at all, do you have the same tempo/tempo map in Studio One as you were using during export from Tracker?
    – If you export with a tempo of 120 in Tracker Export, you must use the same tempo in your DAW.
    – If you have a tempo map in Tracker and choose to use that tempomap during export, then you must use the same tempo map in your DAW.
    – If you have a tempo map in your DAW, you must import it to the Tracker and use it when exporting your Tracker Midi.

    Please let us know if nothing of this works, and you might have a different problem. (Like the notes lining up but gives you a Flam sound or something)

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @spell99 said:

    However, when I switch the drums to any of my SD2 SDX Kits they load but the minute I hit play SD3 crashes with a dump file.

    Yes, found the problem, Thanks for reporting in!

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @Chris Rollason said:
    Get an error “Time Type Mismatch”
     

    Have not heard about this error before, sounds like a Cubase issue, could it have anything to do with what is selected in Cubase -> Preferences>Editing Default Track Time Type?

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @macsearcher_1 said:
    Hello,
    Can someone here explain how drum augmentation works with Tracker.

    Not sure where your problem is from the information you wrote.
    There is a bugfix coming out in the next release, 3.0.3, that fixes a possible phase/flam issue during midi playback from your DAW or inside S3 Song Track when having large tempo changes over shorter distances.

    Or
    if the replacement/augmentation sounds good inside Tracker during playback, i.e no flams or phasing, then something might go wrong during your export.
    Then these export steps should help you.
    On export from Tracker, the main rule is that “The same tempo or tempomap used during Export must be used later during playback of that midifile”.

    1)
    The first option, and easiest, is to use a fixed tempo during Export, and then use the same fixed tempo in your DAW.

    2)
    If you already have a Tempo map (or any tempo changes) in your DAW that you want to use, you need to import this tempomap into the Tracker (“Load Tempo Map from midi file”, in the Tempo Map menu on the left side in the Tracker Tab). Then upon Export, you choose the Tempo menu option “Tracker Tempo Map”.

    3)
    The third option is to Create a tempo map in Trackers “Find Tempo”, then select to use this tempo map on Export from Tracker. The tempo information will be stored inside the midifile and must then be imported to your DAW.

    Using any of these 3 options, you will export the midifile in the same tempo(s) as you playback the midifile.

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @megapeng said:
    i loaded a 2.5 hour wave and it crashed (48khz 24 bit) as mentioned above what is the max wav lenght allowed?
    dave  

    Yes, I could reproduce your crash. If memory allocation fails during a part of the analysis it could crash. Will fix this and add an alert dialog telling the user what happened. So, there is no limit to what you can load in Tracker except for what your RAM can handle since parts of the analysis is memory heavy.
    I have also added your shortcut suggestions on our feature requests lists.

    Thanks for reporting and the feedback!

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @John said:
    Hi,

     

    oh, missed your reply..

    Jacob Norén - Toontrack
    Coder

    Jacob
    Participant

    @David Snow said:
    Again, the is already a variable tempo map in DP, and that map cannot be undone as all audio in DP follows it.
      

    When you export Midi from Tracker, you will have to use the same tempomap as you will use upon playback in DP.
    So since you have a tempomap in DP, you must export that tempomap from DP to a midifile and import that midifile in the tracker main window (see attached pic).Please make sure that the imported tempos are the same as in the Host otherwise it could be signs of a bug.
    Then do your tracking and in the Exportview, export with the “Tracker Tempo Map” option selected in the tempo menu.

    The other way would be to create a tempomap in Tracker Find Tempo, then do your export with the “Tracker Tempo map”. Then make sure that DP loads the tempomap from the exported midifile.
    In both these scenarios the Host and Tracker Export are using the same tempomap.

    The other options in the tempomenu are:
    1) When exporting with Follow Host, it will only export with a fixed tempo that is returned from the host playhead position.
    2) You can export with the tempomap from the S3 Songtrack tempo editor.

    I hope this helps, otherwise get back to us.
    // Jacob
    tempomap.png

    Jacob Norén - Toontrack
    Coder

Viewing 11 replies - 16 through 30 (of 71 total)

No products in the cart.

×