Have you closed iTunes, waited a few seconds, then clicked the refresh icon beside the iTunes tree?
hi
i have the problem in recordbox when i have remove tracks in iTunes recordbox stil show them in the itues three? and i can't remove them from the list?
thanks
Post ist für Kommentare geschlossen.
Have you closed iTunes, waited a few seconds, then clicked the refresh icon beside the iTunes tree?
Hi
I have close en refres iTunes en recordbox but they stay in de iTunes tree and there from the pc removed But there is and red symbool begrote the songs
Thanks
Are you talking about songs you've imported to your collection, or songs in the iTunes portion of the tree?
Hi
I have first import my full iTunes collection in recordbox
Than I have remove songs there where dubble from iTunes and i remove them Oslo from recordbox collection
But when I restart everyting the songs stay in the iTunes tree with a wring red symbool and I can’t Remove them?
Thanks
Gino
You're starting to confuse the picture for me -- you had duplicates in iTunes and removed them from where?
Hi
all my music is in iTunes and when i started to use RB i import my whole collection in RB,
when this was happend and after time my collection in iTunes was to big and i source for double songs and deleted these in iTunes and in RB collection but the songs stay in rb iTunes tree and i can't delete them
greatz Gino
Those songs are in iTunes; if you have deleted them from iTunes, they won't appear within the rekordbox iTunes tree. If they do, it could be you have a sharing / permission issue with the iTunes library, or it hasn't been refreshed.
than it is a sharing/ permission issue because there no more in iTunes and i have refreshed rb iTunes tree
Try this, i had the same problem:
Songs still in my Itunes Cloud Library were causing this issue. Meaning the songs i bought with itunes but have been deleted from the hard drive. They were still hidden in my library as cloud songs. After clicking "View all Music" in Itunes i deleted all the songs with the cloud symbol and the problem was solved!
@christian > This was the topic; thanks for sharing it. :D