PG Music Home
Posted By: andi.k BIAB 2010 MegaPak - missing RealTrack files!! - 01/17/10 03:28 PM
I downloaded & installed BIAB2010 Megapak inkl. 10Pak and there seem to be either some files missing or some bugs.

If I select style _POPOMED, BIAB complains about following real tracks missing:
style set 32, 524 guitar acoustic strumming ev 165
style set 27, 544 guitar electric rhytm dreamy ev 165

then, pressing play, it complains about following files missing:

c:\bb\relgt041.st2
c:\bb\racg25.st2

When I select _POPORGN or other styles, there are similar errors.

I tried BIAB 2010 update 294 - didn't help
I tried both RealTracks updates (August and December 2009) - didn't help

Rebuilding style list file doesn't help either.

Anyone?
Mega Pak only includes this:
MegaPAK RealCombos:
40 RealTracks in 10 Bands
Jazz Swing 140, Country Ballad 65
Pop Rock 120,Bossa 140, Bluegrass 130
Blues 120, American PopRock 120,
SmoothCool Jazz 100, JazzBallad 85,
HardRock Thrash 85
+ RealDrums Sets 1-5

You should have gotten the Ultra Plus Pak. If it's been less then 30 days they'll probably exchange.
I don't get it

Do you want to say that BIAB includes incomplete styles?

I mean, either an AddOn, Pak or whatever it is called is _installed_ or it is _not_.

So, when there is an error message about something missing, I conclude that there is something wrong with the installation...

But if this behaviour is a "feature", not a bug, that it is plain stupid and missleading to new users.
Yup we are all stupid. This is a user forum. If you want to rant email support. Read all about what you ordered first, so you are not embarrassed in the end. Sort of like you bought a new car and after a few days discover that it does not have a feature you wanted. Obviously it's the dealer's fault.

There exist different versions so that those who have limited budgets can get a Volkswagon beetle and upgrade to the Ferrari later.

Later.
Real Tracks & Real Drums are enhancements to the styles. The Mega Pak contains all 77 styles but will be limited to MIDI for those instruments that you don't have a Real Track or Real Drum file.
I'll assume this is a first time purchase. If you had checked here either asking or doing a search you'd find that the reccommendation from all of us old timers is to buy nothing less then the Ultra Plus Pak. Save up the extra $200 and go all the way.
As I said if it's been less then 30 days they'll upgrade you or take it back.
John Conley: John, you should take it a bit easier with the sarcasm. It doesn't come across as either helpful or friendly. Andi is only new to BIAB (and the forum) and he has a genuine concern. He hasn't had a chance to appreciate your sense of humor yet nor has he had the chance to appreciate that you can be a really helpful guy.

Andi,

When you are new to BIAB and you read the descriptions in the sales section of the website, it's easy for things not to be perfectly clear. I remember what it was like when I first purchased the product! When you compare the Megapak with the UltraPlusPak, you can see that the MegaPak has 40 Realtracks and sets 1 - 5 of Realdrums; the UltraPlusPak, on the other hand, has 82 Realtracks and 200+ Realdrums. Both installations have 77 style sets. The style sets are the basis of the backing arrangements you hear and work both in MIDI and with various pre-set configurations of Realtracks and Realdrums.

From what you say, it seems that some configurations of the styles that you have tried to load-in have Realdrums and/or Realtracks that are not included in the Megapak. In those cases, the styles can only be played with MIDI instruments replacing the missing Real-instruments. This is as it should be.

As silvertones has said, if you haven't yet had BIAB for 30 days, contact PGMusic. They are very honorable when it comes to their 30-day money-back guarantee. They want to see you happy too. (I'd contact them on their toll-free number immediately.) I strongly encourage you to get the package that has all Realstyles and Realdrums.

When you have a bit more experience with BIAB, you'll appreciate how it all works and it's never as confusing again.

All the best,
Noel
You didn't get me - despite Noel. It's not about "Oh, my new car misses some features I expected" but "Oh, my new car seems broken because it's giving me error messages."

That's it.

I didn't want to buy the Ultra Pak and still don't want to. Period.

My point is: why do they include incomplete styles and make BIAB complain about missing files!!??

From a stupid user perspective, I expect an application so be self-consistent, without open ends and broken parts.

So, when installing the Mega Pak, BIAB should be aware of being a Mega Pak installation and not bug the user with such non-sense error messages. Period.
Hi andi,

I notice you only joined the forums a day ago. I meant to say to welcome

Have you spoken to PGMusic about this to make sure that the Megapak you have is operating properly? If I were you, I'd be checking with PGMusic directly just to make sure.

These forums are a place where BIAB users help one another solve problems or give one another ideas. We don't have any say in the actual making or marketing of BIAB. It is possible that your MegaPak is not behaving in the way that it should be.

Regards,
Noel
There was no sarcasm intended. One looks at one's purchase and that's that.

