Jump to content


  • Content Count

  • Joined

  • Last visited

About HHfallback

  • Rank
    Professional Member

Recent Profile Visitors

981 profile views
  1. not really no,just some user error of me :- i duplicated a section a few times pressing "D" .. but it didn't loop well,so i set the snap to full bar,made sure that the object was adjusted to full bar (it was slightly short - but i didn't notice till i looped) after that "D" worked perfectly .. maybe this is your problem ?
  2. that was great! loved it part 2 in a bit
  3. this sounds great! .. nice work
  4. sounds like what i get if i use the "magix low latency" driver .. or if i use bad settings for "Performance" and "extended buffer settings" (press Y then look for "system options") - these can get worse when live monitoring as also used im currently testing Samplitude 5,and have found the default ASIO settings work well for me (i then imported my settings from an earlier Sam4 test into sam5,she works even better!) Magix low latency driver is kinda ASIO4all - a fallback for when the supplied ASIO drivers for your card have a problem (or as a last resort if no ASIO drivers are available) ...
  5. that was the scene i thought of when first hearing the sad news nice tribute
  6. tracks not "live" can be set to economy (some cannot be economy - but sam will tell you this = freeze these if needed) your live track (the one your playing into) use with no changes ... Sam has (kinda) 2 audio engines ... 1 the "normal" ASIO of other daws (fast,for real time low latency) 2nd the higher buffer setting secondary (slower,larger buffer) when you set track economy,the track will use secondary engine to pre-calculate effects ... lets say secondary calculates FX 4 seconds in advance this means the "normal" ASIO buffer is under less load (cos the fx have been calculated 4 seconds already,then "normal" ASIO only has to process the output of secondary,not the whole chain) so,if you have a very fast cpu .. then it will out-run the ASIO driver engine (give to much data to ASIO driver,while showing little CPU usage) .. Sam having 2 audio engines means you can use unused CPU cycles to pre-calculate track chains - while maintaining low latency freezing tracks is no doubt best to free up CPU .. but sometimes is not necessary (depends on project ... but is good Sam has many options for control)
  7. hey Terry thicko me forgot to mention that FX use a lot of cpu .. so freezing just the FX and buss channels (on tracks your currently not using "live" - i.e not the Native Instruments piano your actively playing) can save a lot of cpu (maybe try that first when you hit a ceiling?)
  8. have you looked at economy tracks? .. they use Sams larger secondary audio buffer to pre-compile effects ... takes strain off the main ASIO buffer,then freeze tracks that cant be made economy
  9. Pilyser is cool ahhhhhhhhhhhhhhh,you like the same as me i use the method i posted above,and have an isolation cabinet connected (Box with a speaker in,soundproofing = ISO cab) .. i also take a feed from the send of the amp (send on amp = pre-amp out) and send this to Kefir (an Impulse loader plug = IR loader) in the daw ... i can mix in the sound of the 2 mics also .. if wanted i also use another 2 stand alone valve pre-amps,and send those to Kefir on other channels (this is totally silent in the room) the switching to pre-amps or big amp (with ISO box) is done in the daw ... (you are able to pick which multichannel hardware outputs you want to use) there are problems you will come across using this method,but you *are* recording the DI,so can change at will later ... oh! just in case anyone reads this and doesn't know, NEVER run a valve amp without a load = KA-BOOM!!! i say Kifir cos that's the IR loader i had the least trouble with
  10. you might be better plugging the guitar DI to your interface,exactly the same as using an AmpSim, then send the DI signal to the amp added as an external effect .. this way you are in effect re-amping ... you can also use this method to also use the amp playing "live" .. the good bit is:- your not committed to any hardware amp tone (change your mind later,cos only the DI signal is recorded) its easier to edit clean DI tracks,find transients (for beat/tempo markers) than it is to edit tracks recorded with high gain you can perfect your lead tracks,before sent to the amp (neighbours will be happier you use the amp for only 10 mins rather than all day) you can use an amp sim at 3am,the recorded DI can be sent to the amp at any time ... or used in another studio you can add effects to the return signal only (or on the send to the amp,if thats what you wanted at some point,maybe a compressor,noise gate ) recorded and perfected DI tracks can be disabled and hidden after you have re-amped,and always there if wanted later problems:- you need a multichannel interface (you cant do this easily on a 2 channel interface,although still possible,but creates extra steps) at first it can be hard to setup,once you "get" the idea,its pretty easy to use in any daw i have tested this is sam3,it works perfectly,i had no latency or phase problems (don't forget to use the delay compensation option) ...
  11. ahh,sorry i cant help you really .. i don't actually use sam (cos it never worked for me) .. but i spent a lot of time trying to get it to run stably ... a few months ago i found out sam4 was out,so i tried that for 2 weeks (only testing audio stability and not any features,while filling time editing a skin) then a friend said "i get 40% better usage in win10" so i went m/s and downloaded win10 .. all my spare time is used making my own install iso (without the spyware and hidden services) im only here cos i like the people
  12. 1) check your windows display settings (right click on desktop and select "screen resolution" ) .. some people are unaware they can make the desktop "bigger" .. if your using an old monitor/graphics card then it might not be able to support the larger screens needed by some programs ... im guessing here.but i *think* sam needs 1280x1024 at least (someone will be along to correct me soon if wrong) 2) drag the transport by the little handle on the top left side (if you use micro transport i *think* you can click on the time display? .. around there anyhoo) 3) yes,64bit sam will run 32bit pluggins ... it uses a software bridge,some plugs will work better than others ... now is a good time to start upgrading your 32bit plugs to 64 ... 32bit plugs are dead now 4) not sure about that one,cos it could be lots of things .. but i would start with sam asio audio settings,then the monitoring options ...
  13. btw - welcome,good to have you here read around the forum,they are a great bunch of helpful people ... its not the busiest of boards (specially at weekends) but you`ll love it
  14. try setting your fonts and Dpi setting to default .. that's usually where these things come from ... if that cures your plug display,then its a juggling act to get the right settings that will work for you daws will "frame" the plug gui using their settings (like sonar will make a meter gui to wide to fit in your workspace ) but the pluggin maker might have a different idea about the skin it uses ... btw- it looks like your on win10,did you know that if you have 2 or more monitors connected to your pc you can choose scaling options for each monitor? - something else to consider for that problem pluggin gui
  15. if your logging in correctly,and ticking the "remember me" box then don't delete the site cookies after you visit ... your site options are stored in them/it if you got a cookie cleaner add this forum to its whitelist ... *think* this is a non-official magix site,so not supported by magix ..?? .. not 100% sure .. soon find out when a regular comes by and corrects me
  • Create New...