next 2.0 beta

Posted by: cwillenbrock

next 2.0 beta - 26/11/2001 14:06

What's the timeframe for releasing the next public beta of the 2.0 software? Has there been any indication of a release date that I missed somewhere?

Just curious.
Posted by: muzza

Re: next 2.0 beta - 26/11/2001 19:32

when it's finished!tm
Posted by: cwillenbrock

Re: next 2.0 beta - 26/11/2001 21:08

I had a feeling somebody would say that.
Posted by: smu

Re: next 2.0 beta - 27/11/2001 18:47

Hi.

It was virtually released at the end of last week, it just didn't materialize into reality by now.

cu,
sven
Posted by: cwillenbrock

Re: next 2.0 beta - 27/11/2001 21:28

Ah that clears everything up!

Thanks for the insight.
Posted by: rob

Re: next 2.0 beta - 28/11/2001 05:07

The next release will go to the alpha team this week. If it works OK it will become a public beta within a day or two, if not - who knows!

Rob
Posted by: pgrzelak

Re: next 2.0 beta - 28/11/2001 06:03

Greetings!

Is there any hope of getting the release notes posted as a teaser, as you did with 2.0b3? This would be very helpful to identify what has been added / FITNR.
Posted by: rob

Re: next 2.0 beta - 28/11/2001 06:13

No, the release notes will be built with the release this time. There's little in terms of new functionality - mostly bug fixes. I'm not sure how useful it would be to review them ahead of time.

Rob
Posted by: Dearing

Re: next 2.0 beta - 28/11/2001 06:28

It would let us know what bugs have been found/fixed, since there is no open Bug List. I've found a couple related to bookmarks that I haven't mentioned yet, because I wanted to see if you guys already found them.
Posted by: rob

Re: next 2.0 beta - 28/11/2001 11:47

OK - no release notes, but here are the bugs fixed since beta3 (so far).

Player Fixes since 1.00-beta3

