Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: AudioShell Beta Release (Read 31640 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

AudioShell Beta Release

Reply #25
As an aside, I used Get-AudioInfo of multiple files.  The cmdlet works as expected however it outputs a list of info without file names.  A quick check of file sizes will determine which files have been checked but it would be easier if file names were included by default.


Get-AudioInfo returns AudioInfo objects, which contain, well, information about the audio. Really, that cmdlet just returns the AudioInfo property (like calling $audioFile.AudioInfo). I might remove it, because it's a borderline useless cmdlet. AudioFiles also have a FileInfo property ($audioFile.FileInfo), which is what you want to look at.

AudioShell Beta Release

Reply #26
As an aside, I used Get-AudioInfo of multiple files.  The cmdlet works as expected however it outputs a list of info without file names.  A quick check of file sizes will determine which files have been checked but it would be easier if file names were included by default.


Get-AudioInfo returns AudioInfo objects, which contain, well, information about the audio. Really, that cmdlet just returns the AudioInfo property (like calling $audioFile.AudioInfo). I might remove it, because it's a borderline useless cmdlet. AudioFiles also have a FileInfo property ($audioFile.FileInfo), which is what you want to look at.


Yeah, I was just toying around to gauge the scope of the program; I tend to use MediaInfo when I need to read audio information.

AudioShell Beta Release

Reply #27
Version 0.9.5:

API Changes

  • ExtensionProvider is now a static class that includes additional common functionality.
  • Moved many properties into new SampleEncoderInfo and MetadataEncoderInfo classes.
  • New Get-AudioEncoderInfo and Get-AudioMetadataEncoderInfo cmdlets added.
  • Removed some obsolete cmdlets.
  • Added Day and Month to standard metadata.
Bug Fixes

  • Vorbis Comment DATE field is now parsed correctly.
  • ExtensionProvider now loads referenced assemblies in the root directory.
Other Changes

  • Lame extension now uses ReplayGain module for scaling (eliminates redundant code).
  • Proper WiX deployment projects added, now that Visual Studio Community Edition supports extensions.
  • Added shiny new icons!

AudioShell Beta Release

Reply #28
Version 0.9.7

This is the last API breaking release before 1.0.

API Changes
  • New Get-AudioAnalyzerInfo cmdlet added (replaces Get-AudioAnalyzerList)
  • Minor changes to the GroupToken class, for easier analyzer development
New Features
  • ReplayGain 2.0 (R128) analysis
Bug Fixes
  • Resolved crashes when using new cmdlets from a 64-bit process or when missing native libraries
Other
  • Bootstrap installer now includes the full Visual C++ 2013 Redistributable (required by various native libraries)

edit: Updated to 0.9.7. There was a serious bug in the iTunes metadata encoder that's been there for some time. You should reencode any MP4 files created with any earlier versions. Sorry!

AudioShell Beta Release

Reply #29
Version 0.9.8

This is a "release candidate" for version 1.0, assuming no serious bugs are identified.

Features

  • Upgraded FLAC extension to version 1.3.1.
  • WAVEFORMATEXTENSIBLE wave files can now be read.
  • Types returned by cmdlets are now serializable.
Bug Fixes

  • MP4 ©day atom now handles the full date, instead of just the year.

AudioShell Beta Release

Reply #30
Version 1.0.0 - First production-ready release!

Bug fixes
  • Better parsing of MP3s with "false syncs" due to cover art or other metadata.

For version 1.1, I'm focusing on cover art support.

AudioShell Beta Release

Reply #31
I know the name AudioShell was already addressed but I back in the day an HA member (IIRC, possibly, it was Jan) also had a small program named AudioShell that allowed you to change the default audio icons in WinXP.  I actually got a little excited that perhaps there was a new version to address Win7/8!
"You can fight without ever winning, but never win without a fight."  Neil Peart  'Resist'

 

AudioShell Beta Release

Reply #32
Hi Jebus,

thanks for your work on PowerShell Audio.

I created an entry in the Hydrogenaudio Wiki. Link
As a Logo I used the Icon of your executable. Hope that is fine with you.
Please tell me if you have any corrections or additional infos.

AudioShell Beta Release

Reply #33
Thanks for developing this tool, it seems promising.

Can someone tell me the proper command line to add SoundCheck to m4a files that already have Replaygain?

AudioShell Beta Release

Reply #34
Code: [Select]
Get-AudioFile "input.flac" | Measure-AudioFile "ReplayGain" -PassThru | Save-Metadata
When I try to use this command from the Primer I get the following error.

Code: [Select]
The term 'save-metadata' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path
was included, verify that the path is correct and try again.At line:1 char:69
+ get-audiofile .\b.flac | measure-audiofile "replaygain" -passthru |
save-metadat ...
+
~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (save-metadata:String) [], Comma
  ndNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

AudioShell Beta Release

Reply #35
Code: [Select]
Get-AudioFile "input.flac" | Measure-AudioFile "ReplayGain" -PassThru | Save-Metadata
When I try to use this command from the Primer I get the following error.

Code: [Select]
The term 'save-metadata' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path
was included, verify that the path is correct and try again.At line:1 char:69
+ get-audiofile .\b.flac | measure-audiofile "replaygain" -passthru |
save-metadat ...
+
~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (save-metadata:String) [], Comma
  ndNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
After comparing the Primer with your simple examples in the post it looks like Save-Metadata should be updated to Save-AudioMetadata in the Primer.

AudioShell Beta Release

Reply #36
Hi Jebus,

thanks for your work on PowerShell Audio.

I created an entry in the Hydrogenaudio Wiki. Link
As a Logo I used the Icon of your executable. Hope that is fine with you.
Please tell me if you have any corrections or additional infos.


Thanks! Can you please edit the sidebar to indicate the license is LGPL? I already updated the text.

AudioShell Beta Release

Reply #37
There is no reponse ? waiting here...

AudioShell Beta Release

Reply #38
Version 1.1:

Highlights
  • Cover art is now persisted during conversions.
  • Cover art can be extracted from file metadata, and/or loaded from external bitmap, JPEG and PNG files.
  • Cover art can be saved to a file as metadata, and/or exported to .png or .jpg image files.
  • For compression purposes, cover art images can be converted to JPEG format and/or resized.
  • Expanded Get-Help documentation for cmdlet parameters.
New Cmdlets
  • Clear-AudioFileMetadata
  • Convert-AudioCoverArt
  • Convert-AudioFileCoverArt
  • Export-AudioCoverArt
  • Export-AudioFileCoverArt
  • Get-AudioCoverArt
  • Get-AudioFileCoverArt
  • Set-AudioFileCoverArt
Cmdlet Changes
  • Get-AudioMetadata was renamed to Get-AudioFileMetadata
  • Save-AudioMetadata was renamed to Get-AudioFileMetadata
  • Set-AudioMetadata was renamed to Set-AudioFileMetadata
  • Many cmdlets that require an output directory have had their syntax changed, and now recognize the current directory and relative paths.

AudioShell Beta Release

Reply #39
Thanks for developing this tool, it seems promising.  Can someone tell me the proper command line to add SoundCheck to m4a files that already have Replaygain?


How do they already have ReplayGain stored? In an embedded ID3 tag? There is no atom for ReplayGain as far as I know.

Right now embedded ID3 tags are skipped. I could parse them if it's a useful feature.


AudioShell Beta Release

Reply #41
OK, i'll look into adding an APE reader at minimum to the next version. I don't think I want to include a writer though, since it's technically incompatible the MP4 specification. Maybe for MP3.

AudioShell Beta Release

Reply #42
How do they already have ReplayGain stored? In an embedded ID3 tag? There is no atom for ReplayGain as far as I know.

Right now embedded ID3 tags are skipped. I could parse them if it's a useful feature.


They are in APE tags generated by Foobar2000.

One more question. Is there a way to calculate and apply Soundcheck without converting from Replaygain?

AudioShell Beta Release

Reply #43
Not sure I understand what you mean. You have to calculate using the ReplayGain or the ReplayGain 2.0 (R128) algorithm. The algorithm Apple uses is proprietary (and doesn't support album gain, so IMO it isn't as good). If you use something like this, on an .m4a file:

Code: [Select]
$audioFile | Measure-AudioFile "ReplayGain 2.0" | Save-AudioFileMetadata -Setting @{AddSoundCheck = "Album"}


You are going to get SoundCheck tags, based on R128 analysis, on a per-album basis. No ReplayGain tags.

AudioShell Beta Release

Reply #44
Version 1.2.0 is out, with 64-bit AAC and Apple Lossless support. Previously you had to run under a 32-bit PowerShell prompt for these extensions to work. iTunes 12 shipped with 64-bit support libraries, so this is now possible.

This version also targets .NET 4.6, and some support libraries were recompiled. Basically, this is a maintenance release beyond the above.