search for: metadata_upd

...s->metadata = (char **)param; + s->newtrack = 1; + thread_mutex_unlock(&s->metadatalock); + break; default: LOG_WARN1("Unhandled event %d", ev); return -1; @@ -58,6 +89,24 @@ return 0; } +static void metadata_update(void *self, vorbis_comment *vc) +{ + stdinpcm_state *s = self; + char **md; + + thread_mutex_lock(&s->metadatalock); + + md = s->metadata; + + if(md) + { + while(*md) + vorbis_comment_add(vc, *md++); + } + + thread_mutex_unlock(&s->metad...

...e that's included in the source, you could search on the error code, find where it's blowing up, and then try to figure out what library it's using when it does. There may be a different version of that library for each different processor. if(encoding) { if(inmod->metadata_update) inmod->metadata_update(inmod->internal, &sdsc->vc); sdsc->enc = encode_initialise(stream->channels, stream->samplerate, stream->managed, stream->min_br, stream->nom_br, stream->max_br, stream->quality, &amp...

Hi Jens, this series removes the revalidate_disk() function, which has been a really odd duck in the last years. The prime reason why most people use it is because it propagates a size change from the gendisk to the block_device structure. But it also calls into the rather ill defined ->revalidate_disk method which is rather useless for the callers. So this adds a new helper to just