Jump to content

JoaCHIP

Members
  • Content Count

    75
  • Joined

  • Last visited

Everything posted by JoaCHIP

  1. So, I have a track where I have multiple automation curves controlling various parameters in three different VST plugins. I have another track with the same three plugins. Now I want to copy all the automation curves from the first track to the other one without copying objects or anything else. Is there a fairly direct and simple way to do this? (Actually, I did manage to do this already, but not in a very logic way, so I already forgot what I did because it was sort of weird.)
  2. I'm not sure exactly when this happened as I usually run ASIO which works well. But it seems to me that (at least) the latest Windows 10 version (v1803, build 17134.112) has completely lost support for good old WaveIn (both WDM and MME in Samplitude). No matter how nudge the M-audio 2496 and Motu 2408mk3 drivers, recording only works in ASIO mode. This goes for all the software I have, not just things made by Magix. Software that I've been using for ages on the same two soundcards in Windows 7 and earlier are no longer working. The problem is that not all software has ASIO support. When googling around, I only find useless "tips" like "try updating your driver" (yes, did that), "try rebooting" (yup, did that), "try enabling permissions to the mic" (new thing in Windows 10 which only lists those Metro apps that noone has anyway) and such. Has anyone else experienced something like this with Win10? My hardware setup hasn't changed for years. Here's what Samplitude shows when trying to record in MME or WDM mode (regardless of using 16 or 24 bit record mode, and regardless of sample rate): I had the driver set up 16-bit resolution here btw. I've also tried SoundForge, VUmeter.exe, Wavosaur and OBS screen capture. All dead. Any ideas?
  3. JoaCHIP

    Windows 10 WDM and MME support broken?

    Thanks for your help, but I already did both before writing here: I have the latests drivers. I enabled said permission.
  4. JoaCHIP

    Moderator / Magix Representative

    Speaking of "Magix representatives", it would be quite interesting if someone from the Magic company could drop by this place and perhaps tell us a bit about their future visions. A few questions I would probably be curious about: Will Samplitude and Sequoia still be something that targets the pro segment (mastering studios etc.)? Or will Samplitude's focus be shifted towards more typical consumers, laptop musicians etc? Which parts of Samplitude do Magix see as essential? How will Samplitude be marketed in the future? (You almost never hear people talk about it online. What can be done?) How does Magix keep in touch with its userbase? Are bug reports and feature requests on this forum taken into consideration?
  5. Admitted, I haven't tried Ozone. But it's obviously made for mastering, and I don't think (or hope) that any mastering technician out there is relying on presets. Mastering is a tedious process that should be based on how the delivered material is, as well as what kind of final media (mp3/LP/cd/whatever) is the target. It could very well be a deliberate choice to make a point.
  6. JoaCHIP

    Samplitude Metadata Editing?

    TagScanner takes a little bit of getting used to, but I really like it a lot. PS: A word of warning about tagging .wav files. There are two ways of doing this, and it's about 50-50 what software uses which approach: 1) The correct way: Using RIFF data chunks. This works for both .wav files, .avi files and all the other many files formats that are based on the RIFF container (the first 4 bytes of such a binary file says "RIFF"). This is an official part of the whole RIFF container standard, and Samplitude does this correctly. 2) The wrong way: Using an mp3 format id3 tag placed in the .wav file. As far as I recall, VLC does this, and this practise should be strongly discouraged.
  7. JoaCHIP

    Moderator / Magix Representative

    I second that. Your effort is truly appreciated, kraznet.
  8. JoaCHIP

    Split object at each bar (or beat)

    I reached the same conclusion, so I assigned a hotkey to "split object" and repeated the hotkey sequence: Arrow-right, split, arrow-right, split ... It worked. But considering how Samplitude generally has a bazillion features, I still have a feeling that maybe there is a feature like this hiding in there somewhere.
  9. I have a fairly long .wav file object that I want to cut at each bar so that it becomes many separate objects of the same length. I could probably do this manually by enabling snap-to-grid and then cut using the mouse. But I wonder if there's an automatic way to do this?
  10. JoaCHIP

    Moderator / Magix Representative

    I am quite curious about this too, but the link is now pointing to something that's not there anymore.
  11. Keeping a VST wrapper around for the upcoming 32-bit apocalypse is actually really good advice.
  12. First Logic, now Cubase... it seems more and more DAWs are actively removing support for 32 bit plugins. This seems fantastically odd to me, considering how the vast majority of my current plugin selection consists of 32 bit VST plugins. Many of them are abandonware, and there will never be a 64-bit version. In fact, I think Samplitude could out-compete the other DAWs in this regard simply by doing nothing. (Thus keeping 32-bit VST support.) It's a silly world! PS: Of course, I really hope Samplitude won't follow this frustrating trend.
  13. They are not "necessary". If you remove them, they will be rebuilt automatically the next time you load the .VIP file. They don't need to be in the same folder. Samplitude just needs to be able to map a .wav file to the corresponding .HDP and .H2 files, whereever these are configured to be stored. Just like RawTherapee does. Imagine people also using different kinds of software (Acid, Soundforge, whatever) that also leaves similar files next to your .wav files. It could become quite a mess. Also, whenever I've made a folder full of .wav files ready to be exported to someone else who is not using Samplitude, I have to clean up the mess, because I don't want to deliver a folder full of "gunk". This looks unprofessional and can even cause confusion.
  14. This has nagged me too. Samplitude feels a bit spammy the way it spreads those .H2 and .HDP files all over your file system. Some sort of option to store them in separate folder would be absolutely lovely. The photo software RawTherapee already does a similar thing with photos: It has a "cache folder". I don't know how it keeps track of mapping the path to the external file to the file(s) in its own cache, but they seem to have solved that problem somehow. In fact, Samplitude could just use the system temp folder (see the %TEMP% environment variable). This would be optimal, as people might have already set up a clean-up mechanism to get rid of old obsolete files in their Temp folder using a scheduled task.
  15. This channel lacks something very obvious: A good reason to record something at a very high sample rate is that you want to play it back in slowmotion for special sound effects reasons. Example: Sometimes when I do a techno track, I might want a hihat to be lower and more gnarly. By playing it at half speed, I get that. Butif the sample was recorded at only 48 khz, and I play it back at just 24 khz, the treble will go up to 12 kHz max, and a lot of people will be able to tell that it lacks overtones. By recording at 96 khz or even 192 khz, you can play back stuff at half speed and still have good sound quality. Try it - it's really fun!
  16. JoaCHIP

    Having fun with Vita Jazz Drums

    The pipe sounds this way because I recorded it at 96 khz and play it back at 32 khz.
  17. I was testing the "Vita Jazz Drums" plugin that apparently comes with Samplitude, and I ended up with this madness. Enjoy! This is the "saxophone" that you hear in this track. boheme_cigars.mp3
×