Topic: volume label syntax is incorrect

[rigpimp]

I have been transferring some really esoteric hardcore punk vinyl from the mid 80's and I started to get this error on my 24/96 files last night.  If I double click then FOOBAR opens and plays them fine but I cannot used Wavelab, CD WAVE or Trader's Little Helper. 

The error I get says "the filename, directory name, or volume label syntax is incorrect".  I have tried to rename and move off my external and rename.

Anyone?

Is it a header issue?

[fleish]

I googled this and found several threads about illegal characters in the file/path names that could result in such an error

[rigpimp]

I googled this and found several threads about illegal characters in the file/path names that could result in such an error

I read that too but renaming stuff doesn't fix it.  I thought that it was actually spaces in the name that caused it.  I need a fix.

Here is an example of one of my file names: "Bedlam ‎– Lost In Space - Side B"

...and stop posting about my illegal characters in public forums!

[flipp]

Drive/Folder/Bedlam_LostInSpace_SideB.wav

What happens if you use the above syntax? Do you still get the same error message?

< if you are using the quote marks in your title, that is your illegal character >

[rigpimp]

Drive/Folder/Bedlam_LostInSpace_SideB.wav

What happens if you use the above syntax? Do you still get the same error message?

< if you are using the quote marks in your title, that is your illegal character >

I'm not using quotes.

[flipp]

Try importing (File > Import Raw) and opening the file in Audacity. You can edit the metadata there (File > Open Metadata Editor) if Audacity will open the file. Then save and see if your other programs will then recognize the newly saved file.

Other than that, I got nothin.

[rigpimp]

Try importing (File > Import Raw) and opening the file in Audacity. You can edit the metadata there (File > Open Metadata Editor) if Audacity will open the file. Then save and see if your other programs will then recognize the newly saved file.

Other than that, I got nothin.

Fuggin A on the Audacity call!  Import created a scratchy pile of puke but for grins I tried to open the file normally and it opened just fine.  Now if I can remember how to save the files in the same format they were already in and try to re-open them in Wavelab and RX2.  +T

Edit to say that I can open and edit the files in Audacity  but when I save them they are still in a state where I cannot open them with any other program other than FOOBAR to play the file.  I am baffled.

[flipp]

When you originally transferred them, what format/file extension was created?

Rather than "saving" in Audacity, try "Export" and use whatever extension you want.

[rigpimp]

When you originally transferred them, what format/file extension was created?

Rather than "saving" in Audacity, try "Export" and use whatever extension you want.

My source was turntable > V3 > R-44.  I ran everything through at 24/96.

I copied each R-44 file into individually named folders using the nomenclature BAND - LP NAME - SIDE.wav with those spaces and hyphens.  I also created a word document and pasted in LP info from www.discogs.com

I can export a 24 bit file from Audacity and it will play in FOOBAR fine but it still will not open in Wavelab or CD Wave.  It will open in Audacity or RX2.  I saved one from either RX2 or Audacity and took out all spaces and hyphens and I was able to get it to open in Wavelab.  I got super excited sure that I found the fix so I copied over all 8GB of LP sides onto a different drive.  When I did Teracopy told me one of the files was missing.  I looked on the drive and it was there so I tried to drag and drop it but windows said I did not have permission to copy the file.  I had to change the file properties to allow me to copy it over.  Why or how would that get changed?

Also the other LP side which mates with the file that I was able to open in Wavelab would not open at all.  It was just a copy and when I went to delete it windows said it was only 96MB while the original file was 250MB.  I am seeing some seriously weird shit across several hard drives and machines. 

[flipp]

When you originally transferred them, what format/file extension was created?

Rather than "saving" in Audacity, try "Export" and use whatever extension you want.

My source was turntable > V3 > R-44.  I ran everything through at 24/96.

I copied each R-44 file into individually named folders using the nomenclature BAND - LP NAME - SIDE.wav with those spaces and hyphens.  I also created a word document and pasted in LP info from www.discogs.com

