|
Trying to get same top level view as Twonky
|
|
12-11-2012, 00:30
Post: #1
|
|||
|
|||
|
Trying to get same top level view as Twonky
Hi Simon,
I use Bubble DS on SIII as control point and have two NAS devices each with same database, one serving with Twonky and one with minimserver. (one NAS acts as data backup of the other and eventually both will only use minimserver) The top level view of the Twonky library shows three folders; Music, Photos and Videos. In order to make the user experience the same how may I get minimserver to display the same top level please? I use minimserver exclusively for music played on Linn devices at present. The database also has photos and videos and Twonky serves these to some AV renderers on the lan. Is minimserver OK to serve these AV media? Are there any issues of which I should be aware? Budgie |
|||
|
12-11-2012, 10:06
Post: #2
|
|||
|
|||
RE: Trying to get same top level view as Twonky
(12-11-2012 00:30)Budgie Wrote: Hi Simon, MinimServer only serves music, and I don't have any plans to extend it to serve photos and videos. You'll need to carry on using Twonky for those. |
|||
|
12-11-2012, 13:40
Post: #3
|
|||
|
|||
RE: Trying to get same top level view as Twonky
(12-11-2012 10:06)simoncn Wrote:(12-11-2012 00:30)Budgie Wrote: Hi Simon, Hi Simon, Many thanks. Understood and good decision!. What about my other question though? Even more important now as minimserver is showing some tags that are not music. If I had the top level Music, Photos, Video folders it would avoid the ambiguity. Any thoughts? Also what are implicationms of running Twonky and minimserver on same NAS. I can (I think) ensure Twonky only serves video and photos but need to be able to confine minimserver to music. Budgie |
|||
|
12-11-2012, 14:30
Post: #4
|
|||
|
|||
RE: Trying to get same top level view as Twonky
(12-11-2012 13:40)Budgie Wrote: Hi Simon, Please can you explain what tags MinimServer is showing that are not music. The only case I can think of would be a .mp4 file that contains both video and audio information. Is this what you are seeing? There shouldn't be any problem with running MinimServer and Twonky on the same NAS. To confine MinimServer to music only, you should set the content directory values accordingly in both Twonky and MinimServer. For example, if you have a folder structure like: Multimedia --Multimedia/Photos --Multimedia/Videos --Multimedia/Music you would set the content directories for Twonky to Multimedia/Photos and Multimedia/Videos, and you would set the content directory for MinimServer to Multimedia/Music. |
|||
|
13-11-2012, 00:59
Post: #5
|
|||
|
|||
|
RE: Trying to get same top level view as Twonky
Hi Simon,
Sorry to be so dense. I had forgotten about using minimwatch. I have now set directory correctly and restarted and the odd video tags have gone so that has answered my original question thanks. I thought I would watch the log after the restart because it tooka while and I see I am getting very many errors reported such as conflicting ALBUM tag value and a host of different errors with the BBC downloads. All my BBC audio downloads such as the "Early Music Show" and "Composer of the Week" are now ending up as .mp4 or rather .m4a files as are video downloads. In the past and for BBC archives they were mp3s I am having trouble with these BBC audio files and had put the problems down to poor tagging but now the subject has come up and before I start digging into the tagging, is minimserver OK with .m4a files? Would you have time to look at and comment on the last restart log file please? It is quite large and for reasons I don't understand seems to start half way through the scanning process but it does illustrate a good many issues if you have time! Thanks again for the above help. Budgie |
|||
|
13-11-2012, 07:35
Post: #6
|
|||
|
|||
RE: Trying to get same top level view as Twonky
(13-11-2012 00:59)Budgie Wrote: Hi Simon, The .mp4/.m4a extensions are a bit confusing. .mp4 is the ISO standard for video files, audio files or video+audio files. These files use AAC as the format for audio data. .m4a is an Apple naming convention for audio files only, containing either AAC audio data or ALAC (Apple Lossless) audio data. MinimServer can handle all of these except for .mp4 containing video only. For .mp4 files containing video+audio, MinimServer ignores the video portion. A file containing audio data only in AAC format can be named either .mp4 or .m4a because it fits correctly into both the .mp4 and .m4a categories. Most servers, control points and music players understand this, but there are a few that insist on one of other of these filetype suffixes. In such cases it should be fine to simply rename the file from .m4a to .mp4 or vice versa. Quote:Would you have time to look at and comment on the last restart log file please? It is quite large and for reasons I don't understand seems to start half way through the scanning process but it does illustrate a good many issues if you have time! Yes, I'd be happy to do this. The log starts part way through because MinimWatch has a fixed-size buffer for log data and discards earlier data as later data arrives. You can find the complete file on the QNAP. The default location for the log file is /share/Public/minimserver.log, and you can use the Advanced page of MinimWatch to change or view this location (see the .logfile property). Please zip the complete file and post it as an attachment here. |
|||
|
13-11-2012, 21:33
Post: #7
|
|||
|
|||
RE: Trying to get same top level view as Twonky
(13-11-2012 07:35)simoncn Wrote:As suggested zipped whole log file from NAS.(13-11-2012 00:59)Budgie Wrote: Hi Simon, |
|||
|
13-11-2012, 22:22
Post: #8
|
|||
|
|||
RE: Trying to get same top level view as Twonky
(13-11-2012 21:33)Budgie Wrote: As suggested zipped whole log file from NAS. Thanks for this. All the messages seem to be one of the following: 1) Warning: conflicting ALBUM tag value xxxxxxxx ignored The track is tagged with more than one ALBUM tag. This isn't valid because a track can only belong to one album. 2) Error: no valid MPEG header near offset xxxxxxxx This might be a MinimServer bug. I'll send you a PM about this. 3) Warning: unexpected image item class 0 at offset xxxxxxxx This might be a MinimServer bug. I'll send you a PM about this. 4) Warning: invalid DISCNUMBER tag value 0 ignored If a disc number is specified, it must be 1 or greater. 5) Warning: audio stream corruption at offset xxxxxxxx This file appears to have corrupt audio. Are you able to play it? 6) Error: unexpected end of file at offset 1179407873 This looks like a MinimServer bug. I'll send you a PM about this. 7) java.lang.StringIndexOutOfBoundsException: String index out of range: -3 This is a known bug in 0.63. It will be fixed in the next release. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



