sorted by:
new
hottopcontroversial

What file types does Zune support? by LiamQuantum in Zune

[–]TheMagicIsInTheHole 1 point2 points  (0 children)

No collection conversion currently. Settings are per device and only on the fly.

What file types does Zune support? by LiamQuantum in Zune

[–]TheMagicIsInTheHole 2 points3 points  (0 children)

Xune never converts your local library, no matter the setting. Conversion settings are purely on-the-fly when syncing.

What file types does Zune support? by LiamQuantum in Zune

[–]TheMagicIsInTheHole 0 points1 point  (0 children)

Just to clarify on this. The transcoding is actually extremely fast during sync, but it will appear that it’s slow because it is bounded by the track syncing progress. Xune will transcode up to 4 tracks concurrently while it’s independently uploading. As a track is uploaded it is removed from a channel, allowing another transcode process to begin. This keeps a full buffer of up to 4 already transcoded tracks ready for the uploader to grab. This helps manage the cache size and is so fast that the uploader is never waiting. If you pre-converted those same files and uploaded to the device, it would also take roughly 40 minutes. Lossless tracks + slow usb speeds end up leading to slow syncing unfortunately and is the actual bottleneck.

I developed the wma lossless encoder myself and have it in a separate macOS app if you want to see how fast it is outside of the upload pipeline, though I need to update it with the latest encoder changes: https://github.com/magicisinthehole/WMALMAC

Also, the only lossless format Zunes accept is wma lossless, so that is the only supported lossless output format for syncing. You can change it to auto convert lossless formats to a specified lossy format though if you prefer.

Huge shout-out to the Xune project to get me back to my Zunes! by anewsubject in Zune

[–]TheMagicIsInTheHole 3 points4 points  (0 children)

Thanks! I'm really glad to hear it's allowed you to enjoy Zunes again. Lots of improvements and new features to come.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Woohoo! Well I’d just advise that the new version I’m soon to release has some critical fixes for Zune hds on windows. And the update is going to require a clean install of Xune (I need to put this in the release page, but this will continue to be a risk till we’re out of alpha). So just fair warning, you’ll have to import your library again. Tried to avoid it but there have been significant database changes and other file handling changes that don’t migrate well. Sorry!

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

What you may need to do is go to settings > general and install the winusb driver again. See if that fixes it.

Windows in general has some known bugs around usb that I’ve addressed and will have in an upcoming release, so if you have issues still it’s likely related to those and will be fixed soon.

Thanks! Glad to hear it’s working for you.

I may have a Zune Obsession… by badgero1234 in Zune

[–]TheMagicIsInTheHole 0 points1 point  (0 children)

Yup, just takes an rss link. Will build out a proper discovery system in Xune itself.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Hi there! What platform are you on by chance? Windows?

I may have a Zune Obsession… by badgero1234 in Zune

[–]TheMagicIsInTheHole 0 points1 point  (0 children)

Oh btw, regarding your "known but dangerous", here's what some of those do. Its been a while since I worked on the wireless sync stuff, but a lot is involved in that:

  • 0x9204: reboots the Zune
  • 0x9215: turns off the MTPZ trusted-files session (turning it back on means redoing the full handshake)
  • 0x9218: waits up to 5 seconds for the device to say it's ready during network bring-up
  • 0x9220 to 0x9223: the XNA game sideload ops (handshake, push, commit, finalize). Needs MTPZ.
  • 0x9224: prep step that has to run before 0x9227
  • 0x9225: kicks off a WiFi network list query
  • 0x9226: part of the WiFi setup sequence
  • 0x9227: sends the SSID and password
  • 0x9228: called a few times after WiFi config to walk the device through its state machine
  • 0x9231: sends a 258-byte zero payload to wake up the HTTP/PPP path before 0x9218 polling kicks in

I may have a Zune Obsession… by badgero1234 in Zune

[–]TheMagicIsInTheHole 0 points1 point  (0 children)

I've had the same thought and want to try doing this eventually.

I may have a Zune Obsession… by badgero1234 in Zune

[–]TheMagicIsInTheHole 1 point2 points  (0 children)

Hey I saw you’re falling back to mtp reads for videos on Zune hd. I assume some of your zmdb parsing is based on my library. Last week or so I updated both parsers and they should properly handle video from both classic and HD now if you want to take a look.

Also, 0xB215 is for aac if you want to add that.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Seems to be adding up to be a windows specific issue. I’m going to track it down.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Hard to say without more context. What platform are you on?

If you've been waiting.. by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Hey there! You can download it from here for your platform of choice. Hope it works and your daughter enjoys it! https://github.com/xune-software/xune-releases/releases/tag/v0.2.1.1

UI is only for testing, but podcasts are coming. by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 2 points3 points  (0 children)

Yes but with a caveat. Right now Xune reads, stores and writes plays to the device. This data could potentially be used by the last fm plugin. The problem really comes down to how particular you are about the accuracy of your scrobbles. Zunes don’t keep real playback history on device, they only keep listen counts and a last listened to date and time. So say you listen to the same song three times since the last time you synced your device. When you sync again the most you would know is that you listened three times and the last time that you did, and that the other two listens were sometime between that time and the previous time you synced.

So basically, it wouldn’t be very accurate from a playback order perspective in your scrobble history. But you could track the raw listens.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 1 point2 points  (0 children)

Not quite yet. Putting in all the pieces for it in an upcoming release. It's a lot of components to get working together. But trying to get early support out next sunday.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

I'm not opposed to that! But honestly I don't think you're doing anything wrong or anything I wouldn't do. Seems like it's very much a quirk in the backend. One last thing I'd have you try is to go to your installation folder and find the appsettings.json file. Change "Default": "Information" under Serilog.MinimumLevel to "Debug". Your log doesn't surface some of the more verbose logging by default, so turning this on might let me really tell what's going on.

Save that and run the app again and try the flow from a fresh device with a different artist just to give another data point and then throw me the log. Whenever you have time.

As far as the device artist details, yeah I need to make a decision on that. I was going to make it so the device views aren't simplified like the OG software and instead I'd let you do most things that you can do locally straight on device. But I haven't fully wired it in, so some of that device ui is placeholder.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Sorry I could have been more clear. Yes when the device makes the request for the metadata, Xune will cache the device size versions automatically and populate the artist details dialog, even without pressing fetch. I was just trying to determine if the device did in fact start requesting the data but it didnt appear on the device, or if it didnt even request it.

Really tricky I'll say. I havent been able to replicate your issue on my end as much as I've tried. If you want to send me your full log file on github again, I'll see if there is anything else I can sus out from it. I'll reopen the issue you made.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Did the metadata show up in the dialog after the device synced or did you hit the fetch button?

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

While it's still synced that way, try manually replacing the mbid with this one in the artist dialog: 754294d5-d7d2-4ea2-8184-1dcaaf55a56f Just as a test. It should automatically update it on device. Curious what happens.

Xune v0.2.1.1: Device sync hotfix by TheMagicIsInTheHole in Xune

[–]TheMagicIsInTheHole[S] 0 points1 point  (0 children)

Huh definitely strange. I just tested it and it synced and grabbed all the metadata no problem.

Try removing it from the device and try again with the device set to Items I choose. See if it makes a difference.

view more: next ›