broadcast metadata not transferring to stream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
High
|
RJ Skerry-Ryan | ||
2.0 |
Won't Fix
|
High
|
RJ Skerry-Ryan | ||
2.1 |
Fix Released
|
High
|
RJ Skerry-Ryan |
Bug Description
I have a Mac with OS 10.6.8 (and access to 10.10 as well). I have loaded Mixx and used it successfully (on 10.6.8) to broadcast both live and with auto DJ. However, everything appears properly tagged (song, artist, album) in the library and autoDJ. It also appears on the decks properly. When transmitted to the station the tags are not transmitted.
We have several DJs using the software on PCs and this is not an issue.
Are there any special settings or patches to fix this problem?
Daniel Schürmann (daschuer) wrote : | #1 |
Changed in mixxx: | |
status: | New → Confirmed |
importance: | Undecided → High |
Christopher Johnson (cjohnson-k) wrote : | #2 |
We don't see the first song's tags either, may or may not be the same problem (wrt 1319754)
Ian Vince (ixn) wrote : | #3 |
I have verified all the metatags are present by streaming the same tunes unmixed in iTunes. This is a consistent, repeatable bug on my Mac. I'm using 10.11.5 and Mixx 2.0. It's the only real thing I have found that's wrong - it's an incredible piece of software otherwise
James (c-james-h) wrote : | #4 |
This is confirmed with me and thus far the only annoying problem I've had with Mixxx 2.0, was not present in 1.xx. Am running 10.9 Mavericks using a shoutcast Stream. Please fix! thank you so much!
Daniel Schürmann (daschuer) wrote : | #5 |
Unfortunately this high rates bug was not picked up since a while.
I assume there is no Mac + broadcasting user among the contributors and our mac build server is broken for a while.
For a fix, we need one who is able to build Mixxx from source and is willing to investigate the issue more. Are you?
You may try it using: http://
Else you may try our latest alpha build found here:
http://
It includes some more debug messages.
Please do a test run and provide your mixxx.log:
http://
Ian Vince (ixn) wrote : | #6 |
Hi - I tried out mixxx-2.
Daniel Schürmann (daschuer) wrote : | #7 |
could you provide the mixxx.log file?
Ian Vince (ixn) wrote : | #8 |
- Mixx log from a Mac running 10.11.6 Edit (47.3 KiB, text/plain)
Here's the most recent full log file. For some reason I've redacted my u/n - because I saw someone else do it.
Ian Vince (ixn) wrote : | #9 |
Let me know if this .log file isn't the one you need
Ian Vince (ixn) wrote : | #10 |
- Mixxx.log file - logged while live broadcasting Edit (32.4 KiB, text/plain)
So Sorry - the last attached was of a session where I was not streaming. In the log file attached here, I stream two tracks
Blue (dj-blue) wrote : | #11 |
OK, I was planning on compiling, streaming, and posting the log, but when I built the app, to my surprise, it actually worked sending the metadata. I compiled it with
scons hss1394=0 mad=1 faad=1 coreaudio=0 modplug=1 verbose=0
to use alternate mp3/mp4 support. I will recompile it and try it with core audio. Perhaps that will point someone in the right direction.
Christopher Johnson (cjohnson-k) wrote : | #12 |
That's great news dj-blue!!! Can we get our hands on that build? It would appear you have a working alternative. Is there some reason that would be an undesirable build on MacOS?
Blue (dj-blue) wrote : | #13 |
@Christopher Johnson
I just built the app from source using the instructions provided by Daniel up-thread. Specifically these: http://
The trick appears to have been including the MP3/MP4 internal support via the compile command I posted. This would seem to indicate the problem is in the "core audio" support. Let me know if you need more instructions on how I built it.
Daniel Schürmann (daschuer) wrote : | #14 |
Did you cross check that a coreaudio=1 build still suffers the issue?
It is an interesting result, since once the track metatdata is in the library, it should be independent from the used sound source.
If ther is actually a difference, could you add a debug message here:
Something like:
qDebug() << "EngineBroadcas
qDebug() << metadataFinal;
And verify if it is reached when changing the track?
Blue (dj-blue) wrote : | #15 |
- mixxx_compile.sh Edit (494 bytes, text/x-sh)
I've now tested with both core audio and the alternate mp3/mp4 builds. Both send metadata. Perhaps this is not so much of a bug as a bad build of the official distribution? Or perhaps a compiler upgrade between the release of 2.0.0 and now has corrected the issue? I haven't bothered adding your debug prints for obvious reasons.
I've attached my build script if this helps anyone else build a working version.
Ian Vince (ixn) wrote : | #16 |
Unfortunately, I am not a developer and found instructions rightfully geared towards people who have a clue. After messing about in Terminal, installing macports and Xcode, I found myself unable to troubleshoot my way out of it. Seems xcode 8 is playing silly buggers as well. Is there anyway that this fix can be uploaded as an alpha?
Matt (m-matt-w) wrote : | #17 |
Bump. Can we get a patch released to fix this? Would be greatly appreciated!
Thanks
Ian Vince (ixn) wrote : | #18 |
Bumping this as well. Would make my live mixing so much easier if the tags were attached to the stream. Would be more than happy to test out an alpha or beta and report back...
Blue (dj-blue) wrote : | #19 |
Repeat, this does not appear to be a bug. A build from source produces a working version. One of the devs needs to build this and re-release it, or you can build it yourself. I attached my build script up thread. You just need to follow the build instructions on the wiki page, selecting the Home Brew method, and then execute my script (you may need to change the versions at the top to match your library versions).
Ian Vince (ixn) wrote : | #20 |
Hi Blue - I have tried to compile this myself (using your script) and just get errors I don't understand how to fix - I've even looked up those errors, but I find that most of the help out there presumes a level of knowledge of compiling that I don't have. I don't have much experience using Terminal and CLI, so if things work with a couple of tweaks it's fine, but deep troubleshooting stops me in my tracks.
I understand that it isn't a bug so much as a mis-build and that it's a question of one of the devs re-compiling and releasing it. In the mean time, I'll try to hunt down what is going wrong with my builds, but there are only so many hours in the day...
Christopher Johnson (cjohnson-k) wrote : | #21 |
dj-blue is there any way you would be able to provide us a build to try?
Blue (dj-blue) wrote : | #22 |
Sorry no. This is open source. You need to build it yourself. I'm not a developer associated with this project, just a user. Hassle the developers please.
RJ Skerry-Ryan (rryan) wrote : | #23 |
cjohnson-k: can you please test build git5979 from here:
http://
Ian Vince (ixn) wrote : | #24 |
Hi RJ
I downloaded and tested build git5979 and unfortunately found the problem unresolved. A glance at my shoutcast stream page http://
Ian Vince (ixn) wrote : | #25 |
All the above ^^ for your info. And I forgot to say: thanks for all the work you do on Mixxx
Christopher Johnson (cjohnson-k) wrote : | #26 |
Ok, as the non-Mac guy here I'll ask what is likely to be a very stupid question. DJ Blue indicated that "...tested with both core audio and the alternate mp3/mp4 builds.
Both send metadata. Perhaps this is not so much of a bug as a bad build
of the official distribution? Or perhaps a compiler upgrade between the
release of 2.0.0 and now has corrected the issue?"
possible reasons suggested there are 1) bad build 2) compiler differences
But as a 40 year sw eng, instinct suggests some other possible causes...
3) OS dependency
4) sound system setup
5) sound system software or mixer dependencies
are support for these subsystems, like coreaudio, mad, etc provided in mixxx via statically linked libraries? are there assumptions that an expert Mac sound use might make that the rest of us wouldn't know about?
just some thoughts
RJ Skerry-Ryan (rryan) wrote : | #27 |
The difference between CoreAudio and libmad/libfaad (internal MP3/M4A decoding) is only at the point we read the metadata from the file to load it into the Mixxx library.
Ian: can you confirm whether the file you tested shows up with the correct artist/title in the Mixxx library? Based on your log file, you are loading both MP3s and M4As -- can you test one of each please?
If the metadata shows up in the library correctly, we can rule out CoreAudio/
Blue: Can you please confirm the version of libshout you have installed via homebrew (the output of "brew info libshout"). On the buildserver, we use libshout 2.4.1.
Everybody: Are you using Ogg or MP3 for your broadcast format? If you are using Ogg, do you have "Dynamically update Ogg Vorbis metadata" selected?
RJ Skerry-Ryan (rryan) wrote : | #28 |
If using Ogg, and "Dynamically update Ogg Vorbis metadata" is not selected, then it is expected that metadata is not updated. We don't do this by default because some streaming clients have bugs that don't deal well with receiving frequent Ogg metadata updates.
See https:/
"New in version 2.0: Dynamically update Ogg Vorbis metadata option
Dynamically update Ogg Vorbis metadata: Due to flaws in some streaming clients, updating Ogg Vorbis metadata dynamically can cause listener glitches and disconnections. Check this box to update the metadata anyway."
RJ Skerry-Ryan (rryan) wrote : | #29 |
Related: Bug #1012053
Christopher Johnson (cjohnson-k) wrote : | #30 |
FYI, we have a bunch of DJs, all using mixxx on Windows, and are unable to realiably stream m4a files without loss of tags, or more usually crashes. I've restricted all of them to mp3 only
RJ Skerry-Ryan (rryan) wrote : | #31 |
Thanks for the info Christopher -- Windows M4A and Mac M4A are entirely different beasts :) but that is really troubling indeed. It would be great to get more information about that issue but this bug isn't good for that since we're mostly talking about Mac here -- have you already left info on a different bug? I would love to hear if the latest Windows builds have this problem, since we have done significant amounts of work on the decoders since Mixxx 2.0 has been released that Mixxx 2.1 will include.
Bug #1635671 and Bug #1519472 look related.
Blue (dj-blue) wrote : | #32 |
$ brew list libshout
libshout: stable 2.3.1 (bottled)
Data and connectivity library for the icecast server
http://
/usr/local/
Poured from bottle on 2016-10-01 at 08:59:50
From: https:/
2.3.1 still seems to be the latest in the Brew repository, I did nothing special to install this version.
I'm using MP3 exclusively. I do not have "Dynamically update Ogg Vorbis metadata" selected.
Ian Vince (ixn) wrote : | #33 |
The files I am testing - M4a & MP3 - all show up with the correct artist/title in the Mixxx library but the tags don't get passed to the shoutcast server. These files will also play fine AND pass on the tags if played from any other music app.
The only thing I can add - which may be of some use(?) - when I connect the stream to a Shoutcast board in Second Life, it displays the title / artist of the last song I streamed with - say - iTunes - as though it hasn't been updated at all - even with a N/A. I wonder whether this might be a clue?
RJ Skerry-Ryan (rryan) wrote : | #34 |
Hi Ian,
Could you please let me know the answer to these two questions:
* Are you streaming with Ogg Vorbis or MP3 as your encoding format?
* Do you have "Dynamically update Ogg Vorbis metadata" checked?
Note, encoding format doesn't refer to whether the files you are playing are Ogg or MP3. You can check this in Preferences -> Live Broadcasting -> Format (in the Encoding section).
thanks!
Ian Vince (ixn) wrote : | #35 |
I am streaming with mp3.
I do NOT have "Dynamically update Ogg Vorbis metadata" checked?
The only other thing is I have Use UTF-8 encoding for metadata (which I believe is the default)
RJ Skerry-Ryan (rryan) wrote : | #36 |
I just tried Mixxx 2.0 (the release binary from our website) and it properly sends metadata on my machine using a locally running Icecast server in both MP3 and Ogg Vorbis encoding mode (with dynamic metadata update enabled). The latest code (master) also works for me in both modes when built from source or built by our build server. So I can't reproduce locally yet.
Blue -- I don't think you ever explicitly mentioned trying Mixxx 2.0 in this thread, just that you built from source and it worked. Just confirming, are you able to reproduce the issue with the Mixxx 2.0 release build?
Blue, Ian, Christopher, James -- can you please let me know what server (including version number) you are streaming to with Mixxx? (Shoutcast, Icecast, etc.) I am testing with Icecast 2.4.99.1.
Ian Vince (ixn) wrote : | #37 |
SHOUTcast Server Version 1.9.9beta/Linux
Ian Vince (ixn) wrote : | #38 |
As a btw: I also tried capturing the stream from Mixxx using Rogue Amoeba's "Nicecast" software (which streams output from apps to Icecast and Shoutcast servers)instead of using Mixxx's built in broadcast feature. Nicecast streamed the music but was not receiving the song titles/artists from Mixxx either.
Blue (dj-blue) wrote : | #39 |
I first encountered this with the standard build downloaded from here:
http://
After watching this thread for a while and seeing post #5 (https:/
I am streaming to a shoutcast server running version 1.9.8/linux
RJ Skerry-Ryan (rryan) wrote : | #40 |
Ah ha, so you're all using Shoutcast and not Icecast? I installed Shoutcast 1.9.8 for Linux on my server and can sort of repro:
* The latest builds from my machine properly send metadata.
* Mixxx 2.0 does not properly send metadata.
* The latest builds from the build server don't seem to connect to my Shoutcast server.
RJ Skerry-Ryan (rryan) wrote : | #41 |
Nevermind on the not connecting, it was some socket weirdness from SSH tunneling into my server.
* The latest builds from the build server don't properly send metadata.
RJ Skerry-Ryan (rryan) wrote : | #42 |
Looks like a bug in libshout 2.4.0 onwards.
* the Mixxx 2.0 release was packaged with libshout 2.4.0.
* our build server uses libshout 2.4.1
My machine was using homebrew for libshout so my version was 2.3.1. I uninstalled it and installed 2.4.1 from source and now my local builds don't send metadata correctly. I'll dig into the code changes between 2.3.1 and 2.4.0 to see if I can find the problem and report a bug upstream.
Ian Vince (ixn) wrote : | #43 |
Fine bit of detective work RJ. My version here is 2.4.1 also, so even if I'd managed to compile anything, it wouldn't have corrected the problem either. I'm guessing a rebuild using 2.3.1 is probably bad practice.
RJ Skerry-Ryan (rryan) wrote : | #44 |
Ah, looks like the key differentiator is being built with TLS mode enabled or not (the build server's libshout build has TLS enabled). If I build 2.4.1 with TLS enabled then the bug occurs but without TLS mode it works.
This switch statement doesn't consider SHOUT_TLS_AUTO (the default mode):
https:/
which results in shout_set_metadata failing.
Looks like this bug was fixed upstream in July:
https:/
https:/
Changed in mixxx: | |
assignee: | nobody → RJ Ryan (rryan) |
Ian Vince (ixn) wrote : | #45 |
Great news you got to the bottom of it. Looking forward to not typing out all the Artists/Titles and letting the shoutcast boards do the lifting. Once again, thanks for all the work you and the other devs do on Mixxx
Christopher Johnson (cjohnson-k) wrote : | #46 |
Wow, that's great work RJ. If the bug was fixed, what does that mean for the dumb user like me who doesn't want to do my own build? Are there any builds, beta or otherwise that support the newer libshout? Is there a way to turn off TLS being enabled by default at runtime that would allow the current 2.0 to work? Worst option would be perhaps some way to patch the existing 2.0?
As to the earlier question, Mark and I are using the same server, its shoutcast 1. How do I determine the exact version, if that's still useful information?
Ian Vince (ixn) wrote : | #47 |
Christopher: try pasting your full stream url, including port number eg: http://
RJ Skerry-Ryan (rryan) wrote : | #48 |
I'm going to fix the build server to patch libshout. After I do this, nightly builds should immediately be fixed. You can use these to work around the problem.
Mixxx 2.1 release will contain the fix. If we decide to do a Mixxx 2.0.1 patch release (still undecided), it will contain the fix also.
RJ Skerry-Ryan (rryan) wrote : | #49 |
I don't think I need any more information since I'm pretty sure the bug I found is the root cause, thank you!
Christopher Johnson (cjohnson-k) wrote : | #50 |
Our server is v2.4.7.
RJ, again with my apologies, would you mind posting a link once a nightly build exists we should try? If good, we can close this ticket. On behalf of Mark and I we thank you in advance
RJ Skerry-Ryan (rryan) wrote : | #51 |
Here's the first mac build (git5996) with the fix:
http://
RJ Skerry-Ryan (rryan) wrote : | #52 |
For reference, here's the fix patch I deployed on top of libshout 2.4.1:
https:/
I thought this was fixed in libshout by:
https:/
but I actually had to hack it a bit more.
In the "TODO: do something" block I put this:
++ if (self->tls_mode == SHOUT_TLS_
++ self->tls_mode_used = SHOUTERR_NOTLS;
++ return SHOUTERR_NOTLS;
++ }
++ self->tls_mode_used = SHOUT_TLS_DISABLED;
which probably isn't the right fix, but it works around the problem. It seems that self->tls_mode_used is still SHOUTERR_NOTLS when Mixxx calls shout_send_metadata even though we use SHOUT_TLS_AUTO, not SHOUT_TLS_
RJ Skerry-Ryan (rryan) wrote : | #53 |
Ian Vince (ixn) wrote : | #54 |
RJ - the workaround you've done in code works brilliantly in use. All my song titles and artists are now in the stream. Many many thanks to you and all who helped sort this.
RJ Skerry-Ryan (rryan) wrote : | #55 |
\o/ nice, glad to hear it. Sorry it took 9 months to get someone to take a look :(.
I wonder if this also affects Windows builds using libshout 2.4.0 w/ TLS enabled?
Christopher Johnson (cjohnson-k) wrote : | #56 |
I can certainly say the 2.0 release run by most of our DJs have no such issue with mp3 tags (Windows) but testing on the other platforms is a good idea.
Ian - and others who have tested it, please indicate the MacOS version you were running? This original report is for 10.6.8 and Mark would like to run it there. His first attempt at install appears to have not worked (installing). Is it necessary to uninstall a previous version?
RJ Skerry-Ryan (rryan) wrote : | #57 |
Mixxx 2.1 (which the build is a pre-release of) requires OS X 10.7 or higher, so that's why it's not working on 10.6.8 unfortunately.
(Mixxx on OSX doesn't have an installer, the DMG contains an app bundle that you can drag directly into your Applications folder -- so you can have two versions of Mixxx side-by-side)
Ian Vince (ixn) wrote : | #58 |
Christopher - I'm on El Cap - 10.11.6.
What I do to install is mount the .dmg and copy the app out on the desktop, rename it Mixxx-2-1a.app and then drop it in the applications folder. That saves me from copying over my previous working-
Matt (m-matt-w) wrote : | #59 |
#51
Thank you very much for that build R5996
I can confirm also that the bug is fixed here, There is a slight delay in it sending to the server but it's not a major issue.
Hopefully this bug will continue to be fixed in the next final release of Mixxx.
RJ Skerry-Ryan (rryan) wrote : | #60 |
This bug also affects Windows builds -- which were updated to libshout 2.4.0 right before the Mixxx 2.0 release.
A fix for the Windows build is deployed in 2.1 alpha from version "master-git6150" onwards. If you'd like to try it out, you can download it here: http://
summary: |
- metatags not transfering to stream on mac version + broadcast metadata not transferring to stream |
RJ Skerry-Ryan (rryan) wrote : | #61 |
Both the Mac and Windows builds are now updated for 2.1 (soon to go into beta) to have this bug fixed. Mixxx 2.0 is still affected and won't be fixed unless we do a 2.0.1 release.
RJ Skerry-Ryan (rryan) wrote : | #62 |
I received confirmation on IRC that the Windows build "master-git6150" resolves the problem on Windows.
Daniel Schürmann (daschuer) wrote : | #63 |
@shane n cal: If there is still an issue withe Metadata in 2.1 alpha, please file a new bug.
Please not that this is not fixed in Mixxx 2.0
shane n cal (shanencal) wrote : | #64 |
i been having a little problem to it might bee just me but when im using m ixxx it seens like beats are having a hard time after like a minute beats start losing sync and I might be just me have to stay on top of it. started happing recently but it could be just me .....
shane n cal (shanencal) wrote : Re: [Bug 1544739] Re: broadcast metadata not transferring to stream | #65 |
Think i understand so Im supposed to redownloaded 2.1 and install it? I had
2.1 and lost it during the up dates when i noticed it seemed to me that i
might have that problem, and after the up dates I found 2.0 installed and
no lames, so i replaced them, now im back at the same problem almost bit
not it seems like the beat line not lineing up correctly either and Im a
half a beat off and can't to find the top of that beat sometimesi was
wondering thanks shane
<https:/
Virus-free.
www.avast.com
<https:/
<#DAB4FAD8-
On Wed, Nov 15, 2017 at 11:39 AM, Be <email address hidden> wrote:
> ** Changed in: mixxx/2.1
> Status: Fix Released => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> broadcast metadata not transferring to stream
>
> Status in Mixxx:
> Confirmed
> Status in Mixxx 2.0 series:
> Confirmed
> Status in Mixxx 2.1 series:
> Fix Committed
>
> Bug description:
> I have a Mac with OS 10.6.8 (and access to 10.10 as well). I have loaded
> Mixx and used it successfully (on 10.6.8) to broadcast both live and with
> auto DJ. However, everything appears properly tagged (song, artist, album)
> in the library and autoDJ. It also appears on the decks properly. When
> transmitted to the station the tags are not transmitted.
> We have several DJs using the software on PCs and this is not an issue.
> Are there any special settings or patches to fix this problem?
>
> To manage notifications about this bug go to:
> https:/
>
Daniel Schürmann (daschuer) wrote : | #66 |
2.1 alpha is the version, that fixed the Mac metadata. The beatgrid off issue is a side effect from improving our MP3 decoder.
Now fixed decoding issues leading to a beatgrid offset. To fix it, you need to delete the beatgrid and analyse is again.
https:/
The solution for our final release is under consideration.
shane n cal (shanencal) wrote : | #67 |
my machine is way passed screwed up now i don't have any any recording
it does not keep any kind of sync or anything I have to do everything
manually it dosen't even show any kind of scale at all nothing if i didn't
know how to mixx beats already, i couldn't use it at all,,,, Im about to
thro this in the trash thats how frustrated I am right now it so broke
<https:/
Virus-free.
www.avast.com
<https:/
<#DAB4FAD8-
On Sun, Nov 19, 2017 at 11:27 PM, Daniel Schürmann <
<email address hidden>> wrote:
> 2.1 alpha is the version, that fixed the Mac metadata. The beatgrid off
> issue is a side effect from improving our MP3 decoder.
> Now fixed decoding issues leading to a beatgrid offset. To fix it, you
> need to delete the beatgrid and analyse is again.
> https:/
> The solution for our final release is under consideration.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> broadcast metadata not transferring to stream
>
> Status in Mixxx:
> Confirmed
> Status in Mixxx 2.0 series:
> Confirmed
> Status in Mixxx 2.1 series:
> Fix Committed
>
> Bug description:
> I have a Mac with OS 10.6.8 (and access to 10.10 as well). I have loaded
> Mixx and used it successfully (on 10.6.8) to broadcast both live and with
> auto DJ. However, everything appears properly tagged (song, artist, album)
> in the library and autoDJ. It also appears on the decks properly. When
> transmitted to the station the tags are not transmitted.
> We have several DJs using the software on PCs and this is not an issue.
> Are there any special settings or patches to fix this problem?
>
> To manage notifications about this bug go to:
> https:/
>
Be (be.ing) wrote : | #68 |
That sounds like you may have encountered Bug #1676140. We're working on a fix for that right now. In the meantime, try going to Options > Preferences > Interface and select a range for the pitch slider that isn't 0%.
shane n cal (shanencal) wrote : | #69 |
ok i got the lame squared away....
<https:/
Virus-free.
www.avast.com
<https:/
<#DAB4FAD8-
On Mon, Nov 20, 2017 at 8:51 PM, Be <email address hidden> wrote:
> That sounds like you may have encountered Bug #1676140. We're working on
> a fix for that right now. In the meantime, try going to Options >
> Preferences > Interface and select a range for the pitch slider that
> isn't 0%.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> broadcast metadata not transferring to stream
>
> Status in Mixxx:
> Confirmed
> Status in Mixxx 2.0 series:
> Confirmed
> Status in Mixxx 2.1 series:
> Fix Committed
>
> Bug description:
> I have a Mac with OS 10.6.8 (and access to 10.10 as well). I have loaded
> Mixx and used it successfully (on 10.6.8) to broadcast both live and with
> auto DJ. However, everything appears properly tagged (song, artist, album)
> in the library and autoDJ. It also appears on the decks properly. When
> transmitted to the station the tags are not transmitted.
> We have several DJs using the software on PCs and this is not an issue.
> Are there any special settings or patches to fix this problem?
>
> To manage notifications about this bug go to:
> https:/
>
shane n cal (shanencal) wrote : | #70 |
also the beats drag a bit and the songs studder four about mesure
sometimes two and three mesures and the indicater the moves with the song
disappears when it gets warm...
On Mon, Nov 20, 2017 at 10:09 PM, Shane N. Cal <email address hidden>
wrote:
> ok i got the lame squared away....
>
>
>
> <https:/
> www.avast.com
> <https:/
> <#m_-2707698581
>
> On Mon, Nov 20, 2017 at 8:51 PM, Be <email address hidden> wrote:
>
>> That sounds like you may have encountered Bug #1676140. We're working on
>> a fix for that right now. In the meantime, try going to Options >
>> Preferences > Interface and select a range for the pitch slider that
>> isn't 0%.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> broadcast metadata not transferring to stream
>>
>> Status in Mixxx:
>> Confirmed
>> Status in Mixxx 2.0 series:
>> Confirmed
>> Status in Mixxx 2.1 series:
>> Fix Committed
>>
>> Bug description:
>> I have a Mac with OS 10.6.8 (and access to 10.10 as well). I have
>> loaded Mixx and used it successfully (on 10.6.8) to broadcast both live and
>> with auto DJ. However, everything appears properly tagged (song, artist,
>> album) in the library and autoDJ. It also appears on the decks properly.
>> When transmitted to the station the tags are not transmitted.
>> We have several DJs using the software on PCs and this is not an issue.
>> Are there any special settings or patches to fix this problem?
>>
>> To manage notifications about this bug go to:
>> https:/
>>
>
>
Changed in mixxx: | |
status: | Confirmed → Fix Released |
Changed in mixxx: | |
assignee: | RJ Skerry-Ryan (rryan) → Reva Schaffer (r3vasu3) |
Daniel Schürmann (daschuer) wrote : | #71 |
Hi Reva, you cannot adopt a "Fixed Released" bug. Do you have a pending issue you like to fix?
If yes file a new bug, and adopt that.
This is a good start to read https:/
If you have any question or need help, ask here: https:/
Changed in mixxx: | |
assignee: | Reva Schaffer (r3vasu3) → RJ Skerry-Ryan (rryan) |
Swiftb0y (swiftb0y) wrote : | #72 |
Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https:/
lock status: | Metadata changes locked and limited to project staff |
Probably related Bug #1319754