Jump to content

Sonarman

Members
  • Content Count

    63
  • Joined

  • Last visited

Posts posted by Sonarman


  1. 7 hours ago, Justin P Brown said:

    I have re-imported the exported stereo track into CW (is CbB another name for Cakewalk (CW)?) & it plays fine. I'm just trying to figure out why my CW tracks are affected when they are played through media players on my laptop. It's very odd.

    Also, 32 bit is the default export setting so I used it originally. I tried the 16 & 24 settings on advice.

    Yes, CbB is Cakewalk by Bandlab, no harm in using CW as well. 

    In that case your export is fine. Something to cheer about. Hope you figure out whats wrong in your pc.

    • Like 1

  2. Quote

    (I tried altering the bit depth to both 24 & 16, but this had no noticeable affect).

    You should also try 32bit. Coz 32bit export is the one that will sound exactly similar to  how the daw played back during session. 24 bit and 16 bit will always have subtle differences caused due to either truncation noise or dithering noise. But this should be subtle with some exceptions. Depending on the musical content sometimes this can cause some obvious differences. 


  3. Hi, anyone remember we had a big thread in the old forum regarding s1 sounding different from Sonar. That was the time many where transitioning from sonar to s1 and many other daws due to Gibson abandoning us. Goodness! Bandlab saved us. And here I have discovered that s1 does sound different from cakewalk once again. 

    Little history:
    Here in this thread (http://forum.cakewalk.com/Comparing-Sonar-with-Studio-One-m3697861-p5.aspx) some of us folks that where trying s1 found that s1 sounded different from sonar. Few were trying to move their projects from sonar to s1 and was not able to create the the same mix despite having the same settings. Later in the thread 'Sylvan' made some inverted phase cancellation tests and posted the video. Many others including me did the same test and found that the audio from s1 and sonar didn't null despite having the same settings and mix values. We where puzzled, but later in the thread we found out that this was coz s1 by default uses a pan law that's different from that of sonar(for more details read the old thread). 
    By rendering the same tracks with same panlaw we were able to create perfect nulls. And that scientifically concluded that s1 and sonar rendered the same and hence sounded the same if same pan law is used. 

    However me and some folks still felt that s1 does sound different despite the null tests that proves otherwise. We kind of concluded the thread (or convinced our minds) that the rendered files form s1 and sonar does sound the same but whether the playback engine of s1 and cakewalk are same is questionable and couldn't be proved through any experiments known to us. 

    And now, I was trying to master a track inside s1 and found some infos that shed some light on why S1's playback might sound a bit different from Sonar & CbB.

    In CbB and many other daws the playback is always in 32bit engine or 64bit engine(correct me if I'm wrong). But in some daws like S1 the playback is presented in the projects resolution. So if your projects are set to 24bit the daw does its internal processing in 32bit or 64bit(all daws process the signals in 32bit or above by default) then convert the audio to 24bit for playback. This introduces truncation error and hence generates noise which leads to some subtle harmonic differences. To avoid this S1 has option in settings “Use dithering for playback and audio file export.” If enabled all your playback and exports will be dithered by default. This is an usual solution to avoid the truncation noise. But again this is also noise, and in my experience both dithering and truncation noise always affects the audio quality.(there are many people who believe the effects of dithering and truncation are not audible, but I got my ears to believe in this with certainty). This is why I prefer to keep the project resolution to 32bit. This way there is no noise in playback or render(if you render to 32bit). When I render to 24bit or 16bit its again the same story and I end up with less optimal audio quality). I really wish that people who set the standards for audio long back pushed 32bit as the standard, and we wont be having any of these problems.

    As of S1, just set the projects resolution to 32bit and the audio playback wont be any diff from CbB playback . But's its just today I have come across this so for me its far to early to conclude. I will do a bit more listening with both CbB and S1 kept in 32bit and see if I hear any difference. 

    Any stupid assumptions have I made or wrong abt any of these technical infos that led me towards this pls do correct me. Hope someone with more inside knowledge on how the playback engine of CbB and S1 works chime in here and enlighten us. 


  4. Yes, If you are using internal soundcard. How good does your old notebook perform? If you are using internal soundcard make sure not to use Fast Bounce while exporting. Some systems produce bad quality Bounce if the CPU is peaking or the MB is heated up. But this totally depends on how good your old notebook is. You can install a cup meter gadget to always keep an eye on the cpu. Also the latency will improve with better specs


  5. Sorry for the brief op. I thought this will be a easy one. When I click on a midi note for what  ever reason (to drag, to see its details etc) the midi note makes its sound. This is the default way it works right? What if dont what the notes to make a sound when I click on them. Sometimes its too annoying when I have to make extensive editing and the synth sounds keep  on making noise every time I click, it makes the entire process unpleasant. Velocity Audition turns this off while doing velocity edits, doesn't seem to help while doing note edits. 


  6. 20 hours ago, Kevin said:

    A VCA is a Voltage Controlled Amplifier (VCA) and provides a means of easily controlling a group of faders, allowing the overall level of the grouped tracks to be brought up or down whilst maintaining the relative balance of the group members and retaining the individual track automation. VCA's work differently to aux faders and make it much easier to control group volume. 

    I do the same using  aux tracks. You mentioned VCA's work differently to aux faders. But in CbB I could do the same procedure you mentioned using Aux tracks. If I am wrong or missing something do correct me.


  7. Yes, that's just a different feature @Kevin Please watch the video link in the opening post to know more of the capture record feature. This link will also help http://logicprogem.com/Logic-Pro-X-Tutorials/Entries/2014/6/13_Capture_Recording__Logic_Pro_is_Always_Listening.html and I agree with one thing mentioned in this article. You don’t have to use the Capture Recording Button only as a safety net. I use it almost exclusively for any MIDI recording. You just play along with your song as it develops and every time you perform a good pass, you hit the Capture Recording Button and your performance is right there as a new MIDI Region.


  8. 1 hour ago, David Baay said:

    That's generally true for me, too, but  there have been many times over the years that something I played while improvising a new piece or rehearsing a part (lead solo, melody, bass line, high-hat pattern, whatever...) just worked perfectly, and I wished I had been recording because I couldn't reproduce it exactly. 

    I've mostly learned to just go ahead and hit 'R' when there's a chance some magic might happen, but I still miss things occasionally.

    Yea, there have been times I hit a few wrong notes or in the verge of messing up the timing but it ends up sounding soo good. I try to recreate them and eventually get closer to that but its never the same. Also this feature can be really helpful while working with a producer. If you forgot to hit the record button on some good takes the next few minutes will be really awkward. They might be even fantasizing on choking you 😰

    • Like 1

  9. @Jim Fogle this feature only applies to midi. This feature is always on in logic by default. I don't think you can disable it. You can hide the capture record magic button though. But I am no expert in logic so I can't confirm it. Midi data is microscopic in size and the captured data is only stored temporarily.

    Although this feature doesn't work for audio there seems to be a trick to capture audio. I am not sure if such a trick can be implemented in CbB. Someone please enlighten us. Here is an article that explains capturing audio http://logicprogem.com/Logic-Pro-X-Tutorials/Entries/2014/6/13_Capture_Recording__Logic_Pro_is_Always_Listening.html


  10. U can simply turn off the audio engine in cakewalk and play the video file or audio file from any media player.  U don't have to exit cakewalk. If you want to play both cakewalk and media player simultaneously u can change the driver mode as directed by scook. To turn off audio engine click on the icon below the now time meter in the control bars transport module. Once you are finished with the media player you can click the icon again to turn on the audio engine. 


  11. Not  sure how many are aware of the capture recording feature available in some daws like logic pro. I made this request long back in the old forum.To  me this is a feature that CbB must have. Use of this feature is enormous. This helps not only when you forgot to click the record button but also in enormous ways. Lot of times the best takes happens when you are simply trying out something with no conscience to record. This feature helps to capture those takes. Sometimes such precious takes are not recreateable. Magic happens spark happens and they deserve to be captured. Please implement this feature.

    Just in case if someone has no idea what this feature is, here is a video demonstrating this.
    https://www.youtube.com/watch?v=qOB4dFpipOU

     

    • Like 3

  12. Hey I just checked out the S1 Pipeline XT it has some new features like saving pictures or notes of the external hardware settings. Also shows up waveform of some sorts. The storing pictures or notes of external settings will be a very useful and handy feature. Hope CbB can implement something like this in its External Insert.


  13. @tecknotI'm sorry I wasnt clear in the first post. Thats how I insert markers. I press M and the Marker Dialog Box appears and I click enter. Another way is to press M on the flow while the transport is moving. Eitherway its cumbersome if I want all the markers to be locked in SMPTE time I need to select it everytime while entering or I have to open the markers view and open the Markers dialog of each marker and select lock to SMPTE. This could be made a little easier.
     


  14. I mean what I want is, I would like the Now Time to rewind to a specific Bar (lets say bar 5) everytime I hit the 'W' Key. I know by default it just goes back to zero. Is there any possible way this could be achieved? 
    Also I have  noticed some DAW's would rewind to some landmarks and you will have to repeatedly press the same key if you have to go back to Zero.  Not sure if CbB has anything similar.


  15. 25 minutes ago, Tezza said:

    I couldn't get hold of the S61 mki or the s49 mkii. They were both available in my area but they sold before I could get to them.

    I don't like the mki because it has those touch strips instead of the solid pitch and modulation wheels. I could live with it though, at least you can turn the lights off. On the markii you cannot turn the lights off. I couldn't live with that.

    They have the Fatar keybed which is supposed to be good. Some are saying that the A series kontrol keybeds are also good. I won't buy another keyboard without testing it out though. I get what you are saying about testing on the DAW, Keybed has to be good and velocities also, I don't know how you do that though other than buy secondhand and if you don't like then move on. The nearest music shop to me is about 100kms away. They don't carry a lot and what they do carry, you can't really try in the shop as they are not hooked up.

     

    Yea I  totally understand. There are some online retailers in my area who would accept return within 10days are so if I am unhappy with it by charging a 15% of the MRP. Its kind of a good deal for them since they are getting 15% profit without even selling the product. Another gud idea to demo any gear is to see if any commercial studios nearby have them and then book a hourly session and try them out. I did that to demo some monitors and headphones. Try your luck.


  16. On 7/24/2019 at 8:31 PM, Tezza said:

    Well said! It's like the cheaper midi controllers with "piano feel" keybeds are fighting against you when you play them, constant pressure against your fingers as opposed to the synth style controllers which are not that bad. I've found that in general, keybeds with aftertouch always seem a little better. Even the Samson 49 I tried was nice as was the Novation impulse and Roland A500 but they all come with baggage when it comes to setting them up, getting a bit old in the tooth now I guess. Looking for a basic high quality midi keyboard controller by itself (with no faders/pots etc) seems impossible, the only one I can think of is the studio logic series which are as rare as hens teeth here in Australia and quite expensive to buy new. Even the newer stuff, the Nektar P and T series are not getting great reviews when it comes the the keybed.

    I've got a chance at trying a Kontrol s61 mk1 tomorrow, they are supposed to have nice keys. The new A series Kontrol keyboards seem to be getting good reviews regarding their keys despite being the cheaper version of the S series. I've not tried either the Kontrols or the Arturias yet. They are next on the list. I would be interested in your opinion of the Arturia when you get to try it.

    Tried the Arturia keylab essentials in a local shop, the keys are nice. Very less resistance and really had a premium feel. However I am sure the only way to get to know the keybed is to connect to a daw and start playing for real. Most stores dont allow this for midi controllers. But I'm sure this is the best keybed I have got my hands on in this price range. I also noticed that, since ive been paying the hard resistance springy keys of maudio keystation for a while, playing in the keylab felt bit awkward as if its hard to maintain a grip and timing. I guess it gets okay with practice but probably this is why many people prefer keys with high resistance (with a premium action perhaps). I guess while playing instruments like piano I would still prefer the action of keystation, but to play rhodes, leads, pads or organs keylab keys will be amazing.  btw I am just speculating, like I said I couldn't demo it with a sound source. And regarding the samson carbon, I have read tons of reviews online that they feel so nice to play but their velocity response in horrible. Perhaps thats again a thing to stress on the fact that you only get to know 60% of the keybed by demoing without connecting to a sound source. I've been trying to demo the S61 aswell but these stores here rarely have them and even if they do they prefer to sell it closed box. Do let me know if you demo the S61. 


  17. On 7/21/2019 at 12:46 PM, Tezza said:

    With the LX, it helps to clarify what model you are talking about, the older LX61, which I have, works fine for me but I have seen some complaints regarding integration with Cakewalk about the LX61+ which is the newer model, they are pretty much the same, except flashing leds and a couple of other things. They do use different integration files from Nektar though.  

    I also have the GX61 (new model) and that has very different key action to my LX61 but it could be the same as the newer LX61+, I don't know. I find the LX (older version) to have easier to play keys that seem to have lower travel (synth like?), I can do a run more easily and reach for more complex chords and play them cleanly. The GX seems to have more travel and stiffer to play (more piano like) which makes these things more difficult for me. I have shorter fingers though.

    For me, same as using .10 gauge strings vs .09 on my Strat. If I use the GX and .10 gauge strings on the Strat, it takes more effort and my fingers tire more quickly. I've opted for the LX and .09 gauge strings which is like coming home, I can play both instruments all day without thinking about it.

     

    Yes thats one detail I missed. The LX I tried was mostly LX61 and the GX I tried was GX61+. The diff might have been due to the newer model. I dont remember abt the difference in key travel or failed to notice that but the LX had low resistance to press or hold down the keys. while the GX+ had high resistance to both pressing and holding and it was really uninspiring to play. I dont understand why they try a piano like resistance in these cheap boards. Piano like resistance is great but in a real piano the mechanism is totally different. To match that they will have to implement a really meticulously crafted mechanism. On a basic level the piano keys have high resistance only when you start pressing them i.e the resistance lasts only when you start triggering the key, after you have moved the keys  for abt 2mm then its easy to further press them and also easy to hold them. I do like the resistance of piano keys but these cheap controllers cant reproduce anything thats even close to that, so just putting strings on them with stronger resistance is bad idea which is what I felt how the GX+ keys where like. AT the same time cheep keys made with very low resistance themselves are a pleasure to play, while playing synths. Which is what I expected while trying these models. I'm gonna try the arturia keylab next, just for the keys.

    • Like 1

  18. When I tried these keyboards the GX61 had bad Key action compared with LX. But Nectar says they are the same. There are some variations aswell due to bad quality control from these manufactures. Its always a good option to demo and buy. But more often you will notice most things only after you set it up and start using it for a day or two.

×
×
  • Create New...