Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support played column in browse mode #7820

Closed
mixxxbot opened this issue Aug 22, 2022 · 4 comments
Closed

Support played column in browse mode #7820

mixxxbot opened this issue Aug 22, 2022 · 4 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: ywwg
Date: 2015-01-19T14:25:26Z
Status: New
Importance: Low
Launchpad Issue: lp1412453


Browse mode uses a separate tablemodel system and doesn't have a played column (nor many of the other standard columns). It should use the standard model or if there is some sort of limitation (because the tracks aren't in the db?), create temporary tables or something so it can work.

@mixxxbot mixxxbot added the bug label Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

mixxxbot commented Aug 22, 2022

Commented by: daschuer
Date: 2015-01-20T08:10:01Z


Original, the browse view was designed to just see the truth from the HD like a file manager would do.

Since many users, including me know sometimes a track by store position in a file system folder, It is more continent to find it in the broth tree, than sort and filter the library by location.

I am also aware that not only a few user select all of there tracks from th browse tree. IMHO this just works by an accident ;-) .. because the user experience is real bad: No library support, Slow and tree navigation feels bad.

https://bugs.launchpad.net/mixxx/+bug/1179318
https://bugs.launchpad.net/mixxx/+bug/1160525
https://bugs.launchpad.net/mixxx/+bug/925628
https://bugs.launchpad.net/mixxx/+bug/1376709
https://bugs.launchpad.net/mixxx/+bug/909959
https://bugs.launchpad.net/mixxx/+bug/797440
https://bugs.launchpad.net/mixxx/+bug/1196311
https://bugs.launchpad.net/mixxx/+bug/1259064
https://bugs.launchpad.net/mixxx/+bug/1166278

On the other hand we it is a common wish to feature a hierarchical structure of tracks of any type.

So I think before rushing into a quick hack solution, we may consider to implement this bug:
Virtual folders below the Library tree node:
This was discussed here:
https://bugs.launchpad.net/mixxx/+bug/1228789

A static solution showing all library folders, seams to be a weekend project and would solve the most of the bugs above at once.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2015-01-20T14:09:17Z


A regular user of mixxx would not use the browse mode, however I was at a party and a DJ friend of mine had brought a USB stick and he wanted to play a set. The only way for us to share the copy of Mixxx was to use browse mode. This type of situation is actually very common for traveling DJs, they only bring a USB stick and plug it into whatever is at the club. Usually that means a CDJ setup, but in this case Mixxx worked fine the same way.

By the way, I showed him how my controller works and the basic functionality of mixxx in about 30 seconds and he was off and running, no problems :). This has been my experience in the past, experienced DJs can pick up mixxx really easily.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2015-01-20T19:09:44Z


Ah yes, this an other common use case, we may adopt in Mixxx. A variation of this is if you play on a birthday party and the host ask to play tracks from his USB stick.
On one hand you do not want to pollute you library with the tracks, on the other hand it could be handy to have a consistent history.

Some of this is covered by https://bugs.launchpad.net/mixxx/+bug/918233

.. 30 seconds ..
Cool. You should have record this session to publish it at Youtube.

@ronso0
Copy link
Member

ronso0 commented Oct 25, 2023

Somewhat a dupe of #7028
Let's continue the discussion there.

@ronso0 ronso0 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants