Duplicate albums, tagging issues

I’m getting duplicate albums popping up with the tracks dispersed between the two (see photo). What do I need to do to prevent this? I tagged everything in the latest version of iTunes because tagging in AO took too long, and did not solve the problem.

Also, when I make mixes, AO places the music back to their original location rather than all together under one album title.

Audirvana Origin 1.0.5 (10005)

macOS Version 12.4 (Build 21F79) with 32GB physical RAM

Connected account of : RONALD BUCK

SIGNAL PROCESSING:

Polarity Inversion:
	Globally: OFF
	Per track: ON
Effects plugins NOT ACTIVE

UPSAMPLING:
r8brain not in use
r8brain filter parameters
Bandwidth = 99.5%
Stop band attenuation 218dB
Phase linear

AUDIO VOLUME:
Max allowed volume: 100
Replay Gain: None
SW volume control: OFF

LIBRARY SETTINGS:
Sync list: 1 folders
AUTO: /Volumes/PIPER 6/HiResLibrary/iTunes Media/Music
iTunes/Music library synchronization: not synchronized
Library database path: /Users/ronbuck123/Library/Application Support/Audirvana/AudirvanaDatabase.sqlite

Remote Control server:
Listening on 127.0.0.1 on port 51428

=================== AUDIO DEVICE ========================

CoreAudio audio path, buffer I/O frame size: 512

Max. memory for audio buffers: 29696MB
Exclusive access: Enabled
Integer mode: Enabled

Preferred device:
APPLE INC. RON BUCK’S BEATS STUDIO³
Model UID:2009 4c
UID:50-1F-C6-60-91-ED:output

Active Sample Rate: 44.1kHz
Hog Mode is off

Bridge settings:
Sample rate limitation: none
Sample rate switching latency: none
Limit bitdepth to 24bit: OFF
Mute during sample rate change: OFF

Selected device:
Local audio device
ID 0x4a iMac Speakers
Manufacturer: Apple Inc.
Model Name: Apple Inc. iMac Speakers
Model UID: Speaker
UID: BuiltInSpeakerDevice

4 available sample rates up to 96000Hz
44100
48000
88200
96000
Audio buffer frame size : 14 to 4096 frames
Current I/O buffer frame size : 512
Volume Control
Physical: Yes
Virtual: Yes
MQA capability
Auto-detect MQA devices: Yes
Not a MQA device, user set to not MQA
DSD capability: Unhandled
Device audio channels
Preferred stereo channels L:1 R:2
Channel bitmap: Ox3, layout:
Channel 0 mapped to 0
Channel 1 mapped to 1

Audio channels in use
Number of channels: 2
Use as stereo device only: No
Simple stereo device: Yes

1 output streams:
Number of active channels: 2, in 1 stream(s)
Channel #0 :Stream 0 channel 0
Channel #1 :Stream 0 channel 1

Stream ID 0x4b 2 channels starting at 1
4 virtual formats:
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 96kHz
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 88.2kHz
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 48kHz
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 44.1kHz

4 physical formats
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 96kHz
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 88.2kHz
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 48kHz
2 ch Mixable linear PCM Interleaved 32 little endian Signed Float 44.1kHz

Local devices found : 1
Device #0: ID 0x4a iMac Speakers Manufacturer: Apple Inc. Model UID: Speaker UID: BuiltInSpeakerDevice Model Name: Apple Inc. iMac Speakers

UPnP devices found : 0

Hmm… How are the tags set when it comes to disc numbers?

If these aren’t set correctly, then you’ll end up with what you are describing.

I’m using JRiver Media Center to do all my tagging.

The same album in JRiver. All the tracks in the album have disc number 1 set. JRiver can set all tracks of an album at once this way. Instead of having to do it for each track seperately.

Hi everyone

I can change the disc/track problem… in Audirvana… it is a nuscience and I can’t figure out why this occasionanly by continually pops up. One day all in place, next AO start and duplicates and disc incorrectly numbered.

I go to the album, select all tracks and either remove any disc references or make then one disc of one.

Sometimes I have to rearrange the track numbers which is track by track which means I have to find the track order from “dust jacket cover” (that’s a fun reference) and then reorder those tracks.

I’d love to be able to open the pdf in an outside of Audirvana program. It’s annoying to want to read the notes but not have access to the tracks at the same time.
I don’t recall having to redo “that album” again.

One of my lovely early memories was sitting in my “listening/chair/room” and reading the cover or CD notes. These things… listening and reading accompany each other. Yes, I mostly listen to classical music but every-now-and-then it’s Joni Mitchell’s bio or Duke Ellington I want to read about.

Never Ye’s bio though. Ney, never Ye’s bio.

Another weird thing is the pdf disappearing. I have to download the zip/extract/replace pdf.

Ah, the mysteries of our lives make our lives interesting

I often wonder what the hell am I gunna do if I get everything perfectly aligned.

rolandarnold I have the same problem.

What I suspect is that this happens when I copy new music to my local MacOS drive while Nirvana Origin is running. Could it be that when Aurivana detects new content it indexes a partial album before all tracks have been copied to the drive; then Nirvana revisits the disk and creates another index entry of the album with the remaining tracks? Disclaimer: this totally a guess. In any case, it would be great to have a “merge” function to fix these duplicates.

1 Like

Merge is an excellent solution.

It is weird they way these things happen. I can understand on a new installation, but simply adding a new album…? Maybe something to do with the metadata online retrieving info system… I can’t remember what it’s called.

Dear all,
It appears that such an issue pops up when tagging is not correct (Some tracks are pointing to a different album).
But it also appear that in some cases, there are no issue with the tagging and there is no obvious reason leading to create separated albums. In such cases I already encountered at least twice, I tried to remove the tracks that were not put in the right place and copy them again, and “miracle” after another (or two) trials, finally all tracks are merged into only one album.

Maybe the hypothesis raised by Pierre168 is something to look at: file copy performed as the same time as import task by AS.

1 Like

Well… A couple of times I’ve simply deleted the album in AO or AS. Move the file from the source position. Closed AOoe AS. Reopened. Added file to source position… and still the erroneous data appears.

Hi to everyone
AO, AS and already A 3.5 had this issue. It has gotten better with time but never disapeared.
Before you add tracks to your library, tag them with an external app. I use Yate. Be sure that they are taged the way you want it, before you open Audirvana. Updating changed ID3 tags of already added tracks does not work correctly always.
After having synced, control if everything is alright and then make a backup of your new library. This way you always have a correct version of your library to go back to, if something happens.

1 Like

I know. But my excitement getting a new album is always eclipsed by administrative tasks.

I am always discovering these glitches days after the acquisition of a new file and then I have to remember to back up (to my three (yes three) external BU discs. It’s a nightmare and I want to see an easy fix. (Apart from gaining patience.)

Patience is a good virtue :wink:
There are so many threads of frustrated users about this problem.
It seems to be very difficult to solve it.

Philosophically we might look at the need for us (mere) human’s neediness for control. When things go wrong, out of our domain, we panic (I frequently panic and worry) for fear of loss… loss of control over our precious and fragile life/world. A mere 80 to 100 years and poof… nothingness.

I too was having duplicate albums and duplicate titles even if they are different files and the tagging is correct. Once I deleted the “.cue” files in the album, the library refreshed and the duplicate tracks are all fixed. Perhaps a clue for the devs as well.