djcity
I'm looking for a software that can go through my whole HD and convert files from WAV or WMA to MP3. Anyone know of a software that can do that? If such a program exists and I am thinking one does, if I run the software, will it change the info of the tracks? What I mean is that I don't want a database issue where VDJ no longer recognizes each track.
I'm thinking that Terry knows what I am looking for and will post one of his famous ""Try This one"".
Oh...Free is a great price and one that I can afford so if it falls in that price range, all the better.
I'm thinking that Terry knows what I am looking for and will post one of his famous ""Try This one"".
Oh...Free is a great price and one that I can afford so if it falls in that price range, all the better.
Posté Mon 16 Nov 09 @ 5:01 pm
Caliente123
This is Switch sound file converter.. " Click on get it now ". Ive been using this for a while now. Its free..
http://www.nch.com.au/switch/plus.html
http://www.nch.com.au/switch/plus.html
Posté Mon 16 Nov 09 @ 5:29 pm
djcity
Will this program go through my whole HD and convert ONLY what is NOT MP3? In other words, I have about 420GB of music on my ext HD. I have way too much music to look through one at a time to find the wav's and wma's.
Will this program go through everything, changing only the files that are NOT MP3 while leaving the MP3's alone?
Will this program go through everything, changing only the files that are NOT MP3 while leaving the MP3's alone?
Posté Mon 16 Nov 09 @ 5:43 pm
Caliente123
I never tried it like that. I used the program for individual songs. For many songs, You have to do it by folder. Try doing it on a folder with mixed bitrates to see how the songs come out. If its already MP3, it would probably just overwritte.
Posté Mon 16 Nov 09 @ 6:43 pm
acw_dj
City,
I recommend you to do a convert from WAV to mp3 (maybe 320 kbps CVR or 192 VBR) and after that do that for WMA but check it's rate (128, 160 or 192) and convert them to mp3 equivalent. If you don't so it that way, you may convert 128 to 192 without any better sound and could confuse you if you get in another time a really 192 quality file.
I use "magic converter" or "Real Player" to do this kind of task ;-)
I recommend you to do a convert from WAV to mp3 (maybe 320 kbps CVR or 192 VBR) and after that do that for WMA but check it's rate (128, 160 or 192) and convert them to mp3 equivalent. If you don't so it that way, you may convert 128 to 192 without any better sound and could confuse you if you get in another time a really 192 quality file.
I use "magic converter" or "Real Player" to do this kind of task ;-)
Posté Mon 16 Nov 09 @ 10:02 pm
djcity
Cool...
I also remember seeing a software that finds duplicates on your HD. It said that it finds the duplicates even if the filenames are not the same then gives you the option to listen to them before you delete them.
I don't remember where I saw this software at sooooo....
Anybody know where I can find a free software to get the job done?
Terry.......Where are you with all those links you know about?
I also remember seeing a software that finds duplicates on your HD. It said that it finds the duplicates even if the filenames are not the same then gives you the option to listen to them before you delete them.
I don't remember where I saw this software at sooooo....
Anybody know where I can find a free software to get the job done?
Terry.......Where are you with all those links you know about?
Posté Tue 17 Nov 09 @ 6:45 am
GadgetMan
City,
MediaMonkey has conversion capabilities plus you can build queries that sit in the tree view on the left of files to convert based on extension for example.
That way you can batch a few, make sure they convert correctly and move on. Chances are you are going to have to do this in several stages so it's best to use something that can help keep a track of where you last got to..
MediaMonkey has MMScripting too, I haven't looked but I am sure you could write a script that scanned for WMA's and then converted them. And ensuring what track info existing prior to conversion was recaptured in the new MP3's tag.
Also, make sure you have enough disk space... Don't simply replace the WAV or WMA with the newly craeted MP3. What happens if the conversion process didn't go smoothly? You'll need to run it again.
If budget allows, have a new external HDD where the newly converted files will end up, thus leaving your original files intact.
There is one other issue that you need to consider... How are you going to proof all these files your converting? I mentioned the odd failure, but what would happen if you took your newly converted fiels to a gig only to find they all sound bad.
Yes, it would be great to "mass convert" but you will need to check on the quality of your conversions. I would suggest doing this at a slower pace and in a way where you can at least play the tracks and sample the start, middle and end of each track before commiting to use it.
Again, I have found MediaMonkey very good for quickly scanning new tracks/rips for quality.
Downsides:
1. You are gonna have to re-import all your new files in to VDJ
2. All your history files will point to the old files and will be unuseable
3. Virtual folders will have to be re-built and the old tracks removed
4. VDJ will need to re-scan all these new tracks
So as I said, if you can find a way to batch these in some way you will get a better result in the long term - there is no quick solution.
Cheers,
Roy
MediaMonkey has conversion capabilities plus you can build queries that sit in the tree view on the left of files to convert based on extension for example.
That way you can batch a few, make sure they convert correctly and move on. Chances are you are going to have to do this in several stages so it's best to use something that can help keep a track of where you last got to..
MediaMonkey has MMScripting too, I haven't looked but I am sure you could write a script that scanned for WMA's and then converted them. And ensuring what track info existing prior to conversion was recaptured in the new MP3's tag.
Also, make sure you have enough disk space... Don't simply replace the WAV or WMA with the newly craeted MP3. What happens if the conversion process didn't go smoothly? You'll need to run it again.
If budget allows, have a new external HDD where the newly converted files will end up, thus leaving your original files intact.
There is one other issue that you need to consider... How are you going to proof all these files your converting? I mentioned the odd failure, but what would happen if you took your newly converted fiels to a gig only to find they all sound bad.
Yes, it would be great to "mass convert" but you will need to check on the quality of your conversions. I would suggest doing this at a slower pace and in a way where you can at least play the tracks and sample the start, middle and end of each track before commiting to use it.
Again, I have found MediaMonkey very good for quickly scanning new tracks/rips for quality.
Downsides:
1. You are gonna have to re-import all your new files in to VDJ
2. All your history files will point to the old files and will be unuseable
3. Virtual folders will have to be re-built and the old tracks removed
4. VDJ will need to re-scan all these new tracks
So as I said, if you can find a way to batch these in some way you will get a better result in the long term - there is no quick solution.
Cheers,
Roy
Posté Tue 17 Nov 09 @ 7:17 am
acw_dj
Yes I forgot this Media Monkey software... great tool. Thanks for the comments, indeed you need to consider all possibilities before you could finally get all done.
City, you have to much work with this on your hands ;-) Good Luck!
Posté Tue 17 Nov 09 @ 11:15 am
JoeyKJ
GadgetMan wrote :
City,
MediaMonkey has conversion capabilities plus you can build queries that sit in the tree view on the left of files to convert based on extension for example.
That way you can batch a few, make sure they convert correctly and move on. Chances are you are going to have to do this in several stages so it's best to use something that can help keep a track of where you last got to..
MediaMonkey has MMScripting too, I haven't looked but I am sure you could write a script that scanned for WMA's and then converted them. And ensuring what track info existing prior to conversion was recaptured in the new MP3's tag.
Also, make sure you have enough disk space... Don't simply replace the WAV or WMA with the newly craeted MP3. What happens if the conversion process didn't go smoothly? You'll need to run it again.
If budget allows, have a new external HDD where the newly converted files will end up, thus leaving your original files intact.
There is one other issue that you need to consider... How are you going to proof all these files your converting? I mentioned the odd failure, but what would happen if you took your newly converted fiels to a gig only to find they all sound bad.
Yes, it would be great to "mass convert" but you will need to check on the quality of your conversions. I would suggest doing this at a slower pace and in a way where you can at least play the tracks and sample the start, middle and end of each track before commiting to use it.
Again, I have found MediaMonkey very good for quickly scanning new tracks/rips for quality.
Downsides:
1. You are gonna have to re-import all your new files in to VDJ
2. All your history files will point to the old files and will be unuseable
3. Virtual folders will have to be re-built and the old tracks removed
4. VDJ will need to re-scan all these new tracks
So as I said, if you can find a way to batch these in some way you will get a better result in the long term - there is no quick solution.
Cheers,
Roy
MediaMonkey has conversion capabilities plus you can build queries that sit in the tree view on the left of files to convert based on extension for example.
That way you can batch a few, make sure they convert correctly and move on. Chances are you are going to have to do this in several stages so it's best to use something that can help keep a track of where you last got to..
MediaMonkey has MMScripting too, I haven't looked but I am sure you could write a script that scanned for WMA's and then converted them. And ensuring what track info existing prior to conversion was recaptured in the new MP3's tag.
Also, make sure you have enough disk space... Don't simply replace the WAV or WMA with the newly craeted MP3. What happens if the conversion process didn't go smoothly? You'll need to run it again.
If budget allows, have a new external HDD where the newly converted files will end up, thus leaving your original files intact.
There is one other issue that you need to consider... How are you going to proof all these files your converting? I mentioned the odd failure, but what would happen if you took your newly converted fiels to a gig only to find they all sound bad.
Yes, it would be great to "mass convert" but you will need to check on the quality of your conversions. I would suggest doing this at a slower pace and in a way where you can at least play the tracks and sample the start, middle and end of each track before commiting to use it.
Again, I have found MediaMonkey very good for quickly scanning new tracks/rips for quality.
Downsides:
1. You are gonna have to re-import all your new files in to VDJ
2. All your history files will point to the old files and will be unuseable
3. Virtual folders will have to be re-built and the old tracks removed
4. VDJ will need to re-scan all these new tracks
So as I said, if you can find a way to batch these in some way you will get a better result in the long term - there is no quick solution.
Cheers,
Roy
Hi Roy
Downsides:
1. You are gonna have to re-import all your new files in to VDJ
2. All your history files will point to the old files and will be unuseable
3. Virtual folders will have to be re-built and the old tracks removed
4. VDJ will need to re-scan all these new tracks
You make an excellent point to the downside of any changes in your songs file folder no matter how small the change including a period or one space you'll wind up paying a consequence in VDJ.
There is no function with the program to address this very Basic ability that you can find in programs that cost nothing for free, but not available in VDJ, This Is The Weakest Link In Virtual DJ.
But even this problem can be solved very easily by providing an export import option in the XML database.
You just need to make ONE Change to ONE Field (song file name) that affects countless Links all over the program as you mention a few but there are others.
The way it is now you can throw it all away with just one change, this seems to me out of touch with the realities of today’s technology.
The Export Import Option in the XML Database idea would keep everything that you spent hours, days, weeks, months, or even years organizing in place.
Information is the root to a well organized system, why has this very important part been neglected?
I use VDJ every week in and week out and I don't want to sound like i'm trashing but this headache is fast becoming a migraine.
Thank You
Joey...
Posté Tue 17 Nov 09 @ 11:46 am
GadgetMan
JoeyKJ wrote :
You make an excellent point to the downside of any changes in your songs file folder no matter how small the change including a period or one space you'll wind up paying a consequence in VDJ.
There is no function with the program to address this very Basic ability that you can find in programs that cost nothing for free, but not available in VDJ, This Is The Weakest Link In Virtual DJ.
But even this problem can be solved very easily by providing an export import option in the XML database.
You just need to make ONE Change to ONE Field (song file name) that affects countless Links all over the program as you mention a few but there are others.
The way it is now you can throw it all away with just one change, this seems to me out of touch with the realities of today’s technology.
The Export Import Option in the XML Database idea would keep everything that you spent hours, days, weeks, months, or even years organizing in place.
Information is the root to a well organized system, why has this very important part been neglected?
I use VDJ every week in and week out and I don't want to sound like i'm trashing but this headache is fast becoming a migraine.
Thank You
Joey...
There is no function with the program to address this very Basic ability that you can find in programs that cost nothing for free, but not available in VDJ, This Is The Weakest Link In Virtual DJ.
But even this problem can be solved very easily by providing an export import option in the XML database.
You just need to make ONE Change to ONE Field (song file name) that affects countless Links all over the program as you mention a few but there are others.
The way it is now you can throw it all away with just one change, this seems to me out of touch with the realities of today’s technology.
The Export Import Option in the XML Database idea would keep everything that you spent hours, days, weeks, months, or even years organizing in place.
Information is the root to a well organized system, why has this very important part been neglected?
I use VDJ every week in and week out and I don't want to sound like i'm trashing but this headache is fast becoming a migraine.
Thank You
Joey...
Joey,
Here's where I disagree. VDJ is a player, not a music manager. There are countless programs out there to do this and everyone has their own favourite. Whatever Atomix did in this space would bring criticism regardless of how good the feature was. Plus it would only add unnecessary resource to the application.
I imagine you only spend a fraction of the time tagging your files in comparison to the time you spend spinning (if not - you have a problem!). All this would do is add to the footprint of the application and open it up potentially to more crashes which would have nothing to do with the act of DJing itself.
And WRT an import/export cabaility there again you have more potential for failures. Yes, you and I may understand XML, but that's not the case for everyone. And if one of those users fiddled with an XML field, that again would cause corruption and increase the possibility of crashing the application.
The ONLY - and I mean ONLY way to safely do this would be for Atomix to release an ActiveX control/function library that application developers could call from varying programming languages or from advance media tools such as MediaMonkey with its MMScript.
This way the only code that reads/writes the XML is Atomix code, but can be used by countless others.
In fact I'm going to request this now in the New Features forum!!
TTFN,
Roy
Posté Tue 17 Nov 09 @ 2:27 pm
JoeyKJ
Quote;
Here's where I disagree.
Answer;
Ok that's fair
Quote;
VDJ is a player, not a music manager.
Answer;
Then why is there a database?
To manage what it has in its Database (Not iTunes, ect.)
Quote;
There are countless programs out there to do this and everyone has their own favourite. Whatever Atomix did in this space would bring criticism regardless of how good the feature was. Plus it would only add unnecessary resource to the application.
Answer;
It's not criticism, it's an observations based on experience I own a copy and I work with it and I have found this area of the program that needs improvements, why do you call it (Criticism), it's truth, isn't this forum setup for the exchange of ideas and of opinion you sound like you're taking this to a different, personal level, you have no way to know the time I spend with this issue I talk about.
Yes your right for MP3 (Not Video Vob, Mpg, wav, wmv, wma, ect.)
You would need to suffer your way into what VDJ has to manually key in all information one at a time, that's six fields per file.
Now if you have a 30 file video DVD after you finish ripping and naming those files, then to input all this information again into VDJ Takes allot of time and work.
Example;
30 files X 6 fields = 180 entries just to get the file info. into VDJ from this one DVD and that's not including all the work that was already done naming the files after ripping.
If there was a global edit feature then the above task would take only 36 entries instead of 180.
There is no MP3Tag, iTunes or other third party software for videos files to help import information into VDJ, If there was we wouldn’t be having this conversation.
Just imagine if you had to do this with all your MP3 files and albums?
Quote;
I imagine you only spend a fraction of the time tagging your files in comparison to the time you spend spinning (if not - you have a problem!).
Answer;
You imagine incorrectly.
I do spin frequently and yes I am busy and I do have a life to live too.
I rather spend more time spinning then tagging that's for sure, but the problem part of your statement is partially correct and it's not with what you are inferring, but the products shortcomings in this area.
I do spend allot of time tagging and using the tools that I purchase to get my media information in VDJ correctly, how else can I organize without it.
That’s the reason why I post because I do put in the time to find out about this problem area, and I also read other post with similar concerns.
Quote;
All this would do is add to the footprint of the application and open it up potentially to more crashes which would have nothing to do with the act of DJing itself.
Answer;
How do you know that are you a programmer with VDJ?
Then why do other software companies have this ability?
I understand this maybe a big investment of time and money to add this feature within the program.
That is why I suggested the export import method in the MXL database to at least give us a tool to deal with this issue.
Don't you read the post, allot of us see a need to open the database (export and import feature) making global changes in Access or other database programs and then after edits reimport back into MXL.
I do this now with other software i'm using it's mush faster for me outside the program and I'm 100%, changes take minutes instead of hours.
Quote;
WRT an import/export cabaility there again you have more potential for failures. Yes, you and I may understand XML, but that's not the case for everyone. And if one of those users fiddled with an XML field, that again would cause corruption and increase the possibility of crashing the application.
Answer;
Yes you are correct, and so is scripting a potential problem, but you make it available because there's a need, Not because of a potential problem.
A good example is the registry tool that VDJ makes available for download, to me it's a potential Atom Bomb, But there's a need for it.
If you tell the user you need to backup the Registry or Database first, and you do it at your own risk, then you've met your obligations just like everything else in life.
Quote;
The ONLY - and I mean ONLY way to safely do this would be for Atomix to release an ActiveX control/function library that application developers could call from varying programming languages or from advance media tools such as MediaMonkey with its MMScript This way the only code that reads/writes the XML is Atomix code, but can be used by countless others.
Answer;
Why make it complicated?
Quote;
In fact I'm going to request this now in the New Features forum!!
Good for You...Roy
Thanks
Joey....
Here's where I disagree.
Answer;
Ok that's fair
Quote;
VDJ is a player, not a music manager.
Answer;
Then why is there a database?
To manage what it has in its Database (Not iTunes, ect.)
Quote;
There are countless programs out there to do this and everyone has their own favourite. Whatever Atomix did in this space would bring criticism regardless of how good the feature was. Plus it would only add unnecessary resource to the application.
Answer;
It's not criticism, it's an observations based on experience I own a copy and I work with it and I have found this area of the program that needs improvements, why do you call it (Criticism), it's truth, isn't this forum setup for the exchange of ideas and of opinion you sound like you're taking this to a different, personal level, you have no way to know the time I spend with this issue I talk about.
Yes your right for MP3 (Not Video Vob, Mpg, wav, wmv, wma, ect.)
You would need to suffer your way into what VDJ has to manually key in all information one at a time, that's six fields per file.
Now if you have a 30 file video DVD after you finish ripping and naming those files, then to input all this information again into VDJ Takes allot of time and work.
Example;
30 files X 6 fields = 180 entries just to get the file info. into VDJ from this one DVD and that's not including all the work that was already done naming the files after ripping.
If there was a global edit feature then the above task would take only 36 entries instead of 180.
There is no MP3Tag, iTunes or other third party software for videos files to help import information into VDJ, If there was we wouldn’t be having this conversation.
Just imagine if you had to do this with all your MP3 files and albums?
Quote;
I imagine you only spend a fraction of the time tagging your files in comparison to the time you spend spinning (if not - you have a problem!).
Answer;
You imagine incorrectly.
I do spin frequently and yes I am busy and I do have a life to live too.
I rather spend more time spinning then tagging that's for sure, but the problem part of your statement is partially correct and it's not with what you are inferring, but the products shortcomings in this area.
I do spend allot of time tagging and using the tools that I purchase to get my media information in VDJ correctly, how else can I organize without it.
That’s the reason why I post because I do put in the time to find out about this problem area, and I also read other post with similar concerns.
Quote;
All this would do is add to the footprint of the application and open it up potentially to more crashes which would have nothing to do with the act of DJing itself.
Answer;
How do you know that are you a programmer with VDJ?
Then why do other software companies have this ability?
I understand this maybe a big investment of time and money to add this feature within the program.
That is why I suggested the export import method in the MXL database to at least give us a tool to deal with this issue.
Don't you read the post, allot of us see a need to open the database (export and import feature) making global changes in Access or other database programs and then after edits reimport back into MXL.
I do this now with other software i'm using it's mush faster for me outside the program and I'm 100%, changes take minutes instead of hours.
Quote;
WRT an import/export cabaility there again you have more potential for failures. Yes, you and I may understand XML, but that's not the case for everyone. And if one of those users fiddled with an XML field, that again would cause corruption and increase the possibility of crashing the application.
Answer;
Yes you are correct, and so is scripting a potential problem, but you make it available because there's a need, Not because of a potential problem.
A good example is the registry tool that VDJ makes available for download, to me it's a potential Atom Bomb, But there's a need for it.
If you tell the user you need to backup the Registry or Database first, and you do it at your own risk, then you've met your obligations just like everything else in life.
Quote;
The ONLY - and I mean ONLY way to safely do this would be for Atomix to release an ActiveX control/function library that application developers could call from varying programming languages or from advance media tools such as MediaMonkey with its MMScript This way the only code that reads/writes the XML is Atomix code, but can be used by countless others.
Answer;
Why make it complicated?
Quote;
In fact I'm going to request this now in the New Features forum!!
Good for You...Roy
Thanks
Joey....
Posté Tue 17 Nov 09 @ 10:02 pm
mini reaper
Posté Wed 18 Nov 09 @ 12:09 am
dizzyrocks2001
Why not use iTunes? It will convert to mp3. All you would have to do is put all your tracks into iTunes, sort by filetype and convert all the non-mp3s.
Posté Wed 18 Nov 09 @ 12:43 am
GadgetMan
Joey,
You make some good points - this is a good debate. So to respond...
Quote;
Then why is there a database?
To manage what it has in its Database (Not iTunes, ect.)
Answer;
Having a database does not make the application a media manager (ok, yes there is a limited interface). There is lots of software out there that uses a database in one form or another. Does they give you direct access to its raw data? Not necessarily. The database is needed to make searching for files easier, for storing information about each file when it is scanned, for saving cue points etc. All to make our lives as DJ's that much easier.
Quote;
It's not criticism, it's an observations based on experience I own a copy and I work with it and I have found this area of the program that needs improvements, why do you call it (Criticism), it's truth, isn't this forum setup for the exchange of ideas and of opinion you sound like you're taking this to a different, personal level, you have no way to know the time I spend with this issue I talk about.
Answer;
What I was saying is that any attempt to improve the media management in VDJ would bring criticism. There is no guarantee that if changes were made it would be the changes you need in a way you would use them. And if there were, they may not be the changes I need - To this end, there is no right way to implement media management in VDJ.
Quote;
Yes your right for MP3 (Not Video Vob, Mpg, wav, wmv, wma, ect.)
...
There is no MP3Tag, iTunes or other third party software for videos files to help import information into VDJ, If there was we wouldn’t be having this conversation.
Answer;
I cannot disagree with you there. However I do feel there is a better way (read on ;-) )
Quote;
You imagine incorrectly.
...
That’s the reason why I post because I do put in the time to find out about this problem area, and I also read other post with similar concerns.
Answer;
I can see where you are coming from now. OK, to date my library consists of 99% MP3 and 1% video. Of that 1% I have 90% MP4 and 10% VOB. So I have only had to enter a few details manually.
I still think there is another way...
Quote;
How do you know that are you a programmer with VDJ?
Answer;
No but I am a programmer. Extra code = extra footprint. The amount it grows depends on how extensive the changes are. Media management may seem fairly trivial, but when you lift the hood, there's probabaly more code than you would realise. The smaller the app, the more memory for track\video manipulation etc...
Quote;
Yes you are correct, and so is scripting a potential problem, but you make it available because there's a need, Not because of a potential problem.
Answer;
Yes scripting can cause issues, but as you say, with the right health warnings first. However scripting from a defined API provided by Atomix as opposed to hacking the database is far safer...
Quote;
A good example is the registry tool that VDJ makes available for download, to me it's a potential Atom Bomb, But there's a need for it.
Answer;
Yes, but the registry tool has been written by the people who know what needs to be done. Yes there are risks, but I would much rather run Atomix tools than JoeBloggsDJ tools (no offence to JoeBloggsDJ if he exists)
Quote;
Why make it complicated?
Answer;
I don't want to make it complicated - I want to make it safe. A database API would work in multiple ways - and here's my solution for you:
Yes there is a shortcoming in VDJ for tagging video, and yes the VDJ interface does not make this easy. If the API was exposed, then not only could experienced programmers/scripters use it, but so could Atomix. The same way there is a video ripper and a registry tool, they could easily provide a video tagging tool.
Yes, a standalone tool that makes the scanning and tagging of video much more straightforward without comprimising VDJ. No need for a 6.0.4 or even a 6.1. Just a standalone tool that would be able to read/write the database with a full screen, data oriented interface.
But not only that, this tool could actually come from the community and be adopted by Atomix, but this could only happen if we had the API.
Quote;
Good for You...Roy
Answer;
Thanks I did ;-)
Cheers,
Roy
You make some good points - this is a good debate. So to respond...
Quote;
Then why is there a database?
To manage what it has in its Database (Not iTunes, ect.)
Answer;
Having a database does not make the application a media manager (ok, yes there is a limited interface). There is lots of software out there that uses a database in one form or another. Does they give you direct access to its raw data? Not necessarily. The database is needed to make searching for files easier, for storing information about each file when it is scanned, for saving cue points etc. All to make our lives as DJ's that much easier.
Quote;
It's not criticism, it's an observations based on experience I own a copy and I work with it and I have found this area of the program that needs improvements, why do you call it (Criticism), it's truth, isn't this forum setup for the exchange of ideas and of opinion you sound like you're taking this to a different, personal level, you have no way to know the time I spend with this issue I talk about.
Answer;
What I was saying is that any attempt to improve the media management in VDJ would bring criticism. There is no guarantee that if changes were made it would be the changes you need in a way you would use them. And if there were, they may not be the changes I need - To this end, there is no right way to implement media management in VDJ.
Quote;
Yes your right for MP3 (Not Video Vob, Mpg, wav, wmv, wma, ect.)
...
There is no MP3Tag, iTunes or other third party software for videos files to help import information into VDJ, If there was we wouldn’t be having this conversation.
Answer;
I cannot disagree with you there. However I do feel there is a better way (read on ;-) )
Quote;
You imagine incorrectly.
...
That’s the reason why I post because I do put in the time to find out about this problem area, and I also read other post with similar concerns.
Answer;
I can see where you are coming from now. OK, to date my library consists of 99% MP3 and 1% video. Of that 1% I have 90% MP4 and 10% VOB. So I have only had to enter a few details manually.
I still think there is another way...
Quote;
How do you know that are you a programmer with VDJ?
Answer;
No but I am a programmer. Extra code = extra footprint. The amount it grows depends on how extensive the changes are. Media management may seem fairly trivial, but when you lift the hood, there's probabaly more code than you would realise. The smaller the app, the more memory for track\video manipulation etc...
Quote;
Yes you are correct, and so is scripting a potential problem, but you make it available because there's a need, Not because of a potential problem.
Answer;
Yes scripting can cause issues, but as you say, with the right health warnings first. However scripting from a defined API provided by Atomix as opposed to hacking the database is far safer...
Quote;
A good example is the registry tool that VDJ makes available for download, to me it's a potential Atom Bomb, But there's a need for it.
Answer;
Yes, but the registry tool has been written by the people who know what needs to be done. Yes there are risks, but I would much rather run Atomix tools than JoeBloggsDJ tools (no offence to JoeBloggsDJ if he exists)
Quote;
Why make it complicated?
Answer;
I don't want to make it complicated - I want to make it safe. A database API would work in multiple ways - and here's my solution for you:
Yes there is a shortcoming in VDJ for tagging video, and yes the VDJ interface does not make this easy. If the API was exposed, then not only could experienced programmers/scripters use it, but so could Atomix. The same way there is a video ripper and a registry tool, they could easily provide a video tagging tool.
Yes, a standalone tool that makes the scanning and tagging of video much more straightforward without comprimising VDJ. No need for a 6.0.4 or even a 6.1. Just a standalone tool that would be able to read/write the database with a full screen, data oriented interface.
But not only that, this tool could actually come from the community and be adopted by Atomix, but this could only happen if we had the API.
Quote;
Good for You...Roy
Answer;
Thanks I did ;-)
Cheers,
Roy
Posté Wed 18 Nov 09 @ 3:58 am
djcity
Gadget and Joey...
Not to be rude but do you think you could start your own thread? I was looking for suggestions on an issue. Not looking for a debate about the software capabilities.
Thank you all for the help.
I'm still surprised that TearEmUp has not chimed in on this yet.
I'm still open to suggestions.
Not to be rude but do you think you could start your own thread? I was looking for suggestions on an issue. Not looking for a debate about the software capabilities.
Thank you all for the help.
I'm still surprised that TearEmUp has not chimed in on this yet.
I'm still open to suggestions.
Posté Wed 18 Nov 09 @ 12:09 pm
GadgetMan
djcity wrote :
Gadget and Joey...
Not to be rude but do you think you could start your own thread? I was looking for suggestions on an issue. Not looking for a debate about the software capabilities.
Thank you all for the help.
I'm still surprised that TearEmUp has not chimed in on this yet.
I'm still open to suggestions.
Not to be rude but do you think you could start your own thread? I was looking for suggestions on an issue. Not looking for a debate about the software capabilities.
Thank you all for the help.
I'm still surprised that TearEmUp has not chimed in on this yet.
I'm still open to suggestions.
Sorry dude...
Roy
Posté Wed 18 Nov 09 @ 12:33 pm