Jump to content

tdor

Members
  • Content Count

    584
  • Joined

  • Last visited

Posts posted by tdor


  1. Be careful! Some of these files hold the data of your edits. For example edits on your audio file, or freeze data, etc. I have recently deleted a bunch of these files using Ultrasearch, then I reopened a VIP project and some edits were just gone.

    Safest way to clean up: Go to File -> Clean up -> Save complete VIP in... a folder of your choice. Open your file from within that new folder and check for errors. Then replace your original folder with this new one. Or, check what files the process copied, and delete all but those files from your original folder.

     


  2. "Samplitude Pro X4 Suite has been on sale for $149 for the past 4-5 months," that's right, of course I know that. Magix runs these Samplitude sales since January 2018
    Everyone here knows that. But not everyone wants to purchase X4, for various reasons.

    I was not talking about look and feel unless you misunderstood the word "design" - the term can be used for other situations than visuals, e.g. design of a circuit board, research design, design of an engine, etc.

    Since you have already gone through troubleshooting with tech support, that may be a good time to ask for a refund.

    Best, Thomas


  3. 2 hours ago, Cielspacing said:

    So, Mr tdor,  with due respect; sure there exist new features desire and needs out there. However they have  to be tempered with stability, promised features and functionality completion.

    What is this in reference to? desire, needs, cycles, I didn't post anything related to this :huh:

    Please read my post as some general advice, it's not Magix' fault that nvidia releases every once in a while crap products/and drivers, and they do. Further, nvidia licenses their design to different manufacturers, YMMV. Samplitude's GUI sure should arrive in the 21st century. Until then, make it work for you.

    EVEN MUCH MORE IMPORTANT, 15.1.1.236  is not the latest version - it's Build 387 now :excl: it has been praised by many users here.

    Further, for all who use X3, tech support informed me that there will be an update as well.

     


  4. Every Windows system is different, left alone the hardware we all use. Thus, there are many factors contributing to some "sluggish" behavior of X4, or any of your programs. You may need to optimize Windows for Audio Production, likely if you have an older PC.

    Check on your graphic card first, do you use NVIDIA or AMD? If it is NVIDIA, that could be the culprit in combination with X4. Not nvidia in general, but maybe your specific model. If you have an AMD card, the problem might be somewhere else. Same is true for ITG, many users he reported best results with integrated graphics. I use ITG combined with AMD to drive three screens, no issues. I had issues with an nvidia card, latency, and occasionally sluggish graphics, but not only in Samplitude.

    If you want a good score editor, have a look at MuseScore, export from Samplitude using xml.

    BTW: My X5 "screenshot" is a montage of Digital Performer and Samplitude


  5. Hi BX,

    Open a new project and write some controller data in a MIDI track, edit with the pencil tool, freehand or line drawing. You likely will see that you can overwrite anything without having multiple layers of controller curves.

    Delete all that, now record some MIDI data, notes, and controller events. Record over the same track using overdubbing. You will see, that your notes of the 2nd pass as well all controller data of the 2nd pass have been added, i.e., MIDI controller data on top of one another.

    I tried all that in another DAW and found a difference: When I recorded MIDI in overdubbing mode the controller data coming from my mod-wheel were nicely overwritten. That is what you want, but what you don’t get in Sequoia. That’s the end of the story, all you can do is delete a section and re-enter controller values.

    There might be also a chance, that your project misbehaves. When in doubt, start a new project and explore what you want to do.

    Cheers,
    Thomas


  6. Hi BX,

    Writing curves with the automation slider:

    Change the automation mode (e.g., latch) and move a slider. It writes by default a volume curve, if you move the pan knob at the same time, you'll get a pan curve. I don’t see a way to re-assign controller numbers here;  let’s say I want C11 written into an automation lane.

    Use a hardware controller and midi learn to control a slider in the mixer. Whatever controller data comes from your hardware, it will be converted into a volume curve, or a pan curve, or whatever you address.

    You lost me when you wrote you can write, e.g., C11 directly into an automation curve (A lane! Not MIDI). Using Samplitude X3 here, I checked the manual of Sequoia, couldn’t find it ad hoc and of course I won’t study a manual of a Software that I don’t have.

    Enlighten us how you achieved that.

    Thanks,
    Thomas


  7. Hey BX,

    Howdy howdy how did you manage to use an external midi controller to write any automation curves that appear as object automation? Let’s say CC11 does not appear in the midi editor but as CC11 auto curve layered over an object. Is that what you are saying?

    I don’t see how this works, I am using Samplitude X3, what parameters do you set in your Hardware Controller preferences? What do you choose from the Function Drop Down Menu?

    I thought what you expect what this software can do is simply not there, but I wonder if we are looking at the same thing.

    Please post a screenshot that shows your auto curves and your settings in the Hardware Controller.

    Cheers,
    Thomas

     


  8. Either method works fine, it's really a matter of routine and an eye for detail. I haven't used the curve mode much, it seems indeed more convenient than working in the midi editor.

    On another level, doing all this with a mouse seems so totally yesterday. I am considering to buy a drawing table (Grafiktablett) for drawing automation curves. Have not tried it yet, but I don't see why this should not work really well.

    Cheers,
    Thomas


    • You will need a plugin that allows real VST MIDI out, by default this option is always shown, for any VSTi, but that does not mean that it works. I used for this test MIDIChFilter from CodeFN42 https://www.codefn42.com/midichfilter/index.html
    • In your track to be converted (source), plug in MIDIChFilter, in the plugin menu enable VST MIDI out (top, provided by our DAW)
    • Create a target track, MIDI, enable VST MIDI out - Recording. In the header of the mixer, or in the track header MIDI in select menu.
    • Enable recording on your target track, hit recording in transport. It should record your source MIDI Track, real time. And voilà! There is your conversion.

    Sounds more complicated than it is, if there is a better way please post!

    Cheers,
    Thomas


  9. I found a way, real time, feels a bit like a hack, but it works: Using the VST Midi Out option at the plugin level, and the VST Midi Out - Recording at the Track Level.

    Hit playback with all your midi automation curves and record at the same time via the whole MIDI LOOP back thing on a new MIDI track. It's like bouncing your wave track in real time to a new audio track, just instead of wav we use MIDI.

    See:

     


  10. When you convert midi controller data to object automation, the data inside that object becomes inactive, so it won't conflict with your auto curves. In case you don't like  your automation curve edits,  you can delete all or parts of it and extract the midi data again form the object, it will merge.

    There is another function in the Objects Menu: Edit -> Apply MIDI Objects and Track Effects, that will remove all midi controller data that you converted into auto curves.

×
×
  • Create New...