Jump to content

marcL

Members
  • Posts

    1,265
  • Joined

  • Last visited

Posts posted by marcL

  1. Sometimes I have a slip-edit problem with certain clips. When I try to slip the beginning of the clip either to the left or to the right the clip data moves in the opposite direction. Snap is disabled and this happens either with the Smart tool or the Edit tool. I also get the correct cursor for slip-edit. The strange thing is that slip-edit runs properly on other clips. It also doesn't help to close the program and reopen the project. Any ideas?

    Also if I slip-edit such a clip and zoom in (ctrl right), then the clip data is moving arbitrarily, but not with each zooming step.

  2. Yep, now I have found out in what case the overlap goes wrong!

    You can reproduce it with any 2 clips:

    1. Just split the clips at 2 shifted positions so that they overlap (or split at the same position and shift one clip borders).
    2. Set the now time to the start of the 2nd clip (the one on the right side!).
    3. Cut/copy the 2nd clip and paste it into the lane of the first clip.
    4. RESULT: The first clip is being truncated!

    If you cut/copy the first of the 2 clips, then it works as expected, i.e. you get an overlap. So it seems that most of the time I did it that way (it worked) and in some rare cases I tried to cut/copy the rear clip that caused the bug (yes, it is surely a bug IMHO).

  3. 22 hours ago, Grem said:

    Maybe you were in comping mode and it keeps thinking (and acting) like your selecting portions of the clips to comp. Can you change to sound on sound and see if it acts better? 

     

    If not can you get a recipe for a repro and submit it?  

     

    I also come across some strange stuff using take lanes when trying to edit the takes as I would a regular trek. But have not been able to get any reproducible steps to submit. 

    Yes, I am in comping mode. But I do not understand why it was working several times before with other clips and also when I copied the clips to an empty track it was working! To me it seems it just happens in about 5 to 10% of the cases. It is very strange! And even when I continued to work in the same project and assembled other clips, it worked!

    Sorry, I was a bit dense that I did not backup the project for reproduction 🙃. Unfortunately I cannot reproduce the case anymore. ☹️

    The only strange take lane behaviour I can always reproduce is when I COPY a clip and paste it into another lane at the same position, then the clip disappears in the original lane (like with cut and paste). But when I re-paste it into the original lane, then I get the required result!

  4. 12 hours ago, sjoens said:

    When this happens, it may be possible to simply drag the clipped end back over the other clip where it should be, but I never tried that.

    In my case it did not work to copy the 2nd clip behind the 1st one and then move it over. It was only pushing the separation of the other clip instead of overlapping. The only thing that worked for me was to copy the clips to a new track and do the whole bouncing in there and copy back the result clip into the lane.

  5. To delete a beat change (time) you have to open the Meter/Key view, select the beat you want to delete and then click on the minus sign. If this is what you mean?

    To delete some measures (inclusive the data within) you have to enable "Ripple Edit All" either in the Options menu or with the new button, select the measures you want to delete in the time line and then use Edit > Delete or the delete key.

  6. As a workaround I copied the 2 overlapping clips to a new empty track (same positions) and bounced them to clips. This worked like expected.

    But still I wonder whether there is a proper solution? One thing I have to check next time when the problem occurs is whether it makes a difference if I copy the first clip to the lane of the 2nd one or vice versa.

  7. Description: I have 2 clips in different take lanes and I want to merge them, i.e. leave the start of the target lane and copy the ending of the source lane so that they OVERLAP with a crossfading.

    1.  I Split the clips at about the same position, so that they overlap.
    2. I add a fade out/in to the clips at the overlap.
    3. I select both clips with the comping tool (unmute them). It sound okay when playing.
    4. I cut (or copy) the source clip and paste it into the same location of the target clip.
    5. I bounce the result to clips, okay.

    I must add that I have set "Blend Old and New" in the Drag and Drop Options. Most of the time the above process runs perfect. But sometimes it drives me nuts, because the target clip is always cut off (truncated) at the overlap position, so that there is only a fade-in instead of a crossfade. The weird thing is that in the same session it runs with other clips/takes in the same track! WTF do I do wrong?

  8. 18 hours ago, S.L.I.P. said:

    A good video to understand the complexity of vocal editing. 

     

    IMHO the video only shows a small part of the complexity. They touch the challenge at the beginning when they split a blob. There you see how Melodyne recalculates the pitch of the two halfs. I have found out that in many cases when I had moved the starting points or introduced new split points the notes were almost perfect! So I find that my older Melodyne pitch corrections were absolutely wrong. I really had tampered some vocal performances! That's because I relied too much on Melodyne's blob starting point and split detection (that is simply bad).

    Since about 1 year I do a lot of manual work in the detection mode first. That has led to almost no pitch corrections, i.e. I use Melodyne primarily to tighten the vocal rhythmics. Now the results are much better!

    It is also crucial to understand that a singer can set the accentuation on completely different points of a syllable. Very often Melodyne's detection mode computes this totally wrong for a blob. Thus a lot of manual work is required in the detection mode first, before you can change the vocal performance. My advice is to trust more in the singer's skill than in Melodyne's detection mode, i.e. search the blob's emphasis near proper beat positions!

  9. I had reported dropout problems with loop recording in the old forum. But that time I was only using my weak laptop (i5-5200U, 8GB) and I just complained about the comparison to Samplitude that had no difficulties with such tiny projects even with a smaller buffer size.

    But now I have a project on my DAW (i5-8600K/6-cores, 16GB, 512 SSD, W10) with only 9 audio and 1 synth track(muted) that reveals the same problems. 5 of the audio tracks contain only one clip and on the other 4 tracks I intended to do loop recording at different positions. When I reached the 4th loop recording it began with dropouts. So I had removed the only 2 FX plugins used for tracking, but it did not help. As workaround I saved the project under another name, removed the tracks with the previous loop recordings in there and then I could finish my last recording. Afterwards I copied the takes back to the original project. All so fine!

    Now trying to comp the takes with a play loop I run into dropout problems again (trying to increase the ASIO buffer size did not help)! And if I do comping without loop playing, then there is always an obvious play retardation. Okay, one thing I have not yet disclosed: I have surely overdone the loop recordings with about 30-40 takes! 😁

    Thus, to me it seems that Cakewalk/Sonar has a performance issue with increasing number of take lanes (no issues with other Daws on the same PC).
    What did I do wrong? Did someone have similar problems? Are there settings that can fix the issues?

  10. This concerns me more and more,  these days it is difficult for the software (and hardware) users to find out which updates/upgrades are worth to be installed. Sometimes it is even the case that you get serious drawbacks with new versions (e.g. today's license models and update control, it gets worse and worse).

    George Orwell was right, but he confused the date. It is today not 1984.

  11. 25 minutes ago, Johnbee58 said:

    You're serious?  You don't know who Bill Cosby is?  Maybe you're not American but he's a very popular TV personality and comedian who was busted in recent years by the so called #Metoo movement (man hating feminists, for the most part).  A bunch of women came out after some 30+ years to claim he sexually assaulted them.  Why they waited that long to report a rape is the question of the century.  But they all ganged up on him and as the result of one, he is currently in a PA  (USA) prison for drugging a women in the 1980 to seduce her.  He's 81 years old and legally blind.  It's a controversy whether or not he was fairly tried.  More details here: https://en.wikipedia.org/wiki/Bill_Cosby

    😀John B

    That's why IMHO "Me too" is the incarnated inquisition (Catholic Church).  And it is not the only thing that reminds me these days of the Middle Ages!

    • Like 1
  12. 12 hours ago, Soundwise said:

    TH3 is alright. It has some usable sounds, but it's not my number one for anything,  be it clean, crunch or lead tones. TH-U is not a game changer either.    Changing preamp/poweramp tubes  feel more like switching between different IRs. Hard to explain, but even though it sounds different and, to a certain degree, reminiscent of the modeled amplifier, it still doesn't feel right.

    The same goes for me!

    I prefer Magix Vandal over all of them, although I don't like its interface. For me it sounds nearest to real amplifiers.

    But I think the sound of each amp sim can be improved if you use hardware effects before your audio interface. If I play lead I often connect my guitars to a real overdrive or distortion stomp even in the case when I use nearly no drive. IMHO it sounds much better, no simulation comes near to that!

  13. What I am missing in TH3 is something like the "air" setting in other guitar plugins (like GuitarRig). I played a lot with real guitar amplifiers and still do and I feel that the air setting helps to get closer to a "real" guitar sound.

    Second, I have the impression that TH3 sounds better with humbuckers than with single coils. Generally (with all guitar plugins that I know) I miss the information whether a preset has been made for humbuckers or for single coils, as it really makes a difference!

  14. 1 hour ago, msmcleod said:

    For me the GUI of the sonitus plugins is pretty low priority. IMHO there's too much emphasis on trying to make VST's look like "real" gear, often at the expense of usability. Turning knobs with a mouse isn't the most intuitive thing, whereas sliders and graphical envelopes are perfect for a mouse.

    If anything, making the GUI slightly bigger would be nice, but apart from that the interface works well for me and they sound great.

    I must admit that I am one of these ordinary, simple guys who likes if Vsts look like "real" gear! 😄 I hate those old-fashioned or modern abstract plugin interfaces.

    And I do not agree that knobs are not intuitive (I prefer them absolutely over sliders). It depends only how you can tweak them, e.g. I like if I can set them with the mouse wheel and with shift+wheel for fine tuning (even if there is a lot of difference on different plugins). There are remarkable good solutions with even some free plugins (e.g. TokyoDawnLabs, SleepyTime)! What I agree is that setting knobs with mouse up/down is really bothersome, but for me the worst thing is the implementation where you click on a knob position to set it. But if the plugin sounds well, then I use it nevertheless!

    Never mind, Mark! It's only my opinion and maybe (or sure) I am very exotic!

  15. 8 hours ago, Bapu said:

    I have samplitude and mixcraft.

     They are dead  to me. Not worth my time. Not even Samp v4.

    Wasted a total of $200 on those two.

    For me, Samplitude is one of the better Daws out there. For I don't like those EDM style ones! Yes, I confess I am one of those old farts!

  16. 3 minutes ago, abacab said:

    Sorry, but I will stand by the statement "A lot of competition in a saturated market", and belief that it was not misused in this context. 

    I don't like it either, but the reality is that Cakewalk wouldn't have failed in the market under Gibson if the opposite were true. If it were a money making machine, don't you think there would have been eager buyers lining up, rather than shutdown plans for a 30 year old company? 

    Sorry either, I think a lot of management failure is excused like that! There are many reasons why a company is not successful, not profitable, it is not only the market's fault. That's too simple! I am 100% sure that Sonar could have survived with other (cleverer) managers!

×
×
  • Create New...