If the issue is that from a Marketing Perspective missing 'pieces' that are for sale should be brought to the user's attention, then perhaps the methodology should be examined. The code may be 'old', and may have been put there when things were simpler, like all we had was 40 jazz styles 4 country styles, and 5 classical ones, and if one was undetected then the software flagged it. Who knows. It's a software issue, and probably nothing is missing. If you go through what you bought and compare, well it's there or it's not.

It took me over 10 years to cure my wife of coming home with 100 items on a grocery bill and ticking each item off her sales slip.

I do that at the store as the checkout is happening, and trust me, my memory is good enough to know the bananas were 19 cents / pound, and I sure as heck speak up. Here if it's wrong it's free. I once bought 10 pounds of bacon, the sign said 2.99 / pound. That was the previous weeks sale. My Dad was with me and he got 2 pounds. We get to the check out and gee doesn't the amount come to 4.00 / pound. I point out it's on an end aisle, big sign says 2.99 and according to the 'fair code of pricing', the bacon was free!

AT THE END of the day,this user forum is SOMETIMES watched by pg music, but any real concern should be documented, well written, and sent to pgmusic@support.com. I write them quite often...
Andi,
If the warnings is your only issue go to:
opt/preferences. On the first screen bottom right hand side "text Hints" uncheck everything.
Hello andi,

We have added a fix for this to the build 294 patch. Thank you for reporting it.
Quote:

Yup we are all stupid.



John,
This wasn't sarcasm? Then I'm offended.
Noel
[offtopic]
'we' may also relate to different egos of a single person...

But knowing to be stupid and still giving whatever answer jumps into ones mind whenever someone has a serious question... what's that called btw?
[/offtopic]

Anyways - PG Support responded and has fixed one of the styles. But there are many more that are broken and I sent a complete list with screenshots to support@pgmusic.com

Finally, I learned my lesson and won't be using the forum for reporting bugs anymore.
Don't let one poster steer you away from this forum, andi.k, it is likely going to be a needed resource for you as you get up and running.

Welcome!


--Mac
Andi,
The 294 fix was global in that it was meant to fix all. If your still having issues try DL the 294 patch again as it looks like on the 18 they added to it. What I'm saying is that although you have 294 it may be the old one. There should have been a 294b.
I _just_ downloaded+reinstalled 294 _just_ before I checked all styles and discovered that the following are broken:

=clap_be
_ROOTSRK
_bossgs
=RTSRKCT
=SLAMRK2
=TEKDRKA
_BOSSPF
_BOSSAF
_POPORGN
_BOSPGS
_POPSHB
=RTSRK16
_POPBRIT
_POPHAR2
_POPHARM
_ROKKAARP
=SYNTHRK

This was _after_ PGMusic told us about the fix.

So where does it say that 294 was meant to fix _all_?

It definitely doesn't.

On http://www.pgmusic.com/support_windowsupdates.htm#294 it says "Missing RT error in Pro and Mega versions." But the only styles that got fixed are the two mentioned in my first post.

I'd really appreciate people owning the MegaPak try it out themselves and people not owning the MegaPak... uhm... guest what.
Good catch, silvertones.

I just compared with the 294 I downloaded and installed the other day.

The earlier one is a bit smaller in overall size than the one that is there today.

While the Creation Dates in Properties are the same, the Modification Dates differ.

The earlier update has a Modification Date of 1-15.

The one I just downloaded has a Modification Date of 1-19.

Yes, I think that fit should have been published as "294b" also.

If you hadn't spotted that, I would be thinking I had 294 and it would be the same as everyone else's 294...


--Mac
Mac, do you have MegaPak?

294b from 1-15 was _beta_

294 from 1-18 is not beta anymore.

That's it.


Edit: ahh, well and please don't check the modification date. this is when you downloaded it. better check _creation date_


Quote:

Mac, do you have MegaPak?

294b from 1-15 was _beta_

294 from 1-18 is not beta anymore.

That's it.




In the past, going from beta to release has not included any changes or additions to the file.


Quote:


Edit: ahh, well and please don't check the modification date. this is when you downloaded it. better check _creation date_





?

Properties reports 3 dates.

Created:

Modified:

Accessed:

I cannot Modify the file by downloading or installing it.

Therefore the Modification date reflects something that happened at the file creator end of things.

The "Accessed" date should reflect anything I have done with the file since downloading.

I just didn't report the Accessed date above, as it is irrelevant to the scope of the discussion.

They are indeed two different files. One is slightly larger in size than the other. There is also now a longer list of things corrected over on the download page than what was there before, IIRC.


--Mac
Andi,
I removed the RT folder for the bass that is part of the =clap_BE that you mention in your list. If I then load the style I get the yellow warning stating the file was not found. That is how it's supposed to work.
Mac - I understand your concerns, but this seems to be the way, it works... under M$ Windows at least.

The update I downloaded today has _creation_ date 1-17 and _modification_ date 1-19 and a size of 6.537.709 Bytes (my timezone is GMT+1).

I guess that downloading indeed counts as a modification by the OS, at least the download process starts at zero bytes and then adds more bytes to the file until it's finished.

Why it manages to maintain the creation date according to the download server must be some http/ftp protocol magic.

