| 2012-11-29 22:13:07 |
RAWRR |
bug |
|
|
added bug |
| 2012-11-29 22:49:27 |
Daniel Schürmann |
mixxx: status |
New |
Confirmed |
|
| 2013-02-10 00:37:50 |
RJ Skerry-Ryan |
mixxx: status |
Confirmed |
Fix Committed |
|
| 2013-02-10 00:37:53 |
RJ Skerry-Ryan |
mixxx: assignee |
|
RJ Ryan (rryan) |
|
| 2013-02-10 00:37:55 |
RJ Skerry-Ryan |
mixxx: importance |
Undecided |
Low |
|
| 2013-02-10 00:37:57 |
RJ Skerry-Ryan |
mixxx: milestone |
|
1.11.0 |
|
| 2013-02-10 00:41:46 |
RJ Skerry-Ryan |
mixxx: milestone |
1.11.0 |
|
|
| 2013-02-10 00:41:48 |
RJ Skerry-Ryan |
mixxx: assignee |
RJ Ryan (rryan) |
|
|
| 2013-02-10 00:41:51 |
RJ Skerry-Ryan |
mixxx: status |
Fix Committed |
Confirmed |
|
| 2014-08-21 17:06:57 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension? I don't know what needs to happen. But I would REALLY love portable analysis data.
Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something (not a huge priority). |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
<strike>Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?</strike> I don't know what needs to happen. But I would REALLY love portable analysis data.
<strike>Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something</strike> (not a huge priority). |
|
| 2014-08-21 17:09:27 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
<strike>Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?</strike> I don't know what needs to happen. But I would REALLY love portable analysis data.
<strike>Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something</strike> (not a huge priority). |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
[s]Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?[/s] I don't know what needs to happen. But I would REALLY love portable analysis data.
[s]Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something[/s] (not a huge priority). |
|
| 2014-08-21 17:13:54 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
[s]Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?[/s] I don't know what needs to happen. But I would REALLY love portable analysis data.
[s]Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something[/s] (not a huge priority). |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
<s>Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?</s> I don't know what needs to happen. But I would REALLY love portable analysis data.
<s>Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something</s> (not a huge priority). |
|
| 2014-08-21 17:15:08 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
<s>Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?</s> I don't know what needs to happen. But I would REALLY love portable analysis data.
<s>Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something</s> (not a huge priority). |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
<del>Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?</del> I don't know what needs to happen. But I would REALLY love portable analysis data.
<s>Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something</s> (not a huge priority). |
|
| 2014-08-21 17:29:56 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
<del>Maybe the data could be stored in the same directories as the songs, using the same filenames but with an appropriate extension?</del> I don't know what needs to happen. But I would REALLY love portable analysis data.
<s>Somewhere down the line I'd even be into some extra function that could add the data to the song itself via id3 or something</s> (not a huge priority). |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ ̶e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority). |
|
| 2014-08-21 17:40:09 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ ̶e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority). |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ ̶e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority).
I now think id3 and/or same directory are bad ideas. I would better like the data to end up in a single blob (like messages.dat in Bitmessage) for portability, or for it to end up with analysis data in "Application Data\Mixxx\analysis" or perhaps "Application Data\Mixxx\trackdata" etc.
This should not affect basic ID3 editing functions, of course.
Regarding "more portable", it would also help if somehow the track data could end up *not* taking up almost a gigabyte of space. VirtualDJ saves waveforms too, but somehow does it without enormous space requirements. |
|
| 2014-08-21 17:43:48 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ ̶e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority).
I now think id3 and/or same directory are bad ideas. I would better like the data to end up in a single blob (like messages.dat in Bitmessage) for portability, or for it to end up with analysis data in "Application Data\Mixxx\analysis" or perhaps "Application Data\Mixxx\trackdata" etc.
This should not affect basic ID3 editing functions, of course.
Regarding "more portable", it would also help if somehow the track data could end up *not* taking up almost a gigabyte of space. VirtualDJ saves waveforms too, but somehow does it without enormous space requirements. |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶
e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶
t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority).
I now think id3 and/or same directory are bad ideas. I would better like the data to end up in a single blob (like messages.dat in Bitmessage) for portability, or for it to end up with analysis data in "Application Data\Mixxx\analysis" or perhaps "Application Data\Mixxx\trackdata" etc.
This should not affect basic ID3 editing functions, of course.
Regarding "more portable", it would also help if somehow the track data could end up *not* taking up almost a gigabyte of space. VirtualDJ saves waveforms too, but somehow does it without enormous space requirements. |
|
| 2014-08-21 17:44:37 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶
e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶
t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority).
I now think id3 and/or same directory are bad ideas. I would better like the data to end up in a single blob (like messages.dat in Bitmessage) for portability, or for it to end up with analysis data in "Application Data\Mixxx\analysis" or perhaps "Application Data\Mixxx\trackdata" etc.
This should not affect basic ID3 editing functions, of course.
Regarding "more portable", it would also help if somehow the track data could end up *not* taking up almost a gigabyte of space. VirtualDJ saves waveforms too, but somehow does it without enormous space requirements. |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶
t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶
t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority).
I now think id3 and/or same directory are bad ideas. I would better like the data to end up in a single blob (like messages.dat in Bitmessage) for portability, or for it to end up with analysis data in "Application Data\Mixxx\analysis" or perhaps "Application Data\Mixxx\trackdata" etc.
This should not affect basic ID3 editing functions, of course.
Regarding "more portable", it would also help if somehow the track data could end up *not* taking up almost a gigabyte of space. VirtualDJ saves waveforms too, but somehow does it without enormous space requirements. |
|
| 2015-03-12 06:28:50 |
RAWRR |
bug |
|
|
added subscriber Be |
| 2015-03-12 06:30:55 |
RAWRR |
bug |
|
|
added subscriber lacsaP |
| 2015-03-12 06:38:54 |
RAWRR |
summary |
make BPM/waveform analysis data portable |
make BPM/waveform analysis data portable, **especially important for live distros** |
|
| 2015-03-12 06:45:56 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
M̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶d̶a̶t̶a̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶s̶t̶o̶r̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶i̶r̶e̶c̶t̶o̶r̶i̶e̶s̶ ̶a̶s̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶s̶,̶ ̶u̶s̶i̶n̶g̶
t̶h̶e̶ ̶s̶a̶m̶e̶ ̶f̶i̶l̶e̶n̶a̶m̶e̶s̶ ̶b̶u̶t̶ ̶w̶i̶t̶h̶ ̶a̶n̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ e̶x̶t̶e̶n̶s̶i̶o̶n̶?̶ I don't know what needs to happen. But I would REALLY love portable analysis data.
S̶o̶m̶e̶w̶h̶e̶r̶e̶ ̶d̶o̶w̶n̶ ̶t̶h̶e̶ ̶l̶i̶n̶e̶ ̶I̶'̶d̶ ̶e̶v̶e̶n̶ ̶b̶e̶ ̶i̶n̶t̶o̶ ̶s̶o̶m̶e̶ ̶e̶x̶t̶r̶a̶ ̶f̶u̶n̶c̶t̶i̶o̶n̶ ̶t̶h̶a̶t̶ ̶c̶o̶u̶l̶d̶ ̶a̶d̶d̶
t̶h̶e̶ ̶d̶a̶t̶a̶ ̶t̶o̶ ̶t̶h̶e̶ ̶s̶o̶n̶g̶ ̶i̶t̶s̶e̶l̶f̶ ̶v̶i̶a̶ ̶i̶d̶3̶ ̶o̶r̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ (not a huge priority).
I now think id3 and/or same directory are bad ideas. I would better like the data to end up in a single blob (like messages.dat in Bitmessage) for portability, or for it to end up with analysis data in "Application Data\Mixxx\analysis" or perhaps "Application Data\Mixxx\trackdata" etc.
This should not affect basic ID3 editing functions, of course.
Regarding "more portable", it would also help if somehow the track data could end up *not* taking up almost a gigabyte of space. VirtualDJ saves waveforms too, but somehow does it without enormous space requirements. |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move and recognize the analysis data itself wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
|
| 2015-03-12 06:46:32 |
RAWRR |
description |
This is a wishlist feature.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move and recognize the analysis data itself wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move and recognize the analysis data itself wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
|
| 2015-03-12 06:49:35 |
RAWRR |
description |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move and recognize the analysis data itself wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move tjhe analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
|
| 2015-03-12 06:50:04 |
RAWRR |
description |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move tjhe analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move the analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
|
| 2015-03-12 06:51:06 |
RAWRR |
description |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move the analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems. |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move the analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems.
Analysis data is very important. See bug #1431168. |
|
| 2015-03-12 06:53:18 |
RAWRR |
description |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move the analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems.
Analysis data is very important. See bug #1431168. |
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder.
**EDIT 2015 04 12**
It has come to my attention that this bug as originally suggested, meaning being able to move the analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of end-user customization, something live environments are not typically engineered for. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the .Mixxx directory in the live tree, and even then the paths would potentially cause problems.
Analysis data is very important. See bug #1431168. |
|
| 2016-09-26 07:19:41 |
Daniel Schürmann |
tags |
analysis bpn data library waveform |
analyzer library metadata waveform |
|
| 2022-10-08 19:29:58 |
Swiftb0y |
bug watch added |
|
https://github.com/mixxxdj/mixxx/issues/6728 |
|
| 2022-10-08 19:29:59 |
Swiftb0y |
lock status |
Unlocked |
Comment-only |
|
