Allow export of loop from deck to sampler.

Bug #878549 reported by RJ Skerry-Ryan
82
This bug affects 17 people
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Wishlist
Unassigned

Bug Description

As in the description of Ryan Baker for the sampler Feature he puts

DJ Awesome wants to sample directly from a playing song and use this to create on the fly remixes and loops. You should be able to sample directly from a playing song.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Wishlist
tags: added: sampler
tags: added: looping
Carl Pillot (cpillz)
Changed in mixxx:
assignee: nobody → Carl Pillot (cpillz)
Revision history for this message
RAWRR (rawrr) wrote :

Something as simple as taking a loop selected the traditional way (the in/out section from a deck) and shoving it down to a selected sampler, sort of a "hold this chunk of track in sampler" scenario would be so awesome.

I wonder if there would be a way that you could just instruct the sampler to grab the whole file but only show the looped section? That way there wouldn't need to be any file creation/encoding of new file. Just some way to make the sampler focus exclusively on a section defined by the loops set in Deck...

Carl Pillot (cpillz)
Changed in mixxx:
status: Confirmed → In Progress
Revision history for this message
Be (be.ing) wrote :

What's up with this? It has been marked as "In Progress" for over a year.

It should be possible to adjust the length of the loop after it is already in the sample deck. That is, the whole track would be in the sample deck with a loop automatically on it, rather than cutting out the loop.

It would be really awesome if saving a loop could automatically set hot cues at quantized points in the loop, somewhat like Serato Itch's slice mode. The number of hot cues should be configurable to accommodate skins and controllers with different numbers of buttons. For example, a 2x4 grid of buttons, common on many controllers, could be mapped to 8 hotcues on a loop, or 4 hotcues on two different sample decks. So, saving a 4 beat loop with 4 hotcue points would chop it up into quarter notes, or saving it with 8 hotcue points would chop it into eigth notes. Combined with Mixxx's ability to set loops of different numbers of beats, and the ability to change the length of the loop as described above, this could be a very powerful and fun feature for live remixes and mashups.

Revision history for this message
Carl Pillot (cpillz) wrote : Re: [Bug 878549] Re: Allow export of loop from deck to sampler.

Currently no active development is happening on this. It may pick up after
1.12 is released.

On Mon, Dec 29, 2014 at 2:45 PM, Be <email address hidden> wrote:

> What's up with this? It has been marked as "In Progress" for over a
> year.
>
> It should be possible to adjust the length of the loop after it is
> already in the sample deck. That is, the whole track would be in the
> sample deck with a loop automatically on it, rather than cutting out the
> loop.
>
> It would be really awesome if saving a loop could automatically set hot
> cues at quantized points in the loop, somewhat like Serato Itch's slice
> mode. The number of hot cues should be configurable to accommodate skins
> and controllers with different numbers of buttons. For example, a 2x4
> grid of buttons, common on many controllers, could be mapped to 8
> hotcues on a loop, or 4 hotcues on two different sample decks. So,
> saving a 4 beat loop with 4 hotcue points would chop it up into quarter
> notes, or saving it with 8 hotcue points would chop it into eigth notes.
> Combined with Mixxx's ability to set loops of different numbers of
> beats, and the ability to change the length of the loop as described
> above, this could be a very powerful and fun feature for live remixes
> and mashups.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/878549
>
> Title:
> Allow export of loop from deck to sampler.
>
> Status in Mixxx:
> In Progress
>
> Bug description:
> As in the description of Ryan Baker for the sampler Feature he puts
>
> DJ Awesome wants to sample directly from a playing song and use this
> to create on the fly remixes and loops. You should be able to sample
> directly from a playing song.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/878549/+subscriptions
>

Revision history for this message
Ferran Pujol (ferranpujol) wrote :

Isn't this achievable with the loop recorder? https://blueprints.launchpad.net/mixxx/+spec/loop-recorder
Otherwise if I understood it well, it will suffice to support instant doubles from deck to sample.

Be (be.ing)
Changed in mixxx:
status: In Progress → Confirmed
Revision history for this message
Damian Wheel (tfwnogf) wrote :

Are there any news on this (10 years old!) feature request?

Revision history for this message
Be (be.ing) wrote :

Kinda. In the main branch Mixxx can save loops as hotcues. The track could then be loaded into a sampler.

Revision history for this message
Carl Pillot (cpillz) wrote :

I am not working on this and probably never will.

On Sat, Sep 11, 2021 at 9:45 AM Damian Wheel <email address hidden>
wrote:

> Are there any news on this (10 years old!) feature request?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/878549
>
> Title:
> Allow export of loop from deck to sampler.
>
> Status in Mixxx:
> Confirmed
>
> Bug description:
> As in the description of Ryan Baker for the sampler Feature he puts
>
> DJ Awesome wants to sample directly from a playing song and use this
> to create on the fly remixes and loops. You should be able to sample
> directly from a playing song.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/878549/+subscriptions
>
>

Foss-4 (foss-4)
Changed in mixxx:
assignee: Carl Pillot (cpillz) → nobody
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6026

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.