| 2015-03-12 06:21:48 |
RAWRR |
bug |
|
|
added bug |
| 2015-03-12 06:22:37 |
RAWRR |
description |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so as you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had bee pointed out to me early on, it would have saved me loads of grief.
Sometimes things you think are obvious just aren't. |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so as you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had bee pointed out to me early on, it would have saved me loads of grief.
Sometimes things you think are obvious just aren't. |
|
| 2015-03-12 06:24:01 |
RAWRR |
description |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so as you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had bee pointed out to me early on, it would have saved me loads of grief.
Sometimes things you think are obvious just aren't. |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so as you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had been pointed out to me early on, it would have saved me loads of grief.
Sometimes things that seem obvious just aren't. |
|
| 2015-03-12 06:25:24 |
RAWRR |
description |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so as you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had been pointed out to me early on, it would have saved me loads of grief.
Sometimes things that seem obvious just aren't. |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so the first time you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had been pointed out to me early on, it would have saved me loads of grief.
Sometimes things that seem obvious just aren't. |
|
| 2015-03-12 06:26:03 |
RAWRR |
description |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so the first time you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had been pointed out to me early on, it would have saved me loads of grief.
Sometimes things that seem obvious just aren't. |
It may seem obvious to a lot of people, but it has taken me awhile to realize that generating waveforms on the fly during a set can be really dangerous, leading to all kinds of overflows and cutouts and stutter and embarrassment. Whether it was me being stupid or not, there is no reason that this needs to be an unspoken detail or one that users should have to RTFM to discover.
Considering the use ethic of the project, I think adding this should be a no-brainer. Suggested text:
"Welcome to Mixxx! Word to those intending to use Mixxx in a professional setting: Mixxx will generate waveforms and beatgrids for every track in your library, and by default it will do so the first time you play each track. HOWEVER - this can require a significant amount of system resources. For professional use, it is better to use the 'Analyze' feature to pre-generate waveforms and beatgrids for all your tracks *before* a set, so that all of your system's resources can go toward playing the music."
Edits obviously warranted, but there is the general idea.
If this had been pointed out to me early on, it would have saved me loads of grief.
Sometimes things that seem obvious just aren't. |
|
| 2015-03-13 14:22:20 |
Be |
bug |
|
|
added subscriber Be |
| 2016-09-26 07:16:20 |
Daniel Schürmann |
tags |
analyze beatgrid beatgrids notification notifications polish waveform waveforms |
analyzer waveform |
|
| 2018-01-04 07:15:05 |
Be |
mixxx: status |
New |
Confirmed |
|
| 2018-01-04 07:15:08 |
Be |
mixxx: importance |
Undecided |
Low |
|
| 2018-01-04 07:15:15 |
Be |
tags |
analyzer waveform |
analyzer usability waveform |
|
| 2022-10-08 20:09:55 |
Swiftb0y |
bug watch added |
|
https://github.com/mixxxdj/mixxx/issues/7893 |
|
| 2022-10-08 20:09:57 |
Swiftb0y |
lock status |
Unlocked |
Comment-only |
|
