Jump to content

Sascha

Advanced User
  • Content Count

    1,417
  • Joined

Everything posted by Sascha

  1. Thanks We'll feed our shop starting on Monday. Meanwhile, some others already have the items on stock (for instance, I've seen Thomann, Music Store Cologne & digitalaudioservice in Germany). Steve had started shipping the stuff by the beginning of this week. The regular 'boxed' pricing for non-Sam users is 199€/USD for AM suite, the same with VariVerb and 119,- with the VE suite. I've heard from Steffen Holly that Sam/Sequoia users get 50% off. I cant't remember the exact discount for additional serials (e.g. if you own a boxed product already, as the printed manual & CD covers all 3 products). To my knowledge, that was at least 20%, but I have to ask again next week.
  2. Hallo zusammen, wir haben heute die Samplitude-Webseite aktualisiert und die ersten Infos zu den 'unbundled' VST-Plugins zusammengestellt, und ich denke, es ist an der Zeit, diesen neuen Teil unseres geliebten Forums als eröffnet zu betrachten und alle hiermit herzlich zu begrüßen, die bereits zu diesem Zeitpunkt hier hereinstolpern Inzwischen werden die ersten Pakete der Plugins an Läden und Vertrieb ausgeliefert. Wir haben keinen großen, hochtrabenden Marketingaufwand betrieben und generell als Infos zu den Plugins diejenigen eingepflegt, die sich im Handbuch finden. Somit findet jeder Interessierte verlässliche Informationen aus erster Hand, um sich einen ersten Überblick über das zu machen, was ihn/sie erwartet, ohne dass eine komplette Demo-Installation von Samplitude erforderlich wäre (ich würd's natürlich trotzdem tun...). Natürlich ist 'Selber-Schrauben' schon besser... Gut, es fehlen noch Demoversionen der Plugins. Diese sollten Anfang kommender Woche verfügbar sein, sobald wir das Installer-Paket fertig geschnürt und getestet haben. Nun denn. Dieses Forum sollte idealerweise ein Treffpunkt sein für alles, was sich mit den Plugins beschäftigt, insbesondere Wünsche, Anregungen, Kritik, in Punkto zukünftiger Versionen, Bugs (die ja bekanntlich nie auszuschließen sind), etc. Desweiteren habe ich vor, ein paar nicht so bekannte Details zu den Plugins zu geben, Hintergrundinfos, versteckte Features usw., also Dinge, die sich im Handbuch nicht finden. So weit es die Zeit erlaubt... Wir würden uns wünschen, wenn dieses Forum dem Community-Gedanken entsprechend einen Ort zum Austausch von Ideen von Usern für User darstellt. Ich denke da etwa an oft gestellte Fragen wie etwa 'könnte mal jemand beschreiben, was die beste Kompressoreinstellung für xxxx ist...?'... natürlich gibt es die beste Einstellung nicht, aber womöglich gibt es jemanden, der für ähnlichen Anwendungsfall kürzlich ein paar Einstellungen abgespeichert hat. Wer meint, dass seine Settings auch anderen von Nutzen sein könnten, bitte her damit! Presets (fxp/fxb-Dateien) lassen sich über die Upload-Funktion beim posten mit hochladen, wir könnten das sammeln und bei einem ordentlichen 'Füllstand' als 'sticky' deklarieren. Natürlich ist das mit den Presets nur ein Beispiel von vielen... wir werden sehen. Grüße, Sascha
  3. Hi everybody, as we've currently updated the Samplitude website and fed it with info on the 'unbundled' VST plugins, I'd like to take the chance and welcome all guests, users and whoever stops on by, to this new section of our beloved forum The current week has been the one where we've started shipping the first VST effects boxes to stores and distributors. We haven't performed much of a marketing blahblah and just compiled a few pages for the main Samplitude web site. Most of the stuff was directly taken from the manuals, so that anyone curious about the stuff is able to get a detailed overview on what it's all about without having to download & install the Samplitude demo (which I'd always recommend, anyways....). But that doesn't suffice, I know. As of today, we do still owe you demo versions of the plugins. There's not much sense in reading a bunch of pages without getting your hands on the stuff. That'll come next week, as soon as we've finished & tested the install package. Okay, this forum shall be the melting pot for everything concerning these plugins, their bugs (there's never any SW without...), your proposals & ideas, critique and whatever concerning future versions. I'll also try to give some additional info, background stories, hidden secrets that aren't in the manuals etc. Of course, as time allows. This forum is also intended to serve as a place where users should exchange their ideas, especially when it comes to questions like 'gimme some tips about the right compression settings for xxxx'... while we all know that there's never the 'right' setting, we do also know that switching some presets can be of great value at times. So, please: whenever you encounter a setting on one of these plugins that you'd consider helpful for others, too, don't hesitate to post them. I mean it. We'll see how we can arrange that best as things evolve. My initial assumption is that this could be first solved by attaching an fxp/fxb preset file to a post such as this. Maybe we have to gather stuff and create a sticky topic. We'll see. Surely, there's more to 'community' than changing presets, but you get the point Cheers, Sascha
  4. Nein, es sind verschiedene Paar Schuhe... wir haben uns bewusst für Wibu und gegen Synchrosoft & iLok entschieden. Liegt insbesondere an den Anforderungen für Sequoia. Klar, die Dongles brauchen einen USB-Port. Generell raten wir immer zu externen Hubs. Vor allem was Ausfallsicherheit, Schutz der Host-Ports und auch die Unfallgefahr betrifft (Fuß gegen Rechner->Dongle abgehebelt...). [Tipp für die Anverwandten zu Weihnachten: aktive Hubs gibt's jedes Jahr bei Tschibo... ]
  5. Hi, O-Ton Vertrieb: Du kannst soviel installieren, wie Du lustig bist... Gleichzeitiger Betrieb geht allerdings nicht. Seit Version 8 wird Samplitude/Sequoia inklusive Hardware-Dongle (Wibu) ausgeliefert. Dieser ist sowohl Kopierschutz als auch Lizenzverwaltung (Upgrades, weitere Software). Den Wibu CodeMeter bekommst Du natürlich nur 1x im Paket. Das Programm wird darauf freigeschaltet/authorisiert und von dort an kannst Du an jedem beliebigen Rechner Sam nutzen, sofern es installiert ist. Also z.B. auch unterwegs am Notebook. Der CodeMeter benutzt zum Lizenzmanagement ein Web-Frontend, das einfach lokal im Browser läuft. Er ist auch netzwerkfähig, d.h. Du kannst etwa in einem Studiorechner-Verbund ihn zentral als Server-Applikation laufen lassen und er verwaltet die angeschlossenen Rechner. Sofern dort im Lizenzmanager mehrere Programme freigeschaltet sind, kannst Du entsprechend viele Lizenen auf die Stationen verteilen. Wie es sich mit zusätzlichen Lizenzen verhält, müsstest Du ggf. mit dem Vertrieb aushandeln. Da gibt es kein allgemeingültiges Prozedere. Aber wenn's halt nur die Installation ist... go for it... ich hab hier auch 4 Rechner, aber nur 2 Dongles...
  6. The VST plugins that come with Sam/Seq (am-suite/VariVerb) provide functioning mousewheel support. To achieve this, I've implemented the simplest thing: there are 'wheel messages' that The OS (Windows) sends around and I simply catch and process them. This is what plugin manufacturers *should* simply do, from my point of view. It's dead easy, reliable and not host-dependant. Some plugins, however, seem to rely on a method that I'd call a 'Steinberg hack' where messages have to be collected by the host which passes them on to the plugin. This was once given as an example and might be implemented in Cubase and Nuendo (I'm not sure of that, though). I'm uncertain how many manufacturers actually do it that way, but if they do, it's yet another non-standardised dirty trick on top of the VST specs, that don't deserve the word 'specs' quite right because you can always do what you want by overriding good habits... To cut it short, you may ask the UAD guys if they were so kind to handle classic WM_MOUSEWHEEL messages themselves as millions of apps do. I'd be curious to know.
  7. [While I was typing my blabla below, Frank already answered. But I add my words anyways.] The CPU load mainly doesn't come from the host. Actually the plugin plays the larger role here. Let's look behind the curtain: The host (Sam, Cubase, Sonar, whatever) processes every bit of audio in small buffers (usually 64..2048 samples, depending on the ASIO/driver settings). Buffers are needed for the application to be realtime-capable. Consider buffer handling just like a manufacturing belt: You put something on the start of it, other workers process it along the way, hand it over to the next guy and someone receives it at the end and puts it into a box. In technical terms, such a thing is a 'ring buffer', just like the belt it has a defined length. As long as it is long enough (or running slow enough), you can safe time through it and work quite effectively. Run it too fast / have too many workers handle things / have too time-consuming operations and your goods will tumble off the belt. With VST, there are input & output buffers. If you insert an effect plugin, it gets its input via such an input buffer, processes each containing sample one by one and writes the result to the output buffer, which is given back to the host program. In & out buffers have to be of the same size, for sure. [Now, if you have a VSTi, the input buffer is usually non-existent or discarded, most hosts don't hand them to a VSTi. So, you only point the plugin to the output buffer and say how big that is. The rest is up for the instrument.] Such buffer handling is happening in time slices; a buffer is given, processed, handed back, along comes the next etc. Question is: how much time has a plugin got in order to fill a buffer? As said, it depends partly on the buffer size; small ones are fed up very quickly, while larger ones stay more relaxed. But one has to keep in mind that the host is still running at the fixed sample rate (e.g. 44k1), because we're doing realtime, it has to fetch the next buffer in order to keep up with the current speed. So, at the end of a buffer size, the host says 'Plugin, gimme that damn buffer!'. Plugin says: 'Are you joking? I've got 10 voices to process, each one with 6 oscs, 2 hi-end-analog-jummyjummy filters, high-class effects invented by outer-space intelligence... and you want me to hurry up??? No way!' Then comes the crackling... we are literally stuck in time. If we were 'offline' (the opposite of realtime, such as wav rendering), we could easily wait for the buffer to get filled. If the plugin were a cheap & tiny monophonic, 2 oscillator thingy with not much else going on, that would be smarter. It would probably bore itself to death before the end of a buffer run. You see, it's very rarely a host thing (most of them are interchangeable in terms of bringing in their own CPU load). You can observe slight CPU load fluctuations with different driver models (ASIO, WDM) and by either using Sam's high- or low-latency engine. But the more complex a plugin is, the more the constant load depends on its complexity, the algorithmical structure, the underlying processor (some CPUs/FPUs are quite fast but have bad caching schemes, some are slower but cache quite good and can predict things pretty clever etc.), the overall system throughput, amount of memory/cache and last not least, the audio hardware (buffer size, efficiency, CPU load). So it's also a vague thing to compare CPU consumptions on different machines. There are benchmark tests for CPUs and graphic cards, but there's no 'standard' thing for audio yet. You can freely test your VSTi's with the v8 demo and compare it to any other host you are used to. I guess the basic load doesn't differ that much. But when it comes to quite small buffers (I'd say < 512 samples), the internal regime plays a matter; this is where we've put much effort into with V9 and the hybrid engine: tracks without realtime input can stay 'relaxed' by handling large buffers, realtime tracks with VSTi input can get small ones to be as responsive as possible. Cheers, Sascha
  8. This is exactly what Steve Smith from our sales office at Lübbecke just said to me as I asked him about the topic. [i think Steinberg wouldn't consider me being loyal either because I left out VST5 and SX 1 at that time... ] It doesn't matter if you upgrade from Sam 7, 6, 5 or even RedRoaster, the price is always the same if you left out the latest version. Terry, about the SE upgrade you asked at kvr: this is a limited offer in Germany and it's likely to become limited in the other countries, too.
  9. Die Anzahl (DX/VST) ist theoretisch unbegrenzt. Visuell gibt's natürlich schon Grenzen, die Zahl 6 bezog sich sicherlich auf die sichtbaren Slots im Mixer- bzw. Objekteditor-Skin. Mit Rechtsklick wird aber der komplette Routingdialog sichtbar, inklusive allen geladenen Plugins. Dort lässt sich nach Herzenslust der Kanal füllen, Reihenfolge festlegen etc.
  10. K-Slash, I received your PM. Thanks for the proposals. A quite unusual approach for an EQ (at least for a software plugin) is taken in am|phibia, currently. I've tried to build a box that's versatile and can be used to focus on completely different fields. We have beta testers that even want to use it for mastering (that I haven't had in mind primarily). Funny thing is that the final fine tuning took place with mastering apps in mind while the main development was pretty much a 'coloring' approach. The filters (more precise: the active and passive baxandall types) are pretty gentle and perform quite different than the usual digital biquads you get with most of the other stuff. Building a 'good' eq (whatever that is) needs not only knowledge but also tons of experience. You need to be in that business for a while to get a hang on 'good' sounds and to seperate the perfect algos from the ones that really lead to a perfect sound. Which doesn't need to be the same. I'm still trying to gain experience but I wouldn't say I have that already. So I'd be curious to know how things evolve once am|phibia is out in the wild. What comes next... I don't know right away... About the compressors. I'd love to have a thing in Sam/Seq that feels like - as I said once in the regular Sam forum - an 'end monster' thing (I was refering to arcade games ). But the thing is, we've got compressors all over the place now in Sam & Sequoia but we're not 'the compressor company', you know... There already exist numerous tips & tricks to perform multiband compression/limiting based on am|track & the multiband dynamics/stereo enhancer and the limiter (which is still one of the best available). So one approach for us might be to combine what we've already got and put it together in an easy-to-use and inspiring fashion. Beautiful, maybe. But that decision isn't up to me and currently, we're heading for V9. So I can only note that down as a proposal, but I'm afraid I can't tell you more here & today.
×
×
  • Create New...