Export set list

Bug #766814 reported by Mark Booth
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Wishlist
Daniel Schürmann

Bug Description

Feature request
Would it be possible to get Mixxx to create a set-list of all the tracks played during a session? Just a simple text file would be fine.

Related branches

Revision history for this message
jus (jus) wrote :

FYI a session history feature for Mixxx is part of the Google Summer of Code 2011 so exporting a setlist should be possible in the foreseeable future. http://mixxx.org/wiki/doku.php/gsoc2011ideas#session_history_feature

Revision history for this message
Phillip Whelan (pwhelan) wrote :

Trunk also has support for recording CUE files, http://en.wikipedia.org/wiki/Cue_file, when recording to a file.

jus (jus)
Changed in mixxx:
importance: Undecided → Wishlist
jus (jus)
Changed in mixxx:
status: New → Confirmed
Revision history for this message
Daniel Schürmann (daschuer) wrote :

It is possible to export a m3u Playlist from a set-log with lp:~daschuer/mixxx/features_setlog

Changed in mixxx:
assignee: nobody → Daniel Schürmann (daschuer)
Changed in mixxx:
status: Confirmed → In Progress
Revision history for this message
Jens Nachtigall (nachtigall) wrote :

> It is possible to export a m3u Playlist from a set-log with lp:~daschuer/mixxx/features_setlog

I think a m3u is not the same. What I personally (and I think also the bug reporter) would like is the mix's playlist in txt form like

1 interpret name - title
2 interpret name - title
3 interpret name - title

maybe also the track duration / time. This would be very useful for creating a cd cover (if the mix is burned to CD) or if the mix is uploaded to sound- or mixcloud in order to give a list of track played (for mixcloud such a track list is even mandatory, I do not know if cloudmix requires a certain txt format. If it does then one could maybe follow there requirements). What I currently do to have such a list, is by hand editing of the cue file in a text editor and rearrange the listed information there - very cumbersome.

there was also a poll here about it:
http://www.mixxx.org/forums/viewtopic.php?f=1&t=2463&view=viewpoll

i think that this is similar to the "create cue file" option for recordings but simply other output formats.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Hi Jens,

I have recently added, a csv export feature. Does this fulfil your requirements?
The cue INDEX feature is still missing, because we need a database schema update for that.

I have noticed that the text export has the most votes at the forum. Somehow, all output files have a text format.

What about exporting a mixcloud txt format? Do you have an example?

I have just notice that they have an API http://www.mixcloud.com/developers/documentation
I have not figured out so far, if we might upload the set log directly from Mixxx.
What do you think?

Cheers Daniel

Revision history for this message
Jens Nachtigall (nachtigall) wrote : Re: [Bug 766814] Re: Export set list

Am 30.11.2011 11:45, schrieb Daniel Schürmann:
> I have recently added, a csv export feature. Does this fulfil your requirements?
> The cue INDEX feature is still missing, because we need a database schema update for that.

Yes and no. Yes, because surely I can with some spreadsheat fiddling get
my preferred txt output from this (at least easier then fiddling with
the cue file). No, because actually I do not want to fiddle around with
spreadsheats just to get a simple tracklist of a mix.

> I have noticed that the text export has the most votes at the forum.
> Somehow, all output files have a text format.
>
> What about exporting a mixcloud txt format? Do you have an example?

It is very simple, just:
Artist1 - Track1
Artist2 - Track2
Artist3 - Track3
...

I think this is what most people want. Such a .txt file should simply be
droped in the Recordings folder.

>
> I have just notice that they have an API http://www.mixcloud.com/developers/documentation
> I have not figured out so far, if we might upload the set log directly from Mixxx.
> What do you think?

No, absolutely not necessary. I would not even use such a feature since
on the web upload you usually can add an image and other information.
And you have more control over what is done instead of automagic upload.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Now it possible to export a Readable Text Playlist from a set-log with lp:~daschuer/mixxx/features_setlog.
Like:
1 interpret name - title
2 interpret name - title
3 interpret name - title

I have played around with the mixcloud upload and found out that they support list separated with dashes and comma (*.csv) format. They support:
Artist - Titel
Artist - Titel - Label
Artist,Titel,Label
"Artist"Titel","Label"
Artist - Titel(Label)
A leading number with a dot is ignored. A number without dot causes that the first letter of the artist is ignored.
Unfortunatly the can not handle embedded dashes, but that's their problem.

In forum ther was mentioned the 1001tracklists format. This is described here:
http://www.1001tracklists.com/create/tracklist.php?new

01. 00:00 artist - trackname (remixer remixname)
02. 04:30 ID
03. 08:00 artist2 - trackname2 (...)

This format is not excepted by mixcloud because of the additional Cue information.

Should we extend our "Readable Text" format with these Cue information when we have it in database?

In any case I will change the playlist position format to a "01."

Revision history for this message
Jens Nachtigall (nachtigall) wrote :

Am 01.12.2011 11:31, schrieb Daniel Schürmann:
> In forum ther was mentioned the 1001tracklists format. This is described here:
> http://www.1001tracklists.com/create/tracklist.php?new
>
> 01. 00:00 artist - trackname (remixer remixname)
> 02. 04:30 ID
> 03. 08:00 artist2 - trackname2 (...)
>
> This format is not excepted by mixcloud because of the additional Cue
> information.
>
> Should we extend our "Readable Text" format with these Cue information
> when we have it in database?

Yes, this looks nice. The cue information is good, because very often
people ask "what track is this at minute 50?" and then you know it in a
description field of the mix on the web and people can easily look it up.

> In any case I will change the playlist position format to a "01."

ok, I do not really care about dot or not dot ;)

anyway: great and thanks! I will test it if i have time :)

jus (jus)
Changed in mixxx:
status: In Progress → Fix Committed
milestone: none → 1.11.0
RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
follower (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1ohg85w3jabxlrqbgszpjpwcmvkbcvq9spp6z3w5j1m33k06tlsfszeuscyt241h-launchpad-a811i2i3ytqlsztthjth0svbccw8inm65tmkqp9sarr553jq53in4xm1m8wn3o4rlwaer06ogwvqwv9mrqoku2x334n7di44o65qze67n1wneepmidnuwnde1rqcbpgdf70gtqq2x9thj5tlcsac) wrote :

FWIW, I wrote a script to convert from the .csv format Mixxx outputs to a format ("Artist"Title") that the track list text area will accept when pasted into it. (It probably doesn't work if either value contains a " character.)

The script is here: https://github.com/follower/mixcloud-munger/blob/master/mixcloud-munger.py

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Thank you.

I am afraid this will be lost here, since the bug is "Fixed Released"
You may post it at http://www.mixxx.org/forums/viewforum.php?f=6&sid=f376269aab59af26ab4e5a2bb46e1a5f as well.

You upload the recorded mix and you paste the Tracklist in a second step, right?
How does it work at Mixcloud to set the cue points?

Could it become a part of the recording feature?
Option:
* create Cue Sheet
* Create "Artist"Title" file
* future: Save Serato playlist ;-)

If yes, you may file a new Bug for this.

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/5866

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 blueprints

Remote bug watches

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