Jump to content

murat k.

Members
  • Posts

    577
  • Joined

  • Last visited

Posts posted by murat k.

  1. When theTempo Track is at minimal height, it snaps to integers,only if we don't have any decimals on any Tempo. 

    But when we extend the height of the Tempo Track we start to see decimals on the Tempo when we draw.

    Can we get a fixed increment with an INI setting for drawing Tempos like:

    TempoDrawIncrement = 1

    or if we want more specific increment like:

    TempoDrawIncrement = 8

    or if we want decimals:

    TempoDrawIncrement = 0.1

    So we will able to draw Tempos in our desired setting regardless of theTempo Track height on the view.

  2. 12 hours ago, Starship Krupa said:

    Drawing automation already ignores snap settings. Try it. While the Aim Assist line will snap to the nearest snap point, you can place a node wherever you have the cursor. It's easier to see when you have snap set to a higher value, like a whole note.

    To me, this is a bug, but it seems like for you, maybe a blessing.

    To be clear, when the Snap is on, the automation is drawing by the PRV snap distance.

  3. Punch does not mute existing audio when recording and there is a preference called "Mute Previous Takes"

    But when we record with Punch with Mute Previous Takes preference is selected, and if the clip begins outside of the punch area, it mutes that part of the clip.

    And when we stop recording all part of the clip inside the Punch area remains Muted.

    I am aware of unmuting notes/waves with the Mute tool but this is an extra process after every recording.

    Why do I hear existing audio when recording with Punch even if the record mode is Comping?

    Punch recording has to work like "Recording with selected recording mode only for the selected area"

    Nothing more.

  4. 13 minutes ago, Noel Borthwick said:

    Well even if they are doing WASAPI they are likely using WASAPI Exclusive mode rather than WASAPI shared. WASAPI shared mode cannot go lower than 10 msec for any USB devices so there isn't anything they could do to enable that. It's at the OS level.

    I already know that. This is why I said:

    8 hours ago, murat k. said:

    Image-Line did the job which Microsoft was supposed to do with this ASIO driver.

    It works like WASAPI Shared Driver. But at the same time it gives low latency. And why

    15 minutes ago, Noel Borthwick said:

    We don't flag the FL studio driver

    I had no issues with this driver even once. You can flag it and give no warning to the users when they select and use this driver.

  5. 12 hours ago, Noel Borthwick said:

    This is why we advise never installing or using these drivers. What they do is hook into Windows and utilize the audio device via low level WDM.
    Since at startup time Cakewalk loads all drivers to check for availability, when we hit this driver, it causes symtoms like you saw even if you never intended to use it. Sometimes it will even change the sample rate of your audio interface as a result of being loaded.
    The best solution is to remove these ASIO wrapper drivers from your system so Cakewalk never sees them.

    One thing I've been wanting to do is to change how Cakewalk starts up to avoid loading all ASIO drivers once one has been selected by the user. This might help alleviate problems like this. Its a pretty big change so will have to wait for when I have time to tackle that.

    But we can say "Except FL Studio ASIO driver"
    FL Studio ASIO driver is different from the other ASIO Drivers because it's not a WDM wrapper. It's a WASAPI wrapper. 
    And with the new Cakewalk release 2022.11, performs better with the performance improvement in WASAPI mode by selecting the preference "Enable MMCSS for ASIO Driver"
    We can call it "Low Latency WASAPI Shared Mode". Image-Line did the job which Microsoft was supposed to do with this ASIO driver.

  6. 2 hours ago, azslow3 said:

    "FL Studio/ASIO4ALL/other generic" ASIO is visible from applications as ASIO. But they have to access hardware driver, which is not ASIO.

    FL Studio ASIO is a WASAPI drive actually.

    This is why the file's name is ILWASAPI2ASIO. Means Image Line (company name) WASAPI (The actual driver) To ASIO (Acts like an ASIO driver)

    2 hours ago, azslow3 said:

    Note that is not automatically expensive. Like 8 years ago I have payed around 20€ for M-Audio Audiophile FireWire, it has own ASIO and allows other apps in parallel. And it is still my "default" interface for desktop

    Thanks for the suggestion. I was thinking to buy a simple mixer to route audios which is cheaper than you suggest then I gave up because I have no trouble with latency anymore with this solution. Also these are extra profits which comes besides working with multiple interfaces:

    11 hours ago, murat k. said:

    Also, it reduces the CPU load on the DAW, you can see the difference when you switch between WASAPI and FL Studio ASIO.
    And also you can switch the active playback/recording sound device easily without having to open the Preferences menu.

    And the new prefence "Enable MMCSS for ASIO Driver" made it better. In the past sometimes I was getting audio crackling on the playback, nowadays I don't get any issues.

  7. 44 minutes ago, Alan Tubbs said:

    Asio4all wasn’t any good 10 years ago and I haven’t heard a good thing about it in the last 10 years.  Everybody who has used it has moved on.  If your interface didn’t come with custom drivers and the generic drivers don’t get the job done, why would a another layer of cludge work?

    Actually the topic is about FL Studio ASIO vs WASAPI now. But thanks for sharing your thoughts. 🙂

  8. I have had no issue with ASIO4All since I found a way to use it. In the beginning, people get some issues and leaves it, but after getting its working principle, you can handle it without a problem.
    But the problem with ASIO4All and some other drivers, you can't get sound outside of the DAW. There is a solution with WASAPI Shared but it has too much latency. With the MME(32bit) you get sound crackling eventually. Suspending the Audio engine is not working all the time depending on the task you want. 
    With FL Studio ASIO you don't get any issues with the sound or latency. I mean it also focuses on your DAW, but still allows you to hear/send other audio on your PC and still get low latency.
    Yes, there is a way to get low latency with no audio issues. Having multi-input/output soundcard with the internal one and connecting one to another. But you don't need this since you have a working solution called FL Studio ASIO.
    Also, it reduces the CPU load on the DAW, you can see the difference when you switch between WASAPI and FL Studio ASIO.
    And also you can switch the active playback/recording sound device easily without having to open the Preferences menu.
    This is why I recommend FL Studio ASIO to people when the topic comes to sound drivers. I tried all others and came back to it all the time. 

  9. It seems that you didn't installed it. No problem, you'll figure it out.

    FL Studio ASIO will give you low latency with Shared device like support. This means you'll get no input/output issue anymore and get no "playback error" issue inside or outside of the Cakewalk when it's running.

    I tried all other driver modes in the past but FL Studio ASIO Driver is the best for work efficiency.

  10. Also having an option to color them, filtering the markers view by color and navigating between the same marker color shortcuts will be useful.

    I mean we can separate the markers by color used for different purposes. They can be used for notes (just like the OP), timing, pitching, chords etc. 

    Filtering the view of  the markers by color will be also useful if the markers seems so much and complicated in the Timeline and the Markers View.

    And if there is a shortcut like "Next/Previous Marker with the same color", navigating between the markers which have same purpose will be possible. It will act like the same as "Next/Previous Marker" shortcut at first use to jump a marker, and if it's already at a marker shortcut will jump to the next marker which has the same color. And Next/Previous marker commands will only work for visible Markers in the view at this way.

    These ideas are for the case of wanting to be developed by preserving the existing state of markers in the Cakewalk instead of making Marker Tracks like Cubase have.

    • Great Idea 1
  11. On 11/23/2022 at 10:30 PM, Kurre said:

    . The paste special confirmed the  now time and had the number of copies, 2, and event was checked but automation unchecked. Ok then...

    There was only one clip pasted. It did not paste at the now time at 10:03:00 but was located a couple of beats later. 🙀

    It seems that there is an issue with the "Paste Special". I haven't encountered the issue but you're not the only one having this:

×
×
  • Create New...