I can export a 24 bit file from Audacity and it will play in FOOBAR fine but it still will not open in Wavelab or CD Wave.  It will open in Audacity or RX2.  I saved one from either RX2 or Audacity and took out all spaces and hyphens and I was able to get it to open in Wavelab.  I got super excited sure that I found the fix so I copied over all 8GB of LP sides onto a different drive.  When I did Teracopy told me one of the files was missing.  I looked on the drive and it was there so I tried to drag and drop it but windows said I did not have permission to copy the file.  I had to change the file properties to allow me to copy it over.  Why or how would that get changed?

Also the other LP side which mates with the file that I was able to open in Wavelab would not open at all.  It was just a copy and when I went to delete it windows said it was only 96MB while the original file was 250MB. I am seeing some seriously weird shit across several hard drives and machines.

Gotta agree with your last sentence. Sounds like you've either acquired some sort of nasty (malware, trojan, etc that's messing with your registry) or you are seeing the first signs of a component failure (hard drive, memory, power supply, cable, etc).

Like I said earlier, at this point I got nothin else to suggest.

[rigpimp]

Also the other LP side which mates with the file that I was able to open in Wavelab would not open at all.  It was just a copy and when I went to delete it windows said it was only 96MB while the original file was 250MB. I am seeing some seriously weird shit across several hard drives and machines.

Gotta agree with your last sentence. Sounds like you've either acquired some sort of nasty (malware, trojan, etc that's messing with your registry) or you are seeing the first signs of a component failure (hard drive, memory, power supply, cable, etc).

Like I said earlier, at this point I got nothin else to suggest.
[/quote]

It is interesting that you say that because the thought popped into my mind that I had bad reg files.  I found Malware the other day on my new laptop maybe even the night before this occurred.  I think that it was called Yontoo or something similar and I thought that it was a simple toolbar that got installed by utorrent, etc.  Either way it made it past my Avast! and Malwarebytes which both run real-time.  I uninstalled it and ran CCleaner to clear cookies and my registry.  Since then I have seen the issues seen above.  I think that I have a clean registry version that I am going to edit back in.  If that does not fix it I will simply wipe everyone's ass clean.  I back my shit up and do it regularly anyway and the install on the lappy is new with nothing to lose anyway.  My question is why it would be on both machines that run mutually exclusive of one another?

I never have stuff like this happen to me.  For 10 years + I am always the one cleaning up others messes for them.  Ugh.

[flipp]

Yontoo's toolbar mysteriously wound up on my Dad's laptop. He doesn't even know what a torrent is, much less ever used a torrent client. I "think" he got it as a driveby download from one of his financial newsletter advertisements but that was sheer subjection on my part. I recall it also installed some other program. Somewhere (sorry, don't recall where) one of the AV vendors had pretty good instructions on how to remove it. I just went to Add/Remove Programs and uninstalled both Yontoo and the other program, then ran whatever security suite was on his comp (Norton 360). Didn't notice any adverse effects after that but he never used the toolbar and it showed to have been installed the day before I asked him what it was so it didn't have much time to download more nasties. A quick google search shows some folks have minor problems while others have systems that are pretty much hosed. Good luck getting rid of it.

Please report back if you can successfully open/edit your vinyl transfers after getting rid of yontoo.

[rigpimp]

Just a quick follow up on what I think it was that caused the problem and how I fixed it. 

While naming folders and files I copied the artist and LP name off of discogs and pasted it right into the file name field.  There were illegal characters there that were not visible but were present.  I discovered the illegal characters presence via trader's little helper which showed them.  By going in and deleting all of the spaces and illegal characters as well as using underscores I never ran into any additional problems and never had to re-transfer anything.

Yontoo ended up not being the problem at all but that is long gone too.

Thanks to those that helped.

[flipp]

Thanks for the update and the solution. If I ever run into something similar I hope I remember to use TLH to see if there are invisible illegal characters.