Announcement

Collapse
No announcement yet.

Truncate

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Truncate

    Hello wonderful people at 1010music!

    A destructive truncate / trim / crop option for samples would be super great!


    It would improve load time for recorded samples with unused parts as well as being very helpful when exporting recorded samples for later use or external processing.

    Sample cells and clip cells would also improve from this, as you'd be able to set a "max" start point, when modulating the start parameter, so you won't be playing silence or untight samples by accident.

  • #2
    I concur. As on blackbox?

    Comment


    • #3
      +1000

      i consider a truncate function as absolutely necessary to move the bitbox towards beeing a finished module.
      As is now is it looking to me like a work in progress.
      while you´re allready selling your next work in progress............./ tired of that

      Comment


      • #4
        We have a process that builds our data warehouse.
        The processes execute SPs in serial order.
        Each SP builds separate table.
        Each table is build destructive (truncate and Insert Into).

        I've tried to change the configuration by running 4 SP in parallel by SSIS to shorten the update time.
        I've noticed in two declines in performance:
        1. Each SP execution time is higher in the parallel execution in around 50% then in the serial execution. The CPU utilization is the same.
        2. On each parallel execution we have a decline in performance of around 5 -10% compare to the previous parallel execution.

        Do you have any directions to inquire?

        Comment


        • vantablack
          vantablack commented
          Editing a comment
          Ja, logic dictates that one should look at other factors beside CPU.
      Working...
      X