Jump to content


  • Posts

  • Joined

  • Last visited

Contact Methods

  • Website URL

Profile Information

  • Interests
    Experimental music, studio gear, writing my own plugins.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JoaCHIP's Achievements

Professional Member

Professional Member (4/8)

  1. I've posted a video in the beta forum.
  2. The problem is not sporadic. It happens every time you load a project. Steinberg are shutting down VST2, and because of that many new plugins are often only available as VST3, so this problem will become increasingly severe. I will make a video very soon.
  3. Confirmed. This is especially fatal for this plugin: https://rhizomatic.fr/index.php/plasmonic/ The "Macros" at the bottom of the UI are normal VST parameters that also listen to CC. They are very fundamental to the sound, and their default setting is not zero. Hence, the Plasmonic is unusable in Samplitude. Steps to reproduce: Insert Plasmonic on a track. Select the "Going Rhythmic B" preset and notice the current setting of the macros (M1 - M8) at the bottom of the plugin's UI. Save the project. Restart Samplitude and load the project. Play a note using the Plasmonic plugin (either via the sequencer or simply by playing on a midi keyboard). Notice how all the macros are now set to 0, which is wrong. Can someone please tell me how to disable this behavior? I've been in contact with the developer of Plasmonic, and he assures me that these parameters are not special in way except that they listen to midi control changes.
  4. I didn't know that deleting these was risky. I guess I never used the specific functionality mentioned above. So now my suggestion is not to delete them, but rather that Samplitude should offer an option to store these files in a different location, the same way as LightRoom or RawTherapee can do with "sidecar" files. The reason I find the current behavior undesirable is: Imagine a large company with many sound designers using the same sound library on a shared network drive. If everyone uses a different DAW, the sample library folders will get spammed with all sorts of odd files that are only relevant to each corresponding DAW. A folder with 100 .wav files might end up containing several hundred weird files left by different "spammy" DAWs. And can we even be certain that e.g. the .HDP and .H2 files are even compatible across different versions of Samplitude in the future? If two users in said company use different incompatible versions of Samplitude, they might end up causing trouble for each other.
  5. Many many years ago I made a .bat file that removes these files. I use it often to clean up. This has never ever given me any problems. Raw processing software for photographers often produce similar files, e.g. RawTherapee and Lightroom. But these programs offer to store those files in a separate folder. It puzzles me that Samplitude doesn't have a similar configuration option, e.g. by offering an "Alternative peak file location" folder in the "Program / General" section where you also control the other paths. And if left blank, it could simply do what it does now. This is still high up on my wish list. In fact, one of my friends was so upset with this feature that he quickly abandoned Samplitude because he didn't want his entire folder structure full of these files.
  6. 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.)
  7. Thanks for your help, but I already did both before writing here: I have the latests drivers. I enabled said permission.
  8. 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?
  9. 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?
  10. 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.
  11. 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.
  12. 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.
  13. 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?
  14. I am quite curious about this too, but the link is now pointing to something that's not there anymore.
  • Create New...