Qute refuses to play my FLACs

Hi Okli

Yep, been there! It must be the weather.

Bought 5 albums during the week, ripped them using same program, same settings etc. 4 worked fine as expected the 5th ….. Unrecognised file format. Re-ripped re-scanned the NAS nothing, album title was there OK but........ Repeated the re-ripping a couple more times during the week. This morning I thought I would rip to WAV and drop them into the same folder as the flac files. Selected the album on the Qute – Great, music started playing – success!

A bit puzzled I thought I would check the file info of the track playing, yes you have probably guessed it was the flac files that had been there all week; no sign of the WAV files just added.......Bizarre.

By the way, didn't I see you were in Gloucester last week was it? One of my very favourite counties.

Regards
Peter

Hi Peter,

Thanks for the hint with the weather - I didn't think of it, but this could be very good reason, because the weather here was awful, too - rainy and foggy . So, we have to be careful not to use qute a lot on bad weather days (hmm, what else shall we do on these days... but this is another topic)

Gloucester is a way too far for me (see Location on the profile), but will consider it for my next visit in UK ;-)

quote:

Originally posted by okli:

Gloucester is a way too far for me (see Location on the profile), but will consider it for my next visit in UK ;-)

Okli....Sorry about that, could have sworn it was one of your posts I was reading, remember thinking lucky ..... Austria and Gloucester. Oh well clearly time to book another appointment with the Doctor.

Allen I don't know why you believe wav is 'industry standard' however the mac burns WAV exactly as just that wav.

Just FYI if you stick a CD in a PC and manually open it you will see files called WAVs, put same CD in a mac and you will see files call .Aiff

You guys aren't using the latest version of EyeConnect, are you?

If the qute cannot see the wavs from mac then either the qute has issues or your UPNP server does.

Lets face it UPNP is shit isn't it?

Its by microsoft so it makes sense

You should be able to play WAV files on Qute no matter how they have been "produced", so you should really check the server or qute. Normally, qute should give you "Unrecognized format" if it receives the stream and can't play it. Have you tried to play the files directly?

OK - we hit the send button at the same time :-)

I see - will try to check this with my mac - I have some albums in wav ripped in windows and they are ok, but never ripped anything on my mac

quote:

Lets face it UPNP is shit isn't it?

Its by microsoft so it makes sense Winker

Back away from your grudge garyi.

UPNP is NOT a Microsoft invention. Just because Apple has shunned it, doesn't entail that Microsoft developed it.

It is simply Apple trying to develop their own thing so they can try to make a few more bucks. Just like EVERYTHING they do. Mini-monopoly, mega-monopoly..... who cares.

Just imported a single track in wav, using itunes on my macbook - plays wonderful on qute from my NAS with Twonky server, however no tags available, but this was an issue with windows rips to wav as well. So, it should be something on your side...

quote:

UPnP works fine (mostly), one thing i do hate though is having to step back and forward through the hierarchy of folders ad not be able to jump two or three steps. For example, you are playing a track but want to get back to the device (i.e. the UPnP server) root directory to then jump to artist or genre. With the Qute you have to go back all the way through to how you got to playing that track in the first place.

Hi Allen

You can just press the 'PC' button from anywhere in the menu to return to the server selection screen, kind of re-initialises (technical term ) the connection but much quicker if that is where you wish to get to.

Not the most eloquent way of doing things I would agree. I do find being able to jump through the selection process using the number keys very useful though.

Regards
Peter

Patrick I thought I read somewhere that microsoft came up with the concept of UPNP but were lazy for a while to develop it, I am corrected if wrong.

MS and Intel are co-fonder of the UPnP organization responsible for the UPnP standards. After that some other companies joined it too, but Apple wanted / wants to go its own way. The "problem" with UPnP is that the specification is hold very abstract and defines the basic architecture for inter-operability, leaving implementation details up to the vendors. For example, the spec defines the use-case of disconnecting a control point at some time, leaving the server and renderer to communicate directly and then re-connecting at later time, taking the control over them again at the current state of the devices, but does not specify how to implement this scenario. However, exactly the so called "implementation details" break the interoperability at the moment, because each vendor comes with its own implementation, compatible only with its own range of products. Some of the vendors make their solutions public, others hold them proprietary. As explained from Naim in "Very technical question..." topic here, Naim comes with its own API, too and is making it public to integration partners, thus allowing some qualified 3rd parties to make compatible products with their devices. AFAIK Linn opened their API completely under some open source licence, thus allowing everyone to develop compatible products. Which way is better, the consumers (we?) will decide. I'm not sure what's new in UPnP 1.1 and I think there is a 2.0 proposal, too, but I think that the direction is to make the specification more implementation specific. Unfortunately, I'm not aware of products supporting these newer versions, I think everything is UPnP v1.0 biased now. I hope I didn't misunderstand something, but feel free to correct me :-)

UPnP is like a very cheap motor ... I won't upset anyone by giving examples ... It works ...most of the time, will get you from A to B but is hardly a comfortable ride. Over time it will stop working from time to time and in the end you will end up selling it before it falls apart.

Naim is a premium brand and deserves better - if, has been pointed out in another strand we are being unfair for moaning about UPnP (polite rephrasing)then we must consider the alternatives ...RipNas, Apple Mac ...

Naim have clearly managed to knock UPnP into some form of shape with the Serve ... It isn,t good enough to say "if you want to use any other UPnP server ...good luck but it's not our fault they are all rubbish"

Tog

Hi AllenB,

exactly this strange behaviour was my problem published in the beggining of the thread - I restarted qute (power down) and after that everything was ok again. Perhaps this will help...

quote:

Thanks Peter, that will be a useful shortcut.

What we could do with on the n-Stream app is some fixed navigation buttons at the bottom of the screen (similar to the n-Serve app, but including 'server' or 'device' as well as album, artist, etc.)

Hello Allen.... I am unable to use any wireless so have not seen either of the n-app's you speak of. However, I understand that they can be used to control all of the functions of the devices not just the streaming which must be extremely useful. Your suggestion would certainly be welcomed I would think, and I would like to see the app,s or a similar program able to run on a computer.

Peter

quote:

Originally posted by AllenB:
No Eyeconnect here, I'd like to avoid transcoding.

EyeConnect only transcodes when the filetype (e.g., Apple Lossless) cannot be played by the destination device.

quote:

Originally posted by garyi:
If the qute cannot see the wavs from mac then either the qute has issues or your UPNP server does.

Lets face it UPNP is shit isn't it?

Its by microsoft so it makes sense

Ermmm no.
uPNP is an international standard ISO/IEC 29341.
Therefore it is open. I find Apples's stance of not fully embracing this open standard given their view on Flash and HTML 5 somewhat inconsistent.... Anyway that is another topic.
Simon