Hi Ryan,
Thanks for the update.
The revised description gives the project/idea better organizing tools and
the user experience relating to it. Will write my proposal on those lines.
The bug report on metadata updating caught my curiosity though. Independant
of the project, would like to continue the mail thread on the bug . Trust
it is fine.
Cheers
Uma Priyadarsi
On Wed, Apr 24, 2013 at 9:23 PM, RJ Ryan <[email protected]> wrote:
> Hi Uma,
>
> This email thread and others made us realize that our project description
> for the Advanced Tagging project was overly confusing. We really did not
> intend for the focus to be on file metadata -- Mixxx can already read and
> write common metadata formats but writing is currently disabled due to a
> bad file corruption / concurrency issue.
>
>
> http://www.mixxx.org/wiki/doku.php/gsoc2013ideas#advanced_track_management_organization_tools
>
> Please check out our revised description of the project on the ideas page.
> I hope it makes things more clear. The focus of the project is the
> user-interface for managing and organizing tracks in the Mixxx library.
>
> Best regards,
> RJ Ryan
>
>
> On Mon, Apr 22, 2013 at 3:00 PM, RJ Ryan <[email protected]> wrote:
>
>> HI Uma,
>>
>> Just to answer your question directly about ID3v1, your proposal and
>> project should have an answer that is not specific to the particular
>> metadata format (e.g. when possible it should work with any metadata format
>> that taglib works with and every format that Mixxx supports -- MP3, Ogg
>> Vorbis, FLAC, M4A, WAV/AIFF/RIFF, etc. In some cases it just wont be
>> possible such as with WAV/AIFF/RIFF. You should research each one to make
>> sure you know what is possible).
>>
>> I agree with Daniel that DJ-specific metadata can't easily be stored to
>> existing metadata container formats because there is no existing standard.
>> We have considered defining a standard in the past but we don't believe we
>> could get all the stakeholders (VDJ, Traktor, Serato, etc.) on board.
>>
>> Hope that helps,
>> RJ
>>
>>
>> On Mon, Apr 22, 2013 at 2:53 PM, Daniel Schürmann <[email protected]>wrote:
>>
>>> Hi Uma,
>>>
>>> Yes, you are right!
>>>
>>> In addition you could also think in a direction what will be store-able
>>> in Mixxx database about the tracks.
>>>
>>> I am personal not a big fan of writing more meta data then the basic
>>> tags into the users media files.
>>> It is fine for syncing them between media players and of corse Mixxx
>>> schould be able to fix errors and detect changes.
>>> DJ specific meta data should be stored in the Mixxx database, so you
>>> don't have to worry about exotic tag formats.
>>> in the first place.
>>>
>>> I am happy about any help with the tag writing bug :-)
>>>
>>> Kind regards,
>>>
>>> Daniel
>>>
>>>
>>>
>>> Am 22.04.2013 18:54, schrieb Uma Priyadarsi:
>>>
>>> Hi,
>>>
>>> Thank you, Daniel.
>>>
>>> I have seen the updated page on Advanced Tagging and appreciate the
>>> focus on intuitive GUI and user experience. May be we can include single
>>> and group tagging. Excited to work on this.
>>>
>>>
>>> I have started exploring the components within ID3 V1 tags and extended
>>> tags and am actively considering the tags that a DJ would like to see/edit
>>> from the user interface. Do I need to look into ID3v2 tags as well? Would
>>> also need your guidance on implementation for other formats - .wav, .flac,
>>> .ogg .
>>>
>>> And thanks again for directing me to the bug report. Had a quick run
>>> through it. It gives insight into the complexity of the issue. From thr bug
>>> description, I've understood that mixxx is facing problems with the UI mode
>>> of editing tags as it is resulting in unspecified reference portions of the
>>> mapped region of the file. Trust I got the crux of the bug right. Believe
>>> the bug resolution should be part of the project.
>>>
>>> I have some submissions in college, will revert to advance tagging and
>>> the bug report shared, shortly.
>>>
>>> Cheers
>>> Uma Priyadarsi
>>>
>>>
>>> On Sun, Apr 21, 2013 at 6:14 PM, Daniel Schürmann <[email protected]>wrote:
>>>
>>>> Hi Uma,
>>>>
>>>> Sorry for the late response.
>>>>
>>>> You investigation results are correct.
>>>> You find more details in the bug report:
>>>> https://bugs.launchpad.net/mixxx/+bug/728197
>>>> I hope I can finish a basic version just before GSoC so your would
>>>> continue it.
>>>>
>>>> Have you read the updated page:
>>>> http://www.mixxx.org/wiki/doku.php/gsoc2013ideas#advanced_tagging
>>>>
>>>> For me, the main focus of this project and the place for your ideas the
>>>> user experience while editing meta date.
>>>> So which data should Mixxx collect for each track and how the user can
>>>> edit it.
>>>> This is much more than Artist, Album and Bmp.
>>>>
>>>> Kind regards,
>>>>
>>>> Daniel
>>>>
>>>>
>>>>
>>>>
>>>> Am 20.04.2013 11:10, schrieb Uma Priyadarsi:
>>>>
>>>> Hi,
>>>>
>>>> I did a bit more exploring on tagging and think I am able to figure out
>>>> the objectives of this project.
>>>>
>>>> When I changed metadata of an mp3 file in mixxx, it is not updating the
>>>> metadata in the mp3 file, but only writing to / .mixxx/mixxxdb.sqlite. I
>>>> tried the same with vlc media player, there it is updating the original
>>>> mp3(ID3 tags). Trust I got the main objective right. Am also thinking of
>>>> GUI to include an option for the DJ to choose whether to update the
>>>> original track or not.
>>>>
>>>> I had a look at the code and think src/library/DAO/trackdao.cpp -
>>>> TrackDAO::updateTrack() - is where it is updating the sqlite. Trying to
>>>> figure out how to write tags/metadata back to the track using TagLib.
>>>>
>>>> Trust I am on the right lines. Appreciate your advice.
>>>>
>>>> I would write my proposal on the above lines.
>>>>
>>>> Cheers
>>>> Uma Priyadarsi
>>>>
>>>>
>>>> On Sun, Apr 14, 2013 at 12:17 AM, Uma Priyadarsi <
>>>> [email protected]> wrote:
>>>>
>>>>> Hello
>>>>>
>>>>> I would like to participate in gsoc 13 for mixxx. Allow me to give a
>>>>> brief introduction about myself and the progress I've made so far-> I
>>>>> started out during late feb - early march. Initially I had trouble
>>>>> compiling mixxx on my system in windows, then as suggested, I compiled it
>>>>> linux(ubuntu) which was much easier. After that I was trying to work on
>>>>> the
>>>>> following bug: bug#1000784<
>>>>> https://bugs.launchpad.net/mixxx/+bug/1000784> , to get accomusted to
>>>>> the code. I was kind of late in replying back after that. Anyway, by the
>>>>> end of march, after I felt I had done what I could about the bug, and had
>>>>> experimented and played with the code, I wrote back. I felt there was no
>>>>> bug at all, and I explianed why I felt so. That reply of mine is there in
>>>>> mailing list vol 83, issue 1. However, nobody replied to that. I would
>>>>> like
>>>>> to get a feedback, if what I had done was not enough or what I reported
>>>>> was
>>>>> inaccurate or whatever. After that I again got busy with college related
>>>>> work->exams etc. And by the end of this month I would again get busy with
>>>>> my practicals and end sem exams. But however my vaccation period starts
>>>>> before gsoc work period starts. So, that would not be problem then.
>>>>>
>>>>> Right now, I'm going through the various ideas mentioned in gsoc13
>>>>> ideas page in the mixxx website. And I quite could not understand what
>>>>> exactly was expected of, in this poject/idea. As such, mixxx already does
>>>>> show, genre, album, artist, year etc. and we can also manually edit the
>>>>> title, artist,album etc. It also shows number of times played. I could not
>>>>> understand what else for, we might require want to write metadata back to
>>>>> the track. I tried searching in the net, as well as downloaded other music
>>>>> players, and couldn't quite understand what and why mixx would have to
>>>>> write metadata back to tracks. Could you please throw some light into
>>>>> it,and tell me what is expected of, of this project/idea.
>>>>>
>>>>> Awaiting your reply.
>>>>>
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> Priyadarsi
>>>>> 2nd Year undergraduate
>>>>> Department of Production Engineering
>>>>> National Institute of Technology, Trichy
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