Fixed: Normalisation routines can seriously distort playback (#1142)
Fixed: Rotary button does nothing. (#36)
Fixed: Wish list: TOD in the time-cycle (#124)
Fixed: Changing volume from the remote control is too slow (#1121)
Fixed: More than 22 chars on the serial port exits the player. (#1108)
Fixed: Radio is silent when booting into radio mode. (#1005)
Fixed: Volume up/down speed from remote too slow. (#1383)
Fixed: Tuner/boot/stop mode switching issues. (#1386)
Fixed: Home EQ lets you set the EQ to four channels (#1389)
Fixed: Flashes to a screen with one horizontal line across the middle of the screen and reboots (#1119)
Fixed: Perpetual reboot with empty playlist (#1134)
Fixed: Play count (& other stats?) not updated in Repeat track mode (#1104)
Fixed: Time Display Modes in AUX Mode (#1393)
Fixed: Time mode info popups - cosmetic bug (#1073)
Fixed: Info:Track Clock doesn't update when time is set. (#1212)
Fixed: Now and Next overridden at in-car startup. (#1111)
Fixed: Anna Vu freaks out when tuner is pause/muted (#1112)
Fixed: TimeShade 128 behaves poorly with Info:Line/Transient (#1322)
Fixed: Player paused when returning from Tuner (#1324)
Fixed: Now and Next screen shows multiple repeats of single track (#1052)
Fixed: Clock timemode doesn't update while player is paused (#1137)
Fixed: Pushing the rotary brings up the fader at home (#1316)
Fixed: Beep Volume Window should beep (#1360)
Fixed: Track skip beeps for Kenwood but not Rio remote (#1140)
Fixed: Source switching problem after power-on in car (#1188)
Fixed: Hush volume level propogates across reboot to be normal volume (#1345)
Fixed: Absurdly short timeout on loudness/fader/etc. (#1377)
Fixed: Inappropriate menu choices in RADIO and AUX source modes (#1135)
Fixed: Rewind time pop-up window moves slowly. (#17)
Fixed: InfoTex visuals contain blitter and don't always get proper info fed to them (#976)
Fixed: "Title bar" text on search screens overlaps "xxxx tunes" text (#1020)
Fixed: Info:Transient doesn't display frequency when scanning in radio (#1038)
Fixed: No "pause" or "mute" indicator on Info:Tuner screen (#1109)
Fixed: Info screen clock stays at 24hr when Clock visual is at 12hr (#1114)
Fixed: After entering Year, search screens stop working (#1172)
Fixed: Tuner Info:Transient showing Mute indicator at startup in 2.0b4/b5 (#1197)
Fixed: Kenwood remote DNPP did not confirm time setting (#1211)
Fixed: If BPM is present, last line of Track Details screen is cut off (#1216)
Fixed: Rewind popup is "clock" if that's the current time mode (#1323)

Emplode Fixes since 1.00-beta3

Fixed: Checkbox in Emplode to switch playlist ordering modes (#979)
Fixed: Emplode fails to recognise genres, albums, artists (B5) (#1206)
Fixed: Soup views quit working on 2.0 Beta 5? (#1210)
Fixed: User should be warned that deleting a playlist doesn't do what they're expecting (#1105)
Fixed: Tags with leading zeroes are incorrectly parsed as octal when coerced to an integer (#1143)
Fixed: Wendy tab on track properties should not appear if player doesn't support wendy flags (#1164)
Fixed: No way to turn on quit option from emplode (#1222)
Fixed: Tracks with long comments fields get lost (#1329)
Fixed: Overall progress bar is not working (#1363)
Fixed: Bitrate column sorted oddly (#1400)
Fixed: There's no way to reset track metadata (#1413)
Fixed: Needs XML export (#1430)
Fixed: Need a "Yes to all" for deleting items from a search. (#1131)
Fixed: Total playlist play time value incorrect when editing properties. (#1346)
Fixed: Switching properties tabs loses changes. (#1358)
Fixed: Emplode truncates exit event WAV (#1031)
Fixed: Cut & paste into track properties doesn't forget font (#1056)
Fixed: Error writing player configuration (#919)

Emptool Fixes since 1.00-beta3

Fixed: emptool falls over on "cd /" if you start it with no parameters (#1118)

Upgrade Tool Fixes since 1.00-beta3

Fixed: "Serial Port In Use" Error Not Correctly Reported (#1214)
Fixed: Error message displayed when serial port is in use is rather lame (#1183)
Fixed: Installer for Emplode does not associate EmpegUpgrade.exe with .upgrade files. (#27)
Fixed: Upgrade does not listen for player "peace..." message soon enough (#1058)
Fixed: empegUpgrade uses wrong registry key (#1128)
Fixed: empegUpgrade uses wrong icon in Alt-Tab window (#1245)

End.
Posted by: morrisdl

Re: next 2.0 beta - 28/11/2001 12:37

Wow! Thats a truly amazing amount of work when you look at it like that. Great job!!

Thanks again for the fantastic support!
Posted by: Diznario

Re: next 2.0 beta - 28/11/2001 16:13

Looks good! Obviously you guys have been busy!

One question, regarding this fix:

Fixed: Rotary button does nothing. (#36)

What exactly is the funtionality now, and how will Mark's Hijack kernal affect it?
Posted by: tfabris

Re: next 2.0 beta - 28/11/2001 16:28

Yeah, I've been waiting for that shoe to drop. The biggest problem is that the new software will be released while Mark is gone.
Posted by: tonyc

Re: next 2.0 beta - 28/11/2001 16:33

Certainly one of us Linux hacks will be able to release an unofficial MLord kernel of the new beta.
Posted by: Roger

Re: next 2.0 beta - 29/11/2001 02:39

It toggles between the various sound settings (e.g. volume, fader, balance, etc.).
Posted by: smu

Re: next 2.0 beta - 29/11/2001 08:08

Hi Rob.

Player Fixes since 1.00-beta3
[...]
Emplode Fixes since 1.00-beta3
[...]
Emptool Fixes since 1.00-beta3
[...]
Upgrade Tool Fixes since 1.00-beta3
[...]


Nice cut'n'paste'd typo.
Quite busy you guys, right?

cu,
sven
Posted by: rob

Re: next 2.0 beta - 29/11/2001 12:30

Whoops.

You get the idea, though.
Posted by: davec

Re: next 2.0 beta - 29/11/2001 12:44

What about the sort by PIN in emplode? Roger said it was FITNR...
Posted by: Roger

Re: next 2.0 beta - 29/11/2001 13:19

It is. I fixed it on a CVS branch for "another product". Those changes got merged back into the v2.0 release, but Rob's bug query doesn't necessarily pick all of those up.

So:

Fixed: Needs PIN column (#1126)
Posted by: davec

Re: next 2.0 beta - 29/11/2001 13:27

In reply to:

Fixed: Needs PIN column (#1126)




Just making sure. Thanks!
Posted by: wvloon

Re: next 2.0 beta - 03/12/2001 04:13

According to this post a new build was released to the alpha team friday. Let's hope it's good enough for release, it would be nice to be able to sync again without having to downgrade to 1.03

Maybe Rob can share some "alpha team feedback" with us ?
Posted by: tfabris

Re: next 2.0 beta - 03/12/2001 13:15

Maybe Rob can share some "alpha team feedback" with us ?

It's certainly working OK for me, and has been fine all weekend.

There are a couple of items on the bug list which haven't been resolved yet, namely I had this one happen to me on Friday, but otherwise all the bug fixes they stated seem to be in there as promised.
Posted by: wvloon

Re: next 2.0 beta - 03/12/2001 15:59

I'm glad to hear that we don't have to start about horrible things involving fish again . I'll cross my fingers and hope for a new beta by the end of the week.
Posted by: xavyer

Re: next 2.0 beta - 03/12/2001 23:41

What?!? - You were listening to Bad Header Chili Peppers?
Posted by: tfabris

Re: next 2.0 beta - 04/12/2001 11:11

Heh. Actually, it was a Quoop Queen tune.
Posted by: cwillenbrock

Re: next 2.0 beta - 05/12/2001 18:33

It's certainly working OK for me, and has been fine all weekend

Great! I'm looking forward to seeing the next beta any time now.
Posted by: rob

Re: next 2.0 beta - 06/12/2001 03:48

There's an indication that it doesn't work with Mk.1's, which we're investigating now.

Rob
Posted by: cwillenbrock

Re: next 2.0 beta - 10/12/2001 09:34

Ah I see..

Well, do keep us posted :)
Posted by: wvloon

Re: next 2.0 beta - 20/12/2001 12:55

Any luck with fixing this yet or is it already clear that this will be a post-holidays beta ?
Posted by: rob

Re: next 2.0 beta - 20/12/2001 19:57

It's not clear either way yet. Tomorrow will be the critical juncture.

Rob
Posted by: hybrid8

Re: next 2.0 beta - 20/12/2001 20:22

Does it depend on how many pints go down at lunch? :)

Bruno
Posted by: andy

Re: next 2.0 beta - 21/12/2001 06:07

If we don't get a new beta for Xmas...

...any chance of just a rebuild of the player executable from 2.0b3 with the normalization feature turned off ?

Otherwise I will have to downgrade to 1.03 over the Xmas period, as most of my favourite albums are now doing the distorted output thing, I can't have people that I end up demoing it do over the period hearing it like that...
Posted by: svferris

Re: next 2.0 beta - 21/12/2001 13:01

Does the static problem happen to you a lot? I've only had it happen once so far, on one track. I removed the track and re-uploaded it, and everything was good.

If you have the problem songs readily available, I'd do this as a temporary fix, rather than downgrading.
Posted by: andy

Re: next 2.0 beta - 21/12/2001 13:17

I have only had the static problem a couple of times.

It is the clipped output that I have problems.
Posted by: andy

Re: next 2.0 beta - 21/12/2001 13:18

I have only had the static problem a couple of times.

It is the clipped output that I have problems with.
Posted by: mlord

Re: next 2.0 beta - 21/12/2001 15:07

I have tons of tunes that come out as a heavily clipped static mess with beta3, Blue Man Group being especially affected this way. But they seem to have fixed the bug internally, so hopefully the next public beta will solve this problem for us all.

-ml
Posted by: cwillenbrock

Re: next 2.0 beta - 21/12/2001 15:20

I sure hope so, because this has happened to me several times and is getting to be a real drag.