-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual Compilation #11
Comments
An alternative to this would be to add a new flag to the
Where For example, if the rules were partitioned by
Tells freyr to download the album and to use a custom source for a track in the album |
yeah, a good deal of advantage would be for anyone to easily manually compile any track in case one doesnt like the sound of a particular song or just being able to add an alternative version of a song to the album would be cool |
So, It's been a minute, and one more issue – #103. Looking at this now, I don't particularly like the Now, there are two approaches to this;
I think my personal preference is leaning towards #2. |
Tagging this "help wanted" so hopefully someone steps up to take this up. Unfortunately, I don't have as much free time to work on this. But I've prioritized it so maybe sometime soon. |
Does this work? it ask for '--sources'. doesnt work with '---source'. output: |
@Leezan-1, this hasn't been implemented just yet, unfortunately |
Sometimes, freyr's internal logic for identifying sources across services fails, and track(s) affected can't be downloaded.
We should provide a means for manual intervention.
Where a user could manually identify the source and provider URIs that freyr can thereafter compile a track from.
We can do this by introducing a new subcommand -
make
For example:
freyr make spotify:track:54bFM56PmE4YLRnqpW6Tha --source youtube:oDn4eKyhSH4
The text was updated successfully, but these errors were encountered: