Jump to content

Sascha Franck

Member
  • Posts

    1,138
  • Joined

  • Last visited

Recent Profile Visitors

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

Sascha Franck's Achievements

  1. Fwiw, I have a bunch of similar devices as well. Pretty much everything with a "let's slap this in kinda for free" interface is usually only working properly at 48kHz as long as it's not coming with dedicated drivers (inexpensive small mixers, guitar amp modelers, whatever). You can set Logic to 44.1, though, and sometimes it may work ok-ish, but as can be seen in this very thread, it's not a reliable thing.
  2. Fwiw, just some hours ago I opened Logic 9 under Snow Leopard on my old Mac Pro. What a wonderful version. Especially as the zoom functions are working as great as they ever did until the unholy event of LPX.
  3. When you downgrade to Kontakt 7 V9, it should be fine. V10 was horrible. The V9 installer (posted by NI themselves) is here: https://drive.google.com/drive/folders/1wakk3I4jKsxMRBmnu2bM1dXc4boNZEZE Fwiw, they already pulled V10 from their NA update options. Apart from that, all NI is an incredible ****show these days. Reaktor is running as bad as it gets under silicon, will likely never be updated again, the latter seems to be true for Battery 4 as well. Selling content, that's all that's left.
  4. Not sure I like any of this. I will most likely end up using lots of things, but in general, AI was exactly what music never needed.
  5. That's exactly what I'm doing, too (just a little different than you). Hear, hear... I only noticed recently that you can actually delete channel presets within the browser while pressing backspace. That's just completely weird as it's the only item you can delete there using a KC (usually, the selected track will be deleted). The lack of any file organisation (others than "save" and being able to delete channel presets") is not exactly making the thing look particularly hot. Which is quite bad as once you've got your presets done and sorted, it's absolutely excellent to navigate through them. The bare minimum they could do is adding a "show in Finder" option (which exists for other Logic-internal things too, let alone plugins such as Zebra and what not, all having a "show in Finder" option on board). Add some "auto refresh" library function (so files deleted/moved in Finder are automatically deleted/moved in the library as well) and you really wouldn't have to do much on the library itself anymore. Ah well ok, with an ever growing number of presets, a tagging/favourite system would certainly be nice to have.
  6. Not really, just all the additional information (author, patch comments, tags) is getting lost when converting them to aupreset.
  7. Btw, not to end up with doubled files inside Z2's own browser, I placed the .aupresets in "/Users/<username>/Music/Audio Music Apps/Plug-In Settings" instead of keeping them in "/Users/<username>/Library/Audio/Presets/u-he" Goes to show how all of Apples preset organisation could do with a major overhaul. You simply never know where they go, the library based paths even exist twice, so theoretically there's always 3 places to look for presets. Add to this that in "/Library/Audio/Presets/" different types of presets are allowed to co-exist. And add to this that many companies still decide to roll their own and save their presets in yet another place - which I can perfectly understand, given the mess that Apple's organisation displays.
  8. What is "KM"? Fwiw, it was reasonably fast just doing it within Z2, rightclick > select all in a folder > rightclick again > convert to native. But you have to do it for each and every folder.
  9. As I'm still setting up some things on my machine, I thought it'd finally be a good idea to convert the latest Zebra2 Factory and Legacy libraries (all available for free for users) to aupresets. I love using the Logic Library browser instead of the internal Zebra one, no need to even keep the UI open. Infofile inside the zip. https://drive.google.com/file/d/13lKw7eFZG4ipcub41a2gPqtGzXHT1LUD/view?usp=sharing
  10. Uli B.: "What's that betatesting you're talking about?"
  11. Perfectly horrible on all accounts. Most terrible UI, mediocre sounding OSCs (at best), a glorious waste of screen estate. There's around 20y old freebies doing a better job. If this is a hint of what Behringer's long awaited DAW might be like, good night!
  12. Well, it is kind of a problem, since Reaper seems to be doing better. For the time being, it's pretty much a rather academic issue, though, simply because I will very likely not run into any CPU issues any day soon - and I'd suspect that Apple will fix it at least one day. Oh, I am! --- Fwiw... just got a new Motu M2 (needed something as portable as possible) and it's almost phenomenal regarding latency. 3.5ms RTL at 32 samples, 44.1kHz. That's RME league. Unfortunately, they messed up their driver communication, so it's reporting just 2.5ms - which I couldn't care less about, but these wrong reports always come along with a recording offset. Which I already confirmed, all recordings are 45 samples late. I already adjusted that in Logics audio driver menu, but a decent audio interface should *not* require this (in general, you should only ever use that offset compensation when dealing with converters the interface has no idea of). Already reported, in case Motu doesn't at least answer, I'll reach for the Gearspace megathread, I guess no interface maker likes being mentioned there for releasing unreliable drivers. Apart from that, I will keep the M2 regardless of that, at least the offset is stable, so I just need to remember adjusting it in case I'd use another interface (I might not exactly notice, though - 1ms is like 30cm, so there...). Whatever, Motu really got their Hi-Z inputs right as it seems. Compared two DI tracks, looped beforhand, then one recorded through the Motu, one through my Line 6 HX Stomp and was then running both through Helix Native. After a tiny bit of input leveling, I couldn't tell the difference anymore. The feel when playing through the Motu is near to absolutely identical to the patches running in the hardware, too (and as I use them live and for recording since years, I know them pretty well), so that's fantastic. Btw, having a hardware modeler 1:1 compatible (minus the switching options of course) with a plugin is fantastic. And so far there's been no update fees at all (Line 6 just added a bunch of fantastic amps).
  13. This will perform very nicely. Personally, I'd consider the 1TB SSD, though. Ok, I have no idea about how you work (or plan to work), but for my needs, 1TB would be the bare minimum I could deal with - and I'd still have to connect an external drive often. Obviously, in case the latter is no issue for you, then go for it.
  14. I bought the fully maxed out version (24GB RAM, 2TB SSD). I actually don't think I will need the RAM so badly, so I could've kept it at 16GB, but more RAM possibly also translates to at least somewhat less SSD usage (less caching) and compared to the SSD upgrade it seemed sort of "affordable" (of course, none of those upgrade prices are even close to reasonable, so you have to calculate differently in Apple land). The 2TB SSD however was a must, even if I sort of cringed on the €690 (from 512GB to 2TB), simply because I know that this would be enough to have all relevant sample libaries, all actual projects (and some "permanent" things I need to practice for gigs and such) plus some "casual" things with me all the time. Add to this it's recommended to not fill your SSDs much above around 80% for maximum longevity. And as one of the key aspects of going for a Macbook was mobility, I couldn't see myself fooling around with an external SSD while having a good time in the garden's hammock or so.
  15. If you can afford it, defenitely. I just got mine last week and the power this little thing delivers is just stunning.
×
×
  • Create New...