Needless to say, but yes: date and time are properly set on my machine

-------

Back to topic, summing up the current state: the 294 non-beta patch does fix only _POPOMED, but does not fix the following styles:

=clap_be
_ROOTSRK
_bossgs
=RTSRKCT
=SLAMRK2
=TEKDRKA
_BOSSPF
_BOSSAF
_POPORGN
_BOSPGS
_POPSHB
=RTSRK16
_POPBRIT
_POPHAR2
_POPHARM
_ROKKAARP
=SYNTHRK


I'm not sure if PG received my emails... Does anyone get sorts of a receipt or even a reply when writing to support@pgmusic.com ? Do they have a bug tracking / ticketing system?
I think I need to drop out of this one. I don't even have a style called _POPOMED that's mentioned.And I've got them all. So....................Good bye.
Let me just reinforce as you never mentioned it. The flyby message for missing Real Tracks is supposed to be there.
silvertones - which BIAB version and Paks do you have?

I have BIAB 2010 MegaPak but I did not mention the 10-Pak which was included with my purchase (http://www.pgmusic.com/bonuspaks.htm).

_POPOMED is shown under "Classic" RealStyles [Rock], SD#94
I see what andi.k means concerning the dates now.


--Mac
Hello Andi,

We'll continue this via email, and will determine what happened. You may have got some of those files from a different installation, or perhaps are missing one of the install files. There was a problem with one of the files (fixed in the patch, thank you for finding that), but that's not related to the others.
Sorry Andi I don't have this style. I have 2010 Everything Pak.
Does anyone else have this _POPOMED Style ?
I'm curious why I don't.
John,
I have _POPO(FST, MSL, SLO) styles and no MED style. I have the UltraPak.
Noel
yea same here
Hi folks,

there's good news - problem solved - thanks to PG email support - no more complains about missing RealTrack files - everything's fine now

FYK:

_POPOMED seems to be included with a standard installation of BIAB2010 (BIAB main setup + Pro RealTracks 1+2) and gets updated by patch 294. The Memo says "Pop-Rock band with "Dreamy" Electric Guitar, Background Organ and Ac. Strumming. T = 100-130" and it is filed under "Classic Realstyles [Rock]"

=clap_be has been mistakenly installed because one of my MegaPak setup files has a bug. This will be fixed soon.

All other broken styles do not belong to BIAB MegaPak nor 10-Pak but got installed when I tried to fix _POPOMED by installing Realtrack Updates Aug08 and Dec09 provided at http://www.pgmusic.com/support_windows_realdrums.htm

As a result, style picker showed 21 RealStyles and 57 Realtracks where it should be only 10 RealStyles and 37 RealTracks.

These RT updates did not properly determine which RealTracks have to be updated and mistakenly installed additional style files. This is gonna be fixed soon as well.

In order to fix my BIAB installation I deleted everything, re-installed everything except RT updates, applied the 294 patch and deleted =clap_be.sty

Cheers,
Andi
To all:

Just a bit about how windows (in particular, windows explorer, which is called when you download a file, regardless of the browser in use) that may be useful. Unfortunately, the three date properties presented when you examine a file (e.g., downloaded), can be misleading.

The Created Date property is actually the date you downloaded the file (or if in the case of using windows explorer direct) is the date you copied it. This can be misleading to some windows users and has been a long standing issue with how windows handles files. Linux and other operating systems don't modify the create date when you copy or download a file. There are other "auto" file naming 'features' that windows explorer imposes on the user that are also problematic, but that is outside the scope of the Created Date attribute.

A postscript: If PG updates the information in the file, and you use the call up the properties dialog, click the Version tab, the file version and property version may be the only reliable version information. This would thus, require PG to make sure this reflects the actual version (e.g., in the 2010.0.0.294, 2010.0.0.294b, etc.)

Richard
To richard: Needless to say that this is very offtopic.... but as stated before, the update I downloaded on 2010-1-19 has _creation_ date 2010-1-17 and _modification_ date 2010-1-19. So, at least with Firefox under Windows XP, creation date is actually not the date when a file was downloaded but modification date is.
Well glad it's fixed for you. I and Noel and I suspect others don't have that _POPOMED style. They must have messed around with the Pro & Mega Pak.
if you download an older update, click on properties, you will see that both the create and modify date match your time of download. Hence, the properties of Windows modules used in the download. Off-topic, well, the topic replies included suggestions from forum members on determination of the file create/modify/accessed dates. If you download an older update, examine the properties, I believe you will see the create/modify dates reflect the download date. Accessed date will be when you examined the properties. BTW, I also use FF and XP.
Andi, I'm glad to hear that it's all worked out for you.
Noel
Listening to all this re,biab megapak as Ive just purchased this pack Ive got a feeling it was a mistake and I should have gone for the next one up.
Quote:

Listening to all this re,biab megapak as Ive just purchased this pack Ive got a feeling it was a mistake and I should have gone for the next one up.




Then contact PGMusic Sales right away to see about arranging an upgrade. They'll work with you, within reason and they are great people to deal with.


--Mac
© PG Music Forums