Jump to content

tdor

Members
  • Content Count

    584
  • Joined

  • Last visited

Everything posted by tdor

  1. There was no change log, visually it's the same, same manual, functions all the same. I think the update is for all Independent Versions, i.e, for Pro, and the one that comes with the Suite. What you get depends on your license. I updated to 3.6 with X3 Suite with no issues at all.
  2. @Factor, You can do this with "Ranges", select a range from start to end of your project, the play cursor will stop at the end of the range. You can define multiple ranges. Then there is also the option to define the length of your project in project properties, first tab "General"
  3. 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.
  4. I see, the GUI, — I was thinking about ergonomics, the option to scale all windows by using vector graphics. Samplitude is still using bitmaps.
  5. "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
  6. What is this in reference to? desire, needs, cycles, I didn't post anything related to this 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 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.
  7. 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
  8. Samplitude X5 This would be tremendously helpful: The option to compare and edit midi notes parallel. The current midi editor is a pain in the brain for composition and orchestration. At least we got a score editor.
  9. I worked in Cakewalk, early version, like 20 years ago, then moved through Pro-Tools, Logic, Ardour, Digital Performer (my favorite for years) and a year ago I started using Samplitude. I am a bit torn between Digital Performer and Samplitude, both are great, very different workflows. I'd like to have Digix Performitude
  10. Software hopping is a waste of time, try some demos, decide, study the manual, functions, and master to use it. Working with X3
  11. Hi Phil, I bought Samplitude because of its reputation and excellent bundled plugins. Will contact tech support. Magix sells these plugins separately. I liked that plugin, too. Is there any decent free plugin that does can replace it? Merci, Thomas
  12. MIDI EDITOR, right under the keyboard, check if you have Cell view on, or just click on it. Interesting to read you found a trial version of Sequoia. Cheers, Thomas
  13. 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
  14. 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
  15. 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
  16. 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
  17. The default path, you should find in the Preferences of Independence: Windows\ProgramFiles (x86)\Magix\Independence Libraries The other path is: Windows\ProgramData\Magix\Independence Libraries
  18. I was wondering about such a function and what it might be called. In Finale (MakeMusic) that is Insert Measure. Thanks for this video, very helpful! Definitely something I will use as this is an essential function for composing. Thomas
  19. 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
  20. I can't answer this exactly. I suggest creating a restore point within Windows. Then run this installer for 3.6. I am 99% sure you'll be fine, but if anything goes south then wind back to your restore point.
  21. Check this out: US market: https://www.macprovideo.com/article/news/the-top-11-most-popular-daws-you-voted-for De market: https://de.ehomerecordingstudio.com/beste-daw-software/ Samplitude nowhere! The only other DAW I use is Digital Performer. Industry standard is AAF/OMF - most studios are DAW-agnostic
  22. 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:
  23. 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.
  24. I brought this up some time ago in another thread. If you never ever want or have to share your compositions as midi files then it won't matter. I find such data too valuable to convert into a format that another DAW cannot read.
×
×
  • Create New...