Jump to content


Samplitude Members
  • Posts

  • Joined

  • Last visited

Everything posted by DBMusic

  1. Hey DonM, Sonar user here too. The biggest issue I have in Samplitude is "unlearning" my ways of doing things in Sonar. Unfortunately, different methodologies make the learning curve rather steep. Trying to cram a 1 week crash course in Samplitude is going to be daunting so I would expect you to encounter some frustration. I'm still learning my way around Samplitude too so I can't be all that helpful in getting you up and operation in a short time. But I can offer encouragement to stick with it. There are a few head-scratchers (I don't really care for their approach to file management, seeing old UAD integration issues that are thing of the past in Sonar is annoying, and then there's this dongle nonsense if you go with the Pro version), but the more I use Samplitude 10 the more I'm impressed. Another thing is the professional and helpful environment you'll find in the forums. Good luck! Regards, DB
  2. Greg, Jeff Thanks, that explains a great deal about "Remove unused samples". The "save complete VIP" feature appears like a good way to handle file maintenance. IMO though, having an efficient way to remove all unreferenced project files would be an obvious benefit. As to the track resizing, there appears to be some sort of rescaling of remaining track sizes when deleting tracks and also some inconsistency in the size of new tracks. This isn't a big issue. I'm just a bit of a neatness freak and I'm used to having everything on my screen stay exactly as it is until I specifically take some action on a target track. Again, one of those perceptual issues I've grown accustomed to over the years. Regards, DB
  3. Randy, Greg Thanks guys. When navigating new paradigms sometimes the wall we beat our head against ends up being our own perceptual bias on how we've done things in the past. The frustration is similar to suddenly finding yourself stuck in traffic on a road you've traveled a thousand times before. Does anyone have any input regarding what appears to be this track automatic resizing? I seem to be spending and inordinate amount of time manually vertically resizing tracks each time I add or delete new tracks? I would really like each track to maintain it's height when working on others. Also, this "Remove unused samples" doesn't appear to work very well. Maybe another paradigm I can't get my head around? But I know I can create literally hundreds of files this function will not remove from a project folder even though I've clears all reference to them in the project (deleted the Undo history, takes, tracks, objects) and I can manually delete these files while Samplitude is still open. I'm definitely a stickler when it comes to file maintenance so I'm curious as to what I'm missing here. Regards, DB
  4. I'm going a little nuts here with what should be, in my estimation very simple tasks. For example, I want to bounce several percussion tracks to a separate track. I've tried several ways but all I end up with around 500 MB and 360 new files in my project folder that are useless to me. Why is this so convoluted? In Sonar you just select the tracks you want to bounce, select the bounce parameters, select the target track, and just bounce. In Samplitude I have no idea how to do this simple task. I can't even seem to figure out how to select multiple tracks. I simply want the end result of bouncing multiple tracks to be 1 new wave represented by 1 new object on a new track. Easy, right? Also, I have 100's of new unused files in my project folder that I created just trying to achieve the above. Now when I use the Remove unused samples... feature, none of these files are deleted. I've deleted my undo history, restarted Samplitude and can get this feature to delete NONE of these new filed. Frustrating. Is there something I'm missing here. This really should be DAW basics. Regards, DB
  5. Hi Sebastian, Adjusting the sample delay in either the primary Perc bus or the Aux Send bus or the Aux Return bus only increases the distinct delay heard on playback. I should emphasize here that the delay I'm concerned with here is playback delay and not recording delay. If I record through the Aux Return bus there is only about an 8 sample delay. However the playback delay is much greater. As I'm sure you are aware using parallel compression requires some dynamic adjustment of the compression on the Aux Send signal and summing adjustment of the two buses during playback to achieve the right sound and balance. As I have it configured in Samplitude, unless I record the Aux Return first and then use this to sum with the original Perc bus, this will not be possible. This, of course, makes the entire process of using an external compressor for parallel compression possible, but time consuming. Regards, DB
  6. Is there are way to control the tracks size behavior when adding or deleting new tracks? There are a few things the I find somewhat annoying that I cannot find in any setup options. For example, we using a key binding to add a new audio track the vertical size takes up my entire screen. Is there not a way you can set a default size for new tracks? However, If I create a track my left-clicking and select Insert Track(s) and acceptable sized track is created. Next, when I delete a track all other tracks in the Track View are for some reason resized. Of course I can save a Track View preset but I would really like to be able to add and remove tracks without these major track size adjustments. Is there a way to control this Track View behavior? I've searched through the project and help file and can't seem to find any setting that would affect this. Regards, DB
  7. Parallel external compression may indeed be the rub here. In Samplitude I have no issue with delay compensation when simply routing a track through an external processing loop and recording the return (I found only a 5-6 sample offset from the original track). However, when routing that analog loop via an Aux send off a bus fed several percussion tracks then monitoring the return against the original bus, there is a distinct delay that makes any artful summing of the two impossible. Interesting though, if I place a plugin, in this case a UAD Plate 140 on the original percussion bus and engage it, some additional delay compensation kicks in as then the distinct delay is gone but there is still phasing that is unacceptable. I did the appropriate setup by pinging external effects and making sure the sends and returns have identical routes (everything is processed through a single HEDD). A little research reveals this is not an uncommon issue when attempting parallel compression via external processing. From what I read it seems that Nuendo and Cubase have the compensation nailed. I suppose there are some less than elegant workarounds to this as well as other purely digital alternatives. Still, I wish this were possible in Samplitude. Regards, DB
  8. I was able to eliminate most of the doubling sound when using the external effect configuration by decreasing the ASIO buffer to 128. But I'm still getting the phasing effect that would still indicate lack of synchronization. Frustrating. These delay compensation issues are what made Sonar such a pain to work with. Regards, DB
  9. Ok, I take back part of what I said. I set up an Aux send off the Perc bus and added a UAD-1 1176LN to it. Upon playback I'm getting the same phasing affect when it's on and a doubling of the playback with it off. So I removed it from the Aux send completely. When bring up the fader of the Aux send I can hear the doubling affect (like the playback of the Perc bus and the Aux Send are misaligned). So, I start over and add an Aux send to the Perc Bus and just play it back with no plugins. It plays back fine. Now I add a UAD-1 1176LN to the Aux send bus. Playback is now synchronized. I do it again and this time add the 1176LN before I play back the empty Aux send. Playback again sounds synchronized. I start over and add an external effect via an Aux send. The playback is no longer synchronized. And I'm frustrated and confused... Regards, DB
  10. Having a bit of an issue with using my external gear. Here is what I'm trying to do: I want to create some parallel compression of my percussion tracks using an external EQ and compressor. In the Project Options dialog I have my External Effect set up for the appropriate Send and Return and have detected the latency. I have several percussion tracks all routed to a submix bus (Perc Bus). I have a UAD-1 Plate 140 set up as an effect on the Perc Bus. Off the Perc Bus in have set up an external effect via an Aux send (creating an FX send as an Aux bus named Var-Mu Send and a return tack named Var-Mu Return). I have the Aux send setup Pre fader. When playing back the Perc Bus and Var-Mu Send with the Plate 140 on, I hear considerable phasing when bring up the Var-Mu Send fader. If I turn off the Plate 140, it gets even worse as I can actually hear a doubling of the percussion tracks. I guess the routing in Samplitude is a bit confusing to me so I'm not sure what exactly I'm hearing. I have one set of I/O's (1+2) set up that route through a single set of converters in my Crane Song HEDD. I have one out set up as 15+16 that I use for monitoring that runs through a separate converter. All percussion tracks show IN as 1+2 and the OUT as Perc Bus. The Perc Bus shows the IN as 1+2 and OUT as StMast (15+16). The Var-Mu Send has both the IN and OUT set as 1+2. The Var-Mu Return as the IN set to 1+2 and the OUT as StMast. The Send and Return of my External Effect is set up both as 1+2. Now in Sonar you can set the IN of any track to None. You have no option for Bus IN's because that is defined by what tracks/buses are routed to it. For this configuration in Samplitude I have no choice but to set the IN's of all tracks and buses to 1+2. Since my Aux send is routing out through 1+2, I was wondering if the return through 1+2 wasn't being fed through all these tracks. So I created a dummy 3+4 I/O that was connected to nothing in my audio system and routed all my IN's though it. This made no difference it what I'm hearing. For another test I simply set up an Aux send off the Perc Bus and added a UAD-1 1176N as an effect. This worked fine and I was able to create, at least to my ears, a perfectly synchronized parallel compression effect. The conclusion I'm coming to is that there is some rather significant issues with the delay compensation in Samplitude when using an external effect in the way I'm describing. Is this true? I've been trying for a few hours now and can't seem to make this work. Regards, DB
  11. Hey MJB, You're very welcome...and the best of luck with your decision. Keep in mind that often one of the hardest things to overcome in adapting to any new system of doing things is the bias we bring from our previous experience. Several times in evaluating Samplitude I was stopped cold wondering what the heck was going on only to eventually discover it to be something really easy...albeit just a bit different route to the same destination. The reasons that brought me here were a bit different from yours in that I have a very stable system. Apart from 1 issue in Samplitude that was reported resolved in version 10.2 (the DLV is 10.1 and cannot be updated while in trial mode), both Sonar and Samplitude run perfect on my system. For me it was more about poorly implemented features, poor resolution response, and the feeling that the general trend for a target market was more the novice home hobbyist. That's all good and well, just not personally what I'm looking for. I do hope you find some resolution to your DAW issues. And once again, I wish you the best on your decision to give Samplitude a try. Regards, DB
  12. Sebastian and Greg, thanks for the kudos. And thanks to all who have taken the time and effort to offer your feedback an opinions. I placed my order for Samplitude today. Regards, DB
  13. Hey MJB, I encourage you to try the download. I think you'll be impressed. I know I am. The learning curve may be a bit steep but don't let that discourage you. And yes, with only 1 exception in this entire thread, the discourse around here is very upbeat and helpful. Good luck! Regards, DB
  14. No sides here, holyjaguar. Hopefully, just reasonable people agreeing to disagree. I've put in a lot of hours over the last week evaluating Samplitude and my tendency is to agree that it's very good DAW software. Sonar is good DAW software too and I admire their protection/activation policy. Fortunately, for Samplitude 10 (not pro) the dongle is optional. If I purchase, this would be my route (though I do take objection to the installation of CodeMeter software without my permission). Many have no problems with dongles and 3rd party software. Many others do. Personally, there are other perfectly reliable protection schemes that make them unnecessary...and to lose a sale because you don't respect people who do have issues with dongles is, in my opinion, just plain silly. Regards, DB
  15. Received this from Magix regarding crossgrade options for the DLV: Not sure why I have to uninstall the DLV and purchase a crossgrade option just to get the same program installed, but no big deal I guess. Regards, DB
  16. Hi Sebastian, No, I was curious if the crossgrade licensing option was even available for the download version. I've sent an email to Magix requesting some details. hennessey, I'll be glad to share the response I get from Magix when it arrives. Regards, DB
  17. Floridamusicco.com sells a Samplitude 10 crossgrade here: Crossgrade I'm evaluating the DLV and also am interested in the easiest crossgrade path. I'm not sure if this would be to order the crossgrade separately or if there is a way to authorize the crossgrade in my currently installed DLV. Regards, DB
  18. Hi Tobben, Thank you so much. That is precisely what I was looking for. I knew there had to be a simple way of doing this. Regards, DB
  19. Hey imdrecordings, I understand building and utilizing loops in Samplitude. The only issue I have with them is with the lack of looping of the fades. If you create an audio track, press CTRL+L, and then drag either end you will notice that the fade moves and does not repeat itself with each instance of the loop. In objects where the wave may slightly exceed beyond the end of the loop (say you're trying to loop a 1 measure wave that slightly exceeds the length of the measure), without applying a fade at the very end of each loop you will here a slight click/pop. This happens in Sonar too. But it Sonar it is very easy to use what is called "Bounce to Clip" where the clip (object) is rendered in place applying whatever fades or effects you may have. Now I can do this in Samplitude by utilizing Track bouncing and setting the Generating Options to "New separate Object in current VIP" and setting the Source as Objects:bounce selected. this works but it creates a new rendered object in a new track. I can just drag the new object and replace the one in my current track ok and delete the new track, but it seems an odd way to go about it. If I choose my Generating Options as "Replace Objects in current VIP", this renders in place but for some reason the effect of the fades are NOT rendered by this method. Thanks! Yeah those long file names can get pretty hairy. I have Samplitude set up now to for "Each Record take in a new file" now, but the Wave Editor threw me a bit. I think I understand it better now. It appears just opening the Wave Editor on an object automatically applies the editing (even if there is none), thereby creating a new take which is stored in a new "FX" .wav file. Each success opening of the Wave editor creates a new take that is stored in this same FX file. I really don't understand why all of editing takes for an object are displayed in the Wave Editor, but to be honest I've just started working with it. It allows me to render fades to an object in place but it also has the potential of saving a lot of unused takes that only uses up disk space. But like I said, I'm learning. Hi MGB, Yeah, this works, but it's not as slick, IMO, as utilizing looping. If there were simply a way to render an object in place, including the effects of the fades, that would be perfect. Hey roger, I'm not a big soft synth user so 2G of RAM has always been plenty. My old Athlon X2 4800+ may be a relative dinosaur, but my machine is rock solid and the CPU handles whatever I throw at it with ease. I do believe my one crash I had with Samplitude may have been related with the CPU usage creep when using the CC7 MIDI volume for the track faders. I know what you mean about the newer CPU's though and all that power is fun to dream about. But DAW's can be hell...and if it ain't broke... Regards. DB
  20. Have you tried "duplicate objects"? MGB Hi MGB, If by duplicate objects you mean essentially just copying the object and dragging in to the new position, yes. but this defeats the convenience, speed, and efficiency of using loop based objects. Regards, DB
  21. Hi Rolf, Yes, I have tried "Each Record Take in a new file", but it does not affect the issue with the Wave Editor. Let me be more specific: There is an audio object in my project that is named Take55 and is based on the"Test Project 110_24_T0555.wav". If I select the Take55 object, right-click and select "Edit copy of wave project", and just close the editor, a new take is created named "Effect 01/20/09 14:51:49"in a new file named "Test Project 110_24_T055_FX.wav" with a size of 6,350,480 bytes. If I repeat this and open the wave editor on object Take55 again I will see the previous "Effect 01/20/09 14:51:49" and the new take ""Effect 01/20/09 14:54:13" in the editor. I close the editor. Now the "Test Project 110_24_T055_FX.wav" file has grown to 12,700,880 bytes. If I repeat this once again a new take is created in the Wave Editor named "Effect 01/20/09 14:57:41", in addition to the 2 previous ones. I close the Wave Editor. Now the "Test Project 110_24_T055_FX.wav" file has grown to 19,051,280 bytes. If I open the Take Manager I will see the following takes: FX Original Effect 01/20/09 14:57:41 Both of these point to the "Test Project 110_24_T055_FX.wav" file created by the Wave Editor to hold these takes. If I attempt to delete either of these takes I get the message "The file E:\Samplitude\Audio\Test Project 1\Test Project 110_24_T055_FX.wav has more than one take and can't be delete." Now there is no way I can get rid of these unwanted takes. Even if I delete my undo history and run Remove Unused Samples, it will not remove the "Test Project 110_24_T055_FX.wav" file. I did just notice, however, it DID remove one of the takes in the file, but the file itself stays intact. For example, if I repeat the above and create a new take "Take X" in the "Test Project 110_24_T055_FX.wav" file, open the Take Manager, select "Take X", right-click and select Delete take, I get the message "The file E:\Samplitude\Audio\Test Project 1\Test Project 110_24_T055_FX.wav has more than one take and can't be delete." If I then use Remove Unused Samples and run it, I'll notice the size of "Test Project 110_24_T055_FX.wav" has been reduced. When I re-open the Take Manager I will see "Take X" still listed but when I click on it I get the message "Warning! New Take is shorter than the object". Regardless, I have unneeded takes and files I cannot get rid of apart from closing Samplitude and deleting them manually. I know I'm a novice at all this, but compared to Sonar this is quite confusing. All audio in Sonar is represented by a separate .wav file that has an internal marker as to whether or not it is actively referenced in the project. A "Clean Audio Folder" function then simply locates these unreferenced files and provides the option to delete them. This makes for very efficient project file management. Hopefully, Samplitude's methodology will get easier to use and I'm sure I can figure out workarounds, but for now it doesn't really appear very efficient. Regards, DB
  22. I've not changed anything in the default config. In the System Options - Record - Extended options the "Show confirmation dialog (OK,Delete) after record" option is checked. I do get the message when recording, however, just opening and closing the Wave Editor creates another take that gets added to an existing file. Via the Take Manager I cannot delete this unwanted take because it says there are multiple takes in the file. As mentioned above, selecting an object, opening the Wave Editor, and then immediately closing the Wave Editor creates another take that gets added to an existing .wav file. Now when opening the Take Manager and attempting to delete the take I get a message saying "The file xxx.wav has more than one take and can't be deleted." Apparently deleting a take means deleting a file, but when there are multiple takes contained within a single file you cannot delete a single take within than file. I did check "Each Record take in a new file" but made no difference in takes being added to the same file via the Wave Editor. Deleting the undo history has no affect. I can create a recoding, delete it from the project, delete the undo history, run Remove unused samples, and the file is not deleted. I get a message stating "Remove usnused Sampels finished. Please save your project first! All previous copies of these project are invalid." Don't have a clue what this means since I do save the project first. Regardless, no unused samples are removed. Neither on of these processes appear to render the affect of the fades. The new bounced object still has the original fades and when drug out return the file to it's unfaded form. I need to fades to be rendered in the bounce. I guess I'm not understanding why when a fade applied to a looped object that the fade is not applied to EACH instance of the loop that gets created when dragging. Instead it just moves the fade to the very end of the object. *** Ok, I've found that bouncing an object using the "New separate Object in current VIP" under Generating options DOES render the effects of the fades. However, the "Replace Objects in current VIP" does not. This allows me to do what I want but seems a bit cumbersome to have to create a new object and track just to do so. Thanks Sebastian and Greg for your time to help me evaluate Samplitude. I understand new users can be rather frustrating to deal with and I do appreciate your efforts. Regards, DB
  23. This is one of the paradigms of Samplitude - when you open the wav editor, it will show you all your takes, but it SHOULD have a range highlighted for the span of the particular VIP object you're working on. Before copying your objects, you can put a manual fade on the object edges by sliding the corner 'nurb'/hook over to the left/right. No need to do all the work of rendering to wav first. I'm not sure why your getting clicking when crossing the edges of the looped objects - other than there may not be any fade - but I've never noticed clicks at borders. You can also try simply sliding objects against each other to create an instant crossfade (if you're in object mode). So, there's object fades (at the edges), and automation fades (another topic), and volatile wave edits (not necessary in Samplitude), but when working with objects, you just need to set things up once before copying/looping or whatever. Greg I'm finding Samplitude's implementation of "takes" a bit confusing. For example, every time I open the wave editor it creates another take that is saved in the same .wav file. Even if I don't want to keep the take it saves it anyway. Now I have all these takes being saved that I don't want that keep increasing the size of the .wav file. In the Take Manager I can't delete these takes because there are multiple takes in the same file. This seems very strange to me. Now in this .wav file there are some good takes that are represented by other objects. Why would I have to keep all these useless takes that do nothing but take up disk space? Also, I noticed under the Tools menu there is an option to remove unused samples. But this doesn't really seem to remove all samples I'm not using anymore...or maybe keeps references that are not needed. Regardless, I seem to end up with a lot of .wave files and takes that I don't need. Regarding the loops, if you notice when dragging a loop, the fade at the end moves to the end point of the drag. Each loop that gets repeated in the drag does NOT contain the original fade. These clicks when looping typically happen when your original audio was slightly extended beyond the object range and has been cut off. Because Samplitude does not apply the fade with each reproduction of the loop when dragging, the original object needs to have the fade rendered first so when dragging the effect of the fade can be repeated. In Sonar this is very easy. Is there not an easy way to simply render and existing object in place to apply the fades? For the most part I'm finding audio loops actually easier to work with in Samplitude. I know it's mostly my lack of knowledge of Samplitude, but it does seem odd that I cannot simply bounce a single audio file in place (so that the original object is now replaced by the new rendering) to apply fades (or any other effects or editing for that matter). Regards, DB
  24. Hi Greg, By "turning off CC07 on the mixer faders" do you mean mean de-selecting Controller 7 in the "Automatic Column Fader mode for MIDI Tracks" section of the System Options - MIDI? If so, I've done that and it had no affect. I'm not using any plugins...just 5 straight MIDI tracks set up to interface with an external synth (Motif ES7). Regards, DB I think Dax mentioned turning it off at the fader (which may be the same thing). Right-click over the fader handle and set the volume mode for audio only. Don't worry about the system config. at this point. Greg Thanks, that does appear to work around the issue. Regarding the Wave Editor, is it possible to open it for a single audio object? Opening the Wave Editor appears to open several takes. Or is there a way to simply bounce the audio object in place to apply the fades? The reason I ask is because in converting audio objects to loops and dragging, the fade out is not applied to each loop section but is instead moved to the very end. Without being able to apply a small fade at the end of the object when looped it will sometimes create a little click or pop at the beginning of each loop (typically happens when the original audio extended beyond the object end). I've been able a apply the Wave Editor to apply this fadeout successfully, but I keep getting multiple takes when opened. Interestingly, instead of looping an object if you simply copy the object and place it in sequence there is no clicking when playback crosses from one object to the next. Happens only when looping. This happens in Sonar too but is easily resolved by place a small fade at the end of a clip and you can then quickly just bounce the audio clip in place before creating your groove clip. Regards, DB
  25. Hi Greg, By "turning off CC07 on the mixer faders" do you mean mean de-selecting Controller 7 in the "Automatic Column Fader mode for MIDI Tracks" section of the System Options - MIDI? If so, I've done that and it had no affect. I'm not using any plugins...just 5 straight MIDI tracks set up to interface with an external synth (Motif ES7). Regards, DB
  • Create New...